Sunteți pe pagina 1din 708

See notice on first age

Alcatel-Lucent CDMA2000 1xEV-DO


Network
1xEV-DO
Release 30.0
Feature Provisioning Guide

401-614-413
Issue 5
May 2008

Alcatel-Lucent - Proprietary
This document contains proprietary information of Alcatel-Lucent and
is not to be disclosed or used except in accordance with applicable agreements.
Copyright 2008 Alcatel-Lucent
Unpublished and Not for Publication
All Rights Reserved

See notice on first age

Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their
respective owners.
The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright 2008 Alcatel-Lucent. All Rights Reserved.

Alcatel-Lucent - Proprietary
See notice on first page

Contents

About this information product


Purpose

.......................................................................................................................................................................................

Intended audience

...................................................................................................................................................................

xxiii

............................................

xxiii

..................................................................................................................................................................

xxiv

To obtain technical support, documentation, and training or submit feedback


Reason for reissue

xxiii

Chapter distribution

xxv

.................................................................................................................................................................

Operations and Maintenance Center - Radio Access Network (OMC-RAN) equivalents to common
Element Management System (EMS) screens ....................................................................................................... xxvii
Conventions used

xxxi

Related information

..............................................................................................................................................................

xxxii

History of revisions

............................................................................................................................................................

xxxiii

..................................................................................................................................................................

xxxiv

How to comment
1

....................................................................................................................................................................

CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Flexible Scheduler


Overview

......................................................................................................................................................................................

Availability

..................................................................................................................................................................................

Prerequisites

................................................................................................................................................................................

1-1
1-3
1-4

Feature description

...................................................................................................................................................................

1-5

Feature interactions

..................................................................................................................................................................

1-7

Impacts on the Element Management System (EMS)

..............................................................................................
...............

1-16

...................................................................................................................................

1-23

Impacts on the Operations and Maintenance Center - Radio Access Network (OMC-RAN)
Impacts on service measurements

1-8

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
iii
Issue 5, May 2008
See notice on first page

Contents

Implementing the feature


Activating the feature

....................................................................................................................................................

1-24

...........................................................................................................................................................

1-25

..........................................................................

1-26

..............................................................................

1-28

Configuring the Flexible Scheduler feature for Service Nodes


Configuring the Flexible Scheduler feature for base stations
2

CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Radio Access Network Authentication
(RAN)
Overview

......................................................................................................................................................................................

Availability

..................................................................................................................................................................................

Prerequisites

................................................................................................................................................................................

2-3
2-4

Feature description

...................................................................................................................................................................

2-5

Feature interactions

..................................................................................................................................................................

2-7

......................................................................................................................................

2-8

.......................................................................................................................................................

2-9

Impacts on service measurements


Implementing the feature
Activating the Feature

..........................................................................................................................................................

Provisioning the Access Terminal

2-10

................................................................................................................................

2-11

...................................................................................................................................

2-16

Configuring the feature using EMS

Provisioning the RAN AAA server

................................................................................................................................

Provisioning the route for RAN AAA on the TP


3

2-1

.....................................................................................................

2-17
2-18

Cell Swing Capability for EVolution Data Optimized (1xEV-DO)


Overview

......................................................................................................................................................................................

Availability

..................................................................................................................................................................................

Prerequisites

................................................................................................................................................................................

Feature description: Cell Swing Capability for 1xEV-DO

3-4
3-5
3-7

................................................................................................................................................................

3-19

..................................................................................................................................................................

3-22

Feature interactions
Issues and caveats

......................................................................................

3-1

Implementing the features


Activating the feature

..................................................................................................................................................

3-23

...........................................................................................................................................................

3-24

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

iv

Contents

Confirming feature activation


Determining the NthIP

...........................................................................................................................................

3-26

.........................................................................................................................................................

3-27

Move a 1xEV-DO cell (intra-RNC)

...............................................................................................................................

Move a 1xEV-DO cell (inter-RNC/Same Service Node)

......................................................................................

3-44

.........................................................

3-61

..........................................................................................................................................................................

3-79

Move a converged 1xEV-DO cell (inter-RNC/Different Service Node)


Rename a cell

3-29

Move and Rename a cell (intra-RNC)

..........................................................................................................................

Move and Rename a cell (inter-RNC)

........................................................................................................................

3-108

.......................................................................................................................................

3-126

Cell Swing backout procedure

.................................................................................

3-129

.......................................................................................................................

3-132

....................................................................................................................................

3-134

Verify OA&M on moved and/or renamed converged cell


Verify service measurements reporting
Cleanup of old Cell Swing files

3-93

Moving Base Stations from R1SR Based 1xEV-DO RNC APs to Universal Cabinet (UNC)-Based
1xEV-DO RNC APs ........................................................................................................................................................ 3-136
4

CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Handoff Matrix (HOM) Tool and
Related Features
Overview

......................................................................................................................................................................................

Availability

..................................................................................................................................................................................

Prerequisites

................................................................................................................................................................................

Feature description: 1xEV-DO HOM Tool feature (FID 12146.0)

......................................................................

Feature description: BC0/BC1 Dual Band 1xEV-DO (FID 8219.7)

.................................................................

4-1
4-5
4-6
4-9

4-12

...........

4-14

................

4-18

evstarthom command

............................................................................................................................................................

4-19

evdisphom command

............................................................................................................................................................

4-22

Feature description: 1xEV-DO Support for Multi-Carrier Coverage Differences (FID 8219.9)
Feature description: Support of Multiple 1xEV-DO Carriers - IFHO feature (FID 8219.11)

......

4-30

................................................................................................................................................................

4-32

Feature description: Six Sector Modular Cell 4.0B with Mixed 1x and 1xEV-DO (FID 8882.2)
Feature interactions

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
v
Issue 5, May 2008
See notice on first page

Contents

Service measurements: 1xEV-DO Support for Multi-Carrier Coverage Differences (FID 8219.9)
Issues and caveats

....

4-33

..................................................................................................................................................................

4-34

...................................................................................

4-37

.......................................................................................................

4-38

Implementing the 1xEV-DO HOM feature (FID 12146.0)


Activating the 1xEV-DO feature (FID 12146.0)
5

Per Call Measurement Data (PCMD) for CDMA 3G-1x EVolution Data Optimized
(1xEV-DO)
Overview

......................................................................................................................................................................................

Availability

..................................................................................................................................................................................

Prerequisites

................................................................................................................................................................................

5-4
5-5

PCMD terminology

..................................................................................................................................................................

5-6

Feature description

...................................................................................................................................................................

5-7

Issues and caveats

..................................................................................................................................................................

Post-processing tool guidelines

5-10

..................................................................................................................

5-11

........................................................................................................................................

5-15

How data is delivered to the OMP-FX v.2

...................

5-26

...................................................

5-47

How data is accessed from the OMP-FX v.2

.............................................................................................................

5-63

Using telnet to retrieve EV-DO PCMD data

..............................................................................................................

5-64

.................................................................................................................

5-66

Description of 1xEV-DO per-connection performance data delivered to the OMP-FX v.2


Per-connection performance data output examples from the OMP-FX v.2

Using FTP to retrieve EV-DO PCMD data

.........................................................................

5-68

..............................................................................................

5-70

................................................................................................................................................................

5-72

Using the EV-DO PCMD viewer to view EV-DO PCMD data


EV-DO PCMD viewer command format and syntax
Feature interactions

Implementing the feature

....................................................................................................................................................

Activating the PCMD for 1xEV-DO feature


6

5-1

..............................................................................................................

5-73
5-74

High Rate Packet Data Radio Network Controller (HRPD RNC) Performance and
Capacity Improvements
Overview

......................................................................................................................................................................................

6-1

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

vi

Contents

Availability

..................................................................................................................................................................................

Prerequisites

................................................................................................................................................................................
...................................................................................................................................................................

6-5

Feature interactions

..................................................................................................................................................................

6-7

....................................................................................................................................................................

6-8

Implementing the feature


Activating the feature

.......................................................................................................................................................

...........................................................................................................................................................

Deactivating the feature

6-9

6-10

...........................................................................................................

6-11

.......................................................................................................................................................

6-13

Activating the Carrier Capacity Enhancement

EVolution Data Optimized (1xEV-DO) Basic Revision A (Rev. A) Feature Bundle


Overview

......................................................................................................................................................................................

Availability

..................................................................................................................................................................................

Prerequisites

................................................................................................................................................................................

Feature description: Basic Rev. A Feature Bundle


Feature interactions

.....................................................................................................

................................................................................................................................................................

7-5
7-6
7-7

7-14
7-15

..................................................................................................................................................

7-30

...........................................................................................................................................................

7-31

Implementing the features


Activating the feature

7-1

...................................................................................................................................

Impacts on service measurements

6-4

Feature description

Issues and caveats

6-3

Enhanced Data Only Revision A (DOrA) Application Quality of Service (QoS) Features
Overview

......................................................................................................................................................................................

Availability

..................................................................................................................................................................................

Prerequisites

................................................................................................................................................................................

Feature descriptions: DOrA Application QoS Features


Feature interactions

................................................................................................................................................................

8-6
8-7
8-9

8-19

...................................................................................................................................

8-24

..................................................................................................................................................................

8-51

Impacts on service measurements


Issues and caveats

............................................................................................

8-1

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
vii
Issue 5, May 2008
See notice on first page

Contents

Implementing the features


Activating the feature
9

..................................................................................................................................................

8-52

...........................................................................................................................................................

8-54

CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Backhaul w/Multi Link Point-to-Point
Protocol at Layer 2 Over T1/E1
Overview

......................................................................................................................................................................................

Availability

..................................................................................................................................................................................

Prerequisites

................................................................................................................................................................................

9-4
9-5

Feature description

...................................................................................................................................................................

9-6

Feature interactions

..................................................................................................................................................................

9-9

....................................................................

9-10

...................................................................................................................................

9-11

..................................................................................................................................................................

9-12

Element Management System (EMS) configuration management


Impacts on service measurements
Issues and caveats

....................................................................................................................................................

9-13

...........................................................................................................................................................

9-14

Implementing the feature


Activating the feature

Provisioning cell2 RC/V form


10

9-1

..........................................................................................................................................

9-15

EVolution Data Only (1xEV-DO) Revision A (Rev. A) Voice Over Internet Protocol (VoIP)
and Application Pricing
Overview

....................................................................................................................................................................................

Availability

................................................................................................................................................................................

Prerequisites

..............................................................................................................................................................................

Feature description: 1xEV-DO Rev. A VoIP and Application Pricing (FID 12905.0)

...............................

10-5
10-6
10-7

...................

10-13

...........................

10-17

Feature description: 1xEV-DO Rev A Application Pricing Enhancements (FID 12905.1)


Feature interactions: 1xEV-DO Rev. A VoIP and Application Pricing (FID 12905.0)

10-1

Feature interactions: 1xEV-DO Rev A Application Pricing Enhancements (FID 12905.1)

..................

10-19

Impacts on service measurements: 1xEV-DO Rev. A VoIP and Application Pricing (FID 12905.0) ............
10-2010-2010-20
10-20
Impacts on service measurements: 1xEV-DO Rev A Application Pricing Enhancements (FID 12905.1)
........................................................................................................................................................................................ 10-2310-23
10-23
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

viii

Contents

License Key Installation


11

...................................................................................................................................................

10-24

Radio Network Controller (RNC) Grouping to Improve Idle Hand-off Performance


Overview

....................................................................................................................................................................................

Availability

................................................................................................................................................................................

Prerequisites

..............................................................................................................................................................................

11-1
11-3
11-4

Feature description

.................................................................................................................................................................

11-5

Feature interactions

................................................................................................................................................................

11-9

.................................................................................................................................

11-10

....................................................................................................................................................

11-13

................................................................................................................................................................

11-15

Impacts on service measurements


Impacts on TI messages
Issues and caveats

Implementing the feature

..................................................................................................................................................

11-18

Radio Network Controller (RNC) Group Setup Scenarios in Element Management System (EMS) ..........
11-1911-1911-19
11-19
Radio Network Controller (RNC) Group Setup Scenarios in Operations and Maintenance Center Radio Access Network (OMC-RAN) ..................................................................................................................... 11-26
12

EVolution Data Optimized (EV-DO) Performance Monitoring Tools Enhancements


Overview

....................................................................................................................................................................................

Availability

................................................................................................................................................................................

Prerequisites

..............................................................................................................................................................................

Feature description: 1xEV-DO Performance Monitoring Tools Enhancements (FID 9253.1)

...............

12-1
12-5
12-6
12-8

Feature description: 1xEV-DO Tool Interface between OMP-FX and 1xEV-DO RNC (FID 9253.2)
........................................................................................................................................................................................ 12-1112-11
12-11
..........................................

12-13

.............................................................................................................................................................

12-15

Feature description: AT Trace Enhancement for Customer Use (FID 9253.3)


Feature interactions

.................................................................................................................................

12-16

....................................................................................................................................................

12-17

Impacts on service measurements


Impacts on TI messages

Implementing the feature

..................................................................................................................................................

Activating the feature: 1xEV-DO Performance Monitoring Tools Enhancements

...................................

12-26
12-27

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
ix
Issue 5, May 2008
See notice on first page

Contents

Activating the feature: AT Trace Enhancement for Customer Use


Manual Pages: AT Trace Enhancement for Customer Use
13

12-28

................................................................................

12-29

Intra-Radio Network Controller (RNC) Session Resource Balancing in EVolution Data


Optimized (1xEV-DO)
Overview

....................................................................................................................................................................................

Availability

................................................................................................................................................................................

Prerequisites

..............................................................................................................................................................................

13-1
13-3
13-4

Feature description

.................................................................................................................................................................

13-5

Feature interactions

................................................................................................................................................................

13-7

Impacts on service measurements


Impacts on TI messages

...................................................................................................................................

....................................................................................................................................................

Implementing the feature


14

.................................................................

..................................................................................................................................................

13-8

13-11
13-14

Inter-User Priority for Best Effort Data Applications (IUPBEDA)


Overview

....................................................................................................................................................................................

Availability

................................................................................................................................................................................

Prerequisites

..............................................................................................................................................................................

14-1
14-4
14-5

Feature description

.................................................................................................................................................................

14-6

Feature interactions

................................................................................................................................................................

14-9

Sample call scenarios

.........................................................................................................................................................

Impacts on the AAA network element

........................................................................................................................

14-17

.................................................................................................................................

14-23

.................................................................................................

14-26

..................................................................................................................................................

14-29

.........................................................................................................................................................

14-30

Configuration and implementation considerations


Implementing the feature
Activating the feature

14-15

..........................................................................................................

Impacts on the OMC-RAN network element


Impacts on service measurements

14-10

Confirming feature activation

.........................................................................................................................................

Adjusting the IUP weight assignments for the Service Node

...........................................................................

14-31
14-32

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

Contents

Adjusting the IUP weight assignments for a BTS

.................................................................................................
.......................................................................

14-36

............................................................................................................................................................

14-37

Setting Inter-User Priority attribute in AAA subscriber profile


Enabling the feature
15

14-34

Jurisdictional Priority for Public Safety Users of Best Effort Data Applications
(JPPSUBEDA)
Overview

....................................................................................................................................................................................

Availability

................................................................................................................................................................................

Prerequisites

..............................................................................................................................................................................

Feature description

.................................................................................................................................................................

Feature interactions

.............................................................................................................................................................

Sample call scenarios

.........................................................................................................................................................

Impacts on the AAA network element

........................................................................................................................

Impacts on the OMC-RAN network element

..........................................................................................................

15-5
15-6

15-10
15-11
15-16
15-18
15-27

..................................................................................................................................................

15-34

.........................................................................................................................................................

15-35

Implementing the feature

.........................................................................................................................................

15-36

.........................................................................................................................................................

15-37

Confirming feature activation


Creating jurisdictions

15-4

.................................................................................................

Configuration and implementation considerations

Activating the feature

15-1

..............................................................................

15-39

Creating jurisdictional policies

.......................................................................................................................................

15-45

Updating jurisdictional policies

.....................................................................................................................................

15-47

Creating OMC-RAN user account restricted to jurisdiction

Making jurisdictional policy assignments

.................................................................................................................

15-49

Making BTS assignments for a jurisdiction

.............................................................................................................

15-56

Viewing BTS assignments for a jurisdiction

............................................................................................................

15-59

...................................................................................................

15-62

............................................................................................................................................................

15-64

Setting Subscriber Home Area attribute in AAA


Enabling the feature

Deactivating the feature

....................................................................................................................................................

15-66

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
xi
Issue 5, May 2008
See notice on first page

Contents

16

Universal Traffic Processor (UTP) Protocol Acceleration in Hardware


Overview

....................................................................................................................................................................................

Availability

................................................................................................................................................................................

Prerequisites

..............................................................................................................................................................................

16-3
16-4

Feature description

.................................................................................................................................................................

16-5

Feature interactions

................................................................................................................................................................

16-6

Configuration management

................................................................................................................................................

Activating the feature

16-7

...................................................................................................................................

16-8

...........................................................................................................................................................

16-9

Impacts on service measurements

17

16-1

Backhaul Enhancement in Support of Small Packets on the Reverse and Forward Links
in 1xEV-DO
Overview

....................................................................................................................................................................................

Availability

................................................................................................................................................................................

Prerequisites

..............................................................................................................................................................................

17-1
17-5
17-7

Feature description: Backhaul Enhancement in Support of Small Packets on the Reverse Link in
1xEV-DO (Phase 1a) (FID 12102.5) .......................................................................................................................... 17-9
Feature description: Backhaul Enhancement in Support of Small Packets on the Forward Link in
1xEV-DO (Phase 1b) (FID 12102.14) ..................................................................................................................... 17-10
Feature interactions: Backhaul Enhancement in Support of Small Packets on the Reverse and Forward
Links in 1xEV-DO features .......................................................................................................................................... 17-11
Implementing the features

................................................................................................................................................

17-14

Activating the Backhaul Enhancement in Support of Small Packets on the Reverse and Forward Links
in 1xEV-DO features via EMS ................................................................................................................................... 17-15
Deactivating the Backhaul Enhancement in Support of Small Packets on the Reverse and Forward
Links in 1xEV-DO feature via EMS ........................................................................................................................ 17-17
Activating the Backhaul Enhancement in Support of Small Packets on the Reverse and Forward Links
in 1xEV-DO features via OMC-RAN ...................................................................................................................... 17-18
Deactivating the Backhaul Enhancement in Support of Small Packets on the Reverse and Forward
Links in 1xEV-DO features via OMC-RAN ......................................................................................................... 17-20
Glossary
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

xii

Contents

Index

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
xiii
Issue 5, May 2008
See notice on first page

List of tables

About this information product


1
1

................................................................................................................................................

xxiv

CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Flexible Scheduler


1-1

Flexible Scheduler parameters

1-2

Flexible Scheduler parameters on the BTS instance page

1-3

Flexible Scheduler parameters

1-4

Flexible Scheduler parameters on the BTS instance page

1-5

1xEV-DO service measurements

............................................................................................................................

1-9

....................................................................

1-13

..........................................................................................................................

1-17

....................................................................

1-20

.....................................................................................................................

1-23

CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Radio Access Network Authentication
(RAN)
2-1

Reason for Reissue

1xEV-DO service measurements

........................................................................................................................

2-8

CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Handoff Matrix (HOM) Tool and
Related Features
4-1

Error Codes for evstarthom Command

.........................................................................................................

4-20

4-2

Error Codes for evdisphom Command

.........................................................................................................

4-25

4-3

Header Variables for evdisphom Command

...............................................................................................

4-26

4-4

Record Variables for evdisphom Command

...............................................................................................

4-27

4-5

1xEV-DO Support for Multi-Carrier Coverage Differences Feature: New Service Measurements
............................................................................................................................................................................ 4-334-33
4-33

....................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
xv
Issue 5, May 2008
See notice on first page

List of tables

Per Call Measurement Data (PCMD) for CDMA 3G-1x EVolution Data Optimized
(1xEV-DO)
5-7

5-1

EV-DO terminology

5-2

Key service measurements

5-3

SMs for DO SM Enhancements Phase 2

5-4

CFC values

5-5

Normal connection qualifiers

5-6

Dropped connection qualifiers

5-7

AT-Initiated/AN-Initiated Connection Failed - Subscriber

5-8

AT-Initiated/AN-Initiated Connection Failed - Cell

5-9

AT-Initiated/AN-Initiated Connection Failed - RNC

5-10

AT-Originated/AN-Originated Connection Failed - Network

5-11

EV-DO PCMD record data fields - Administrative

5-12

EV-DO PCMD record data fields - Session

5-13

EV-DO PCMD record data fields - Connection

.......................................................................................

5-31

5-14

EV-DO PCMD record data fields - RLP Layer

........................................................................................

5-36

5-15

EV-DO PCMD record data fields - Key Service Measurements

5-16

EV-DO PCMD record data fields - Personality Type:

5-17

EV-DO PCMD record data fields - Additional Data

5-18

DO PCMD RUM Fields

5-19

Flow Data Fields

5-20

Flow Final Classes (FFC) and FFC Qualifiers for Flow Reservation

5-21

evdo_pcmdaemon command options

.................................................................................................................................................
.................................................................................................................................

5-16

.....................................................................................................

5-19

...............................................................................................................................................................

5-20

............................................................................................................................
..........................................................................................................................

5-21
5-22

....................................................................

5-22

.................................................................................

5-23

...............................................................................

5-23

..............................................................

5-24

.................................................................................

5-28

...............................................................................................

5-29

.......................................................

5-36

...........................................................................

5-38

..............................................................................

5-38

.....................................................................................................................................

5-42

....................................................................................................................................................

5-44

.............................................

5-46

.............................................................................................................

5-70

EVolution Data Optimized (1xEV-DO) Basic Revision A (Rev. A) Feature Bundle


7-15

7-1

Protocols with Rev. A Physical Layer Feature: New and Modified Service Measurements

7-2

Inter and Intra-Radio Network Controller (RNC) Handoff Enhancement Feature: New Service
Measurements ....................................................................................................................................................... 7-28

..

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

xvi

List of tables

10

Enhanced Data Only Revision A (DOrA) Application Quality of Service (QoS) Features
8-1

RAN Quality of Service Enhancements for HRPD Rev. A Feature: New Service Measurements
............................................................................................................................................................................ 8-258-25
8-25

8-2

More QoS Enhancements for the HRPD Rev. A Network: Modified Service Measurements
............................................................................................................................................................................ 8-298-29
8-29

8-3

More QoS Enhancements for the HRPD Rev. A Network: New Service Measurements

8-4

More QoS Enhancements for the HRPD Rev. A Network: Existing Service Measurements
Pegged by Feature .............................................................................................................................................. 8-38

8-5

More QoS Enhancements for the HRPD Rev. A Network: Renamed Service Measurements
............................................................................................................................................................................ 8-388-38
8-38

8-6

Data Over Signaling Protocol Feature: New Service Measurements

8-7

.......

8-30

...............................................

8-44

RNC sector carrier service measurements

...................................................................................................

8-45

8-8

HCS sector carrier service measurements

...................................................................................................

8-45

8-9

HDR sector carrier service measurements

...................................................................................................

8-46

8-10

OHM-PageableProfileID service measurements

8-11

OHM-PageableProfileID-PageAttempt service measurements

8-12

OHM-PageableProfileID service measurements

8-13

OHM-PageableProfileID-PageAttempt service measurements

8-14

RNC-pgpf service measurements

8-15

Valid Combinations for DoS Method and Paging Area Settings

.......................................................................................

8-48

............................................................

8-48

.......................................................................................

8-49

............................................................

8-49

....................................................................................................................

8-49

.......................................................

8-61

CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Backhaul w/Multi Link Point-to-Point
Protocol at Layer 2 Over T1/E1
9-1

Related RC/V forms

9-2

Related fields in the cell2 page

9-3

1xEV-DO service measurements - Data link counts

9-4

Fields to be populated in the cell2 form

.............................................................................................................................................
....................................................................................................................

9-10
9-10

...............................................................................

9-11

..................................................................................................

9-15

EVolution Data Only (1xEV-DO) Revision A (Rev. A) Voice Over Internet Protocol (VoIP)
and Application Pricing
10-1

1xEV-DO service measurements - BTS-HDR Counts

.........................................................................

10-20

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
xvii
Issue 5, May 2008
See notice on first page

List of tables

11

13

14

15

10-2

1xEV-DO service measurements - SECT-CARR-HDRC counts

.....................................................

10-20

10-3

1xEV-DO service measurements - SN-RNC counts

.............................................................................

10-21

Radio Network Controller (RNC) Grouping to Improve Idle Hand-off Performance


....................................................

11-10

...........................................................................................................

11-10

...............................................................................................................................

11-20

11-1

1xEV-DO service measurements - SECT-CARR-HDRC Counts

11-2

Other Service Measurement Impacts

11-3

Modify Paging Parameters

11-4

Values for Auxiliary Service Node Control - 1

11-5

Modify Paging Parameters

11-6

Values for Auxiliary Service Node Control - 1

......................................................................................

11-24

...............................................................................................................................

11-27

......................................................................................

11-32

Intra-Radio Network Controller (RNC) Session Resource Balancing in EVolution Data


Optimized (1xEV-DO)
13-1

1xEV-DO service measurements - OHM Counts

13-2

1xEV-DO service measurements - SECT-CARR-HDRC Counts

13-3

1xEV-DO service measurements - SECT-CARR-HDRC CI Counts

.....................................................................................
......................................................
................................................

13-8
13-8
13-9

Inter-User Priority for Best Effort Data Applications (IUPBEDA)


14-1

Related AAA subscriber profile attributes

................................................................................................

14-15

14-2

3GPP2-Inter-User-Priority attribute format

...............................................................................................

14-15

14-3

Related fields in EvDO RNC FAF form

...................................................................................................

14-17

14-4

Related fields in EvDO RNC FAF form

...................................................................................................

14-18

14-5

Related fields in Cell Site Configuration form

14-6

HCS service measurements

14-7

Example assignment of Inter-User Priority values

14-8

Example of adjusting Inter-User Priority Weights to reduce impact of priorities

14-9

Example of adjusting Inter-User Priority Weights for specific user classes

.......................................................................................

14-20

.............................................................................................................................

14-23

................................................................................

14-26

....................

14-27

...............................

14-28

Jurisdictional Priority for Public Safety Users of Best Effort Data Applications
(JPPSUBEDA)
15-1

Related AAA subscriber profile attributes

................................................................................................

15-16

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

xviii

List of tables

15-2

3GPP2-Inter-User-Priority attribute format

...............................................................................................

15-16

15-3

Lucent-VID-Home-Area attribute format

................................................................................................

15-17

15-4

Related fields in EvDO RNC FAF form

...................................................................................................

15-18

15-5

Related fields in SN General form

..............................................................................................................

15-19

15-6

Related fields in Serving Jurisdiction Main Details form

15-7

Related fields in Serving Jurisdiction BTS Allocation Details form

15-8

Objects in Serving Jurisdiction subtree

15-9

Related fields in the BERoamPolTable Instance Details form

..................................................................

15-20

.............................................

15-21

......................................................................................................

15-22

.........................................................
..............................................

15-25

..........................................................................................

15-30

15-10 Related fields in Serving Jurisdiction RoamPolAssgn Details form


15-11 Sample Jurisdictional Policy TreatAsLocal

15-23

15-12 Sample Jurisdictional Policy AdjustedService

.....................................................................................

15-31

15-13 Sample Jurisdictional Policy StandardService

.....................................................................................

15-31

...........................................................................................

15-32

15-14 Sample Jurisdictional Policy BasicService

15-15 Tasks permitted for OMC-RAN user account types

.............................................................................

15-33

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
xix
Issue 5, May 2008
See notice on first page

List of figures

CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Flexible Scheduler


1-1

Service Nodes/Flexible Scheduler instance page

1-2

BTS instance page

1-3

Service Nodes/Flexible Scheduler instance page

1-4

BTS instance page

14

.................................................................................................................................................

1-9

1-12

......................................................................................

1-16

.................................................................................................................................................

1-19

CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Radio Access Network Authentication
(RAN)
2-1

........................................................................................

1xEV-DO RAN Authentication architecture

.................................................................................................

2-6

Per Call Measurement Data (PCMD) for CDMA 3G-1x EVolution Data Optimized
(1xEV-DO)
5-12

5-1

EV-DO PCMD data delivery path

5-2

Example raw data output from the OMP-FX v.2 with RUM disabled

...........................................

5-48

5-3

Example raw data output from the OMP-FX v.2 with RUM enabled

............................................

5-48

5-4

Example raw data output from the OMP-FX v.2 with RUM and Flow enabled

..................................................................................................................

........................

5-48

CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Backhaul w/Multi Link Point-to-Point
Protocol at Layer 2 Over T1/E1
9-1

EVDO Network Configuration Diagram with a MLPPP

9-2

RC/V form cell2

........................................................................

.....................................................................................................................................................

9-7

9-16

Inter-User Priority for Best Effort Data Applications (IUPBEDA)


14-1

Example Application of the Inter-User Priority for Best Effort Data Applications feature

14-2

Establishment of New Data Session with Inter-User Priority

....

...........................................................

14-8

14-11

....................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
xxi
Issue 5, May 2008
See notice on first page

List of figures

15

14-3

Reactivation of existing data session with IUPBEDA enabled

........................................................

14-13

14-4

Snapshot of portion of EvDO RNC FAF form

.......................................................................................

14-18

14-5

Snapshot of portion of SN General form

..................................................................................................

14-20

14-6

Snapshot of portion of Cell Site Configuration form

14-7

Sample HCS service measurement report

...........................................................................

14-22

.................................................................................................

14-25

Jurisdictional Priority for Public Safety Users of Best Effort Data Applications
(JPPSUBEDA)
15-1

Example Application of the Jurisdictional Priority feature

15-2

Establishment of New Data Session with Home Area Attribute

15-3

Reactivation of existing data session with JPPSUBEDA enabled

15-4

Snapshot of portion of EvDO RNC FAF form

15-5

Snapshot of portion of SN General form

15-6

Snapshot of Serving Jurisdiction Main Details form

15-7

Snapshot of Serving Jurisdiction BTS Allocation Details form

15-8

Snapshot of of Serving Jurisdiction subtree

15-9

Snapshot of of Serving Jurisdiction BERoamPolTable Details form

..................................................................

15-14

.......................................................................................

15-19

..................................................................................................

15-20

...........................................................................

15-21

......................................................

15-22

.............................................................................................

15-23

............................................

15-24

.......................................................

15-26

..............................................................

15-28

..............................................................................................................

15-29

15-11 Example of geographic border splitting BTS service areas

17

15-12

..................................................

15-10 Snapshot of Serving Jurisdiction RoamPolAssgn Details form

15-12 Example use of border jurisdiction

.....................................................

15-9

Backhaul Enhancement in Support of Small Packets on the Reverse and Forward Links
in 1xEV-DO
..................................................................................................................................

17-16

.........................................................................................................................................

17-19

17-1

EMS SN General Screen

17-2

OMC General Screen

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

xxii

About this information product


About this information product

Purpose

The 1xEV-DO Feature Provisioning Guide, 401-614-413 is a new document for


Release 27.0 and later. It was developed based on the needs of the Service Provider
who requested all 1xEV-DO procedural information be accessible in one document. All
1xEv-DO procedural features for R27.0 and later are documented in this guide.
This guide also includes all the feature information from the following 1xEV-DO
Feature Description documents from earlier releases, including:

1xEV-DO Flexible Scheduler, 401-614-400


1xEV-DO Radio Access Network Authentication, 401-614-402
Cell Swing Capability for 1xEV-DO, 401-614-407
1xEV-DO Handoff Matrix (HOM) Tool and Related Features, 401-614-409
Per Call Measurement Data (PCMD) for 1xEV-DO, 401-614-410
HRPD RNC Performance and Capacity Improvements, 401-614-412

Intended audience

This document is designed for system administrators and other technical personnel who
perform operations, administration, and maintenance (OA&M) on the elements of a
CDMA2000 1xEV-DO wireless networks.
To obtain technical support, documentation, and training or submit feedback

The Online Customer Support (OLCS) web site (http://support.lucent.com/) provides


access to technical support, related documentation, related training, and feedback tools.
The site also provides account registration for new users.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
xxiii
Issue 5, May 2008
See notice on first page
,

About this information product

Reason for reissue

This document supports numerous 1xEV-DO features and their releases. New releases,
software updates or Modification Requests (MRs) introduce new features or updates
reflected in Table 1, Reason for Reissue (p. xxiv) listed below. For content and
changes of previous issues see History of revisions (p. xxxiii):
Table 1

Reason for Reissue

Feature
Identification (FID)
Number

Base Release/SU
Release

Chapter Number

Issue

Addition of
OMC-RAN
Procedures

R30 and later

Multiple Chapters
throughout the
document

FID 8219.9

R30.0 and later

Chapter 4

FID 9253.3

R30.0 and later

Chapter 12

FID 10737.9

R30 and later

Chapter 3

FID 12102.5

R29.0 and later

Chapter 17
(new)(was
document
401-614-416)

FID 12102.14

R29.0 and later

Chapter 17 (new)
(was document
401-614-416)

FID 12885.1

R30.0 and later

Chapter 3, see
Feature Interactions

FID 12370.1

R30.0 and later

Chapter 5

FID 12766.2

R30.0 and later

Chapter 5

FID 12780.3

R30.0 and later

Chapter 16 (new)

FID 13181.0*

R30.0 and later

Multiple Chapters
throughout the
document

*Impact of Support for up to 999 CDMA/3G-1x cells (FID 13181.0): The maximum
number of cells that may be supported in a system is dependent upon which (if any)
cell-numbering feature is implemented in that specific system. The base system allows
for a maximum of 222 cells. Cell-numbering features may be implemented to increase
this maximum. Therefore, this document has been updated to generalize any
information about the maximum number of cells supported in a system, rather than
state a possible limit (such as, 384 or 600, etc).

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
,

xxiv

About this information product

Chapter distribution

This document contains the following CDMA 3G-1x EVolution Data Optimized
(1xEV-DO) procedural chapters which cover the CDMA2000 1xEV-DO networks.

Chapter 1, 1xEV-DO Flexible Scheduler, describes the 1xEV-DO Flexible


Scheduler feature, FID 8948.0.
Chapter 2, 1xEV-DO Radio Access Network Authentication, describes the
1xEV-DO Radio Access Network Authentication feature, FID 8103.0.
Chapter 3, Cell Swing Capability for 1xEV-DO, describes the Cell Swing
Capability for 1xEV-DO features:
Cell Swing Capability for 1xEV-DO, FID 12188.0
Cell Swing Capability for 1xEV-DO, FID 12188.1
Privilege Minimization and Restrict Root Login in 1xEV-DO RNC APs , FID
10737.9
Chapter 4, 1xEV-DO Handoff Matrix (HOM) Tool and Related Features, provides
service providers with important information to assist in 1xEV-DO neighbor list
adjustments needed to improve handoff performance. Related features include:
1xEV-DO Handoff Matrix (HOM) Tool, FID 12146.0
BC0/BC1 Dual Band 1xEV-DO, FID 8219.7
Dual Band 1xEV-DO Support for Coverage Differences, FID 8219.9
Support for Multiple 1xEV-DO Carriers - Inter-frequency Handoff (IFHO), FID
8219.11
Six Sector Modular Cell 4.0B with Mixed 1x and 1xEV-DO, FID 8882.0
Chapter 5, Per Call Measurement Data (PCMD) for 1xEV-DO, describes the Per
Call Measurement Data (PCMD) for 1xEV-DO and Enhancements features:
CDMA2000 1xEV-DO Feature Provisioning GuidePCMD for 1xEV-DO, FID
12269.0
Enhancements to EVDO Per Call Service Measurements, FID 12269.2
EVDO Service Measurements Enhancement - Phase 2, FID 12370.1
Customer Critical Performance Measurements and Translations - Phase 3, FID
12766.2
Chapter 6, High Rate Packet Data Radio Network Controller (HRPD RNC)
Performance and Capacity Improvements, feature, FID 10607.3.
Chapter 7, 1xEV-DO Rev. A Basic Feature Bundle, describes the following basic
1xEV-DO Rev. A feature bundles and related features:
Basic Rev. A Feature Bundle:
Enhanced Reverse and Forward Links using Enhanced MAC Protocols with
Rev. A Subtype 2 Physical Layer, FID 12078.2
Generic Attribute Update Protocol (GAUP) for Dynamic Parameters Update,
FID 12078.3

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
xxv
Issue 5, May 2008
See notice on first page
,

About this information product

HRPD Rev. A Support on Modular Cell 1-3 BTS Platforms using SB-EVMm,
FID 12078.4

HRPD Rev. A Support on Modular Cell 4.0 BTS Platforms using SB-EVM,
FID 12078.5
Inter and Intra-RNC Handoff Enhancement, D 12078.7
Chapter 8, 1xEV-DO Enhanced Rev. A Feature Bundle, describes the following
enhanced 1xEV-DO Rev. A feature bundle and related features using the 1xEV-DO
Enhanced Rev. A (DOrA) application license:
Application Based Quality of Service (QoS) Support for HRPD Rev. A, FID
12078.9
RAN Quality of Service Enhancements for HRPD Rev. A, FID 12078.10
More Quality of Service (QoS) Enhancements for the High Rate Packet Data
(HRPD) Revision A (Rev. A) Network FID 12078.11
Data Over Signaling Protocol, FID 12078.12
Enhanced Idle State Protocol, FID 12078.13
1xEV-DO Revision A (Rev. A): Data Over Signaling Protocol - FL FID
12078.36
Basic PTT on HRPD-A, FID 12184.1.
HRPD PTT Paging Enhancements, FID 12184.5
Push-to-Talk (PTT) Enhancements FID 12184.7
Reference to Backhaul Enhancement in Support of Small Packets on the
Reverse and Forward Links in 1xEV-DO. Detailed feature description of FID
12102.5 can be found in Chapter 17 of this document..
Chapter 9, CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Backhaul with
Multi Link Point-to-Point Protocol (MLPPP) at Layer 2 Over T1/E1, describes
FID 12304.11.
Chapter 10, CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Only Revision
A (Rev. A) Voice Over Internet Protocol (VoIP) and Application Pricing, describes
the following features:
1xEV-DO Only Rev. A Voice Over Internet Protocol (VoIP) and Application
Pricing, FID 12905.0
1xEV-DO Rev. A Application Pricing Enhancements FID 12905.1
Chapter 11, Radio Network Controller (RNC) Grouping to Improve Idle Hand-off
Performance, describes FID 12456.1.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
,

xxvi

About this information product

Chapter 12, EVolution Data Optimized (1xEV-DO) Performance Monitoring Tools


Enhancements, describes the following features:

1xEV-DO Performance Monitoring Tools Enhancements, FID 9253.1


1xEV-DO Tool Interface between Operations and Maintenance Platform for
Flexent (OMP-FX) and 1xEV-DO Radio Network Controller (RNC), FID
9253.2
Access Terminal (AT) Trace Enhancement for Customer Use, FID 9253.3
Updates for post R28.0 General Availability (GA) and later. Added this new FID
9253.1 per customer concerns that a portion of a 1xEV-DO R27 feature was
missed. Issue was resolved in (AR1-1652484).
Chapter 13, Intra-Radio Network Controller (RNC) Session Resource Balancing in
1xEV-DO, describes FID 12458.0.
Chapter 14, Inter-User Priority for Best Effort Data Applications (IUPBEDA),
describes FID 12171.4.
Chapter 15, Jurisdictional Priority for Public Safety Users of Best Effort Data
Applications (JPPSUBEDA), describes FID 12171.5.
Chapter 16, Universal Traffic Processor (UTP) Protocol Acceleration in
Hardware, describes FID 12780.3.
Chapter 17, Backhaul Enhancement in Support of Small Packets on the Reverse
and Forward Links in 1xEV-DO, describes the following features:
Backhaul Enhancement in Support of Small Packets on the Reverse Link in
1xEV-DO (Phase 1a) FID 12102.5
Backhaul Enhancement in Support of Small Packets on the Forward Link in
1xEV-DO (Phase 1b) FID 12102.14
The Glossary defines technical terms and abbreviations that are used in this
document.

Operations and Maintenance Center - Radio Access Network (OMC-RAN) equivalents to


common Element Management System (EMS) screens

All the information that was available about EV-DO network elements on EMS is
available on the OMC-RAN Graphical User Interface (GUI). However, there is not a
one-to-one correspondence between equivalent views in EMS and on the OMC-RAN.
Listed here are the most commonly-used ways to find certain information on EMS and
where to find the equivalent information on the OMC-RAN. Remember that as a
powerful Windows-based application, the OMC-RAN often has several different ways
to access the same data. This Operations and Maintenance Center - Radio Access
Network (OMC-RAN) equivalents to common Element Management System (EMS)
screens (p. xxviii) shows one way to access the most commonly used information.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
xxvii
Issue 5, May 2008
See notice on first page
,

About this information product

For a detailed reference table mapping individual EMS parameters to individual


OMC-RAN parameters, see the CDMA2000 1xEV-DO Configurations Parameters
Guide, 401-614-324.
For this function

in EMS you go to...

on the OMC-RAN you go to...

Starting out

OMP Web screen

Desktop

Monitoring all BTSs


in a Service Node

Base Transceiver
Systems (BTSs) screen

The following places

CellSiteTable under the DO


Object (lists all DO cells).
Look at the CsCabTable and
SectorTable and other tables
for more information

For CDMA BTSs that are


DO-capable, the BTS Overview

BTS group in the Network


Manager tree under the ORCA

Group Note that DO-capable


BTSs have a blue icon besides
them that says DO.
Finding alarms on a
BTS

Base Transceiver
Systems (BTSs) screen

The following places

Alarm Manager

CellSiteTable under the DO


Object (lists all DO cells)

For CDMA BTSs that are


DO-capable, the BTS Overview

Go to the Detail view screen


for an individual network
element

BTS group in the Network


Manager tree under the ORCA

Group. Note that DO-capable


BTSs have a blue icon besides
them that says DO.
Note that the Highest Severity
Alarm (HSA) for each network
element shows up as an icon in
the NM tree.
Monitoring an
individual

Drill down from the Base


Transceiver Systems
(BTSs) screen

Use the NE view Detail view


screen for the network element.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
,

xxviii

About this information product

For this function

in EMS you go to...

on the OMC-RAN you go to...

Starting out

OMP Web screen

Desktop

Monitoring all
EV-DO RNCs in a
Service Node

Start with the CDMA2000

The following places:

EV-DO Radio Network


Controllers (EV-DO RNCs)

Look at the Rackview (Note


that in OMC-RAN Release
28.0, SU 2, both TPs in each
drawer will show up on the
Rackview). Right-click or run
your cursor over a network
element to get maintenance
states. Right-click and select
Details from the drop down
menu to get detailed
information

On each EV-DO DO-RNC,


expand the HDRFrame Table in
the NE view

On each EV-DO DO-RNC


HDRFrame Table, right click
and select AP Table from the
drop-down menu.

screen and drill down to


the AP Summary

Monitoring an
individual EV-DO
RNC

Drill down from the AP


Summary View

Find the DO Object, the name


with a lowercase do in the
middle:

Working with
configuration data for
a BTS

Configuration Data tables

Drill down to the network


element view by clicking on
the right arrow on the HM
tree, expand the DO Object in
the network element view, then
double click on the AP Table
and TP Table.

Go to the following places:

Go to the CellSiteTable under


the DO Object, then right-click
to do Expand ALL from the
CellSiteTable, then double
click on any network element
or table to get a Detail view
screen

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
xxix
Issue 5, May 2008
See notice on first page
,

About this information product

For this function

in EMS you go to...

on the OMC-RAN you go to...

Starting out

OMP Web screen

Desktop

Working with
configuration data for
a Service Node

Configuration Data tables

Go to the following places:

Working with
configuration data
single frame

In R29 and earlier, FxApx


VNE (the FxApx listed at the
bottom of the ORCA Group)
gives a global SN general view
for all EV-DO RNCs on one
FxApx. On FxApx VNE,
proceed to the network
element view, highlight the
network element, right click on
Details.

In R30 and later, x:R30 Global


Config DO where x is the
FxApx for the ORCA Group)
gives a global SN general view
for all EV-DO RNCs on one
FxApx. Use R30 Global Config
DO, proceed to the network
element view, highlight the
network element, right click on
Details.

Use System CLI to enter


configuration commands.

Drill down from the

Go to the following places:

Configuration Data

Go to the HDR frame Detail


view screen

Use System CLI to enter


configuration commands.

tables

See Appendix 7 of Alcatel-Lucent 9271 EV-DO Radio Network Controller,


401-614-102 for basic information in order to:

understand the OMC-RAN,


understand the layout of EV-DO information on the OMC-RAN, and
provisioning activities on EV-DO network and elements from the OMC-RAN.

For more information about the different 1xEV-DO OA&M interfaces that are used in
performing OA&M tasks on the EV-DO controller and its managed resources,
including the purpose of each interface and how to access it, see Alcatel-Lucent 9271
EV-DO Radio Network Controller, 401-614-102, Chapter 3, User Interfaces.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
,

xxx

About this information product

Conventions used

The following conventions are used throughout this document:


Typographic conventions

This document presents different types of information in different typefaces to


emphasize the nature of the information:

Literal user input. Keystrokes that you are to enter character by character exactly
as shown in the text appear in monospace bold type. For example:
Enter the following command:
apappsconfig

Variable user input. Input values that vary from one execution or instance to
another appear in monospace bold italic type. For example:
cd directory
Where:
directory = the

directory to which to change.


Literal system output. The names of files, directories, forms, messages, and other
information that a system outputs exactly as shown in the text appear in
monospace regular type. For example:
RST SPA=cnam REQUEST ACKNOWLEDGED

Variable system output. Values that vary from one instance to another in system
output appear in monospace italic type. For example:
RST SPA=SPA_NAME REQUEST COMPLETED
Where:
SPA_NAME = the name of the Service Package

Application (SPA) that is successfully

restored.
The names of keys on a terminal keyboard are indicated by bold letters. For
example:
Press the F4 (Enter Query) function key.
The Ctrl (Control) key is signified by the carat ( ^ ) symbol. When the ^ symbol
precedes the name of another key (as in ^e), press the Crtl key and the other key
simultaneously.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
xxxi
Issue 5, May 2008
See notice on first page
,

About this information product

Actions for user input

In this document, the following words specify what action you should perform to input
data or execute commands:

The word enter means to key in the specified keystrokes (such as a command) and
then press the Enter or Return key. For example:
Enter the following command:
apappconfig

The word press means to push down the specified key or keys on the keyboard.
For example:
Press the F4 (Enter Query) function key.
The word type means to key in the specified keystrokes (such as a value in the
field of a form) without pressing the Enter or Return key. For example:
In the IP address field, type the IP address of the host server.

Related information

The following documents are either referenced in this document or provide additional
information that relates 1xEV-DO:

System Capacity Monitoring & Engineering Guidelines (SCME), 401-610-009


Wireless Networks Input Messages, 401-610-055
Wireless Networks Output Messages, 401-610-057
Automatic Message Accounting (AMA) Format Descriptions, 401-610-133
Wireless Networks Service Measurements., 401-610-135,
Inter-MSC Cell Swing, 401-612-150
CDMA2000 1xEV-DO RAS Planning and Implementation Guide, 401-614-101
Alcatel-Lucent 9271 EV-DO Radio Network Controller Operations, Administration,
and Maintenance (OA&M), 401-614-102
CDMA2000 1xEV-DO Configurations Parameters Guide, 401-614-324
CDMA 2000 1xEV-DO EMS Configuration Management Bulk Provisioning,
401-614-325
CDMA2000 1xEV-DO Service Measurements, 401-614-326
5ESS Digital Cellular Switch (DCS) documents
Hardware Change Procedures: Growth, 235-105-231
Hardware Change Procedures: Degrowth, 235-105-331
Packet Switch Wireless Applications Operations, Administration, and
Maintenance (OA&M), 235-200-100,
Wireless Networks Element Management System (EMS) Users Guide, 401-710-110
Mobility Manager Compact System Capacity Monitoring and Engineering
Guidelines, 401-710-729

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
,

xxxii

About this information product

History of revisions

This is a history of the reissues for this document.


Issue 4.1

The following list summarizes the major changes or additions in this document for
1xEV-DO Release 29.1:

Introduced FID 12171.4 in new chapter 14.


Introduced FID 12171.5 in new chapter 15.
Introduced FID 12458.0 in new Chapter 13.

Issue 4

The following list summarizes the major changes or additions in this document for
1xEV-DO Release 29.0:

Introduced FIDs 12102.5, 12078.11, 12078.36, and 12184.11 in existing Chapter 8.


Introduced FID 12905.1 in existing Chapter 10.
Introduced FID 12458.01 in new Chapter 13.
Full feature description of FID 12102.5 was introduced in new document, Backhaul
Enhancement in Support of Small Packets on the Reverse and Forward Links in
1xEV-DO, 401-614-416.
Moved FID 9253.2 from existing Chapter 4 to existing Chapter 12.

Issue 3

The following list summarizes the major changes or additions in this document for
1xEV-DO Release 28.1:

Introduced FID 8219.7 in existing Chapter 4.

Issue 2.2

The following list summarizes the major changes or additions in this document for
1xEV-DO Release 28.0:

Introduced FID 9253.1 in new Chapter 12.

Issue 2.1

The following list summarizes the major changes or additions in this document for
1xEV-DO Release 28.0:

Updates for post R28.0 General Availability (GA) and later to existing Chapter 5,
PCDM table updates.
Updates for post R28.0 General Availability (GA) and later to existing Chapter 8,
FID 12078.13 update (T_page1 parameter) value is off.
Updates for post R28.0 General Availability (GA) and later to existing Chapter 11
per updates to FID 12456.1.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
xxxiii
Issue 5, May 2008
See notice on first page
,

About this information product

Issue 2

The following list summarizes the major changes or additions in this document for
1xEV-DO Release 28.0:

Introduced
Introduced
Introduced
Introduced
Introduced
Introduced

FID 9253.2 in existing Chapter 4.


FIDs 12078.9, 12078.10, 12078.12, and 12078.13 in new Chapter 8.
FIDs 12184.1 and 12184.5 in new Chapter 8.
FID 12304.11 in new Chapter 9.
FID 12905.0 in new Chapter 10.
FID 12456.1 in new Chapter 11.

Issue 1

The following list summarizes the major changes or additions in this document for
1xEV-DO Release 27.0:

Moved document 401-614-400, into 401-614-413 as new Chapter 1 (FID 8948.0).


Moved document 401-614-402, into 401-614-413 as new Chapter 2 (FID 8103.0).
Moved document 401-614-407, into 401-614-413 as new Chapter 3 (FIDs 12188.0
and 12188.1).
Moved document 401-614-409, into 401-614-413 as new Chapter 4 (FIDs 12146.0,
8219.11, and 8882.0).
Moved document 401-614-410, into 401-614-413 as new Chapter 5 (FIDs 12269.0
and 12269.2).
Moved document 401-614-412, into 401-614-413 as new Chapter 6 (FID 10607.3).
Introduced FIDs 12078.2, 12078.3, 12078.4, 12078.5, and 12078.7 in new Chapter
7.

How to comment

To comment on this information product, go to the Online Comment Form


(http://www.lucent-info.com/comments/enus/) or e-mail your comments to the
Comments Hotline (comments@alcatel-lucent.com).

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
,

xxxiv

1 DMA 3G-1x EVolution Data


C
Optimized (1xEV-DO) Flexible
Scheduler

Overview
...................................................................................................................................................................................................................................
Purpose

This optional feature description describes the CDMA 3G-1x EVolution Data
Optimized (1xEV-DO) Flexible Scheduler optional feature in wireless networks.
Feature summary

The Flexible Scheduler feature allows the selection of a scheduling algorithm to be


used for forward link data.
Feature Identifier (FID)

The Feature Identifier (FID) of the of the Flexible Scheduler feature is FID 8948.0.
Impacts on user interfaces

The Flexible Scheduler affects the user interfaces that are listed in the following table.
User interface

Feature impact

Element Management System


(EMS)

See Impacts on the Element Management System


(EMS) (p. 1-8).

Operations and Maintenance


Center - Radio Access Network
(OMC-RAN)

See Impacts on the Operations and Maintenance


Center - Radio Access Network (OMC-RAN)
(p. 1-16).

Service measurements

See Impacts on service measurements (p. 1-23).

Automatic Message Accounting


(AMA) subsystem

None

Technician Interface (TI)


(input/output messages)

None

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
1-1
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Flexible Scheduler

Overview

To obtain technical support, documentation, and training or submit feedback

The Online Customer Support (OLCS) web site (http://support.lucent.com/) provides


access to technical support, related documentation, related training, and feedback tools.
The site also provides account registration for new users.
Contents
Availability

1-3

Prerequisites

1-4

Feature description

1-5

Feature interactions

1-7

Impacts on the Element Management System (EMS)

1-8

Impacts on the Operations and Maintenance Center - Radio Access


Network (OMC-RAN)

1-16

Impacts on service measurements

1-23

Implementing the feature

1-24

Activating the feature

1-25

Configuring the Flexible Scheduler feature for Service Nodes

1-26

Configuring the Flexible Scheduler feature for base stations

1-28

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

1-2

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Flexible Scheduler

Availability
...................................................................................................................................................................................................................................
Release availability

The Flexible Scheduler feature is available in Release 22.0 and later.


Market availability

The Flexible Scheduler feature is available in all regions.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
1-3
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Flexible Scheduler

Prerequisites
...................................................................................................................................................................................................................................
Introduction

The Flexible Scheduler feature has the following prerequisites.


Supported technologies

The Flexible Scheduler feature is supported in the following air-interface technologies:

CDMA cellular
CDMA PCS

Software requirements

The Flexible Scheduler feature requires 1xEV-DO Release 22.0 or later.


Hardware requirements

The Flexible Scheduler feature requires no hardware beyond the standard hardware in a
CDMA2000 1xEV-DO network.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

1-4

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Flexible Scheduler

Feature
description
...................................................................................................................................................................................................................................
Introduction

The following information describes the functionality, benefits, and operation of the
Flexible Scheduler feature.
Functionality

The Flexible Scheduler feature allows the provider to select from four different forward
link scheduler algorithms:

Proportional Fair (PF)

The default choice and the algorithm in use before this feature was available.

Min/Max Rate Control

This algorithm allows the provider to control the minimum and maximum average
throughput rate for the user.

G-Fair

This algorithm allows control of one users thoughput in relation to other users
throughput.

Random Activity Factor

This algorithm is used with the Test Application feature for supporting Minimum
Performance Standard testing.
Benefits

The Flexible Scheduler feature allows providers to match the forward link scheduler
algorithm to market needs. This feature gives providers more control over users
throughput based on different service classes.

User throughput control

The 1x-EV-DO system can guarantee a users minimum throughput. It can also
restrict a users maximum throughput so that the user can have a relatively steady
data throughput experience.

Hooks for future Quality of Service needs

The Flexible Scheduler Feature provides hooks to support Quality of Service (QoS)
needs in the future.
How the feature operates

The forward link consists of a single data channel only. At any one time, only one
users data is being transmitted. The Access Terminal (AT) requests the best serving
sector and the data rate through the Data Rate Control (DRC) channel. (The DRC is
the data rate that the AT requests for service. The better the RF conditions, the better

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
1-5
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Flexible Scheduler

Feature description

the DRC. The DRC rates that are supported on the forward link are 2457.5 kbps,
1843.2 kbps, 1228.8 kbps, 921.6 kbps, 614.4 kbps, 307.2 kbps, 153.6 kbps, 76.8 kbps,
and 38.4 kbps.)
The Radio Access Network (RAN) transmits packet data at the rate requested by the
AT. When multiple users are requesting data, a scheduler uses the DRCs received to
determine the order and the data rate at which to transmit to users on the forward link.
The Flexible Scheduler attempts to take advantage of the temporal variations in the
channel by scheduling transmissions to ATs during the time periods where the AT sees
strong signal levels. The scheduler sends data to the mobile that has the highest
DRC/R, where DRC is the rate requested by the mobile in a given slot, and R is the
average rate transmitted to the mobile over a window of time. This way each user is
served in slots in which its requested rate is closer to the peak, as compared with
recent requests.
The four Flexible Scheduler algorithms supported are

PF (default)
Min/Max Rate Control
G-Fair
Random Activity Factor

These algorithms and their associated parameters are set on the Service Nodes/Flexible
Scheduler instance page in the Element Management System (EMS) Configuration
Management set of pages. The Flexible Scheduler meets the throughput requirements
for the algorithm that has been chosen.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

1-6

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Flexible Scheduler

Feature
interactions
...................................................................................................................................................................................................................................
Introduction

The Flexible Scheduler feature does not interact with other features.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
1-7
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Flexible Scheduler

Impacts
on the Element Management System (EMS)
...................................................................................................................................................................................................................................
Configuration Management pages

The Flexible Scheduler feature affects these Configuration Management pages in the
Element Management System:

Service Nodes/Flexible Scheduler instance page (new page)


Base Transceiver Station (BTS) instance page (additional parameters)

The Flexible Schedule Feature can be configured at the service node level for all base
stations in that service node. If the Flexible Scheduler feature is configured at the base
station level using the BTS instance page, those settings take precedence over settings
at the service node level. (The settings at the service node level take precedence for
any Flexible Scheduler parameters which are blank, however.)
For detailed procedures, see CDMA2000 1xEV-DO Radio Access System Planning
and Implementation Guide, 401-614-101.
For detailed procedures regarding the impact of OMC-RAN becoming a mandatory
platform for EV-DO in R29.1 and later, see Appendix 7 of Alcatel-Lucent 9271 EV-DO
Radio Network Controller, 401-614-102.
Service Nodes/Flexible Scheduler instance page

The Flexible Scheduler feature can be configured for all base stations in a service node
through the Service Nodes/Flexible Scheduler instance page.
Important! If the Flexible Scheduler feature for a base station is configured at the
base station level using the BTS instance page, those settings take precedence over
the settings at the service node level.
The Service Nodes/Flexible Scheduler instance page is shown in the following figure.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

1-8

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Flexible Scheduler

Impacts on the Element Management System (EMS)

Figure 1-1 Service Nodes/Flexible Scheduler instance page

An asterisk (*) by a parameter indicates that parameter is required. A green


exclamation point (!) by a parameter indicates that parameter is dynamically
updateable. If you change the value of the dynamically parameter, you do not have to
reboot the application for the new value to take effect.
Important! All Flexible Scheduler parameters except for Flexible Scheduler Choice
(FSC) are dynamically updateable. If you change the FSC parameter, you have to
reset the modem for the new FSC to take effect.
The configuration parameters on the Service Node/Flexible Scheduler instance page are
described in Table 1-1, Flexible Scheduler parameters (p. 1-9).
Table 1-1

Flexible Scheduler parameters

Parameter name
Flexible Scheduler
Choice

Description

Allowed values

The FSC specifies the scheduler


algorithm to be used on forward
link transmission.

PF (default)

This parameter is not


dynamically updateable. If you
change the FSC parameter, you
have to reset the modem for the
new FSC to take effect.

Random Activity Factor

Min/Max Rate Control


G-Fair

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
1-9
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Flexible Scheduler

Table 1-1

Impacts on the Element Management System (EMS)

Flexible Scheduler parameters

Parameter name
Minimum Throughput
Target (Rmin)

Restrict Throughput
After Reaching Rmax

(continued)

Description

Allowed values

When the FSC is Min/Max Rate


Control, this parameter indicates
the minimum user throughput the
scheduler should try to achieve
for any individual user.

0 to 64 kbps in steps of
4k

When the FSC is Min/Max Rate


Control, this parameter indicates
if the scheduler should strictly
enforce the maximum throughput
bound Rmax.

Unspecified

Default = 0

Non-strict (default)
Strict
Out-of-Range

Non-strict enforcement allows


some users throughputs to go
above Rmax, but only in cases
when all users throughputs are
already at or above Rmax.
Strict enforcement caps each
users throughput at Rmax at all
times, even if this requires that
timeslots would be underused.
G-Fair Control Function

If the FSC is set to G-Fair, this


parameter indicates the h()
function to be used by the
scheduler. Every h() function has
a different expected throughput.

Unspecified
h(x)=x(proportional_
fair)
(default)
h(x)=2*x
h(x)=4*x
Out-of-Range

Min/Max Rate Control


Direction

If the FSC is set to Min/Max


Rate Control, the direction
parameter indicates the scheduler
algorithm optimization direction
after the minimum threshold is
met for all users in the sector.

Unspecified
PFMR (default)
MTMR
Out-of-Range

PFMR = Proportional Fair after


meeting Minimum User Rate
Target
MTMR = Maximum Sector
Throughput after meeting
Minimum User Rate Target
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

1-10

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Flexible Scheduler

Table 1-1

Impacts on the Element Management System (EMS)

Flexible Scheduler parameters

Parameter name
Maximum Throughput
Threshold (Rmax)

(continued)

Description
When the FSC is set to Min/Max
Control, this parameter indicates
the desired bound on the
maximum user throughput. This
bound is enforced non-strictly or
strictly, depending on the entry
for the parameter Restrict
Throughput After Reaching
Rmax.

Allowed values
2457.6 (default)
9.6 to 2457.6 kbps in

steps of 4.8 kbps

The Rmax must be at least two


times larger than Rmin.
Rmin Hog Prevention
Factor

When the FSC is set to Min/Max


Control, this parameter indicates
the prevention factor used in the
algorithm to prevent a bad RF
user from hogging the system
resources when Rmin is being
enforced.

Off (default)
1.5 to 2.5 in steps of

0.1
Out-of-Range

BTS instance page

The Flexible Scheduler feature adds several configuration parameters to the BTS
instance page, shown in the following figure. If the Flexible Scheduler feature for a
base station is configured at the base station level using the BTS instance page, those
settings take precedence over the settings at the service node level.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
1-11
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Flexible Scheduler

Impacts on the Element Management System (EMS)

Figure 1-2 BTS instance page

An asterisk (*) by a parameter indicates that parameter is required. A green


exclamation point (!) by a parameter indicates that parameter is dynamically
updateable. If you change the value of the dynamically parameter, you do not have to
reboot the application for the new value to take effect.
Important! All Flexible Scheduler parameters except for FSC are dynamically
updateable. If you change the FSC parameter, you have to reset the modem for the
new FSC to take effect.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

1-12

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Flexible Scheduler

Impacts on the Element Management System (EMS)

The Flexible Scheduler parameters on the BTS instance page are shown in Table 1-2,
Flexible Scheduler parameters on the BTS instance page (p. 1-13).
Table 1-2

Flexible Scheduler parameters on the BTS instance page

Field name
Flexible Scheduler
Choice

Description
The FSC specifies the scheduler
algorithm to be used on forward
link transmission.
This parameter is not
dynamically updateable. If you
change the FSC parameter, you
have to reset the modem for the
new FSC to take effect.

Min/Max Rate Control


Direction

If the FSC is set to Min/Max


Rate Control, the direction
parameter indicates the scheduler
algorithm optimization direction
after the minimum threshold is
met for all users in the sector.

Allowed values
Unspecified (default)
Proportional Fair
Min/Max Rate Control
G-Fair
Random Activity Factor

Unspecified (default)
PFMR
MTMR
Out-of-Range

PFMR = Proportional Fair after


meeting Minimum User Rate
Target
MTMR = Maximum Sector
Throughput after meeting
Minimum User Rate Target
Maximum Throughput
Threshold (Rmax)

When the FSC is set to Min/Max


Control, this parameter indicates
the desired bound on the
maximum user throughput. This
bound is enforced non-strictly or
strictly, depending on the entry
for the parameter Restrict
Throughput After Reaching
Rmax.

9.6 to 2457.6 kbps in

steps of 4.8 kbps


default = blank

The Rmax must be at least two


times larger than Rmin.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
1-13
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Flexible Scheduler

Table 1-2

Impacts on the Element Management System (EMS)

Flexible Scheduler parameters on the BTS instance page


(continued)

Field name
Rmin Hog Prevention
Factor

Minimum Throughput
Target (Rmin)

Restrict Throughput
After Reaching Rmax

Description
When the FSC is set to Min/Max
Control, this parameter indicates
the prevention factor used in the
algorithm to prevent a bad RF
user from hogging the system
resources when Rmin is being
enforced.
When the FSC is Min/Max Rate
Control, this parameter indicates
the minimum user throughput the
scheduler should try to achieve
for any individual user.
When the FSC is Min/Max Rate
Control, this parameter indicates
if the scheduler should strictly
enforce the maximum throughput
bound Rmax.

Allowed values
Unspecified (default)
1.5 to 2.5 in steps of

0.1
Out-of-Range

0 to 64 kbps in steps of

4k
default = blank

Unspecified (default)
Non-strict
Strict
Out-of-Range

Non-strict enforcement allows


some users throughputs to go
above Rmax, but only in cases
when all users throughputs are
already at or above Rmax.
Strict enforcement caps each
users throughput at Rmax at all
times, even if this requires that
timeslots would be underused.
G-Fair Control Function

If the FSC is set to G-Fair, this


parameter indicates the h()
function to be used by the
scheduler. Every h() function has
a different expected throughput.

Unspecified (default)
h(x)=x(proportional_
fair)
h(x)=2*x
h(x)=4*x
Out-of-Range

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

1-14

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Flexible Scheduler

Impacts on the Element Management System (EMS)

References

For information on how to configure the parameters for this feature, see Configuring
the Flexible Scheduler feature for Service Nodes (p. 1-26) in this chapter. For more
information about configuration parameters, see the following document:

1xEV-DO Configuration Parameters Guide, 401-614-324

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
1-15
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Flexible Scheduler

Impacts on the Operations and Maintenance Center - Radio


Access
Network (OMC-RAN)
...................................................................................................................................................................................................................................
Configuration Management pages

The Flexible Scheduler feature affects this OMC-RAN Screen:

FxApx

For detailed procedures regarding the impact of OMC-RAN becoming a mandatory


platform for EV-DO in R29.1 and later, see Appendix 7 of Alcatel-Lucent 9271 EV-DO
Radio Network Controller OA&M, 401-614-102.
FxApx OMC-RAN Screen

The Flexible Scheduler feature can be configured for all base stations in a service node
through the Service Nodes/Flexible Scheduler instance page.
Important! If the Flexible Scheduler feature for a base station is configured at the
base station level using the BTS instance page, those settings take precedence over
the settings at the service node level.
The Service Nodes/Flexible Scheduler instance page is shown in the following figure.
Figure 1-3 Service Nodes/Flexible Scheduler instance page

An asterisk (*) by a parameter indicates that parameter is required. A green


exclamation point (!) by a parameter indicates that parameter is dynamically
updateable. If you change the value of the dynamically parameter, you do not have to
reboot the application for the new value to take effect.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

1-16

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Flexible Scheduler

Impacts on the Operations and Maintenance Center Radio Access Network (OMC-RAN)

Important! All Flexible Scheduler parameters except for Flexible Scheduler Choice
(FSC) are dynamically updateable. If you change the FSC parameter, you have to
reset the modem for the new FSC to take effect.
The configuration parameters on the Service Node/Flexible Scheduler instance page are
described in Table 1-3, Flexible Scheduler parameters (p. 1-17).
Table 1-3

Flexible Scheduler parameters

Parameter name
Flexible Scheduler
Choice

Minimum Throughput
Target (Rmin)

Restrict Throughput
After Reaching Rmax

Description

Allowed values

The FSC specifies the scheduler


algorithm to be used on forward
link transmission.

PF (default)

This parameter is not


dynamically updateable. If you
change the FSC parameter, you
have to reset the modem for the
new FSC to take effect.

Random Activity Factor

When the FSC is Min/Max Rate


Control, this parameter indicates
the minimum user throughput the
scheduler should try to achieve
for any individual user.

0 to 64 kbps in steps of
4k

When the FSC is Min/Max Rate


Control, this parameter indicates
if the scheduler should strictly
enforce the maximum throughput
bound Rmax.

Unspecified

Min/Max Rate Control


G-Fair

Default = 0

Non-strict (default)
Strict
Out-of-Range

Non-strict enforcement allows


some users throughputs to go
above Rmax, but only in cases
when all users throughputs are
already at or above Rmax.
Strict enforcement caps each
users throughput at Rmax at all
times, even if this requires that
timeslots would be underused.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
1-17
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Flexible Scheduler

Table 1-3

Impacts on the Operations and Maintenance Center Radio Access Network (OMC-RAN)

Flexible Scheduler parameters

(continued)

Parameter name

Description

G-Fair Control Function

If the FSC is set to G-Fair, this


parameter indicates the h()
function to be used by the
scheduler. Every h() function has
a different expected throughput.

Allowed values
Unspecified
h(x)=x(proportional_
fair)
(default)
h(x)=2*x
h(x)=4*x
Out-of-Range

Min/Max Rate Control


Direction

If the FSC is set to Min/Max


Rate Control, the direction
parameter indicates the scheduler
algorithm optimization direction
after the minimum threshold is
met for all users in the sector.

Unspecified
PFMR (default)
MTMR
Out-of-Range

PFMR = Proportional Fair after


meeting Minimum User Rate
Target
MTMR = Maximum Sector
Throughput after meeting
Minimum User Rate Target
Maximum Throughput
Threshold (Rmax)

When the FSC is set to Min/Max


Control, this parameter indicates
the desired bound on the
maximum user throughput. This
bound is enforced non-strictly or
strictly, depending on the entry
for the parameter Restrict
Throughput After Reaching
Rmax.

2457.6 (default)
9.6 to 2457.6 kbps in

steps of 4.8 kbps

The Rmax must be at least two


times larger than Rmin.
Rmin Hog Prevention
Factor

When the FSC is set to Min/Max


Control, this parameter indicates
the prevention factor used in the
algorithm to prevent a bad RF
user from hogging the system
resources when Rmin is being
enforced.

Off (default)
1.5 to 2.5 in steps of

0.1
Out-of-Range

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

1-18

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Flexible Scheduler

Impacts on the Operations and Maintenance Center Radio Access Network (OMC-RAN)

BTS instance page

The Flexible Scheduler feature adds several configuration parameters to the BTS
instance page, shown in the following figure. If the Flexible Scheduler feature for a
base station is configured at the base station level using the BTS instance page, those
settings take precedence over the settings at the service node level.
Figure 1-4 BTS instance page

An asterisk (*) by a parameter indicates that parameter is required. A green


exclamation point (!) by a parameter indicates that parameter is dynamically
updateable. If you change the value of the dynamically parameter, you do not have to
reboot the application for the new value to take effect.
Important! All Flexible Scheduler parameters except for FSC are dynamically
updateable. If you change the FSC parameter, you have to reset the modem for the
new FSC to take effect.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
1-19
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Flexible Scheduler

Impacts on the Operations and Maintenance Center Radio Access Network (OMC-RAN)

The Flexible Scheduler parameters on the BTS instance page are shown in Table 1-4,
Flexible Scheduler parameters on the BTS instance page (p. 1-20).
Table 1-4

Flexible Scheduler parameters on the BTS instance page

Field name
Flexible Scheduler
Choice

Description
The FSC specifies the scheduler
algorithm to be used on forward
link transmission.
This parameter is not
dynamically updateable. If you
change the FSC parameter, you
have to reset the modem for the
new FSC to take effect.

Min/Max Rate Control


Direction

If the FSC is set to Min/Max


Rate Control, the direction
parameter indicates the scheduler
algorithm optimization direction
after the minimum threshold is
met for all users in the sector.

Allowed values
Unspecified (default)
Proportional Fair
Min/Max Rate Control
G-Fair
Random Activity Factor

Unspecified (default)
PFMR
MTMR
Out-of-Range

PFMR = Proportional Fair after


meeting Minimum User Rate
Target
MTMR = Maximum Sector
Throughput after meeting
Minimum User Rate Target
Maximum Throughput
Threshold (Rmax)

When the FSC is set to Min/Max


Control, this parameter indicates
the desired bound on the
maximum user throughput. This
bound is enforced non-strictly or
strictly, depending on the entry
for the parameter Restrict
Throughput After Reaching
Rmax.

9.6 to 2457.6 kbps in

steps of 4.8 kbps


default = blank

The Rmax must be at least two


times larger than Rmin.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

1-20

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Flexible Scheduler

Table 1-4

Impacts on the Operations and Maintenance Center Radio Access Network (OMC-RAN)

Flexible Scheduler parameters on the BTS instance page


(continued)

Field name
Rmin Hog Prevention
Factor

Minimum Throughput
Target (Rmin)

Restrict Throughput
After Reaching Rmax

Description
When the FSC is set to Min/Max
Control, this parameter indicates
the prevention factor used in the
algorithm to prevent a bad RF
user from hogging the system
resources when Rmin is being
enforced.
When the FSC is Min/Max Rate
Control, this parameter indicates
the minimum user throughput the
scheduler should try to achieve
for any individual user.
When the FSC is Min/Max Rate
Control, this parameter indicates
if the scheduler should strictly
enforce the maximum throughput
bound Rmax.

Allowed values
Unspecified (default)
1.5 to 2.5 in steps of

0.1
Out-of-Range

0 to 64 kbps in steps of

4k
default = blank

Unspecified (default)
Non-strict
Strict
Out-of-Range

Non-strict enforcement allows


some users throughputs to go
above Rmax, but only in cases
when all users throughputs are
already at or above Rmax.
Strict enforcement caps each
users throughput at Rmax at all
times, even if this requires that
timeslots would be underused.
G-Fair Control Function

If the FSC is set to G-Fair, this


parameter indicates the h()
function to be used by the
scheduler. Every h() function has
a different expected throughput.

Unspecified (default)
h(x)=x(proportional_
fair)
h(x)=2*x
h(x)=4*x
Out-of-Range

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
1-21
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Flexible Scheduler

Impacts on the Operations and Maintenance Center Radio Access Network (OMC-RAN)

References

For information on how to configure the parameters for this feature, see Configuring
the Flexible Scheduler feature for Service Nodes (p. 1-26) in this chapter. For more
information about configuration parameters, see the following document:

1xEV-DO Configuration Parameters Guide, 401-614-324

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

1-22

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Flexible Scheduler

Impacts
on service measurements
...................................................................................................................................................................................................................................
Introduction

The Flexible Scheduler feature affects the following categories of services


measurements:

1xEV-DO service measurements

1xEV-DO service measurements

The Flexible Scheduler feature adds the 1xEV-DO service measurements that are
identified in Table 1-5, 1xEV-DO service measurements (p. 1-23).
Table 1-5

1xEV-DO service measurements

Count abbreviation

Brief description

EVM_AVG_PCNT_SLOTS_BELOW_RMIN

Average percentage of time slots


when any users average
throughput is below Rmin
threshold for the selector/carrier
by 10%

EVM_AVG_PCNT_SLOTS_ABOVE_RMAX

Average percentage of time slots


when any users average
throughput is above the
translation parameter Rmax
setting by 10%

EVM_AVG_ELIG_USER

Average number of active users


eligible to be selected by the
scheduler for the sector/carrier

EVM_TOTAL_BUSY_PCNT_SLOT

Total number of busy slots


percentage used for user traffic
data transmission

EVM_TOTAL_PCNT_SLOTS_RMIN_HOGGING_
EFFECTIVE

Total percentage of slots when


the Rmin Hogging Prevention
algorithm takes effect

References

For detailed information about 1xEV-DO service measurements, see ,


CDMA2000 1xEV-DO Service Measurements,, 401-614-326.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
1-23
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Flexible Scheduler

Implementing
the feature
...................................................................................................................................................................................................................................
Overview

To implement the Flexible Scheduler feature, perform the following procedures in


sequence:
Activating the feature (p. 1-25)
Configuring the Flexible Scheduler feature for Service Nodes (p. 1-26)
Configuring the Flexible Scheduler feature for base stations (p. 1-28)

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

1-24

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Flexible Scheduler

Activating
the feature
...................................................................................................................................................................................................................................
Purpose

This procedure activates the Flexible Scheduler feature in a CDMA2000 1xEV-DO


wireless network.
For detailed procedures, see CDMA2000 1xEV-DO Radio Access System Planning
and Implementation Guide, 401-614-101.
For detailed procedures regarding the impact of OMC-RAN becoming a mandatory
platform for EV-DO in R29.1 and later, see Appendix 7 of Alcatel-Lucent 9271 EV-DO
Radio Network Controller, 401-614-102.
Procedure

Perform the following steps:


...................................................................................................................................................................................................

Ask your account executive to activate the following entry in your Feature Activation
File (FAF):
1xEV-DO Flexible Scheduler Capacity
...................................................................................................................................................................................................

Proceed to Configuring the Flexible Scheduler feature for Service Nodes (p. 1-26).
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
1-25
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Flexible Scheduler

Configuring
the Flexible Scheduler feature for Service Nodes
...................................................................................................................................................................................................................................
Purpose

This procedure provisions the Flexible Scheduler feature for Service Nodes using the
EMS Service Nodes/Flexible Scheduler instance page.
Procedure

Perform the following steps:


...................................................................................................................................................................................................

Access the Operations and Maintenance Platform (OMP) Web page according to your
local practices.
...................................................................................................................................................................................................

Click on the Configuration Data icon.


Result: The Configuration Data page appears.
...................................................................................................................................................................................................

Click on the link to Service Nodes.


Result: The Service Node Summary page appears.
...................................................................................................................................................................................................

Click on the Service Node ID for the service node you want to provision for Flexible
Scheduler.
Result: The following page appears.

...................................................................................................................................................................................................

In the window, scroll down to Flexible Scheduler and click on that link.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

1-26

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Flexible Scheduler

Configuring the Flexible Scheduler feature for Service


Nodes

Result: The Flexible Scheduler instance page appears.

...................................................................................................................................................................................................

Configure the Flexible Scheduler Parameters for this Service Node. Refer to Table 1-1,
Flexible Scheduler parameters (p. 1-9) for the description and values for each
parameter.
...................................................................................................................................................................................................

Click the Submit button at the bottom of the page when you have finished configuring
the parameters. (Scroll down until you see the blue Submit button.)
...................................................................................................................................................................................................

If you wish to configure the Flexible Scheduler feature for base stations, continue with
the following procedure: Configuring the Flexible Scheduler feature for base stations
(p. 1-28).
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
1-27
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Flexible Scheduler

Configuring
the Flexible Scheduler feature for base stations
...................................................................................................................................................................................................................................
Purpose

This procedure provisions the Flexible Scheduler feature for base stations using the
EMS BTS instance page.
Procedure

Perform the following steps:


...................................................................................................................................................................................................

If you have not already accessed the EMS Configuration Data pages in the following
procedure, do so as follows:

Access the OMP Web page according to your local practices.


Click on the Configuration Data icon.

...................................................................................................................................................................................................

In the column of blue navigation buttons on the left side of this page, click on BTSs.
Result: The BTS container page appears.
...................................................................................................................................................................................................

Using filters if needed, access the BTS instance page for the BTSs you want to
configure.
Important! You can set up different schedulers for different base stations if you
wish. Keep in mind that any base station value takes precedence over the service
node value unless the base station value is blank. In that case, the service node
value is used.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

1-28

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Flexible Scheduler

Configuring the Flexible Scheduler feature for base


stations

Result: A BTS instance page appears.

...................................................................................................................................................................................................

Configure the Flexible Scheduler Parameters for this base station. Refer to Table 1-4,
Flexible Scheduler parameters on the BTS instance page (p. 1-20) for the description
and values for each parameter related to this feature.
...................................................................................................................................................................................................

Click the Submit button at the bottom of the page when you have finished configuring
the Flexible Scheduling parameters on this page.
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
1-29
Issue 5, May 2008
See notice on first page

2 DMA 3G-1x EVolution Data


C
Optimized (1xEV-DO) Radio
Access Network Authentication
(RAN)

Overview
...................................................................................................................................................................................................................................
Purpose

This chapter describes the CDMA 3G-1x Evolution Data Optimized (1xEV-DO) Radio
Access Network (RAN) Authentication feature in CDMA2000 1xEV-DO networks.
Feature summary

The 1xEV-DO RAN Authentication feature allows wireless service providers to verify
that an Access Terminal (AT) is a legitimate user of the service.
Feature Identifier (FID)

A unique FID is assigned to each feature. The FID of the 1xEV-DO RAN
Authentication feature is FID 8103.0.
Impacts on user interfaces

The 1xEV-DO RAN Authentication affects the user interfaces that are listed in the
following table.
User interface

Feature impact

Element Management
System (EMS)

See Implementing the feature (p. 2-9)

Operations and
Maintenance Center Radio Access Network
(OMC-RAN)

For information on configuring the OMC-RAN, see


Implementing the feature (p. 2-9)

Service measurements

See Impacts on service measurements (p. 2-8).

Automatic Message
Accounting (AMA)
subsystem

The RAN Authentication feature allows for retrieval of the


International Mobile Station Identity (IMSI) assigned to the
Access Terminal (AT). This enables IMSI-based billing.

....................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
2-1
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Radio


Access Network Authentication (RAN)

User interface

Feature impact

Technician Interface
(TI) (input/output
messages)

None

Overview

To obtain technical support, documentation, and training or submit feedback

The Online Customer Support (OLCS) web site (http://support.lucent.com/) provides


access to technical support, related documentation, related training, and feedback tools.
The site also provides account registration for new users.
Contents
Availability

2-3

Prerequisites

2-4

Feature description

2-5

Feature interactions

2-7

Impacts on service measurements

2-8

Implementing the feature

2-9

Activating the Feature

2-10

Configuring the feature using EMS

2-11

Provisioning the Access Terminal

2-16

Provisioning the RAN AAA server

2-17

Provisioning the route for RAN AAA on the TP

2-18

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

2-2

CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Radio


Access Network Authentication (RAN)

Availability
...................................................................................................................................................................................................................................
Release availability

The 1xEV-DO RAN Authentication feature is available in Release 22 and later.


Market availability

The 1xEV-DO RAN Authentication feature is available in all regions.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
2-3
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Radio


Access Network Authentication (RAN)

Prerequisites
...................................................................................................................................................................................................................................
Introduction

The 1xEV-DO RAN Authentication feature has the following prerequisites.


Supported technologies

The 1xEV-DO RAN Authentication feature is supported in the following air-interface


technologies:

CDMA2000 1xEV-DO

Software requirements

The 1xEV-DO RAN Authentication feature requires Release 22 or later. The 1xEV-DO
RAN Authentication feature is not dependent on other features.
Hardware requirements

The 1xEV-DO RAN Authentication feature requires the standard hardware in a


CDMA2000 1xEV-DO network including at least one RADIUS Accounting,
Authentication, and Authorization (AAA) server.
RAN AAA application can co-exist in the same platform with PDSN AAA. However,
having a separate platform for RAN AAA is recommended. Having the RAN AAA and
the PDSN AAA application on separate platforms has these benefits:

If the AAA server crashes or needs to be taken out of service and they are on the
same platform, both the PDSN AAA functions and the RAN AAA functions are
impacted. When the PDSN function is impacted, there is no way to make
1xEV-DO calls on the system. If the RAN AAA and the PDSN AAA applications
are kept separate, the service provider could still service 1xEV-DO calls by
disabling the RAN functionality from the EMS temporarily.
Internet Protocol (IP) network management and growth become more manageable.
Subscriber Provisioning can be done independently for RAN AAA and PDSN AAA
by different provisioning personnel. This keeps AT information more secure.

Interface requirements

This feature requires a 1xEV-DO A12 software interface on the AAA.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

2-4

CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Radio


Access Network Authentication (RAN)

Feature
description
...................................................................................................................................................................................................................................
Introduction

The following information describes the functionality, benefits, and operation of the
1xEV-DO RAN Authentication feature. This feature is implemented as defined in
TIA/EIA/IS-878 standards.
Functionality

The 1xEV-DO RAN Authentication feature allows authentication of AT devices. The


AT device authentication is separate from the user authentication performed at the
Packet Data Serving Node-Accounting, Authentication and Authorization server
(PDSN-AAA) after the Point-to-Point Protocol (PPP) link to the PDSN is established.
Benefits

The 1xEV-DO RAN Authentication feature provides the following benefits:

With this feature, the provider can verify that an AT is a legitimate user of the
service.
When a Wireless Service Provider (WSP) does not provide the Internet Service
Provider (ISP) function and does not own the PDSN-AAA, this feature provides a
way of provisioning and controlling access to the network via an additional AAA
owned by the WSP.
This feature provides a way to obtain the Mobile Node Identifier (MN-ID),
Equipment Serial Number (ESN), and Intelligent Network (IN) information. This
information can be used for billing customers.

How the feature operates

Figure 2-1, 1xEV-DO RAN Authentication architecture (p. 2-6) shows the A12-AAA
server as a logical entity without implying specific location or implementation. There is
one A12 connection to the A12-AAA on the 1xEV-DO RNC. It is the operators choice
to have a centralized A12-AAA serving the entire 1xEV-DO network with multiple
1xEV-DO RNCs or having a network of A12-AAA servers interconnected. It is also an
implementation choice to have the A12-AAA and the PDSN-AAA running as software
applications collocated on the same hardware platform. A maximum of two RAN AAA
servers can be connected to the 1xEV-DO network.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
2-5
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Radio


Access Network Authentication (RAN)

Feature description

Figure 2-1 1xEV-DO RAN Authentication architecture

The service provider has a more secure access network once the RAN Authentication
is implemented. Once the feature is implemented, there are two steps to gaining access
to the 1xEV-DO network. First, the RAN Authentication capability authenticates the
access device, then the PDSN AAA does a user level authentication.
RAN Authentication ensures that 1xEV-DO resources are better utilized, since all RNC
resources are released once RAN authentication is unsuccessful. Without this feature,
RNC resources could be held onto by an unauthorized subscriber trying gain access
using the user name/password authentication from the PDSN AAA.
This feature should be considered for deployment at the beginning of 1xEV-DO
deployment. Otherwise, the service provider must recall all 1xEV-DO ATs to program
the CHAP login and password. ATs without the CHAP login and password cannot
make 1xEV-DO calls once RAN Authentication is enabled.
Subscriber perspective

The subscriber does not have to do anything for RAN authentication. All RAN
parameters are provisioned by the service provider.
When the subscriber initiates a 1xEV-DO call, RAN authentication is attempted first. If
this is successful, PDSN Authentication is attempted. If RAN Authentication fails, the
subscriber receives an error on the 1xEV-DO dial-up screen.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

2-6

CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Radio


Access Network Authentication (RAN)

Feature
interactions
...................................................................................................................................................................................................................................
Introduction

There are no feature interactions for this feature.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
2-7
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Radio


Access Network Authentication (RAN)

Impacts
on service measurements
...................................................................................................................................................................................................................................
Introduction

The 1xEV-DO RAN Authentication feature affects the following categories of services
measurements:

1xEV-DO service measurements

1xEV-DO service measurements

The 1xEV-DO RAN Authentication feature introduces the RAN Authentication counts
identified in Table 2-1, 1xEV-DO service measurements (p. 2-8).
Table 2-1

1xEV-DO service measurements

Count abbreviation

Count name

RAN_AUTH_TOTAL_ATTMPT

Total RAN Authentication


Attempts

RAN_AUTH_SUCCESSFUL_ATTMPT

Successful RAN Authentication


Attempts

RAN_AUTH_FAILURE_AAA_REJECT_RSP

RAN Authentication Rejections

RAN_AUTH_FAILURES_STREAM_SELECTION_
FAILED

RAN Authentication Stream


Selection Failures

RAN_AUTH_FAILURES_LCP_RELATED_PPP_EST_RAN Authentication
FAILED
Configure-Ack Related PPP
Establishment Failures
RAN_AUTH_FAILURES_CONFIGURE_NAK_PPP_ RAN Authentication
EST_FAILED
Configure-NAK Related PPP
Establishment Failures
RAN_AUTH_INVALID_AT_CONFIGURE_REQ_
PPP_EST_FAILED

RAN Authentication Invalid AP


Configuration Request PPP
Establishment Failures

RAN_AUTH_FAILURES_NO_AT_CHALLENGE_
RSP

RAN Authentication Failures Due


to Missing AT Challenge
Response

AAA_SERVER_FAILURES

AAA Server Failures

References

For detailed information about service measurements, see

CDMA2000 1xEV-DO Network Service Measurements, 401-614-326

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

2-8

CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Radio


Access Network Authentication (RAN)

Implementing
the feature
...................................................................................................................................................................................................................................
Overview

The following interface must be available before RAN Authentication can be


implemented:

a 1xEV-DO A12 software interface on the AAA

To implement the 1xEV-DO RAN Authentication feature, perform the following EMS
procedures:
Activating the Feature (p. 2-10)
Configuring the feature using EMS (p. 2-11)
Provisioning the Access Terminal (p. 2-16)
Provisioning the RAN AAA server (p. 2-17)
Provisioning the route for RAN AAA on the TP (p. 2-18)

Operations and Maintenance Center - Radio Access Network (OMC-RAN) configuration


management

For more information about the different 1xEV-DO OA&M interfaces that are used in
performing OA&M tasks on the EV-DO controller and its managed resouces,
including the purpose of each interface and how to access it, see Alcatel-Lucent 9271
EV-DO Radio Network Controller, 401-614-102, Chapter 3, User Interfaces.
See Appendix 7 of Alcatel-Lucent 9271 EV-DO Radio Network Controller,
401-614-102 for basic information in order to:

understand the OMC-RAN,

understand the layout of EV-DO information on the OMC-RAN, and


provisioning activities on EV-DO network and elements from the OMC-RAN.

Also see the About this information product at the beginning of this document for
the most commonly-used ways to find certain information on EMS and where to find
the equivalent information on the OMC-RAN, or CDMA2000 1xEV-DO
Configurations Parameters Guide, 401-614-324.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
2-9
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Radio


Access Network Authentication (RAN)

Activating
the Feature
...................................................................................................................................................................................................................................
Purpose

This procedure activates the 1xEV-DO RAN Authentication feature in a CDMA2000


1xEV-DO network. Follow the steps for a standalone OMP-FX or a shared OMP-FX,
depending on your configuration.
Procedure for a standalone OMP-FX

If you have a standalone OMP-FX, perform the following steps:


...................................................................................................................................................................................................

Contact your Customer Technical Advocate (CTA) about the generation of an OMP
Feature Activation File (FAF).
...................................................................................................................................................................................................

Proceed to Configuring the feature using EMS (p. 2-11).


E...................................................................................................................................................................................................
ND OF STEPS

Procedure for a shared OMP-FX

If you have a shared OMP-FX, perform the following steps:


...................................................................................................................................................................................................

Ask your account executive to activate the following entry in your FAF:
A12 RAN Authentication
...................................................................................................................................................................................................

Proceed to Configuring the feature using EMS (p. 2-11).


END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

2-10

CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Radio


Access Network Authentication (RAN)

Configuring
the feature using EMS
...................................................................................................................................................................................................................................
Purpose

Use this procedure to configure the 1xEV-DO RAN Authentication feature for a service
node using the EMS Graphical User Interface (GUI).
Procedure

Perform the following steps:


...................................................................................................................................................................................................

Verify IP connectivity to the RNC. From the RAN AAA server, ping the Traffic
Processor (TP) external ports. If the ping is successful, proceed with EMS
provisioning. If the ping fails, do a routeadd on the TP. The procedure to add routes
to the TP is described in the CDMA2000 1xEV-DO Radio Access System Planning
and Implementation Guide, 401-614-101.
...................................................................................................................................................................................................

Access the OMP Web page according to your local practices.


Result: The OMP Web page appears.
...................................................................................................................................................................................................

Click on the Configuration Data Icon.


Result: The Configuration Data page appears. It lists the components that can be

configured.
...................................................................................................................................................................................................

Click on the link to AAA Servers.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
2-11
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Radio


Access Network Authentication (RAN)

Configuring the feature using EMS

Result: A page similar to the following appears.

...................................................................................................................................................................................................

Click on the AAA IP Address for the AAA you want to configure for RAN
Authentication.
Result: The AAA Server Instance page appears. (The blue navigation buttons are

not shown in the rest of the examples.)

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

2-12

CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Radio


Access Network Authentication (RAN)

Configuring the feature using EMS

...................................................................................................................................................................................................

Configure the AAA server parameters as follows:

Click on the value you wish to use for A12 Shared Secret Format. The default is
ASCII format.
Enter a value for A12 Shared Secret.
The length of Shared Secret data is a fixed length of 16 for ASCII format and a
fixed length of 32 for hexadecimal format.

...................................................................................................................................................................................................

Click the Submit button.


...................................................................................................................................................................................................

In the list of blue navigation buttons on the left side of this EMS page, click on the
link to Service Nodes. (You may need to scroll down to see that link.)
Result: The Service Nodes Summary page appears.
...................................................................................................................................................................................................

Click on the Service Node you want to configure for RAN Authentication. On the
resulting screen, scroll down in the window until you see the link to A12 RAN
Authentication.
Result: The following example shows the link to the A12 RAN Authentication

parameters for Service Node 3.

...................................................................................................................................................................................................

10

Click on the link for A12 RAN Authentication.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
2-13
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Radio


Access Network Authentication (RAN)

Configuring the feature using EMS

Result: The RAN Authentication Instance Page for that service node appears.

...................................................................................................................................................................................................

11

Configure the A12 RAN Authentication parameters as follows:

Enable RAN Authentication


This parameter indicates the status of the RAN authentication feature:
Click the radio button beside Enabled.
A12 Retry Timer
This timer indicates the allowed interval for receiving either an Access Accept or
Access Reject message from the A12 AAA before retrying the Access Request
message and re-reaching 0.
Enter a number from 1 to 4. The default is 2 seconds.
AAA Server Out-of-Service Retry Timer
If an AAA server has been declared out of service by the Radio Network Controller
(RNC), this timer sets the interval after which the TP attempts an A12 Access
Request to the AAA server to test if it is back in service. This timer does not apply
if all provisioned A12 AAA servers are declared out of service. In this example all
provisioned means is only one server is provisioned and it is out of service or if
two servers are provisioned and they are both out of service.
Enter a number from 1 to 900. The default is 900 seconds.
A12 Retry Count
This parameter indicates the number of times the RNC can reset the A12 Retry
Timer before declaring an AAA server out of service. If an alternate A12 AAA
server has been provisioned, this counter is reset to 0 when the RNC sends its first
Access Request message to the alternate AAA for a given CHAP identifier.
Enter a number from 1 to 3. The default is 3.

...................................................................................................................................................................................................

12

Click the Submit button at the bottom of the page. (Scroll down to see this button, if
it is not visible on the screen.)

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

2-14

CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Radio


Access Network Authentication (RAN)

Configuring the feature using EMS

Result: You have submitted the RAN Authentication parameters for that service

node.
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
2-15
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Radio


Access Network Authentication (RAN)

Provisioning
the Access Terminal
...................................................................................................................................................................................................................................
Purpose

Use this procedure to provision the AT for RAN Authentication.


Procedure

Perform the following steps:


...................................................................................................................................................................................................

Provision the International Mobile Station Identity (IMSI).


...................................................................................................................................................................................................

Provision the CHAP username. This should match the username format in the RAN
AAA server.
...................................................................................................................................................................................................

Provision the CHAP Authentication password. This should match the password in the
RAN AAA server.
...................................................................................................................................................................................................

Provision any other AT parameters at your discretion.


END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

2-16

CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Radio


Access Network Authentication (RAN)

Provisioning
the RAN AAA server
...................................................................................................................................................................................................................................
Purpose

Use this procedure to provision the RAN AAA server.


Procedure

Perform the following steps:


...................................................................................................................................................................................................

Make sure you are running NAVIS Radius 4.3.2 or later.


...................................................................................................................................................................................................

Provision the Shared Secret Data to match what is provisioned in the EMS.
...................................................................................................................................................................................................

Create a profile for each device. In the profile, Call Back ID is a mandatory field that
should be returned by the RAN AAA when RAN AAA is successful. All other fields
are optional.
Enter a Callback ID for each profile and any of the optional fields:
1. Call Back ID, which is 0 (zero) plus 15 digit IMSI. Call Back ID must be defined
as a string for the functionality to work.
2. RAN AAA username as defined by the service provider. This should be different
from the username for PDSN AAA authentication.
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
2-17
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Radio


Access Network Authentication (RAN)

Provisioning
the route for RAN AAA on the TP
...................................................................................................................................................................................................................................
Purpose

Use this procedure to provision the route for the RAN AAA on the traffic processor.
Procedure

Perform the following steps:


...................................................................................................................................................................................................

Do a routeadd on the TPs for each RNC to route to the RAN AAA server.
For more information, see CDMA2000 1xEV-DO Radio Access System Planning and
Implementation Guide, 401-614-101.
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

2-18

3 ell Swing Capability for


C
EVolution Data Optimized
(1xEV-DO)

Overview
...................................................................................................................................................................................................................................
Purpose

This chapter describes the following optional features in CDMA2000 1xEV-DO


networks. The Feature Identifiers (FIDs) of the feature in this chapter is:

Cell Swing Capability for 1xEV-DO (FID 12188.1)

Cell Swing Capability for 1xEV-DO removed in Release 29.0

Important! As of Release 28.0, Pre-Converged Cell Swings (FID 12188.0) are no


longer applicable once all the cells are converged, or the OMP-FX has been
upgraded to Release 28.0 software, whichever comes first. The instructions for Cell
Swings and the deprecated objects were removed from this document in R29.0,
maintaining only the FAF activation and any background information that helps the
understanding of this feature.
This document will acknowledge that if the EVDO RNC is managed by OMC-RAN,
nothing changes with respect to Cell Swing. Release 28.0 feature OMP-FX Bulk
Provisioning Capability for OMC-RAN Managed DO-RNCs, (FID 9123.2), provides
the functionality for BP to still work on the OMP-FX regardless of whether the RNC is
managed by EMS or OMC-RAN (and BP [and therefore Cell Swing] still runs on the
OMP-FX in both cases).
Information about migrating the RNC from EMS to OMC-RAN is described in
CDMA2000 1xEV-DO Radio Access System Planning and Implementation Guide,
401-614-101.
For detailed procedures regarding the impact of OMC-RAN becoming a mandatory
platform for EV-DO in R29.1 and later, see Appendix 7 of Alcatel-Lucent 9271 EV-DO
Radio Network Controller, 401-614-102.
Feature summary

Following is the high-level summary of the feature covered in this chapter:


...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-1
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Overview

Cell Swing Capability for 1xEV-DO (FID 12188.1)

The Cell Swing Capability for 1xEV-DO feature provides the ability to:

move one or more 1xEV-DO Base Transceiver Stations (BTSs), along with all of
their related managed objects and call processing data, from one pair of FMS-APs
to another pair of FMS-APs
on the same RNC frame, or
between two RNC frames within the same or different Service Node(s)
rename one or more 1xEV-DO BTS(s) without moving the BTS(s) off of the
FMS-AP pair
performing a move and rename in one procedure for one or more 1xEV-DO BTSs
updating specific fields of specific forms associated with the cell data in the
1xEV-DO RNC call processing databases for cells that are moving/renaming
updating the Source and Target Dynamic Host Configuration Protocol (DHCP)
tables, netmask files, and T1 network files

This feature also moves mixed-mode cells in a network that supports Cell Operations,
Administration and maintenance (OA&M) Convergence.
Impacts on user interfaces
Feature

User interface

Feature impact

Cell Swing Capability for


1xEV-DO (FID 12188.1)

Element Management
System (EMS) and
Operations and
Maintenance Center Radio Access Network
(OMC-RAN)

See Activating the


feature (p. 3-24)

Service measurements

None

Automatic Message
Accounting (AMA)
subsystem

None

Technician Interface (TI)


(input/output messages)

None

To obtain technical support, documentation, and training or submit feedback

The Online Customer Support (OLCS) web site (http://support.lucent.com/) provides


access to technical support, related documentation, related training, and feedback tools.
The site also provides account registration for new users.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-2

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Overview

Contents
Availability

3-4

Prerequisites

3-5

Feature description: Cell Swing Capability for 1xEV-DO

3-7

Feature interactions

3-19

Issues and caveats

3-22

Implementing the features

3-23

Activating the feature

3-24

Confirming feature activation

3-26

Determining the NthIP

3-27

Move a 1xEV-DO cell (intra-RNC)

3-29

Move a 1xEV-DO cell (inter-RNC/Same Service Node)

3-44

Move a converged 1xEV-DO cell (inter-RNC/Different Service Node)

3-61

Rename a cell

3-79

Move and Rename a cell (intra-RNC)

3-93

Move and Rename a cell (inter-RNC)

3-108

Cell Swing backout procedure

3-126

Verify OA&M on moved and/or renamed converged cell

3-129

Verify service measurements reporting

3-132

Cleanup of old Cell Swing files

3-134

Moving Base Stations from R1SR Based 1xEV-DO RNC APs to


Universal Cabinet (UNC)-Based 1xEV-DO RNC APs

3-136

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-3
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Availability
...................................................................................................................................................................................................................................
Release availability
Feature

Available in

Cell Swing Capability for 1xEV-DO

Releases 26.0 SU2 and later


(Cell Release 25)

Market availability
Feature

Available in

Cell Swing Capability for 1xEV-DO

all markets

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-4

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Prerequisites
...................................................................................................................................................................................................................................
Introduction

The 1xEV-DO Cell Swing features have the following prerequisites.


Important! Per the impact of 1xEV-DO Gold BCMCS (FID 10862.5) feature the
Broadcast/Multicast Service (BCMCS) carrier activation must be deactivated
before attempting a cell swing. If not the cell swing will be aborted and the or the
result will be an aborted and the Source RNC Database must be restored.
Supported technologies

The 1xEV-DO Cell Swing features are supported in the following air-interface
technologies:

1xEV-DO

Software requirements

The Cell Swing Capability for 1xEV-DO software capabilities are listed below:
Cell Swing Capability for 1xEV-DO feature

The Cell Swing Capability for 1xEV-DO feature requires Platform Release 25.0 or
later, and the following features to be activated:

Bulk Provisioning (FID 9123.0)


1xEV-DO Bulk Provisioning Enhancements (FID 9123.1)

To support mixed-mode cells, the folowing features are required:

Inter-MSC Cell Swing (FID 2794.0)


Inter-MSC Cell Swing Modular Cell 4.0/HD4.0 (FID 2794.1)
Important! 1xEV-DO Cell Swing is activated by a single FAF entry (see
Activating the feature (p. 3-24) ).

RRL (Restricted Root Login)

In RRL on mode, you need to be a system administrator or you have to have the user
account access that is assigned the rsysadm system administrator role.
Hardware requirements

The Cell Swing Capability for 1xEV-DO feature requires no hardware beyond the
standard hardware in a wireless network.
Supported BTS types are: CDMA2000 , 1xEV-DO modular cells and Alcatel-Lucent
CDMA Base Stations.
The Cell Swing Capability for 1xEV-DO hardware capabilities are listed below:
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-5
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Prerequisites

Interface requirements

The Cell Swing Capability for 1xEV-DO feature requires root login access on the
Operations and Maintenance Platform (OMP) and the FMS-AP interfaces to enter the
1xEV-DO cell swing tool(s).

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-6

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Feature
description: Cell Swing Capability for 1xEV-DO
...................................................................................................................................................................................................................................
Introduction

The following information describes the functionality and operation of the 1xEV-DO
Cell Swing feature.
Functionality

The 1xEV-DO Cell Swing feature facilitates:

moving one or more 1xEV-DO Base Transceiver Stations (BTSs), along with all of
their related managed objects and call processing data, from one pair of FMS-APs
to another pair of FMS-APs
on the same RNC frame
between two RNC frames within the same Service Node
between two RNC frames residing on different Service Node(s)
renaming one or more 1xEV-DO BTS(s) without moving the BTS(s) off the
FMS-AP pair
perform a move and rename in one procedure for one or more 1xEV-DO BTSs
updating specific fields of specific forms associated with the cell data in the
1xEV-DO RNC call processing databases for cells that are moving/renaming
updating the Source and Target Dynamic Host Configuration Protocol (DHCP)
tables, netmask files, and T1 network files
Additionally, the evdoswing tool has been updated to generate backout scripts for
the Neighbor SN NeighborSector managed objects. The backout scripts are to be
used in the event a cell is not successful.

How the feature operates

The 1xEV-DO Cell Swing feature is comprised of several tools run on the OMP for
(OMP-FX). The tools, restricted to root login permission, accomplish a 1xEV-DO cell
move by accessing the following tasks by creating/deleting/modifying information as
needed:

Source Bulk Provisioning (BP) database table dumps


Target Bulk Provisioning database table dumps (if Target RNC is different from the
Source RNC)
Neighboring Service Node (SN) Bulk Provisioning Neighbor Sector table dumps
Source network files
Target network files on the Source OMP (copied from the Target system to the
Source OMP if Target RNC is different from the Source RNC)

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-7
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Feature description: Cell Swing Capability for 1xEV-DO

The Cell Swing Capability for 1xEV-DO feature also examines the value of BTS
Convergence Flag to determine if a particular cell has gone through the Cell OA&M
Convergence conversion process. BTS Convergence Flag is a read-only attribute,
available on the Element Management System (EMS) or if the RNC was migrated to
the OMC-RAN, go to the OMC-RAN GUI, used to indicate the Cell OA&M
Convergence status of the Base Transceiver Station (BTS).
For cells that have gone through convergence (BTS Convergence Flag is yes), the
tool migrates only the following cell data:

Cell
Sector
NeighborSector
IFHO Targets
Sector Carriers

Tool Set
Tool

Description

evdodump

Tool to extract the 1xEV-DO RNC


FMS-AP database tables/data used by
evdoswing; run on the OMP of the
Source, Target, and Neighboring service
node system.

evdoswing

Tool used to create the BP scripts to move


the BTS translation data from the Source
to the Target system; run on the Source
OMP.

evdomkdir

Creates a directory structure for


evdonetwork to use.

evdonetwork

Tool used to delete/update the network


files on both the Source and Target RNC
FMS-APs; run on the Source OMP. It
creates scripts which have to be
transferred to both the Source and Target
Lead FMS-APs and run on those systems
to delete/create the corresponding entries
for the moved/renamed BTS.

Note: The tools reside on the OMP, under the /omp/bin directory.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-8

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Feature description: Cell Swing Capability for 1xEV-DO

Logfiles

Logfiles for all tools are housed in: /omp-data/logs/evdotools/


Logfile names:

evdodump.log
evdoswing.log
evdonetwork.log
runBPmmddyyyy.log

Preliminary setup

The user prepares for the move by:


1. Logging on to the Source OMP as root in the order shown
2. See Step 6 for the explanation of the Restrict Root Login (RRL).
In the RRL off mode make a backup copy of the FMS-AP using dbunload, located
in: /flx/ONEXEVc/current/release/util
In the RRL on mode, log on to the database FMS-AP with a user account and
assume rsysadm role. Choose a directory under
rsysadm home /roles/rsysadm/dbbackup.
Important! If this directory does not exist, then it should be created:
mkdir p /roles/rsysadm/dbbackup
cd /roles/rsysadm/dbbackup
$HDRROOT/release/util/dbunload
3. Obtaining a list of active generics on the Source and Target systems (to ensure that
the cell generics installed on the cell to be swung are available on the Target RNC)
4. Enabling the BP tools environment
5. Making a temporary directory to contain the user-created input files and BP dump
output files
6. Starting with Release 30.0, DO RNC security feature Restrict Root Login (RRL)
(FID 10737.9) restricts access to DO RNC root and onexev accounts on APs.
However, the steps on OMP are still performed with an OMP root account. But in
the RRL on mode, you will need access to the RNC user account that has access to
the rsysadm role or you are the privileged system administrator. Specific steps
within this chaptes procedures indicate the RRL on mode and the RRL off mode. In
the RRL on mode, there are specific steps to be done on a DO RNC AP with a role
user account like taking backing and transferring the swing scripts. There are
specific steps that are needed to be executed as the rsysadm role in this mode.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-9
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Feature description: Cell Swing Capability for 1xEV-DO

If person1 were to log on DO RNC lead AP and has access to the rsysadm role
the following is an example of how to login and access the rsysadm role:
Type and enter: ssh person1@flx121
Type and enter: su rsysadm
Type and enter a password:
Enter the rsysadm role password on the prompt to get access.

evdodump

The user changes directory (cd) to the temporary directory made during the initial
setup. The user enters the evdodump tool from within the temporary directory. The user
is then prompted for the SN OMP type (s for Source, n for Neighbor, or t for Target)
and the SN ID. The tool invokes the Bulk Provisioning (BP) tool, creating BP dump
scripts which automatically dump data using Bulk Provisioning on the Source, Target,
or Neighboring SNs OMP. On the Source SN OMP, all the tables will be dumped.
Important! Never breakout of evdodump after the command has been started. Once
the command has been entered, information is transmitted to the database interface.
Using the Break Key or using <CNTL> -c does not stop evdodump from executing,
it will only prevent you from seeing any output (success or failure) messages that
would have been displayed on the OMP. This feature allows the moving/renaming
of converged cells. When moving/renaming converged cells, the -c option is
mandatory on the command line.
For additional information, see Bulk Data Provisioning - Limitations section of
CDMA2000 1xEV-DO Networks EMS Configuration Management Bulk
Provisioning Guide, 401-614-325.
On the Target SN OMP, only the AP and Neighbor Sector tables will be dumped. On
the Neighboring SN OMP, only the AP and the Neighbor Sector tables will be dumped.
The evdodump tool utilizes the following information:
1. A user-created file (called cell_file) defining the changeable cell attributes
Example command lines:
evdodump -d evdo_dumpdir -i cell_file
evdodump -h

Where:
evdo_dumpdir

Top node of directory structure where BP


unloads data; Use $bpPath variable.

cell_file

user-created cell input file

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-10

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Feature description: Cell Swing Capability for 1xEV-DO

-c

dumps tables for converged cells

-h

prints the evdoswing command usage


help message

Sample BP dump output

This sample shows all the Source BTS Identifier-related forms. The first script dumps
AP table, which is later parsed to gather the FMSFrameId (needed to dump all other
scripts by frame ID).
output stored AP for which (hdrsnID=xx) to APxx.txt;
output stored Cell for which (hdrsnId = xx, FMSFrameId = yy) to
Cellxxyy.txt;
output stored CellCabinet for which (hdrsnId = xx, FMSFrameId = yy) to
CellCabinetxxyy.txt;
output stored Sector for which (hdrsnId = xx, FMSFrameId = yy) to
Sectorxxyy.txt;
output stored NeighborSector for which (hdrsnId = xx, FMSFrameId = yy)
to NeighborSectorxxyy.txt;
output stored CDM for which (hdrsnId = xx, FMSFrameId = yy) to
CDMxxyy.txt;

Forms and key fields


Form (in growth order)

Key Fields

Cell

hdrsnId, FMSFrameId, CellSiteId

Sector

hdrsnId, FMSFrameId, CellSiteId, SectorId

NeighborSector

hdrsnId, FMSFrameId, CellSiteId,


SectorId, NbrId

IFHOTarget

hdrsnId, FMSFrameId, CellSiteId,


SectorId, CarrierId, TargetId

SectorCarrier

hdrsnId, FMSFrameId, CellSiteId,


SectorId, CarrierId

Form (in degrowth order)

Key Fields

SectorCarrier

hdrsnId, FMSFrameId, CellSiteId,


SectorId, CarrierId

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-11
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Feature description: Cell Swing Capability for 1xEV-DO

Form (in degrowth order)

Key Fields

IFHOTarget

hdrsnId, FMSFrameId, CellSiteId,


SectorId, CarrierId, TargetId

NeighborSector

hdrsnId, FMSFrameId, CellSiteId,


SectorId, NbrId

CDM

hdrsnId, FMSFrameId, CellSiteId,


CellSiteCabId, CdmId

Sector

hdrsnId, FMSFrameId, CellSiteId, SectorId

CellCabinet

hdrsnId, FMSFrameId, CellSiteId,


CellSiteCabId

Cell

hdrsnId, FMSFrameId, CellSiteId

For cells that have not gone through the convergence process, the tool continues to
migrate all of the cell-related data supported by the 1xEV-DO Cell Swing feature.
evdoswing

The evdoswing tool is entered on the Source OMP to create the insert, delete, and
replace BP scripts to move the BTS translation data. The evdoswing tool utilizes three
pieces of information:
1. A user-created file (called cell_file) defining the changeable cell attributes
2. A user-created file (called sn_file) defining the service nodes for the Source SN,
Target SN, and each of the Neighbor SNs affected by the moving of cells on the
Source SN
3. The path to the temporary directory (used in the evdodump command) where the
table data was dumped
It also allows the moving/renaming of cells.
cell_file file

The cell_file file is a user-created file that defines the changeable cell attributes. The
first row of the file is a required header row containing a comma-separated list of key
field names, entered in any order. The subsequent rows contain lists of
comma-separated data values and must match the same order as the header row. The
data value rows may contain a new value or an n. The n value means no change and
can be used as a place holder for any of the optional fields, in case some of the fields
change for some but not all of the BTSs.

Required fields are:


CellSiteIdOld, CellSiteNew, FMSFrameIdNew,and convFlag

Optional fields are: apIDNew, hdrHWSrvrIdNew, and btsNameNew

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-12

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Feature description: Cell Swing Capability for 1xEV-DO

Sample cell_file file:


CellSiteIdOld,CellSiteIdNew,FMSFrameIdNew,convFlag,apIdNew,
hdrHWSrvrIdNew,btsNameNew
11,205,20,1,193,418,farHills
107,203,20,1,194,426,N
166,263,20,1,192,410,N

Important! All cells in the user-created cell_file must be converged.


Important! The convFlag value must be set to one, 1, designating converged
cells.
Important! The btsNameNew value included in the input file cannot be the same
as any btsNameNew that exists on the Target system.
Important! Optional field hdrHWSrvrIdNew should be provided with a value of
800 for a converged cell whose current hdrHWSrvrId is not 800 , whenever the cell
is swung to a different frame.
Important! This work around can be used only to correct the HWSrvrId of only
ONE converged cell with a non-800 HWSrvrId. For all other converged cells which
are swung in this tool execution, the hdrHWSrvrIdNew should be n.
sn_file file

The sn_file file is a user-created file that defines the affected service nodes. This file
does not have a header line. The file contains a single comma-separated list of node
names (numbers):
Source Service Node, Target Service Node, Neighbor Service Node 1,
Neighbor Service Node 2,. . ., Neighbor Service Node 10 .

Required fields are:


Source Service Node and Target Service Node (Target SN is required
only if it is different from the Source SN or if a Neighbor SN is entered).

Optional fields are: Neighbor Service Node #

Sample sn_file file:


3,1,2

Where:

3 = Source SN
1 = Target SN
2 = Neighbor SN
Important! If Neighbor Service Node IDs are not entered, then it is assumed that
they are not affected and therefore scripts will not be generated for them.
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-13
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Feature description: Cell Swing Capability for 1xEV-DO

Important! All OMPs (including the Source 1xEV-DO RNC FMS-AP, the Target
1xEV-DO RNC FMS-AP, and the Neighboring cells) must be on the same software
release and software update. If the Neighbor cell(s)/OMP(s) are on a different
release, the Neighbor lists must be manually updated.
Path to the temp directory

The temporary directory contains the output of the BP dump scripts (one .txt file for
each applicable cell-related form). When executing the EVDO cell swing tools, the -d
field requires the user to specify the path the temporary directory. The $bpPath
environment variable may be substituted for the full path in the command line.
Example command lines:

The command is typed on a single continuous line at the OMP interface:


evdoswing -d evdo_dumpdir -i cell_file -s sn_file [-v]
evdoswing -h

Where:
evdo_dumpdir

Top node of directory structure where BP


unloads data; Use $bpPath variable.

cell_file

user-created cell input file

sn_file

user-created service node file

-v

prints further details of evdoswing


process (optional)

-h

prints the evdoswing command usage


help message

evdomkdir

The evdomkdir command is run once on the Source OMP. The evdomkdir command
creates a directory structure to be used when transferring the network files, which are
later used by evdonetwork. For each Source service node XXX, evdomkdir creates the
directory top_node/sXXX/fYY. Likewise, for each Target service node XXX and
FMSFrameIdNew YY, evdomkdir creates the directory top_node/s XXX/fYY.
If the directory is already present, the tool will report that this is the case. If there are
problems creating the directory, or if a file (instead of directory) is already present,
errors will print.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-14

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Feature description: Cell Swing Capability for 1xEV-DO

evdonetwork

The evdonetwork tool is run once on the Source OMP. The evdonetwork tool creates
scripts that

Delete v entries for each cell being modified


Delete dhcp entries for each cell being modified
Delete netmasks entries for each cell being modified
Create netmasks entries
Create dhcp entries
Create T1 entries
Adds T1 entries

Scriptnames

are in the format

t1fileDel<SNID><FMSID>
dhcpDel<SNID><FMSID>
netmskDel<SNID><FMSID>
netmskAdd<SNID><FMSID>
dhcpAdd<SNID><FMSID>
t1fileCrt<SNID><FMSID>
t1entryAdd<SNID><FMSID>

network_file file

The network_file file is a user-created file that defines the Source and Target frame
IDs. The first row of the file is a required header row containing key field names,
entered in any order. The second row is a data value row and must match the same
order as the header row.

Required fields are:


FMSFrameIdOld, FMSFrameIdNew, CellSiteIdOld, CellSiteNew,

and NthIp

Optional fields are:


CellSubnet, CellNetmask, T1IpAddr_1, T1SubnetMask_1, T1IpAddr_2,
T1SubnetMask_2, T1IpAddr_3, T1SubnetMask_3, T1IpAddr_4, T1SubnetMask_
4, EthernetBH, EthernetBH_Subnet, EthernetBH_Netmask, btsNameNew,and
CdmNo (CDM number in multi-carrier cell: value range = 1 to 3)

Sample network_file file:


CellSiteIdOld,CellSiteIdNew,FMSFrameIdOld,FMSFrameIdNew,CdmNo,NthIp
242,542,5,8,1,2

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-15
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Feature description: Cell Swing Capability for 1xEV-DO

The Nth IP variable is determined by subtracting the last three digits of the
T1_IP_address from the Client IP address. Refer to the Determining the NthIP
(p. 3-27) procedure for specific details.
NthIP

The Nth IP variable is determined by subtracting the last three digits of the
T1_IP_address from the Client IP address. Refer to the Determining the NthIP
(p. 3-27) procedure for specific details.
Example command lines:
evdonetwork -n evdo_dumpdir -i network_file -s sn_file
evdonetwork -h

Where:
evdo_dumpdir

Top node of directory structure where BP


unloads data; Use $bpPath variable.

network_file

user-created network input file

sn_file

user-created service node file

-h

prints the evdonetwork command usage


help message

Backout scripts

The evdoswing tool to generates backout scripts for the Neighbor Service Node BTS
Neighbor Sector managed objects which can be used in the event a cell swing is not
successful:
Example:

NeighborSectorXXXYYBackoutZ)
Where:
XXX
YY

= three-digit value for the Service Node ID

= two-digit value for the Frame ID

The backout scripts are housed in the same directory as the Add/Delete/Create scripts.
When entered, the backout scripts delete the new Neighbors and then add back the
original Neighbors.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-16

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Feature description: Cell Swing Capability for 1xEV-DO

Service-provider perspective

The 1xEV-DO Cell Swing feature requires service providers to ensure that:

The Bulk Provisioning feature is available to dump and load 1xEV-DO RNC table
data,
Sufficient disk space is available on the OMP to dump the 1xEV-DO RNC table
data (disk space requirement should be based on table data sizes as known by local
craft),
All OMPs (including the Source 1xEV-DO RNC FMS-AP, the Target 1xEV-DO
RNC FMS-AP, and the Neighboring cells) are on the same software release and
software update (if the Neighbor cell(s)/OMP(s) are on a different release, the
Neighbor lists must be manually updated),
The OMP and FMS-AP are networked and have a means to transfer data files via
the network command sftp, and
The FMS-APs must have the same software revision numbers.

Modifiable BTS information

Non-key attributes of the BTS and its contained managed objects may be modified.
These attributes are:

BTS primary FMS-AP number


BTS (cell) name
BTS (cell) cabinet - hardware server ID

Networking information may also be modified; specifically:

Primary FMS-AP IP address


Cell IP address (cell subnet)
Cell netmask
T1 IP address
T1 subnet mask

Ethernet Backhaul Subnet


Ethernet Backhaul Netmask
Important! If the user does not provide this information, then the existing
information provisioned on the Source RNC is used.

Skill Sets Required

When moving cells, the Cell Swing tools user should be familiar with:

the database backup command/operation


the database copy forward command/operation
OMP ROP files
cell translations for various cell configurations

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-17
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

CDMA Cell Swing tools

Bulk Provisioning

Feature description: Cell Swing Capability for 1xEV-DO

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-18

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Feature
interactions
...................................................................................................................................................................................................................................
Cell Swing Capability for 1xEV-DO feature

The Cell Swing Capability for 1xEV-DO feature interacts with the following features:

1xEV-DO Rev. A Software License (FID 12078.2)


Bulk Provisioning (FID 9123.0)
Universal Cabinet (UNC) Based 1xEV-DO RNC Infrastructure (FID 12885.1)
1xEV-DO Cell OA&M Convergence (FID 11003.1)
Inter-MSC Cell Swing (FID 2794.0)
Inter-MSC Cell Swing Modular Cell 4.0/HD4.0 (FID 2794.1)
1xEV-DO Gold BCMCS (FID 10862.5)

1xEV-DO Rev. A Software License (FID 12078.2)

The 1xEV-DO Rev. A software license key, introduced by FID 12078.2, is required to
activate Rev. A on Rev. A capable BTS carriers. When a Rev. A converged cell is to
be swung, the user must check that there are available Rev. A software licenses on the
target RNC so that the Rev. A will be active on this cell after it is swung.
If Rev. A is not active on the target RNC, then Rev. A must be deactivated on the
cell(s) before the cell swing tools are used.
If there are not enough Rev. A software licenses available on the target RNC, and the
cell is swung to that RNC, then the cell will come up as a Rev0 cell.
If more Rev A licenses are needed, the user has to install a new Rev. A software
license key. The procedure to install the Rev A software license key is described in the
Activating the 1xEV-DO Rev. A services chapter of the CDMA2000 1xEV-DO Radio
Access System Planning and Implementation Guide, 401-614-101.
Bulk Provisioning (FID 9123.0)

The Bulk Provisioning feature allows configuration of multiple cells (via a script)
without going through individual cell provisioning via EMS screens. The 1xEV-DO
Cell Swing feature uses the Bulk Provisioning feature to dump and load 1xEV-DO
RNC table data. For details, see CDMA2000 1xEV-DO EMS Configuration
Management Bulk Provisioning Guide, 401-614-325.
Universal Cabinet (UNC) Based 1xEV-DO RNC Infrastructure (FID 12885.1)

The Universal Cabinet (UNC) Based 1xEV-DO RNC Infrastructure completes and
delivers the 1xEV-DO RNC in the Universal Cabinet (UNC).

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-19
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Feature interactions

This feature introduces the next generation 1xEV-DO Radio Network Controller
(RNC), which will be housed in a Universal Network Cabinet (UNC). The UNC-based
RNC is intended to provide a significant capacity increase compared to the
R1SR-based RNC. It is anticipated that the UNC-based RNC will support up to 600
1xEV-DO Carriers.
In order to provide the increased capacity, the UNC-based 1xEV-DO RNC cabinet
utilizes two new 48-port Ethernet switches (Extreme), up to 8 new Application
processors (AP CP2500) and up to 10 Universal Traffic Processors (UTP).
Important! Only UTPs are supported in UNCs (that is no 690s or 752s).
The configuration management of the UNC-based RNC is performed only via the
OMC-RAN (using OMC-RAN Graphical User Interface (GUI)). Information about
migrating the RNC from EMS to OMC-RAN is described in CDMA2000 1xEV-DO
Radio Access System Planning and Implementation Guide, 401-614-101
1xEV-DO Cell OA&M Convergence (FID 11003.1)

The 1xEV-DO Cell OA&M Convergence feature allows 1xEV-DO cell hardware
components to reside in the RC/V database instead of the 1xEV-DO database. Once a
cell has been moved to the RC/V database, it is considered converged. The BTS
Convergence Flag attribute, introduced by FID 11003.1, is used by the 1xEV-DO Cell
Swing feature to determine cell convergence status. When moving a converged cell,
only the BTS, BTS Cabinet, CDM, Sector, and Neighbor Sector objects will be moved.
Inter-MSC Cell Swing / Inter MSC Cell Swing Modular Cell 4.0/HD4.0 (FID 2794.1)

The Inter-MSC Cell Swing / Inter MSC Cell Swing Modular Cell 4.0/HD4.0 features
allow move/rename of CDMA modular cells. When 1xEV-DO cells are in mixed mode,
that is, CDMA Modular cells with 1xEV-DO cells in the same cell, it is expected that
both the Inter-MSC Cell Swing tool for the CDMA cells and the 1xEV-DO Cell Swing
for 1xEV-DO cells will be executed. For more information on the Inter-MSC Cell
Swing tools, see Inter-MSC Cell Swing, 401-612-150. Converged and unconverged
cells must be moved separately.
1xEV-DO Gold BCMCS (FID 10862.5)

Important! Must disable BCMCS carrier on the cell before running the cell swing
tool.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-20

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Feature interactions

When the 1xEV-DO Gold BCMCS feature is aligned with a cell swing:

If bcmcsActivationflag was set to Activate, prior to the cell swing , the


operator must set the flag to Deactivate before proceeding with a cell swing
procedure.
If the operator executes the cell swing tool and one of the carriers being swung has
a bcmcsActivationflag set to Activate the cell swing is aborted. Subsequently,
the database at the source RNC must be restored, using the database restoration
procedure.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-21
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Issues
and caveats
...................................................................................................................................................................................................................................
Introduction

The 1xEV-DO Cell Swing feature is subject to the following special issues and/or
caveats.
Issues

The 1xEV-DO Cell Swing feature supports only configurations where all OMPs
(including the Source 1xEV-DO RNC FMS-AP, the Target 1xEV-DO RNC FMS-AP,
and the Neighboring 1xEV-DO RNC FMS-APs) are on the same software release and
software update. If the Neighbor 1xEV-DO RNC FMS-AP(s)/OMP(s) are on a different
release, the Neighbor lists must be manually updated.
Caveats

Any router configuration updates that might be necessary as a result of cell


movement is beyond the scope of the 1xEV-DO Cell Swing feature and beyond the
scope of this chapter.
However, note that when cells are being moved inter-RNC under the same
ServiceNode (which requires router changes), change the current IP
helperaddress/dhcp relay IP address and do not just add it to the current router
configuration. If the router has both the new and the previous IP helper/dhcp relay
addresses in the router configuration(s), then it can cause the cell not to dhcp or
stable clear (or can take hours to finally dhcp because the router would be going to
the previous lead FMS-AP for the BTSs IP address). This applies to both primary
and secondary routers when there is a redundancy.
It is recommended that the service provider swing no more than 10 cells during a
single maintenance window. This applies to either pre-converged or converged
cells.
Refresh any BTS Summary Page opened before or during Cell Swing activities to
ensure current BTS Cell Status is displayed. Using only one instance of the BTS
Summary Page will minimize display performance issues.
A converged cell that is swung using the EVDO Cell Swing tool cannot be backed
out and converted into a non-converged cell once it is in the new system. Unless it
is done using the manual procedures.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-22

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Implementing
the features
...................................................................................................................................................................................................................................
Process

To implement the 1xEV-DO Cell Swing feature, perform the following procedures in
sequence:
Activating the feature (p. 3-24)
Confirming feature activation (p. 3-26)
Determining the NthIP (p. 3-27)
Move a 1xEV-DO cell (intra-RNC) (p. 3-29)
Move a 1xEV-DO cell (inter-RNC/Same Service Node) (p. 3-44)
Move a converged 1xEV-DO cell (inter-RNC/Different Service Node) (p. 3-61)
Rename a cell (p. 3-79)
Move and Rename a cell (inter-RNC) (p. 3-108)
Move and Rename a cell (intra-RNC) (p. 3-93)
Cell Swing backout procedure (p. 3-126)
Verify OA&M on moved and/or renamed converged cell (p. 3-129)
Verify service measurements reporting (p. 3-132)
Cleanup of old Cell Swing files (p. 3-134)

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-23
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Activating
the feature
...................................................................................................................................................................................................................................
Purpose

This procedure activates the 1xEV-DO Cell Swing feature in a wireless network.
Important! If the RNC is managed by EMS, procedures as stated in this document
are valid, going through the GUI. If the RNC has been migrated to the OMC-RAN,
the customer has to go through the OMC-RAN GUI to see maintenance state
displays, because Fault Management on EMS GUI will be shutdown for such
RNCs. If all the RNCs for a release were migrated to the OMC-RAN, the customer
must go to the OMC-RAN GUI to look at database data on a GUI screen, BUT
that data is always available to Bulk Provisioning users on the OMP-FX.
For detailed procedures regarding the impact of OMC-RAN becoming a mandatory
platform for EV-DO in R29.1 and later, see Appendix 7 of Alcatel-Lucent 9271
EV-DO Radio Network Controller, 401-614-102.
Configuration management: Operations and Maintenance Center - Radio Access Network
(OMC-RAN)

For more information about the different 1xEV-DO OA&M interfaces that are used in
performing OA&M tasks on the EV-DO controller and its managed resouces,
including the purpose of each interface and how to access it, see Alcatel-Lucent 9271
EV-DO Radio Network Controller, 401-614-102, Chapter 3, User Interfaces.
See Appendix 7 of Alcatel-Lucent 9271 EV-DO Radio Network Controller,
401-614-102 for basic information in order to:

understand the OMC-RAN,


understand the layout of EV-DO information on the OMC-RAN, and
provisioning activities on EV-DO network and elements from the OMC-RAN.

Also see the About this information product at the beginning of this document for
the most commonly-used ways to find certain information on EMS and where to find
the equivalent information on the OMC-RAN, or CDMA2000 1xEV-DO
Configurations Parameters Guide, 401-614-324.
Procedure

Perform the following steps:


...................................................................................................................................................................................................

Ask your account executive to activate the following entry in your Feature Activation
File (FAF):
1xEV-DO Cell Swing (EVDOSWING)

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-24

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Activating the feature

...................................................................................................................................................................................................

Proceed to Confirming feature activation (p. 3-26) .


END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-25
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Confirming
feature activation
...................................................................................................................................................................................................................................
Purpose

This procedure confirms the successful activation of the 1xEV-DO Cell Swing feature
in a wireless network.
Procedure

Important! Per the impact of 1xEV-DO Gold BCMCS (FID 10862.5) feature the
BCMCS carrier activation must be deactivated before attempting a cell swing. If
not the cell swing will be aborted and the or the result will be an aborted and the
Source RNC Database must be restored.
Perform the following steps:
...................................................................................................................................................................................................

For a stand-alone OMP, log in as root on all Source, Target, and Neighboring OMPs.
For a shared OMP, log in as root on the ECP.
...................................................................................................................................................................................................

At the prompt, enter: fafprint | grep EVDOSWING


Result: If the 1xEV-DO Cell Swing feature is active, the system returns:
1xEV-DO Cell Swing (EVDOSWING),

then this procedure is complete and you may

log off the root login.


...................................................................................................................................................................................................

If the system returns only a prompt, then the FAF was not activated. Rerun the
Activating the feature (p. 3-24) procedure.
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-26

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Determining
the NthIP
...................................................................................................................................................................................................................................
Purpose

This procedure calculates the NthIP variable used by the evdonetwork command.
When to perform

Perform this procedure prior to attempting to move/rename a cell, as the information


obtained during this procedure will be used during a cell move/rename.
Procedure

Important! Per the impact of 1xEV-DO Gold BCMCS (FID 10862.5) feature the
BCMCS carrier activation must be deactivated before attempting a cell swing. If
not the cell swing will be aborted and the or the result will be an aborted and the
Source RNC Database must be restored.
Perform the following steps:
...................................................................................................................................................................................................

Log onto the lead FMS-AP:

In RRL off mode


su - root.

In RRL on mode login with user


by entering: su - rsysadm.

assume onexev on lead AP and assume root id by entering:


account and then assume rsysadm role on lead AP

...................................................................................................................................................................................................

Enter: grep Cell <cell_id> /etc/netmasks


Where: <cell_id> is the ID of the cell being modified.
Example: grep Cell 155 /etc/netmasks
Result: A list of IP addresses are output.
Example:
10.150.200.20

255.255.255.224

#Cell 155

10.200.35.200

255.255.255.252

#first T1 for Cell 155

10.200.35.204

255.255.255.252

#second T1 for Cell 155

10.200.35.208

255.255.255.252

#third T1 for Cell 155

10.200.35.212

255.255.255.252

#fourth T1 for Cell 155

...................................................................................................................................................................................................

Write down the value of the first T1_IP_address (column 1 in the grep output from
Step 2) for the cell being modified.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-27
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Determining the NthIP

Example: 10.200.35.200
...................................................................................................................................................................................................

Enter: pntadm -P <T1_IP_address>


Where:
<T1_IP_address>

is the T1_IP_address from Step 3.

Example: pntadm -P 10.200.35.200


Result: Output example as follows:
Client ID

Flags

Client IP

Server IP

Lease
Expiration

00

01

10.200.35.202

10.208.172.59 Forever

Macro

Comment

mod5150

...................................................................................................................................................................................................

Write down the value of the Client IP from the output of the pntadm command in Step
4.
Example: 10.200.35.202
...................................................................................................................................................................................................

Subtract the last set of digits of the T1_IP_address from the Client IP address.
Example: 202 - 200 = 2
Result: The resulting value (in this example, 2) will be used as the NthIP

argument in the network_file.


END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-28

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move
a 1xEV-DO cell (intra-RNC)
...................................................................................................................................................................................................................................
Purpose

This procedure moves a 1xEV-DO cell from one FMS-AP pair to another FMS-AP pair
on the same RNC (intra-RNC). The Source OMP and Target OMP are the same for an
intra-RNC move.
Important! Mixed-mode EV-DO cells, that is, CDMA cells with EV-DO cells in
the same cell, may be moved by executing both the Inter-MSC Swing tools for the
CDMA cells (see Inter-MSC Cell Swing, 401-612-150) and the EV-DO Cell Swing
tools for the EV-DO cells.
Important! Before performing an EVDO cell swing, contact the Security
Administrator to ensure that security settings for the cell site EVDO CDMs are
properly set before the swing occurs.
Required skills and personnel

This procedure is best performed by an expert system administrator.


Related documentation

For detailed information on Inter-MSC Cell Swing, see Inter-MSC Cell Swing,
401-612-150.
For detailed information regarding 1xEV-DO Bulk Provisioning, see CDMA2000
1xEV-DO Network EMS Configuration Management Bulk Provisioning Guide,
401-614-325.
Prerequisites

To use the 1xEV-DO cell swing tools, you must have the following:

root

login access on the Operations & Maintenance Platform (OMP)


In RRL on mode, you need to be a system administrator or you have to have the
user account access that is assigned the rsysadm system administrator role.
1xEV-DO Cell Swing feature activated.

To use the Bulk Provisioning tool, you must have the following:

Access to the OMP shell


Appropriate permissions

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-29
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a 1xEV-DO cell (intra-RNC)

Important! For information on setting up a login on the OMP, see Alcatel-Lucent


9271 EV-DO Radio Network Controller, 401-614-102.

In addition, certain EMS provisioning steps must be completed before attempting to


use the Bulk Provisioning tool:
The Service Node and Frame must already be known to EMS by having
completed the AP Configuration process. (See the CDMA2000 1xEV-DO
Radio Access System Planning and Implementation Guide, 401-614-101).
The Configuration Database must be installed and operational (see the
CDMA2000 1xEV-DO Radio Access System Planning and Implementation
Guide, 401-614-101).
Data supplied to the configuration database should meet the known parameter
configuration guidelines. (See the CDMA2000 1xEV-DO Radio Access System
Planning and Implementation Guide, 401-614-101).
Ensure that all systems are stable before attempting an actual cell move.

Procedure

Important! Per the impact of 1xEV-DO Gold BCMCS (FID 10862.5) feature the
BCMCS carrier activation must be deactivated before attempting a cell swing. If
not the cell swing will be aborted and the or the result will be an aborted and the
Source RNC Database must be restored.
Perform the following steps:
...................................................................................................................................................................................................

Log on to the Source OMP as root.


Important! EVDO Cell Swings need to be done as root, and use a secured shell
environment.
...................................................................................................................................................................................................

In the RRL off mode, log on to the database FMS-AP of the Source OMP and make a
backup copy of the database as per standard procedures via dbunload. Run this
command in a new directory in the /app2 filesystem.
Important! /app2/DBbackup/swing<yyyymmdd>/ should be created and used as
the destination for the database backup.
For backup procedures, see Alcatel-Lucent 9271 EV-DO Radio Network Controller,
401-614-102.
In the RRL on mode, log on to the database FMS-AP with a user account and
assume rsysadm role. Choose a directory under
rsysadm home /roles/rsysadm/dbbackup.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-30

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a 1xEV-DO cell (intra-RNC)

Important! If this directory does not exist, then it should be created:

mkdir p /roles/rsysadm/dbbackup
cd /roles/rsysadm/dbbackup
$HDRROOT/release/util/dbunload

...................................................................................................................................................................................................

Log off of the DO-RNCAPs (returning to the OMP).


...................................................................................................................................................................................................

Skip this step if no network changes are being made. Otherwise, back up the network
files that may/will be modified on the lead FMS-APs.
In RRL off mode:

1. Log on to AP01 as onexev


2. mkdir -p /app2/swing/<yyyymmdd>/scripts
3. mkdir -p /app2/swing/<yyyymmdd>/backup
4. cd /app2/swing/<yyyymmdd>/backup
5. cp /etc/netmasks /app2/swing/<yyyymmdd>/backup
6. cp /var/dhcp/* /app2/swing/<yyyymmdd>/backup
7. Repeat Substeps 1 - 6 for AP02
8. Log off all DO-RNC APs
In RRL on mode:

1. Log on to AP01 as with the a user login


2. mkdir -p /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts
3. mkdir -p /<home_DIR>/<login_ID>/swing/<yyyymmdd>/backup
4. Log on to AP01 as user login account and create a swing dir under the login
account. cd /<home_DIR>/<login_ID>/swing/<yyyymmdd>/backup
5. cp /etc/netmasks /<home_DIR>/<login_ID>/swing/<yyyymmdd>/backup
6. cp /var/dhcp/* /<home_DIR>/<login_ID>/swing/<yyyymmdd>/backup
7. Repeat Substeps 1 - 6 for AP02
8. Log off all DO-RNC APs
Result: Temporary directories for the scripts and for saving a backup copy of the

network files are created. Backup copies of the /etc/netmasks files and of the entire
/var/dhcp/* directory are made. Note that the scripts directory will be used later.
...................................................................................................................................................................................................

Repeat Main Procedure Step 1-Step 3 for the Neighboring OMPs/RNCs.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-31
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a 1xEV-DO cell (intra-RNC)

...................................................................................................................................................................................................

On the OMP, make a temporary directory where the necessary input and output files
for this procedure will be stored.
Example: mkdir -p /home/swing/<yyyymmdd>
Where: <yyyymmdd>is the date in year/month/day format.
Result: The temporary directories are created, wherein the input files will be stored

and the cell swing tools will be run.


...................................................................................................................................................................................................

Change directory into the temporary directory just created.


Example: cd /home/swing/<yyyymmdd>
Result: The user is in the temporary directory.
...................................................................................................................................................................................................

Important! If the directory is already present, the tool will report that this is the
case. If there are problems creating the directory, or if a file (instead of directory)
is already present, errors will print.
When creating the input files, use the exact syntax for the attributes. Capital letters
need to be used where specified.
Create the cell_file, sn_file, and network_file input files in the temporary directory
created in Main Procedure Step 6 on the Source OMP. For file formatting instructions,
refer to cell_file file (p. 3-12), sn_file file (p. 3-13) , and network_file file
(p. 3-15) .
Result: The user creates the input files to be used by the cell swing tools.
...................................................................................................................................................................................................

Important! Cell swing template files may be found in $cstempsafter the BP


environment is enabled for the root user.
The temporary directory from Step 6 is now defined as $bpPath.
Enable the BP tools environment.
Example:

1. exec /usr/bin/ksh
2. . BP_user_setup
3. Enter: Y

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-32

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a 1xEV-DO cell (intra-RNC)

Result: The BP tools environment is enabled.


...................................................................................................................................................................................................

10

On the OMP in the temporary directory,


Enter: evdodump -d evdo_dumpdir -i cell_file
Where:
evdo_dumpdir

Top node of directory structure where BP


unloads data; Use $bpPath variable.

cell_file

user-created cell input file

-c

dumps tables for converged cells

-h

prints the evdoswing command usage


help message

Result: An explanation of what will be done is displayed and the user is prompted:
Are you ready to run 1xEV-DO Bulk-Provisioning commands via runBP
(y/n)?
...................................................................................................................................................................................................

11

At the prompt,
Enter: Y
Result: The evdodump tool continues running on the OMP.
...................................................................................................................................................................................................

12

When prompted for the Service Node OMP, enter s (for Source).
...................................................................................................................................................................................................

13

For EMS GUI Users: Enter the Service Node ID (SNID) for the OMP. If you do not

know the SNID, access the EMS GUI for the OMP, click the Configuration Data icon,
and click the Service Nodes link.
Important! Once the SNID is entered, the runBP tool is automatically entered and
may run for several minutes, depending on how many cells and Neighbor lists are
being dumped.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-33
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a 1xEV-DO cell (intra-RNC)

Result: The SNID for the OMP is displayed if needed and entered. The runBP tool

then automatically extracts the information needed from the Source system.
For OMC-RAN Users or BP Users: Enter the Service Node ID (SNID) for the

OMP. If you do not know the SNID, setup your Bulk Provisioning environment
and then execute the following command:
Enter: runBP -C output stored ServiceNode | grep hdrsnId
...................................................................................................................................................................................................

14

If the cell to be moved has Neighbors on other RNCs or different SNs, log into the
Neighbor OMP(s) and enter Step 6 - Step 12 (run evdodump for those systems,
specifying the appropriate SN type (n for Neighbor) in Main Procedure Step 12 .
Result: The evdodump tool is run for all Neighboring OMPs for which a handoff

can occur.
...................................................................................................................................................................................................

15

Transfer the files generated for the Neighbor OMPs to the temporary directory (created
in Step 6) on the Source OMP via sftp.
Important! If you cannot sftp as the root user, use the omptech login and put
the files in /tmp. Go back to the Source OMP and copy the transferred files from
/tmp to $bpPath
...................................................................................................................................................................................................

16

At the prompt,
Enter: evdoswing -d evdo_dumpdir -i cell_file -s sn_file [-v]
Where:
evdo_dumpdir

Top node of directory structure where BP


unloads data; Use $bpPath variable.

cell_file

user-created network input file

sn_file

user-created service node file

-v

prints further details of evdoswing


process (optional)

Result: The evdoswing script files for deleting and adding the cell components are

created, along with the replace scripts for updating the Neighbor sectors on other
RNCs/SNs.
...................................................................................................................................................................................................

17

Skip to Step 27 if no networking changes are being made. Otherwise, run the
evdomkdir tool.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-34

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a 1xEV-DO cell (intra-RNC)

Example: evdomkdir -d evdo_dumpdir -i network_file -s sn_file


Result: A directory structure is created to be used when transferring the network

files.
...................................................................................................................................................................................................

18

On the OMP, go to the Source SNID/Frame ID directory that was created by


evdomkdir.
Example:
cd $bpPath/sXXX/fYY

Where:
XXX
YY

= three-digit value for the Service Node ID

= two-digit value for the Frame ID

Result: A directory structure to be used when transferring the network files is

created.
...................................................................................................................................................................................................

19

In RRL off mode start a sftp to AP01 as onexev.


In RRL on mode start a sftp to AP01 as login user.
...................................................................................................................................................................................................

20

Go to the dhcp directory and get a copy of the SUNWfiles1_dhcptab file.


Example:

1. cd /var/dhcp
2. get SUNWfiles1_dhcptab
Result: Copy of the SUNWfiles1_dhcptab file is obtained.
...................................................................................................................................................................................................

21

Go to the /etc directory and get a copy of the netmasks file.


Example:

1. cd /etc
2. get netmasks
Result: Copy of the Source netmasks file is obtained.
...................................................................................................................................................................................................

22

Exit sftp by entering bye or quit and pressing the Enter key.
...................................................................................................................................................................................................

23

At the prompt,

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-35
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a 1xEV-DO cell (intra-RNC)

Enter: cd $bpPath
...................................................................................................................................................................................................

24

At the prompt,
Enter: evdonetwork -n evdo_dumpdir -i network_file -s sn_file
Where:
evdo_dumpdir

Top node of directory structure where BP


unloads data; Use $bpPath variable.

network_file

user-created network input file

sn_file

user-created service node file

Result: The evdonetwork script files for deleting, creating, and adding the network

components are created.


...................................................................................................................................................................................................

25

Important! Add scripts using either put or mput commands.


Transfer the network addition, creation, and deletion scripts (T1, dhcp, netmasks) to the
first two FMS-APs in the cluster and make them executable.
Where:
XXX
YY

= three-digit value for the Service Node ID

= two-digit value for the Frame ID

In RRL off mode:

1. cd $bpPath/sXXX/fYY
2. Start an sftp to AP01 as onexev
3. cd /app2/swing/<yyyymmdd>/scripts
4. Transfer the scripts using sftp
5. Exit sftp by entering bye or quit; press the Enter key
6. Repeat Substeps 2 - 5 for AP02, but enter n for the files that begin with netmsk,
as these files are not needed on AP02
7. cd $bpPath
In RRL on mode:

1. cd $bpPath/sXXX/fYY
2. Start an sftp to AP01 as login user account
3. cd /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts
4. Transfer the scripts using sftp
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-36

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a 1xEV-DO cell (intra-RNC)

5. Exit sftp by entering bye or quit; press the Enter key


6. Repeat Substeps 2 - 5 for AP02, but enter n for the files that begin with netmsk,
as these files are not needed on AP02
7. cd $bpPath
Result: The network deletion scripts are transferred to the first two FMS-APs in

the cluster.
...................................................................................................................................................................................................

26

Change permissions on the script files.


In RRL off mode:

1. Log on to AP01 as onexev


2. cd /app2/swing/<yyyymmdd>/scripts
3. chmod +x *
4. Log off of AP01
5. Repeat Substeps 1 - 4 for AP02
In RRL on mode:

1. Log on to AP01 as login user


2. cd /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts
3. chmod +x *
4. Log off of AP01
5. Repeat Substeps 1 - 4 for AP02
Result: The network addition and deletion scripts are made executable.
...................................................................................................................................................................................................

27

Important! If you cannot sftp as the root user, use the omptech and put the files
in /tmp. Go back to the Source OMP and copy the transferred files from /tmp to
$bpPath.
If they were generated, transfer the Neighbor sector replacement scripts via sftp from
the temporary directory on the Source OMP to the temporary directory created on the
Neighboring OMPs where evdodump was run.
Sample filename: NeighborSectorXXXYYReplace<BPfile#>
Where: XXX = three-digit value for the Service Node ID
YY

= two-digit value for the Frame ID

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-37
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a 1xEV-DO cell (intra-RNC)

Result: The scripts used to update the Neighbor sectors on Neighboring RNCs/SNs

are transferred.
...................................................................................................................................................................................................

28

Important! If the -V is omitted, the script will be executed.


Do not proceed if any script execution reports an error or is not OK!
Run each script individually in validate mode (-V) to confirm syntax.
Example: runBP -i -O /omp-data/logs/evdotools/runBPmmddyyyy.log -A V scriptname
Where:
scriptname

is in the format

<element><SNID><FMSID>Add<BPfile#>
<element><SNID><FMSID>Delete<BPfile#>
<element><SNID><FMSID>Replace<BPfile#>
NeighborSector<SNID><FMSID>Replace<BPfile#>

(run on Neighboring OMPs)

...................................................................................................................................................................................................

29

Take only the EVDO CDMs unconditionally out of service (OOS) to divert call traffic.
Repeat this Step for all the CDMs in a multicarrier cell.
Example:
TICLI> rmv:cell #, cdm <CDM ID>, crc; ucl
Result: The EVDO CDM is OOS and call traffic diverted.
...................................................................................................................................................................................................

30

Important! Do not proceed if any script execution reports an error or is not OK!
Run the BP Delete scripts, found in the /home/swing/<yyyymmd> directory, in normal
mode (without the -V command line parameter) in degrowth order on the Source OMP
for the cell components.
Refer to the Degrowth Table, Forms and key fields (p. 3-11) for the degrowth order
on the Source OMP for the cell components. For more information on BP, see
CDMA2000 1xEV-DO EMS Configuration Management Bulk Provisioning,
401-614-325.
Example:
runBP -i -O /omp-data/logs/evdotools/runBPmmddyyyy.log -A <element>
<SNID><FMSID>Delete<BPfile#>

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-38

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a 1xEV-DO cell (intra-RNC)

Result: The cell is deleted from the database of the Source RNC.
...................................................................................................................................................................................................

31

If no network changes were made, skip to Step 33 . Otherwise, run the deletion scripts
as root on the first two DO-RNC-APs.
Where:
XXX
YY

= three-digit value for the Service Node ID

= two-digit value for the Frame ID

In RRL off mode:

1. Log on to AP01 as onexev and become the root user (su - root)
2. cd /app2/swing/<yyyymmdd>/scripts
3. Run the t1 deletion script ./t1fileDelXXXYY
4. Run the dhcp deletion script ./dhcpDelXXXYY
5. Repeat Substeps 1 - 4 for AP02
6. Log off of AP02
7. Log on to AP01 as root and run the netmasks deletion script:
/flx/ONEXEVc/current/release/tools/cfg/modifyNetmasks DELETE < /app2/
swing/<yyyymmdd>/scripts/netmskDelXXXYY

8. Stop and restart DHCP on AP01 (as root):


/etc/init.d/dhcp stop
/etc/init.d/dhcp start

9. Log off of AP01.


10. Log on to AP02 and repeat Substep 8.
11. Log off of AP02 and log back onto the OMP as root.
In RRL on mode:

1. Log on to AP01 as login user and assume rsysadm role


2. cd /flx/ONEXEVc/current/release/tools/cfg
3. Run the t1 deletion script
./bpproxy /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/t1fileDel
XXXYY

4. Run the dhcp deletion script


./bpproxy /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/dhcpDel
XXXYY

5. Repeat Substeps 1 - 4 for AP02


6. Log off of AP02
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-39
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a 1xEV-DO cell (intra-RNC)

7. Log on to AP01 as login user and assume rsysadm and run the netmasks
deletion script:
/flx/ONEXEVc/current/release/tools/cfg/modifyNetmasks DELETE < /
<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/netmskDelXXXYY

8. Stop and restart DHCP on AP01:


/etc/init.d/dhcp stop
/etc/init.d/dhcp start

9. Log off of AP01.


10. Log on to AP02, assume rsysadm role and repeat Substep 8.
11. Log off of AP02 and log back onto the OMP as root.
Result: The network entries for the cell being moved are deleted from the Source

RNC.
...................................................................................................................................................................................................

32

Make any applicable network changes to support the cell swing (for example,
(multiple) router changes between the cell and the Source/Target FMS-APs).
...................................................................................................................................................................................................

33

Important! Do not proceed if any script execution reports an error or is not OK!
On the OMP, run the BP Add scripts (not in validate mode...remove the -V command
line parameter) in growth order on the Target OMP for the cell components.
Refer to the Growth Table, Forms and key fields (p. 3-11) for the growth order on
the Target OMP for the cell components. For more information on BP, see CDMA
2000 1xEV-DO EMS Configuration Management Bulk Provisioning, 401-614-325.
Example:
runBP -i -O /omp-data/logs/evdotools/runBPmmddyyyy.log -A <element>
<SNID><FMSID>Add<BPfile#>

Result: The cell is added back into the database.


...................................................................................................................................................................................................

34

If no network changes were made, skip to the next Step. Otherwise,run the network
addition and creation scripts as root on the first two FMS-APs.
Where:
XXX
YY

= three-digit value for the Service Node ID

= two-digit value for the Frame ID

In RRL off mode:

1. Log on to AP01 as onexev and become the root user (su - root)
2. cd /app2/swing/<yyyymmdd>/scripts
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-40

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a 1xEV-DO cell (intra-RNC)

3. Run the netmasks addition script


/flx/ONEXEVc/current/release/tools/cfg/modifyNetmasks ADD < /app2/
swing/<yyyymmdd>/scripts/netmskAddXXXYY

4. Run the dhcp addition script ./dhcpAddXXXYY


5. Run the t1 creation script ./t1fileCrtXXXXYY
6. Run the t1 addition script ./t1entryAddXXXYY
7. Repeat Substeps 1 - 2 and 4 - 6 for AP02
8. Log off of AP02
9. Stop and restart DHCP on AP01 (as root):
/etc/init.d/dhcp stop
/etc/init.d/dhcp start

10. Log off of AP01.


11. Log on to AP02 and repeat Substep 9
12. Log off of AP02 and log back onto the OMP as root
In RRL on mode:

1. Log on to AP01 as user account and assume rsysadm role


2. cd /flx/ONEXEVc/current/release/tools/cfg
3. Run the netmasks addition script
/flx/ONEXEVc/current/release/tools/cfg/modifyNetmasks ADD < /<home_
DIR>/<login_ID>/swing/<yyyymmdd>/scripts/netmskAddXXXYY

4. Run the dhcp addition script


./bpproxy <home_DIR>/<login_ID>/<yyyymmdd>/scripts/dhcpAddXXXYY

5. Run the t1 creation script


./bpproxy <home_DIR>/<login_ID>/<yyyymmdd>/scripts/t1fileCrtXXXYY

6. Run the t1 addition script


./bpproxy <home_DIR>/<login_ID>/<yyyymmdd>/scripts/t1entryAddXXXYY

7. Repeat Substeps 1 - 2 and 4 - 6 for AP02


8. Log off of AP02
9. Stop and restart DHCP on AP01:
/etc/init.d/dhcp stop
/etc/init.d/dhcp start

10. Log off of AP01.


11. Log on to AP02, assume rsysadm role and repeat Substep 9
12. Log off of AP02 and log back onto the OMP as root

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-41
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a 1xEV-DO cell (intra-RNC)

Result: The network entries for the cell being moved are deleted from the Source

RNC.
...................................................................................................................................................................................................

35

If they were generated, run the BP Neighbor Sector Replace scripts on all of the
Neighboring OMPs to update the Neighbor sectors on the Neighbor FMS-APs.
Example:
runBP -i -O /omp-data/logs/evdotools/runBPmmddyyyy.log -A

NeighborSectorXXXYYReplace<BPfile#>
Where:

NeighborSectorXXXYYReplace<BPfile#> contains:
XXX
YY

= three-digit value for the Service Node ID

= two-digit value for the Frame ID

Result: The Neighbor sectors on the Neighboring SNs/OMPs are updated for the
cell that has been moved.
...................................................................................................................................................................................................

36

Restore the CDM from the TICLI. Restore each of the CDMs in case of a multi-carrier
cell.
Example:
TICLI> rst:cell #, cdm <CDM ID>, crc; ucl
...................................................................................................................................................................................................

37

Wait for the cell to come up on the new FMS-AP pair. Monitor the cell status from
whichever interface is appropriate: EMS GUI if the RNC is EMS managed, or the
OMC-RAN GUI if the RNC is managed by the OMC-RAN.
Important! The cell may take up to 30 minutes to come up, as the cell has to
come up either on a new system, with a new name, or both. If the cell does not
come up after 30 minutes, contact WTSC for further assistance.
...................................................................................................................................................................................................

38

Enter the Verify OA&M on moved and/or renamed converged cell (p. 3-129)
procedure.
...................................................................................................................................................................................................

39

Verify successful cell move by placing a call on the new cell. Start a continuous ping
to a good system, and perform handoffs across the faces of the cell.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-42

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a 1xEV-DO cell (intra-RNC)

Result: A call is placed and intra-cell handoffs are completed.


...................................................................................................................................................................................................

40

If a Neighbor cell is available, start a new session on the moved cell and perform three
active handoffs between the moved cell and a Neighbor cell.
Result: Handoffs between the moved cell and the Neighbor cell are done.
...................................................................................................................................................................................................

41

After 5 days of verified stability, enter the Cleanup of old Cell Swing files (p. 3-134)
procedure.
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-43
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move
a 1xEV-DO cell (inter-RNC/Same Service Node)
...................................................................................................................................................................................................................................
Purpose

This procedure moves a 1xEV-DO cell from an FMS-AP pair on one RNC to another
FMS-AP pair on another RNC (inter-RNC move). Source and Target OMPs may be
different (inter-SN).
Important! Mixed-mode EV-DO cells, that is, CDMA cells with EV-DO cells in
the same cell, may be moved by executing both the Inter-MSC Swing tools for the
CDMA cells (see Inter-MSC Cell Swing, , 401-612-150) and the EV-DO Cell
Swing tools for the EV-DO cells.
Important! Before performing an EVDO cell swing, contact the Security
Administrator to ensure that security settings for the cell site EVDO CDMs are
properly set before the swing occurs.
Required skills and personnel

This procedure is best performed by an expert system administrator.


Related documentation

For detailed information on Inter-MSC Cell Swing, see Inter-MSC Cell Swing,
401-612-150.
For detailed information regarding 1xEV-DO Bulk Provisioning, see CDMA2000
1xEV-DO EMS Configuration Management Bulk Provisioning Guide, 401-614-325.
Prerequisites

To use the 1xEV-DO cell swing tools, you must have the following:

root

login access on the Operations & Maintenance Platform (OMP)


In RRL on mode, you need to be a system administrator or you have to have the
user account access that is assigned the rsysadm system administrator role.
1xEV-DO Cell Swing feature activated.

To use the Bulk Provisioning tool, you must have the following:

Access to the OMP shell


Appropriate permissions

Important

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-44

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a 1xEV-DO cell (inter-RNC/Same Service Node)

For information on setting up a login on the OMP, see Alcatel-Lucent 9271 EV-DO
Radio Network Controller, 401-614-102.

In addition, certain EMS provisioning steps must be completed before attempting to


use the Bulk Provisioning tool:
The Service Node and Frame must already be known to EMS by having
completed the AP Configuration process. (See the CDMA2000 1xEV-DO
Radio Access System Planning and Implementation Guide, 401-614-101).
The Configuration Database must be installed and operational (see the
CDMA2000 1xEV-DO Radio Access System Planning and Implementation
Guide, 401-614-101).
Data supplied to the configuration database should meet the known parameter
configuration guidelines. (See the CDMA2000 1xEV-DO Configurations
Parameters Guide, 401-614-324).
Ensure that all systems are stable before attempting an actual cell move.

Procedure

Important! Per the impact of 1xEV-DO Gold BCMCS (FID 10862.5) feature the
BCMCS carrier activation must be deactivated before attempting a cell swing. If
not the cell swing will be aborted and the or the result will be an aborted and the
Source RNC Database must be restored.
Perform the following steps:
...................................................................................................................................................................................................

Log on to the Source OMP as root.


Important! For an Inter-RNC Cell Swing, the DO-RNCs need to have the same
load.
...................................................................................................................................................................................................

In the RRL off mode, log on to the database FMS-AP of the Source OMP and make a
backup copy of the database as per standard procedures via dbunload. Run this
command in a new directory in the /app2 filesystem.
Important! /app2/DBbackup/swing<yyyymmdd>/ should be created and used as
the destination for the database backup.
For backup procedures, see Alcatel-Lucent 9271 EV-DO Radio Network Controller,
401-614-102.
In the RRL on mode, log on to the database FMS-AP with a user account and
assume rsysadm role. Choose a directory under
rsysadm home /roles/rsysadm/dbbackup.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-45
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a 1xEV-DO cell (inter-RNC/Same Service Node)

Important! If this directory does not exist, then it should be created:

mkdir p /roles/rsysadm/dbbackup
cd /roles/rsysadm/dbbackup
$HDRROOT/release/util/dbunload

...................................................................................................................................................................................................

Log off of the FMS-APs (returning to the OMP).


...................................................................................................................................................................................................

Back up the network files that may/will be modified on the lead FMS-APs.
In RRL off mode:

1. Log on to AP01 as onexev


2. mkdir -p /app2/swing/<yyyymmdd>/scripts
3. mkdir -p /app2/swing/<yyyymmdd>/backup
4. cd /app2/swing/<yyyymmdd>/backup
5. cp /etc/netmasks /app2/swing/<yyyymmdd>/backup
6. cp /var/dhcp/* /app2/swing/<yyyymmdd>/backup
7. Repeat Substeps 1 - 6 for AP02
8. Log off all FMS-APs
In RRL on mode:

1. Log on to AP01 as login account


2. mkdir -p /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts
3. mkdir -p /<home_DIR>/<login_ID>/swing/<yyyymmdd>/backup
4. cd /<home_DIR>/<login_ID>/swing/<yyyymmdd>/backup
5. cp /etc/netmasks /<home_DIR>/<login_ID>/<yyyymmdd>/backup
6. cp /var/dhcp/* /<home_DIR>/<login_ID>/swing/<yyyymmdd>/backup
7. Repeat Substeps 1 - 6 for AP02
8. Log off all FMS-APs
Result: Temporary directories for the scripts and for saving a backup copy of the

network files are created. Backup copies of the /etc/netmasks files and of the entire
/var/dhcp/* directory are made. Note that the scripts directory will be used later.
...................................................................................................................................................................................................

Repeat Main Procedure Step 2 - Step 4 for the Target DO-RNC.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-46

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a 1xEV-DO cell (inter-RNC/Same Service Node)

...................................................................................................................................................................................................

Repeat Main Procedure Step 1 - Step 3 for the Neighboring OMPs (SNs) with
DO-RNCs.
...................................................................................................................................................................................................

Through TICLI, obtain list of active generics on the cells being moved.
Example:
TICLI
TICLI> op:cell #,generic
TICLI> quit
Result: A list of active generics on the cells are displayed and sent to the ROP and
the TICLI session is terminated.
...................................................................................................................................................................................................

Confirm Target RNCs cell generic:


1. Log on to the Target FMS-AP
2. cd /flx/ONEXEVc/versions
3. ls -d cell_generic
Where: cell_generic is the name of the active generic obtained from the
op:bts #,generic

command entered in Main Procedure Step 7

4. If generic is the same as the Source OMP, then this sub-procedure is complete.
Go to Step 9.
If the result is: cell_generic: No such file or directory then install the
same generic as is found on the Source OMP on the Target OMPs system. See
Section 8, of Alcatel-Lucent 9271 EV-DO Radio Network Controller, 401-614-102,
for cell generic installation procedures.
...................................................................................................................................................................................................

On the Source OMP, make a temporary directory where the necessary input and output
files for this procedure will be stored.
Example: mkdir -p /home/swing/<yyyymmdd>
Where: <yyyymmdd> is the date in year/month/day format.
Result: The temporary directories are created, wherein the input files will be stored

and the cell swing tools will be run.


...................................................................................................................................................................................................

10

Change directory into the temporary directory just created.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-47
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a 1xEV-DO cell (inter-RNC/Same Service Node)

Example: cd /home/swing/<yyyymmdd>
Result: The user is in the temporary directory.
...................................................................................................................................................................................................

11

Create the cell_file, sn_file, and network_file input files in the temporary directory
created in Main Procedure Step 9 on the Source OMP. For file formatting instruction,
refer to cell_file file (p. 3-12), sn_file file (p. 3-13), and network_file file
(p. 3-15).
Important! If the directory is already present, the tool will report that this is the
case. If there are problems creating the directory, or if a file (instead of directory)
is already present, errors will print.
Result: The user creates the input files to be used by the cell swing tools
...................................................................................................................................................................................................

12

Important! The BP tool requires ksh (Korn Shell) to be running.


Cell swing template files may be found in $cstemps after the BP environment is
enabled for the root user.
The temporary directory from Step 9 is now defined as $bpPath.
Enable the BP tools environment.
Example:

1. exec /usr/bin/ksh
2. . BP_user_setup
3. Enter: Y
Result: The BP tools environment is enabled.
...................................................................................................................................................................................................

13

In the temporary directory,


Example: evdodump -d evdo_dumpdir -i cell_file
Where:
evdo_dumpdir

Top node of directory structure where BP


unloads data; Use $bpPath variable.

cell_file

user-created cell input file

-c

dumps tables for converged cells

-h

prints the evdoswing command usage


help message

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-48

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a 1xEV-DO cell (inter-RNC/Same Service Node)

Result: An explanation of what will be done is displayed and the user is prompted:
Are you ready to run 1xEV-DO Bulk-Provisioning commands via runBP
(y/n)?
...................................................................................................................................................................................................

14

At the prompt,
Enter: Y
Result: The evdodump tool continues running on the OMP.
...................................................................................................................................................................................................

15

When prompted, enter s (for Source).


...................................................................................................................................................................................................

16

For EMS GUI Users: Enter the Service Node ID (SNID) for the OMP. If you do not

know the SNID, access the EMS GUI for the OMP, click the Configuration Data icon,
and click the Service Nodes link.
Important! Once the SNID is entered, the runBP tool is automatically entered and
may run for several minutes, depending on how many cells and Neighbor lists are
being dumped.
Result: The SNID for the OMP is displayed if needed and entered. The runBP tool
then automatically extracts the information needed from the Source system.
For OMC-RAN Users or BP Users: Enter the Service Node ID (SNID) for the
OMP. If you do not know the SNID, setup your Bulk Provisioning environment
and then execute the following command:
Enter: runBP -C output stored ServiceNode | grep hdrsnId
...................................................................................................................................................................................................

17

At the prompt,
Enter: Y
Result: The evdodump tool continues running on the OMP.
...................................................................................................................................................................................................

18

When prompted for the Service Node OMP, enter t (for Target)
...................................................................................................................................................................................................

19

If the cell to be moved has Neighbors on other RNCs or different SNs, log into the
Neighbor OMP(s) and enter Main Procedure Step 9-Step 16 (run evdodump for those
systems, specifying the appropriate SN type (n for Neighbor) in Step 15.
Important! If no Neighbors, skip to Step 21.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-49
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a 1xEV-DO cell (inter-RNC/Same Service Node)

Result: The evdodump tool is run for all Neighboring OMPs for which a handoff

can occur.
...................................................................................................................................................................................................

20

Transfer the files generated for the Neighbor OMPs to the temporary directory (created
in Main Procedure Step 9) on the Source OMP via sftp.
Important! If you cannot sftp as the root user, use the omptech login and put the
files in /tmp. Go back to the Source OMP and copy the transferred files from /tmp
to $bpPath.
...................................................................................................................................................................................................

21

Enter:
evdoswing -d evdo_dumpdir -i cell_file -s sn_file [-v]

Where:
evdo_dumpdir

Top node of directory structure where BP


unloads data; Use $bpPath variable.

cell_file

user-created cell input file

sn_file

user-created service node file

-v

prints further details of evdoswing


process (optional)

Result: The evdoswing script files for deleting and adding the cell components are

created, along with the replace scripts for updating the Neighbor sectors on other
RNCs/SNs.
...................................................................................................................................................................................................

22

Run the evdomkdir tool.


Example:
evdomkdir -d evdo_dumpdir -i network_file -s sn_file

Where:
evdo_dumpdir

Top node of directory structure where BP


unloads data; Use $bpPath variable.

network_file

user-created network input file

sn_file

user-created service node file

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-50

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a 1xEV-DO cell (inter-RNC/Same Service Node)

Result: A directory structure is created to be used when transferring the network

files.
...................................................................................................................................................................................................

23

On the OMP, go to the Source SNID/Frame ID directory that was created by


evdomkdir.
Example:
cd $bpPath/sXXX/fYY

Where: XXX = three-digit value for the Service Node ID


YY

= two-digit value for the Frame ID

Result: A directory structure to be used when transferring the network files is

created.
...................................................................................................................................................................................................

24

In RRL off mode start a sftp to AP01 as onexev.


In RRL on mode start a sftp to AP01 a user account.
...................................................................................................................................................................................................

25

Go to the dhcp directory and get a copy of the SUNWfiles1_dhcptab file.


Example:

1. cd /var/dhcp
2. get SUNWfiles1_dhcptab
Result: Copy of the SUNWfiles1_dhcptab file is obtained.
...................................................................................................................................................................................................

26

Go to the /etc directory and get a copy of the netmasks file.


Example:

1. cd /etc
2. get netmasks
Result: Copy of netmasks file is obtained.
...................................................................................................................................................................................................

27

Exit sftp by entering bye or quit and pressing the Enter key.
...................................................................................................................................................................................................

28

Repeat Main Procedures Step 23 and Step 27 for the Target RNC, replacing all
occurrences of Source with Target.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-51
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a 1xEV-DO cell (inter-RNC/Same Service Node)

...................................................................................................................................................................................................

29

At the prompt,
Enter: cd $bpPath
...................................................................................................................................................................................................

30

At the prompt,
Enter:
evdonetwork -n evdo_dumpdir -i network_file -s sn_file

Where:
evdo_dumpdir

Top node of directory structure where BP


unloads data; Use $bpPath variable.

network_file

user-created network input file

sn_file

user-created service node file

Result: The evdonetwork script files for deleting, creating, and adding the network

components are created.


...................................................................................................................................................................................................

31

Important! Add scripts using either put or mput commands.


Transfer the network deletion scripts (T1, dhcp, netmasks) to the first two FMS-APs of
the Source system.
Where:
XXX
YY

= three-digit value for the Service Node ID

= two-digit value for the Frame ID

Example:

1. cd $bpPath/sXXX/fYY
2. Start an sftp to AP01 as onexev
3. cd /app2/swing/<yyyymmdd>/scripts
4. Transfer the scripts using sftp
5. Exit sftp by entering bye or quit; press the Enter key
6. Repeat Substeps 2 - 5 for AP02, but enter n for the files that begin with netmsk,
as these files are not needed on AP02
7. cd $bpPath

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-52

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a 1xEV-DO cell (inter-RNC/Same Service Node)

Result: The network deletion scripts are transferred to the first two FMS-APs in

the cluster.
...................................................................................................................................................................................................

32

Transfer the network addition and creation scripts (T1, dhcp, netmasks) to the first two
FMS-APs of the Target system.
Important! If the Target RNC is on a different OMP, the creation and addition
scripts will have to be transferred to the $bpPath directory of the Target OMP.
After that, they can then be transferred to the first two FMS-APs of the Target
system.
Add scripts using either put or mput commands.
Where:
XXX
YY

= three-digit value for the Service Node ID

= two-digit value for the Frame ID

In RRL off mode:

1. cd $bpPath/sXXX/fYY
2. Start an sftp to AP01 as onexev
3. cd /app2/swing/<yyyymmdd>/scripts
4. Transfer the scripts using sftp
5. Exit sftp by entering bye or quit; press the Enter key
6. Repeat Substeps 2 - 5 for AP02, but enter n for the files that begin with netmsk,
as these files are not needed on AP02
7. cd $bpPath
In RRL on mode:

1. cd $bpPath/sXXX/fYY
2. Start an sftp to AP01 as login user account
3. cd /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts
4. Transfer the scripts using sftp
5. Exit sftp by entering bye or quit; press the Enter key
6. Repeat Substeps 2 - 5 for AP02, but enter n for the files that begin with netmsk,
as these files are not needed on AP02
7. cd $bpPath
Result: The network deletion scripts are transferred to the first two FMS-APs in

the cluster.
...................................................................................................................................................................................................

33

Change permissions on the script files (transferred in Step 31 for the Source RNC).

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-53
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a 1xEV-DO cell (inter-RNC/Same Service Node)

In RRL off mode:

1. Log on to AP01 as onexev


2. cd /app2/swing/<yyyymmdd>/scripts
3. chmod +x *
4. Log off of AP01
5. Repeat Substeps 1 - 4 for AP02
In RRL on mode:

1. Log on to AP01 as login user


2. cd /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts
3. chmod +x *
4. Log off of AP01
5. Repeat Substeps 1 - 4 for AP02
Result: The network deletion scripts are made executable.
...................................................................................................................................................................................................

34

Change permissions on the script files (transferred in Step 32 for the Target RNC).
Example:

1. Log on to AP01 as onexev


2. cd /app2/swing/<yyyymmdd>/scripts
3. chmod +x *
4. Log off of AP01
5. Repeat Substeps 1 - 4 for AP02
Result: The network deletion scripts are made executable.
...................................................................................................................................................................................................

35

Important! If you cannot sftp as the root user, use the omptech login and put the
files in /tmp. Go back to the Source OMP and copy the transferred files from /tmp
to $bpPath.
If they were generated, transfer the Neighbor sector replacement scripts via sftp from
the temporary directory on the Source OMP to the temporary directory created on the
Neighboring OMPs where evdodump was run.
Sample filename: NeighborSectorXXXYYReplace<BPfile#>
Where: XXX = three-digit value for the Service Node ID
YY

= two-digit value for the Frame ID

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-54

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a 1xEV-DO cell (inter-RNC/Same Service Node)

Result: The scripts used to update the Neighbor sectors on Neighboring RNCs/SNs

are transferred.
...................................................................................................................................................................................................

36

Important! If the -V is omitted, the script will be executed.


Do not proceed if any script execution reports an error or is not OK!
Run each script individually in validate mode (-V) to confirm syntax.
Example:
runBP -i -O /omp-data/logs/evdotools/runBPmmddyyyy.log -A -V
scriptname

Where:
scriptname

is in the format

<element><SNID><FMSID>Add<BPfile#>
<element><SNID><FMSID>Delete<BPfile#>
<element><SNID><FMSID>Replace<BPfile#>
NeighborSector<SNID><FMSID>Replace<BPfile#>

(run on Neighboring OMPs)

...................................................................................................................................................................................................

37

Take the 1xEV-DO CDMs unconditionally out of service (OOS) to divert call traffic.
Repeat this Step for all the CDMs in a multicarrier cell.
Example:
TICLI> rmv:cell #, cdm <CDM ID>, crc; ucl
...................................................................................................................................................................................................

38

Important! Do not proceed if any script execution reports an error or is not OK!
Run the BP Delete scripts, found in the /home/swing/<yyyymmdd> directory, in normal
mode (without the -V command line parameter) in degrowth order on the Source OMP
for the cell components.
Refer to the Degrowth Table, Forms and key fields (p. 3-11) for the degrowth order
on the Source OMP for the cell components. For more information on BP, see
CDMA2000 1xEV-DO EMS Configuration Management Bulk Provisioning,
401-614-325.
Example:
runBP -i -O /omp-data/logs/evdotools/runBPmmddyyyy.log -A <element>
<SNID><FMSID>Delete<BPfile#>

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-55
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a 1xEV-DO cell (inter-RNC/Same Service Node)

Result: The cell is deleted from the database of the Source RNC.
...................................................................................................................................................................................................

39

Run the deletion scripts as root on the first two Source FMS-APs.
Where:
XXX
YY

= three-digit value for the Service Node ID

= two-digit value for the Frame ID

In RRL off mode:

1. Log on to AP01 as onexev and become the root user (su - root)
2. cd /app2/swing/<yyyymmdd>/scripts
3. Run the t1 deletion script ./t1fileDelXXXYY
4. Run the dhcp deletion script ./dhcpDelXXXYY
5. Repeat Substeps 1 - 4 for AP02
6. Log off of AP02
7. Log on to AP01 as root and run the netmasks deletion script:
/flx/ONEXEVc/current/release/tools/cfg/modifyNetmasks DELETE
</app2/swing/<yyyymmdd>/scripts/netmskDelXXXYY

8. Stop and restart DHCP on AP01 (as root):


/etc/init.d/dhcp stop
/etc/init.d/dhcp start

9. Log off of AP01.


10. Log on to AP02 and repeat Substep 8.
11. Log off of AP02 and log back onto the OMP as root.
In RRL on mode:

1. Log on to AP01 as login user and assume rsysadm role


2. cd /flx/ONEXEVc/current/release/tools/cfg
3. Run the t1 deletion script
./bpproxy /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/t1fileDel
XXXYY

4. Run the dhcp deletion script


./bpproxy /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/dhcpDel
XXXYY

5. Repeat Substeps 1 - 4 for AP02


6. Log off of AP02
7. Log on to AP01 as login user and assume rsysadm and run the netmasks
deletion script:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-56

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a 1xEV-DO cell (inter-RNC/Same Service Node)

/flx/ONEXEVc/current/release/tools/cfg/modifyNetmasks DELETE < /


<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/netmskDelXXXYY

8. Stop and restart DHCP on AP01:


/etc/init.d/dhcp stop
/etc/init.d/dhcp start

9. Log off of AP01.


10. Log on to AP02, assume rsysadm role and repeat Substep 8.
11. Log off of AP02 and log back onto the OMP as root.
Result: The network entries for the cell being moved are deleted from the Source

RNC.
...................................................................................................................................................................................................

40

Make any applicable network changes to support the cell swing (for example,
(multiple) router changes between the cell and the Source/Target FMS-APs).
...................................................................................................................................................................................................

41

Important! Do not proceed if any script execution reports an error or is not OK!
Run the BP Add scripts (not in validate mode, remove the -V command line parameter)
in growth order on the Target OMP for the cell components.
Refer to the Growth Table, Forms and key fields (p. 3-11) for the growth order on
the Target OMP for the cell components. For more information on BP, see CDMA
2000 1xEV-DO EMS Configuration Management Bulk Provisioning, 401-614-325.
Example:
runBP -i -O /omp-data/logs/evdotools/runBPmmddyyyy.log -A
<element><SNID><FMSID>Add<BPfile#>

Result: The cell is added into the database of the Target RNC.
...................................................................................................................................................................................................

42

Run the network addition and creation scripts as root on the first two Target
FMS-APs.
Where:
XXX
YY

= three-digit value for the Service Node ID

= two-digit value for the Frame ID

In RRL off mode:

1. Log on to AP01 as onexev and become the root user (su - root)
2. cd /app2/swing/<yyyymmdd>/scripts
3. Run the netmasks addition script:
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-57
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a 1xEV-DO cell (inter-RNC/Same Service Node)

/flx/ONEXEVc/current/release/tools/cfg/modifyNetmasks ADD < /app2/


swing/<yyyymmdd>/scripts/netmskAddXXXYY

4. Run the dhcp addition script ./dhcpAddXXXYY


5. Run the t1 creation script ./t1fileCrtXXXXYY
6. Run the t1 addition script ./t1entryAddXXXYY
7. Repeat Substeps 1 - 2 and 4 - 6 for AP02
8. Log off of AP02
9. Stop and restart DHCP on AP01 (as root):
/etc/init.d/dhcp stop
/etc/init.d/dhcp start

10. Log off of AP01.


11. Log on to AP02 and repeat Substep 9
12. Log off of AP02 and log back onto the OMP as root
In RRL on mode:

1. Log on to AP01 as user account and assume rsysadm role


2. cd /flx/ONEXEVc/current/release/tools/cfg
3. Run the netmasks addition script
/flx/ONEXEVc/current/release/tools/cfg/modifyNetmasks ADD < /<home_
DIR>/<login_ID>/swing/<yyyymmdd>/scripts/netmskAddXXXYY

4. Run the dhcp addition script


./bpproxy <home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/dhcpAddXXXYY

5. Run the t1 creation script


./bpproxy <home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/
t1fileCrtXXXYY

6. Run the t1 addition script


./bpproxy <home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/
t1entryAddXXXYY

7. Repeat Substeps 1 - 2 and 4 - 6 for AP02


8. Log off of AP02
9. Stop and restart DHCP on AP01:
/etc/init.d/dhcp stop
/etc/init.d/dhcp start

10. Log off of AP01.


11. Log on to AP02, assume rsysadm role and repeat Substep 9
12. Log off of AP02 and log back onto the OMP as root
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-58

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a 1xEV-DO cell (inter-RNC/Same Service Node)

Result: The network entries for the cell being moved are deleted from the Target

RNC.
...................................................................................................................................................................................................

43

If they were generated, run the BP Neighbor Sector Replace scripts on all of the
Neighboring OMPs to update the Neighbor sectors on the Neighbor FMS-APs.
Example:
runBP -i -O /omp-data/logs/evdotools/runBPmmddyyyy.log -A

NeighborSectorXXXYYReplace<BPfile#>
Where: NeighborSectorXXXYYReplace<BPfile#> contains:
XXX
YY

= three-digit value for the Service Node ID

= two-digit value for the Frame ID

Result: The Neighbor sectors on the Neighboring SNs/OMPs are updated for the

cell that has been moved.


...................................................................................................................................................................................................

44

Restore the CDM from theTICLI. Restore each of the CDMs in case of a multi-carrier
cell.
Example:
TICLI> rst:cell #, cdm <CDM ID>, crc; ucl
...................................................................................................................................................................................................

45

Wait for the cell to come up on the new FMS-AP pair. Monitor the cell status from
whichever interface is appropriate: EMS GUI if the RNC is EMS managed, or the
OMC-RAN GUI if the RNC is managed by the OMC-RAN.
Important! The cell may take up to 30 minutes to come up, as the cell has to
come up either on a new system, with a new name, or both. If the cell does not
come up after 30 minutes, contact WTSC for further assistance.
...................................................................................................................................................................................................

46

Enter the Verify OA&M on moved and/or renamed converged cell (p. 3-129)
procedure.
...................................................................................................................................................................................................

47

Verify successful cell move by placing a call on the new cell. Start a continuous ping
to a good system, and perform handoffs across the faces of the cell.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-59
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a 1xEV-DO cell (inter-RNC/Same Service Node)

Result: A call is placed and intra-cell handoffs are completed.


...................................................................................................................................................................................................

48

If a Neighbor cell is available, start a new session on the moved cell and perform three
active handoffs between the moved cell and a Neighbor cell.
Result: Handoffs between the moved cell and the Neighbor cell are done.
...................................................................................................................................................................................................

49

After 5 days of verified stability, enter the Cleanup of old Cell Swing files (p. 3-134)
procedure.
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-60

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a converged 1xEV-DO cell (inter-RNC/Different Service


Node)
...................................................................................................................................................................................................................................
Purpose

This procedure moves a converged 1xEV-DO Modular Cell from one FMS-AP pair to
another FMS-AP pair on a different service node RNC (inter-RNC).
Important! Mixed-mode EV-DO cells, that is, CDMA modular cells with EV-DO
cells in the same cell, may be moved by executing both the Inter-MSC Swing tools
for the CDMA cells (see 401-612-150, Inter-MSC Cell Swing) and the EV-DO Cell
Swing tools for the EV-DO cells.
Important! Before performing an EVDO cell swing, contact the Security
Administrator to ensure that security settings for the cell site EVDO CDMs are
properly set before the swing occurs.
Required skills and personnel

This procedure is best performed by an expert system administrator.


Related documentation

For detailed information on Inter-MSC Cell Swing, see Inter-MSC Cell Swing,
401-612-150.
For detailed information regarding 1xEV-DO Bulk Provisioning, see CDMA2000
1xEV-DO Network EMS Configuration Management Bulk Provisioning Guide,
401-614-325.
Prerequisites

To use the 1xEV-DO cell swing tools, you must have the following:

root

login access on the Operations & Maintenance Platform (OMP)


In RRL on mode, you need to be a system administrator or you have to have the
user account access that is assigned the rsysadm system administrator role.
1xEV-DO Cell Swing feature activated.

To use the Bulk Provisioning tool, you must have the following:

Access to the OMP shell


Appropriate permissions

Important

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-61
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a converged 1xEV-DO cell (inter-RNC/Different


Service Node)

For information on setting up a login on the OMP, see Alcatel-Lucent 9271 EV-DO
Radio Network Controller, 401-614-102.

In addition, certain EMS provisioning steps must be completed before attempting to


use the Bulk Provisioning tool:
The Service Node and Frame must already be known to EMS by having
completed the AP Configuration process. (See the CDMA2000 1xEV-DO
Radio Access System Planning and Implementation Guide, 401-614-101.
The Configuration Database must be installed and operational (see the
CDMA2000 1xEV-DO Radio Access System Planning and Implementation
Guide, 401-614-101.
Data supplied to the configuration database should meet the known parameter
configuration guidelines. (See the CDMA2000 1xEV-DO Network
Configurations Parameters Guide, 401-614-324).
Ensure that all systems are stable before attempting an actual cell move.

Procedure

Important! Per the impact of 1xEV-DO Gold BCMCS (FID 10862.5) feature the
BCMCS carrier activation must be deactivated before attempting a cell swing. If
not the cell swing will be aborted and the or the result will be an aborted and the
Source RNC Database must be restored.
Perform the following steps:
...................................................................................................................................................................................................

Log on to the Source OMP as root.


Important! For inter-RNC Cell Swing, the DO-RNCs need to have the same load.
RCS-APs (CDMA) also need to have the same load.
...................................................................................................................................................................................................

In the RRL off mode, log on to the database FMS-AP of the Source OMP and make a
backup copy of the database as per standard procedures via dbunload. Run this
command in a new directory in the /app2 filesystem.
Important! /app2/DBbackup/swing<yyyymmdd>/ should be created and used as
the destination for the database backup.
For backup procedures, see Alcatel-Lucent 9271 EV-DO Radio Network Controller,
401-614-102.
In the RRL on mode, log on to the database FMS-AP with a user account and
assume rsysadm role. Choose a directory under
rsysadm home /roles/rsysadm/dbbackup.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-62

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a converged 1xEV-DO cell (inter-RNC/Different


Service Node)

Important! If this directory does not exist, then it should be created:

mkdir p /roles/rsysadm/dbbackup
cd /roles/rsysadm/dbbackup
$HDRROOT/release/util/dbunload

...................................................................................................................................................................................................

Log off of the FMS-APs (returning to the OMP).


...................................................................................................................................................................................................

Back up the network files that may/will be modified on the lead FMS-APs.
In RRL off mode:

1. Log on to AP01 as onexev


2. mkdir -p /app2/swing/<yyyymmdd>/scripts
3. mkdir -p /app2/swing/<yyyymmdd>/backup
4. cd /app2/swing/<yyyymmdd>/backup
5. cp /etc/netmasks /app2/swing/<yyyymmdd>/backup
6. cp /var/dhcp/* /app2/swing/<yyyymmdd>/backup
7. Repeat Substeps 1 - 6 for AP02
8. Log off all FMS-APs
In RRL on mode:

1. Log on to AP01 as login account


2. mkdir -p /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts
3. mkdir -p /<home_DIR>/<login_ID>/swing/<yyyymmdd>/backup
4. cd /<home_DIR>/<login_ID>/<yyyymmdd>/backup
5. cp /etc/netmasks /<home_DIR>/<login_ID>/<yyyymmdd>/backup
6. cp /var/dhcp/* /<home_DIR>/<login_ID>/swing/<yyyymmdd>/backup
7. Repeat Substeps 1 - 6 for AP02
8. Log off all FMS-APs
Result: Temporary directories for the scripts and for saving a backup copy of the

network files are created. Backup copies of the /etc/netmasks files and of the entire
/var/dhcp/* directory are made. Note that the scripts directory will be used later.
...................................................................................................................................................................................................

Repeat Main Procedure Step 1 -Step 4 for the Target OMPs.


...................................................................................................................................................................................................

Repeat Main Procedure Step 1 - Step 3 for the Neighboring OMPs.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-63
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a converged 1xEV-DO cell (inter-RNC/Different


Service Node)

...................................................................................................................................................................................................

Through TICLI, obtain list of active generics on the cells being moved.
Example: TICLI
TICL> op:cell #,generic
TICLI> quit
Result: A list of active generics on the cells are displayed and sent to the ROP and
the TICLI session is terminated.
...................................................................................................................................................................................................

Confirm Target RNCs cell genericConfirm Target RNCs cell generic:


1. Log on to Target FMS-AP
2. cd /flx/ONEXEVcs/versions
3. ls -d cell_generic
Where: cell_generic is the name of the active generic obtained from the
op:cell #,generic

command entered in main procedure Step 7 .

4. If generic is the same as the Source OMP, then this sub-procedure is complete.
Go to Step 9.
If result is: cell_generic: No such file or directory then install the same
generic as is found on the Source OMP on the Target OMPs system. See Section
8, of Alcatel-Lucent 9271 EV-DO Radio Network Controller, 401-614-102, for cell
generic installation procedures.
...................................................................................................................................................................................................

On the Source OMP, make a temporary directory where the necessary input and output
files for this procedure will be stored.
Example: mkdir -p /home/swing/<yyyymmdd>
Where: <yyyymmdd> is the date in year/month/day format.
Result: The temporary directories are created, wherein the input files are stored
and the cell swing tools will be run.
...................................................................................................................................................................................................

10

Change directory into the temporary directory just created.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-64

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a converged 1xEV-DO cell (inter-RNC/Different


Service Node)

Example: cd /home/swing/<yyyymmdd>
Result: The user is in the temporary directory.
...................................................................................................................................................................................................

11

Important! If the directory is already present, the tool will report that this is the
case. If there are problems creating the directory, or if a file (instead of directory)
is already present, errors will print.
If this is the Target OMP, just copy the cell_file file from the Source OMP to the
Target OMP. Do not create any other files on the Target OMP.
Create the cell_file, sn_file, and network_file input files in the temporary directory
created in Main Procedure Step 9 on the Source OMP. For file formatting instructions,
refer to cell_file file (p. 3-12), sn_file file (p. 3-13), and network_file file
(p. 3-15).
Result: The user creates the input files to be used by the cell swing tools.
...................................................................................................................................................................................................

12

Important! The BP tool requires ksh (Korn Shell) to be running.


Cell swing template files may be found in $cstemps after the BP environment is
enabled for the root user.
The temporary directory from Step 9 is now defined as $bpPath
Enable the BP tools environment.
Example:

1. exec /usr/bin/ksh
2. . BP_user_setup
3. Enter: Y
Result: The BP tools environment is enabled.
...................................................................................................................................................................................................

13

Important! Parameter -c is not optional.


On the Source OMP, in the temporary directory,
Example: evdodump -d evdo_dumpdir -i cell_file
Where:
evdo_dumpdir

Top node of directory structure where BP


unloads data; Use $bpPath variable.

cell_file

user-created cell input file

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-65
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a converged 1xEV-DO cell (inter-RNC/Different


Service Node)

-c

dumps tables for converged cells

-h

prints the evdoswing command usage


help message

Result: An explanation of what will be done is displayed and the user is prompted:
Are you ready to run 1xEV-DO Bulk-Provisioning commands via runBP
(y/n)?
...................................................................................................................................................................................................

14

At the prompt,
Enter: Y
Result: The evdodump tool continues running on the OMP.
...................................................................................................................................................................................................

15

When prompted for the Service Node OMP, enter s (for Source), t (for Target), or
n (for Neighbor) as appropriate.
...................................................................................................................................................................................................

16

For EMS GUI Users: Enter the Service Node ID (SNID) for the OMP. If you do not
know the SNID, access the EMS GUI for the OMP, click the Configuration Data icon,
and click the Service Nodes link.

Important! Once the SNID is entered, the runBP tool is automatically entered and
may run for several minutes, depending on how many cells and Neighbor lists are
being dumped.
Result: The SNID for the OMP is displayed if needed and entered. The runBP tool

then automatically extracts the information needed from the Source system.
For OMC-RAN Users or BP Users: Enter the Service Node ID (SNID) for the

OMP. If you do not know the SNID, setup your Bulk Provisioning environment
and then execute the following command:
Enter: runBP -C output stored ServiceNode | grep hdrsnId
...................................................................................................................................................................................................

17

Repeat Main Procedure Step 9 - Step 16 on the Target OMP, then transfer the
following files back to the temporary directory created in Step 9 on the Source OMP:
Example: APXXX.txtNeighborSectorXXXYY.txt
Where: XXX = Target SN ID
YY

= Target Frame ID

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-66

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a converged 1xEV-DO cell (inter-RNC/Different


Service Node)

...................................................................................................................................................................................................

18

If the cell to be moved has Neighbors on other RNCs or different SNs, log into the
Neighbor OMP(s) and enter Main Procedure Step 9 - Step 16 (run evdodump for those
systems, specifying the appropriate SN type (n for Neighbor) in Main Procedure Step
15 .
Important! If no Neighbors, skip to Step Important!
Result: The evdodump tool is run for all Neighboring OMPs for which a handoff
can occur.
...................................................................................................................................................................................................

19

Transfer the files generated for the Neighbor OMPs to the temporary directory (created
in Main Procedure Step 9) on the Source OMP via sftp.
Important! If you cannot sftp as the root user, use the omptech login and put the
files in /tmp. Go back to the Source OMP and copy the transferred files from /tmp
to $bpPath.
...................................................................................................................................................................................................

20

On the Source OMP, enter:


evdoswing -d evdo_dumpdir -i cell_file -s sn_file [-v]

Where:
evdo_dumpdir

Top node of directory structure where BP


unloads data; Use $bpPath variable.

cell_file

user-created cell input file

sn_file

user-created service node file

-v

prints further details of evdoswing


process (optional)

Result: The evdoswing script files for deleting and adding the cell components are

created, along with the replace scripts for updating the Neighbor sectors on other
RNCs/SNs.
...................................................................................................................................................................................................

21

On the Source OMP, run the evdomkdir tool.


Example:
evdomkdir -d evdo_dumpdir -i network_file -s sn_file

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-67
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a converged 1xEV-DO cell (inter-RNC/Different


Service Node)

Where:
evdo_dumpdir

Top node of directory structure where BP


unloads data; Use $bpPath variable.

network_file

user-created network input file

sn_file

user-created service node file

Result: A directory structure is created to be used when transferring the network

files.
...................................................................................................................................................................................................

22

On the Source OMP, go to the Source SNID/Frame ID directory that was created by
evdomkdir

Example:
cd $bpPath/sXXX/fYY

Where:
XXX
YY

= three-digit value for the Service Node ID

= two-digit value for the Frame ID

Result: A directory structure to be used when transferring the network files is

created.
...................................................................................................................................................................................................

23

In RRL off mode start a sftp to AP01 as onexev.


In RRL on mode start a sftp to AP01 as login user.
...................................................................................................................................................................................................

24

Go to the dhcp directory and get a copy of the SUNWfiles1_dhcptab file.


Example:

1. cd /var/dhcp
2. get SUNWfiles1_dhcptab
Result: Copy of the SUNWfiles1_dhcptab file is obtained.
...................................................................................................................................................................................................

25

Go to the /etc directory and get a copy of the netmasks file.


Example:

1. cd /etc
2. get netmasks
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-68

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a converged 1xEV-DO cell (inter-RNC/Different


Service Node)

Result: Copy of the netmasks file is obtained.


...................................................................................................................................................................................................

26

Exit sftp by entering bye or quit and pressing the Enter key.
...................................................................................................................................................................................................

27

Repeat Main Procedure Step 22-Step 26 for the Target OMP, replacing all occurrences
of Source with Target.If the Target OMP is different, save the files on the Target OMP
in $bpPath directory and transfer the network files via sftp to the appropriate
directory ($bpPath/s<TargetSNID>/f<TargetFrameID>) on the Source OMP.
...................................................................................................................................................................................................

28

On the Source OMP,


Enter: cd $bpPath
...................................................................................................................................................................................................

29

On the Source OMP,


Example: evdonetwork -n evdo_dumpdir -i network_file -s sn_file
Where:
evdo_dumpdir

Top node of directory structure where BP


unloads data; Use $bpPath variable.

network_file

user-created network input file

sn_file

user-created service node file

Result: The evdonetwork script files for deleting, creating, and adding the network

components are created.


...................................................................................................................................................................................................

30

Important! Add scripts using either put or mput commands.


Transfer the network deletion scripts (T1, dhcp, netmasks) to the first two FMS-APs of
the Source system.
Where:
XXX
YY

= three-digit value for the Service Node ID

= two-digit value for the Frame ID

In RRL off mode:

1. cd $bpPath/sXXX/fYY
2. Start an sftp to AP01 as onexev
3. cd /app2/swing/<yyyymmdd>/scripts
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-69
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a converged 1xEV-DO cell (inter-RNC/Different


Service Node)

4. Transfer the scripts using sftp


5. Exit sftp by entering bye or quit; press the Enter key
6. Repeat Substeps 2 - 5 for AP02, but enter n for the files that begin with netmsk,
as these files are not needed on AP02
7. cd $bpPath
In RRL on mode:

1. cd $bpPath/sXXX/fYY
2. Start an sftp to AP01 as login user account
3. cd /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts
4. Transfer the scripts using sftp
5. Exit sftp by entering bye or quit; press the Enter key
6. Repeat Substeps 2 - 5 for AP02, but enter n for the files that begin with netmsk,
as these files are not needed on AP02
7. cd $bpPath
Result: The network deletion scripts are transferred to the first two FMS-APs in

the cluster.
...................................................................................................................................................................................................

31

Transfer the network addition and creation scripts (T1, dhcp, netmasks) to the first two
FMS-APs of the Target system.
Important! If the Target RNC is on a different OMP, the creation and addition
scripts will have to be transferred to the $bpPath directory of the Target OMP.
After that, they can then be transferred to the first two FMS-APs of the Target
system.
Add scripts using either put or mput commands.
Where:
XXX
YY

= three-digit value for the Service Node ID


= two-digit value for the Frame ID

In RRL off mode:

1. cd $bpPath/sXXX/fYY
2. Start an sftp to AP01 as onexev
3. cd /app2/swing/<yyyymmdd>/scripts
4. Transfer the scripts using sftp
5. Exit sftp by entering bye or quit; press the Enter key
6. Repeat Substeps 2 - 5 for AP02, but enter n for the files that begin with netmsk,
as these files are not needed on AP02
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-70

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a converged 1xEV-DO cell (inter-RNC/Different


Service Node)

7. cd $bpPath
In RRL on mode:

1. cd $bpPath/sXXX/fYY
2. Start an sftp to AP01 as onexev
3. cd /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts
4. Transfer the scripts using sftp
5. Exit sftp by entering bye or quit; press the Enter key
6. Repeat Substeps 2 - 5 for AP02, but enter n for the files that begin with netmsk,
as these files are not needed on AP02
7. cd $bpPath
Result: The network deletion scripts are transferred to the first two FMS-APs in

the cluster.
...................................................................................................................................................................................................

32

Change permissions on the script files for the Source RNC.


In RRL off mode:

1. Log on to AP01 as onexev


2. cd /app2/swing/<yyyymmdd>/scripts
3. chmod +x *
4. Log off of AP01
5. Repeat Substeps 1 - 4 for AP02
In RRL on mode:

1. Log on to AP01 as onexev


2. cd /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts
3. chmod +x *
4. Log off of AP01
5. Repeat Substeps 1 - 4 for AP02
Result: The network deletion scripts are made executable.
...................................................................................................................................................................................................

33

Change permissions on the script files for the Target RNC.


Example:

1. Log on to AP01 as onexev


2. cd /app2/swing/<yyyymmdd>/scripts
3. chmod +x *
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-71
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a converged 1xEV-DO cell (inter-RNC/Different


Service Node)

4. Log off of AP01


5. Repeat Substeps 1 - 4 for AP02
Result: The network deletion scripts are made executable.
...................................................................................................................................................................................................

34

Transfer the Add scripts to the Target OMP, /home/swing/<yyyymmdd>


...................................................................................................................................................................................................

35

Important! If you cannot sftp as the root user, use the omptech login and put the
files in /tmp. Go back to the Source OMP and copy the transferred files from /tmp
to $bpPath.
If they were generated, transfer the Neighbor sector replacement scripts via sftp from
the temporary directory on the Source OMP to the temporary directory created on the
Neighboring OMPs where evdodump was run.
Sample filename: NeighborSectorXXXYYReplace<BPfile#>
Where: XXX = three-digit value for the Service Node ID
YY

= two-digit value for the Frame ID

Result: The scripts used to update the Neighbor sectors on Neighboring RNCs/SNs
are transferred.
...................................................................................................................................................................................................

36

Important! If the -V is omitted, the script will be executed.


Do not proceed if any script execution reports an error or is not OK!
On the Source OMP, run the Delete scripts in validate (-V) mode to confirm syntax.
Example:
runBP -i -O /omp-data/logs/evdotools/runBPmmddyyyy.log -A -V
scriptname

Where:
scriptname

is in the format

<element><SNID><FMSID>Delete<BPfile#>
...................................................................................................................................................................................................

37

Important! If the -V is omitted, the script will be executed.


Do not proceed if any script execution reports an error or is not OK!
On the Target OMP, run the BP Add and Replace scripts in validate (-V) mode.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-72

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a converged 1xEV-DO cell (inter-RNC/Different


Service Node)

Example:
runBP -i -O /omp-data/logs/evdotools/runBPmmddyyyy.log -A -V
scriptname

Where:
scriptname

is in the format

<element><SNID><FMSID>Add<BPfile#>
<element><SNID><FMSID>Replace<BPfile#>
...................................................................................................................................................................................................

38

Important! If the -V is omitted, the script will be executed.


Do not proceed if any script execution reports an error or is not OK!
If they were generated, run the Neighbor OMP, run the NeighborSector Replace scripts
in validate (-V) mode, on the neighboring MOPs.
Example:
runBP -i -O /omp-data/logs/evdotools/runBPmmddyyyy.log -A -V

NeighborSectorXXXYYReplace<BPfile#>
Where:

NeighborSectorXXXYYReplace<BPfile#> contains:
XXX
YY

= three-digit value for the Service Node ID

= two-digit value for the Frame ID

...................................................................................................................................................................................................

39

Take the 1xEV-DO CDMs unconditionally out of service (OOS) to divert call traffic.
Repeat this Step for all the CDMs in a multicarrier cell.
Example:
TICLI> rmv:cell #, cdm <CDM ID>, crc; ucl
...................................................................................................................................................................................................

40

Important! Do not proceed if any script execution reports an error or is not OK!
On the Source OMP, run the BP Delete scripts, found in the /home/swing/<yyyymmdd>
directory, in normal mode (without the -V command line parameter) in degrowth order
on the Source OMP for the cell components.
Refer to the Degrowth Table, Forms and key fields (p. 3-11) for the degrowth order
on the Source OMP for the cell components. For more information on BP, see
CDMA2000 1xEV-DO EMS Configuration Management Bulk Provisioning,
401-614-325.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-73
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a converged 1xEV-DO cell (inter-RNC/Different


Service Node)

Example:
runBP -i -O /omp-data/logs/evdotools/runBPmmddyyyy.log -A
<element><SNID><FMSID>Delete<BPfile#>

Result: The cell is deleted from the database of the Source RNC.
...................................................................................................................................................................................................

41

On the Source OMP, run the deletion scripts as root on the first two Source
FMS-APs.
Where:
XXX
YY

= three-digit value for the Service Node ID

= two-digit value for the Frame ID

In RRL off mode:

1. Log on to AP01 as onexev and become the root user (su - root)
2. cd /app2/swing/<yyyymmdd>/scripts
3. Run the t1 deletion script ./t1fileDelXXXYY
4. Run the dhcp deletion script ./dhcpDelXXXYY
5. Repeat Substeps 1 - 4 for AP02
6. Log off of AP02
7. Log on to AP01 as root and run the netmasks deletion script:
/flx/ONEXEVc/current/release/tools/cfg/modifyNetmasks DELETE < /app2/
swing/<yyyymmdd>/scripts/netmskDelXXXYY

8. Stop and restart DHCP on AP01 (as root):


/etc/init.d/dhcp stop
/etc/init.d/dhcp start

9. Log off of AP01.


10. Log on to AP02 and repeat Substep 8.
11. Log off of AP02 and log back onto the OMP as root.
In RRL on mode:

1. Log on to AP01 as login user and assume rsysadm role


2. cd /flx/ONEXEVc/current/release/tools/cfg
3. Run the t1 deletion script
./bpproxy /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/t1fileDel
XXXYY

4. Run the dhcp deletion script


./bpproxy /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/dhcpDel
XXXYY
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-74

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a converged 1xEV-DO cell (inter-RNC/Different


Service Node)

5. Repeat Substeps 1 - 4 for AP02


6. Log off of AP02
7. Log on to AP01 as login user and assume rsysadm and run the netmasks
deletion script:
/flx/ONEXEVc/current/release/tools/cfg/modifyNetmasks DELETE < /
<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/netmskDelXXXYY

8. Stop and restart DHCP on AP01:


/etc/init.d/dhcp stop
/etc/init.d/dhcp start

9. Log off of AP01.


10. Log on to AP02, assume rsysadm role and repeat Substep 8.
11. Log off of AP02 and log back onto the OMP as root.
Result: The network entries for the cell being moved are deleted from the Target

RNC.
...................................................................................................................................................................................................

42

Make any applicable network changes to support the cell swing (for example,
(multiple) router changes between the cell and the Source/Target FMS-APs). Refer to
Issues and caveats (p. 3-22) for more information.
Important! Prior to entering the BP ADD scripts, the CDMA portion of the cell
should be swung, up and made operational.
...................................................................................................................................................................................................

43

Important! Do not proceed if any script execution reports an error or is not OK!
Run the BP Add scripts (not in validate mode remove the -V command line parameter)
in growth order on the Target OMP for the cell components.
Refer to the Growth Table, Forms and key fields (p. 3-11) for the growth order on
the Target OMP for the cell components. For more information on BP, see
CDMA2000 1xEV-DO EMS Configuration Management Bulk Provisioning,
401-614-325.
Example:
runBP -i -O /omp-data/logs/evdotools/runBPmmddyyyy.log -A
<element><SNID><FMSID>Add<BPfile#>

Result: The cell is added back into the database of the Target RNC.
...................................................................................................................................................................................................

44

If they were generated, run the network addition and creation scripts as rooton the
first two Target FMS-APs of the Target OMP.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-75
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a converged 1xEV-DO cell (inter-RNC/Different


Service Node)

Where:
XXX
YY

= three-digit value for the Service Node ID

= two-digit value for the Frame ID

In RRL off mode:

1. Log on to AP01 as onexev and become the root user (su - root)
2. cd /app2/swing/<yyyymmdd>/scripts
3. Run the netmasks addition script
/flx/ONEXEVc/current/release/tools/cfg/modifyNetmasks ADD < /app2/
swing/<yyyymmdd>/scripts/netmskAddXXXYY

4. Run the dhcp addition script ./dhcpAddXXXYY


5. Run the t1 creation script ./t1fileCrtXXXXYY
6. Run the t1 addition script ./t1entryAddXXXYY
7. Repeat Substeps 1 - 2 and 4 - 6 for AP02
8. Log off of AP02
9. Stop and restart DHCP on AP01 (as root):
/etc/init.d/dhcp stop
/etc/init.d/dhcp start

10. Log off of AP01.


11. Log on to AP02 and repeat Substep 9
12. Log off of AP02 and log back onto the OMP as root
In RRL on mode:

1. Log on to AP01 as user account and assume rsysadm role


2. cd /flx/ONEXEVc/current/release/tools/cfg
3. Run the netmasks addition script
/flx/ONEXEVc/current/release/tools/cfg/modifyNetmasks ADD < /<home_
DIR>/<login_ID>/swing/<yyyymmdd>/scripts/netmskAddXXXYY

4. Run the dhcp addition script


./bpproxy <home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/dhcpAddXXXYY

5. Run the t1 creation script


./bpproxy <home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/
t1fileCrtXXXYY

6. Run the t1 addition script


./bpproxy <home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/
t1entryAddXXXYY

7. Repeat Substeps 1 - 2 and 4 - 6 for AP02


8. Log off of AP02
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-76

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a converged 1xEV-DO cell (inter-RNC/Different


Service Node)

9. Stop and restart DHCP on AP01:


/etc/init.d/dhcp stop
/etc/init.d/dhcp start

10. Log off of AP01.


11. Log on to AP02, assume rsysadm role and repeat Substep 9
12. Log off of AP02 and log back onto the OMP as root
Result: The network entries for the cell being moved are deleted from the Target

RNC. START HERE


...................................................................................................................................................................................................

45

If they were generated, run the BP Neighbor Sector Replace scripts on all of the
Neighboring OMPs to update the Neighbor sectors on the Neighbor FMS-APs.
Example: runBP -i -O /omp-data/logs/evdotools/runBPmmddyyyy.log -A

NeighborSectorXXXYYReplace<BPfile#>
Where: NeighborSectorXXXYYReplace<BPfile#> contains:
XXX
YY

= three-digit value for the Service Node ID

= two-digit value for the Frame ID

Result: The Neighbor sectors on the Neighboring SNs/OMPs are updated for the
cell that has been moved.
...................................................................................................................................................................................................

46

Restore the 1xEV-DO CDMs from the TICLI. Restore each of the CDMs in case of a
multi-carrier cell.
Example:
TICLI> rst:cell #, cdm <CDM ID>, crc; ucl
...................................................................................................................................................................................................

47

Wait for the cell to come up on the new FMS-AP pair. Monitor the cell status from
whichever interface is appropriate: EMS GUI if the RNC is EMS managed, or the
OMC-RAN GUI if the RNC is managed by the OMC-RAN.
Important! The cell may take up to 30 minutes to come up, as the cell has to
come up either on a new system, with a new name, or both. If the cell does not
come up after 30 minutes, contact WTSC for further assistance.
...................................................................................................................................................................................................

48

Enter the Verify OA&M on moved and/or renamed converged cell (p. 3-129)
procedure.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-77
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move a converged 1xEV-DO cell (inter-RNC/Different


Service Node)

...................................................................................................................................................................................................

49

Verify successful cell move by placing a call on the new cell. Start a continuous ping
to a good system, and perform handoffs across the faces of the cell.
Result: A call is placed and intra-cell handoffs are completed.
...................................................................................................................................................................................................

50

If a Neighbor cell is available, start a new session on the moved cell and perform three
active handoffs between the moved cell and a Neighbor cell. This should be done for
both CDMA and EVDO.
Result: Handoffs between the moved cell and the Neighbor cell are done.
...................................................................................................................................................................................................

51

After 5 days of verified stability, enter the Cleanup of old Cell Swing files (p. 3-134)
procedure.
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-78

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Rename
a cell
...................................................................................................................................................................................................................................
Purpose

This procedure renames a stand alone modular cell or the DO-side of a mixed-mode
modular cell on the same RNC. The Source OMP and Target OMP are the same.
Required skills and personnel

This procedure is best performed by an expert system administrator.


Prerequisites

To use the 1xEV-DO cell swing tools, you must have the following:

root

login access on the Operations & Maintenance Platform (OMP)


In RRL on mode, you need to be a system administrator or you have to have the
user account access that is assigned the rsysadm system administrator role.
1xEV-DO Cell Swing feature activated.

To use the Bulk Provisioning tool, you must have the following:
Access to the OMP shell
Appropriate permissions
Important

For information on setting up a login on the OMP, see Alcatel-Lucent 9271 EV-DO
Radio Network Controller, 401-614-102.

In addition, certain EMS provisioning steps must be completed before attempting to


use the Bulk Provisioning tool:
The Service Node and Frame must already be known to EMS by having
completed the AP Configuration process. (See the CDMA2000 1xEV-DO
Radio Access System Planning and Implementation Guide, 401-614-101).
The Configuration Database must be installed and operational (see the
CDMA2000 1xEV-DO Radio Access System Planning and Implementation
Guide, 401-614-101).
Data supplied to the configuration database should meet the known parameter
configuration guidelines. (See the CDMA2000 1xEV-DO Configurations
Parameters Guide, 401-614-324).
Ensure that all systems are stable before attempting an actual cell rename.

Related documentation

For descriptions of service measurements for the Ethernet Interface Node (EIN), see
CDMA Network Service Measurements., 401-610-135, .
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-79
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Rename a cell

For backup procedures, see Alcatel-Lucent 9271 EV-DO Radio Network Controller,
401-614-102.
Procedure

Important! Per the impact of 1xEV-DO Gold BCMCS (FID 10862.5) feature the
BCMCS carrier activation must be deactivated before attempting a cell swing. If
not the cell swing will be aborted and the or the result will be an aborted and the
Source RNC Database must be restored.
Perform the following steps:
...................................................................................................................................................................................................

Log on to the OMP as root


...................................................................................................................................................................................................

In the RRL off mode, log on to the database FMS-AP and make a backup copy of the
database as per standard procedures via dbunload. Run this command in a new
directory in the /app2 filesystem.
Important! /app2/DBbackup/swing<yyyymmdd>/ should be created and used as
the destination for the database backup.
For backup procedures, see Alcatel-Lucent 9271 EV-DO Radio Network Controller,
401-614-102.
In the RRL on mode, log on to the database FMS-AP with a user account and
assume rsysadm role. Choose a directory under
rsysadm home /roles/rsysadm/dbbackup.
Important! If this directory does not exist, then it should be created:

mkdir p /roles/rsysadm/dbbackup

$HDRROOT/release/util/dbunload

cd /roles/rsysadm/dbbackup

...................................................................................................................................................................................................

Log off of the FMS-APs (returning to the OMP).


...................................................................................................................................................................................................

Backup the network files that may/will be modified on the lead FMS-APs.
In RRL off mode:

1. Log on to AP01 as onexev


2. mkdir -p /app2/swing/<yyyymmdd>/scripts
3. mkdir -p /app2/swing/<yyyymmdd>/backup
4. cd /app2/swing/<yyyymmdd>/backup
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-80

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Rename a cell

5. cp /etc/netmasks /app2/swing/<yyyymmdd>/backup
6. cp /var/dhcp/* /app2/swing/<yyyymmdd>/backup
7. Repeat Substeps 1 - 6 for AP02
8. Log off all FMS-APs
In RRL on mode:

1. Log on to AP01 as login account


2. mkdir -p /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts
3. mkdir -p /<home_DIR>/<login_ID>/swing/<yyyymmdd>/backup
4. cd /<home_DIR>/<login_ID>/swing/<yyyymmdd>/backup
5. cp /etc/netmasks /<home_DIR>/<login_ID>/<yyyymmdd>/backup
6. cp /var/dhcp/* /<home_DIR>/<login_ID>/swing/<yyyymmdd>/backup
7. Repeat Substeps 1 - 6 for AP02
8. Log off all FMS-APs
Result: Temporary directories for the scripts and for saving a backup copy of the
network files are created. Backup copies of the /etc/netmasks files and of the entire
/var/dhcp/* directory are made. Note that the scripts directory will be used later.
...................................................................................................................................................................................................

Repeat Main Procedure Steps 1 - 3 for the Neighboring OMPs.


...................................................................................................................................................................................................

Make a temporary directory where the necessary input and output files for this
procedure will be stored.
Example: mkdir -p /home/swing/<yyyymmdd>
Where: <yyyymmdd> is the date in year/month/day format.
Result: The temporary directories are created, wherein the input files will be stored

and the cell swing tools will be run.


...................................................................................................................................................................................................

Change directory into the temporary directory just created.


Example: cd /home/swing/<yyyymmdd>
Result: The user is in the temporary directory.
...................................................................................................................................................................................................

Create the cell_file, sn_file, and network_file input files in the temporary directory
created in Main Procedure Step 6 on the Source OMP. For file formatting instructions,
refer to cell_file file (p. 3-12), sn_file file (p. 3-13), and network_file file
(p. 3-15) .

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-81
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Rename a cell

Important! If the directory is already present, the tool will report that this is the
case. If there are problems creating the directory, or if a file (instead of directory)
is already present, errors will print.
Result: The user creates the input files to be used by the cell swing tools.
...................................................................................................................................................................................................

Important! The BP tool requires ksh (Korn Shell) to be running.


Cell swing template files may be found in $cstemps after the BP environment is
enabled for the root user.
The temporary directory from Step 6 is now defined as $bpPath.
Enable the BP tools environment.
Example:
1. exec /usr/bin/ksh
2. . BP_user_setup
3. Enter: Y

Result: The BP tools environment is enabled.


...................................................................................................................................................................................................

10

In the temporary directory,


Example: evdodump -d evdo_dumpdir -i cell_file
Where:
evdo_dumpdir

Top node of directory structure where BP


unloads data; Use $bpPath variable.

cell_file

user-created cell input file

-h

prints the evdoswing command usage help


message

Result: An explanation of what will be done is displayed and the user is prompted:
Are you ready to run 1xEV-DO Bulk-Provisioning commands via runBP
(y/n)?
...................................................................................................................................................................................................

11

At the prompt,
y

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-82

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Rename a cell

Result: The evdodump tool continues running on the OMP.


...................................................................................................................................................................................................

12

When prompted for the Service Node OMP, enter s (for Source).
...................................................................................................................................................................................................

13

For EMS GUI Users: Enter the Service Node ID (SNID) for the OMP. If you do not

know the SNID, access the EMS GUI for the OMP, click the Configuration Data icon,
and click the Service Nodes link.
Important! Once the SNID is entered, the runBP tool is automatically entered and
may run for several minutes, depending on how many cells and Neighbor lists are
being dumped.
Result: The SNID for the OMP is displayed if needed and entered. The runBP tool

then automatically extracts the information needed from the Source system.
For OMC-RAN Users or BP Users: Enter the Service Node ID (SNID) for the

OMP. If you do not know the SNID, setup your Bulk Provisioning environment
and then execute the following command:
Enter: runBP -C output stored ServiceNode | grep hdrsnId
...................................................................................................................................................................................................

14

If the cell to be moved/renamed has Neighbors on other RNCs or SNs, log into the
Neighbor OMP(s) and enter Main Procedure Steps 6 - 13 (run evdodump for those
systems, specifying the appropriate SN type (n for Neighbor) in Step 12.
Result: The evdodump tool is run for all Neighboring OMPs for which a handoff

can occur.
...................................................................................................................................................................................................

15

Transfer the files generated for those OMPs to the temporary directory (created in Step
6) on the Source OMP.
...................................................................................................................................................................................................

16

On the Source OMP,


Example: evdoswing -d evdo_dumpdir -i cell_file -s sn_file [-v]
Where:
evdo_dumpdir

Top node of directory structure where BP


unloads data; Use $bpPath variable.

cell_file

user-created cell input file

sn_file

user-created service node file

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-83
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

-v

Rename a cell

prints further details of evdoswing process


(optional)

...................................................................................................................................................................................................

17

On the Source OMP, run the evdomkdir tool.


Example:
evdomkdir -d evdo_dumpdir -i network_file -s sn_file

Where:
evdo_dumpdir

Top node of directory structure where BP


unloads data; Use $bpPath variable.

network_file

user-created network input file

sn_file

user-created service node file

Result: A directory structure is created to be used when transferring the network

files.
...................................................................................................................................................................................................

18

On the OMP, go to the Source SNID/Frame ID directory that was created by


evdomkdir

Example:
cd $bpPath/sXXX/fYY

Where:
XXX
YY

= three-digit value for the Service Node ID

= three-digit value for the Frame ID

Result: A directory structure to be used when transferring the network files is

created.
...................................................................................................................................................................................................

19

In RRL off mode start a sftp to AP01 as onexev.


In RRL on mode start a sftp to AP01 as login user.
...................................................................................................................................................................................................

20

Go to the dhcp directory and get a copy of the SUNWfiles1_dhcptab file.


Example:
1. cd /var/dhcp

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-84

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Rename a cell

2. get SUNWfiles1_dhcptab
Result: Copy of the SUNWfiles1_dhcptab file is obtained.
...................................................................................................................................................................................................

21

Go to the /etc directory and get a copy of the netmasks file.


Example:
1. cd /etc
2. get netmasks

Result: Copy of the netmasks file is obtained.


...................................................................................................................................................................................................

22

Exit sftp by entering bye or quit and pressing the Enter key.
...................................................................................................................................................................................................

23

Repeat Main Procedures Step 18 and Step 22 for the Target RNC, replacing all
occurrences of Source with Target.
...................................................................................................................................................................................................

24

At the prompt,
cd $bpPath
...................................................................................................................................................................................................

25

If no network changes are being made, skip to Main Procedure Step 28 . Otherwise,
Example: evdonetwork -n evdo_dumpdir -i network_file -s sn_file
Where:
evdo_dumpdir

Top node of directory structure where BP


unloads data; Use $bpPath variable.

network_file

user-created network input file

sn_file

user-created service node file

Result: The dhcp, netmask, and t1 deletion, creation, and addition scripts are

created.
...................................................................................................................................................................................................

26

Important! Add scripts using either put or mput commands.


Transfer the network addition, creation, and deletion scripts (T1, dhcp, netmasks) to the
first two FMS-APs in the cluster and make them executable.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-85
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Rename a cell

Where:
XXX
YY

= three-digit value for the Service Node ID


= two-digit value for the Frame ID

In RRL off mode:

1. cd $bpPath/sXXX/fYY
2. Start an sftp to AP01 as onexev
3. cd /app2/swing/<yyyymmdd>/scripts
4. Transfer the scripts using sftp
5. Exit sftp by entering bye or quit; press the Enter key
6. Repeat Substeps 2 - 5 for AP02, but enter n for the files that begin with netmsk,
as these files are not needed on AP02
7. cd $bpPath
In RRL on mode:

1. cd $bpPath/sXXX/fYY
2. Start an sftp to AP01 as login user account
3. cd /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts
4. Transfer the scripts using sftp
5. Exit sftp by entering bye or quit; press the Enter key
6. Repeat Substeps 2 - 5 for AP02, but enter n for the files that begin with netmsk,
as these files are not needed on AP02
7. cd $bpPath
Result: The network deletion scripts are transferred to the first two FMS-APs in
the cluster.
...................................................................................................................................................................................................

27

Change permissions on the script files.


In RRL off mode:

1. Log on to AP01 as onexev


2. cd /app2/swing/<yyyymmdd>/scripts
3. chmod +x *
4. Log off of AP01
5. Repeat Substeps 1 - 4 for AP02
In RRL on mode:

1. Log on to AP01 as login user


2. cd /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-86

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Rename a cell

3. chmod +x *
4. Log off of AP01
5. Repeat Substeps 1 - 4 for AP02
Result: The network addition and deletion scripts are made executable.
...................................................................................................................................................................................................

28

If they were generated, transfer the Neighbor sector replacement scripts from the
temporary directory on the Source OMP to the temporary directory created on the
Neighboring OMPs where evdodump was run.
Sample filename: NeighborSectorXXXYYReplace<BPfile#>
Where: XXX = three-digit value for the Service Node ID
YY

= two-digit value for the Frame ID

Result: The scripts used to update the Neighbor sectors on Neighboring RNCs/SNs

are transferred.
...................................................................................................................................................................................................

29

Important! If the -V is omitted, the script will be executed.


Do not proceed if any script execution reports an error or is not OK!
Run each script individually in validate (-V) mode to confirm syntax.
Example: runBP -i -O /omp-data/logs/evdotools/runBPmmddyyyy.log -A V scriptname

Where:
scriptname

is in the format

<element><SNID><FMSID>Delete<BPfile#>
<element><SNID><FMSID>Add<BPfile#>
<element><SNID><FMSID>Replace<BPfile#>
...................................................................................................................................................................................................

30

If they were generated, on the Neighbor OMP, run the NeighborSector Replace scripts
in validate (-V) mode.
Important! If the -V is omitted, the script will be executed.
Do not proceed if any script execution reports an error or is not OK!
...................................................................................................................................................................................................

31

Take the cell unconditionally out of service (OOS) to divert call traffic.
Example:
TICLI> rmv:cell # <BTS ID>, cdm <CDM ID>, crc; ucl

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-87
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Rename a cell

Result: The cell is OOS and call traffic diverted.


...................................................................................................................................................................................................

32

While still in TICLI, inhibit audits on the cell being renamed.


Example:
TICLI>inh:bts old#, aud maint
TICLI>inh:bts old#, aud config
TICLI> quit
...................................................................................................................................................................................................

33

Important! Do not proceed if any script execution reports an error or is not OK!
Run the BP Delete scripts, found in the /home/swing/<yyyymmdd> directory, in normal
mode (without the -V command line parameter) in degrowth order on the Source OMP
for the cell components.
Refer to the Degrowth Table, Forms and key fields (p. 3-11) for the degrowth order
on the Source OMP for the cell components. For more information on BP, see
CDMA2000 1xEV-DO Network EMS Configuration Management Bulk Provisioning
Guide, 401-614-325.
Example:
runBP -i -O /omp-data/logs/evdotools/runBPmmddyyyy.log -A
<element><SNID><FMSID>Delete<BPfile#>

Result: The cell is deleted from the database of the Source RNC.
...................................................................................................................................................................................................

34

Run the deletion scripts as root on the first two FMS-APs.


Where:
XXX
YY

= three-digit value for the Service Node ID

= two-digit value for the Frame ID

In RRL off mode:

1. Log on to AP01 as onexev and become the root user (su - root)
2. cd /app2/swing/<yyyymmdd>/scripts
3. Run the t1 deletion script ./t1fileDelXXXYY
4. Run the dhcp deletion script ./dhcpDelXXXYY
5. Repeat Substeps 1 - 4 for AP02
6. Log off of AP02
7. Log on to AP01 as root and run the netmasks deletion script:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-88

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Rename a cell

/flx/ONEXEVc/current/release/tools/cfg/modifyNetmasks DELETE < /app2/


swing/<yyyymmdd>/scripts/netmskDelXXXYY

8. Stop and restart DHCP on AP01 (as root):


/etc/init.d/dhcp stop
/etc/init.d/dhcp start

9. Log off of AP01.


10. Log on to AP02 and repeat Substep 8.
11. Log off of AP02 and log back onto the OMP as root.
In RRL on mode:

1. Log on to AP01 as login user and assume rsysadm role


2. cd /flx/ONEXEVc/current/release/tools/cfg
3. Run the t1 deletion script
./bpproxy /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/t1fileDel
XXXYY

4. Run the dhcp deletion script


./bpproxy /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/dhcpDel
XXXYY

5. Repeat Substeps 1 - 4 for AP02


6. Log off of AP02
7. Log on to AP01 as login user and assume rsysadm and run the netmasks
deletion script:
/flx/ONEXEVc/current/release/tools/cfg/modifyNetmasks DELETE < /
<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/netmskDelXXXYY

8. Stop and restart DHCP on AP01:


/etc/init.d/dhcp stop
/etc/init.d/dhcp start

9. Log off of AP01.


10. Log on to AP02, assume rsysadm role and repeat Substep 8.
11. Log off of AP02 and log back onto the OMP as root.
Result: The network entries for the cell being moved are deleted from the Source

RNC.
...................................................................................................................................................................................................

35

Make any applicable network changes to support the cell swing (for example,
(multiple) router changes between the cell and the Source/Target FMS-APs).
...................................................................................................................................................................................................

36

Important! Do not proceed if any script execution reports an error or is not OK!

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-89
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Rename a cell

Run the BP Add scripts (not in validate mode remove the -V command line parameter)
in growth order on the Target OMP for the cell components.
Refer to the Growth Table, Forms and key fields (p. 3-11) for the growth order on
the Target OMP for the cell components. For more information on BP, see CDMA
2000 1xEV-DO EMS Configuration Management Bulk Provisioning., 401-614-325.
Example:
runBP -i -O /omp-data/logs/evdotools/runBPmmddyyyy.log -A
<element><SNID><FMSID>Add<BPfile#>

Result: The renamed cell is added into the database of the Target RNC.
...................................................................................................................................................................................................

37

Run the network addition and creation scripts as root on the first two FMS-APs.
Where:
XXX
YY

= three-digit value for the Service Node ID

= two-digit value for the Frame ID

In RRL off mode:

1. Log on to AP01 as onexev and become the root user (su - root)
2. cd /app2/swing/<yyyymmdd>/scripts
3. Run the netmasks addition script
/flx/ONEXEVc/current/release/tools/cfg/modifyNetmasks ADD < /app2/
swing/<yyyymmdd>/scripts/netmskAddXXXYY

4. Run the dhcp addition script ./dhcpAddXXXYY


5. Run the t1 creation script ./t1fileCrtXXXYY
6. Run the t1 addition script ./t1entryAddXXXYY
7. Repeat Substeps 1 - 2 and 4 - 6 for AP02
8. Log off AP02
9. Stop and restart DHCP on AP01 (as root):
/etc/init.d/dhcp stop
/etc/init.d/dhcp start

10. Log off of AP01


11. Log on to AP02 as root and repeat Substep 9
12. Log off of AP02 and log back onto the OMP as root
In RRL on mode:

1. Log on to AP01 as user account and assume rsysadm role


2. cd /flx/ONEXEVc/current/release/tools/cfg
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-90

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Rename a cell

3. Run the netmasks addition script:


/flx/ONEXEVc/current/release/tools/cfg/modifyNetmasks ADD < /<home_
DIR>/<login_ID>/swing/<yyyymmdd>/scripts/netmskAddXXXYY

4. Run the dhcp addition script


./bpproxy <home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/dhcpAddXXXYY

5. Run the t1 creation script


./bpproxy <home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/
t1fileCrtXXXYY

6. Run the t1 addition script


./bpproxy <home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/
t1entryAddXXXYY

7. Repeat Substeps 1 - 2 and 4 - 6 for AP02


8. Log off of AP02
9. Stop and restart DHCP on AP01:
/etc/init.d/dhcp stop
/etc/init.d/dhcp start

10. Log off of AP01.


11. Log on to AP02, assume rsysadm role and repeat Substep 9
12. Log off of AP02 and log back onto the OMP as root
Result: The network entries for the cell being moved are deleted from the Target

RNC.
...................................................................................................................................................................................................

38

If they were generated, run the BP Neighbor Sector Replace scripts on all of the Target
OMPs Neighboring OMPs to update the Neighbor sectors on the Neighbor FMS-APs.
Example: runBP -i -O /omp-data/logs/evdotools/runBPmmddyyyy.log -A

NeighborSectorXXXYYReplace<BPfile#>
Where: NeighborSectorXXXYYReplace<BPfile#>contains:
XXX
YY

= three-digit value for the Service Node ID

= two-digit value for the Frame ID

Result: The Neighbor sectors on the Neighboring SNs/OMPs are updated for the

cell that has been moved.


...................................................................................................................................................................................................

39

Restore the 1xEV-DO CDMs from the TICLI. Restore each of the CDMs in case of a
multi-carrier cell.
Example:
TICLI> rst:cell #, cdm <CDM ID>, crc; ucl

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-91
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Rename a cell

...................................................................................................................................................................................................

40

Wait for the cell to come up on the new FMS-AP pair. Monitor the cell status from
whichever interface is appropriate: EMS GUI if the RNC is EMS managed, or the
OMC-RAN GUI if the RNC is managed by the OMC-RAN.
Important! The cell may take up to 30 minutes to come up, as the cell has to
come up either on a new system, with a new name, or both. If the cell does not
come up after 30 minutes, contact WTSC for further assistance.
...................................................................................................................................................................................................

41

Enter the Verify OA&M on moved and/or renamed converged cell (p. 3-129)
procedure.
...................................................................................................................................................................................................

42

Verify successful cell rename by placing a call on the renamed cell. Start a continuous
ping to a good system, and perform handoffs across the faces of the cell.
Result: A call is placed and intra-cell handoffs are completed.
...................................................................................................................................................................................................

43

If a Neighbor cell is available, start a new session on the renamed cell and perform
three active handoffs between the renamed cell and the Neighbor cell.
Result: Handoffs between the renamed cell and the Neighbor cell are done.
...................................................................................................................................................................................................

44

After 5 days of verified stability, enter the Cleanup of old Cell Swing files (p. 3-134)
procedure.
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-92

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move
and Rename a cell (intra-RNC)
...................................................................................................................................................................................................................................
Purpose

This procedure moves and renames a stand alone modular cell or the DO-side of a
mixed-mode modular cell from one FMS-AP pair to another FMS-AP pair on the same
RNC (intra-RNC). The Source OMP and the Target OMP are the same.
Important! Before performing an EVDO cell swing, contact the Security
Administrator to ensure that security settings for the cell site EVDO CDMs are
properly set before the swing occurs.
When to perform

Perform this procedure when you need to simultaneously move and rename a cell.
Required skills and personnel

This procedure is best performed by an expert system administrator.


Prerequisites

To use the 1xEV-DO cell swing tools, you must have the following:

root

login access on the Operations & Maintenance Platform (OMP)


In RRL on mode, you need to be a system administrator or you have to have the
user account access that is assigned the rsysadm system administrator role.
1xEV-DO Cell Swing feature activated.

To use the Bulk Provisioning tool, you must have the following:

Access to the OMP shell


Appropriate permissions

Important

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-93
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move and Rename a cell (intra-RNC)

For information on setting up a login on the OMP, see CDMA Network Operations and
Management Platform (OMP-FX) ECP Operations, Administration, and Maintenance,
401-662-102.

In addition, certain EMS provisioning steps must be completed before attempting to


use the Bulk Provisioning tool:
The Service Node and Frame must already be known to EMS by having
completed the AP Configuration process. (See the CDMA2000 1xEV-DO
Radio Access System Planning and Implementation Guide, 401-614-101).
The Configuration Database must be installed and operational (see the
CDMA2000 1xEV-DO Radio Access System Planning and Implementation
Guide, 401-614-101).
Data supplied to the configuration database should meet the known parameter
configuration guidelines. (See the CDMA2000 1xEV-DO Network
Configurations Parameters Guide, 401-614-324).
Ensure that all systems are stable before attempting an actual cell move and
rename.

Related documentation

For backup procedures, see Alcatel-Lucent 9271 EV-DO Radio Network Controller,
401-614-102.
Procedure

Important! Per the impact of 1xEV-DO Gold BCMCS (FID 10862.5) feature the
BCMCS carrier activation must be deactivated before attempting a cell swing. If
not the cell swing will be aborted and the or the result will be an aborted and the
Source RNC Database must be restored.
Perform the following steps:
...................................................................................................................................................................................................

Log on to the Source OMP as root.


Important! For inter-RNC Cell Swing, the DO-RNCs need to have the same load.
RCS-APs (CDMA) also need to have the same load.
...................................................................................................................................................................................................

In the RRL off mode, log on to the database FMS-AP of the Source OMP and make a
backup copy of the database as per standard procedures via dbunload. Run this
command in a new directory in the /app2 filesystem.
Important! /app2/DBbackup/swing<yyyymmdd>/ should be created and used as
the destination for the database backup.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-94

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move and Rename a cell (intra-RNC)

For backup procedures, see Alcatel-Lucent 9271 EV-DO Radio Network Controller,
401-614-102.
In the RRL on mode, log on to the database FMS-AP with a user account and
assume rsysadm role. Choose a directory under
rsysadm home /roles/rsysadm/dbbackup.
Important! If this directory does not exist, then it should be created:

mkdir p /roles/rsysadm/dbbackup
cd /roles/rsysadm/dbbackup
$HDRROOT/release/util/dbunload

...................................................................................................................................................................................................

Log off of the FMS-APs (returning to the OMP).


...................................................................................................................................................................................................

Back up the network files that may/will be modified on the lead FMS-APs.
In RRL off mode:

1. Log on to AP01 as onexev


2. mkdir -p /app2/swing/<yyyymmdd>/scripts
3. mkdir -p /app2/swing/<yyyymmdd>/backup
4. cd /app2/swing/<yyyymmdd>/backup
5. cp /etc/netmasks /app2/swing/<yyyymmdd>/backup
6. cp /var/dhcp/* /app2/swing/<yyyymmdd>/backup
7. Repeat Substeps 1 - 6 for AP02
8. Log off all FMS-APs
In RRL on mode:

1. Log on to AP01 as login account


2. mkdir -p /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts
3. mkdir -p /<home_DIR>/<login_ID>/swing/<yyyymmdd>/backup
4. cd /<home_DIR>/<login_ID>/<yyyymmdd>/backup
5. cp /etc/netmasks /<home_DIR>/<login_ID>/<yyyymmdd>/backup
6. cp /var/dhcp/* /<home_DIR>/<login_ID>/swing/<yyyymmdd>/backup
7. Repeat Substeps 1 - 6 for AP02
8. Log off all FMS-APs

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-95
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move and Rename a cell (intra-RNC)

Result: Temporary directories for the scripts and for saving a backup copy of the

network files are created. Backup copies of the /etc/netmasks files and of the entire
/var/dhcp/* directory are made. Note that the scripts directory will be used later.
...................................................................................................................................................................................................

Repeat Main Procedure Step 1-Step 3 for the Neighboring OMPs/RNCs.


...................................................................................................................................................................................................

On the Source OMP, make a temporary directory where the necessary input and output
files for moving a cell will be stored.
Example: mkdir -p /home/swing/<yyyymmdd>
Where: <yyyymmdd> is the date in year/month/day format.
Result: The temporary directories are created, wherein the input files will be stored

and the cell swing tools will be run.


...................................................................................................................................................................................................

Change directory into the temporary directory just created.


Example: cd /home/swing/<yyyymmdd>
Result: The user is in the temporary directory.
...................................................................................................................................................................................................

Create the cell_file, sn_file, and network_file input files in the temporary directory
created in Main Procedure Step 6 on the Source OMP. For file formatting instructions,
refer to cell_file file (p. 3-12), sn_file file (p. 3-13), and network_file file
(p. 3-15).
Important! If the directory is already present, the tool will report that this is the
case. If there are problems creating the directory, or if a file (instead of directory)
is already present, errors will print.
Result: The user creates the input files to be used by the cell swing tools.
...................................................................................................................................................................................................

Important! The BP tool requires ksh (Korn Shell) to be running.


Cell swing template files may be found in $cstemps after the BP environment is
enabled for the root user.
The temporary directory from Step 6 is now defined as $bpPath.
Enable the BP tools environment.
Example:

1. exec /usr/bin/ksh
2. . BP_user_setup
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-96

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move and Rename a cell (intra-RNC)

3. Enter: Y
Result: The BP tools environment is enabled.
...................................................................................................................................................................................................

10

In the temporary directory,


Example:

evdodump -d

evdo_dumpdir

-i cell_file

Where:
evdo_dumpdir

Top node of directory structure where BP


unloads data; Use $bpPath variable.

cell_file

user-created cell input file

-c

dumps tables for converged cells

-h

prints the evdoswing command usage help


message

Result: An explanation of what will be done is displayed and the user is prompted:
Are you ready to run 1xEV-DO Bulk-Provisioning commands via runBP
(y/n)?
...................................................................................................................................................................................................

11

At the prompt,
Enter: Y
Result: The evdodump tool continues running on the OMP.
...................................................................................................................................................................................................

12

When prompted for the Service Node OMP, enter s (for Source).
...................................................................................................................................................................................................

13

For EMS GUI Users: Enter the Service Node ID (SNID) for the OMP. If you do not
know the SNID, access the EMS GUI for the OMP, click the Configuration Data icon,
and click the Service Nodes link.

Important! Once the SNID is entered, the runBP tool is automatically entered and
may run for several minutes, depending on how many cells and Neighbor lists are
being dumped.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-97
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move and Rename a cell (intra-RNC)

Result: The SNID for the OMP is displayed if needed and entered. The runBP tool

then automatically extracts the information needed from the Source system.
Where: -c dumps tables for converged cells.
For OMC-RAN Users or BP Users: Enter the Service Node ID (SNID) for the
OMP. If you do not know the SNID, setup your Bulk Provisioning environment
and then execute the following command:
Enter: runBP -C output stored ServiceNode | grep hdrsnId
...................................................................................................................................................................................................

14

If the cell to be move/renamed has Neighbors on other RNCs or SNs, log into the
Neighbor OMP(s) and enter Main Procedure Step 6 - Step 13 (run evdodump for those
systems, specifying the appropriate SN type (n for Neighbor) in Main Procedure Step
12 .
Result: The evdodump tool is run for all Neighboring OMPs for which a handoff

can occur.
...................................................................................................................................................................................................

15

Transfer the files generated for the Neighbor OMPs to the temporary directory (created
in Main Procedure Step 6) on the Source OMP via sftp.
Important! If you cannot sftp as the root user, use the omptech login and put the
files in /tmp. Go back to the Source OMP and copy the transferred files from /tmp
to $bpPath.
...................................................................................................................................................................................................

16

In the temporary directory,


Example:

evdoswing -d evdo_dumpdir -i cell_file -s sn_file [-v]

Where:
evdo_dumpdir

Top node of directory structure where BP


unloads data; Use $bpPath variable.

cell_file

user-created cell input file

sn_file

user-created service node file

-v

prints further details of evdoswing


process (optional)

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-98

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move and Rename a cell (intra-RNC)

Result: The evdoswing script files for deleting and adding the cell components are

created, along with the replace scripts for updating the Neighbor sectors on other
RNCs/SNs.
...................................................................................................................................................................................................

17

On the Source OMP, run the evdomkdir tool.


Example:
evdomkdir -d evdo_dumpdir -i network_file -s sn_file

Where:
evdo_dumpdir

Top node of directory structure where BP


unloads data; Use $bpPath variable.

network_file

user-created network input file

sn_file

user-created service node file

Result: A directory structure is created to be used when transferring the network

files.
...................................................................................................................................................................................................

18

On the OMP, go to the Source SNID/Frame ID directory that was created by


evdomkdir.
Example:
cd $bpPath/sXXX/fYY

Where:
XXX
YY

= three-digit value for the Service Node ID

= two-digit value for the Frame ID

Result: A directory structure to be used when transferring the network files is

created.
...................................................................................................................................................................................................

19

In RRL off mode start a sftp to AP01 as onexev.


In RRL on mode start a sftp to AP01 as login user.
...................................................................................................................................................................................................

20

Go to the dhcp directory and get a copy of the SUNWfiles1_dhcptab file.


Example:

1. cd /var/dhcp
2. get SUNWfiles1_dhcptab
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-99
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move and Rename a cell (intra-RNC)

Result: Copy of the SUNWfiles1_dhcptab file is obtained.


...................................................................................................................................................................................................

21

Go to the /etc directory and get a copy of the netmasks file.


Example:

1. cd /etc
2. get netmasks
Result: Copy of the netmasks file is obtained.
...................................................................................................................................................................................................

22

Exit sftp by entering bye or quit and pressing the Enter key.
...................................................................................................................................................................................................

23

Repeat Main Procedures Step 18 and Step 22 for the Target RNC, replacing all
occurrences of Source with Target.
...................................................................................................................................................................................................

24

At the prompt,
Enter: cd $bpPath
...................................................................................................................................................................................................

25

If no network changes are being made, skip to Step 28 . Otherwise,


Example: evdonetwork -n evdo_dumpdir -i network_file -s sn_file
Where:
evdo_dumpdir

Top node of directory structure where BP


unloads data; Use $bpPath variable.

network_file

user-created network input file

sn_file

user-created service node file

Result: The evdonetwork script files for deleting, creating, and adding the network

components are created.


...................................................................................................................................................................................................

26

Important! Add scripts using either put or mput commands.


Transfer the network addition, creation, and deletion scripts (T1, dhcp, netmasks) to the
first two FMS-APs in the cluster and make them executable.
Where:
XXX

= three-digit value for the Service Node ID

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-100

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

YY

Move and Rename a cell (intra-RNC)

= two-digit value for the Frame ID

In RRL off mode:

1. cd $bpPath/sXXX/fYY
2. Start an sftp to AP01 as onexev
3. cd /app2/swing/<yyyymmdd>/scripts
4. Transfer the scripts using sftp
5. Exit sftp by entering bye or quit; press the Enter key
6. Repeat Substeps 2 - 5 for AP02, but enter n for the files that begin with netmsk,
as these files are not needed on AP02
7. cd $bpPath
In RRL on mode:

1. cd $bpPath/sXXX/fYY
2. Start an sftp to AP01 as login user account
3. cd /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts
4. Transfer the scripts using sftp
5. Exit sftp by entering bye or quit; press the Enter key
6. Repeat Substeps 2 - 5 for AP02, but enter n for the files that begin with netmsk,
as these files are not needed on AP02
7. cd $bpPath
Result: The network deletion scripts are transferred to the first two FMS-APs in
the cluster.
...................................................................................................................................................................................................

27

Change permissions on the script files.


In RRL off mode:

1. Log on to AP01 as onexev


2. cd /app2/swing/<yyyymmdd>/scripts
3. chmod +x *
4. Log off of AP01
5. Repeat Substeps 1 - 4 for AP02
In RRL on mode:

1. Log on to AP01 as as login user


2. cd /<home_DIR>/<login_ID>/<yyyymmdd>/scripts
3. chmod +x *
4. Log off of AP01
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-101
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move and Rename a cell (intra-RNC)

5. Repeat Substeps 1 - 4 for AP02


Result: The network addition and deletion scripts are made executable.
...................................................................................................................................................................................................

28

Important! If you cannot sftp as the root user, use the omptech login and put the
files in /tmp. Go back to the Source OMP and copy the transferred files from /tmp
to $bpPath.
If they were generated, transfer the Neighbor sector replacement scripts via sftp from
the temporary directory on the Source OMP to the temporary directory created on the
Neighboring OMPs where evdodump was run.
Sample filename: NeighborSectorXXXYYReplace<BPfile#>
Where: XXX = three-digit value for the Service Node ID
YY

= two-digit value for the Frame ID

Result: The scripts used to update the Neighbor sectors on Neighboring RNCs/SNs
are transferred.
...................................................................................................................................................................................................

29

Important! If the -V is omitted, the script will be executed.


Do not proceed if any script execution reports an error or is not OK!
On the Source OMP, at the $bpPath directory, run each script individually in validate
mode (-V) to confirm syntax.
Example: runBP -i -O /omp-data/logs/evdotools/runBPmmddyyyy.log -A Vscriptname
Where:
scriptname

is in the format

<element><SNID><FMSID>Delete<BPfile#>
<element><SNID><FMSID>Add<BPfile#>
<element><SNID><FMSID>Replace<BPfile#>
NeighborSector<SNID><FMSID>Replace<BPfile#>

(run on Neighboring OMPs)

...................................................................................................................................................................................................

30

Remove the CDM using the TICLI. This step must be repeated for all CDMs in a
multiple carrier cell.
Take the cell unconditionally out of service (OOS) to divert call traffic.
Example:
TICLI

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-102

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move and Rename a cell (intra-RNC)

TICLI> rmv:cell #, cdm <CDM ID>, crc; ucl


Result: The cell is OOS and call traffic diverted.
...................................................................................................................................................................................................

31

Important! Do not proceed if any script execution reports an error or is not OK!
Run the BP Delete scripts, found in the /home/swing/<yyyymmdd> directory, in normal
mode (without the -V command line parameter) in degrowth order on the Source OMP
for the cell components.
Refer to the Degrowth Table, Forms and key fields (p. 3-11) for the degrowth order
on the Source OMP for the cell components. For more information on BP, see
CDMA2000 1xEV-DO EMS Configuration Management Bulk Provisioning,
401-614-325.
Example:
runBP -i -O /omp-data/logs/evdotools/runBPmmddyyyy.log -A
<element><SNID><FMSID>Delete<BPfile#>

Result: The cell is deleted from the database of the Source RNC.
...................................................................................................................................................................................................

32

Run the deletion scripts as root on the first two Source FMS-APs.
Where:
XXX
YY

= three-digit value for the Service Node ID

= two-digit value for the Frame ID

In RRL off mode:

1. Log on to AP01 as onexev and become the root user (su - root)
2. cd /app2/swing/<yyyymmdd>/scripts
3. Run the t1 deletion script ./t1fileDelXXXYY
4. Run the dhcp deletion script ./dhcpDelXXXYY
5. Repeat Substeps 1 - 4 for AP02
6. Log off of AP02
7. Log on to AP01 as root and run the netmasks deletion script:
/flx/ONEXEVc/current/release/tools/cfg/modifyNetmasks DELETE < /app2/
swing/<yyyymmdd>/scripts/netmskDelXXXYY

8. Stop and restart DHCP on AP01 (as root):


/etc/init.d/dhcp stop
/etc/init.d/dhcp start

9. Log off of AP01.


...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-103
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move and Rename a cell (intra-RNC)

10. Log on to AP02 and repeat Substep 8.


11. Log off of AP02 and log back onto the OMP as root.
In RRL on mode:

1. Log on to AP01 as login user and assume rsysadm role


2. cd /flx/ONEXEVc/current/release/tools/cfg
3. Run the t1 deletion script
./bpproxy /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/t1fileDel
XXXYY

4. Run the dhcp deletion script


./bpproxy /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/dhcpDel
XXXYY

5. Repeat Substeps 1 - 4 for AP02


6. Log off of AP02
7. Log on to AP01 as login user and assume rsysadm and run the netmasks
deletion script:
/flx/ONEXEVc/current/release/tools/cfg/modifyNetmasks DELETE < /
<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/netmskDelXXXYY

8. Stop and restart DHCP on AP01:


/etc/init.d/dhcp stop
/etc/init.d/dhcp start

9. Log off of AP01.


10. Log on to AP02, assume rsysadm role and repeat Substep 8.
11. Log off of AP02 and log back onto the OMP as root.
Result: The network entries for the cell being moved are deleted from the Source

RNC.
...................................................................................................................................................................................................

33

Make any applicable network changes to support the cell swing (for example,
(multiple) router changes between the cell and the Source/Target FMS-APs).
Important! Prior to entering the BP ADD scripts, the CDMA portion of the cell
should be swung, up and made operational.
...................................................................................................................................................................................................

34

Important! Do not proceed if any script execution reports an error or is not OK!
Run the BP Add scripts (not in validate mode remove the -V command line parameter)
in growth order on the Target OMP for the cell components.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-104

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move and Rename a cell (intra-RNC)

Refer to the Growth Table, Forms and key fields (p. 3-11) for the growth order on
the Target OMP for the cell components. For more information on BP, see
CDMA2000 1xEV-DO EMS Configuration Management Bulk Provisioning,
401-614-325.
Example:
runBP -i -O /omp-data/logs/evdotools/runBPmmddyyyy.log -A <element>
<SNID><FMSID>Add<BPfile#>

Result: The renamed cell is added into the database of the Target RNC.
...................................................................................................................................................................................................

35

Run the network addition and creation scripts as root on the first two Target
FMS-APs.
Where:
XXX
YY

= three-digit value for the Service Node ID

= two-digit value for the Frame ID

In RRL off mode:

1. Log on to AP01 as onexev and become the root user (su - root)
2. cd /app2/swing/<yyyymmdd>/scripts
3. Run the netmasks addition script
/flx/ONEXEVc/current/release/tools/cfg/modifyNetmasks ADD < /app2/
swing/<yyyymmdd>/scripts/netmskAddXXXYY

4. Run the dhcp addition script ./dhcpAddXXXYY


5. Run the t1 creation script ./t1fileCrtXXXXYY
6. Run the t1 addition script ./t1entryAddXXXYY
7. Repeat Substeps 1 - 2 and 4 - 6 for AP02
8. Log off of AP02
9. Stop and restart DHCP on AP01 (as root):
/etc/init.d/dhcp stop
/etc/init.d/dhcp start

10. Log off of AP01.


11. Log on to AP02 and repeat Substep 9
12. Log off of AP02 and log back onto the OMP as root
In RRL on mode:

1. Log on to AP01 as user account and assume rsysadm role


2. cd /flx/ONEXEVc/current/release/tools/cfg
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-105
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move and Rename a cell (intra-RNC)

3. Run the netmasks addition script


/flx/ONEXEVc/current/release/tools/cfg/modifyNetmasks ADD < /<home_
DIR>/<login_ID>/swing/<yyyymmdd>/scripts/netmskAddXXXYY

4. Run the dhcp addition script


./bpproxy <home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/dhcpAddXXXYY

5. Run the t1 creation script


./bpproxy <home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/
t1fileCrtXXXYY

6. Run the t1 addition script


./bpproxy <home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/
t1entryAddXXXYY

7. Repeat Substeps 1 - 2 and 4 - 6 for AP02


8. Log off of AP02
9. Stop and restart DHCP on AP01:
/etc/init.d/dhcp stop
/etc/init.d/dhcp start

10. Log off of AP01.


11. Log on to AP02, assume rsysadm role and repeat Substep 9
12. Log off of AP02 and log back onto the OMP as root
Result: The network entries for the cell being moved/renamed are added to the
Target RNC.
...................................................................................................................................................................................................

36

If they were generated, run the BP Neighbor Sector Replace scripts on all of the
Neighboring OMPs to update the Neighbor sectors on the Neighbor FMS-APs.
Example:
runBP -i -O /omp-data/logs/evdotools/runBPmmddyyyy.log -A

NeighborSectorXXXYYReplace<BPfile#>
Where:

NeighborSectorXXXYYReplace<BPfile#> contains:
XXX
YY

= three-digit value for the Service Node ID

= two-digit value for the Frame ID

Result: The Neighbor sectors on the Neighboring SNs/OMPs are updated for the
cell that has been moved.
...................................................................................................................................................................................................

37

Restore the 1xEV-DO CDMs from the TICLI. Restore each of the CDMs in case of a
multi-carrier cell.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-106

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move and Rename a cell (intra-RNC)

Example:
TICLI> rst:cell #, cdm <CDM ID>, crc; ucl
...................................................................................................................................................................................................

38

Wait for the cell to come up on the new FMS-AP pair. Monitor the cell status from
whichever interface is appropriate: EMS GUI if the RNC is EMS managed, or the
OMC-RAN GUI if the RNC is managed by the OMC-RAN.
Important! The cell may take up to 30 minutes to come up, as the cell has to
come up either on a new system, with a new name, or both. If the cell does not
come up after 30 minutes, contact WTSC for further assistance.
...................................................................................................................................................................................................

39

Enter the Verify OA&M on moved and/or renamed converged cell (p. 3-129)
procedure.
...................................................................................................................................................................................................

40

Verify successful cell move by placing a call on the new cell. Start a continuous ping
to a good system, and perform handoffs across the faces of the cell.
Result: A call is placed and intra-cell handoffs are completed.
...................................................................................................................................................................................................

41

If a Neighbor cell is available, start a new session on the moved cell and perform three
active handoffs between the moved cell and a Neighbor cell. This should be done for
both CDMA and EVDO.
Result: Handoffs between the moved cell and the Neighbor cell are done.
...................................................................................................................................................................................................

42

After 5 days of verified stability, enter the Cleanup of old Cell Swing files (p. 3-134)
procedure.
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-107
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move
and Rename a cell (inter-RNC)
...................................................................................................................................................................................................................................
Purpose

This procedure moves and renames a stand alone modular cell or the DO-side of a
mixed-mode modular cell from an FMS-AP pair on one RNC to another FMS-AP pair
on another RNC (inter-RNC).
Important! Before performing an EVDO cell swing, contact the Security
Administrator to ensure that security settings for the cell site EVDO CDMs are
properly set before the swing occurs.
When to perform

Perform this procedure when you need to simultaneously move and rename a cell.
Required skills and personnel

This procedure is best performed by an expert system administrator.


Prerequisites

To use the 1xEV-DO cell swing tools, you must have the following:

root

login access on the Operations & Maintenance Platform (OMP)


In RRL on mode, you need to be a system administrator or you have to have the
user account access that is assigned the rsysadm system administrator role.
1xEV-DO Cell Swing feature activated.

To use the Bulk Provisioning tool, you must have the following:

Access to the OMP shell


Appropriate permissions

Important

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-108

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move and Rename a cell (inter-RNC)

For information on setting up a login on the OMP, see Alcatel-Lucent 9271 EV-DO
Radio Network Controller, 401-614-102.

In addition, certain EMS provisioning steps must be completed before attempting to


use the Bulk Provisioning tool:
The Service Node and Frame must already be known to EMS by having
completed the AP Configuration process. (See the CDMA2000 1xEV-DO
Radio Access System Planning and Implementation Guide, 401-614-101).
The Configuration Database must be installed and operational (see the
CDMA2000 1xEV-DO Radio Access System Planning and Implementation
Guide, 401-614-101).
Data supplied to the configuration database should meet the known parameter
configuration guidelines. (See the CDMA2000 1xEV-DO Configurations
Parameters Guide, 401-614-324).
Ensure that all systems are stable before attempting an actual cell move and
rename.

Related documentation

For backup procedures, see Alcatel-Lucent 9271 EV-DO Radio Network Controller,
401-614-102.
Procedure

Important! Per the impact of 1xEV-DO Gold BCMCS (FID 10862.5) feature the
BCMCS carrier activation must be deactivated before attempting a cell swing. If
not the cell swing will be aborted and the or the result will be an aborted and the
Source RNC Database must be restored.
Perform the following steps:
...................................................................................................................................................................................................

Log on to the Source OMP as root.


...................................................................................................................................................................................................

In the RRL off mode, log on to the database FMS-AP of the Source OMP and make a
backup copy of the database as per standard procedures via dbunload. Run this
command in a new directory in the /app2 filesystem.
Important! /app2/DBbackup/swing<yyyymmdd>/ should be created and used as
the destination for the database backup.
For backup procedures, see Alcatel-Lucent 9271 EV-DO Radio Network Controller,
401-614-102.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-109
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move and Rename a cell (inter-RNC)

In the RRL on mode, log on to the database FMS-AP with a user account and
assume rsysadm role. Choose a directory under
rsysadm home /roles/rsysadm/dbbackup.
Important! If this directory does not exist, then it should be created:

mkdir p /roles/rsysadm/dbbackup
cd /roles/rsysadm/dbbackup
$HDRROOT/release/util/dbunload

...................................................................................................................................................................................................

Log off of the FMS-APs (returning to the OMP).


...................................................................................................................................................................................................

Back up the network files that may/will be modified on the lead FMS-APs.
In RRL off mode:

1. Log on to AP01 as onexev


2. mkdir -p /app2/swing/<yyyymmdd>/scripts
3. mkdir -p /app2/swing/<yyyymmdd>/backup
4. cd /app2/swing/<yyyymmdd>/backup
5. cp /etc/netmasks /app2/swing/<yyyymmdd>/backup
6. cp /var/dhcp/* /app2/swing/<yyyymmdd>/backup
7. Repeat Substeps 1 - 6 for AP02
8. Log off all FMS-APs
In RRL on mode:

1. Log on to AP01 as login account


2. mkdir -p /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts
3. mkdir -p /<home_DIR>/<login_ID>/swing/<yyyymmdd>/backup
4. cd /<home_DIR>/<login_ID>/swing/<yyyymmdd>/backup
5. cp /etc/netmasks /<home_DIR>/<login_ID>/<yyyymmdd>/backup
6. cp /var/dhcp/* /<home_DIR>/<login_ID>/swing/<yyyymmdd>/backup
7. Repeat Substeps 1 - 6 for AP02
8. Log off all FMS-APs
Result: Temporary directories for the scripts and for saving a backup copy of the
network files are created. Backup copies of the /etc/netmasks files and of the entire
/var/dhcp/* directory are made. Note that the scripts directory will be used later.
...................................................................................................................................................................................................

Repeat Main Procedure Step 1 - Step 4 for the Target OMP.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-110

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move and Rename a cell (inter-RNC)

...................................................................................................................................................................................................

Repeat Main Procedure Step 1 - Step 3 for the Neighbor OMP.


...................................................................................................................................................................................................

Using TICLI, obtain list a active generics on the cells to be moved/removed.


Example: TICLI
TICLI> OP:CELL #, generic
TICLI> quit
Result: A list of active generics on the cells are displayed and sent to the ROP and
the TICLI session is terminated.
...................................................................................................................................................................................................

Confirm Target RNCs cell generic:


1. Log on to Target OMP as root
2. Log on to Target FMS-AP
3. cd /flx/ONEXEVcs/versions
4. ls -d cell_generic
Where: cell_generic is the name of the active generic obtained from the
op:bts #,generic

command entered in Main Procedure Step 5.

5. If generic is the same as the Source OMP, then this sub-procedure is complete.
Go to the next Substep.
If the result is: cell_generic: No such file or directory then install the
same generic as is found on the Source OMP on the Target OMPs system. See
Section 8, of Alcatel-Lucent 9271 EV-DO Radio Network Controller, 401-614-102,
for cell generic installation procedures.
6. Repeat Substeps 2-4 for all cells being moved/removed.
...................................................................................................................................................................................................

On the Source OMP, make a temporary directory where the necessary input and output
files for moving a cell will be stored.
Example: mkdir -p /home/swing/<yyyymmdd>
Where: <yyyymmdd> is the date in year/month/day format.
Result: The temporary directories are created, wherein the input files will be stored

and the cell swing tools will be run.


...................................................................................................................................................................................................

10

Change directory into the temporary directory just created.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-111
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move and Rename a cell (inter-RNC)

Example: cd /home/swing/<yyyymmdd>
Result: The user is in the temporary directory.
...................................................................................................................................................................................................

11

Create the cell_file, sn_file, and network_file input files in the temporary directory
created in Main Procedure Step 9 on the Source OMP. For file formatting instructions,
refer to cell_file file (p. 3-12), sn_file file (p. 3-13), and network_file file
(p. 3-15).
Important! If the directory is already present, the tool will report that this is the
case. If there are problems creating the directory, or if a file (instead of directory)
is already present, errors will print.
Result: The user creates the input files to be used by the cell swing tools.
...................................................................................................................................................................................................

12

Important! The BP tool requires ksh (Korn Shell) to be running.


Cell swing template files may be found in $cstemps after the BP environment is
enabled for the root user.
The temporary directory from Step 9 is now defined as $bpPath.
Enable the BP tools environment.
Example:

1. exec /usr/bin/ksh
2. . BP_user_setup
3. Enter: Y
Result: The BP tools environment is enabled.
...................................................................................................................................................................................................

13

In the temporary directory,


Example:

evdodump -d

evdo_dumpdir -i cell_file

Where:
evdo_dumpdir

Top node of directory structure where BP


unloads data; Use $bpPath variable.

cell_file

user-created cell input file

-c

dumps tables for converged cells

-h

prints the evdoswing command usage


help message

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-112

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move and Rename a cell (inter-RNC)

Result: An explanation of what will be done is displayed and the user is prompted:
Are you ready to run 1xEV-DO Bulk-Provisioning commands via runBP
(y/n)?
...................................................................................................................................................................................................

14

At the prompt,
Enter: Y
Result: The evdodump tool continues running on the OMP.
...................................................................................................................................................................................................

15

When prompted for the Service Node OMP, enter s (for Source).
...................................................................................................................................................................................................

16

For EMS GUI Users: Enter the Service Node ID (SNID) for the OMP. If you do not

know the SNID, access the EMS GUI for the OMP, click the Configuration Data icon,
and click the Service Nodes link.
Important! Once the SNID is entered, the runBP tool is automatically entered and
may run for several minutes, depending on how many cells and Neighbor lists are
being dumped.
Result: The SNID for the OMP is displayed if needed and entered. The runBP tool
then automatically extracts the information needed from the Source system.
Where: -c dumps tables for converged cells.
For OMC-RAN Users or BP Users: Enter the Service Node ID (SNID) for the

OMP. If you do not know the SNID, setup your Bulk Provisioning environment
and then execute the following command:
Enter: runBP -C output stored ServiceNode | grep hdrsnId
...................................................................................................................................................................................................

17

If the Target RNC is on a different OMP, repeat Main Procedure Step 9 - Step 16 on
the Target OMP, then transfer the following files back to the temporary directory
created in Step 9 on the Source OMP , otherwise skip this step:
Example: APXXX.txtNeighborSectorXXXYY.txt
Where: XXX = Target SN ID
YY

= Target Frame ID

...................................................................................................................................................................................................

18

If the cell to be moved/removed has Neighbors on other RNCs or SNs, log into the
Neighbor OMP(s) and enter Main Procedure Step 9 - Step 16 (run evdodump for those
systems, specifying the appropriate SN type (n for Neighbor) in Step 15 .

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-113
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move and Rename a cell (inter-RNC)

Result: The evdodump tool is run for all Neighboring OMPs for which a handoff

can occur.
...................................................................................................................................................................................................

19

Transfer the files generated for those OMPs to the temporary directory (created in
Main Procedure Step 9 ) on the Source OMP.
...................................................................................................................................................................................................

20

On the Source OMP,


Example: evdoswing -d evdo_dumpdir -i cell_file -s sn_file [-v]
Where:
evdo_dumpdir

Top node of directory structure where BP


unloads data; Use $bpPath variable.

cell_file

user-created cell input file

sn_file

user-created service node file

-v

prints further details of evdoswing


process (optional)

Result: The evdoswing script files for deleting and adding the cell components are

created along with the replace scripts for updating the Neighbor sectors on other
RNCs/SNs.
...................................................................................................................................................................................................

21

On the Source OMP, run the evdomkdir tool.


Example:
evdomkdir -d evdo_dumpdir -i network_file -s sn_file

Where:
evdo_dumpdir

Top node of directory structure where BP


unloads data; Use $bpPath variable.

network_file

user-created network input file

sn_file

user-created service node file

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-114

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move and Rename a cell (inter-RNC)

Result: A directory structure is created to be used when transferring the network

files.
...................................................................................................................................................................................................

22

On the Source OMP, go to the Source SNID/Frame ID directory that was created by
evdomkdir.
Example:
cd $bpPath/sXXX/fYY

Where:
XXX
YY

= three-digit value for the Source Service Node ID

= two-digit value for the Source Frame ID

Result: A directory structure to be used when transferring the network files is

created.
...................................................................................................................................................................................................

23

In RRL off mode start a sftp to AP01 as onexev.


In RRL on mode start a sftp to AP01 as login user.
...................................................................................................................................................................................................

24

Go to the dhcp directory and get a copy of the SUNWfiles1_dhcptab file.


Example:

1. cd /var/dhcp
2. get SUNWfiles1_dhcptab
Result: Copy of the Source SUNWfiles1_dhcptab file is obtained.
...................................................................................................................................................................................................

25

Go to the /etc directory and get a copy of the netmasks file.


Example:

1. cd /etc
2. get netmasks
Result: Copy of the Source netmasks file is obtained.
...................................................................................................................................................................................................

26

Exit sftp by entering bye or quit and pressing the Enter key.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-115
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move and Rename a cell (inter-RNC)

...................................................................................................................................................................................................

27

Repeat Main Procedure Step 22 - Step 26 for the Target RNC, replacing all
occurrences of Source with Target.If the Target OMP is different, save the files on the
Target OMP in $bpPath directory and transfer the network files via sftp to the
appropriate directory ($bpPath/s<TargetSNID>/f<TargetFrameID>) on the Source
OMP.
...................................................................................................................................................................................................

28

On the Source OMP,


Enter: cd $bpPath
...................................................................................................................................................................................................

29

On the Source OMP,


Example: evdonetwork -n evdo_dumpdir -i network_file -s sn_file
Where:
evdo_dumpdir

Top node of directory structure where BP


unloads data; Use $bpPath variable.

network_file

user-created network input file

sn_file

user-created service node file

Result: The evdonetwork script files for deleting, creating, and adding the network

components are created.


...................................................................................................................................................................................................

30

Important! Add scripts using either put or mput commands.


Transfer the network deletion scripts (T1, dhcp, netmasks) to the first two FMS-APs of
the Source system.
Where:
XXX
YY

= three-digit value for the Service Node ID

= two-digit value for the Frame ID

In RRL off mode:

1. cd $bpPath/sXXX/fYY
2. Start an sftp to AP01 as onexev
3. cd /app2/swing/<yyyymmdd>/scripts
4. mput *Del* (press the Enter key when prompted)
5. Exit sftp by entering bye or quit; press theEnter key.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-116

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move and Rename a cell (inter-RNC)

6. Repeat Substeps 2 - 5 for AP02, do not transfer the files that begin with netmsk,
as these files are not needed on AP02
7. cd $bpPath
In RRL on mode:

1. cd $bpPath/sXXX/fYY
2. Start an sftp to AP01 as login user account
3. cd /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts
4. Transfer the scripts using sftp
5. Exit sftp by entering bye or quit; press the Enter key
6. Repeat Substeps 2 - 5 for AP02, but enter n for the files that begin with netmsk,
as these files are not needed on AP02
7. cd $bpPath
Result: The network deletion scripts are transferred to the first two FMS-APs in

the cluster.
...................................................................................................................................................................................................

31

Important! If the Target RNC is on a different OMP, the creation and addition
scripts will have to be transferred to the $bpPath directory of the Target OMP.
After that, they can then be transferred to the first two FMS-APs of the Target
system.
Add scripts using either put or mput commands.
Transfer the network addition and creation scripts (T1, dhcp, netmasks) to the first two
FMS-APs of the Target system.
Where:
XXX
YY

= three-digit value for the Service Node ID

= two-digit value for the Frame ID

In RRL off mode:

1. cd $bpPath/sXXX/fYY
2. Start an sftp to AP01 as onexev
3. cd /app2/swing/<yyyymmdd>/scripts
4. Transfer the scripts using sftp
5. Exit sftp by entering bye or quit; press the Enter key
6. Repeat Substeps 2 - 5 for AP02, but enter n for the files that begin with netmsk,
as these files are not needed on AP02
7. cd $bpPath
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-117
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move and Rename a cell (inter-RNC)

In RRL on mode:

1. Log on to AP01 as as login user


2. cd /<home_DIR>/<login_ID>/<yyyymmdd>/scripts
4. Transfer the scripts using sftp
5. Exit sftp by entering bye or quit; press the Enter key
6. Repeat Substeps 2 - 5 for AP02, but enter n for the files that begin with netmsk,
as these files are not needed on AP02
7. cd $bpPath
Result: The network deletion scripts are transferred to the first two FMS-APs in

the cluster.
...................................................................................................................................................................................................

32

Change permissions on the deletion script files (transferred in Step 30 for the Source
RNC).
In RRL off mode:

1. Log on to AP01 as onexev


2. cd /app2/swing/<yyyymmdd>/scripts
3. chmod +x *
4. Log off of AP01
5. Repeat Substeps 1 - 4 for AP02
In RRL on mode:

1. Log on to AP01 as onexev


2. cd /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts
3. chmod +x *
4. Log off of AP01
5. Repeat Substeps 1 - 4 for AP02
Result: The network deletion scripts are made executable.
...................................................................................................................................................................................................

33

Change permissions on the addition script files (transferred in Step 31 for the Target
RNC).
In RRL off mode:

1. Log on to AP01 as onexev


2. cd /app2/swing/<yyyymmdd>/scripts
3. chmod +x *
4. Log off of AP01
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-118

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move and Rename a cell (inter-RNC)

5. Repeat Substeps 1 - 4 for AP02


In RRL on mode:

1. Log on to AP01 as onexev


2. cd /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts
3. chmod +x *
4. Log off of AP01
5. Repeat Substeps 1 - 4 for AP02
Result: The network addition scripts are made executable.
...................................................................................................................................................................................................

34

If they were generated, transfer the Neighbor sector replacement scripts from the
temporary directory on the Source OMP to the temporary directory created on the
Neighboring OMPs where evdodump was run.
Sample filename: NeighborSectorXXXYYReplace<BPfile#>
Where: XXX = three-digit value for the Service Node ID
YY

= two-digit value for the Frame ID

Result: The scripts used to update the Neighbor sectors on Neighboring RNCs/SNs

are transferred.
...................................................................................................................................................................................................

35

Important! If the -V is omitted, the script will be executed.


Do not proceed if any script execution reports an error or is not OK!
On the Source OMP, at the $bpPath directory, run each scripts individually in validate
(-V) mode to confirm syntax.
Example:
runBP -i -O /omp-data/logs/evdotools/runBPmmddyyyy.log -A -V
scriptname

Where:
scriptname

is in the format

<element><SNID><FMSID>Delete<BPfile#>
<element><SNID><FMSID>Add<BPfile#>

(Source)

(Target)

<element><SNID><FMSID>Replace<BPfile#>

(Target)

...................................................................................................................................................................................................

36

Important! If the -V is omitted, the script will be executed.


Do not proceed if any script execution reports an error or is not OK!

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-119
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move and Rename a cell (inter-RNC)

On the Neighbor OMP, run the NeighborSector Replace scripts in validate (-V) mode.
Example:
runBP -i -O /omp-data/logs/evdotools/runBPmmddyyyy.log -A -V

NeighborSectorXXXYYReplace<BPfile#>
Where:

NeighborSectorXXXYYReplace<BPfile#> contains:
XXX
YY

= three-digit value for the Service Node ID

= two-digit value for the Frame ID

...................................................................................................................................................................................................

37

Important! If the -V is omitted, the script will be executed.


Do not proceed if any script execution reports an error or is not OK!
If Target OMP is different than the Source OMP, transfer the Add and Replace scripts
to the Target OMP using sftp, then run the BP Add/Replace scripts in validate (-V)
mode.
Example:
runBP -i -O /omp-data/logs/evdotools/runBPmmddyyyy.log -A -V
scriptname

Where:
scriptname

is in the format

<element><SNID><FMSID>Add<BPfile#>
<element><SNID><FMSID>Replace<BPfile#>
...................................................................................................................................................................................................

38

Remove the CDM using the TICLI. This step must be repeated for all CDMs in a
multiple carrier cell.
Example:
root> TICLI

TICLI> rmv:cell #, cdm <CDM ID>, crc; ucl


Result: The cell is OOS and call traffic diverted.
...................................................................................................................................................................................................

39

Important! Do not proceed if any script execution reports an error or is not OK!
Run the BP Delete scripts, found in the directory, in normal mode (without the -V
command line parameter) in degrowth order on the Source OMP for the cell
components.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-120

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move and Rename a cell (inter-RNC)

Refer to the Degrowth Table, Forms and key fields (p. 3-11) for the degrowth order
on the Source OMP for the cell components. For more information on BP, see
CDMA2000 1xEV-DO EMS Configuration Management Bulk Provisioning,
401-614-325.
Example:
runBP -i -O /omp-data/logs/evdotools/runBPmmddyyyy.log -A <element>
<SNID><FMSID>Delete<BPfile#>

Result: The cell is deleted from the database of the Source RNC.
...................................................................................................................................................................................................

40

Run the deletion scripts as root on the first two Source FMS-APs.
Where:
XXX
YY

= three-digit value for the Service Node ID


= two-digit value for the Frame ID

In RRL off mode:

1. Log on to AP01 as onexev and become the root user(su - root)


2. cd /app2/swing/<yyyymmdd> /scripts
3. Run the t1 deletion script : ./t1fileDelXXXYY
4. Run the dhcp deletion script : ./dhcpDelXXXYY
5. Repeat Substeps 1 - 4 for AP02
6. Log off of AP02
7. Log on to AP01 as root and run the netmasks deletion script:
/flx/ONEXEVc/current/release/tools/cfg/modifyNetmasks DELETE < /app2/
swing/<yyyymmdd>/scripts/netmskDelXXXYY

8. Stop and restart DHCP on AP01 (as root):


/etc/init.d/dhcp stop
/etc/init.d/dhcp start

9. Log off of AP01


10. Log on to AP02 and repeat Substep 8
11. Log off of AP02 and log back onto the OMP as root
In RRL on mode:

1. Log on to AP01 as login user and assume rsysadm role


2. cd /flx/ONEXEVc/current/release/tools/cfg
3. Run the t1 deletion script
./bpproxy /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/t1fileDel
XXXYY
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-121
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move and Rename a cell (inter-RNC)

4. Run the dhcp deletion script


./bpproxy /<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/dhcpDel
XXXYY

5. Repeat Substeps 1 - 4 for AP02


6. Log off of AP02
7. Log on to AP01 as login user and assume rsysadm and run the netmasks
deletion script:
/flx/ONEXEVc/current/release/tools/cfg/modifyNetmasks DELETE < /
<home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/netmskDelXXXYY

8. Stop and restart DHCP on AP01:


/etc/init.d/dhcp stop
/etc/init.d/dhcp start

9. Log off of AP01.


10. Log on to AP02, assume rsysadm role and repeat Substep 8.
11. Log off of AP02 and log back onto the OMP as root.
Result: The network entries for the cell being moved are deleted from the Source

RNC.
...................................................................................................................................................................................................

41

Make any applicable network changes to support the cell swing (for example,
(multiple) router changes between the cell and the Source/Target FMS-APs).
...................................................................................................................................................................................................

42

Important! Do not proceed if any script execution reports an error or is not OK!
Run the BP Add scripts (not in validate mode remove the -V command line parameter)
in growth order on the Target OMP for the cell components.
Refer to the Growth Table, Forms and key fields (p. 3-11) for the growth order on
the Target OMP for the cell components. For more information on BP, see
CDMA2000 1xEV-DO EMS Configuration Management Bulk Provisioning,
401-614-325.
Example: runBP -i -O /omp-data/logs/evdotools/runBPmmddyyyy.log -A
<element><SNID><FMSID>Add<BPfile#>
Result: The cell is added into the database of the Target RNC.
...................................................................................................................................................................................................

43

Run the network addition and creation scripts as root on the first two Target FMS-APs
of the Target OMP.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-122

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move and Rename a cell (inter-RNC)

Where: XXX = three-digit value for the Service Node ID


YY

= two-digit value for the Frame ID

In RRL off mode:

1. Log on to AP01 as onexev and become the root user (su - root)
2. cd /app2/swing/<yyyymmdd>/scripts
3. Run thenetmasks addition script :
/flx/ONEXEVc/current/release/tools/cfg/modifyNetmasks ADD < /app2/
swing/<yyyymmdd>/scripts/netmskAddXXXYY

4. Run the dhcp addition script : ./dhcpAddXXXYY


5. Run the t1 creation script : ./t1fileCrtXXXYY
6. Run the t1 addition script : ./t1entryAddXXXYY
7. Repeat Substeps 1 - 2 and 4 - 6 for AP02
8. Log off AP02
9. Stop and restart DHCP on AP01:
/etc/init.d/dhcp stop
/etc/init.d/dhcp start

10. Log off of AP01


11. Log on to AP02 and repeat Substep 9
12. Log off of AP02 and log back onto the OMP as root
In RRL on mode:

1. Log on to AP01 as user account and assume rsysadm role


2. cd /flx/ONEXEVc/current/release/tools/cfg
3. Run the netmasks addition script
/flx/ONEXEVc/current/release/tools/cfg/modifyNetmasks ADD < /<home_
DIR>/<login_ID>/swing/<yyyymmdd>/scripts/netmskAddXXXYY

4. Run the dhcp addition script


./bpproxy <home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/dhcpAddXXXYY

5. Run the t1 creation script


./bpproxy <home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/
t1fileCrtXXXYY

6. Run the t1 addition script


./bpproxy <home_DIR>/<login_ID>/swing/<yyyymmdd>/scripts/
t1entryAddXXXYY

7. Repeat Substeps 1 - 2 and 4 - 6 for AP02


8. Log off of AP02
9. Stop and restart DHCP on AP01:
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-123
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move and Rename a cell (inter-RNC)

/etc/init.d/dhcp stop
/etc/init.d/dhcp start

10. Log off of AP01.


11. Log on to AP02, assume rsysadm role and repeat Substep 9
12. Log off of AP02 and log back onto the OMP as root
Result: The network entries for the cell being moved are deleted from the Source

RNC.
...................................................................................................................................................................................................

44

If they were generated, run the BP Neighbor Sector Replace scripts on all of the Target
OMPs Neighboring OMPs to update the Neighbor sectors on the Neighbor FMS-APs.
Example: runBP -i -O /omp-data/logs/evdotools/runBPmmddyyyy.log -A

NeighborSector XXXYYReplace<BPfile#>
Where:

NeighborSector XXXYYReplace<BPfile#> contains:


XXX
YY

= three-digit value for the Service Node ID

= two-digit value for the Frame ID

Result: The Neighbor sectors on the Neighboring SNs/OMPs are updated for the
cell that has been moved.
...................................................................................................................................................................................................

45

Restore the 1xEV-DO CDMs from the TICLI. Restore each of the CDMs in case of a
multi-carrier cell.
Example:
TICLI> rst:cell #, cdm <CDM ID>, crc; ucl
...................................................................................................................................................................................................

46

Wait for the cell to come up on the new FMS-AP pair. Monitor the cell status from
whichever interface is appropriate: EMS GUI if the RNC is EMS managed, or the
OMC-RAN GUI if the RNC is managed by the OMC-RAN.
Important! The cell may take up to 30 minutes to come up, as the cell has to
come up either on a new system, with a new name, or both. If the cell does not
come up after 30 minutes, contact WTSC for further assistance.
...................................................................................................................................................................................................

47

Enter the Verify OA&M on moved and/or renamed converged cell (p. 3-129)
procedure.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-124

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Move and Rename a cell (inter-RNC)

...................................................................................................................................................................................................

48

Verify successful cell move by placing a call on the new cell. Start a continuous ping
to a good system, and perform handoffs across the faces of the cell.
Result: A call is placed and intra-cell handoffs are completed.
...................................................................................................................................................................................................

49

If a Neighbor cell is available, start a new session on the moved cell and perform three
active handoffs between the moved cell and a Neighbor cell.
Result: Handoffs between the moved cell and the Neighbor cell are done.
...................................................................................................................................................................................................

50

After 5 days of verified stability, enter the Cleanup of old Cell Swing files (p. 3-134)
procedure.
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-125
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Cell
Swing backout procedure
...................................................................................................................................................................................................................................
Purpose

This procedure moves the stand alone modular cell back to the original FMS-AP pair.
Required skills and personnel

This procedure is best performed by an expert system administrator.


Caveats

This procedure does not cover the removal of newly created dhcp files if the swing
was an intra-RNC swing with network changes.
This procedure does not include backing out applicable network changes to support
the cell swing (for example, (multiple) router changes between the cell and the
Source/Target FMS-APs).

Procedure

Important! Per the impact of 1xEV-DO Gold BCMCS (FID 10862.5) feature the
BCMCS carrier activation must be deactivated before attempting a cell swing. If
not the cell swing will be aborted and the or the result will be an aborted and the
Source RNC Database must be restored.
Perform the following steps:
...................................................................................................................................................................................................

Log on to the Source OMP as root.


...................................................................................................................................................................................................

Follow the database restoration procedure in Alcatel-Lucent 9271 EV-DO Radio


Network Controller, 401-614-102, for both FMS-APs of the Source system.
...................................................................................................................................................................................................

Repeat Step 2 for the Target RNC if an inter-RNC swing or an inter-RNC move and
rename is being backed out.
...................................................................................................................................................................................................

Repeat Step 2 for all Neighboring SNs.


...................................................................................................................................................................................................

Restore the network files (/var/dhcp/SUNWfiles1_dhcptab,


/var/dhcp/SUNWfiles1_A_B_C_D, and /etc/netmasks) on AP01 of the Source system.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-126

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Cell Swing backout procedure

Where: A_B_C_D are determined by searching the Source RNCs netmasks files

for entries for the cell in question.


Example:

1. Assume cell 150, which has two T1s, had been moved to another RNC, and the
move is now being backed out.
2. On the Source RNC:
In RRL off mode login as onexev
cd /app2/swing/<yyyymmdd>/backup
In RRL is enabled login with user account
cd /<home_DIR>/<login_ID>/swing/<yyyymmdd>/backup

3. Enter: grep Cell 150 ./netmasks


Result: output shows all defined network entries for cell 150
10.1.150.0
255.255.255.224 #Cell 150
10.100.19.0
255.255.255.252 #first T1 for Cell 150
10.100.20.0
255.255.255.252 #second T1 for Cell 150
4. The following two additional files from the backup directory would have to be
restored:
Enter:
cp SUNWfiles1_10_100_19_0 /var/dhcp/SUNWfiles1_10_100_19_0
cp SUNWfiles1_10_100_20_0 /var/dhcp/SUNWfiles1_10_100_20_0
...................................................................................................................................................................................................

Restore the network files (/var/dhcp/SUNWfiles1_dhcptab and


/var/dhcp/SUNWfiles1_A_B_C_D, and /etc/netmasks) on AP02 of the Source system.
...................................................................................................................................................................................................

Enter: /flx/ONEXEVc/current/release/tools/cfg/modifyNetmasks SYNC

Result: The netmasks files are synchronized across all FMS-APs of the Source

system.
...................................................................................................................................................................................................

Stop and Start dhcp on AP01 and AP02 of the Source system
1. Stop and restart DHCP on AP01:

assume onexev on lead AP.


In RRL on mode login with user account and then assume rsysadm role on lead AP.
In RRL off mode

2. Stop and restart DHCP on AP01 (as root) :


/etc/init.d/dhcp stop
/etc/init.d/dhcp start

3. Log off of AP01


4. Log on to AP02 and repeat Substep 2.
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-127
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Cell Swing backout procedure

5. Log off of AP02 and log back onto the OMP as root
...................................................................................................................................................................................................

Repeat Main Procedure Step 5 - Step 8 for the Target RNC if an inter-RNC swing or
an inter-RNC move and rename is being backed out, replacing step text Source with
the word Target.
...................................................................................................................................................................................................

10

If backing out an inter-RNC move and/or rename, remove the network files
(/var/dhcp/SUNWfiles1_dhcptab, /var/dhcp/SUNWfiles1_A_B_C_D, and /etc/netmasks)
on AP01 of the Source system.
Where: A_B_C_D are determined by searching the Source RNCs netmasks files

for entries for the cell in question.


Example:

1. Assume cell 150, which has two T1s, had been moved to another RNC, and the
move is now being backed out.
2. Assume cell 150, which has two T1s, had been moved to another RNC, and the
move is now being backed out.
3. On the Target RNC
Enter: cd /app2/swing/<yyyymmdd>/scripts

4. Enter: grep Cell 150 ./t1fileCrtXXXYY


Where:( XXX = SN ID and YY = Frame ID)
Result: output shows the pntadm -C commands run for the cell swing
pntadm -C 10.100.19.0
pntadm -C 10.100.20.0

5. Run the pntadm -C commands on AP01 and AP02 of the Target RNC,
changing the -C (create) to a -R (remove)
pntadm -R 10.100.19.0
pntadm -R 10.100.20.0
...................................................................................................................................................................................................

11

Restore the Neighbor lists on the Neighbor RNCs to is their original settings.
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-128

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Verify
OA&M on moved and/or renamed converged cell
...................................................................................................................................................................................................................................
Purpose

This procedure verifies that OA&M procedures can be successfully entered on a


converged 1xEV-DO cell that has been moved and/or renamed.
When to perform

Perform this procedure after a 1xEV-DO cell has been moved and/or renamed via the
cell swing tools.
Criticality

This procedure ensures that OA&M can be successfully run on a moved 1xEV-DO
cell.
Frequency

Perform this procedure once, for each cell, only after completing a 1xEV-DO cell
move and/or rename.
Required conditions

To perform this procedure successfully, ensure that the following conditions are met
before you begin the procedure:

The 1xEV-DO cell move and/or rename completed successfully

Required skills and personnel

This procedure is best performed by an expert system administrator with extensive


knowledge of the TICLI.
Required tools

To perform this procedure, you require the following tools:

TICLI

Required information

To perform this procedure, you must know the CDMA BTS ID (3G-1x Cell ID on the
EMS GUI, or OMC-RAN) and the 1xEV-DO CDM IDs of the cell that was moved
and/or renamed.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-129
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Verify OA&M on moved and/or renamed converged cell

Related documentation

For detailed information about input and output messages, see CDMA Networks Input
Messages, 401-610-055, and CDMA Network Output Messages, 401-610-057.
Procedure

Important! Per the impact of 1xEV-DO Gold BCMCS (FID 10862.5) feature the
BCMCS carrier activation must be deactivated before attempting a cell swing. If
not the cell swing will be aborted and the or the result will be an aborted and the
Source RNC Database must be restored.
Perform the following steps:
...................................................................................................................................................................................................

Log on to the OMP as root and start the TICLI.


...................................................................................................................................................................................................

Enter:OP:CELL BTS_ID

Where:
BTS_ID

is the ID of the BTS.

Result: The status of the moved cell is displayed.


...................................................................................................................................................................................................

Enter:OP:CELL BTS_ID, CDM CDM_ID

Where:
BTS_ID

is the ID of the BTS

CDM ID

is the ID of the CDM

Result: The status of the specified CDM is displayed.


...................................................................................................................................................................................................

Enter:OP:CELL BTS_ID , AMP

Where:
BTS_ID

is the ID of the BTS.

Result: The status of the amplifiers associated with the moved cell is displayed.
...................................................................................................................................................................................................

Enter: OP:CELL BTS_ID, GENERIC

Where:
BTS_ID

is the ID of the BTS.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-130

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Verify OA&M on moved and/or renamed converged cell

Result: The status of the cell generic/generics installed on the moved cell is/are

displayed.
...................................................................................................................................................................................................

Enter:OP:CELL BTS_ID, ALARM

Where:
BTS_ID

is the ID of the BTS.

Result: The status of any alarmed components associated with the moved cell is
displayed.
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-131
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Verify
service measurements reporting
...................................................................................................................................................................................................................................
Purpose

This procedure verifies that service measurements (SM) for a moved/renamed stand
alone modular cell are reported on the new RNC.
When to perform

Perform this procedure after the top of the second hour after a 1xEV-DO cell has been
moved.
Criticality

This procedure ensures that SM associated with a moved/renamed cell are correctly
being reported on their new RNC.
Frequency

Perform this procedure only once after the 1xEV-DO cell has been moved/renamed.
Required conditions

To perform this procedure successfully, ensure that the following conditions are met
before you begin the procedure:

The 1xEV-DO cell was successfully moved/renamed

Required skills and personnel

This procedure is best performed by an expert system administrator with extensive


knowledge of service measurements.
Required information

To perform this procedure, you must know the new location of the moved cell.
Related documentation

For descriptions of service measurements for the Ethernet Interface Node (EIN), see
CDMA Network Service Measurements, 401-610-135.
Procedure

Important! Per the impact of 1xEV-DO Gold BCMCS (FID 10862.5) feature the
BCMCS carrier activation must be deactivated before attempting a cell swing. If
not the cell swing will be aborted and the or the result will be an aborted and the
Source RNC Database must be restored.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-132

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Verify service measurements reporting

Perform the following steps:


...................................................................................................................................................................................................

Place a call on the moved/renamed cell, establish a continuous ping and perform five
sets of active handoffs across all the faces of the cell. Terminate the session.
Result: A call is placed and five sets of active handoffs are done.
...................................................................................................................................................................................................

Place a call on the moved/renamed cell, establish a continuous ping and perform five
sets of active handoffs across all the faces of the cell. Terminate the session.
Result: A call is placed and five sets of active handoffs are done.
...................................................................................................................................................................................................

Let the AT go idle and then perform five sets of idle handoffs between all the faces of
the cell.
Result: Five sets of active handoffs are done.
...................................................................................................................................................................................................

A few minutes after the top of the hour, verify that service measurements (SM) for
both active and idle handoffs were appropriately pegged for the moved/renamed cell.
Result: Active and idle SM pegs are reported in the appropriate SM file.
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-133
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Cleanup
of old Cell Swing files
...................................................................................................................................................................................................................................
Purpose

This procedure is used to remove the temporary files and directories created and used
during a cell move/rename.
When to perform

Perform this procedure after a 1xEV-DO cell has been successfully moved/renamed
and the temporary files/directories are no longer needed.
Criticality

This procedure ensures that disk space is conserved.


Frequency

Perform this procedure only once after the 1xEV-DO cell has been moved/renamed.
Procedure

Important! Per the impact of 1xEV-DO Gold BCMCS (FID 10862.5) feature the
BCMCS carrier activation must be deactivated before attempting a cell swing. If
not the cell swing will be aborted and the or the result will be an aborted and the
Source RNC Database must be restored.
Perform the following steps:
...................................................................................................................................................................................................

Log on to the OMP as root.


...................................................................................................................................................................................................

Log on to the database FMS-AP.


...................................................................................................................................................................................................

Remove swing file by entering:cd /app2/DBbackuprm -f swing <yyyymmdd>


...................................................................................................................................................................................................

Log on to AP01.
...................................................................................................................................................................................................

Remove the files and directories from within the temporary directories:
rm -fr /app2/swing/<yyyymmdd>/scripts/
rm -fr /app2/swing/<yyyymmdd>/backup/

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-134

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Cleanup of old Cell Swing files

...................................................................................................................................................................................................

Log on to AP02.
...................................................................................................................................................................................................

Remove the files and directories from within the temporary directories:
rm -fr /app2/swing/<yyyymmdd>/scripts/
rm -fr /app2/swing/<yyyymmdd>/backup/
...................................................................................................................................................................................................

Log off of the FMS-APs (returning to the OMP).


...................................................................................................................................................................................................

On all applicable OMPs (Source, Target, Neighboring), remove the temporary directory
used to store the input and output files:
rm -fr /home/swing/<yyyymmdd>
...................................................................................................................................................................................................

10

Log off of the OMP.


END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-135
Issue 5, May 2008
See notice on first page

Cell Swing Capability for EVolution Data Optimized


(1xEV-DO)

Moving Base Stations from R1SR Based 1xEV-DO RNC APs


to
Universal Cabinet (UNC)-Based 1xEV-DO RNC APs
...................................................................................................................................................................................................................................
Purpose

The procedures to move the base stations and to describe the impact of UNC based
1xEV-DO RNC Infrastructure, FID 12885.1, feature, are found in CDMA2000
1xEV-DO Radio Access System Planning and Implementation Guide, 401-614-101 and
Alcatel-Lucent 9271 EV-DO Radio Network Controller, 401-614-102.
Important! Only UTPs are supported in UNCs (that is no 690s or 752s).

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

3-136

4 DMA 3G-1x EVolution Data


C
Optimized (1xEV-DO) Handoff
Matrix (HOM) Tool and Related
Features

Overview
...................................................................................................................................................................................................................................
Purpose

This chapter describes the following optional features in CDMA2000 1xEV-DO


networks. Unique Feature Identifiers (FIDs) are assigned to each feature:

1xEV-DO Handoff Matrix (HOM) Tool (FID 12146.0)


BC0/BC1 Dual Band 1xEV-DO (FID 8219.7)
1xEV-DO Support for Multi-Carrier Coverage Differences (FID 8219.9)
Support for Multiple 1xEV-DO Carriers - Inter-frequency Handoff (IFHO) (FID
8219.11)
Six Sector Modular Cell 4.0B with Mixed 1x and 1xEV-DO (8882.2)

Feature summary

The following summarizes the features covered in this document.


1xEV-DO HOM Tool feature (FID 12146.0)

The 1xEV-DO HOM Tool feature provides service providers with important
information to assist in 1xEV-DO neighbor list adjustments needed to improve handoff
performance. The 1xEV-DO Handoff Matrix tool outputs the number and types of
active session handoffs from all the sectors on a Service Node (SN) to every other
sector to which a handoff occurred. These handoffs are collected and reported by the
in-service Radio Network Controllers (RNCs) in the SN. The data can be
post-processed by a tool or customer-developed tools, such as Excel macros.
BC0/BC1 Dual Band 1xEV-DO (FID 8219.7)

The BC0/BC1 Dual Band 1xEV-DO feature enables the support of BC0/BC1 dual band
in the 1xEV-DO system. BC0 is the cellular (850) frequency band and BC1 is the PCS
(1900) frequency band.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
4-1
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

Overview

1xEV-DO Support for Multi-Carrier Coverage Differences (FID 8219.9)

The 1xEV-DO Support for Multi-Carrier Coverage Differences feature accommodates


coverage differences across band classes for 1xEV-DO in multi-carrier cells.
Support for Multiple 1xEV-DO Carriers - IFHO feature (FID 8219.11)

The Support for Multiple 1xEV-DO Carriers feature provides support for multiple
1xEV-DO carriers - inter-frequency handoff (IFHO) and provides the capability to
perform handoff of an active 1xEV-DO connection from one carrier to a different
carrier. With IFHO, a mobile user moving into a sector that does not have the current
service carrier can be handed off to a new carrier without dropping the connection,
providing a smooth transition.
Six Sector Modular Cell 4.0B with Mixed 1x and 1xEV-DO (FID 8882.2)

The Six Sector Modular Cell 4.0B with Mixed 1x and 1xEV-DO feature addresses the
6-Sector Modular Cell 4.0B which supports up to 6 1x carriers or up 5 1x carriers and
1 1xEV-DO carrier at a power of up to 16W/carrier.
Impacts on user interfaces

The 1xEV-DO HOM Tool feature and related features affect the user interfaces that are
listed in the following table.
Feature

User interface

Feature impact

1xEV-DO HOM Tool feature


(FID 12146.0)

Element Management
System (EMS) or
OMC-RAN
configuration
management

None

Service measurements

None

Automatic Message
Accounting (AMA)
subsystem

None

Technician Interface
(TI) (input/output
messages)

None

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

4-2

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

Overview

Feature

User interface

Feature impact

BC0/BC1 Dual Band


1xEV-DO (FID 8219.7)

EMS or OMC-RAN
configuration
management

None

Service measurements

None

AMA subsystem

None

TI (input/output
messages)

None

EMS or OMC-RAN
configuration
management

None

Service measurements

See Service measurements:


1xEV-DO Support for
Multi-Carrier Coverage
Differences (FID 8219.9)
(p. 4-33)

AMA subsystem

None

TI (input/output
messages)

None

EMS or OMC-RAN
configuration
management

None

Service measurements

None

AMA subsystem

None

TI (input/output
messages)

None

EMS or OMC-RAN
configuration
management

None

Service measurements

None

AMA subsystem

None

TI (input/output
messages)

None

1xEV-DO Support for


Multi-Carrier Coverage
Differences (FID 8219.9)

Support for Multiple


1xEV-DO Carriers - IFHO
feature (FID 8219.11)

Six Sector Modular Cell


4.0B with Mixed 1x and
1xEV-DO (FID 8882.2)

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
4-3
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

Overview

To obtain technical support, documentation, and training or submit feedback

The Online Customer Support (OLCS) web site (http://support.lucent.com/) provides


access to technical support, related documentation, related training, and feedback tools.
The site also provides account registration for new users.
Contents
Availability

4-5

Prerequisites

4-6

Feature description: 1xEV-DO HOM Tool feature (FID 12146.0)

4-9

Feature description: BC0/BC1 Dual Band 1xEV-DO (FID 8219.7)

4-12

Feature description: 1xEV-DO Support for Multi-Carrier Coverage


Differences (FID 8219.9)

4-14

Feature description: Support of Multiple 1xEV-DO Carriers - IFHO


feature (FID 8219.11)

4-18

evstarthom command

4-19

evdisphom command

4-22

Feature description: Six Sector Modular Cell 4.0B with Mixed 1x and
1xEV-DO (FID 8882.2)

4-30

Feature interactions

4-32

Service measurements: 1xEV-DO Support for Multi-Carrier Coverage


Differences (FID 8219.9)

4-33

Issues and caveats

4-34

Implementing the 1xEV-DO HOM feature (FID 12146.0)

4-37

Activating the 1xEV-DO feature (FID 12146.0)

4-38

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

4-4

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

Availability
...................................................................................................................................................................................................................................
Release availability

The following table identifies the AMPS/PCS software releases in which the 1xEV-DO
HOM Tool feature and related features are available.
Feature

Available in

1xEV-DO HOM Tool (FID 12146.0)

Releases 25.0 and later

BC0/BC1 Dual Band 1xEV-DO (FID 8219.7)

Releases 28.01 and later

1xEV-DO Support for Multi-Carrier Coverage


Differences (FID 8219.9)

Releases 30.0 SU-0002 and later

Support for Multiple 1xEV-DO Carriers - IFHO


(FID 8219.11)

Releases 26.0 and later

Six Sector Modular Cell 4.0B with Mixed 1x and


1xEV-DO (FID 8882.2)

Releases 27.0 and later

Market availability

The 1xEV-DO HOM Tool feature and related features are available in the following
markets:
Feature

Available in

1xEV-DO HOM Tool (FID


12146.0)

1xEV-DO markets only

BC0/BC1 Dual Band 1xEV-DO


(FID 8219.7)

1xEV-DO markets only

1xEV-DO Support for


Multi-Carrier Coverage
Differences (FID 8219.9)

1xEV-DO markets only

Support for Multiple 1xEV-DO


Carriers - IFHO (FID 8219.11)

1xEV-DO markets only

Six Sector Modular Cell 4.0B


with Mixed 1x and 1xEV-DO
(FID 8882.2)

1xEV-DO markets only

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
4-5
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

Prerequisites
...................................................................................................................................................................................................................................
Introduction

The 1xEV-DO HOM Tool feature and related features have the following prerequisites.
Supported technologies
1xEV-DO HOM Tool feature (FID 12146.0)

The 1xEV-DO HOM Tool feature is supported in the following air-interface


technologies:

1xEV-DO

BC0/BC1 Dual Band 1xEV-DO (FID 8219.7)

The BC0/BC1 Dual Band 1xEV-DO feature is supported in the following air-interface
technologies:

1xEV-DO

1xEV-DO Support for Multi-Carrier Coverage Differences (FID 8219.9)

The 1xEV-DO Support for Multi-Carrier Coverage Differences feature is supported in


the following air-interface technologies:

1xEV-DO

Support of Multiple 1xEV-DO Carriers - IFHO feature (FID 8219.11)

The Support of Multiple 1xEV-DO Carriers - IFHO feature is supported in the


following air-interface technologies:

1xEV-DO

Six Sector Modular Cell 4.0B with Mixed 1x and 1xEV-DO (FID 8882.2)

The Six Sector Modular Cell 4.0B with Mixed 1x and 1xEV-DO feature is supported
in the following air-interface technologies:

1xEV-DO

HLR configuration
1xEV-DO HOM Tool feature (FID 12146.0)

The 1xEV-DO HOM Tool feature is independent of the Home Location Register
(HLR) configuration.
BC0/BC1 Dual Band 1xEV-DO (FID 8219.7)

The BC0/BC1 Dual Band 1xEV-DO feature is independent of the Home Location
Register (HLR) configuration.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

4-6

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

Prerequisites

1xEV-DO Support for Multi-Carrier Coverage Differences (FID 8219.9)

The 1xEV-DO Support for Multi-Carrier Coverage Differences feature is independent


of the Home Location Register (HLR) configuration.
Support of Multiple 1xEV-DO Carriers - IFHO feature (FID 8219.11)

The Support of Multiple 1xEV-DO Carriers - IFHO feature is independent of the Home
Location Register (HLR) configuration.
Six Sector Modular Cell 4.0B with Mixed 1x and 1xEV-DO (FID 8882.2)

The Six Sector Modular Cell 4.0B with Mixed 1x and 1xEV-DO feature is independent
of the HLR configuration.
Software requirements
1xEV-DO HOM Tool feature (FID 12146.0)

The 1xEV-DO HOM Tool feature requires Release 25.0 or later. The 1xEV-DO HOM
Tool feature is not dependent on other features.
The 1xEV-DO HOM Tool feature FAF must be active. For more information, see
Activating the 1xEV-DO feature (FID 12146.0) (p. 4-38).
BC0/BC1 Dual Band 1xEV-DO (FID 8219.7)

The BC0/BC1 Dual Band 1xEV-DO feature requires Release 28.01 or later. The
BC0/BC1 Dual Band 1xEV-DO feature is not dependent on other features.
The BC0/BC1 Dual Band 1xEV-DO feature covers the testing of 1xEV-DO BC0/BC1
dual band capability (Support for Multiple 1xEV-DO Carriers - Enhancements FID
8219.2).
1xEV-DO Support for Multi-Carrier Coverage Differences (FID 8219.9)

The 1xEV-DO Support for Multi-Carrier Coverage Differences feature requires


Releases 30.0 SU-0002 or later.
The 1xEV-DO Support for Multi-Carrier Coverage Differences feature builds on the
functionality included in the following features. See 1xEV-DO Support for
Multi-Carrier Coverage Differences (FID 8219.9) (p. 4-32) for details.

Support for Multiple 1xEV-DO Carriers (FID 8219.1)


BC0/BC1 Dual Band 1xEV-DO (FID 8219.7)

Support of Multiple 1xEV-DO Carriers - IFHO feature (FID 8219.11)

The Support of Multiple 1xEV-DO Carriers - IFHO feature requires Release 26.0 or
later. The Support of Multiple 1xEV-DO Carriers feature is not dependent on other
features.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
4-7
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

Prerequisites

Six Sector Modular Cell 4.0B with Mixed 1x and 1xEV-DO (FID 8882.2)

The Six Sector Modular Cell 4.0B with Mixed 1x and 1xEV-DO feature requires ECP
Release 27.0 or later. The 1xEV-DO HOM Tool feature is not dependent on other
features.
General software requirements

The following notes apply to the 1xEV-DO Handoff Matrix Tool feature and to related
features:
Important! The users login must be in the ECP group on the OMP.
Important! To run HOM on the RNCs, the RNCs must have been configured by
the SMconfig tool.
Hardware requirements
1xEV-DO HOM Tool feature (FID 12146.0)

The 1xEV-DO Handoff Matrix Tool feature runs only on a 1xEV-DO Operations and
Maintenance Platform (OMP).
BC0/BC1 Dual Band 1xEV-DO (FID 8219.7)

The BC0/BC1 Dual Band 1xEV-DO feature runs only on a 1xEV-DO Operations and
Maintenance Platform (OMP).
1xEV-DO Support for Multi-Carrier Coverage Differences (FID 8219.9)

The 1xEV-DO Support for Multi-Carrier Coverage Differences feature runs only on a
1xEV-DO Operations and Maintenance Platform (OMP).
Support of Multiple 1xEV-DO Carriers - IFHO feature (FID 8219.11)

The Support of Multiple 1xEV-DO Carriers - IFHO feature runs only on a 1xEV-DO
Operations and Maintenance Platform (OMP).
Six Sector Modular Cell 4.0B with Mixed 1x and 1xEV-DO (FID 8882.2)

The Six Sector Modular Cell 4.0B with Mixed 1x and 1xEV-DO feature runs only on a
1xEV-DO Operations and Maintenance Platform (OMP).

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

4-8

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

Feature description: 1xEV-DO HOM Tool feature (FID


12146.0)
...................................................................................................................................................................................................................................
Introduction

The following information describes the functionality, benefits, and operation of the
1xEV-DO HOM Tool feature.
Functionality

The 1xEV-DO Handoff Matrix Tool feature allows service providers to collect
information about the number and types of handoffs and handoff attempts that occur in
their systems.
Important! There are some limitations as to which handoff counts are listed in the
output. See Issues and caveats (p. 4-34). Also, only handoffs for active sessions
are reported. Idle transfers and handoffs for idle sessions are not reported.
Benefits

Analysis of the handoff counts that the 1xEV-DO Handoff Matrix Tool feature
generates can help a service provider to:

determine whether the system meets current needs


plan for future needs

How the feature operates

For each cell in the SN, this feature counts the number of handoff completions and
handoff attempts from each cell:sector to cell:sector combination for which handoffs
are attempted. This feature also reports undeclared neighbors. Undeclared neighbors are
pilots (or PN Offsets) that an AT detects that are not in the current set of the strongest
pilots for the AT. Some undeclared neighbors may need to be added to a sectors
neighbor list if ATs report them often and they are not currently on the sectors
neighbor list. For a user-specified period of time, a single query obtains the individual
counts for each type of handoff that the Service Node supports.
The 1xEV-DO Handoff Matrix Tool is implemented as UNIX commands. A 1xEV-DO
Handoff Matrix Tool session can be started manually or with the use of a cron job. The
session length is variable in increments of one minute from a minimum of ten minutes
up to a maximum session length of 24 hours. The default session length is ten minutes.
Important! The maximum duration for a HOM study is 24 hours. However, if you
plan to schedule a daily cron job to run back-to-back HOM studies, be sure to set
the study duration to a length that allows time to collect the data from one study
before starting the next study. In this case, it is recommended that HOM studies be
no longer than 23.5 hours in length. This allows 30 minutes to collect and
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
4-9
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

Feature description: 1xEV-DO HOM Tool feature (FID


12146.0)

aggregate the HOM data from the RNCs before starting the next study. The
evstarthom command will fail if evdisphom is not completed by the time
evstarthom runs.
The session begins with zeroed counts. The data output goes to a single file in a
default directory. Both successful and attempted handoffs are pegged. Sessions are
stopped automatically, per input arguments, or can be stopped early with an input
command. Using the evstarthom command, a HOM study is started by a user at the
Operations and Maintenance Platform (OMP); the data collected during the study is
accumulated at each RNC. When the study is complete and the user runs the
evdisphom command on the OMP, the OMP transfers the RNC output files to the
OMP and aggregates the data into a single file. The output file generated for a study is
kept on the OMP for a maximum of ten days unless overwritten or removed earlier by
the user.
evstarthom command

The evstarthom command initiates collection of handoff matrix data on a Service


Node.
Important! For detailed information on the use of the evstarthom command, see
evstarthom command (p. 4-19).
evdisphom command

The evdisphom command stops a collection session and/or cause a request for the
OMP to retrieve the HOM data from each RNC for aggregation into a single output
file.
Important! For detailed information on the use of the evdisphom command, see
evdisphom command (p. 4-22).
Service provider perspective

The 1xEV-DO Handoff Matrix Tool feature requires that:

To run either the evstarthom command or the evdisphom command, the service
provider must either use the root login or a login that is a member of the ECP
group.
The service provider must have the Feature Activation File (FAF) entry for the
1xEV-DO Handoff Matrix Tool feature activated.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

4-10

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

Feature description: 1xEV-DO HOM Tool feature (FID


12146.0)

The service provider must also have service measurement collection set up properly
or the HOM tool will not work properly. SMconfig is used to set up this
information. Please make sure that the frame number used in the SMconfig tool is
the same as the AP Frame Logical ID listed on the AP Frame Configuration page
on the EMS GUI. One can also determine this FMS Frame ID from the FMS
Frame Configuration data. For more information on using SMconfig, see document
CDMA2000 1xEV-DO Radio Networks Controller Application Processor
Operations, Administration, and Maintenance (OA&M)., 401-614-102.
Enter the evstarthom command on the OMP to start the counting of handoffs.
Enter the evdisphom command on the OMP to collect the data into a single output
file on the OMP.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
4-11
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

Feature description: BC0/BC1 Dual Band 1xEV-DO (FID


8219.7)
...................................................................................................................................................................................................................................
Introduction

The following information describes the functionality, benefits, and operation of the
BC0/BC1 Dual Band 1xEV-DO feature.
Functionality

The BC0/BC1 Dual Band 1xEV-DO feature enables the support of BC0/BC1 dual band
in the 1xEV-DO system. It covers the testing of 1xEV-DO BC0/BC1 dual band
capability ( Support for Multiple 1xEV-DO Carriers - Enhancements FID8219.2) for
General Availability. BC0 is the cellular (850) frequency band and BC1 is the PCS
(1900) frequency band.
Benefits

The BC0/BC1 Dual Band 1xEV-DO feature offers two carriers dual band with one
carrier on BC0 and the other carrier on BC1. Dual band is provided in the same cell
site with multiple BTS frames and each BTS frame operates in either BC0 or BC1.
The following BTS types are applicable:

Modular Cell 4.0, Modular Cell 4.0B


Compact 4.0
HD 4.0, HDB
Modular Cells 1 to 3

For Modular Cells 1, 2 and 3, dual band will be provided using Modular Cell 4.0 (or
Modular Cell 4.0B) as the growth frame:

Modular Cell(s) 1, 2 or 3 supporting BC0


Modular Cell 4.0 (or Modular Cell 4.0B) supporting BC1

How the feature operates

As Revision A (Rev. A) functions have been offered with the BC0/BC1 Dual Band
1xEV-DO (FID 8219.7) after the inclusion of the dual band software (Support for
Multiple 1xEV-DO Carriers - Enhancements FID 8219.2) feature. The BC0/BC1 Dual
Band 1xEV-DO (FID 8219.7) feature includes the testing of dual band BC0/BC1 using
Rev. A carriers. The following combinations of carrier types are supported

Rev 0 (BC0), Rev 0 (BC1)

Rev 0 (BC0), Rev A (BC1)


Rev A (BC0), Rev 0 (BC1)
Rev A (BC0), Rev A (BC1)

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

4-12

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

Feature description: BC0/BC1 Dual Band 1xEV-DO (FID


8219.7)

Load balance at call connection set up is supported to handle the dual band cell
configuration. Inter-frequency Hand Off (IFHO) is supported. Cross-band hashing will
be supported, allowing the dual band ATs to hash to either band. With cross-band
hashing, the channel list information sent on the control channel includes carriers of
both band classes.
To set up a cell for dual band, different radio resources need to be assigned for BC0
and BC1 and the band class of each 1xEVDO carrier needs to be entered at the EMS.
BC0/BC1 Dual Band 1xEV-DO is a standard feature and is not controlled by
FAF/QFAF.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
4-13
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

Feature description: 1xEV-DO Support for Multi-Carrier


Coverage
Differences (FID 8219.9)
...................................................................................................................................................................................................................................
Introduction

The following information describes the functionality, benefits, and operation of the
1xEV-DO Support for Multi-Carrier Coverage Differences feature.
Functionality

The 1xEV-DO Support for Multi-Carrier Coverage Differences feature addresses call
processing during System Acquisition, Paging, and Connection Setup when carriers on
the accessed sector have different coverage areas.
Benefits

The 1xEV-DO Support for Multi-Carrier Coverage Differences feature is expected to


improve system performance in DO multi-carrier cells by the following options:

turning off cross band hashing which increases the chances that Access Terminals
(ATs) will successfully idle on their assigned carrier, where there is a coverage
difference for carriers in different bands in the same sector.
sending synchronous messages on either the last seen band or on both bands in
dual band cells when cross band hashing is turned off, the improvements
associated with turning off cross band hashing are realized without requiring that
ATs always be paged on both bands, minimizing the impact on paging resources.
application of a distance threshold before doing cross-carrier assignment reduces
the failure rate at connection setup, where there is a coverage difference for
different carriers on the same sector (either due to border/contiguous carrier
differences or due to band class differences).
providing both a maximum distance threshold and a minimum pilot Ec/Io threshold
on the accessed carrier before considering cross-band carrier assignment,
connection setup failures due to cross-band assignment in dual band cells are
reduced.
two cross-band load differentials, one for RF and one based on users makes it
possible to favor same-band cross-carrier assignment over cross-band assignment
when load balancing in dual-band cells. Their names are Cross Band RF load
Differential and Cross Band Load Differential.
Outer Setup Distance Threshold: This threshold sets up a concentric circle outside
of the Inner Tier which restricts TCA to carriers for which AT is within this
distance. The originating carrier is preferred.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

4-14

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

Feature description: 1xEV-DO Support for Multi-Carrier


Coverage Differences (FID 8219.9)

How the feature operates

In multi-carrier cells, carrier coverage can differ for border versus contiguous carriers
and for carriers in different band classes. The 1xEV-DO Support for Multi-Carrier
Coverage Differences feature accommodates multi-carrier coverage differences for
1xEV-DO single band and dual band cells during System Acquisition, Paging, and
Connection Setup.
The feature includes:

An option to turn off cross band hashing per sector in dual band cells.
When cross-band hashing is on for a sector, carriers from both band classes are
included in the channel list of the Sector Parameters Message for each carrier on
that sector. ATs execute cross-band hashing to determine the assigned carrier for
idling.
When cross-band hashing is off for a sector, only same-band carriers are included
in the channel list of the Sector Parameters Message for each carrier on that sector.
ATs execute the same-band hashing to determine the assigned carrier for idling.
Paging changes to support cross-band hashing disable in dual band cells, and adds
up to 8 paging attepnts.
When cross-band hashing is on for a sector, the AN executes cross-band hashing to
select the carrier on which to send synchronous messages to the AT.
When cross-band hashing is off for a sector, the AN delivers synchronous
messages over one or both bands in a dual band cell. Translations are provided to
select the paging option (last seen band or both bands) for each paging attempt.
Distance-based carrier assignment for connection setup in single band and dual
band cells.
If the Load Balancing Method parameter is set to Originating_Carrier,
connection setup is on the carrier on which the Connection Request message is
received, providing the number of users on that originating carrier is less than the
MaxAllowedUser parameter. If the number of users on the originating carrier
exceeds the MaxAllowedUser parameter, then other carriers are considered. The
1xEV-DO Support for Multi-Carrier Coverage Differences feature applies a distance
threshold check before considering other carriers, so that the AT is assigned to a
non-originating carrier only if the distance from the sector to the AT is within the
distance threshold for that carrier. The distance threshold is translatable.
If the Load Balancing Method parameter is set to Number_of_Active_Users,
connection setup is on the originating carrier providing two criteria are met:
the number of users on the originating carrier is less than the MaxAllowedUser
parameter, and
the originating carrier has fewer users than other carriers on the sector by at
least a translatable Load Differential.
Outer Setup Distance Threshold

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
4-15
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

Feature description: 1xEV-DO Support for Multi-Carrier


Coverage Differences (FID 8219.9)

The Inner Circle is defined by the Inner Tier Distance Threshold and Inner Tier
Ec/Io Threshold. If the signal strength and round trip delay of a call meet these
criteria then any carrier can be selected. If these criteria are not met (one or
both) then the call is restricted to the originating carrier if the distance is within
the Outer Setup Threshold. If the original carrier is blocked or unavailable then
carrier selection is restricted to non-originating carriers within the Outer Setup
Distance Threshold.
The thresholds are:
- Cross Carrier Channel Assignment : Inner Tier Distance Threshold
- Cross Carrier Channel Assignment : Inner Tier Minimum Ec/Io Threshold
- Cross Carrier Channel Assignment : Outer Setup Distance Threshold
- Cross Band Assignment : RF load differential offset
- Cross Band Assignment : Load differential offset (in units of users)
The 1xEV-DO Support for Multi-Carrier Coverage Differences feature applies a
distance threshold check before considering other carriers for the Load Differential
check or for traffic channel assignment. Only non-originating carriers for which the
distance from the sector to the AT is within the distance threshold for that carrier
are considered. The distance threshold is translatable.
Distance and pilot strength threshold checks on the accessed carrier, before
allowing cross-band carrier assignment for connection setup in dual band cells.
Carriers in the non-accessed band are considered for cross-band assignment on
connection setup only when the distance from the sector to the AT is within a
maximum distance threshold for cross-band assignment and the Ec/Io measurement
on the accessed carrier is above a minimum Ec/Io threshold for cross-band
assignment. The cross-band distance and pilot strength thresholds are translatable.
A cross-band load differential parameter to favor same-band cross-carrier
assignment over cross-band assignment when load balancing across carriers in dual
band cells.
If the Load Balancing Method parameter is set to Number_of_Active_Users, a
cross-band load differential is used to increase the effective loading (measured in
number of active users) for cross-band carriers. The cross-band load differential is
translatable.
Service Measurements to track cross band assignments and confirmations for both
AT-initiated and Access Network (AN)-initiated connection setup attempts.

Service provider perspective

The 1xEV-DO Support for Multi-Carrier Coverage Differences feature is a standard


feature. Sevice providers control of the feature includes:

Control of cross-band hashing (on/off) per sector.


Selection of paging option (last seen band or both bands) per paging attempt in
dual band cells when cross band hashing is off.
Specification of an outer distance threshold (per sector, per carrier group) to qualify
non-originating carriers for traffic channel selection.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

4-16

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

Feature description: 1xEV-DO Support for Multi-Carrier


Coverage Differences (FID 8219.9)

Specification of a maximum distance and minimum Ec/Io threshold (per sector, per
carrier group) on the accessed carrier before allowing cross-band carrier assignment

Specification of two cross-band load differentials (per sector, per carrier group) to
increase the effective loading on cross band carriers.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
4-17
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

Feature description: Support of Multiple 1xEV-DO Carriers IFHO


feature (FID 8219.11)
...................................................................................................................................................................................................................................
Introduction

The following information describes the functionality, benefits, and operation of the
Support of Multiple 1xEV-DO Carriers - IFHO feature.
Functionality

The Support of Multiple 1xEV-DO Carriers - IFHO feature provides support for
multiple 1xEV-DO carriers - inter-frequency handoff (IFHO) and provides the
capability to perform handoff of an active 1xEV-DO connection from one carrier to a
different carrier. With IFHO, a mobile user moving into a sector that does not have the
current service carrier can be handed off to a new carrier without dropping the
connection, providing a smooth transition.
Benefits

This feature provides improved session transfer time, reduces service interruption, and
improves the end-user experience for real-time applications such as video and audio
streaming.
Service provider perspective

This feature adds two new fields to the 1xEV-DO HOM output from the evdisphom
command. These fields include counts for hard add completes and hard add attempts.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

4-18

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

evstarthom
command
...................................................................................................................................................................................................................................
Abstract

The evstarthom command is used to start a 1xEV-DO HOM study.


Syntax
evstarthom [-h][-t DURATION]

Description

The evstarthom command initiates collection of handoff matrix data from all the
RNCs associated with the OMP on which the command is run. Only one job may be
run per Service Node at any time.
Options

The following options are available:


-t DURATION is the duration of the study in minutes. The default is 10 minutes, which

is also the minimum time for the study. The maximum time is 1440 minutes (24
hours).
-h Displays help information.
Examples
evstarthom

This use of the command starts an EVDO HOM study for 10 minutes.
evstarthom -t 120

This use of the command starts an EVDO HOM study for 2 hours.
evstarthom -h

This version of the evstarthom command displays the usage message (help
information) for the user.
System Response

The initial response to this command is to the terminal of the requesting device. This
indicates to the user whether the job could be successfully initiated.

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
evstarthom
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
EVDO Handoff Matrix Session ID:xxxx
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
EVDO Handoff Matrix Collection Started on RNC(s): x y
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
4-19
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

evstarthom command

Important! This message is output after the session has been successfully started
on any of the associated RNCs so no errors or warnings appear in this output
message. Any further details on failures to start the job on subsequent RNCs, or
errors incurred after the job has initiated, are noted in the resultant output files.
Diagnostics

If the study starts successfully on all RNCs, evstarthom exits with an exit code of
zero. If the study starts successfully on at least one RNC, but not all RNCs, the
command exits with an exit code of one. In both cases, a list of RNCs on which the
study started is sent to the standard output and some error messages are sent to the
error file. In addition, a session ID which identifies the study is written to the standard
output. This session ID is used to access an error file that may be created in the
/omp-data/logs/hom/evdo_summary_files directory to describe the errors in more detail.
The name of the file is evstarthom.<session-ID>.error. This file contains the list of
RNCs on which the study could not be started. For each RNC, the failure reason is
displayed.
The file status.<session-ID> in /omp-data/logs/hom/evdo_summary_files is used to
show the progress of the EVDO HOM study with start time, duration, session-ID, stop
time, and so on.
If the study fails to start on all RNCs, evstarthom exits with a non-zero exit code.
The following table lists some of the possible exit codes and their descriptions.
Table 4-1
Error Code

Error Codes for evstarthom Command


Message

Study completed successfully

Study started on at least one RNC but not all RNCs

Failed to start the study at all RNCs

Invalid arguments

Unable to attach to shared memory

EVDO HOM feature is not active.

Another evstarthom or evdisphom process is running.

Another study is currently running. Wait for the study to be


completed and use the evdisphom command to collect the data later
or run evdisphom -s now to stop the study early and collect the
data.

No RNC is configured for HOM.

20

Other errors

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

4-20

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

evstarthom command

Sample file outputs

The following is the format of the error file generated by the evstarthom command
when the command cannot start the study on all RNCs.

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
SESSION:<Session-ID>
1234567890123456789012345678901212345678901234567890123456789
ERROR_DATE:<Day> <Month and Date> <Time> <Year>
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
HOM_START_FAIL_RNCS:<A list of RNCs on which the study failed to
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
start>
1234567890123456789012345678901212345678901234567890123456789
HOM_START_SKIP_RNCS:<A
list of RNCs that the study skipped because
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
each RNC is unequipped>
1234567890123456789012345678901212345678901234567890123456789
HOM_START_STATUS:<status> where <status> indicates if the start
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
command failed completely or not.
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
The following is the format of the status file generated by the evstarthom command:

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
HOM_START_IN_PROGRESS
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
HOM_DURATION:<duration in minutes>
1234567890123456789012345678901212345678901234567890123456789
HOM_START_TIME:<time in seconds>
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
HOM_DATE_START_TIME:<time in string format>
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
HOM SESSION:<session-ID>
1234567890123456789012345678901212345678901234567890123456789
HOM_START_FRAME:<x>:<start-status> Where <x> is the RNC Number and
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
<start-status> is SUCCESS, FAIL, or SKIP
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
HOM_START_FRAME:<y>:<start-status> Where <y> is the RNC Number and
1234567890123456789012345678901212345678901234567890123456789
<start-status> is SUCCESS, FAIL, or SKIP
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
HOM_START_COMPLETED
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Important! If one of the RNCs connected to the OMP is on Release 24, the
evstarthom command just times out. No warning is given to the user that the RNC
is Release 24.0. There is just no response from the frame.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
4-21
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

evdisphom
command
...................................................................................................................................................................................................................................
Abstract

The evdisphom command stops a HOM session and/or causes a request to retrieve the
HOM data from each RNC for aggregation into a single output file of the name
specified by the -o option or the default file name. Depending on which options are
selected, the command can just gracefully stop the HOM session or stop the session
and collect the data. This command can also just collect the HOM data from the RNCs
but this can only be executed after the evdisphom -s command is executed or the
session has stopped on its own when the study timer expires.
Syntax
evdisphom [-o <output_file_name>] [-fshw]

Description

The evdisphom command causes a request for the OMP to retrieve the HOM data
from each RNC for aggregation into a single output file of the name specified by the
-o option or the default file name.
The aggregated data is available in a file that is prepared and stored on the OMP
within 30 minutes of issuing the command. The default format for the output data is
tabular format.
Options
-o <output_file_name>

where <output_file_name> is the name of the output file.


This option cannot be used with the -s option unless the -w option is also used.
-f

Display the data only separated by colons. This option cannot be used with the -s
option unless the -w option is also used.
-h

Displays the usage of the evdisphom command.

-s

Stops a study gracefully. No collection of data occurs, however, unless this option is
used along with the -w option.
-w

This option, used with -s option, stops the HOM session and collects the data.

Examples
evdisphom

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

4-22

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

evdisphom command

This use of the evdisphom command collects 1xEV-DO HOM data and fails
immediately if data is not available immediately. The output is in table format and the
name of the output file is evhom_table.<Session ID>. The
evhom_table.<SessionID>.error file is located at
/omp-data/logs/hom/evdo_summary_files.
Use of the evdisphom command with no options only works when a HOM session has
already ended, either on its own (by its timer expiring) or by the user having
previously run evdisphom -s to stop a study early.
Important! The service provider may see a failure message after issuing the
evdisphom command. In this case you need to issue this command again. The
reason for this failure may be due to issuing the evdisphom command too quickly
after stopping a study gracefully ( evdisphom s). It is recommended to wait a
minute or so before issuing evdisphom after stopping the study.
evdisphom -o myOutPut

This use of the evdisphom command collects 1xEV-DO HOM data and fails
immediately if data is not available immediately. The output is in table format and the
name of the output file is myOutPut. The name of the error file is myOutPut.error. This
command only works when a HOM session has already been stopped.
evdisphom -s

This use of the evdisphom command stops an 1xEV-DO study gracefully without
collecting the data.
evdisphom -s -w

This use of the evdisphom command stops an 1xEV-DO study gracefully and waits for
data for 15 minutes. The output is in table format and the name of the output file is
evhom_table..<Session ID>.. The name of the error file is evhom_table.<Session
ID>.error.. The file is stored on the OMP in /omp-data/logs/hom/evdo_summary_files.
evdisphom -w

This use of the evdisphom command waits for data to be collected in 15 minutes. It
fails immediately if the study takes longer than 15 minutes to be completed.
evdisphom -s -w -f

This use of the evdisphom command stops an 1xEV-DO study gracefully and waits for
data for 15 minutes. The output is in colon-delimited format and the name of the
output file is evhom_raw.<Session ID>. The name of the error file is
evhom_raw.<Session ID>.error.
evdisphom -o myOutPut -s -w -f

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
4-23
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

evdisphom command

This use of the evdisphom command stops an EVDO study gracefully and waits for
data for 15 minutes. The output is in raw format and the name of the output file is
myOutPut. The name of the error file is myOutPut.error.
evdisphom -h

This use of the evdisphom command displays the usage message for the user.
System Responses

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
evdisphom
1234567890123456789012345678901212345678901234567890123456789
Collection of Files in Progress; Please Wait
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
EVDO Handoff Matrix Session ID:<session ID>
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
EVDO Handoff Matrix Collected on RNC(s): <RNC #>
1234567890123456789012345678901212345678901234567890123456789
evdisphom -s
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Study stopped on all RNCs
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
EVDO Handoff Matrix Session ID:<session ID>
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
EVDO Handoff Matrix Collection Stopped on RNC(s): <List of RNC #s>
1234567890123456789012345678901212345678901234567890123456789
evdisphom -f -o file2
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Collection of Files in Progress: Please Wait
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
EVDO Handoff Matrix Session ID:<session ID>
1234567890123456789012345678901212345678901234567890123456789
EVDO Handoff Matrix Collected on RNC(s): <RNC #>
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Important! It may be up to 15 minutes after the Please Wait message appears
before data is available.

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
evdisphom -w -s
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Study stopped on all RNCs
1234567890123456789012345678901212345678901234567890123456789
EVDO Handoff Matrix Session ID:<session ID>
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
EVDO Handoff Matrix Collection Stopped on RNC(s): <RNC #>
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Collection of Files in Progress; Please Wait
1234567890123456789012345678901212345678901234567890123456789
EVDO Handoff Matrix Session ID:<session ID>
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
EVDO Handoff Matrix Collected on RNC(s): <RNC #>
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Important! It may be up to 15 minutes after the Please Wait message appears
before data is available.
Diagnostics

If the command collects data from all RNCs, evdisphom is successful and exits with
an exit code of zero. If the command collects data from at least one RNC but not all,
the command exists with an exit code of one. The output file has the list of RNCs that
participated in the study. If one or more RNCs do not provide any data, the message
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

4-24

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

evdisphom command

WARNING: Incomplete data

is written to the end of the output file. A list of RNCs


participating in the collection along with the session ID of the study is also sent to the
standard output. More detail on errors found is in the error file.
If the data in the output file is not complete due to missing data for an Adjunct
Processor (AP), invalid data in an AP file, maximum number of records for the output
file, and other reasons, the message WARNING: Incomplete data is written to the end
of the file.
If the command fails to collect data from all of the RNCs, evdisphom exits with an
error code of
The output file will contain only this message
WARNING: Collecting data failed for all RNCs.

If the user specifies an output


file and the output file exists, the existing output file is overwritten in any successful
or failure case without any warning.
If the command is not successful to stop or collect data from all RNCs, an error file is
created. The error file contains more information about RNCs for which no data was
collected. The ftp.<session-ID> log file has information about transferring data files
from APs to the OMP. This file can be found at /ompdata/logs/hom/evdo_summary_files.
The file status.<session-ID> is used to show the progress of an 1xEV-DO HOM
study. It shows start time, duration, session-ID, stop time, and so on. This file can be
found at /omp-data/logs/hom/evdo_summary_files.
The following table lists some of the possible exit codes and their descriptions.
Table 4-2
Error Code

Error Codes for evdisphom Command


Message

Study completed successfully

Study stopped or data is collected from at least one RNC but not all
RNCs

Failed to stop or collect HOM data from any RNCs

Invalid arguments

Unable to attach to shared memory

EVDO HOM feature is not active.

Another evstarthom or evdisphom process is running.

Cannot create or write to output file.

No RNC is configured for HOM.

10

Study is in progress and data is not available.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
4-25
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

Table 4-2

Error Codes for evdisphom Command

Error Code

evdisphom command

(continued)

Message

20

Other errors

Output data format

Colon-delimited output data format (-f option)


The output file consists of a header line and records. The output file may have a
warning line, if there is an error such as incomplete data, at the end of the file. The
first line of the output is the header. The header has the following format:

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
EV-DO|HOMATRIX|<REL>|<START_DATE>|<STOP_DATE>|<SM>|<RNC_LIST>
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
The following table describes the variables in the header:
Table 4-3

Header Variables for evdisphom Command

Variable
<REL>

Description

HOM release number

Example
26.0

<START_DATE>

The start date and start time of the study


in a YYYYMMDDHHMMSS format

20050104142045

<STOP_DATE>

The stop date and stop time of the study


in YYYYMMDDHHMMSS format

20050104143045

<SN>
<RNC_LIST>

The Service Node ID


The list of RNC IDs participating in the
study (separated by |)

12
1|3|4

The header line for the above example looks like:

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
EVDO|HOMATRIX|26.0|20050104142045|20050104143045|12|1|2|4
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
There is one record for each FROM SECTOR in the service node that reported any
adds, drops, or attempts. The first two fields are the FROM cell ID and sector. The rest
of the record contains repeating groups of fields, one set for each TO SECTOR. The
format of the records is:

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

4-26

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

evdisphom command

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
<FROM_CELL>:<FROM_SECTOR>:<TO_SECTOR_DECL>:<TO_CELL_PNOFFSET>:
1234567890123456789012345678901212345678901234567890123456789
<TO_SECTOR_CHAN>:<TO_ACTIVE_IP>:<SOFT_ADD_COMPLETE>:
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
<SOFT_ADD_ATTEMPT>:<SOFT_DROP_COMPLETE>:<SOFT_DROP_ATTEMPT>:
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
<HARD_ADD_COMPLETE>:<HARD_ADD_ATTEMPT>:
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
The following table describes the variables in the record:
Table 4-4

Record Variables for evdisphom Command

Variable
<FROM_CELL>

<FROM_SECTOR>
<TO_SECTOR_DECL>

<TO_CELL_
PNOFFSET>

<TO_SECTOR_CHAN>

<TO_ACTIVE_IP>

Description

Example

This provides the originating cell number


of HOM
(1-maximum number of cells
supported)

This provides the originating sector


number of HOM ( 1-6).

This is a flag indicating whether the To


cell-sector is a declared neighbor; y =
declared neighbor, n= undeclared
neighbor.

For a sector that is a declared neighbor,


cell number
(1-maximum number of cells
supported) is reported. For an undeclared
neighbor sector, PNOffset is reported
( 0-511).
For a sector that is a declared neighbor,
sector number ( 1-3) is reported. For an
undeclared neighbor sector, channel
number ( 0-2047) is reported.
For a sector that is a declared neighbor,
AP IP address is reported. For an
undeclared neighbor sector, this field does
not apply - NA is reported.

or
n
112

135.5.143.6

<SOFT_ADD_
COMPLETE>

This provides the soft/softer handoff


completions (legs added) for declared
neighbor sectors.

<SOFT_ADD_
ATTEMPT>

This provides the soft/softer handoff


attempts for declared and undeclared
neighbor sectors.

12

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
4-27
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

Table 4-4

Record Variables for evdisphom Command

Variable

evdisphom command

(continued)

Description

Example

<SOFT_DROP_
COMPLETE>

This provides the soft/softer legs dropped


for declared neighbor sectors; NA is
reported for undeclared neighbor sectors.

12

<SOFT_DROP_
ATTEMPT>

This provides the soft/softer legs


attempted to be dropped for declared
neighbor sectors; NA is reported for
undeclared neighbor sectors.

13

<HARD_ADD_
COMPLETE>

Hard add complete count for declared or


_ (NA for table format) for undeclared
neighbor.

14

<HARD_ADD_
ATTEMPT>

Hard add attempt count for declared or


undeclared neighbor.

15

The following is a sample record:

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1:1:Y:112:2:135.5.143.6:12:12:13:14:15:134:Y:112:3:153.5.7.123:4:11:
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
10:204
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
The WARNING line is used to specify that an error occurs during the collection of the
data. The format is:

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
WARNING:<warning-text>
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
An example of the <warning-text> is Incomplete data.
Important! It is possible that the output file does not have header and records due
to a problem such as collecting data has failed from all RNCs. In such a case, the
output file has only the WARNING line.
Output data format (table format)

The output file consists of a header section and a table of records. The output file may
have a WARNING line if there is an error such as incomplete data. The header
contains the same variables as described in output data format for the -f option above.
The table contains the same fields as described for the -f option above, the only
difference being they are displayed in an easier-to-read table format.
The following is an example of the output data in table format:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

4-28

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

evdisphom command

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
EVDO HANDOFF MATRIX RELEASE 26.0
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Start Date: 05/24/2005 Start Time: 14:11:27
1234567890123456789012345678901212345678901234567890123456789
Stop Date: 05/24/2005 Stop Time: 14:21:27
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Service Node ID: 1
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Reporting RNC(s): 1, 6
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
FROM FROM

TO

CELL SECT SECT


DECL

DECL: DECL:
TO
CELL

TO
SECT

UNDEC: UNDEC:
PN

TO

ADD

ADD

DROP

DROP

HARD

HARD

ACTIVE COMPL ATTEMP COMPL ATTEMP COMPL ATTEMP


AP
IP

CHAN#

OFFSET

132

132

10.1.9.1

132

132

10.1.9.1

Important! It is possible that the output file does not have header and records due
to a problem such as collecting data has failed from all RNCs. In such a case, the
output file has only the WARNING line.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
4-29
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

Feature description: Six Sector Modular Cell 4.0B with Mixed


1x
and 1xEV-DO (FID 8882.2)
...................................................................................................................................................................................................................................
Introduction

The following information describes the functionality, benefits, and operation of the
Six Sector Modular Cell 4.0B with Mixed 1x and 1xEV-DO feature.
Functionality

The Six Sector Modular Cell 4.0B with Mixed 1x and 1xEV-DO feature extends the
operation of the 6-sector Modular Cell 4.0B to support more 1x carrier traffic than in
its initial release (FID 8882.0). In addition, it supports a mixture of 1x carriers and one
1xEV-DO Rev 0 carrier.
It is offered in the PCS Band and supports the following configurations in one-cabinet:

up to six (6) 1x carriers per sector transmitting up to 16W/carrier, or


up to five (5) 1x carriers and one (1) 1xEV-DO carrier per sector simultaneously
transmitting up to 16W/carrier.

A 6-sector Cell transmitting 8W/carrier requiring less amplifiers than one transmitting
16W, can support more carriers, for example, a single outdoor cabinet will support 7
1x carriers.
Benefits

This feature provides improved session transfer time, reduces service interruption, and
improves the end-user experience for real-time applications such as video and audio
streaming.
How the feature operates

A set of External Voice Terminal Assembly/Vacuum Regulator (EVT/EVR) and/or


Signaling Bus - 1xEV-DO Modem (SB-EVM) are required for 1xEV-DO operation.
The 1xEV-DO Rev 0 carrier baseband signals are generated for two 3-sector groups
using 2 sets of EVT/EVR or 2 SB-EVMs (FID 12078.17) or a combination of the 2,
though RF transmitted in the same radio for each sector. As a result, softer hand-off is
supported across 3 sectors of each group, for example, across a and across ae, not
across sectors of the 2 groups. Customers will have the choice of which sectors will be
assigned to a particular card based on the actual Cell antenna sectorization. For
example, actual adjacent sectors ae can be assigned to 1 SB-EVM while a is
assigned to the other SB-EVM.
The 1x carriers will continue to support 2-way softer hand-offs across all 6 sectors.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

4-30

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

Feature description: Six Sector Modular Cell 4.0B with


Mixed 1x and 1xEV-DO (FID 8882.2)

Due to its high capacity, it is recommended that this Cell be provisioned with URC-IIs
(8973.1). Also, a dedicated Controller for 1xEV-DO Revision 0 (Rev. 0) processing is
required when it is simultaneously supported with 1x.
Service provider perspective

This feature adds two new fields to the 1xEV-DO HOM output from the evdisphom
command. These fields include counts for hard add completes and hard add attempts.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
4-31
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

Feature
interactions
...................................................................................................................................................................................................................................
Introduction

The 1xEV-DO HOM Tool feature does not interact with other features.
Important! The 1xEV-DO HO) Tool feature shares the same OMP with the CDMA
(HOM Tool feature, but there is no interaction between the 1xEV-DO HOM tool
and the CDMA HOM tool.
1xEV-DO Support for Multi-Carrier Coverage Differences (FID 8219.9)

The 1xEV-DO Support for Multi-Carrier Coverage Differences feature builds on the
functionality included in the following features:

Support for Multiple 1xEV-DO Carriers (FID 8219.1)


BC0/BC1 Dual Band 1xEV-DO (FID 8219.7)

Support for Multiple 1xEV-DO Carriers (FID 8219.1)

The Support for Multiple 1xEV-DO Carriers feature enhances the support of multiple
carrier feature in 8219.0. It allows more than one 1xEV-DO carrier to be supported on
a URC1, and supports additional frequency band. It also supports multiple carriers on
URC2.
BC0/BC1 Dual Band 1xEV-DO (FID 8219.7)

The BC0/BC1 Dual Band 1xEV-DO feature enables the support of BC0/BC1 dual band
in the 1xEV-DO system. BC0 is the cellular (850) frequency band and BC1 is the PCS
(1900) frequency band.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

4-32

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

Service measurements: 1xEV-DO Support for Multi-Carrier


Coverage
Differences (FID 8219.9)
...................................................................................................................................................................................................................................
Introduction

The 1xEV-DO Support for Multi-Carrier Coverage Differences feature affects the
following categories of services measurements.
1xEV-DO Support for Multi-Carrier Coverage Differences (FID 8219.9)

The 1xEV-DO Support for Multi-Carrier Coverage Differences feature affects the
service measurements that are identified in Table 4-5, 1xEV-DO Support for
Multi-Carrier Coverage Differences Feature: New Service Measurements (p. 4-33).
Table 4-5

1xEV-DO Support for Multi-Carrier Coverage Differences Feature:


New Service Measurements

Service measurement
subcategory

Count abbreviation

Count name

SECT-CARR-HDRC

AN_INIT_CONN_ATTMPT_ AN-Initiated Connection


DIFF_BAND_RCVD
Requests Different Band
Received

SECT-CARR-HDRC

AN_INIT_CONN_ATTMPT_ AN-Initiated Connection


DIFF_BAND_SENT
Requests Different Band
Sent

SECT-CARR-HDRC

AT_INIT_CONN_ATTMPT_ AT-Initiated Connection


DIFF_BAND_RCVD
Requests Different Band
Received

SECT-CARR-HDRC

AT_INIT_CONN_ATTMPT_ AT-Initiated Connection


DIFF_BAND_SENT
Requests Different Band
Sent

SECT-CARR-HDRC

CROSS_BAND_ATTMPT_
RCVD_TCC_RCVD

Cross-Band Connection
Attempts Received Established Connections

SECT-CARR-HDRC

CROSS_BAND_ATTMPT_
SENT_TCC_RCVD

Cross-Band Connection
Attempts Sent - Established
Connections

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
4-33
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

Issues
and caveats
...................................................................................................................................................................................................................................
Introduction

The 1xEV-DO HOM Tool feature is subject to the following special caveats.
Caveats
Caveat 1 - FROM CELL and FROM SECT Data

In 1xEV-DO, the AT sends a Route Update Message to all of the active sectors in the
HOM data file. The sector that receives this message first is the sector that is listed as
the FROM cell-sector. As a result, the same handoff pattern may show different FROM
cell-sectors. Also, when a sector is dropped, the FROM cell-sector may be the sector
that is dropped.
Consider a call that is active on Cell 132, Alpha Sector. The call is then in soft handoff
between Cell 132-Alpha and Cell133-Beta. Cell 132-Alpha is then dropped and the call
is just active on Cell 133-Beta.
FROM FROM

TO

CELL SECT SECT


DECL

DECL: DECL:
TO
CELL

TO
SECT

UNDEC: UNDEC:
PN

TO

ADD

ADD

DROP

DROP

HARD

HARD

ACTIVE COMPL ATTEMP COMPL ATTEMP COMPL ATTEMP


AP
IP

CHAN#

OFFSET

132

133

10.1.9.1

132

132

10.1.9.1

In each case, the Route Update Message for adding Cell 133-Beta Sector is received
by Cell 132-Alpha Sector. The dropping of the leg is somewhat different. In the first
case, the Route Update Message to drop Cell 132-Alpha Sector is received by Cell
133-Beta Sector first. In the second case, the Route Update Message to drop Cell
132-Alpha Sector is received by Cell 132-Alpha Sector first. Either is acceptable
output.
Caveat 2 - Output from Handoffs between Service Nodes

Handoff-matrix data is only collected on a particular service node which has the
Overhead Manager (OHM) controlling the Access Terminal (AT) session. This control
of the AT session is only transferred to another OHM during an idle handoff. It is not
transferred during an active handoff.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

4-34

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

Issues and caveats

The output from the Handoff-matrix tool on a particular service node only lists
handoffs where the FROM cell-sector is associated with an AP that is on the same
Service Node where the data is being collected. Data where the FROM cell-sector is
associated with an AP that is on another service node does not appear in the output
table. The other service node does not collect this handoff data until an idle transfer of
the AT occurs to that particular service node. As a result, certain handoff data might
not be captured by any OMP.
The data can possibly vary for the same call pattern if it is a handoff between service
nodes and the Route Update Message goes to different Cell-Sectors. Consider the
following:

Cell 132: Sector Alpha is associated with an AP on Service Node 1.


Cell 133: Sector Beta is associated with an AP on Service Node 2.

The call is initiated on cell 132 - Sector Alpha. The call goes into soft handoff between
Cell 132 - Sector Alpha and Cell 133 - Sector Beta. In this case, Cell 132 - Sector
Alpha is dropped and the cell is only active on Cell 133 - Sector Beta.
FROM FROM

TO

CELL SECT SECT


DECL

DECL: DECL:
TO
CELL

TO

PN

CHAN#

SECT
UNDEC: UNDEC:

TO

ADD

ADD

DROP

DROP

HARD

HARD

ACTIVE COMPL ATTEMP COMPL ATTEMP COMPL ATTEMP


AP
IP

OFFSET

132

FROM FROM

TO

CELL SECT SECT


DECL

133

DECL: DECL:
TO
CELL

TO
SECT

UNDEC: UNDEC:
PN

10.2.5.1

TO

ADD

ADD

DROP

DROP

HARD

HARD

ACTIVE COMPL ATTEMP COMPL ATTEMP COMPL ATTEMP


AP
IP

CHAN#

OFFSET

132

133

10.2.5.1

132

132

10.1.9.1

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
4-35
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

Issues and caveats

In the first output example, the service provider only sees the add and not the drop. In
this particular example, the line for the drop should have been:
133

132

10.1.9.10

This is because the from cell sector is Cell 133-Sector Beta which is associated with
an AP that is on service nodeIt is not included in the table since no idle handoff has
occurred between the AP on service node 1 and the AP on service nodeBoth tables are
acceptable and possible outputs for this scenario.
Caveat 3 - Frame Number versus Frame ID

The R24 SM Configuration Data in the customer sites may have Frame Number
instead of Frame ID for each frame configured by SMconfig. In this case, 1xEV-DO
HOM tool will fail. The customer should verify that the data in the SM Configuration
Data is correct in regard to the value of Frame ID for each frame. The customer can
verify the data by using the SMconfig tool to display the SM configuration data. If
they are not correct, the customer needs to update the frame ID of each frame using
the SMconfig tool.
Important! In order to determine the correct Frame ID for a frame, see document
CDMA2000 1xEV-DO RAS Planning and Implementation Guide., 401-614-101.
The Frame ID for AP x is x over 10 plus 1.
Caveat 4 - Search window size can be expanded temporarily to collect more
Undeclared Neighbors

Varying the remaining set search window size in configuration data can be helpful in
identifying undeclared neighbors because the AT is then able to demodulate additional
multi-paths.
To clean up undeclared neighbors, the service provider can open up the remaining set
search window on a cluster of cells for a few days while he or she runs EV-DO HOM
studies. When the investigation and any updates to the neighbor lists are complete, the
user can then set the window size back to its value before the study.
Important! Setting this window size to a high value may impact drop call
performance due to the additional searches the AT needs to do for the remaining
pilots. The more time the AT spends searching for remaining pilots, the less it
spends on active and neighbor pilots. Hence, if a neighbor pilot appears rapidly, for
example, it could impact drop performance since the active legs may deteriorate
before the neighbor can be added to the active set.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

4-36

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

Implementing
the 1xEV-DO HOM feature (FID 12146.0)
...................................................................................................................................................................................................................................
Overview

To implement the 1xEV-DO HOM Tool feature, perform the following procedure:
Activating the 1xEV-DO feature (FID 12146.0) (p. 4-38)
Activating the 1xEV-DO feature (FID 12146.0) (p. 4-38)

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
4-37
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Handoff Matrix (HOM) Tool and Related Features

Activating
the 1xEV-DO feature (FID 12146.0)
...................................................................................................................................................................................................................................
Purpose

This procedure activates the 1xEV-DO HOM Tool feature in a CDMA2000t 1xEV-DO
network.
Procedure

Perform the following steps:


...................................................................................................................................................................................................

Ask your account executive to activate the following entry in your Feature Activation
File (FAF):
EV-DO Handoff Matrix
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

4-38

5 er Call Measurement Data


P
(PCMD) for CDMA 3G-1x
EVolution Data Optimized
(1xEV-DO)

Overview
...................................................................................................................................................................................................................................
Purpose

This optional feature description describes the Per Call Measurement Data (PCMD) for
CDMA 3G-1x Evolution Data Optimized (1xEV-DO) and Enhancements to EVDO Per
Call Service Measurements optional features in CDMA2000 1xEV-DO networks.
Feature summary

The following summarizes the features covered in this document and their PCMD
impact:
PCMD for 1xEV-DO

The PCMD for 1xEV-DO feature provides PCMD that supports the collection of data
for High-Speed Packet Data service for the EV-DO platform. The feature collects
EV-DO PCMD data and makes that data available in files on the OMP-FX v.2, and in
near real-time data streams. (The RNC sends EV-DO PCMD records in blocks to the
OMP-FX, rather than send each record individually. The RNC sends a block of EV-DO
PCMD messages when a maximum has been reached or when a timer has expired.)
The PCMD for 1xEV-DO feature does not provide post-processing tools.
Enhancements to EVDO Per Call Service Measurements

The Enhancements to EVDO Per Call Service Measurements feature provides


enhancements to 1xEV-DO PCMD to support Basic and Enhanced Rev A EV-DO,
general PCMD, and service measurements. The enhancements include collection and
processing of Route Update Message (RUM) data, also, the collection of Personality
Switch and QoS flow reservation data is included as part of Rev. A support.
New service measurements are added as part of this feature. For detailed information
on these service measurements, refer to, CDMA2000 1xEV-DO Service
Measurements, 401-614-326.

....................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-1
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Overview

EVDO Service Measurements Enhancement - Phase 2

The EVDO Service Measurements Enhancement - Phase 2 feature provides 1xEV-DO


Service Measurement counts to improve performance assessment of 1xEV-DO
networks:

Session setup related connection attempt denial/failure


Average forward link user throughput for Best Effort traffic
Average number of handoff legs
Connections rejected/blocked due to overload
Busy slots for Best Effort (BE) and Expedited Forwarding (EF)
Scheduler eligible users for all users and Expedited Forwarding (EF) users
Control Channel slots usage
Active Usage for Best Effort traffic
New PCMD fields to identify cross-carrier activities
Expand the RTD field in PCMD to store either 4-chip RTD value or 1/8-chip RTD
value and add a new field indicate the granularity

Customer Critical Performance Measurements and Translations - Phase 3

The Customer Critical Performance Measurements and Translations - Phase 3 feature


allows fast turnaround to address field issues that require Service Measurements,
PCMD fields, or Translations in EVDO. It also provides for management of Critical
SMs, PCMD fields, and Translations that were used in prior release. This feature is
supported by DO PCMD by the establishment of permanent sets of spare data fields in
each type of DO PCMD record - Primary, Flow and RUM records.
Feature Identifier (FID)

A unique Feature Identifier (FID) is assigned to each feature. This document supports
the following features:

PCMD for 1xEV-DO, FID 12269.0. (Release 26.0)


Enhancements to EVDO Per Call Service Measurements, FID 12269.2
EVDO Service Measurements Enhancement - Phase 2, FID 12370.1
Customer Critical Performance Measurements and Translations - Phase 3, FID
12766.2

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-2

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Overview

Impacts on user interfaces

The PCMD for 1xEV-DO affects the user interfaces that are listed in the following
table.
User interface

Feature impact

Element Management System


(EMS) configuration management

For information on configuring parameters related


to this feature, see Implementing the feature
(p. 5-73).

Service measurements

For information on configuring parameters related


to this feature, see Service measurement (SM)
counts (p. 5-15)

Technician Interface (TI)


(input/output messages)

None

Contents
Availability

5-4

Prerequisites

5-5

PCMD terminology

5-6

Feature description

5-7

Issues and caveats

5-10

How data is delivered to the OMP-FX v.2

5-11

Post-processing tool guidelines

5-15

Description of 1xEV-DO per-connection performance data delivered to


the OMP-FX v.2

5-26

Per-connection performance data output examples from the OMP-FX v.2

5-47

How data is accessed from the OMP-FX v.2

5-63

Using telnet to retrieve EV-DO PCMD data

5-64

Using FTP to retrieve EV-DO PCMD data

5-66

Using the EV-DO PCMD viewer to view EV-DO PCMD data

5-68

EV-DO PCMD viewer command format and syntax

5-70

Feature interactions

5-72

Implementing the feature

5-73

Activating the PCMD for 1xEV-DO feature

5-74

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-3
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Availability
...................................................................................................................................................................................................................................
Release availability

The features described in this chapter have the following release availability:

The PCMD for 1xEV-DO feature is available in Releases 26.0 and later.
The Enhancements to EVDO Per Call Service Measurements feature is available in
1xEV-DO Release 27.0 and later.
EVDO Service Measurements Enhancement - Phase 2 feature is available in
1xEV-DO Release 30.0 and later.
Customer Critical Performance Measurements and Translations - Phase 3 feature is
available in 1xEV-DO Release 30.0 and later.

Market availability

The features listed in this chapter are available in all regions.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-4

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Prerequisites
...................................................................................................................................................................................................................................
Introduction

The PCMD for 1xEV-DO feature has the following prerequisites.


Supported technologies

The PCMD for 1xEV-DO feature is supported in the following air-interface


technologies:

1xEV-DO

Software requirements

The PCMD for 1xEV-DO feature requires DO-RNC Release 26.0 or later. The PCMD
for 1xEV-DO feature is not dependent on other features.
In Release 28.0 and later, 1xEV-DO PCMD is dependent on the following feature for
Rev. A support:

Inter and Intra-RNC Handoff Enhancement (FID 12078.7)


Application Based Quality of Service (QoS) Support for HRPD Rev. A (FID
12078.9)

Hardware requirements

The PCMD for 1xEV-DO feature requires use of the Netra-440-based OMP-FX v.2.
In Release 27.0 and later, 1xEV-DO PCMD requires the service provider to have the
following 1xEV-DO Rev. A capable hardware:

SBEVM for OneBTS


SBEVMm for Modular Cells 1, 2, and 3

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-5
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

PCMD
terminology
...................................................................................................................................................................................................................................
Introduction

The following information defines terms that are specific to Per Call Measurement
Data (PCMD).
PCMD event

A PCMD event is an event of interest to call processing and for troubleshooting call
processing, such as, sessions, connections, and transfers. In Release 27.0, PCMD
Events also include Personality Change Attempts.
PCMD interval

The PCMD interval is the time between the occurrence of a PCMD event (when the
PCMD record is created) and the time the PCMD record is complete and ready to be
sent to the OMP-FX. A PCMD record exists and is open for the duration of a PCMD
interval. For a particular Service Node, a PCMD records for a connection exists for the
duration of that connection. A PCMD Session record lasts only for the time that is
needed to negotiate and begin a session, rather than for the entire duration of the
session.
Important! PCMD records uses Greenwich Mean Time (GMT) time.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-6

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Feature
description
...................................................................................................................................................................................................................................
Introduction

The following information describes the functionality, benefits, and operation of the
PCMD for 1xEV-DO feature.
Functionality

The PCMD for 1xEV-DO feature collects selected data for connections and sessions
and reports this data via the OMP-FX v.2. The data includes connection technology
details, resource usage, and connection failure information.
In Release 27.0 and later, the service provider can choose to include Route Update
Message (RUM) data from the first and last RUM that is received during each PCMD
interval, or the service provider can choose to include no RUM data in the PCMD
record. This feature expands the data that is extracted from the RUM messages to
include the fields shown in Table 5-18, DO PCMD RUM Fields (p. 5-42).
In Release 28.0 adds Flow Data which allows the collection information for up to eight
Flows as part of the PCMD record. If data from more than eight flows is received, a
duplicate record is created that contains the rest of the flow data information.
Benefits

The PCMD for 1xEV-DO feature provides valuable data that can help to monitor,
maintain, and improve the performance and capacity for the EVDO systems.
How the feature operates

The PCMD for 1xEV-DO feature collects performance data that relates to the EV-DO
Access Terminal (AT) connection path for data connections. Overall performance of the
packet data application is not within the scope of the PCMD for 1xEV-DO feature.
For details on how the PCMD for 1xEV-DO feature operates, see How data is
delivered to the OMP-FX v.2 (p. 5-11).
The interval during which data is exchanged, previously referred to as a call in other
systems, need not necessarily involve a calling party, called party, or caller in the
EV-DO system. Terminology to clarify this distinction is found in Table 5-1, EV-DO
terminology (p. 5-7).
Table 5-1

EV-DO terminology

3G1X

EV-DO

call

connection

origination

AT-Initiated Connection

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-7
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Table 5-1

EV-DO terminology

Feature description

(continued)

3G1X

EV-DO

termination

AN-Initiated Connection

Pilot-Strength Measurement Message

Route Update Message (RUM)

Summary of data collected

Data is collected for the EV-DO PCMD records as follows:

EV-DO PCMD records include a field to indicate the EV-DO PCMD software
version which generated the EV-DO PCMD record to indicate the format of the
data.
EV-DO PCMD includes Connection Final Class (CFC) values, as well as qualifiers
specifically applicable to EV-DO PCMD (for example, Radio Network Controller
(RNC) resource data)
EV-DO PCMD mirrors the existing 3G1X PCMD capabilities as well as the current
CFC values applicable to EV-DO
EV-DO PCMD data storage is in the OMP, similar to the way that 3G1X data is
stored in the 3G1X-associated OMP. This data has the same storage requirements
as far as the length of time the data is stored. However, the files are dedicated to
EV-DO PCMD.
EV-DO PCMD records are sent to OMP ports specific to EV-DO PCMD. The
assigned ports are different from those used by 3G1X PCMD data.
The PCMD data for EV-DO is in a completely separate data stream and in separate
directories from PCMD for 3G1X.

In Release 27.0 and later

There is also a field to indicate the number of RUM records. This field can have a
value of either 0 or 1 and provides more detailed RUM data (see Table 5-18, DO
PCMD RUM Fields (p. 5-42).
A Personality Type field is added for the type of AT that is involved in the PCMD
event.
An additional field that reports the number of flow data into the PCMD record has
been added. For Release 27.0, the value for this field will always be none.
In Release 28.0 PCMD reports Flow data as part of the Enhanced Rev-A support.

Subscriber perspective

The PCMD for 1xEV-DO feature is transparent to subscribers.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-8

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Feature description

Service perspective

The most widely used applications for EV-DO PCMD are for troubleshooting, for
example, detection, isolation, and correction of errors. Examples include:

EV-DO PCMD collects all the data associated with the connection. This allows
quick response to customer trouble tickets. There is no need to recreate the failure
scenario in the lab to understand why a connection failed or was dropped. This
virtually eliminates the drive test, which is very expensive and time-consuming.
EV-DO PCMD can determine if a particular brand or model or even a specific AT
is causing set-up failures and dropped connections. This enables isolation of the
root cause of the problem.
EV-DO PCMD gives very useful information regarding RF coverage. Once the
network is established, the RF coverage can be analyzed by looking at signal
strength at the end of connections. Inadequate RF coverage can result in lost
connections, and signal strength at the time of a lost connection can be examined in
the EV-DO PCMD record. EV-DO PCMD can increase efficiency and reduce costs
associated with RF optimization and engineering.
Important! Service providers must set up their own post-processing tool to analyze
the data collected by the PCMD for 1xEV-DO feature. For guidelines on how to set
up the tool, see Post-processing tool guidelines (p. 5-15).

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-9
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Issues
and caveats
...................................................................................................................................................................................................................................
Introduction

The PCMD for 1xEV-DO, FID 12269.0 feature is subject to the following special
issues and/or caveats.
Issues

The message 2 header lines are displayed is NOT an error message. The, PCMD
for 1xEV-DO feature deliberately behaves in this way when the daemon is re-started.
Caveats

The intention of the PCMD for 1xEV-DO feature is each time the daemon is re-started
a new header line is written to the raw data file for the current hour. This header line
serves as an indication that the daemon has re-started and that any data that was sent
from the RNC during the time the daemon was inactive has been lost.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-10

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

How
data is delivered to the OMP-FX v.2
...................................................................................................................................................................................................................................
Introduction

This section describes how the OMP-FX v.2 method of data delivery operates.
Functions

The OMP-FX v.2 method of data delivery provides the following functions:

Combines selected key data from the AMA record with per-connection performance
data
Makes this data available to customer performance analysis applications
(post-processing tools) via Internet-accessible ports on the OMP-FX v.2

Data delivery steps

When the OMP-FX v.2 is on-line, the EV-DO PCMD data is transferred from the RNC
AP to the OMP and stored in an hourly file on the OMP (for file details, see Storage
of one hour of current data (p. 5-12)).
Data delivery path diagram

Figure 5-1, EV-DO PCMD data delivery path (p. 5-12) shows the path of the PCMD
1xEV-DO data transmission message that is sent after a connection ends. The Ethernet
Interface Node Enhanced (EINE) selects an available Mobility Manager B-Server
Applications Processor (AP) to route the message to the OMP-FX v.2.
Important! The EV-DO PCMD record always has fields for RUM data, even if
they are null.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-11
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

How data is delivered to the OMP-FX v.2

Figure 5-1 EV-DO PCMD data delivery path

EV-DO PCMD record viewer tools

Program tools called evdo_rpcmdviewer and evdo_vpcmdviewer are available to display


per-call measurement data at the OMP-FX v.2. For details on the EV-DO PCMD
Viewer, see Using the EV-DO PCMD viewer to view EV-DO PCMD data (p. 5-68).
Storage of one hour of current data

The OMP-FX v.2 stores two types of data files: uncompressed data files of the current
hour and previous hour, and compressed data files of up to eight hours, resulting in
saving up to ten hours of data files.
The OMP-FX v.2 accumulates the current hours worth of data on the OMP-FX v.2
disk. When the current hour is up, the OMP-FX v.2 moves the data for the current
hour to a separate, uniquely named file for the previous hour.
To access the stored data files (current and previous), the user can run File Transfer
Protocol (FTP) software for the files. The files are ASCII text with fields that are
separated by a delimiter (; or |), which is also called the raw format. For a
description of the raw format, seePer-connection performance data output examples
from the OMP-FX v.2 (p. 5-47).
The stored files are located in the following directory:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-12

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

How data is delivered to the OMP-FX v.2

/omp/omp-data/logs/evdo_pcmd
The naming convention for the files is as follows:
YYMMDDHH.EVDOPCMD

where
YY

= year

MM

= month

DD

= day

HH

= hour at the end of the data collection period (in 24-hour format, for example, 15
is 3:00 PM)
Configured OMP-FX v.2 ports

The following configuration files define the port allocations for the OMP-FX v.2
method of data delivery:
/etc/inittab
/etc/services
/etc/inetd.conf
crontab
Important! These files are configured as the OMP package is installed on the
system and are not done manually.
/etc/services file

The /etc/services file defines the services that are available via remote telnet
connection to the OMP-FX v.2. These services map to the following five port
allocations:
evdo_vpcmdviewer7050 7050/tcp
evdo_rpcmdviewer7051 7051/tcp
evdo_rpcmdviewer7052 7052/tcp
evdo_rpcmdviewer7053 7053/tcp
evdo_rpcmdviewer7054 7054/tcp
Port 7050 is reserved for human readable format (also called the verbose format).
Ports 7051 through 7054 are reserved for an ASCII version with fields that are
separated by a delimiter (; or |) (also called the raw format).
Important! By default, the evdo_vpcmdviewer displays 10 records and then quits.
Limiting the number of output records conserves CPU space. You can use the
syntax evdo_vpcmdviewer -n, with n having a value greater than zero and a
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-13
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

How data is delivered to the OMP-FX v.2

maximum value that fits into a signed integer (2, 147, 483, 647), to change the
number of EVDO PCMD records that are displayed. If the number provided is less
than 1, evdo_vpcmdviewer displays 10 records.
/etc/inetd.conf file

The /etc/inetd.conf file defines the services that are available directly from the
OMP-FX v.2 with the evdo_pcmd command and the OMP-FX v.2 port number. The
output format of the EV-DO PCMD data is decided by the port number the user
specifies:
eevdo_vpcmdviewer7050 stream tcp nowait root /omp/bin/evdo_vpcmdviewer
evdo_vpcmdviewer
evdo_rpcmdviewer7051 stream tcp nowait root /omp/bin/evdo_rpcmdviewer
evdo_rpcmdviewer
evdo_rpcmdviewer7052 stream tcp nowait root /omp/bin/evdo_rpcmdviewer
evdo_rpcmdviewer
evdo_rpcmdviewer7053 stream tcp nowait root /omp/bin/evdo_rpcmdviewer
evdo_rpcmdviewer
evdo_rpcmdviewer7054 stream tcp nowait root /omp/bin/evdo_rpcmdviewer
evdo_rpcmdviewer
Port 7050 is reserved for the verbose (human readable) format. Ports 7051-7054 are
reserved for the raw Access and Cross Connect System II (ASCII) version with fields
that are separated by a delimiter (; or |).
/etc/inittab file

The following entry is made in the /etc/inittab file:


IT56:a:respawn:/omp/sbin/evdo_pcmdaemon
See also

For guidelines on how to develop post-processing tools, see Post-processing tool


guidelines (p. 5-15).
For a description of the EV-DO PCMD record that is delivered to the OMP-FX v.2,
see Description of 1xEV-DO per-connection performance data delivered to the
OMP-FX v.2 (p. 5-26).
For examples of verbose and raw data output formats, see Per-connection performance
data output examples from the OMP-FX v.2 (p. 5-47).

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-14

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Post-processing
tool guidelines
...................................................................................................................................................................................................................................
Introduction

Post-processing tools can be developed to produce a wide variety of reports to analyze


and troubleshoot system performance. The following examples illustrate the types of
queries that can be run against the EV-DO PCMD data.
Example 1

For all cells, generate the number of connections with

CFC 9 (Origination FailedCell Problem)


CFC Qualifier of Traffic Channel Unavailable

Example 2

For a given sector and carrier, list all AT Electronic Serial Numbers (ESNs) that
produced a Traffic Channel Confirmation failure. These failures result in failed
connection attempts. With the ESN, you can determine manufacturer and model
number of the AT.
Guidelines

Use the following guidelines during development of post-processing tools:


Guideline

Page

OMP-FX v.2 ports (p. 5-15)

OMP-FX v.2 ports (p. 5-15)

Service measurement (SM) counts (p. 5-15)

Service measurement (SM)


counts (p. 5-15)

CFC Qualifiers and their meanings (p. 5-21)

CFC Qualifiers and their


meanings (p. 5-21)

Connection Final Class field usage (p. 5-20)

Connection Final Class field


usage (p. 5-20)

OMP-FX v.2 ports

Set up the post-processing tools to access the desired OMP-FX v.2 port (7050 or 7051)
as described in Configured OMP-FX v.2 ports (p. 5-13).
Service measurement (SM) counts

Up to nine SM counts are included in EV-DO PCMD records.


For detailed information about the following service measurements, see CDMA2000
1xEV-DO Service Measurements, 401-614-326
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-15
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Post-processing tool guidelines

Key service measurements

The PCMD for 1xEV-DO feature provides fields in the EV-DO PCMD data record to
store key service measurements which are updated during the processing of a
connection. This feature does not define these counts, but it does define a subset of the
total number of potentially generated measurements during a connection whose
pegging may be flagged in the EV-DO PCMD record as the associated code in Table
5-2, Key service measurements (p. 5-16). This allows better fault isolation for
determining the reason for a dropped connection. The Read-Only-Printer (ROP)
Message IDs are included as the Secondary CFCQ for Dropped Connections in Table
5-6, Dropped connection qualifiers (p. 5-22).
Table 5-2

Key service measurements

Code

Count = Explanation

01

AN_INIT_CONN_ATT_FAIL_CONFIG_NEGO_FAILED
= AN-initiated Connection attempt failures - negotiation fail

02

AN_INIT_CONN_ATTMPT_FAIL_NO_TCC_RCVD
= (AN- initiated Connection attempt failures - no response to traffic
channel assignment traffic channel confirmation received

03

AN_INIT_CONN_ATTMPT_FAIL_RL_NOT_ACQ
= AN- initiated Connection attempt failures - rev link not acquired

04

AN_INIT_CONN_ATTMPT_FAIL_NO_RES_AVLBL
= AN- initiated connection attempt failures - no resources available

05

AN_INIT_CONN_ATMPT_FAIL_OTHER_PRETCA
= AN- initiated Connection attempt failures - other failures pre TCA

06

AN_INIT_CONN_ATMPT_FAIL_OTHER_POSTTCA
= AN- initiated Connection attempt failures - other failures pre TCA

07

AT_INIT_CONN_ATT_FAIL_CONFIG_NEGO_FAILED
= AT- initiated Connection attempt failures - negotiation fail

08

AT_INIT_CONN_ATTMPT_FAIL_NO_TCC_RCVD
= AT- initiated Connection attempt failures - no traffic channel confirmation
received response to traffic channel assignment

09

AT_INIT_CONN_ATTMPT_FAIL_RL_NOT_ACQ
= AT- initiated Connection attempt failures - rev link not acquired

10

AT_INIT_CONN_ATTMPT_FAIL_NO_RES_AVLBL
= AT- initiated connection attempt failures - no resources available

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-16

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Table 5-2

Key service measurements

Post-processing tool guidelines

(continued)

Code

Count = Explanation

11

AT_INIT_CONN_ATMPT_FAIL_OTHER_PRETCA
= AT- initiated Connection attempt failures - other failures Pre TCA

12

AT_INIT_CONN_ATMPT_FAIL_OTHER_POSTTCA
= AT- initiated Connection attempt failures - other failures Post TCA

13

FAST_CONNECT
= Number of fast connection requests

15

FAST_CONNECT_FAIL_NO_TCC_RCVD
= Number of fast connection attempt failures due to no Traffic Channel
Confirmation received

16

FAST_CONNECT_FAIL_NOT_RL_ACQ
= Number of fast connection attempt failures due to no reverse link being
acquired

17

AN_INIT_CONN_REQ
= AN-Initiated Connection Requests

18

TCA_FOR_AN_INIT_CONN_REQ
= Traffic Channel Assignments for AN Initiated Connection Requests

19

AT_INIT_CONN_REQ
= AT Initiated Connection Requests

20

TCA_FOR_AT_INIT_CONN_REQ
= Traffic Channel Assignments for AT Initiated Connection Requests

21

CONN_REL_RLL
= Connection Release - RF Link Lost

22

CONN_REL_OTHER_REASON
= Connection Release - Other Reasons

28

INT_SUBNET_IDL_TRFR_ATTMPT
= Number of Inter Subnet Idle Transfer Attempts

29

PERS_SWTCH_CONN_TCA
= Traffic Channel Assignments for Personality Switch

30

PERS_SWTCH_CONN_ESTABLISHED
= Established Connections for Personality Switch

31

CONN_SETUP_PERS_SWTCH_UNKNOWN_TO_REVA
= Personality Switches During Connection Setup from Unknown to Rev A

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-17
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Table 5-2

Key service measurements

Post-processing tool guidelines

(continued)

Code

Count = Explanation

32

CONN_SETUP_PERS_SWTCH_REL0_TO_REVA
= Personality Switches During Connection Setup from Rel 0 to Rev A

33

CONN_SETUP_PERS_SWTCH_REVA_TO_REL0
= Personality Switches During Connection Setup from Rev A to Rel 0

34

AHO_PERS_SWTCH_REVA_TO_REL0
= Personality Switch During Active Connections from Rev A to Rel 0

35

RAN_AUTH_TOTAL_ATTMPT
= RAN Authentications Total Attempts

36

RAN_AUTH_SUCCESSFUL_ATTMPT
= RAN Authentications Successful Attempts

37

RAN_AUTH_FAIL_INTERNAL
= RAN Authentications Internal Failure

38

RAN_AUTH_FAIL_STREAM_SELECTION_FAILED
= RAN Authentications Stream Selection Failures

39

RAN_AUTH_FAIL_AT_CONFIG_RJCT_RCVD
= RAN Authentication Failure AT Configuration Reject Received

40

RAN_AUTH_FAIL_INVLD_AT_CFGRQ_PPP_EST_FLD
= RAN Authentication Failure Invalid AT Configuration Request PPP
Establishment Failed

41

RAN_AUTH_FAIL_LCP_RLTD_PPP_EST_FAILED
= RAN Authentication Configuration - ACK Related PPP Establishment
Failures

42

RAN_AUTH_FAIL_CNFGR_NAK_PPP_EST_FAILED
= RAN Authentication Configure- NAK Related PPP Establishment Failures

43

RAN_AUTH_FAIL_LCP_TERM_RCVD
= RAN Authentication Failures LCP Termination Received

44

RAN_AUTH_FAIL_NO_AT_CONFIG_RQST_RCVD
= RAN Authentication Failures - No AT Configure Request Received

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-18

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Post-processing tool guidelines

The EVDO Service Measurements Enhancement - Phase 2 feature (FID 12370.1)


introduces new service measurement counts to improve performance assessment of
1xEV-DO networks for both Rev. 0 and Rev. A. See Table 5-3, SMs for DO SM
Enhancements Phase 2 (p. 5-19).
Table 5-3

SMs for DO SM Enhancements Phase 2

Code

Count = Explanation

45

AT_INIT_CONN_ATTMPT_FAIL_NO_RES_AVLBL_SESS
= AT-Initiated Connection Attempt Failures - No Resource Available -Session
Setup Short

46

AT_INIT_CONN_ATTMPT_FAIL_RL_NOT_ACQ_SESS
= AT-Initiated Connection Attempt Failures - Reverse Link Not Acquired Session Setup Short

47

AT_INIT_CONN_ATTMPT_FAIL_NO_TCC_RCVD_SESS
= AT-Initiated Connection Attempt Failures - No Traffic Channel Complete
Received - Session Setup Short

48

AT_INIT_CONN_REQ_SESS
= AT Initiated Connection Request - Session Setup Short

49

TCA_FOR_AT_INIT_CONN_REQ_SESS
= AT Initiated Connection Request TCA Sent - Session Setup Short

50

AT_INIT_ESTABLISHED_CONN_SESS
= AT Initiated Connection Request Established Connections - Session Setup
Short

51

SESS_SETUP_REQ_POOR_RF_ALLOW
= Session Setup Request Poor RF Allow Short

52

SESS_SETUP_REQ_POOR_RF_DENY
= Session Setup Request Poor RF Deny Short

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-19
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Post-processing tool guidelines

Connection Final Class field usage

The CFC assignment is made at the end of every 1xEV-DO connection. The CFC
value is a broad classification defining success or failure of the connection as well as
the approximate site of failure (EV-DO, RNC, cell, or access terminal). CFC values are
listed in Table 5-4, CFC values (p. 5-20) with the additional values appearing in
adjacent tables:
Table 5-4

CFC values

Value

Meaning

Additional information

normal connection

The connection ended without any failure


conditions. See Table 5-5, Normal
connection qualifiers (p. 5-21) for
additional qualifiers for this value.

dropped connection

The connection attempt was completed but


then was dropped or lost. See Table 5-6,
Dropped connection qualifiers (p. 5-22)
for additional qualifiers for this value.

AT/AN Connection attempt


failedsubscriber

The AT/AN-originated connection attempt


was unsuccessful due to a problem with
the subscribers account or AT unit. See
Table 5-7, AT-Initiated/AN-Initiated
Connection Failed - Subscriber (p. 5-22)
for additional qualifiers for this value.
Expectation to see the digit 3 without
extra information or value for others.
CFCQ values are not there and will be
expanded in the future.

AT/AN Connection attempt


failedcell

The AT/AN-originated connection attempt


failed due to a cell-related error or
blockage. See Table 5-8, AT-Initiated/
AN-Initiated Connection Failed - Cell
(p. 5-23) for additional qualifiers for this
value.

11

AT/AN Connection attempt


failed network element
independent

The AT/AN-originated connection attempt


failed and the exact cause was
undetermined.

20

AT/AN Connection attempt


failed RNC

The AT/AN-originated connection attempt


failed due to an RNC-related error. See
Table 5-9, AT-Initiated/AN-Initiated
Connection Failed - RNC (p. 5-23) for
additional qualifiers for this value.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-20

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Table 5-4

CFC values

Post-processing tool guidelines

(continued)

Value

Meaning

Additional information

22

AT/AN Connection attempt


failednetwork

The AT/AN-originated connection attempt


failed due to a network-related error or
blockage. See Table 5-10,
AT-Originated/AN-Originated Connection
Failed - Network (p. 5-24) for additional
qualifiers for this value.

CFC Qualifiers and their meanings

The CFC Qualifier field builds on the CFC field to more narrowly isolate the cause of
connection failures. Table 5-5, Normal connection qualifiers (p. 5-21) through Table
5-10, AT-Originated/AN-Originated Connection Failed - Network (p. 5-24) list the
CFC Qualifiers (CFCQs) used by the PCMD for 1xEV-DO feature and any additional
criteria that the PCMD for 1xEV-DO feature uses to apply to the qualifier.
Table 5-5

Normal connection qualifiers

Value

Qualifier

Additional Information

001

Connection established and


released normally.

002

Connection released early by AT.

This is an indication of a
user-initiated connection end or
Hybrid AT hand-down to 1X

005

Connection attempt interrupted


by Idle Transfer.

This indicates that the AT did an


Idle transfer to another RNC
before the connection attempt
could complete.

021

Connection forced to dormancy


early due to congestion control.

Forced dormancy can be used for


intra-user QoS or congestion
control

022

Connection forced to dormancy


early due to QoS priority.

Forced dormancy can be used for


intra-user QoS or congestion
control.

023

Connection Personality Change


Attempt

Secondary CFCQ indicates new


personality type requested.

024

Connection Session Close By


Operator

Session closed by operator


command.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-21
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Table 5-6

Post-processing tool guidelines

Dropped connection qualifiers


Possible
secondary
qualifier

Value

Qualifier

Additional Information

100

Dropped connection

The connection was dropped after


traffic channel confirmation.

106

Lost Connection

Cell has detected a loss of RF


continuity. This is an ending of a
connection due to failures other
than in the network, such as the
AT, or when no TCC was
received during a soft/softer
handoff attempt.

120

RNC Disconnect

Connection was dropped due to a


loss of communication between
the cell and the RNC.

122

AT Tune-Away
Timeout

The AT tuned away and did not


return within the timeout period
(fade timer).

Table 5-7

AT-Initiated/AN-Initiated Connection Failed - Subscriber

Value

Qualifier

Additional Information

Possible
secondary
qualifier

300

AT/AN-Initiated
Connection
inhibited
temporary account
suspension

1=RAN-authentication failure

304

Configuration
Negotiation Failure

Failure occurred during


Configuration Negotiation
exchange.

305

Communication
failed with AT

Communication with AT failed.

310

AT-Initiated Session
Close

AT initiated session close due to


an error detected at AT.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-22

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Table 5-8

Post-processing tool guidelines

AT-Initiated/AN-Initiated Connection Failed - Cell

Value

Qualifier

Additional Information

Possible
secondary
qualifiers

901

Traffic channel
confirmation failure

0 = No indication that AT

acquired reverse link


1 = No Traffic Channel

confirmation received
902

Resource Mismatch

QoS Backhaul expectation

903

Traffic channel
unavailable

Traffic Channel could not be


obtained

904

Internal cell
processing error

Undetermined hardware or
software error

Table 5-9

AT-Initiated/AN-Initiated Connection Failed - RNC


Possible
secondary
qualifiers

Value

Qualifier

Additional Information

2001

AP-related software
failure

Failure was due to an internal AP


software problem, for example,
database error or expired timers.

2002

Configuration
Failure

Failure during Configuration


Negotiation

2003

Internal RNC
communication
failure

Communication between AP &


TP or AP to AP-reasons not
specified

2004

No TP available

The connection failed due to lack


of a TP in the RNC

2007

TP protocol failure

Protocol error between TP and


cell

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-23
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Table 5-10

Post-processing tool guidelines

AT-Originated/AN-Originated Connection Failed - Network

Value

Qualifier

Additional Information

2202

A10/A11 path setup


failure

The connection failed


because the path between
the RNC and PDSN failed.

Possible secondary
qualifiers
Secondary Connection
Final Qualifier
1 = PDSN Rejected
REQUEST_REASON_
UNSPECIFIED
2 = PDSN Rejected
REQUEST_ADMISTRATIVELY_
PROHIBITED
3 = PDSN Rejected
REQUEST_INSUFFICIENT_
RESOURCES
4 = PDSN Rejected
REQUEST_AUTHENTICATION_
FAILED
5 = PDSN Rejected
REQUEST_IDENTIFICATION_
MISMATCH
6 = PDSN Rejected
REQUEST_POORLY_
FORMED_REQUEST
7 = PDSN Rejected
REQUEST_UNKNOWN_
PDSN_ADDRESS
8 = PDSN Rejected
REQUEST_REVERSE_
TUNNEL_
UNAVAILABLE
9 = PDSN Rejected
REQUEST_REVERSE_
TUNNEL_MANDATORY
10 = PDSN Rejected
REQUEST_UNSUPPORT_
VENDORID

2203

Authorization
Exception

Connection could not be


established due to failure to
author license.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-24

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Table 5-10

Post-processing tool guidelines

AT-Originated/AN-Originated Connection Failed - Network


(continued)
Possible secondary
qualifiers

Value

Qualifier

Additional Information

2206

PDSN-initiated
closure

PDSN sends registration


update message

2207

AAA comm.
failures

The communication
between RNC and AAA
failed.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-25
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Description of 1xEV-DO per-connection performance data


delivered
to the OMP-FX v.2
...................................................................................................................................................................................................................................
Introduction

This section describes the 1xEV-DO per-connection performance data that is delivered
to the OMP-FX v.2.
EV-DO PCMD Record Format

Each EV-DO PCMD record may have up to 67 different fields within the following
categories:

Administrative Fields
Session Detail Fields
Connection Detail Fields
RLP Layer Detail Fields
Key Service Measurements
Personality Type
Additional Data
Route Update Message Data
Flow Data

EV-DO PCMD record length

The 1xEV-DO PCMD record has a fixed number of fields. There are always six fields
for service measurements. Data for six legs is always sent/output, even if not all of the
legs have data. In Release 27.0 and later, the PCMD record has a variable length due
to the service provider option to include or exclude RUM data.
Data table

The following tables list the total possible data set that can be collected for each
connection that qualifies for 1xEV-DO PCMD data collection:

Table 5-11, EV-DO PCMD record data fields - Administrative (p. 5-28)
Table 5-12, EV-DO PCMD record data fields - Session (p. 5-29)
Table 5-13, EV-DO PCMD record data fields - Connection (p. 5-31)
Table 5-14, EV-DO PCMD record data fields - RLP Layer (p. 5-36)
Table 5-15, EV-DO PCMD record data fields - Key Service Measurements
(p. 5-36)
Table 5-16, EV-DO PCMD record data fields - Personality Type: (p. 5-38)
Table 5-17, EV-DO PCMD record data fields - Additional Data (p. 5-38)

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-26

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Description of 1xEV-DO per-connection performance data


delivered to the OMP-FX v.2

Table 5-19, Flow Data Fields (p. 5-44)

Table 5-20, Flow Final Classes (FFC) and FFC Qualifiers for Flow Reservation
(p. 5-46)

Sequence of fields in the table

The fields in Table 5-11, EV-DO PCMD record data fields - Administrative (p. 5-28)
through Table 5-17, EV-DO PCMD record data fields - Additional Data (p. 5-38) are
in the same sequence as the fields in the raw and verbose output data. For examples of
the raw and verbose output data, see Per-connection performance data output
examples from the OMP-FX v.2 (p. 5-47).
Column descriptions

The following table describes each column in:

Table 5-11, EV-DO PCMD record data fields - Administrative (p. 5-28)
Table 5-12, EV-DO PCMD record data fields - Session (p. 5-29)
Table 5-13, EV-DO PCMD record data fields - Connection (p. 5-31)
Table 5-14, EV-DO PCMD record data fields - RLP Layer (p. 5-36)
Table 5-15, EV-DO PCMD record data fields - Key Service Measurements
(p. 5-36)
Table 5-16, EV-DO PCMD record data fields - Personality Type: (p. 5-38)
Table 5-17, EV-DO PCMD record data fields - Additional Data (p. 5-38)
Table 5-19, Flow Data Fields (p. 5-44)
Table 5-20, Flow Final Classes (FFC) and FFC Qualifiers for Flow Reservation
(p. 5-46)

Column number

Column name

Description

1.

Field number

Numbers the fields as a


convenient reference. The
fields in the actual output
are not numbered.

2.

Length

Provides the actual length


of the data in the field in
bits or bytes, as
appropriate.

3.

Verbose output field name

Is the name of the field


as it appears on the
verbose output.

4.

Field description

Describes the field and its


usage.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-27
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Description of 1xEV-DO per-connection performance data


delivered to the OMP-FX v.2

Column number

Column name

Description

5.

Range of values

Provides a range of
values that the field can
contain.

Important! Except where specifically noted, all fields in the EV-DO PCMD record
are set to null prior to being populated with any other data
Important! All time stamp fields are represented as milliseconds after midnight.
Table 5-11

EV-DO PCMD record data fields - Administrative

Field
Verbose output
number Length field name
1.

2
bytes

PCMD software
data format version

Field description

Range of values

Identifies data layout.


Unique for each release.

Starts with 1 and


increments by 1
each time there is a
new version of the
data output format:
1 = Release 26.0

2.

4
bytes

Sequence Number
(assigned at OMP)

Sequence number that is


incremented for each
connection record.

Starts with 0 and


increments by 1
each time there is a
new connection
record, up to a
maximum of 232,
and then resets to
0.

3.

2
bytes

Month and Day

Month and day

Any valid month


and day in MMDD
format.

4.

8
bytes

Duplicate Record
Sequence Number

Denotes that this record


is an initial primary
PCMD record.

Always zero in
Release 27.0.

5.

1 byte

Mobile ID Type

Mobile Serial Number


(MSN) (ESN/MEID)

0 = ESN

MSN ESN/MEID

eight-digit
hexadecimal
number

6.

8
bytes

Mobile ID

1 = MEID

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-28

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Table 5-11

EV-DO PCMD record data fields - Administrative

Field
Verbose output
number Length field name
7.

8
bytes

Table 5-12

Description of 1xEV-DO per-connection performance data


delivered to the OMP-FX v.2

International
Mobile Station
Identifier

(continued)

Field description

Range of values

International Mobile
Station Identifier (IMSI)

15 digits
(maximum)

EV-DO PCMD record data fields - Session

Verbose
output field
Field
number Length name

Field
description

Range of values

8.

4
bytes

UATI

Unicast Access
Terminal
Identifier
populated when
the UATI
Complete
message is
received.

32-bits displayed in hexadecimal


format and derived from the
lower 24 bits of the UATI128
plus the 8-bit color code.

9.

4
bytes

UATI Complete
Message
Received Time

Timestamp of
when UATI
Complete
Message
received at the
RNC from the
AT.

32-bits stored as milliseconds


after midnight.

10.

4
bytes

RATI

Random Access
Terminal
Identifier
generated
during session
setup attempt.

32-bits

11.

4
bytes

Control OHM
AP ID Address

Applications
Processor
Identifier
supporting the
event in the
form of an IP
address.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-29
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Table 5-12

EV-DO PCMD record data fields - Session

Verbose
output field
Field
number Length name
12.

Description of 1xEV-DO per-connection performance data


delivered to the OMP-FX v.2

1 byte

Session
Request Type

Field
description
Indicates the
session request
type.

(continued)

Range of values
0 = Not for Session
1 = RATI New Session Setup
2 = Idle Session Transfer
3 = Idle Session Transfer - Prior
Session
4 = Load Balancing with an RNC
group
5 = Connection with
Configuration Negotiation Data

13.

1 byte

Session Setup
Final Class

Indicates the
disposition of
the session
setup.

0 = Success
1 = Failure, UATI Complete Not
Received
2 = Connection Setup to do
Configuration Negotiation Failed
3 = Failure, Configuration
Negotiation Failed
4 = Failure, Idle Transfer Internal
Error
5 = Failure, UATI Assignment
Failed
6 = Failure Request from
unidentified AT
7 = Failure Service Denial Network DHZ Violation
8 = Failure Service Denial Network Other
9 = Failure AT-Initiated Session
Close

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-30

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Table 5-12

EV-DO PCMD record data fields - Session

Verbose
output field
Field
number Length name
14.

Description of 1xEV-DO per-connection performance data


delivered to the OMP-FX v.2

4
bytes

Session or
Connection
CPFail Value

Field
description
Provides details
on why the
session setup
failed.

(continued)

Range of values
CP Failure Codes will be
reported in the field. this CP
Failure Codes will be associated
with PCMD sessions connection
event.
The CP Failure Code will be
associated with the PCMD
session or connection event.

15.

4
bytes

Session
Setup/Transfer
Request Time

Contains a
timestamp of
when the UATI
Request
Message is
Received.

16.

4
bytes

Session
Setup/Transfer
Complete Time

Contains a
timestamp
indicating the
time the
session became
active. The
time is the
point at which
the AT can
request a
connection.

Table 5-13

EV-DO PCMD record data fields - Connection

Verbose
output field
Field
number Length name

Field description

Range of values

17.

4
bytes

Connection
Request Time

The time the request was


received by the AP.

18.

4
bytes

Connection
Established
Time

Timestamp indicating the


time the traffic channel was
successfully established.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-31
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Table 5-13

Description of 1xEV-DO per-connection performance data


delivered to the OMP-FX v.2

EV-DO PCMD record data fields - Connection

Verbose
output field
Field
number Length name

(continued)

Field description

Range of values

19.

4
bytes

A12 RAN
Authentication
Time

The time the AT has been


RAN authenticated.

20.

4
bytes

A10 Link
Established
Time

The time the A10 link was


successfully established.

21.

4
bytes

Connection
Duration

The time the session


becomes dormant.

22.

1 byte

Connection
Final Class

Indicates the connection


ended normally, was
dropped, or lost.

See values in Table


5-3, CFC values.

23.

2
bytes

CFC Qualifier

Indicates the connection was


established and release
normally.

See values in Table


5-4, through Table
5-9..

24.

4
bytes

Secondary CFC
Qualifier

Indicates the connection was


established and released
normally and conditions
detected.

25.

1 byte

AT- or
AN-Initiated
Connection
Request

Defines the type of


connection request.

0 = AT-Initiated
1 = AN-Initiated
2 = Fast Connect

26.

1 byte

Silent
Reorigination
Flag

Indicates that at least one


silent reorigination occurred
during the associated PCMD
Interval.

Always zero in
R26.

27.

1 byte

Service Node
ID

The service node handling


the connection at the time
the connection is closed
(returned to dormancy). This
is the OMP identifier.

0-255

28.

4
bytes

TP for
Connection

Indicates the traffic


processor used for the
connection identified by the
IP address.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-32

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Table 5-13

Description of 1xEV-DO per-connection performance data


delivered to the OMP-FX v.2

EV-DO PCMD record data fields - Connection

Verbose
output field
Field
number Length name

(continued)

Field description

Range of values

29.

4
bytes

PDSN IP No.

Indicates the address.

30.

2
bytes

Seizure Cell
Number

Populated after the Cell Site


identifier is available.

1-maximum number
of cells supported

31.

1 byte

Seizure Sector
Number

Populated once for a PCMD


as soon as the data is
available.

0-6

32.

2
bytes

Last
DRC-Pointed
Cell

Indicates the DRC-pointed


cell site number when the
connection was being
released.

0-maximum number
of cells supported

33.

1 byte

Last
DRC-Pointed
Sector Number

Indicates the ID of the last


sector to which the Datarate
Control message pointed.

0-6

34.

1 byte

Number of DO
pages

Indicates the number of DO


pages leading to set up a
connection. This field is set
only for AN-initiated
connections.

0-255

35.

4
bytes

Configuration
Negotiation
Start Time

Timestamp

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-33
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Table 5-13

EV-DO PCMD record data fields - Connection

Verbose
output field
Field
number Length name
36.

Description of 1xEV-DO per-connection performance data


delivered to the OMP-FX v.2

1 byte

Configuration
Negotiation
Failure Code

(continued)

Field description

Range of values

Indicates the configuration


negotiation failure code.

001 = Could not


proceed
010 = AN-Initiated
Negotiation
Connection Attempt
Failure
011 = AT-Initiated
Negotiation
Connection Attempt
Failure
100 = Security
Protocol
Negotiation Failure
101 = Session Key
Length Negotiation
Failure
110 = No response
from AT during
configuration
negotiation
000 = Success

37.

4
bytes

Configuration
Negotiation
End Time

Timestamp

38.

1 byte

Seizure Band
Class

Indicates seizure band class.

0 = Cellular: 850
band class
1 = PCS: 1900
band class
4 = Korea PCS
5 = 450
6 = China 2100

39.

2
bytes

Seizure
Channel
Number

Indicates seizure channel


number.

0-2047 in
increments of 1

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-34

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Table 5-13

EV-DO PCMD record data fields - Connection

Verbose
output field
Field
number Length name
40.

Description of 1xEV-DO per-connection performance data


delivered to the OMP-FX v.2

1 byte

Assigned Band
Class

(continued)

Field description

Range of values

Indicates assigned band


class.

0 = Cellular: 850
band class
1 = PCS: 1900
band class
4 = Korea PCS
5 = 450
6 = China 2100

41.

2
bytes

Assigned
Channel
Number

Indicates assigned channel


number.

0-2047 in
increments of 1

42.

1 byte

Ending Band
Class

Indicates ending band class.

0 = Cellular: 850
band class
1 = PCS: 1900
band class
4 = Korea PCS
5 = 450
6 = China 2100

43.

2
bytes

Ending
Channel
Number

Indicates ending channel


number.

0-2047 in
increments of 1

44.

1 byte

Connection
Established

Does not require a


connection request received.
If the connection is not
established, the field is set
to null.

y or n*

* Even though the Connection Established field format indicates whether the
connection was established with a response of y or n, the contents are:

NULL = no connection was requested

1 = the connection was successfully established

0 = the connection was requested and not established

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-35
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Table 5-14

Description of 1xEV-DO per-connection performance data


delivered to the OMP-FX v.2

EV-DO PCMD record data fields - RLP Layer

Field
number Length

Verbose output
field name

Field description

Range of values

45.

4 bytes

RLP Bytes
Transmitted to AT

Indicates RLP bytes


transmitted to AT.

46.

4 bytes

RLP Bytes
Received from AT

Indicates RLP bytes


received from AT.

47.

4 bytes

RLP Bytes
Retransmitted
(NAKed) to AT

Indicates the RLP


bytes retransmitted
(NAKed) to AT.

48.

4 bytes

RLP Bytes
Re-received from
AT

Indicates RLP bytes


re-received from
AT.

Table 5-15

EV-DO PCMD record data fields - Key Service Measurements

Verbose
output field
Field
number Length name

Field description

Range of values

49.

1 byte

Number of SM
Counts (One
Field Per
Count)

Number of SM Counts (One


Field Per Count).

1 field per count

50.

1 byte

SM Count 1

SM Count 1

0-44
Values 29 to 34 are
available in R29.0
and later
Values 35 to 44 are
available in
R28.0/SU3 CFTE
and later

51.

1 byte

SM Count 2

SM Count 2

0-44
Values 29 to 34 are
available in R29.0
and later
Values 35 to 44 are
available in
R28.0/SU3 CFTE
and later

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-36

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Table 5-15

EV-DO PCMD record data fields - Key Service Measurements


(continued)

Verbose
output field
Field
number Length name
52.

Description of 1xEV-DO per-connection performance data


delivered to the OMP-FX v.2

1 byte

SM Count 3

Field description

Range of values

SM Count 3

0-44
Values 29 to 34 are
available in R29.0
and later
Values 35 to 44 are
available in
R28.0/SU3 CFTE
and later

53.

1 byte

SM Count 4

SM Count 4

0-44
Values 29 to 34 are
available in R29.0
and later
Values 35 to 44 are
available in
R28.0/SU3 CFTE
and later

54.

1 byte

SM Count 5

SM Count 5

0-44
Values 29 to 34 are
available in R29.0
and later
Values 35 to 44 are
available in
R28.0/SU3 CFTE
and later

55.

1 byte

SM Count 6

SM Count 6

0-44
Values 29 to 34 are
available in R29.0
and later
Values 35 to 44 are
available in
R28.0/SU3 CFTE
and later

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-37
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Table 5-16

EV-DO PCMD record data fields - Personality Type:

Verbose
output field
Field
number Length name
56.

Description of 1xEV-DO per-connection performance data


delivered to the OMP-FX v.2

1 byte

Personality
Type

Field description

Range of values

Indicates Personality Type of


AT.

0 = Rev 0
1 = Rev A
2 = MFPA

Table 5-17

EV-DO PCMD record data fields - Additional Data

Verbose
output field
Field
number Length name

Field
description

Range of values

57.

1 byte

RUM record
data stored

Indicates
whether RUM
collection was
enabled.

0, 1

58.

1 byte

Num of RUM
data stored

When RUM
collection is
enabled, this
value indicates
how many
RUM have
actually been
received and
stored in this
PCMD record.

0-2

59.

1 byte

Num of Flow
Data Included

Indicates the
number of
PCMD
subrecords
that are
included in
the PCMD
primary
record.

0-No Flows
Up to 8 Flows included.
For Release 27.0, the value is
always none.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-38

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Table 5-17

EV-DO PCMD record data fields - Additional Data

Verbose
output field
Field
number Length name
60.

2
bytes

Access Round
Trip Delay
If Access
Round Trip
Delay Precision
= 1, than 1 unit
= 1/8 chip. If
Access Round
Trip Delay
Precision = 32,
than 1 unit = 4
chips.s

61.
62.

Description of 1xEV-DO per-connection performance data


delivered to the OMP-FX v.2

word32 Last AP IP
Address
Last Attempted
Paging Area

Field
description

(continued)

Range of values

Indicates
Round Trip
Packet
Transmission
Delay

0-255

Indicates Last
AP IP Address

pagingArea

1-8, where:
1:Last Active Set
2:Color Code of Last Seen RNC
3: Neighbor RN
4: RNC Group
5:Distance Tier 0
6:Distance Tier 1
7:Distance Tier 2
8:Distance Tier 3

63.

Paging Profile
ID

profileId

0-5 (BEpID, CMCSpID,


PTTCSSpID, PTTICSpID,
CPTTSB1pID, CPTTSB2pID)

64.

Number of
QoS Pages

noOfQosPage

0-7

65.

Last-Seen Cell
Used for
Paging

lastSeenCell

0-999

66.

Last-Seen
Sector Used for
Paging

lastSeenSector

0-6

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-39
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Table 5-17

Description of 1xEV-DO per-connection performance data


delivered to the OMP-FX v.2

EV-DO PCMD record data fields - Additional Data

Verbose
output field
Field
number Length name
67.

(continued)

Field
description

Range of values

Last-Seen
Group Member
Used for
Paging

lastSeenRNC

0-255

68.

2
bytes

Control OHM
Number

This is the
OHM number
associated
with the
Control OHM
IPAddress
(field 11

0.0.0.0-255.255.255.255

69.

4
bytes

Initial Access
OHM AP IP
Address

This is only
populated
when OHM
load-balancing
is attempted.

0.0.0.0-255.255.255.255

70.

2bytes

Initial Access
OHM Number

This is the
OHM number
associated
with the
Initial Access
OHM AP IP
Address (field
69)

0-65535

71.

2
bytes

Subscriber
Home
Jurisdiction ID

0-65535

72.

1 byte

Subscriber
Home
Inter-User
Priority

0-8

73.

2
bytes

Assigned Cell
Site ID For
Connection

1-maximum number of cells


supported

74.

1 byte

Assigned
Sector ID For
Connection

0-6

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-40

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Table 5-17

Description of 1xEV-DO per-connection performance data


delivered to the OMP-FX v.2

EV-DO PCMD record data fields - Additional Data

Verbose
output field
Field
number Length name

(continued)

Field
description

Range of values

75.

3
bytes

SM Count 7

SM Count 7

76.

3
bytes

SM Count 8

SM Count 8

77.

3
bytes

SM Count 9

SM Count 9

78.

1 byte

Access Round
Trip Delay
Precision

1, 32

Indicates the
precision of the
Access Round
Trip Delay. If
1, Access
Round Trip
Delay is in
units of 1/8
chip. If 32,
Access Round
Trip Delay is
in units of 4
chip.
79.

1 byte

EVDO PCMD
Primary Spare
01

0-255

80.

1 byte

EVDO PCMD
Primary Spare
02

0-255

81.

1 byte

EVDO PCMD
Primary Spare
03

0-255

82.

1 byte

EVDO PCMD
Primary Spare
04

0-255

83.

1 byte

EVDO PCMD
Primary Spare
05

0-255

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-41
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Table 5-17

Description of 1xEV-DO per-connection performance data


delivered to the OMP-FX v.2

EV-DO PCMD record data fields - Additional Data

Verbose
output field
Field
number Length name

Field
description

(continued)

Range of values

84.

1 byte

EVDO PCMD
Primary Spare
06

0-255

85.

1 byte

EVDO PCMD
Primary Spare
07

0-255

86.

1 byte

EVDO PCMD
Primary Spare
08

0-255

Detailed RUM data

When the Enhancements to EVDO Per Call Service Measurements feature is active,
the service provider uses the EMS interface to include or exclude data from the first
RUM and the last RUM that are received during the PCMD Interval in the PCMD
record. The PCMD record contains a field to indicate whether RUM data is stored in
that record.
If RUM data is included, the RUM data fields that are shown inTable 5-18, DO
PCMD RUM Fields (p. 5-42) are appended to the end of the PCMD record.
Table 5-18

DO PCMD RUM Fields

Field Number

Description of data

RUM Storage Timestamp

Handoff Activity caused by RUM (select one)


0: No Handoff activity
1: Add a call leg to the active set
2: Drop a call leg to the active set
3: Add/Drop one leg at the same time
4: AT-Assisted IFHO
5: Directed IFHO

Number of non-Reference pilots in the RUM (0-5)

Cell site # of reference pilot

Sector Number

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-42

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Table 5-18

DO PCMD RUM Fields

Description of 1xEV-DO per-connection performance data


delivered to the OMP-FX v.2

(continued)

Field Number

Description of data

RNC ID

SN ID

Carrier Channel Number

Carrier Band Class

10

Reference Pilot PN Offset

11

Reference Pilot Strength

12

Keep indicator for reference pilot

13

Pre handoff evaluation Active Set flag


0 = not in active set
1 = in active set

14

Post handoff evaluation Active Set flag


0 = not in active set
1 = in active set

15

Handoff Complete Active Set flag


0 = no TCC
1 = TCC

16

Round Trip Delay


1 unit = 4 chips

17

Cell site # of pilot

18

Sector Number

19

RNC ID

20

SN ID

21

Carrier Channel Number

22

Carrier Band Class

23

Pilot PN Phase

24

Pilot Strength

25

Keep Indicator

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-43
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Table 5-18

DO PCMD RUM Fields

Description of 1xEV-DO per-connection performance data


delivered to the OMP-FX v.2

(continued)

Field Number

Description of data

26

Pre handoff evaluation Active Set flag:


0 = not in active set
1 = in active set
Important! This field indicates which pilots from the RUM

are currently part of the active set at the moment the RUM
message was received at the RNC.
27

Post Handoff evaluation Active Set flag:


0 = not in active set
1 = in active set
Important! This field indicates which pilots from the RUM
are added/deleted from the active set due to handoff
evaluation at the RNC.

28

Handoff Complete Active Set flag:


0 = no TCC
1 = TCC
Important! This field indicates which pilots from the RUM
were successfully added to the active set after successful
handoff.

29

Round Trip Delay


If Round Trip Delay Precision = 1, than 1 unit = 1/8 chip. If
Round Trip Delay Precision = 32, than 1 unit = 4 chips.

30

Round Trip Delay Precision


Indicates the precision of the Round Trip Delay. If 1, Round
Trip Delay is in units of 1/8 chip. If 32, Round Trip Delay
is in units of 4 chip.

Important! Fields 17 - 29 are repeated for each of the non-Reference pilots in the RUM
specified in Field 3.

The Flow data fields are shown inTable 5-19, Flow Data Fields (p. 5-44) are
appended to the end of the PCMD record.
Table 5-19

Flow Data Fields

Field Number

Description of data

Reservation Request Time Received

Reservation Label

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-44

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Table 5-19

Flow Data Fields

Description of 1xEV-DO per-connection performance data


delivered to the OMP-FX v.2

(continued)

Field Number

Description of data

Reservation Type Requested (Profile ID)

ReservationOnRequest Channel Type (Access/Traffic)


0 - Access Channel
1 - Traffic Channel

Reservation Denied
0 - False
1 - True

Reservation Flow Direction (forward/reverse)


01 - Forward
10 - Reverse
11 - Bidirectional

Flow Event Start/Open Time

Flow Event Duration

Flow Final Class


See values in Table 5-20, Flow Final Classes (FFC) and
FFC Qualifiers for Flow Reservation (p. 5-46)

10

Flow CFC Qualifier


See values in Table 5-20, Flow Final Classes (FFC) and
FFC Qualifiers for Flow Reservation (p. 5-46)

11

Flow CPFailure Value

12

SpareFlow(01)

13

SpareFlow(02)

14

SpareFlow(03)

15

SpareFlow(04)

Important! Fields 1 - 11 are repeated.

The data is repeated accordingly with the value of number of Flow Data in Record
(field 59) and that the maximum that can be reported in 1 PCMD record is 8.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-45
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Table 5-20

Description of 1xEV-DO per-connection performance data


delivered to the OMP-FX v.2

Flow Final Classes (FFC) and FFC Qualifiers for Flow Reservation
Additional Information (FFC
Qualifier)

Secondary FFCQ
(Future Use)

Flow Reservation
established and
released normally

Null

Null

Flow Reservation
Fail

201 = Flow Admission Failed

Null or Cpfail code

Value

Flow Final Class

001

002

202 = QoS Backhaul Exception

(FRF) - QoS
Requirements Not
Met
003

FRF - Resource
Problem - TP

301 = Resource Problem - TP

Null or Cpfail code

004

FRF - Resource
Problem - Cell

401 = FL RF Overload Control Cell

Null or Cpfail code

402 = RL RF Overload Control Cell


403 = FL BH Overload Control Cell
404 = RL BH Overload Control Cell
405 = FL Packet Drop by DSP Cell
406 = FL Packet Loss Due to BH
- Cell
005

Service Denial
(Authorization
Exception)

501 = BTS EQU License


Authorization Exception

Null or Cpfail code

502 = PTT License Authorization


Exception
503 = Conversational Video
License Authorization Exception
504 = VoIP (Conversational
Speech) License Authorization
Exception

006

General System
Error

Not covered by other FFCs

Null

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-46

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Per-connection performance data output examples from the


OMP-FX
v.2
...................................................................................................................................................................................................................................
Introduction

This section contains examples of the per-connection performance output data from the
OMP-FX v.2.
OMP storage control

The EV-DO PCMD process on the OMP can store eight additional previous hours of
EV-DO PCMD data, in a compressed format. Several minutes after a new log file is
started, the log file which is over two hours old is compressed. The data is compressed
using GNU Zip (GZIP).
The data for the current and previous hours are stored in uncompressed format.
Raw ASCII data

The following figures show examples of raw ASCII data output with RUM data
disabled (Figure 5-2, Example raw data output from the OMP-FX v.2 with RUM
disabled (p. 5-48)), with RUM data enabled (Figure 5-3, Example raw data output
from the OMP-FX v.2 with RUM enabled (p. 5-48)) and with Rum and Flow enabled
(Figure 5-4, Example raw data output from the OMP-FX v.2 with RUM and Flow
enabled (p. 5-48)). In these examples, the data is displayed as follows:

Each data field is separated from the other data fields by a delimiter (; or |).
The data fields are in the same order as the data fields in Table 5-11, EV-DO
PCMD record data fields - Administrative (p. 5-28) through Table 5-17, EV-DO
PCMD record data fields - Additional Data (p. 5-38).
Every field is included in this output whether the field has a value or not. If the
field does not have a value, nothing is printed for the field except the semicolon
delimiter.
There can be one through six service measurement counts that are populated in the
record. If only two are populated, the other four have no value. The Num. of SM
Count field (Field 49) specifies how many SM counts (Fields 50 through 55) are
in the record.
A cell number of zero is reported in the EV-DO PCMD when the connection fails
early in the connection, before the system recognizes which cell is involved with
setting up the connection.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-47
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Per-connection performance data output examples from


the OMP-FX v.2

Figure 5-2 Example raw data output from the OMP-FX v.2 with RUM disabled
5;32528;0123;0;0;0000000074111310;0999999812145265;19420251;73996291;;172.26.4.7;2;0;;73994798;73996293;;;;73996293;
;;;;;;7;172.26.4.15;172.47.11.1;599;3;;;;;;;;;;;;;;;;;;1;28;;;;;;0;0;;0;0;172.26.4.7;;;;;;;303;0.0.0.0;;;8;;255;;;;;
;;;;;;;;

Figure 5-3 Example raw data output from the OMP-FX v.2 with RUM enabled
5;32411;0123;0;0;000000007411130b;;170205f8;70842458;964967391;172.26.4.133;1;0;;70841791;70845753;70842479;
70842658;;;4000;1;1;;0;;7;172.26.4.142;;411;1;411;1;;70841750;0;70844700;0;425;0;425;0;425;1;;;;;5;48;19;20;49;
50;;2;1;2;0;1;172.26.4.133;;;;;;;301;0.0.0.0;;;8;411;1;;;;32;;;;;;;;;70841791;0;1;411;1;23;7;425;0;326;14;1;0;0;
0;1;32;;;;;425;0;24069;10;1;0;0;0;2;32;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;|70842847;0;1;411;1;
23;7;425;0;326;14;1;1;1;0;1;32;;;;;425;0;24069;9;1;0;0;0;2;32;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

Figure 5-4 Example raw data output from the OMP-FX v.2 with RUM and Flow
enabled
5;32545;0123;0;0;0000000074111313;0999999210677960;1a420002;;;172.26.4.71;0;;44000;;;74405166;74405357;;;116000;2;10
6;;0;;7;172.26.4.78;172.47.11.1;503;1;503;1;;;;;0;425;0;384;0;384;1;6189964;3847687;7373;0;3;19;20;21;;;;2;1;2;4;52;
172.26.4.71;;;;;;;303;0.0.0.0;;;0;503;1;;;;1;;;;;;;;;74405417;0;4;503;1;26;7;384;0;200;9;1;1;1;0;0;1;503;2;26;7;384;
0;13056;11;1;1;1;0;0;1;503;3;26;7;384;0;13312;12;1;1;1;0;0;1;503;2;26;7;425;0;13056;12;1;1;1;0;0;1;503;3;26;7;425;0;
13312;13;1;1;1;0;0;1;;;;;;;;;;;;;;|74514463;0;2;503;2;26;7;384;0;204;11;1;1;1;0;50;1;503;1;26;7;384;0;12800;9;1;1;1;
0;50;1;503;3;26;7;384;0;13312;12;1;1;1;0;50;1;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;|74407947;3;100;2;0;1;7440797
1;87166;1;;;;;;|74407955;3;100;2;0;2;74407971;87177;1;;;;;;|74407955;4;300;2;0;1;74407971;87220;1;;;;;;|74407955;4;3
00;2;0;2;74407971;87220;1;;;;;;|

Verbose data

The following figures show examples of verbose data output with RUM disabled
(Figure 4) and with RUM enabled (Figure 5) and Data Flows data fields (Figure 6).
Each data field includes a label that describes what the field contains. The data fields
are in the same order as the data fields in Table 5-11, EV-DO PCMD record data
fields - Administrative (p. 5-28) through Table 5-17, EV-DO PCMD record data
fields - Additional Data (p. 5-38).
Example verbose data output from the OMP-FX v.2 with RUM disabled
EVDO PCMD Version: 5
Sequence Number: 32528
Month and Day: 0123
Duplicate Sequence Number: 0
Mobile ID Type (ESN/MEID): 0
Mobile ID(MSN) (ESN/MEID): 0000000074111310
International Mobile Station Identifier: 0999999812145265
UATI: 19420251
UATI Complete Message Received Time: 20:33:16.2
RATI: None
Control OHM AP IP Address: 172.26.4.7
Session Request Type: 2
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-48

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Per-connection performance data output examples from


the OMP-FX v.2

Session Setup Final Class: 0


Session or Connection CPFail Value: None
Session Setup/Transfer Request Time: 20:33:14.7
Session Setup/Transfer Complete Time: 20:33:16.2
Connection Request Time: None
Connection Established Time: None
A12 RAN Authentication Time: None
A10 Link Established Time: 20:33:16.2
Connection Duration: None
Connection Final Class: None
CFC Qualifier: None
Secondary CFC Qualifier: None
AT- or AN-Initiated Connection Request: None
Silent Reorigination Flag: None
Service Node ID: 7
TP for Connection: 172.26.4.15
PDSN IP No.: 172.47.11.1
Seizure Cell Number: 599
Seizure Sector Number: 3
Last DRC-Pointed Cell: None
Last DRC-Pointed Sector Number: None
Number of DO pages: None
Configuration Negotiation Start Time: None
Configuration Negotiation Failure Code: None
Configuration Negotiation End Time: None
Seizure Band Class: None
Seizure Channel Number: None
Assigned Band Class: None
Assigned Channel Number: None
Ending Band Class: None
Ending Channel Number: None
Connection Established: None
RLP Bytes Transmitted to AT: None
RLP Bytes Received from AT: None
RLP Bytes Retransmitted to AT: None
RLP Bytes Re-received from AT: None
Number of SM Counts: 1
SM Count 1: 28
SM Count 2: None
SM Count 3: None
SM Count 4: None
SM Count 5: None
SM Count 6: None
Personality Type Used: 0
Rum Data Stored: 0
Number of RUM data stored: None
Number of Flow data included: 0
Access Round Trip Delay: 0
Last Cell-Serving OHM AP IP Address: 172.26.4.7
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-49
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Per-connection performance data output examples from


the OMP-FX v.2

Last Attempted Paging Area: None


Paging ProfileID: None
Number of QoS Pages: None
Last-Seen Cell Used for Paging: None
Last-Seen Sector Used for Paging: None
Last-Seen RNC Group Member Number Used for Paging: None
Control OHM Number: 303
Initial Access OHM AP Address: 0.0.0.0
Initial Access OHM Number: None
Subscriber Home Jurisdiction ID: None
Subscriber Home Inter-User Priority: 8
Assigned Cell Site ID For Connection: None
Assigned Sector ID For Connection: 255
SM Count 7: None
SM Count 8: None
SM Count 9: None
Access Round Trip Delay Precision: None

Example verbose data output from the OMP-FX v.2 with RUM enabled
EVDO PCMD Version: 5
Sequence Number: 32411
Month and Day: 0123
Duplicate Sequence Number: 0
Mobile ID Type (ESN/MEID): 0
Mobile ID(MSN) (ESN/MEID): 000000007411130b
International Mobile Station Identifier: None
UATI: 170205f8
UATI Complete Message Received Time: 19:40:42.4
RATI: 964967391
Control OHM AP IP Address: 172.26.4.133
Session Request Type: 1
Session Setup Final Class: 0
Session or Connection CPFail Value: None
Session Setup/Transfer Request Time: 19:40:41.7
Session Setup/Transfer Complete Time: 19:40:45.7
Connection Request Time: 19:40:42.4
Connection Established Time: 19:40:42.6
A12 RAN Authentication Time: None
A10 Link Established Time: None
Connection Duration: 4000
Connection Final Class: 1
CFC Qualifier: 1
Secondary CFC Qualifier: None
AT- or AN-Initiated Connection Request: 0
Silent Reorigination Flag: None
Service Node ID: 7
TP for Connection: 172.26.4.142
PDSN IP No.: None
Seizure Cell Number: 411
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-50

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Per-connection performance data output examples from


the OMP-FX v.2

Seizure Sector Number: 1


Last DRC-Pointed Cell: 411
Last DRC-Pointed Sector Number: 1
Number of DO pages: None
Configuration Negotiation Start Time: 19:40:41.7
Configuration Negotiation Failure Code: 0
Configuration Negotiation End Time: 19:40:44.7
Seizure Band Class: 0
Seizure Channel Number: 425
Assigned Band Class: 0
Assigned Channel Number: 425
Ending Band Class: 0
Ending Channel Number: 425
Connection Established: 1
RLP Bytes Transmitted to AT: None
RLP Bytes Received from AT: None
RLP Bytes Retransmitted to AT: None
RLP Bytes Re-received from AT: None
Number of SM Counts: 5
SM Count 1: 48
SM Count 2: 19
SM Count 3: 20
SM Count 4: 49
SM Count 5: 50
SM Count 6: None
Personality Type Used: 2
Rum Data Stored: 1
Number of RUM data stored: 2
Number of Flow data included: 0
Access Round Trip Delay: 1
Last Cell-Serving OHM AP IP Address: 172.26.4.133
Last Attempted Paging Area: None
Paging ProfileID: None
Number of QoS Pages: None
Last-Seen Cell Used for Paging: None
Last-Seen Sector Used for Paging: None
Last-Seen RNC Group Member Number Used for Paging: None
Control OHM Number: 301
Initial Access OHM AP Address: 0.0.0.0
Initial Access OHM Number: None
Subscriber Home Jurisdiction ID: None
Subscriber Home Inter-User Priority: 8
Assigned Cell Site ID For Connection: 411
Assigned Sector ID For Connection: 1
SM Count 7: None
SM Count 8: None
SM Count 9: None
Access Round Trip Delay Precision: 32
RUMData 1: RUM Storage Timestamp: 19:40:41.7
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-51
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Per-connection performance data output examples from


the OMP-FX v.2

RUMData 1: Handoff Activity caused by RUM: 0


RUMData 1: Number of NONREF_PLTS in the RUM: 1
RUMData 1: Cell site # of reference pilot: 411
RUMData 1: Reference Pilot Sector ID: 1
RUMData 1: Reference Pilot RNC ID: 23
RUMData 1: Reference Service Node ID: 7
RUMData 1: Reference Pilot Carrier Channel Number: 425
RUMData 1: Reference Pilot Band Class: 0
RUMData 1: Reference Pilot PN Offset Index: 326
RUMData 1: Reference Pilot strength: 14
RUMData 1: Keep indicator for reference pilot: 1
RUMData 1: Reference Pilot Pre Handoff Evaluation Active Set Flag: 0
RUMData 1: Reference Pilot Post Handoff Evaluation Active Set Flag: 0
RUMData 1: Reference Pilot Handoff complete active set flag : 0
RUMData 1: Reference Pilot Round trip delay: 1
RUMData 1: Reference Pilot Round trip delay Precision: 32
RUMData 1: NonReference pilots 1: Cell site number: None
RUMData 1: NonReference pilots 1: Sector number: None
RUMData 1: NonReference pilots 1: RNC Id: None
RUMData 1: NonReference pilots 1: Service Node ID: None
RUMData 1: NonReference pilots 1: Carrier Channel Number: 425
RUMData 1: NonReference pilots 1: Carrier Band Class: 0
RUMData 1: NonReference pilots 1: Pilot PN phase: 24069
RUMData 1: NonReference pilots 1: Pilot Strength: 10
RUMData 1: NonReference pilots 1: Keep indicator: 1
RUMData 1: NonReference pilots 1: Pre Handoff Evalution active set
flag: 0
RUMData 1: NonReference pilots 1: Post Handoff Evalution active set
flag: 0
RUMData 1: NonReference pilots 1: Handoff complete active set flag: 0
RUMData 1: NonReference pilots 1: Round Trip Delay: 2
RUMData 1: NonReference pilots 1: Round Trip Delay Precision: 32
RUMData 1: NonReference pilots 2: Cell site number: None
RUMData 1: NonReference pilots 2: Sector number: None
RUMData 1: NonReference pilots 2: RNC Id: None
RUMData 1: NonReference pilots 2: Service Node ID: None
RUMData 1: NonReference pilots 2: Carrier Channel Number: None
RUMData 1: NonReference pilots 2: Carrier Band Class: None
RUMData 1: NonReference pilots 2: Pilot PN phase: None
RUMData 1: NonReference pilots 2: Pilot Strength: None
RUMData 1: NonReference pilots 2: Keep indicator: None
RUMData 1: NonReference pilots 2: Pre Handoff Evalution active set
flag: None
RUMData 1: NonReference pilots 2: Post Handoff Evalution active set
flag: None
RUMData 1: NonReference pilots 2: Handoff complete active set flag: None
RUMData 1: NonReference pilots 2: Round Trip Delay: None
RUMData 1: NonReference pilots 2: Round Trip Delay Precision: None
RUMData 1: NonReference pilots 3: Cell site number: None
RUMData 1: NonReference pilots 3: Sector number: None
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-52

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Per-connection performance data output examples from


the OMP-FX v.2

RUMData 1: NonReference pilots 3: RNC Id: None


RUMData 1: NonReference pilots 3: Service Node ID: None
RUMData 1: NonReference pilots 3: Carrier Channel Number: None
RUMData 1: NonReference pilots 3: Carrier Band Class: None
RUMData 1: NonReference pilots 3: Pilot PN phase: None
RUMData 1: NonReference pilots 3: Pilot Strength: None
RUMData 1: NonReference pilots 3: Keep indicator: None
RUMData 1: NonReference pilots 3: Pre Handoff Evalution active set
flag: None
RUMData 1: NonReference pilots 3: Post Handoff Evalution active set
flag: None
RUMData 1: NonReference pilots 3: Handoff complete active set flag: None
RUMData 1: NonReference pilots 3: Round Trip Delay: None
RUMData 1: NonReference pilots 3: Round Trip Delay Precision: None
RUMData 1: NonReference pilots 4: Cell site number: None
RUMData 1: NonReference pilots 4: Sector number: None
RUMData 1: NonReference pilots 4: RNC Id: None
RUMData 1: NonReference pilots 4: Service Node ID: None
RUMData 1: NonReference pilots 4: Carrier Channel Number: None
RUMData 1: NonReference pilots 4: Carrier Band Class: None
RUMData 1: NonReference pilots 4: Pilot PN phase: None
RUMData 1: NonReference pilots 4: Pilot Strength: None
RUMData 1: NonReference pilots 4: Keep indicator: None
RUMData 1: NonReference pilots 4: Pre Handoff Evalution active set
flag: None
RUMData 1: NonReference pilots 4: Post Handoff Evalution active set
flag: None
RUMData 1: NonReference pilots 4: Handoff complete active set flag: None
RUMData 1: NonReference pilots 4: Round Trip Delay: None
RUMData 1: NonReference pilots 4: Round Trip Delay Precision: None
RUMData 1: NonReference pilots 5: Cell site number: None
RUMData 1: NonReference pilots 5: Sector number: None
RUMData 1: NonReference pilots 5: RNC Id: None
RUMData 1: NonReference pilots 5: Service Node ID: None
RUMData 1: NonReference pilots 5: Carrier Channel Number: None
RUMData 1: NonReference pilots 5: Carrier Band Class: None
RUMData 1: NonReference pilots 5: Pilot PN phase: None
RUMData 1: NonReference pilots 5: Pilot Strength: None
RUMData 1: NonReference pilots 5: Keep indicator: None
RUMData 1: NonReference pilots 5: Pre Handoff Evalution active set
flag: None
RUMData 1: NonReference pilots 5: Post Handoff Evalution active set
flag: None
RUMData 1: NonReference pilots 5: Handoff complete active set flag: None
RUMData 1: NonReference pilots 5: Round Trip Delay: None
RUMData 1: NonReference pilots 5: Round Trip Delay Precision: None
RUMData 2: RUM Storage Timestamp: 19:40:42.8
RUMData 2: Handoff Activity caused by RUM: 0
RUMData 2: Number of NONREF_PLTS in the RUM: 1
RUMData 2: Cell site # of reference pilot: 411
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-53
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Per-connection performance data output examples from


the OMP-FX v.2

RUMData 2: Reference Pilot Sector ID: 1


RUMData 2: Reference Pilot RNC ID: 23
RUMData 2: Reference Service Node ID: 7
RUMData 2: Reference Pilot Carrier Channel Number: 425
RUMData 2: Reference Pilot Band Class: 0
RUMData 2: Reference Pilot PN Offset Index: 326
RUMData 2: Reference Pilot strength: 14
RUMData 2: Keep indicator for reference pilot: 1
RUMData 2: Reference Pilot Pre Handoff Evaluation Active Set Flag: 1
RUMData 2: Reference Pilot Post Handoff Evaluation Active Set Flag: 1
RUMData 2: Reference Pilot Handoff complete active set flag : 0
RUMData 2: Reference Pilot Round trip delay: 1
RUMData 2: Reference Pilot Round trip delay Precision: 32
RUMData 2: NonReference pilots 1: Cell site number: None
RUMData 2: NonReference pilots 1: Sector number: None
RUMData 2: NonReference pilots 1: RNC Id: None
RUMData 2: NonReference pilots 1: Service Node ID: None
RUMData 2: NonReference pilots 1: Carrier Channel Number: 425
RUMData 2: NonReference pilots 1: Carrier Band Class: 0
RUMData 2: NonReference pilots 1: Pilot PN phase: 24069
RUMData 2: NonReference pilots 1: Pilot Strength: 9
RUMData 2: NonReference pilots 1: Keep indicator: 1
RUMData 2: NonReference pilots 1: Pre Handoff Evalution active set
flag: 0
RUMData 2: NonReference pilots 1: Post Handoff Evalution active set
flag: 0
RUMData 2: NonReference pilots 1: Handoff complete active set flag: 0
RUMData 2: NonReference pilots 1: Round Trip Delay: 2
RUMData 2: NonReference pilots 1: Round Trip Delay Precision: 32
RUMData 2: NonReference pilots 2: Cell site number: None
RUMData 2: NonReference pilots 2: Sector number: None
RUMData 2: NonReference pilots 2: RNC Id: None
RUMData 2: NonReference pilots 2: Service Node ID: None
RUMData 2: NonReference pilots 2: Carrier Channel Number: None
RUMData 2: NonReference pilots 2: Carrier Band Class: None
RUMData 2: NonReference pilots 2: Pilot PN phase: None
RUMData 2: NonReference pilots 2: Pilot Strength: None
RUMData 2: NonReference pilots 2: Keep indicator: None
RUMData 2: NonReference pilots 2: Pre Handoff Evalution active set
flag: None
RUMData 2: NonReference pilots 2: Post Handoff Evalution active set
flag: None
RUMData 2: NonReference pilots 2: Handoff complete active set flag: None
RUMData 2: NonReference pilots 2: Round Trip Delay: None
RUMData 2: NonReference pilots 2: Round Trip Delay Precision: None
RUMData 2: NonReference pilots 3: Cell site number: None
RUMData 2: NonReference pilots 3: Sector number: None
RUMData 2: NonReference pilots 3: RNC Id: None
RUMData 2: NonReference pilots 3: Service Node ID: None
RUMData 2: NonReference pilots 3: Carrier Channel Number: None
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-54

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
flag: None
RUMData 2: NonReference
flag: None
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
flag: None
RUMData 2: NonReference
flag: None
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
flag: None
RUMData 2: NonReference
flag: None
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference

pilots
pilots
pilots
pilots
pilots

Per-connection performance data output examples from


the OMP-FX v.2

3:
3:
3:
3:
3:

Carrier Band Class: None


Pilot PN phase: None
Pilot Strength: None
Keep indicator: None
Pre Handoff Evalution active set

pilots 3: Post Handoff Evalution active set


pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots

3:
3:
3:
4:
4:
4:
4:
4:
4:
4:
4:
4:
4:

Handoff complete active set flag: None


Round Trip Delay: None
Round Trip Delay Precision: None
Cell site number: None
Sector number: None
RNC Id: None
Service Node ID: None
Carrier Channel Number: None
Carrier Band Class: None
Pilot PN phase: None
Pilot Strength: None
Keep indicator: None
Pre Handoff Evalution active set

pilots 4: Post Handoff Evalution active set


pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots

4:
4:
4:
5:
5:
5:
5:
5:
5:
5:
5:
5:
5:

Handoff complete active set flag: None


Round Trip Delay: None
Round Trip Delay Precision: None
Cell site number: None
Sector number: None
RNC Id: None
Service Node ID: None
Carrier Channel Number: None
Carrier Band Class: None
Pilot PN phase: None
Pilot Strength: None
Keep indicator: None
Pre Handoff Evalution active set

pilots 5: Post Handoff Evalution active set


pilots 5: Handoff complete active set flag: None
pilots 5: Round Trip Delay: None
pilots 5: Round Trip Delay Precision: None

Example verbose data output of RUM and Flow data fields


EVDO PCMD Version: 5
Sequence Number: 32545
Month and Day: 0123
Duplicate Sequence Number: 0
Mobile ID Type (ESN/MEID): 0
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-55
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Per-connection performance data output examples from


the OMP-FX v.2

Mobile ID(MSN) (ESN/MEID): 0000000074111313


International Mobile Station Identifier: 0999999210677960
UATI: 1a420002
UATI Complete Message Received Time: None
RATI: None
Control OHM AP IP Address: 172.26.4.71
Session Request Type: 0
Session Setup Final Class: None
Session or Connection CPFail Value: 44000
Session Setup/Transfer Request Time: None
Session Setup/Transfer Complete Time: None
Connection Request Time: 20:40:05.1
Connection Established Time: 20:40:05.3
A12 RAN Authentication Time: None
A10 Link Established Time: None
Connection Duration: 116000
Connection Final Class: 2
CFC Qualifier: 106
Secondary CFC Qualifier: None
AT- or AN-Initiated Connection Request: 0
Silent Reorigination Flag: None
Service Node ID: 7
TP for Connection: 172.26.4.78
PDSN IP No.: 172.47.11.1
Seizure Cell Number: 503
Seizure Sector Number: 1
Last DRC-Pointed Cell: 503
Last DRC-Pointed Sector Number: 1
Number of DO pages: None
Configuration Negotiation Start Time: None
Configuration Negotiation Failure Code: None
Configuration Negotiation End Time: None
Seizure Band Class: 0
Seizure Channel Number: 425
Assigned Band Class: 0
Assigned Channel Number: 384
Ending Band Class: 0
Ending Channel Number: 384
Connection Established: 1
RLP Bytes Transmitted to AT: 6189964
RLP Bytes Received from AT: 3847687
RLP Bytes Retransmitted to AT: 7373
RLP Bytes Re-received from AT: 0
Number of SM Counts: 3
SM Count 1: 19
SM Count 2: 20
SM Count 3: 21
SM Count 4: None
SM Count 5: None
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-56

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Per-connection performance data output examples from


the OMP-FX v.2

SM Count 6: None
Personality Type Used: 2
Rum Data Stored: 1
Number of RUM data stored: 2
Number of Flow data included: 4
Access Round Trip Delay: 52
Last Cell-Serving OHM AP IP Address: 172.26.4.71
Last Attempted Paging Area: None
Paging ProfileID: None
Number of QoS Pages: None
Last-Seen Cell Used for Paging: None
Last-Seen Sector Used for Paging: None
Last-Seen RNC Group Member Number Used for Paging: None
Control OHM Number: 303
Initial Access OHM AP Address: 0.0.0.0
Initial Access OHM Number: None
Subscriber Home Jurisdiction ID: None
Subscriber Home Inter-User Priority: 0
Assigned Cell Site ID For Connection: 503
Assigned Sector ID For Connection: 1
SM Count 7: None
SM Count 8: None
SM Count 9: None
Access Round Trip Delay Precision: 1
RUMData 1: RUM Storage Timestamp: 20:40:05.4
RUMData 1: Handoff Activity caused by RUM: 0
RUMData 1: Number of NONREF_PLTS in the RUM: 4
RUMData 1: Cell site # of reference pilot: 503
RUMData 1: Reference Pilot Sector ID: 1
RUMData 1: Reference Pilot RNC ID: 26
RUMData 1: Reference Service Node ID: 7
RUMData 1: Reference Pilot Carrier Channel Number: 384
RUMData 1: Reference Pilot Band Class: 0
RUMData 1: Reference Pilot PN Offset Index: 200
RUMData 1: Reference Pilot strength: 9
RUMData 1: Keep indicator for reference pilot: 1
RUMData 1: Reference Pilot Pre Handoff Evaluation Active Set Flag: 1
RUMData 1: Reference Pilot Post Handoff Evaluation Active Set Flag: 1
RUMData 1: Reference Pilot Handoff complete active set flag : 0
RUMData 1: Reference Pilot Round trip delay: 0
RUMData 1: Reference Pilot Round trip delay Precision: 1
RUMData 1: NonReference pilots 1: Cell site number: 503
RUMData 1: NonReference pilots 1: Sector number: 2
RUMData 1: NonReference pilots 1: RNC Id: 26
RUMData 1: NonReference pilots 1: Service Node ID: 7
RUMData 1: NonReference pilots 1: Carrier Channel Number: 384
RUMData 1: NonReference pilots 1: Carrier Band Class: 0
RUMData 1: NonReference pilots 1: Pilot PN phase: 13056
RUMData 1: NonReference pilots 1: Pilot Strength: 11
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-57
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

RUMData 1:
RUMData 1:
flag: 1
RUMData 1:
flag: 1
RUMData 1:
RUMData 1:
RUMData 1:
RUMData 1:
RUMData 1:
RUMData 1:
RUMData 1:
RUMData 1:
RUMData 1:
RUMData 1:
RUMData 1:
RUMData 1:
RUMData 1:
flag: 1
RUMData 1:
flag: 1
RUMData 1:
RUMData 1:
RUMData 1:
RUMData 1:
RUMData 1:
RUMData 1:
RUMData 1:
RUMData 1:
RUMData 1:
RUMData 1:
RUMData 1:
RUMData 1:
RUMData 1:
flag: 1
RUMData 1:
flag: 1
RUMData 1:
RUMData 1:
RUMData 1:
RUMData 1:
RUMData 1:
RUMData 1:
RUMData 1:
RUMData 1:
RUMData 1:
RUMData 1:
RUMData 1:
RUMData 1:

Per-connection performance data output examples from


the OMP-FX v.2

NonReference pilots 1: Keep indicator: 1


NonReference pilots 1: Pre Handoff Evalution active set
NonReference pilots 1: Post Handoff Evalution active set
NonReference
NonReference
NonReference
NonReference
NonReference
NonReference
NonReference
NonReference
NonReference
NonReference
NonReference
NonReference
NonReference

pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots

1:
1:
1:
2:
2:
2:
2:
2:
2:
2:
2:
2:
2:

Handoff complete active set flag: 0


Round Trip Delay: 0
Round Trip Delay Precision: 1
Cell site number: 503
Sector number: 3
RNC Id: 26
Service Node ID: 7
Carrier Channel Number: 384
Carrier Band Class: 0
Pilot PN phase: 13312
Pilot Strength: 12
Keep indicator: 1
Pre Handoff Evalution active set

NonReference pilots 2: Post Handoff Evalution active set


NonReference
NonReference
NonReference
NonReference
NonReference
NonReference
NonReference
NonReference
NonReference
NonReference
NonReference
NonReference
NonReference

pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots

2:
2:
2:
3:
3:
3:
3:
3:
3:
3:
3:
3:
3:

Handoff complete active set flag: 0


Round Trip Delay: 0
Round Trip Delay Precision: 1
Cell site number: 503
Sector number: 2
RNC Id: 26
Service Node ID: 7
Carrier Channel Number: 425
Carrier Band Class: 0
Pilot PN phase: 13056
Pilot Strength: 12
Keep indicator: 1
Pre Handoff Evalution active set

NonReference pilots 3: Post Handoff Evalution active set


NonReference
NonReference
NonReference
NonReference
NonReference
NonReference
NonReference
NonReference
NonReference
NonReference
NonReference
NonReference

pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots

3:
3:
3:
4:
4:
4:
4:
4:
4:
4:
4:
4:

Handoff complete active set flag: 0


Round Trip Delay: 0
Round Trip Delay Precision: 1
Cell site number: 503
Sector number: 3
RNC Id: 26
Service Node ID: 7
Carrier Channel Number: 425
Carrier Band Class: 0
Pilot PN phase: 13312
Pilot Strength: 13
Keep indicator: 1

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-58

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Per-connection performance data output examples from


the OMP-FX v.2

RUMData 1: NonReference pilots 4: Pre Handoff Evalution active set


flag: 1
RUMData 1: NonReference pilots 4: Post Handoff Evalution active set
flag: 1
RUMData 1: NonReference pilots 4: Handoff complete active set flag: 0
RUMData 1: NonReference pilots 4: Round Trip Delay: 0
RUMData 1: NonReference pilots 4: Round Trip Delay Precision: 1
RUMData 1: NonReference pilots 5: Cell site number: None
RUMData 1: NonReference pilots 5: Sector number: None
RUMData 1: NonReference pilots 5: RNC Id: None
RUMData 1: NonReference pilots 5: Service Node ID: None
RUMData 1: NonReference pilots 5: Carrier Channel Number: None
RUMData 1: NonReference pilots 5: Carrier Band Class: None
RUMData 1: NonReference pilots 5: Pilot PN phase: None
RUMData 1: NonReference pilots 5: Pilot Strength: None
RUMData 1: NonReference pilots 5: Keep indicator: None
RUMData 1: NonReference pilots 5: Pre Handoff Evalution active set
flag: None
RUMData 1: NonReference pilots 5: Post Handoff Evalution active set
flag: None
RUMData 1: NonReference pilots 5: Handoff complete active set flag: None
RUMData 1: NonReference pilots 5: Round Trip Delay: None
RUMData 1: NonReference pilots 5: Round Trip Delay Precision: None
RUMData 2: RUM Storage Timestamp: 20:41:54.4
RUMData 2: Handoff Activity caused by RUM: 0
RUMData 2: Number of NONREF_PLTS in the RUM: 2
RUMData 2: Cell site # of reference pilot: 503
RUMData 2: Reference Pilot Sector ID: 2
RUMData 2: Reference Pilot RNC ID: 26
RUMData 2: Reference Service Node ID: 7
RUMData 2: Reference Pilot Carrier Channel Number: 384
RUMData 2: Reference Pilot Band Class: 0
RUMData 2: Reference Pilot PN Offset Index: 204
RUMData 2: Reference Pilot strength: 11
RUMData 2: Keep indicator for reference pilot: 1
RUMData 2: Reference Pilot Pre Handoff Evaluation Active Set Flag: 1
RUMData 2: Reference Pilot Post Handoff Evaluation Active Set Flag: 1
RUMData 2: Reference Pilot Handoff complete active set flag : 0
RUMData 2: Reference Pilot Round trip delay: 50
RUMData 2: Reference Pilot Round trip delay Precision: 1
RUMData 2: NonReference pilots 1: Cell site number: 503
RUMData 2: NonReference pilots 1: Sector number: 1
RUMData 2: NonReference pilots 1: RNC Id: 26
RUMData 2: NonReference pilots 1: Service Node ID: 7
RUMData 2: NonReference pilots 1: Carrier Channel Number: 384
RUMData 2: NonReference pilots 1: Carrier Band Class: 0
RUMData 2: NonReference pilots 1: Pilot PN phase: 12800
RUMData 2: NonReference pilots 1: Pilot Strength: 9
RUMData 2: NonReference pilots 1: Keep indicator: 1
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-59
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

RUMData 2: NonReference
flag: 1
RUMData 2: NonReference
flag: 1
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
flag: 1
RUMData 2: NonReference
flag: 1
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
flag: None
RUMData 2: NonReference
flag: None
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
RUMData 2: NonReference
flag: None

Per-connection performance data output examples from


the OMP-FX v.2

pilots 1: Pre Handoff Evalution active set


pilots 1: Post Handoff Evalution active set
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots

1:
1:
1:
2:
2:
2:
2:
2:
2:
2:
2:
2:
2:

Handoff complete active set flag: 0


Round Trip Delay: 50
Round Trip Delay Precision: 1
Cell site number: 503
Sector number: 3
RNC Id: 26
Service Node ID: 7
Carrier Channel Number: 384
Carrier Band Class: 0
Pilot PN phase: 13312
Pilot Strength: 12
Keep indicator: 1
Pre Handoff Evalution active set

pilots 2: Post Handoff Evalution active set


pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots

2:
2:
2:
3:
3:
3:
3:
3:
3:
3:
3:
3:
3:

Handoff complete active set flag: 0


Round Trip Delay: 50
Round Trip Delay Precision: 1
Cell site number: None
Sector number: None
RNC Id: None
Service Node ID: None
Carrier Channel Number: None
Carrier Band Class: None
Pilot PN phase: None
Pilot Strength: None
Keep indicator: None
Pre Handoff Evalution active set

pilots 3: Post Handoff Evalution active set


pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots

3:
3:
3:
4:
4:
4:
4:
4:
4:
4:
4:
4:
4:

Handoff complete active set flag: None


Round Trip Delay: None
Round Trip Delay Precision: None
Cell site number: None
Sector number: None
RNC Id: None
Service Node ID: None
Carrier Channel Number: None
Carrier Band Class: None
Pilot PN phase: None
Pilot Strength: None
Keep indicator: None
Pre Handoff Evalution active set

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-60

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Per-connection performance data output examples from


the OMP-FX v.2

RUMData 2: NonReference pilots 4: Post Handoff Evalution active set


flag: None
RUMData 2: NonReference pilots 4: Handoff complete active set flag: None
RUMData 2: NonReference pilots 4: Round Trip Delay: None
RUMData 2: NonReference pilots 4: Round Trip Delay Precision: None
RUMData 2: NonReference pilots 5: Cell site number: None
RUMData 2: NonReference pilots 5: Sector number: None
RUMData 2: NonReference pilots 5: RNC Id: None
RUMData 2: NonReference pilots 5: Service Node ID: None
RUMData 2: NonReference pilots 5: Carrier Channel Number: None
RUMData 2: NonReference pilots 5: Carrier Band Class: None
RUMData 2: NonReference pilots 5: Pilot PN phase: None
RUMData 2: NonReference pilots 5: Pilot Strength: None
RUMData 2: NonReference pilots 5: Keep indicator: None
RUMData 2: NonReference pilots 5: Pre Handoff Evalution active set
flag: None
RUMData 2: NonReference pilots 5: Post Handoff Evalution active set
flag: None
RUMData 2: NonReference pilots 5: Handoff complete active set flag: None
RUMData 2: NonReference pilots 5: Round Trip Delay: None
RUMData 2: NonReference pilots 5: Round Trip Delay Precision: None
FlowData 1: Reservation Request Time Received: 20:40:07.9
FlowData 1: Reservation Label: 3
FlowData 1: Reservation Type Requested (Profile ID): 100
FlowData 1: ReservationOnRequest Channel Type (Access/Traffic): 2
FlowData 1: Reservation Denied: 0
FlowData 1: Reservation Flow Direction (forward/reverse): 1
FlowData 1: Flow Event Start/Open Time: 20:40:07.9
FlowData 1: Flow Event Duration: 87166
FlowData 1: Flow Final Class: 1
FlowData 1: Flow CFC Qualifier: None
FlowData 1: Flow CPFail Value: None
FlowData 2: Reservation Request Time Received: 20:40:07.9
FlowData 2: Reservation Label: 3
FlowData 2: Reservation Type Requested (Profile ID): 100
FlowData 2: ReservationOnRequest Channel Type (Access/Traffic): 2
FlowData 2: Reservation Denied: 0
FlowData 2: Reservation Flow Direction (forward/reverse): 2
FlowData 2: Flow Event Start/Open Time: 20:40:07.9
FlowData 2: Flow Event Duration: 87177
FlowData 2: Flow Final Class: 1
FlowData 2: Flow CFC Qualifier: None
FlowData 2: Flow CPFail Value: None
FlowData 3: Reservation Request Time Received: 20:40:07.9
FlowData 3: Reservation Label: 4
FlowData 3: Reservation Type Requested (Profile ID): 300
FlowData 3: ReservationOnRequest Channel Type (Access/Traffic): 2
FlowData 3: Reservation Denied: 0
FlowData 3: Reservation Flow Direction (forward/reverse): 1
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-61
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

FlowData
FlowData
FlowData
FlowData
FlowData
FlowData
FlowData
FlowData
FlowData
FlowData
FlowData
FlowData
FlowData
FlowData
FlowData
FlowData

3:
3:
3:
3:
3:
4:
4:
4:
4:
4:
4:
4:
4:
4:
4:
4:

Per-connection performance data output examples from


the OMP-FX v.2

Flow Event Start/Open Time: 20:40:07.9


Flow Event Duration: 87220
Flow Final Class: 1
Flow CFC Qualifier: None
Flow CPFail Value: None
Reservation Request Time Received: 20:40:07.9
Reservation Label: 4
Reservation Type Requested (Profile ID): 300
ReservationOnRequest Channel Type (Access/Traffic): 2
Reservation Denied: 0
Reservation Flow Direction (forward/reverse): 2
Flow Event Start/Open Time: 20:40:07.9
Flow Event Duration: 87220
Flow Final Class: 1
Flow CFC Qualifier: None
Flow CPFail Value: None

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-62

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

How
data is accessed from the OMP-FX v.2
...................................................................................................................................................................................................................................
Introduction

This section presents three methods to access/view per-connection performance data


from the OMP-FX v.2.
Methods available

Per-connection performance data is accessible in two ways:

A telnet command to the OMP-FX v.2 port (7050 through 7054)


An FTP command to retrieve the EV-DO PCMD hourly file

Per-connection performance data can be viewed on the OMP-FX v.2 using the verbose
or raw EV-DO PCMD Viewers (evdo_vpcmdviewer or evdo_rpcmdviewer).
Both verbose and raw EV-DO PCMD viewers can be active at the same time because
the data source for the verbose-mode EV-DO PCMD viewer and the data source for
the raw-mode EV-DO PCMD viewer is the data files.
The EV-DO PCMD uses TCP/IP to transfer data. One TCP port allows any number of
clients. So the number of ports does not limit the number of clients.
Procedures

The following sections provide procedures for each method:

Using telnet to retrieve EV-DO PCMD data (p. 5-64)


Using FTP to retrieve EV-DO PCMD data (p. 5-66)
Using the EV-DO PCMD viewer to view EV-DO PCMD data (p. 5-68)

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-63
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Using
telnet to retrieve EV-DO PCMD data
...................................................................................................................................................................................................................................
Purpose

This procedure describes how to use telnet to retrieve per-connection performance data.
Before you begin

Verify that the implementation of the PCMD for 1xEV-DO feature is complete. For
implementation details, see Implementing the feature (p. 5-73).
Steps

Perform the following steps:


...................................................................................................................................................................................................

Enter the following command on a UNIX terminal:


telnet [omp machine] [port] [>filename]

Where:
[omp machine]
[port]

is the system name for the OMP-FX v.2

is either 7050 for human readable format or 7051 through 7054 for delimited

format.
[>filename]

is an optional redirection of output to a file, if desired

Example:
telnet ompa 7050

Result: Per-connection performance data immediately starts to stream to the


selected port (7050 through 7054). Reference: For output examples, see
Per-connection performance data output examples from the OMP-FX v.2
(p. 5-47).
...................................................................................................................................................................................................

Process the data received in the post-processing tool.


Important! The post-processing tool must be set to access the desired OMP-FX v.2
port (7050 through 7054) as described in Configured OMP-FX v.2 ports (p. 5-13)
. For guidelines on the post-processing tool, see Post-processing tool guidelines
(p. 5-15).

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-64

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Using telnet to retrieve EV-DO PCMD data

...................................................................................................................................................................................................

To stop the stream of data to the port, close the telnet window.
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-65
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Using
FTP to retrieve EV-DO PCMD data
...................................................................................................................................................................................................................................
Purpose

This procedure describes how to use FTP software to retrieve per-connection


performance data.
Before you begin

Verify that the activation of the PCMD for 1xEV-DO feature is complete. For
activation details, see Implementing the feature (p. 5-73).
Steps

Perform the following steps:


...................................................................................................................................................................................................

Enter the ftp command on a UNIX terminal:


ftp [hostname]

Where:
[hostname]

is the system name for the OMP-FX v.2

Example:
ftp ompa

Result: The system prompts for login information.


...................................................................................................................................................................................................

Enter login information.


...................................................................................................................................................................................................

Use the cd command to go to the directory location where the stored files are located:
cd /omp-data/logs/evdo_pcmd
...................................................................................................................................................................................................

Enter the ls command to display a list of directory files.


Important! Older files are in gzip format. These files can be retrieved if they are
ungzipped.
...................................................................................................................................................................................................

Enter a get command to retrieve the files:get YYMMDDHH.EVDOPCMD


where:
YY

= year

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-66

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

MM

= month

DD

= day

Using FTP to retrieve EV-DO PCMD data

HH

= hour at the end of the data collection period (in 24-hour format, for example, 15
is 3:00 PM)
The files are ASCII text with fields that are separated by a delimiter (; or |),
which is also called the raw format. For a description of the raw format, see
Per-connection performance data output examples from the OMP-FX v.2 (p. 5-47).
Result: Per-connection performance data is transferred to the specified output file.
...................................................................................................................................................................................................

Process the data received in the post-processing tool.


Important! For guidelines on how to set up the post-processing tool, see
Post-processing tool guidelines (p. 5-15).
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-67
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Using
the EV-DO PCMD viewer to view EV-DO PCMD data
...................................................................................................................................................................................................................................
Purpose

This procedure describes how to use the EV-DO PCMD viewer to view per-connection
performance data.
References

For details on OMP-FX v.2 procedures, see,OMP-FX v.2 Operation, Administration, &
Maintenance Guide, 401-662-102
For details on the OMP-FX v.2 pevdo_pcmdaemon command format and syntax, see
EV-DO PCMD viewer command format and syntax (p. 5-70).
Before you begin

Verify that the implementation of the PCMD for 1xEV-DO feature is complete. For
implementation details, see Implementing the feature (p. 5-73).
Steps

Perform the following steps:


...................................................................................................................................................................................................

Log into the OMP-FX v.2.


...................................................................................................................................................................................................

Go to the /omp/bin directory.


...................................................................................................................................................................................................

Enter the evdo_pcmdaemon command to generate the desired data format. For example:
evdo_vpcmdviewer

(in verbose mode) or evdo_rpcmdviewer (in raw mode)

For command format details, see EV-DO PCMD viewer command format and syntax
(p. 5-70).

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-68

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Using the EV-DO PCMD viewer to view EV-DO PCMD


data

Result: The EV-DO PCMD viewer immediately starts to display the data that is

being sent from the DO-RNC to the OMP-FX v.2.


Reference: For output examples, see Per-connection performance data output

examples from the OMP-FX v.2 (p. 5-47).


...................................................................................................................................................................................................

To stop the EV-DO PCMD viewer, use the interrupt character that is set for your
terminal (typically, CTRL+c).
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-69
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

EV-DO
PCMD viewer command format and syntax
...................................................................................................................................................................................................................................
Introduction

This section describes the format and syntax of the evdo_pcmdaemon UNIX command.
Description

The evdo_pcmdaemon command provides three modes:

Start mode for the verbose format


Start mode for the raw format
Help mode

Availability

The evdo_pcmdaemon command is in the /omp/bin directory.


Syntax

The syntax for the evdo_pcmdaemon command is as follows:


evdo_vpcmdviewer
evdo_rpcmdviewer
evdo_vpcmdviewer -h
evdo_rpcmdviewer -h

Syntax conventions

Options begin with a hyphen (-).


Command rules

More than one mode (option) is valid in a command line.


Option descriptions

The options for the evdo_pcmdaemon command are described in Table 5-21,
evdo_pcmdaemon command options (p. 5-70).
Table 5-21

evdo_pcmdaemon command options

Option

Description

-n

Start the evdo_vpcmdviewer and view data in human readable


format (verbose). For example, -n number, 0< = number, maximum =
maximum number that fits into signed integer ( 2, 147, 483, 647)
Start the evdo_rpcmdviewer and view data in delimited format (raw)

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-70

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Table 5-21

EV-DO PCMD viewer command format and syntax

evdo_pcmdaemon command options

(continued)

Option

Description

-h

Help mode. Provide information for the command options.

Command cancellation

The EV-DO PCMD viewer runs continuously until the tool is stopped. To stop the
EV-DO PCMD viewer, use the interrupt character that is set for your terminal
(typically, CTRL+c).
Important! Note that about a minute passes before the EV-DO PCMD viewer
stops.
Examples

Start the EV-DO PCMD viewer to display verbose format data:


evdo_vpcmdviewer

Start the EV-DO PCMD viewer to display raw format data:


evdo_rpcmdviewer

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-71
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Feature
interactions
...................................................................................................................................................................................................................................
Introduction

The PCMD for 1xEV-DO feature does not interact with other features.
The Enhancements to EVDO Per Call Service Measurements feature interacts with the
following feature:

Inter and Intra-RNC Handoff Enhancement (FID 12078.7)

Inter and Intra-RNC Handoff Enhancement

The Inter and Intra-RNC Handoff Enhancement feature adds the following new cases
to the set of PCMD events:

Personality change attempts within an RNC (intra-RNC)


Personality change attempts during an active connection, which is from current
(Rev. A) to non-current (Rev. 0)
When AT comes out of idle, including both Rev. A to Rev. 0 and Rev. 0 to Rev. A
(at connection setup)

These PCMD records indicate all personality change attempts due to changes in
coverage on the BTS where signal strength requires a personality change. In the case
of a new connection, this personality is stored as usual. In cases where an active
connection is present, and a new personality is requested, this request results in a new
connection attempt, and therefore, a new PCMD record. The Inter and Intra-RNC
Handoff Enhancement feature populates the CFCQ and Secondary CFCQ with the
result of the personality change attempt, and the new personality selected, respectively.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-72

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Implementing
the feature
...................................................................................................................................................................................................................................
Overview

To implement the PCMD for 1xEV-DO feature, perform the following procedure:
Activating the PCMD for 1xEV-DO feature (p. 5-74)

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-73
Issue 5, May 2008
See notice on first page

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Activating
the PCMD for 1xEV-DO feature
...................................................................................................................................................................................................................................
Purpose

This procedure activates the PCMD for 1xEV-DO feature in a CDMA2000 1xEV-DO
network.
The following parameters set by the EMS CM management interface control how the
PCMD for 1xEV-DO behaves.

PCMD (PCMDevdoEnable)

- Determines whether EV-DO PCMD features should be

activated.

PCMD Normal (PCMDevdoNormConn) - Determines whether EV-DO PCMD data that


is associated with normal connections should be omitted from output. However,
when this parameter is enabled the EV-DO PCMD data is included.
PCMD Normal Sessions (PCMDevdoNormSess) - Determines whether EV-DO
PCMD data that is associated with sessions should be omitted from output.
However, when this parameter is enabled the EV-DO PCMD data is included.
PCMD Master Key (PCMDevdoMasterKey) - Determines whether EV-DO PCMD
has been allowed on this service node via a FAF entry. This is a display string. The
granularity of this key is for the entire Service Node.
PCMD RUM Collections (PCMDevdoRUM) - Determines whether data from the first
and last RUM messages that occur during a PCMD Interval is included in the
PCMD record.

Procedure

Perform the following steps:


...................................................................................................................................................................................................

Ask your account executive to activate the following entry in your Feature Activation
File (FAF):
EVDO PCMD
...................................................................................................................................................................................................

From the EMS FMS Frame view, activate the PCMD control through the PCMD
parameter.
Important! The user is required to enable PCMD (PCMDevdoEnable) before setting
any of the other parameters.
...................................................................................................................................................................................................

Click Submit.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

5-74

Per Call Measurement Data (PCMD) for CDMA 3G-1x


EVolution Data Optimized (1xEV-DO)

Activating the PCMD for 1xEV-DO feature

...................................................................................................................................................................................................

Activate any other control form the EMS FMS Frame view (such as,
PCMD Normal Connections, PCMD Normal Sessions, PCMD RUM Collections).

Important! These parameters may be enabled separately or together.


...................................................................................................................................................................................................

Click Submit.
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-75
Issue 5, May 2008
See notice on first page

6 igh Rate Packet Data Radio


H
Network Controller (HRPD
RNC) Performance and Capacity
Improvements

Overview
...................................................................................................................................................................................................................................
Purpose

This optional feature description describes the High Rate Packet Data Radio Network
Controller (HRPD RNC.) Performance and Capacity Improvements optional feature in
CDMA2000 1xEV-DO networks.
Feature summary

The HRPD RNC Performance and Capacity Improvements feature improves the
performance and capacity of the FMS-based CDMA 3G-1x Evolution Data Optimized
(1xEV-DO) RNC by:

supporting up to 260 carriers


supporting up to 40,000 (active plus dormant) sessions per Application Processor
(AP) and 20,000 dormant sessions per Force690/Artesyn752i Traffic Processor (TP)
board
supporting up to 1000 active users per Force690/Artesyn752i TP board.

Feature Identifier (FID)

A unique feature identifier (FID) number is assigned to each feature. This chapter
supports HRPD RNC Performance and Capacity Improvements (FID 10607.3).
Impacts on user interfaces

The HRPD RNC Performance and Capacity Improvements affects the user interfaces
that are listed in the following table.
User interface

Feature impact

Element Management System (EMS)

See Implementing the feature (p. 6-9)

....................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
6-1
Issue 5, May 2008
See notice on first page

High Rate Packet Data Radio Network Controller (HRPD


RNC) Performance and Capacity Improvements

Overview

User interface

Feature impact

Operations and Maintenance Center Radio Access Network (OMC-RAN)

For information on configuring with


OMC-RAN, see Implementing the
feature (p. 6-9)

Service measurements

None

Automatic Message Accounting (AMA)


subsystem

None

Technician Interface (TI) (input/output


messages)

None

To obtain technical support, documentation, and training or submit feedback

The Online Customer Support (OLCS) web site (http://support.lucent.com/) provides


access to technical support, related documentation, related training, and feedback tools.
The site also provides account registration for new users.
Contents
Availability

6-3

Prerequisites

6-4

Feature description

6-5

Feature interactions

6-7

Issues and caveats

6-8

Implementing the feature

6-9

Activating the feature

6-10

Activating the Carrier Capacity Enhancement

6-11

Deactivating the feature

6-13

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

6-2

High Rate Packet Data Radio Network Controller (HRPD


RNC) Performance and Capacity Improvements

Availability
...................................................................................................................................................................................................................................
Release availability

The HRPD RNC Performance and Capacity Improvements feature is available in DO


RNC Release 26.0 and later.
Market availability

The HRPD RNC Performance and Capacity Improvements feature is available in all
markets.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
6-3
Issue 5, May 2008
See notice on first page

High Rate Packet Data Radio Network Controller (HRPD


RNC) Performance and Capacity Improvements

Prerequisites
...................................................................................................................................................................................................................................
Introduction

The HRPD RNC Performance and Capacity Improvements feature has the following
prerequisites.
Supported technologies

The HRPD RNC Performance and Capacity Improvements feature is supported in the
following air-interface technologies:

1xEV-DO

Software requirements

The HRPD RNC Performance and Capacity Improvements feature requires

OMP-FX Release R26.0 or later


RNC Release: R26.0 or later
Cell Release (1xEV-DO): R24.0 or later

The HRPD RNC Performance and Capacity Improvements feature is not dependent on
any R26.0 or earlier features, but does have interactions with several features. See
Feature interactions (p. 6-7) for further details.
Hardware requirements

The HRPD RNC Performance and Capacity Improvements feature requires no


hardware beyond the standard hardware in a CDMA2000 1xEV-DO network.
Interface requirements

The processing of A11 messages moves to the Traffic Processor (TP) from the
Application Processor (AP). Standard A11 mechanisms (MD5 authentication and
timestamp replay protection) continue to provide security.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

6-4

High Rate Packet Data Radio Network Controller (HRPD


RNC) Performance and Capacity Improvements

Feature
description
...................................................................................................................................................................................................................................
Introduction

The following information describes the functionality, benefits, and operation of the
HRPD RNC Performance and Capacity Improvements feature.
Functionality

The HRPD RNC Performance and Capacity Improvements feature provides


enhancements to the R25.0 FMS RNC Carrier Count and Session Capacity Increase
feature (FID 10607.2), which had increased the maximum number of configured
carriers and cells to 130 in order to increase the number of cell coverage per RNC
frame, but not the overall RNC performance.
The HRPD RNC Performance and Capacity Improvements feature expands support to
260 Rev 0 Carriers providing improved Forward Link Throughput for the RNC. These
improvements are applicable for the FMS platform (1xEV-DO RNC) and are achieved
through software optimization.
The A11 Packet Control Function (PCF) function is moved to the TP to improve
overall system capacity by eliminating the TP-to-A11-PCF interface, removing the A11
proxy function, and creating additional capacity for AP processing. Additional upgrades
indicate that the number of active and dormant connections per RNC frame has been
increased, this improvement proportionately supports the required 260 carriers.
Benefits

The HRPD RNC Performance and Capacity Improvements feature (10607.3) is a


performance improvement feature offering the following improvements over the R25.0
FID 10607.2:
Per

R25.0

R26.0

AP

26,000 total sessions

40,000 total sessions

TP

13,000 dormant sessions

20,000 dormant sessions

TP

520 active users

1000 active users

RNC

130 carriers

260 carriers

Additionally, file transfer protocol (ftp) transfers have improved throughput on forward
and reverse links and there is significant speed up of the evcup command.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
6-5
Issue 5, May 2008
See notice on first page

High Rate Packet Data Radio Network Controller (HRPD


RNC) Performance and Capacity Improvements

Feature description

How the feature operates

The HRPD RNC Performance and Capacity Improvements feature impacts

A11 message processing at the AP,


TP processing and the IP Stack, and
Operations, Administration and Maintenance (OA&M) (System Initialization Time
Reduction, Service Measurements).

Database view collation changes have been implemented in an effort to minimize the
1xEV-DO controller software initialization times. The changes will decrease the
initialization time for evcup after AP failover, application process failover, and
individual AP and application process initialization durations.
AP process optimization

The basic changes required to support 260 carriers involve increasing the number of
calls supported per AP from 26,000 to up to 40,000. This is accomplished by
increasing the number of Overhead Manager Access Terminal (OHMAT) objects and
by modifying the way Unicast Access Terminal Identifiers (UATIs) are allocated by the
AP.
A11 processing moved from AP to TP

In the R25.0 FMS RNC, the A11 functionality was built into the A11 message
processing at the AP, whereas the actual A11 termination as seen by the Packet Data
Serving Node (PDSN) was at the TP. By migrating the A11 functionality into the TP in
R26.0, internal message flow is reduced from 5 messages to 2. A distributed A11
message processing at the AP architecture also improves reliability and scalability.
TP process optimization

The TP performance was improved by reducing memory copies in the bearer stack and
by optimizing the usage of timers.
OAM link configuration

The OAM links on the first 4 APs are configured on the AP side for 10 Mbps half
duplex rather than auto negotiate. RNC retrofit procedures preserve this setting. The
same switch may be used for the GigE and OA&M links, however in this case the
OAM links will be assigned to a separate (port-based) VLAN.
Service provider perspective

The HRPD RNC Performance and Capacity Improvements feature requires service
providers to perform the following task after the FAF is activated:

Activate the Carrier Capacity Enhancement parameter on the EMS (or OMC-RAN).

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

6-6

High Rate Packet Data Radio Network Controller (HRPD


RNC) Performance and Capacity Improvements

Feature
interactions
...................................................................................................................................................................................................................................
Introduction

The HRPD RNC Performance and Capacity Improvements feature interacts with the
following features:

Support for Multiple 1xEV-DO Carriers IFHO - FID 8219.11


Support for Multiple 1xEV-DO Carriers Enhancements - FID 8219.2.
Increasing 1xEV-DO Limits on the OMP-FX Netra 440 - FID 12518.0

Support for Multiple 1xEV-DO Carriers Enhancements feature

The HRPD RNC Performance and Capacity Improvements feature allows single-sector
carrier cells to support a total of 260 cells per RNC. If the cells are 3 carrier cells
(introduced by the Support for Multiple 1xEV-DO Carriers Enhancements feature), a
maximum of 87 cells are supported per RNC frame.
Increasing 1xEV-DO Limits on the OMP-FX Netra 440

While the OMP-FX Release R26.0 supports the HRPD RNC Performance and Capacity
Improvements feature, the OMP-FX Netra 440 (OMP-FX v.2) provides additional
growth opportunities in conjunction with the Increasing 1xEV-DO Limits on the
OMP-FX Netra 440 feature, allowing the EMS/OMP-FX v.2 to support maximum
number of cells and 600 carriers per Service Node.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
6-7
Issue 5, May 2008
See notice on first page

High Rate Packet Data Radio Network Controller (HRPD


RNC) Performance and Capacity Improvements

Issues
and caveats
...................................................................................................................................................................................................................................
Introduction

The HRPD RNC Performance and Capacity Improvements feature is subject to the
following special issues and/or caveats.
Issues

There are no issues associated with this feature.


Caveats

The R26.0 base release includes the software optimization and architectural
improvements without FAF control. The FAF for FID 10607.3 controls the portions of
the feature that provide

the number of carriers that may be supported and


the maximum number of total and dormant sessions allowed.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

6-8

High Rate Packet Data Radio Network Controller (HRPD


RNC) Performance and Capacity Improvements

Implementing
the feature
...................................................................................................................................................................................................................................
Overview

To implement the HRPD RNC Performance and Capacity Improvements feature,


perform the following procedures:
Activating the feature (p. 6-10)
Activating the Carrier Capacity Enhancement (p. 6-11)
Deactivating the feature (p. 6-13)

Operations and Maintenance Center - Radio Access Network (OMC-RAN) configuration


management

For more information about the different 1xEV-DO OA&M interfaces that are used in
performing OA&M tasks on the EV-DO controller and its managed resouces,
including the purpose of each interface and how to access it, see Alcatel-Lucent 9271
EV-DO Radio Network Controller, 401-614-102, Chapter 3, User Interfaces.
See Appendix 7 of Alcatel-Lucent 9271 EV-DO Radio Network Controller,
401-614-102 for basic information in order to:

understand the OMC-RAN,


understand the layout of EV-DO information on the OMC-RAN, and
provisioning activities on EV-DO network and elements from the OMC-RAN.

Also see the About this information product at the beginning of this document for
the most commonly-used ways to find certain information on EMS and where to find
the equivalent information on the OMC-RAN, or CDMA2000 1xEV-DO
Configurations Parameters Guide, 401-614-324.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
6-9
Issue 5, May 2008
See notice on first page

High Rate Packet Data Radio Network Controller (HRPD


RNC) Performance and Capacity Improvements

Activating
the feature
...................................................................................................................................................................................................................................
Purpose

This procedure activates the HRPD RNC Performance and Capacity Improvements
feature in a CDMA2000 1xEV-DO network.
Procedure

Perform the following steps:


...................................................................................................................................................................................................

Ask your account executive to activate the following entry in your Feature Activation
File (FAF):
1xEV-DO HRPD RNC Performance and Capacity Improvements to support 260
Rev 0 carriers
...................................................................................................................................................................................................

Proceed to Activating the Carrier Capacity Enhancement (p. 6-11).


END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

6-10

High Rate Packet Data Radio Network Controller (HRPD


RNC) Performance and Capacity Improvements

Activating
the Carrier Capacity Enhancement
...................................................................................................................................................................................................................................
Purpose

This procedure activates the Carrier Capacity Enhancement component of the HRPD
RNC Performance and Capacity Improvements feature in a CDMA2000 1xEV-DO
network.
For detailed procedures, see CDMA2000 1xEV-DO Radio Access System Planning
and Implementation Guide, 401-614-101 or 401-710-110, Element Management System
(EMS) Users Guide.
Prerequisites

The
1xEV-DO HRPD RNC Performance and Capacity Improvements to support
260 Rev 0 carriers FAF must be activated.

Procedure

Perform the following steps:


...................................................................................................................................................................................................

Access the OMP Web page according to your local practices.


Result: The OMP Web page appears.
...................................................................................................................................................................................................

Click on the Configuration Data icon.


Result: The Configuration Data page appears. It lists the components that can be

configured.
...................................................................................................................................................................................................

In the list of blue navigation buttons on the left side of this EMS page, click on the
link titled Service Nodes. (You may need to scroll down to see that link.)
Result: The Service Node Summary page appears.
...................................................................................................................................................................................................

Click on the link titled General - section 3.


Result: The General - section 3 page appears.
...................................................................................................................................................................................................

Set the Carrier Capacity Enhancement parameter to On


...................................................................................................................................................................................................

Click the Submit button at the bottom of the page. (Scroll down to see this button.)

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
6-11
Issue 5, May 2008
See notice on first page

High Rate Packet Data Radio Network Controller (HRPD


RNC) Performance and Capacity Improvements

Activating the Carrier Capacity Enhancement

Result: You have activated the Carrier Capacity Enhancement parameter.


END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

6-12

High Rate Packet Data Radio Network Controller (HRPD


RNC) Performance and Capacity Improvements

Deactivating
the feature
...................................................................................................................................................................................................................................
Purpose

This procedure deactivates the HRPD RNC Performance and Capacity Improvements
feature.
Important! In order to deactivate the HRPD RNC Performance and Capacity
Improvements feature, the Carrier Capacity Enhancement component must first be
turned off, followed by turning off the entry in the FAF.
For detailed procedures, see CDMA2000 1xEV-DO Radio Access System Planning
and Implementation Guide, 401-614-101 or 401-710-110, Element Management System
(EMS) Users Guide.
Prerequisites

Both the
1xEV-DO HRPD RNC Performance and Capacity Improvements to support
260 Rev 0 carriers FAF entry and the Carrier Capacity Enhancement

parameter are activated.


Only 130 or fewer carriers may be provisioned on the system in order to turn this
feature off. If more than 130 carriers are provisioned, the Carrier Capacity
Enhancement parameter cannot be deactivated. If more than 130 carriers are
provisioned, deprovision the necessary number of carriers before beginning this
procedure.

Procedure

Perform the following steps:


...................................................................................................................................................................................................

Access the OMP Web page according to your local practices.


Result: The OMP Web page appears.
...................................................................................................................................................................................................

Click on the Configuration Data icon.


Result: The Configuration Data page appears. It lists the components that can be

configured.
...................................................................................................................................................................................................

In the list of blue navigation buttons on the left side of this EMS page, click on the
link titled Service Nodes. (You may need to scroll down to see that link.)

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
6-13
Issue 5, May 2008
See notice on first page

High Rate Packet Data Radio Network Controller (HRPD


RNC) Performance and Capacity Improvements

Deactivating the feature

Result: The Service Node Summary page appears.


...................................................................................................................................................................................................

Click on the link titled General - section 3.


Result: The General - section 3 page appears.
...................................................................................................................................................................................................

Set the Carrier Capacity Enhancement parameter to Off.


Important! If more than 130 carriers are provisioned, the Carrier Capacity
Enhancement parameter cannot be turned off.
...................................................................................................................................................................................................

Click the Submit button at the bottom of the page. (Scroll down to see this button.)
Result: You have deactivated the Carrier Capacity Enhancement parameter.
...................................................................................................................................................................................................

Ask your account executive to deactivate the following entry in your Feature
Activation File
(FAF):1xEV-DO HRPD RNC Performance and Capacity Improvements to support
260 Rev 0 carriers
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

6-14

7 Volution Data Optimized


E
(1xEV-DO) Basic Revision A
(Rev. A) Feature Bundle

Overview
...................................................................................................................................................................................................................................
Purpose

This optional feature description describes the following EVolution Data Optimized
(1xEV-DO) Basic Revision A (Rev. A) Feature Bundle in CDMA 1xEV-DO networks.
A unique Feature Identifier (FID) is assigned to each feature:
Basic Rev. A Feature Bundle:

Enhanced Reverse and Forward Links using Enhanced MAC Protocols with Rev. A
Subtype 2 Physical Layer (FID 12078.2)
Generic Attribute Update Protocol (GAUP) for Dynamic Parameters Update (FID
12078.3)
High Rate Packet Data (HRPD) Rev. A Support on Modular Cell 1-3 BTS
Platforms using SB-EVMm (FID 12078.4)
High Rate Packet Data (HRPD) Rev. A Support on Modular Cell 4.0 BTS
Platforms using SB-EVM (FID 12078.5)
Inter and Intra-Radio Network Controller (RNC) Handoff Enhancement (FID
12078.7)

Feature summary

FIDs 12078.2, 12078.3, 12078.4, 12078.5 and 12078.7 make up the software collection
referred to as Rev. A Basic Feature Bundle and are activated via a software licensing
key mechanism instead of the usual Feature Activation File/Qualified Feature
Activation File (FAF/QFAF) mechanism.
The Basic Rev. A Feature Bundle license key must be purchased in order to enable
Mandatory Rev. A functionality. The license key is used for the activation of the Rev.
A Basic Feature Bundle for one or more Rev. A-capable Base Transceiver Station
(BTS)-Carriers served by the RNC.

....................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
7-1
Issue 5, May 2008
See notice on first page

EVolution Data Optimized (1xEV-DO) Basic Revision A


(Rev. A) Feature Bundle

Overview

Mandatory Rev A license key is managed by the RNC and is enabled per carrier. For
example:

Base station 1 has one Rev A carrier, therefore, 1 Rev A license is required.
Base station 2 has two Rev A carriers, therefore, 2 Rev A licenses are required.
Base station 3 has three Rev A carriers, therefore, 3 Rev A licenses are required.

The service provider needs to install the license key via Element Management System
(EMS) and assign license keys to the base station carriers to enable the base station
carrier(s).
When the Basic Rev. A Features are activated within the Radio Access System they are
referred to as HRPD Rev. A system.
The HRPD Rev. A system supports Release 27.0 and later FIDs and any new Rev. A
features.
Enhanced Reverse and Forward Links using Enhanced MAC Protocols with Rev.
A Subtype 2 Physical Layer (FID 12078.2)

This feature is part of the Rev. A Basic package of features, also referred to as Basic
Rev. A Feature Bundle. This feature introduces the support of the full Rev. A Physical
Layer with the complete set of Rev. A enhanced Medium Access Control (MAC)
protocols. The following MAC protocols are supported:

Enhanced Control Channel (CC) MAC


Enhanced Forward Traffic Channel (FTC) MAC
Enhanced Access Channel (AC) MAC
Enhanced Subtype 3 Reverse Traffic Channel (RTC) MAC

This feature is supported on all Modular Cell BTS types using the new HRPD Rev. A
modem board, the SB-EVM for Modular Cell 4.0 and variants or the SB-EVMm for
Modular Cell 1-3. This feature is supported only by the Rev. A capable RNC.
Generic Attribute Update Protocol (GAUP) for Dynamic Parameters Update (FID
12078.3)

This feature is part of the Rev. A Basic package of features. This feature allows
configuration attribute changes without costly session configuration protocol exchange
and without releasing the connection. It allows the AT and the AN to use the GAUP to
update values of the session parameter attributes belonging to different lower and
higher layer protocols and applications.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

7-2

EVolution Data Optimized (1xEV-DO) Basic Revision A


(Rev. A) Feature Bundle

Overview

HRPD Rev. A Support on Modular Cell 1-3 BTS Platforms using SB-EVMm (FID
12078.4)

This feature is part of the Rev. A Basic package of features and provides the necessary
hardware and software for the Modular Cell 1-3 products to make use of any other
Rev. A feature. This feature includes Software, OA&M and Service Measurements
support related to HRPD Rev. A for the Modular Cell 3.0, Modular Cell 2.0 and
Modular Cell 1.0.
The term Modular Cell 1-3 is used in this chapter to include the variants listed above.
HRPD Rev. A Support on Modular Cell 4.0 BTS Platforms using SB-EVM (FID
12078.5)

This feature is part of the Rev. A Basic package of features and provides the necessary
hardware and software for the Modular Cell 4.0 products to make use of any other
Rev. A feature. This feature supports HRPD Rev. A technology on all Modular Cell 4.0
Platforms. This feature includes Software, OA&M and Service Measurements support
related to HRPD Rev. A for the Modular Cell 4.0 platforms.
The following Modular Cell 4.0 products will be supported:

Modular Cell 4.0


Modular Cell 4.0 B
Compact 4.0
Compact 4.0 B
HD 4.0
HD 4.0 B

The term Modular Cell 4.0 is used in this chapter to include the variants listed above.
Inter and Intra-RNC Handoff Enhancement (FID 12078.7)

This feature is part of the Rev. A Basic package of features. This feature supports, in
both Rel 0 systems and in mixed Rel 0/Rev. A systems:

every type of handoff that is currently supported in a Rel 0 system (soft/softer on


traffic channel; hard handoff across carriers on traffic channel; inter-RNC dormant
session handoff)
handoffs from Rev. A PHYsical/Medium Access Control (PHY/MAC) connections
to Rel 0 PHY/MAC connections.

This feature does not include active handoff from Rel 0 to Rev. A systems.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
7-3
Issue 5, May 2008
See notice on first page

EVolution Data Optimized (1xEV-DO) Basic Revision A


(Rev. A) Feature Bundle

Overview

Impacts on user interfaces

The features that are described in this chapter impact the following user interfaces:
Feature

User interface

Feature impact

Rev. A Basic
Feature
Bundle: FIDs
12078.2,
12078.3,
12078.4,
12078.5,
12078.7

Element Management System


(EMS) or Operations and
Maintenance Center - Radio
Access Network (OMC-RAN)

None

Service measurements

For information on configuring


parameters related to this feature,
see Impacts on service
measurements (p. 7-15).

Automatic Message Accounting


(AMA) subsystem

None

Technician Interface (TI)


(input/output messages)

None

To obtain technical support, documentation, and training or submit feedback

The Online Customer Support (OLCS) web site (http://support.lucent.com/) provides


access to technical support, related documentation, related training, and feedback tools.
The site also provides account registration for new users.
Contents
Availability

7-5

Prerequisites

7-6

Feature description: Basic Rev. A Feature Bundle

7-7

Feature interactions

7-14

Impacts on service measurements

7-15

Implementing the features

7-30

Activating the feature

7-31

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

7-4

EVolution Data Optimized (1xEV-DO) Basic Revision A


(Rev. A) Feature Bundle

Availability
...................................................................................................................................................................................................................................
Release availability

The 1xEV-DO Basic Rev. A Feature Bundle are available in 1xEV-DO Releases 28.0
and later.
Market availability

The 1xEV-DO Basic Rev. A Feature Bundle are available in all regions.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
7-5
Issue 5, May 2008
See notice on first page

EVolution Data Optimized (1xEV-DO) Basic Revision A


(Rev. A) Feature Bundle

Prerequisites
...................................................................................................................................................................................................................................
Introduction

The 1xEV-DO Basic Rev. A Feature Bundle have the following prerequisites.
Supported technologies

The 1xEV-DO Basic Rev. A Feature Bundle are supported in the following air-interface
technology:

1xEV-DO

Software requirements

The 1xEV-DO Basic Rev. A Feature Bundle require Release 27.0 or later.
Hardware requirements

The 1xEV-DO Basic Rev. A Feature Bundle requires the standard in a CDMA
1xEV-DO network hardware.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

7-6

EVolution Data Optimized (1xEV-DO) Basic Revision A


(Rev. A) Feature Bundle

Feature
description: Basic Rev. A Feature Bundle
...................................................................................................................................................................................................................................
Introduction

The following information defines the functionality, benefits, and operation of Basic
Rev. A Feature Bundle.
Functionality

High Rate Packet Data (HRPD) Rev. A is a collection of software features (FIDs
12078.2, 12078.3, 12078.4, 12078.5 and 12078.7) in a Feature Bundle or package, to
provide the main Rev. A functionality. The Package is referred to as Basic Rev. A
Feature Bundle. This bundle of features is mandatory to support 1xEV-DO Rev. A and
is activated via a software licensing key mechanism instead of the usual FAF/QFAF.
Benefits

Several enhancements have been introduced in Rev. A which allow customers to


provide higher data rates especially in the reverse link moreover to support a variety of
applications:

Improved Reverse Link


Up to 1.8 Mbps data rate
Improved Reverse Link Improved MAC, throughput and latency gains with
H-ARQ
Improved Forward Link
Up to 3.1Mbps data rate
Improved MAC & MUP Support

How the feature operates

Basic Rev. A Operation requires an SB-EVM or SB-EVMm hardware per Base


Transceiver Station (BTS)-carrier supporting Rev. A operation, and must have the
software enabled for Rev. A operation by a license key per BTS-carrier. Enabling the
BTS-carrier allows operators to use SB-EVM and SB-EVMm for Rel 0 carriers
without purchasing the Basic Rev. A Feature Bundle. The license key in an RNC will
limit the number of Rev. A enabled BTS-carriers. This license, known as the Rev. A
license, will be installed by a manual license key procedure on each RNC intended to
host a Rev. A enabled BTSs. The RNC will perform Rev. A functions for any
BTS-carrier that is Rev. A enabled. The EMS will be blocked, by the RNC, from
enabling any BTS-carrier for Rev. A operation if the license key is not present, or if
there are already as many BTS-carriers enabled on the RNC as the license-key limit
allows.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
7-7
Issue 5, May 2008
See notice on first page

EVolution Data Optimized (1xEV-DO) Basic Revision A


(Rev. A) Feature Bundle

Feature description: Basic Rev. A Feature Bundle

The Rev. A software license key is used to:

enable one or more BTS-Carriers to support features included in the Basic Rev. A
Feature Bundle served by the RNC, and
allow RNC application to set up Rev. A connections from a Basic Rev. A Feature
Bundle- enabled.

The Rev. A Release RNC base software supports parts of the Basic Rev. A operation
which do not depend on the enhanced physical layer (without control of the license
key). That includes multiple personalities negotiation and changing the personality in
the AT by GAUP, and communicating those personalities on A13. All Rev-A operations
which require the enhanced physical layer will be under control of the Rev. A license
key.
The following scenario explains at high level the activation process of the Basic Rev.
A Feature Bundle using the license key:

Customer requests quote for Basic Rev A Feature Bundle.


In order to create a quote, the CT must acquire the following attribute data:
Lead AP Server Pair Host ID (alpha-numeric)
Service Node ID (alpha-numeric)
RNC Frame ID (alpha-numeric)
Number of additional Rev A carriers
Existing number of Rev A carriers available on DO-RNC
Ship-to E-mail address OR to LED indicator
CT creates quote and a STARS Number is created.
Basic Rev A quote is delivered to the Customer with appropriate OIs and
necessary attribute data to generate the license key.
Customer PO sent to service provider.
Order is checked to ensure that an appropriate number of Rev A RTU fees for the
base stations have been previously purchased by the customer:
If sufficient base station Rev A RTUs, the total for the customers network is
decremented.
If there is insufficient base station Rev A RTUs to fill the order, CT is
contacted to resolve situation.
AP Host ID, RNC Frame ID and Service Node ID are checked to ensure
consistency with order history. If not, CT is contacted to resolve situation.
To generate the license key, add the incremental license key purchased to the
running total and generate a key with the new total. If issues arise, CT is contacted
to resolve them, for example:
License key(s) generated within 3-4 business days.
License key(s) shipped to E-mail address/contact on order or posted to LED.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

7-8

EVolution Data Optimized (1xEV-DO) Basic Revision A


(Rev. A) Feature Bundle

Feature description: Basic Rev. A Feature Bundle

Customer receives license key(s).

Customer gets invoiced for Basic Rev A Package.

Customer installs license key(s) per procedures found in document 1xEV-DO RAS
Planning and Implementation Guide, 401-614-101.

Service provider perspective

The service provider is charged as Right To Use (RTU) fee for each license key. This
is ananlogous to the Rel 0 license key implemented for some other FIDs. Service
providers are charged the Rev. A license fee on top of current Rel 0 license fees.
The serve provider is able to view from the EMS:

At RNC level the number of BTS-Carrier allowed by the software license key and
At RNC level the number of BTS-carrier activated for Rev. A service Package
At BTS level the BTS-Carrier that has been activated for the Basic Rev. A Feature
Bundle

Enhanced Reverse and Forward Links using Enhanced MAC Protocols with Rev. A Subtype 2
Physical Layer (FID 12078.2)

This feature provides the following improvement:


New Rev. A Physical Layer packet types and sizes to improve packing efficiency and
consequently increase the air interface capacity. Packet sizes are from 128 bits to 5120
bits in the FL and from 128 bits to 12288 bits in RL:

Smaller payloads introduced to improve packing efficiency.


Larger payloads introduced and this also useful by multiplexing several higher
layer packets (to one or different users) into one physical layer packet.

New data rates have been introduced in both FL and RL:

In the FL the data rates are from 4.8 kbps (Rel 0 minimum data rate is 38.4 kbps)
to 3.072 Mbps (Rel 0 highest data rate is 2457.6 kbps) and in the RL data rates are
from 4.8 kbps (Rel 0 minimum data rate is 9.6 kbps) and up to 1843.2 kbps (Rel 0
highest data rate is 153.6 kbps).

RL incremental redundancy and early termination: Each packet consists of up to four


4-slot sub-packets: Transmission of the packet may use 1, 2, 3 or 4 sub-packets with
each one spanning over 4 slots and this reduces the delay and increase throughput.
Support physical-layer hybrid ARQ:

AT transmits each RL sub-packet incrementally. If the AT receives a NAK, it


subsequently transmits the next subpacket. It terminates the transmission if it
receives an ACK, hence this yields to a higher throughput.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
7-9
Issue 5, May 2008
See notice on first page

EVolution Data Optimized (1xEV-DO) Basic Revision A


(Rev. A) Feature Bundle

Feature description: Basic Rev. A Feature Bundle

Enhanced RTC MAC which supports:

Different types of applications on top of Rev. A Physical Layer.


Traffic-to-Pilot (T2P) Resource allocation allows a user in a good RF condition to
transmit at a higher rate while Rel 0 MAC does not provide such distinction. Also,
it allows more T2P values even for the same encoder packet size such that a
different PER can be achieved easily.
Traffic-to-Pilot Token Bucket Operation allows users with bursty traffic to transmit
at high data rate when needed.
Low Latency and High Capacity Modes.

Enhanced FTC MAC allows MAC Layer Packing and Multi-Users Packet (MUP):

A single physical-layer packet contains one or more upper-layer packets addressed


to one or different users.
MUP is beneficial to certain applications such as Voice Over IP (VoIP) in both
increasing the capacity and reducing the delay.

Enhanced CC MAC:

New rate at 19.2 kbps in addition to the existing rates of 38.4 kbps and 76.8 kbps.
New packet sizes of 128, 256, 512 or 1024 bits (in Rel 0 only 1024 bits is
supported).
A single-user page of 4-slot transmission versus default control channel of 16-slots.
This allows for quick paging of the mobile.

Enhanced AC MAC:

New data rates at 9.6 kbps, 19.2 kbps and 38.4 kbps (in Rel 0 only 9.6 kbps is
supported). The new higher data rates reduce the channel setup delay.
New packet sizes of 256, 512 or 1024 bits (in Rel 0 only 256 bits is supported).
New ARQ Forward Link Channel which provides a convenient framework to
support the RTC MAC protocol in reducing the delay.
New Data Source Control Channel for seamless cell selection to improve Handoff.

GAUP Update (FID 12078.3)

GAUP is used to update certain attributes for different Protocols and Applications, such
as the Enhanced RTC MAC Layer protocols (subtypes 1, 2 and 3), the Multi-Flow
Packet Application, 3G-1X Circuit Services Notification Application, the
SessionConfigurationToken attribute in the Default Session Configuration Protocol, etc.
GAUP improves the operation of delay sensitive applications, such Video Streaming
and Gaming. Lower latency and reduced call drop rates requirements can be achieved
by dynamically updating multiple flow per user attributes (for instance, GAUP is
useful in Inter and Intra RNC handoff, as well as in QoS-based scheduling). GAUP
supports only Rev. A RNC.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

7-10

EVolution Data Optimized (1xEV-DO) Basic Revision A


(Rev. A) Feature Bundle

Feature description: Basic Rev. A Feature Bundle

GAUP does not support Rel 0 RNC. GAUP is transparent to BTS, and will support
either on Rel 0 or Rev. A BTSs.
Service Providers need this functionality for example, in handoff operation of Rev. A
mobiles from Rel 0 into Rev. A infrastructure and vice-versa. In such cases, GAUP
provides a mechanism for seamless Inter-Personality handoff, when a personality
(configuration) boundary is reached.
Performance improvements brought by GAUP implementation in Rev. A are classified
as improved user experience since faster adjustments between active applications are
possible. In VoIP, GAUP is key to reduce the call drop rate since it allows switching a
Session Configuration (personality) when PHY/MAC boundaries are reached, for
example for Inter-RNC handoff (Rel 0 RNC to Rev. A RNC, or vice-versa).
Implementing GAUP allows support of Subtype 1 RTC MAC protocol which is simply
the Default Rel 0 RTC MAC, but with Rate Transition Vectors that are GAUP-able
dynamically and within a session without dropping the connection. The rate transition
vectors in the Rate Transition Matrix (RTM) are used to determine the AT reverse rate
based on the Reverse Activity Bit (RAB) broadcast by the system.
HRPD Rev. A Support on Modular Cell 1-3 BTS Platforms using SB-EVMm (FID 12078.4)

All Modular Cell 1-3 BTSs currently offer packet data services over HRPD based on
Rel 0. With this feature HRPD Rev. A air-interface will be supported on these products
with software generic upgrades including but not limited to:

Use the HRPD Rev. A modem cards (SB-EVMm) introduced in Feature 12078.27
with the new application and OA&M software to support the new Rev. A air
interface.
Use of the new application software introduced in 12078.2 and 12078.7 to support
Rev. A
Support of faster Received Signal Strength Indication (RSSI) measurements as
specified in FID 12204.0. With the introduction of higher data rate in the RL for
Rev. A air-interface, there is a need to provide better, more accurate and faster
system measurements. RSSI indicates the reverse link total received power at the
base station and is directly related to RL loading. So for better and more accurate
estimate of the RL loading a faster RSSI is needed. It should be mentioned that the
Classic CBR does not have the resources to implement the new Fast RSSI
algorithm, therefore only SBCBR will be supported for Rev. A in Modular Cell 1-3.

Modular Cell 1-3 will have Feature parity (including OA&M and SM features) with
existing Rel. 0 Modular Cell 1-3 features. In a Modular Cell 1-3: there is one
SB-EVMm per CDMA Digital Module (CDM) which can support three sector-carriers.
The Modular Cell 1-3 BTS products will support up to 3 carriers (a carrier refers to
1C-3S), one per CDM (Modular Cell 1-3 can be equipped with up to 3 CDMs).

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
7-11
Issue 5, May 2008
See notice on first page

EVolution Data Optimized (1xEV-DO) Basic Revision A


(Rev. A) Feature Bundle

Feature description: Basic Rev. A Feature Bundle

The Modular Cell 1-3 BTS products will support multi-carriers (up to three carriers)
with HRPD Rev. A, HRPD Rel 0 and 3G-1X carriers can co-exist in the same BTS but
using:

Different modem cards:


Existing EVM for Rel. 0.
SB-EVMm for Rev. A etc.
Separate controllers
One URCm per three sector-carriers.
Separate radios
One radio per sector-carrier.

All frequency bands for Modular Cell 1-3 supported in features 8219.x will be
supported for Rev. A:

850 MHz
1900 MHz
450 MHz (only for Modular Cell 2-3)

HRPD Rev. A Support on Modular Cell 4.0 BTS Platforms using SB-EVM (FID 12078.5)

All Modular Cell 4.0 products currently offer packet data services over HRPD based
on Rel 0. With this feature HRPD Rev. A air-interface will be supported on these
products with software generic upgrades including but not limited to:

Use the HRPD Rev. A modem cards (SB-EVM) introduced in Feature 12078.17
with the new application and OA&M software to support the new Rev. A air
interface
Use the new application software introduced in FID 12078.2 and 12078.7 to
support Rev. A
Support of faster RSSI measurements as specified in FID 12204.0. With the
introduction of higher data rate in the RL for Rev. A air-interface, there is a need to
provide better, more accurate and faster system measurements. RSSI indicates the
reverse link total received power at the base station and is directly related to RL
loading. So for better and more accurate estimate of the RL loading a faster RSSI
is needed. All Modular Cell 4.0 radios are able to support the fast RSSI
measurement, that includes UCR and MCR.

Modular Cell 4.0 will have Feature parity (including OA&M and SM features) with
existing Rel. 0 Modular Cell 4.0 features.
Modular Cell 4.0 HRPD Rev. A will support up to three SB-EVM cards with each
SB-EVM serves three sector-carriers.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

7-12

EVolution Data Optimized (1xEV-DO) Basic Revision A


(Rev. A) Feature Bundle

Feature description: Basic Rev. A Feature Bundle

The Modular Cell 4.0 BTS products will support the multi-carriers feature (FID
8219.x, FID 9043.0 and FID 8973.1) with HRPD Rev. A, HRPD Rel 0 and 3G-1X
carriers can co-exist in the same BTS using:

Different modem cards:


Existing EVM for Rel. 0
SB-EVM for Rev. A etc.
Can share same radio (if FID 8219.x & FID 9043.0 are supported)
Use different controllers

All frequency bands for Modular Cell 4.0 supported in features 8219.x will be
supported for Rev. A:

850 MHz
1900 MHz
1800 MHz (Korea PCS: Modular Cell 4.0 and Compact 4.0)
450 MHz (Compact 4.0)
2100 MHz (Compact 4.0 B)

Inter and Intra-RNC Handoff Enhancement (FID 12078.7)

This feature supports both Rel 0 systems and in mixed Rel 0/Rev. A systems:

Every type of handoff that is currently supported in a Rel 0 system (soft/softer on


traffic channel; hard handoff across carriers on traffic channel; inter-RNC dormant
session handoff)
Handoffs from Rev-A PHY/MAC connections to Rel 0 PHY/MAC connections.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
7-13
Issue 5, May 2008
See notice on first page

EVolution Data Optimized (1xEV-DO) Basic Revision A


(Rev. A) Feature Bundle

Feature
interactions
...................................................................................................................................................................................................................................
General feature dependencies of 1xEV-DO Rev. A Features

All the 1xEV-DO Rev. A features that impact the base station, result in new
requirements for the following features:

HDR Reverse Link Overload Control Feature (FID 8048.0)


Cell Processor Overload Control Feature (FID 10519.0)

All the Rev. A features that impact the RNC, result in new requirements for the
following features:

TP Overload Control and AP Overload Control Features (FID 10519.1)

Enhanced Reverse and Forward Links using Enhanced MAC Protocols with Rev. A Subtype 2
Physical Layer (FID 12078.2)

FID 12078.2 has no interactions with other features.


GAUP Update (FID 12078.3)

The GAUP implementation on the AN has no dependency on other FIDs; however,


GAUP operation requires GAUP implementation on the AT.
HRPD Rev. A Support on Modular Cell 1-3 BTS Platforms using SB-EVMm (FID 12078.4

FID 12078.4 interacts with the following features:

Rev. A modem card SB-EVMm (FID 12078.17 and FID 10861.0)


SBCBR with the Fast RSSI measurement capability (FID 12204.0)
Modular Cell 1-3 radio controller, URCm (FIDs 8212.x)

HRPD Rev. A Support on Modular Cell 4.0 BTS Platforms using SB-EVM (FID 12078.5)

FID 12078.5 interacts with the following features:

Rev. A modem card SB-EVM (FID 12078.17 and FID 10861.0)


Modular Cell 4.0 radio cards (UCR or MCR) with the Fast RSSI measurement
capability (FID 12204.0 )
Modular Cell 4.0 radio controller, URC and URC-II
Depends on the support of multi-carriers feature specified in FID 8219.1 for the
support of multi-carriers in the controllers and radios

Inter and Intra-RNC Handoff Enhancement (FID 12078.7)

This feature is dependent on all features in the Rev. A Basic package. In addition, this
feature depends on 8219.1 feature which supports handoffs across multiple carriers in a
BTS.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

7-14

EVolution Data Optimized (1xEV-DO) Basic Revision A


(Rev. A) Feature Bundle

Impacts
on service measurements
...................................................................................................................................................................................................................................
Introduction

The 1xEV-DO Rev. A features affect the following categories of services


measurements:
Protocols with Rev. A Physical Layer (12078.2)

The following service measurements are supported:

DRC Rate Request (per rate)/DRC measure count


Physical Layer ACK/NAK (Early termination Gain per DRC rate)
Slot usage for Sub-Synchronous, Synchronous and Asynchronous Control Channel

The Protocols with Rev. A Physical Layer feature affects the Executive Cellular
Processor (ECP) service measurements that are identified in Table 7-1, Protocols with
Rev. A Physical Layer Feature: New and Modified Service Measurements (p. 7-15)
Table 7-1

Protocols with Rev. A Physical Layer Feature: New and Modified


Service Measurements

Service
measurement
subcategory

Count abbreviation

Count name

SECT-CARRHCS

EVM_DRC_ERASURE

DRC rate requests


erased

SECT-CARRHCS

EVM_DRC_RATE_0

DRC Rate Requests for


0kbps

SECT-CARRHCS

EVM_DRC_RATE_1228_8

DRC Rate Request for


1228.8 kbps

SECT-CARRHCS

EVM_DRC_RATE_1228_8_L

DRC Rate Request for


1228.8 kbps Long
Format

SECT-CARRHCS

EVM_DRC_RATE_1536

DRC Rate Requests for


1536kbps

SECT-CARRHCS

EVM_DRC_RATE_153_6

DRC rate request for


153.6 kbps

SECT-CARRHCS

EVM_DRC_RATE_1843_2

DRC Rate Request for


1843.2 kbps

SECT-CARRHCS

EVM_DRC_RATE_2457_6

DRC Rate Request for


2457.6 kbps

SECT-CARRHCS

EVM_DRC_RATE_3072

DRC Rate Requests for


3072kbps

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
7-15
Issue 5, May 2008
See notice on first page

EVolution Data Optimized (1xEV-DO) Basic Revision A


(Rev. A) Feature Bundle

Table 7-1

Impacts on service measurements

Protocols with Rev. A Physical Layer Feature: New and Modified


Service Measurements (continued)

Service
measurement
subcategory

Count abbreviation

Count name

SECT-CARRHCS

EVM_DRC_RATE_307_2

DRC rate request for


307.2 kbps

SECT-CARRHCS

EVM_DRC_RATE_307_2_L

DRC Rate Request for


307.2 kbps Long Format

SECT-CARRHCS

EVM_DRC_RATE_38_4

DRC Rate Requests for


38.4kbps

SECT-CARRHCS

EVM_DRC_RATE_614_4

DRC Rate Request for


614.4 kbps

SECT-CARRHCS

EVM_DRC_RATE_614_4_L

DRC Rate Request for


614.4 kbps Long Format

SECT-CARRHCS

EVM_DRC_RATE_76_8

DRC rate request for


76.8 kbps

SECT-CARRHCS

EVM_DRC_RATE_921_6

DRC Rate Request for


921.6 kbps

SECT-CARRHCS

EVM_FTC_NUM_SLOT_1228_8

Number of Slots Used to


Transmit Physical Layer
Data at 1228.8 kbps on
Forward Traffic Channel

SECT-CARRHCS

EVM_FTC_NUM_SLOT_1536

Number of Slots Used to


Transmit Physical Layer
Data at 1536 kbps on
Forward Traffic Channel

SECT-CARRHCS

EVM_FTC_NUM_SLOT_153_6

Number of Slots Used to


Transmit Physical Layer
Data at 153.6 kbps on
Forward Traffic Channel

SECT-CARRHCS

EVM_FTC_NUM_SLOT_1843_2

Number of Slots Used to


Transmit Physical Layer
Data at 1843.2 kbps on
Forward Traffic Channel

SECT-CARRHCS

EVM_FTC_NUM_SLOT_19_2

Number of Slots Used to


Transmit Physical Layer
Data at 19.2 kbps on
Forward Traffic Channel

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

7-16

EVolution Data Optimized (1xEV-DO) Basic Revision A


(Rev. A) Feature Bundle

Table 7-1

Impacts on service measurements

Protocols with Rev. A Physical Layer Feature: New and Modified


Service Measurements (continued)

Service
measurement
subcategory

Count abbreviation

Count name

SECT-CARRHCS

EVM_FTC_NUM_SLOT_2457_6

Number of Slots Used to


Transmit Physical Layer
Data at 2457.6 kbps on
Forward Traffic Channel

SECT-CARRHCS

EVM_FTC_NUM_SLOT_3072

Number of Slots Used to


Transmit Physical Layer
Data at 3072 kbps on
Forward Traffic Channel

SECT-CARRHCS

EVM_FTC_NUM_SLOT_307_2

Number of Slots Used to


Transmit Physical Layer
Data at 307.2 kbps on
Forward Traffic Channel

SECT-CARRHCS

EVM_FTC_NUM_SLOT_38_4

Number of Slots Used to


Transmit Physical Layer
Data at 38.4 kbps on
Forward Traffic Channel

SECT-CARRHCS

EVM_FTC_NUM_SLOT_4_8

Number of Slots Used to


Transmit Physical Layer
Data at 4.8 kbps on
Forward Traffic Channel

SECT-CARRHCS

EVM_FTC_NUM_SLOT_614_4

Number of Slots Used to


Transmit Physical Layer
Data at 614.4 kbps on
Forward Traffic Channel

SECT-CARRHCS

EVM_FTC_NUM_SLOT_76_8

Number of Slots Used to


Transmit Physical Layer
Data at 76.8 kbps on
Forward Traffic Channel

SECT-CARRHCS

EVM_FTC_NUM_SLOT_921_6

Number of Slots Used to


Transmit Physical Layer
Data at 921.6 kbps on
Forward Traffic Channel

SECT-CARRHCS

EVM_FTC_NUM_SLOT_9_6

Number of Slots Used to


Transmit Physical Layer
Data at 9.6 kbps on
Forward Traffic Channel

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
7-17
Issue 5, May 2008
See notice on first page

EVolution Data Optimized (1xEV-DO) Basic Revision A


(Rev. A) Feature Bundle

Table 7-1

Impacts on service measurements

Protocols with Rev. A Physical Layer Feature: New and Modified


Service Measurements (continued)

Service
measurement
subcategory

Count abbreviation

Count name

SECT-CARRHCS

EVM_FTC_TOT_BYTES_1228_8

Total Physical Layer


Bytes Transmitted on
Forward Traffic
Channels at 1228.8 kbps

SECT-CARRHCS

EVM_FTC_TOT_BYTES_1536

Total Physical Layer


Bytes Transmitted on
Forward Traffic
Channels at 1536 kbps

SECT-CARRHCS

EVM_FTC_TOT_BYTES_153_6

Total Physical Layer


Bytes Transmitted on
Forward Traffic
Channels at 153.6 kbps

SECT-CARRHCS

EVM_FTC_TOT_BYTES_1843_2

Total Physical Layer


Bytes Transmitted on
Forward Traffic
Channels at 1843.2 kbps

SECT-CARRHCS

EVM_FTC_TOT_BYTES_19_2

Total Physical Layer


Bytes Transmitted on
Forward Traffic
Channels at 19.2 kbps

SECT-CARRHCS

EVM_FTC_TOT_BYTES_2457_6

Total Physical Layer


Bytes Transmitted on
Forward Traffic
Channels at 2457.6 kbps

SECT-CARRHCS

EVM_FTC_TOT_BYTES_3072

Total Physical Layer


Bytes Transmitted on
Forward Traffic
Channels at 3072 kbps

SECT-CARRHCS

EVM_FTC_TOT_BYTES_307_2

Total Physical Layer


Bytes Transmitted on
Forward Traffic
Channels at 307.2 kbps

SECT-CARRHCS

EVM_FTC_TOT_BYTES_38_4

Total Physical Layer


Bytes Transmitted on
Forward Traffic
Channels at 38.4 kbps

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

7-18

EVolution Data Optimized (1xEV-DO) Basic Revision A


(Rev. A) Feature Bundle

Table 7-1

Impacts on service measurements

Protocols with Rev. A Physical Layer Feature: New and Modified


Service Measurements (continued)

Service
measurement
subcategory

Count abbreviation

Count name

SECT-CARRHCS

EVM_FTC_TOT_BYTES_4_8

Total Physical Layer


Bytes Transmitted on
Forward Traffic
Channels at 4.8 kbps

SECT-CARRHCS

EVM_FTC_TOT_BYTES_614_4

Total Physical Layer


Bytes Transmitted on
Forward Traffic
Channels at 614.4 kbps

SECT-CARRHCS

EVM_FTC_TOT_BYTES_76_8

Total Physical Layer


Bytes Transmitted on
Forward Traffic
Channels at 76.8 kbps

SECT-CARRHCS

EVM_FTC_TOT_BYTES_921_6

Total Physical Layer


Bytes Transmitted on
Forward Traffic
Channels at 921.6 kbps

SECT-CARRHCS

EVM_FTC_TOT_BYTES_9_6

Total Physical Layer


Bytes Transmitted on
Forward Traffic
Channels at 9.6 kbps

SECT-CARRHCS

EVM_CALL_MUTE_STATE_NUM

Number of Times in
Call Mute State

SECT-CARRHCS

EVM_CALL_MUTE_STATE_PEAK_
DUR

Peak Duration in Call


Mute State

SECT-CARRHCS

EVM_CALL_MUTE_STATE_TOT_
DUR

Total Duration in Call


Mute State

SECT-CARRHCS

EVM_CONN_BLOCK_STATE_NUM

Number of Times in
Connection Block State

SECT-CARRHCS

EVM_CONN_BLOCK_STATE_PEAK_
DUR

Peak Duration in
Connection Block State

SECT-CARRHCS

EVM_CONN_BLOCK_STATE_TOT_
DUR

Total Duration in
Connection Block State

SECT-CARRHCS

EVM_FWD_PACKETS_1228_8_L_TOTAL_
Tot pkts trans fwrd traf
COUNT
chan 1228.8 kbps-long
formt

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
7-19
Issue 5, May 2008
See notice on first page

EVolution Data Optimized (1xEV-DO) Basic Revision A


(Rev. A) Feature Bundle

Table 7-1

Impacts on service measurements

Protocols with Rev. A Physical Layer Feature: New and Modified


Service Measurements (continued)

Service
measurement
subcategory

Count abbreviation

Count name

SECT-CARRHCS

EVM_FWD_PACKETS_1228_8_TOTAL_ Tot pkts trans fwrd traf


COUNT
chan 1228.8 kbps

SECT-CARRHCS

EVM_FWD_PACKETS_153_6_TOTAL_
COUNT

SECT-CARRHCS

EVM_FWD_PACKETS_1843_2_TOTAL_ Tot pkts trans fwrd traf


COUNT
chan 1843.2 kbps

SECT-CARRHCS

EVM_FWD_PACKETS_2457_6_TOTAL_ Tot pkts trans fwrd traf


COUNT
chan 2457.6 kbps

SECT-CARRHCS

EVM_FWD_PACKETS_307_2_L_TOTAL_Tot pkts trans fwrd traf


COUNT
chan 307.2 kbps-long
formt

SECT-CARRHCS

EVM_FWD_PACKETS_307_2_TOTAL_
COUNT

Tot pkts trans fwrd traf


chan 307.2 kbps

SECT-CARRHCS

EVM_FWD_PACKETS_38_4_TOTAL_
COUNT

Tot pkts trans fwrd traf


chan 38.4 kbps

SECT-CARRHCS

EVM_FWD_PACKETS_614_4_L_TOTAL_Tot pkts trans fwrd traf


COUNT
chan 614.4 kbps-long
formt

SECT-CARRHCS

EVM_FWD_PACKETS_614_4_TOTAL_
COUNT

Tot pkts trans fwrd traf


chan 614.4 kbps

SECT-CARRHCS

EVM_FWD_PACKETS_76_8_TOTAL_
COUNT

Tot pkts trans fwrd traf


chan 76.8 kbps

SECT-CARRHCS

EVM_FWD_PACKETS_921_6_TOTAL_
COUNT

Tot pkts trans fwrd traf


chan 921.6 kbps

SECT-CARRHCS

SM_LT_NOISE_FLOOR_EST

Long Term Noise Floor


Estimation

SECT-CARRHCS

SM_SILENCE_INT_NOISE_FLOOR_
EST

Silence Interval Noise


Floor Estimation

SECT-CARRHDRC

AN_INIT_CONN_ATMPT_FAIL_OTHER_ AN-Initiated Connection


PRETCA
Attempt Failures - Other
Reasons Pre TCA

Tot pkts trans fwrd traf


chan 153.6 kbps

(Modified)

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

7-20

EVolution Data Optimized (1xEV-DO) Basic Revision A


(Rev. A) Feature Bundle

Table 7-1

Impacts on service measurements

Protocols with Rev. A Physical Layer Feature: New and Modified


Service Measurements (continued)

Service
measurement
subcategory

Count abbreviation

Count name

SECT-CARRHDRC

AT_INIT_CONN_ATMPT_FAIL_OTHER_ AT-Initiated Connection


PRETCA
Attempt Failures - Other
Reasons Pre TCA
(Modified)

SECT-CARRHDRC

AVG_ACTIVE_CONN_PER_SECTOR_
Rev. A

Average Active Rev A


Connections per
sector-carrier

SECT-CARRHDRC

NUM_CONN_BLOCKED

Number of Connections
Blocked

SECT-CARRHDRC

NUM_SUBPKTS_RL_1024

Number of subpackets
received on reverse
traffic channels for
physical packet size of
1024 bits

SECT-CARRHDRC

NUM_SUBPKTS_RL_12288

Number of subpackets
received on reverse
traffic channels for
physical packet size of
12288 bits

SECT-CARRHDRC

NUM_SUBPKTS_RL_128

Number of subpackets
received on reverse
traffic channels for
physical packet size of
128 bits

SECT-CARRHDRC

NUM_SUBPKTS_RL_1536

Number of subpackets
received on reverse
traffic channels for
physical packet size of
1536 bits

SECT-CARRHDRC

NUM_SUBPKTS_RL_2048

Number of subpackets
received on reverse
traffic channels for
physical packet size of
2048 bits

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
7-21
Issue 5, May 2008
See notice on first page

EVolution Data Optimized (1xEV-DO) Basic Revision A


(Rev. A) Feature Bundle

Table 7-1

Impacts on service measurements

Protocols with Rev. A Physical Layer Feature: New and Modified


Service Measurements (continued)

Service
measurement
subcategory

Count abbreviation

Count name

SECT-CARRHDRC

NUM_SUBPKTS_RL_256

Number of subpackets
received on reverse
traffic channels for
physical packet size of
256 bits

SECT-CARRHDRC

NUM_SUBPKTS_RL_3072

Number of subpackets
received on reverse
traffic channels for
physical packet size of
3072 bits

SECT-CARRHDRC

NUM_SUBPKTS_RL_4096

Number of subpackets
received on reverse
traffic channels for
physical packet size of
4096 bits

SECT-CARRHDRC

NUM_SUBPKTS_RL_512

Number of subpackets
received on reverse
traffic channels for
physical packet size of
512 bits

SECT-CARRHDRC

NUM_SUBPKTS_RL_6144

Number of subpackets
received on reverse
traffic channel for
physical packet size of
6144 bits

SECT-CARRHDRC

NUM_SUBPKTS_RL_768

Number of subpackets
received on reverse
traffic channels for
physical packet size of
768 bits

SECT-CARRHDRC

NUM_SUBPKTS_RL_8192

Number of subpackets
received on reverse
traffic channels for
physical packet size of
8192 bits

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

7-22

EVolution Data Optimized (1xEV-DO) Basic Revision A


(Rev. A) Feature Bundle

Table 7-1

Impacts on service measurements

Protocols with Rev. A Physical Layer Feature: New and Modified


Service Measurements (continued)

Service
measurement
subcategory

Count abbreviation

Count name

SECT-CARRHDRC

PEAK_ACTIVE_CONN_PER_SECTOR_ Peak Active Rev A


Rev. A
Connections per sector

SECT-CARRHDRC

REVERSE_FRAME_ERROR_COUNT

1xEV Frames in Error


on RTC
(Modified)

SECT-CARRHDRC

REV_LINK_FRAME_ERROR_COUNT_
153_6_KBPS

Reverse link frame error


count-153.6
(Modified)

SECT-CARRHDRC

REV_LINK_FRAME_ERROR_COUNT_
19_2_KBPS

Reverse link frame error


count-19.2
(Modified)

SECT-CARRHDRC

REV_LINK_FRAME_ERROR_COUNT_
38_4_KBPS

Reverse link frame error


count-38.4
(Modified)

SECT-CARRHDRC

REV_LINK_FRAME_ERROR_COUNT_
76_8_KBPS

Reverse link frame error


count-76.8
(Modified)

SECT-CARRHDRC

REV_LINK_FRAME_ERROR_COUNT_
9_6_KBPS

Reverse link frame error


count-9.6
(Modified)

SECT-CARRHDRC

REV_OL_PC_TOTAL_SETPOINT_1024

Total setpoint for


reverse outer loop power
control for 1024 bit
packets

SECT-CARRHDRC

REV_OL_PC_TOTAL_SETPOINT_
12288

Total setpoint for


reverse outer loop power
control for 12288 bit
packets

SECT-CARRHDRC

REV_OL_PC_TOTAL_SETPOINT_128

Total setpoint for


reverse outer loop power
control for 128 bit
packets

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
7-23
Issue 5, May 2008
See notice on first page

EVolution Data Optimized (1xEV-DO) Basic Revision A


(Rev. A) Feature Bundle

Table 7-1

Impacts on service measurements

Protocols with Rev. A Physical Layer Feature: New and Modified


Service Measurements (continued)

Service
measurement
subcategory

Count abbreviation

Count name

SECT-CARRHDRC

REV_OL_PC_TOTAL_SETPOINT_1536

Total setpoint for


reverse outer loop power
control for 1536 bit
packets

SECT-CARRHDRC

REV_OL_PC_TOTAL_SETPOINT_2048

Total setpoint for


reverse outer loop power
control for 2048 bit
packets

SECT-CARRHDRC

REV_OL_PC_TOTAL_SETPOINT_256

Total setpoint for


reverse outer loop power
control for 256 bit
packets

SECT-CARRHDRC

REV_OL_PC_TOTAL_SETPOINT_3072

Total setpoint for


reverse outer loop power
control for 3072 bit
packets

SECT-CARRHDRC

REV_OL_PC_TOTAL_SETPOINT_4096

Total setpoint for


reverse outer loop power
control for 4096 bit
packets

SECT-CARRHDRC

REV_OL_PC_TOTAL_SETPOINT_512

Total setpoint for


reverse outer loop power
control for 512 bit
packets

SECT-CARRHDRC

REV_OL_PC_TOTAL_SETPOINT_6144

Total setpoint for


reverse outer loop power
control for 6144 bit
packets

SECT-CARRHDRC

REV_OL_PC_TOTAL_SETPOINT_768

Total setpoint for


reverse outer loop power
control for 768 bit
packets

SECT-CARRHDRC

REV_OL_PC_TOTAL_SETPOINT_8192

Total setpoint for


reverse outer loop power
control for 8192 bit
packets

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

7-24

EVolution Data Optimized (1xEV-DO) Basic Revision A


(Rev. A) Feature Bundle

Table 7-1

Impacts on service measurements

Protocols with Rev. A Physical Layer Feature: New and Modified


Service Measurements (continued)

Service
measurement
subcategory

Count abbreviation

Count name

SECT-CARRHDRC

REV_OUTER_LOOP_PC_FRAME_COUNT_
1xEV Reverse Outer
0KBPS
Loop Pwr Cntrl Frm Cnt
- 0 kbps
(Modified)

SECT-CARRHDRC

REV_OUTER_LOOP_PC_FRAME_COUNT_
1xEV Reverse Outer
1536KBPS
Loop Pwr Cntrl Frm Cnt
- 153.6 kbps
(Modified)

SECT-CARRHDRC

REV_OUTER_LOOP_PC_FRAME_COUNT_
1xEV Reverse Outer
192KBPS
Loop Pwr Cntrl Frm Cnt
- 19.2 kbps
(Modified)

SECT-CARRHDRC

REV_OUTER_LOOP_PC_FRAME_COUNT_
1xEV Reverse Outer
384KBPS
Loop Pwr Cntrl Frm Cnt
- 38.4 kbps
(Modified)

SECT-CARRHDRC

REV_OUTER_LOOP_PC_FRAME_COUNT_
1xEV Reverse Outer
768KBPS
Loop Pwr Cntrl Frm Cnt
- 76.8 kbps
(Modified)

SECT-CARRHDRC

REV_OUTER_LOOP_PC_FRAME_COUNT_
1xEV Reverse Outer
96KBPS
Loop Pwr Cntrl Frm Cnt
- 9.6 kbps
(Modified)

SECT-CARRHDRC

REV_OUTER_LOOP_PC_TOTAL_OUTPUT_
1xEV Reverse Outer
0KBPS
Loop Pwr Cntrl Tot Out
- 0 kbps
(Modified)

SECT-CARRHDRC

REV_OUTER_LOOP_PC_TOTAL_OUTPUT_
1xEV Reverse Outer
1536KBPS
Loop Pwr Cntrl Tot Out
- 153.6 kbps
(Modified)

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
7-25
Issue 5, May 2008
See notice on first page

EVolution Data Optimized (1xEV-DO) Basic Revision A


(Rev. A) Feature Bundle

Table 7-1

Impacts on service measurements

Protocols with Rev. A Physical Layer Feature: New and Modified


Service Measurements (continued)

Service
measurement
subcategory

Count abbreviation

Count name

SECT-CARRHDRC

REV_OUTER_LOOP_PC_TOTAL_OUTPUT_
1xEV Reverse Outer
192KBPS
Loop Pwr Cntrl Tot Out
- 19.2 kbps
(Modified)

SECT-CARRHDRC

REV_OUTER_LOOP_PC_TOTAL_OUTPUT_
1xEV Reverse Outer
384KBPS
Loop Pwr Cntrl Tot Out
- 38.4 kbps
(Modified)

SECT-CARRHDRC

REV_OUTER_LOOP_PC_TOTAL_OUTPUT_
1xEV Reverse Outer
768KBPS
Loop Pwr Cntrl Tot Out
- 76.8 kbps
(Modified)

SECT-CARRHDRC

REV_OUTER_LOOP_PC_TOTAL_OUTPUT_
1xEV Reverse Outer
96KBPS
Loop Pwr Cntrl Tot Out
- 9.6 kbps
(Modified)

SECT-CARRHDRC

REV_PACKETS_1024_TOTAL_COUNT

Total physical packets


received on reverse
traffic channels for
packet size of 1024 bits

SECT-CARRHDRC

REV_PACKETS_12288_TOTAL_
COUNT

Total physical packets


Received on reverse
traffic channels for
packet size of 12288
bits

SECT-CARRHDRC

REV_PACKETS_128_TOTAL_COUNT

Total physical packets


received on reverse
traffic channels for
packet size of 128 bits

SECT-CARRHDRC

REV_PACKETS_1536_TOTAL_COUNT

Total physical packets


received on reverse
traffic channels for
packet size of 1536 bits

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

7-26

EVolution Data Optimized (1xEV-DO) Basic Revision A


(Rev. A) Feature Bundle

Table 7-1

Impacts on service measurements

Protocols with Rev. A Physical Layer Feature: New and Modified


Service Measurements (continued)

Service
measurement
subcategory

Count abbreviation

Count name

SECT-CARRHDRC

REV_PACKETS_2048_TOTAL_COUNT

Total physical packets


received on reverse
traffic channels for
packet size of 2048 bits

SECT-CARRHDRC

REV_PACKETS_256_TOTAL_COUNT

Total physical packets


received on reverse
traffic channels for
packet size of 256 bits

SECT-CARRHDRC

REV_PACKETS_3072_TOTAL_COUNT

Total physical packets


received on reverse
traffic channels for
packet size of 3072 bits

SECT-CARRHDRC

REV_PACKETS_4096_TOTAL_COUNT

Total physical packets


received on reverse
traffic channels for
packet size of 4096 bits

SECT-CARRHDRC

REV_PACKETS_512_TOTAL_COUNT

Total physical packets


received on reverse
traffic channels for
packet size of 512 bits

SECT-CARRHDRC

REV_PACKETS_6144_TOTAL_COUNT

Total physical packets


received on reverse
traffic channels for
packet size of 6144 bits

SECT-CARRHDRC

REV_PACKETS_768_TOTAL_COUNT

Total physical packets


received on reverse
traffic channels for
packet size of 768 bits

SECT-CARRHDRC

REV_PACKETS_8192_TOTAL_COUNT

Total physical packets


received on reverse
traffic channels for
packet size of 8192 bits

SECT-CARRHDRC

TOTAL_REVERSE_FRAME_COUNT

1xEV Total Reverse


Link Frames

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
7-27
Issue 5, May 2008
See notice on first page

EVolution Data Optimized (1xEV-DO) Basic Revision A


(Rev. A) Feature Bundle

Impacts on service measurements

Inter and Intra-Radio Network Controller (RNC) Handoff Enhancement (FID


12078.7)

These new service measurements are related to Personality Switches introduced in Rev
A by FID 12078.7.
The Inter and Intra-Radio Network Controller (RNC) Handoff Enhancement feature
affects the Executive Cellular Processor (ECP) service measurements that are identified
in Table 7-2, Inter and Intra-Radio Network Controller (RNC) Handoff Enhancement
Feature: New Service Measurements (p. 7-28)
Table 7-2

Inter and Intra-Radio Network Controller (RNC) Handoff


Enhancement Feature: New Service Measurements

Service measurement
subcategory

Count abbreviation

Count name

AP

NUM_AT_REL0_SESS_
ESTABLISHED

Number of ATs with Rel 0


as the highest personality
negotiated

AP

NUM_AT_Rev.
A_SESS_ESTABLISHED

Number of ATs with Rev


A/DPA as the highest
personality negotiated

SECT-CARR-HDRC

AHO_PERS_SWTCH_Rev.
A_TO_REL0

Number of Personality
Switches During Active
Connections from Rev
A/DPA to Rel 0

SECT-CARR-HDRC

CONN_SETUP_PERS_
SWTCH_REL0_TO_Rev. A

Number of Personality
Switches During
Connection Setup From Rel
0 to Rev A/DPA

SECT-CARR-HDRC

CONN_SETUP_PERS_
SWTCH_Rev. A_TO_REL0

Number of Personality
Switches During
Connection Setup From
Rev A/DPA to Rel 0

SECT-CARR-HDRC

CONN_SETUP_PERS_
SWTCH_UNKNOWN_TO_
REL0

Number of Personality
Switches During
Connection Setup From
Unknown to Rel 0

SECT-CARR-HDRC

CONN_SETUP_PERS_
SWTCH_UNKNOWN_TO_
Rev. A

Number of Personality
Switches During
Connection Setup From
Unknown to Rev A/DPA

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

7-28

EVolution Data Optimized (1xEV-DO) Basic Revision A


(Rev. A) Feature Bundle

Impacts on service measurements

Reference

For detailed information about 1xEV-DO service measurements, see 401-614-326,


Flexent Wireless Networks 1xEV-DO Service Measurements

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
7-29
Issue 5, May 2008
See notice on first page

EVolution Data Optimized (1xEV-DO) Basic Revision A


(Rev. A) Feature Bundle

Implementing
the features
...................................................................................................................................................................................................................................
Process

The 1xEV-DO Basic Rev. A Feature Bundle are activated via a software licensing key
mechanism instead of the usual FAF/QFAF mechanism.
The license key is used for the activation of the 1xEV-DO Basic Rev. A Feature
Bundle for one or more Rev. A-capable BTS-Carrier served by the RNC. The Rev. A
software licensing key is installed via the EMS.
The Rev. A software license key is used to:

enable one or more BTS-Carriers to support features included in the Basic Rev. A
Feature Bundle served by the RNC, and
allow RNC application to set up Rev. A connections from a Basic Rev. A Feature
Bundle enabled. The Rev. A Release RNC base software will support parts of the
Mandatory Rev. A operation which do not depend on the enhanced physical layer
(without control of the license key). That includes multiple personalities negotiation
and changing the personality in the AT by GAUP, and communicating those
personalities on A13. All Rev-A operations which require the enhanced physical
layer under control of the Rev. A license key.

The Enhanced Rev. A Feature bundle is an optional bundle controlled by FAF on a per
service node basis. The activation of the enhanced Rev. A Feature bundle depends on
the Basic Rev. A Feature bundle, this means the Basic Rev. A Feature bundle needs to
be activated before the activation of the Enhanced Rev. A Feature bundle. In other
words, the Enhanced Rev. A Feature Bundle depends on the Rev. A Basic Feature
Bundle.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

7-30

EVolution Data Optimized (1xEV-DO) Basic Revision A


(Rev. A) Feature Bundle

Activating
the feature
...................................................................................................................................................................................................................................
Purpose

This procedure activates the 1xEV-DO Basic Rev. A Feature Bundle in a Flexent
wireless network.
The following scenario explains at high level the activation process of the 1xEV-DO
Basic Rev. A Feature Bundle Bundle using the license key.
For more detailed procedure, see 401-614-101, Flexent Wireless Networks
CDMA2000 1xEV-DO Radio Access System.
Procedure
...................................................................................................................................................................................................

Service provider logs into the lead AP and obtains the host ID of the first AP.
...................................................................................................................................................................................................

Service provider calls Technical Support who provides AP Host ID and the desired
number of licenses, and asks for Rev. A software license key to be generated.
...................................................................................................................................................................................................

Technical Support generates a Rev. A software license key and sends the software
license key to the service provider.
...................................................................................................................................................................................................

Service provider installs the Rev. A Software Licensing Key. Service provider enters
the software license key information on the EMS.
...................................................................................................................................................................................................

EMS sends the license key information to the RNC. The RNC validates the license
key.
...................................................................................................................................................................................................

Service provider inputs the BTS-Carrier to be activated from the EMS. The EMS sends
the information to the RNC. The RNC checks whether or not there are unused licenses.
If so, assigns one license to the BTS-carrier Rev. A capable (SB-EVM/SB-EVMm), the
BTS updates the configuration for that BTS-carrier.
If the BTS-carrier is Rev. A capable (SB-EVM/SB-EVMm), the BTS updates the
configuration for that BTS-carrier.
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
7-31
Issue 5, May 2008
See notice on first page

8 nhanced Data Only Revision A


E
(DOrA) Application Quality of
Service (QoS) Features

Overview
...................................................................................................................................................................................................................................
Purpose

This optional feature description describes the following Enhanced Data Only Revision
A (DOrA) Application Quality of Service (QoS) Features in the CDMA2000
EVolution Data Optimized (1xEV-DO) Network. This group of features are identified
as the DOrA Application QoS Features and use DOrA Application Licenses to
enable/disable.
The DOrA Application QoS Features consist of:

Application Based Quality of Service (QoS) Support for HRPD Rev. A (FID
12078.9)
Radio Access Network (RAN) Quality of Service Enhancements for High Rate
Packet Data (HRPD) Rev. A (FID 12078.10)
More Quality of Service (QoS) Enhancements for the High Rate Packet Data
(HRPD) Revision A (Rev. A) Network (FID 12078.11)
Data Over Signaling Protocol (FID 12078.12)
Enhanced Idle State Protocol (FID 12078.13)
1xEV-DO Revision A (Rev. A): Data Over Signaling Protocol - FL (FID 12078.36)
1xEV-DO Basic Push-To-Talk (PTT) Using 1xEV-DO Rev. A Network (FID
12184.1)
High Rate Packet Data (HRPD) Push-to-Talk (PTT) Paging Enhancements (FID
12184.5)
Push-to-Talk (PTT) Enhancements (FID 12184.7)

Feature summary

In addition to the 1xEV-DO Basic Rev. A Feature Bundle there are sets of optional
Rev. A, VoIP and PTT related features called the DOrA Application QoS Features. The
DOrA Application QoS Features are made up of: FIDs 12078.9, 12078.10,
12078.11,12078.12, 12078.13,12078.36, 12184.1, 12184.5 and 12184.7, where the
....................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-1
Issue 5, May 2008
See notice on first page

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Overview

12078.x FIDs provide the QoS infrastructure and the QoS for Voice Over IP (VoIP)
and video, and the 12184.x FIDs provide QoS for Push-To-Talk (PTT) capabilities. The
DOrA Application QoS Features are an optional bundle controlled by an Application
DOrA License as described in 1xEV-DO RAS Planning and Implementation Guide,
401-614-101.
The activation of the DOrA Application QoS Features depends on the 1xEV-DO Basic
Rev. A Feature Bundle, this means the 1xEV-DO Basic Rev. A Feature Bundle needs to
be activated before the activation of the DOrA Application QoS Features. In other
words, the DOrA Application QoS Features depend on the 1xEV-DO Basic Rev. A
Feature Bundle.
All the DOrA Application QoS Features are enabled by the DOrA Application
Licenses. The FAF entries for all of these features are now enabled in all customers
Feature Activation Files (FAF). FAFs are not used to manage ANY of these features.
The only FAF legacy situation exists is that the 12078.x series of FIDs has a single
FAF entry, while the 12184.x FIDs have separate entries. However, it is not the
mechanism to turn on these features - the DOrA Application Licenses are the
mechanism.
Application Based Quality of Service (QoS) Support for HRPD Rev. A (FID
12078.9)

This feature is not part of the Rev. A Basic package of features. It supports QoS per
application flow based on request from the user, user QoS profile and allocatable
resource at the system. This feature only includes the Radio Access Network (RAN)
network elements. This feature is supported on both existing FMS and next generation
Radio Network Controller (RNC) platforms. Also this feature is supported on any base
station that supports the basic package for Rev. A. This feature will be configured on
both OMC-RAN and Operations and Maintenance Platform (OMP-FX) platforms.
Radio Access Network (RAN) Quality of Service Enhancements for High Rate
Packet Data (HRPD) Rev. A (FID 12078.10)

This feature includes enhancements to the Application Based Quality of Service (QoS)
Support for HRPD Rev. A (FID 12078.9). The enhancements are:

Enhanced Service Measurements


Support of Signaling Bus-1xEV-DO Modem (SB-EVM) Processor Overload
Control
Support of the RNC being able to modify the granted QoS
Overload Control enhancements which includes LIU Processor and RF Overload
situations

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

8-2

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Overview

More Quality of Service (QoS) Enhancements for the High Rate Packet Data
(HRPD) Revision A (Rev. A) Network (FID 12078.11)

This feature supports the following functionality to enhance Quality of Service (QoS)
operation for EV-DO Rev. A network, such as:

Enhanced carrier selection in mixed network (Rev. 0 /Rev. A).


FL Scheduler work to support additional states and allow to use RNC timestamp.
Infrastructure for improving TP clock accuracy and Switching Module (SM) counts
to support Backhaul and RNC processing Delays.
Enhanced Radio Network Controller (RNC) Overload Control and Session Status
Command support for Rev. A and MFPA.
Enhanced SMs and Per Call Measurement Data (PCMD) support .
Synchronizing RTCMAC attributes between AN and AT after they change in the
database.

Data Over Signaling Protocol (FID 12078.12)

This feature supports the Data over Signaling (DoS) Protocol (FID 12078.12). It allows
small amounts of data to be sent over the signaling channel when there is no traffic
channel connection. Applications that require quick message timing (such as, push to
talk), burst transport (such as, short message service) benefit from DoS.
This feature covers DoS for the reverse link. DoS over the forward link is covered in
FID 12076.36.
Important! Only MO-DOS is supported in R28.0.
Enhanced Idle State Protocol (FID 12078.13)

This feature supports the Enhanced Idle State protocol. The Enhanced Idle State offers
the following benefits over the Default Idle State defined in Rel 0, such as

shorter slot cycles for reducing paging delay


dynamic slot cycles defined for different ATs
longer slot cycles for improving battery life
enhanced hashing defined for improving paging delivery

This feature is applicable for all the BTS types that HRPD currently supports, with
classic EVMs/EVMms or SB-EVMs/SB-EVMms.
1xEV-DO Revision A (Rev. A): Data Over Signaling Protocol - FL (FID 12078.36)

This feature enables the support of transmission of small amounts of end user data
over the control channel (forward link) using the Data over Signaling (DoS) protocol
defined in the HRPD Rev. A standard. This feature is a complementary feature to FID
12078.12 which enables the support of transmission of small amounts of end user data
over the access channel (reverse link) using the DoS protocol.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-3
Issue 5, May 2008
See notice on first page

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Overview

1xEV-DO Basic Push-To-Talk (PTT) Using 1xEV-DO Rev. A Network (FID 12184.1)

The 1xEV-DO Basic PTT Using 1xEV-DO Rev. A Network feature provides the basic
PTT functionality in the HRPD RAN using HRPD Rev. A. HRPD Rev. A is required to
help meet the tight delay requirements. The feature provides support for PTT specific
FlowProfileIDs as defined in TIA TSB-58-G, specifically PTT Signaling
FlowProfileID 1283 and PTT Media FlowProfileIDs 261 through 280.
The 1xEV-DO Basic PTT Using 1xEV-DO Rev. A Network feature also includes
paging enhancements that can be used to provide flexibility to trade-off paging
efficiency and paging latency. For PTT, locating the users on the first paging attempt is
crucial for minimizing the initial setup delay. The Basic PTT using 1xEV-DO Rev. A
Network feature introduces QoS Paging where different QoS FlowProfileIDs can
have individual paging strategies. Each paging strategy can use two paging area types:

Last Active Set


Last Seen RNC (Color Code)

HRPD PTT Paging Enhancements (12184.5)

The High Rate Packet Data (HRPD) Push-to-Talk (PTT) Paging Enhancements feature
extends the QoS Paging capabilities provided by the Basic PTT feature above.
The HRPD PTT Paging Enhancements introduces support of two paging area types
when performing QoS Paging:

Neighbor RNC
RNC Group

The High Rate Packet Data (HRPD) Push-to-Talk (PTT) Paging Enhancements feature
adds the ability to have Priority Paging and additional paging areas options for RNC
paging.
Both features 12184.1 and 12184.5 are enhancements required for High Rate Packet
Data (HRPD) network to improve PTT performance by reducing the setup delays and
media delays for the Radio Access Network (RAN) components (base station, backhaul
and Radio Network Controller (RNC)). PTT services are based on HRPD Revision A
(Rev. A) to take advantage of the Enhanced Physical Layer and Quality of Service
(QoS) features that provide support for Voice Over IP (VoIP) and Multimedia services.
The PTT application is expected to prevent operation of the PTT service if High Rate
Packet Data Rev. A (HRPD-A) is not available.
Push-to-Talk (PTT) Enhancements (FID 12184.7)

To support applications like PTT that generate a significant paging load, the
Push-to-Talk (PTT) Enhancements feature adds distance based paging as an additional
paging method for QoS paging that was introduced in previous release by features
12184.1 and 12184.5. Also, this feature introduces the ability to specify QoS paging
strategy per RNC Group.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

8-4

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Overview

Impacts on user interfaces

The features that are described in this document impact the following user interfaces:
Feature

User interface

Feature impact

DOrA Application QoS


Features: FIDs 12087.9,
12078.10, 12078.11,
12078.12, 12078.13,
12078.36, 12184.1, 12184.5
and 12184.7

Element Management System


(EMS) or Operations and
Maintenance Center - Radio
Access Network (OMC-RAN)

See Implementing the


features (p. 8-52)

Service measurements

See Impacts on
service measurements
(p. 8-24)

Automatic Message
Accounting (AMA)
subsystem

None

Technician Interface (TI)


(input/output messages)

None

Intended audience

This document is intended for technicians, engineers, and system administrators who
implement or maintain the DOrA Application QoS Features in a CDMA2000
1xEV-DO Network.
To obtain technical support, documentation, and training or submit feedback

The Online Customer Support (OLCS) web site (http://support.lucent.com/) provides


access to technical support, related documentation, related training, and feedback tools.
The site also provides account registration for new users.
Contents
Availability

8-6

Prerequisites

8-7

Feature descriptions: DOrA Application QoS Features

8-9

Feature interactions

8-19

Impacts on service measurements

8-24

Issues and caveats

8-51

Implementing the features

8-52

Activating the feature

8-54

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-5
Issue 5, May 2008
See notice on first page

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Availability
...................................................................................................................................................................................................................................
Release availability

The following table identifies the AMPS/PCS software releases in which the DOrA
Application QoS Features are available.
Feature

Available in

FIDs 12087.9, 12078.10, 12078.12, 12078.1 3,


12184.1, and 12184.5

Releases 28.0 and later

FIDs 12078.11, 12078.36 and 12184.7

Release 29.0 and later

Market availability

The DOrA Application QoS Features are available in the following market:
Feature

Available in

DOrA Application QoS Features

All markets

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

8-6

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Prerequisites
...................................................................................................................................................................................................................................
Introduction

The DOrA Application QoS Features have the following prerequisites.


Supported technologies

The DOrA Application QoS Features support the following air-interface technologies:

EV-DO

Software requirements

DOrA Application QoS Features depend on the following features:

Basic Revision A (Rev. A) Feature Bundle (12078.2, 12078.3, 12078.4, 12078.5,


12078.7)
The operation of the PTT features (12184.1, 12184.5, 12184.7) depend on different
PTT applications that include AT with PTT client and a compatible PTT server.
MLPPP is required on the BTS-RNC backhaul for QoS features (12078.10). Since
PTT is a QoS application, MLPPP is required for any PTT feature deployment.

MLPPP is required for all the QoS features. The BTS-RNC Backhaul for QoS feature
(12078.10) was chosen as the feature to identified with MLPPP but since features
12078.9 and 12078.10 are both required for all the other features, all Enhanced Data
Only Revision A (DOrA) Application Quality of Service (QoS) Features are dependent
on MLPPP.
1xEV-DO Basic PTT Using 1xEV-DO Rev. A Network (FID 12184.1)

The 1xEV-DO Basic PTT Using 1xEV-DO Rev. A Network (FID 12184.1) feature
requires ECP Releases 28.0 or later.
The 1xEV-DO Basic PTT Using 1xEV-DO Rev. A Network (FID 12184.1) feature is
controlled by the PTT Feature Activation File (FAF) per Service Node basis. The PTT
FAF can be activated only if the Enhanced HRPD Rev. A package FAF is activated.
The Enhanced Rev A package are required for PTT and contain the following features:

Application Based Quality of Service (QoS) Support for HRPD Rev. A (FID
12078.9)
Data Over Signaling Protocol (FID 12078.12)
Enhanced Idle State Protocol (FID 12078.13)

In addition to FAF control the operator will have the ability to turn the feature ON/OFF
on Service Node basis.
Hardware requirements

The following summarizes the features described in this document.


...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-7
Issue 5, May 2008
See notice on first page

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Prerequisites

1xEV-DO Basic PTT Using 1xEV-DO Rev. A Network (FID 12184.1)

The 1xEV-DO Basic PTT Using 1xEV-DO Rev. A Network (FID 12184.1) feature
requires Multi Link Point-to-Point Protocol (MLPPP) on the backhaul in order to
support QoS. MLPPP is replacing the Cisco HDLC (cHDLC) protocol used in previous
releases and needs to be supported by the cells, routers and RNC. Since PTT is a QoS
application, MLPPP is required for PTT deployment.
HRPD PTT Paging Enhancements(FID 12184.5)

The High Rate Packet Data (HRPD) Push-to-Talk (PTT) Paging Enhancements feature
requires no hardware beyond the standard hardware in a CDMA2000 Network.
PTT Enhancements (FID 12184.7)

Push-To-Talk Enhancements feature requires no hardware beyond the standard


hardware for Application Based Quality of Service (QoS) support.
Obtain New License Keys

Customers will obtain new license keys depending on the type of swings:

Intra-RNC swing with the same BTS ID - No new license key is required
Intra-RNC swing with different BTS ID - New BTS license keys are required
Inter-RNC swing with the same or different BTS ID - New license keys are
required on both source and target RNC and BTS
License keys for target RNC and BTS must be installed prior to the swing. License
keys for source RNC and BTS must be installed after the swing.

For more details and specifics on how to obtain new license keys, see 401-614-101,
CDMA2000 1xEV-DO Network Radio Access System.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

8-8

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Feature
descriptions: DOrA Application QoS Features
...................................................................................................................................................................................................................................
Introduction

The following information defines the functionality, benefits, and operation of the
DOrA Application QoS Features.
Functionality

The DOrA Application QoS Features are made up of: FIDs 12078.9, 12078.10,
12078.11,12078.12, 12078.13,12078.36, 12184.1, 12184.5 and 12184.7, where the
12078.x FIDs provide the QoS infrastructure and the QoS for Voice Over IP (VoIP)
and video, and the 12184.x FIDs provide QoS for Push-To-Talk (PTT) capabilities. The
DOrA Application QoS Features are an optional bundle controlled by an Application
DOrA License as described in 1xEV-DO RAS Planning and Implementation Guide,
401-614-101.
Benefits

QoS provides support for differentiated treatment based on Service Categories Profile
ID, etc. The Paging features allow different paging strategies to be set for each Profile
ID.
How the feature operates

Refer to the sections below for a detailed description of how the DOrA Application
QoS Features operate:
Application Based Quality of Service (QoS) support for HRPD Rev. A (FID
12078.9)

This feature supports QoS per application flow based on request from the user, user
QoS profile and allocatable resource at the system. It only includes the RAN network
elements. With VoIP, there are IMS Network elements that need to support QoS. This
feature is supported on both existing FMS and next generation RNC platforms. Also it
is supported on any base station that supports the basic package for Rev. A. This
feature is configured on both OMC-RAN and OMP-FX platforms.
Service provider has the option to enable/disable this feature on a per service node
(SN) basis. The service provider populates a set of QoS profile IDs that they want the
system to support. This set will be from the set of Profile IDs that the product
supports.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-9
Issue 5, May 2008
See notice on first page

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Feature descriptions: DOrA Application QoS Features

RAN Quality of Service Enhancements for HRPD Rev A (FID 12078.10)

This feature provides enhancements to the Application Based Quality of Service (QoS)
support for HRPD Rev. A (FID 12078.9). This feature is dependent on the backhaul
protocol to be upgraded to MLPPP (Multi Link Point to Point Protocol) for T1/E1
links.

This feature offers the capability of the PDSN to modify the granted/ungranted
QoS for an existing reservation: If the AT sends a reservation request which grants
a reservation to the RAN, but the PDSN has a local policy that forbids it, this will
make the PDSN ungrant the reservation. The corollary of this situation is when a
specific AT requests a Profile Id that is not in the AAA server and should not be
granted, but the PDSN overrides this decision.
BTS Overload Control functionality: This includes complete Support of SB-EVM
Processor Overload Control and incremental support of LIU Overload Control. The
LIU Overload Control for Best Effort flows is already supported. This feature will
also take QoS flows into account.
Critical Service Measurements: The above two items include Service Measurements
related to the specific functionality. In addition to that, there are some specific
Service Measurements that the customers have already asked for. These are listed
in Section 8 of this document.
Overload Control enhancements which includes RF and Backhaul Overload
Control: This includes incremental improvements over Overload Detection and
Control mechanisms defined for FID 12078.9.

The control of this feature is the same as the basic QoS feature (12078.9). FID 12078.9
is enabled or disabled through FAF per SN basis. If 12078.9 is enabled, 12078.10 will
automatically be enabled.
More Quality of Service (QoS) Enhancements for the High Rate Packet Data
(HRPD) Revision A (Rev. A) Network (FID 12078.11)

The More Quality of Service (QoS) Enhancements for the High Rate Packet Data
(HRPD) Revision A (Rev. A) Network feature is supported by the same FAF as
12078.9 and 12078.10.
Important! This FID is able to support up to six flows.
After a Rev. A carrier is assigned to a Rev. A capable mobile, the previous
implementation automatically assigned a Rev. A personality to the mobile. In some
scenarios (one example is when the neighboring carriers are Rev. 0), it makes sense to
consider a Rev. 0 personality. This consideration is part of the feature.
A new Threshold is added for carrier selection such that if the number of users in a
Rev. A carrier is above that threshold, the Rev. A only mobile (without QoS
applications) will be assigned to Rev. 0 carriers.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

8-10

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Feature descriptions: DOrA Application QoS Features

A new Threshold is added for carrier selection such that when a Rev. 0 mobile
accesses the network through a Rev. A carrier, the customer has the ability to control if
the Rev. 0 mobile is assigned to the originating Rev. A carrier, or to a Rev. 0 carrier.
The decision is based on the relative number of users in the Rev. 0 and Rev.A carrier
and the threshold.
A new Threshold is added that specifies the minimum pilot strength for supporting a
Rev. A personality (Rev. A/DPA, Rev. A) without downgrading. That is if the combined
signal strength for current Rev. A personality is larger that the MinCombinedPilotStergnthRevA, personality downgrade will not be conducted.
The CSM6800 Scheduler uses 8 priority states for bit and bit stuffing metric but
previous implementation only allows maximum 3 priority states for each flow. The
enhancement increases the maximum number of priority states from 3 to 5 to improve
scheduler performance.
Previous implementation uses BTS timestamp for scheduling. The enhancement allows
the scheduler to use the RNC timestamp for scheduling. The scheduling performance
will be improved since the RNC timestamp includes the delay from RNC to the BTS.
A number of new translations are added for enabling or disabling this enhancement,
and for controlling the thresholds that defines when the RNC timestamp or the BTS
timestamp should be used by the FL scheduler.
Critical SM and PCMD support including delay counts:

Peak and Average Open Flows Per Service Category.


Reservation Terminations because of excessive Packet Loss for Conversational
Speech and Conversational Voice, and PTT applications.
Traffic Delay SMs that measures the Forward Link scheduling delays at the BTS
and also the Backhaul delays between RNC to BTS.
Special Engineering Studies for SB-EVM Overload Control.

Session Status Command:

The Session State Information Record will be enhanced to include Rev A protocols
and MFPA information.

TP and AP Overload Control Enhancement:

For AP Overload Control enhancement, paging request throttling will give


preference to throttling BE related paging requests before QoS related paging
requests. When a TP is in overload when a Reservation Request is received along
with a connection request, an alternate TP should be selected. For PTT Call Setup,
an alternate TP will be selected in a similar situation.

Synchronizing RTCMAC attributes between AN and AT after they change in


translations and tunables:

If there is a change in RTCMAC attribute in RNC DB, ensure that AT also changes
the same in next connection.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-11
Issue 5, May 2008
See notice on first page

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Feature descriptions: DOrA Application QoS Features

Data Over Signaling Protocol (FID 12078.12)

DoS is part of the Multi-Flow Packet Application (M-FPA) and is not separately
negotiated between the AN and the AT. With M-FPA (provided in 12078.9), the AT
establishes RLP flows with the network. When certain criteria is met, DoS is used to
carry the flow data.
The DoS message format has the following characteristics:

Carry the RLP flow ID - identify the RLP flow the data is associated with
Can indicate if acknowledgment to the receipt of DoS message is required
Carry message sequence number to allow duplicated message detection
Contain entire higher layer packet (for example, entire HDLC frame packet)

In the reverse link direction, the AT application decides if the RLP flow packets need
to be sent via DoS. The RLP flow is first established between the AT and the AN (via
session configuration or GAUP) and activated. Once activated (and the associated
reservation is in the open state), the RLP flow packets is sent via the access channel
using DoS and the AN forwards the packets to the PDSN over the associated A10
connection.
In the forward link direction, the AN will send DoS to the AT only when the AT is
dormant (such as, traffic channel has not been established). If a traffic channel is
available, incoming packets received from the PDSN are sent over the traffic channel.
When the AT is dormant, the AN decides if the incoming packet is appropriate to be
sent using DoS or should the AT be paged. It examines the size of the packet, the
availability of the control channel and the DoS filtering criteria to decide.
The DoS filtering criteria specified by the operator, defines the properties of the RLP
flow for which DoS can be considered. It includes options such as matching DSCP
(Differentiated Services Code Point) and QoS Profile data that are used as the filter. If
the condition is not in favor of sending DoS, the AT is paged to receive the data.
As DoS packets is sent to the AT while it is dormant, different DoS sending algorithms
(for example, number of retries, number of sectors receiving DoS, locate AT first
before sending DoS) is adopted for different RLP flows depending on the associated
QoS profile data.
This feature supports DoS which is part of the Multi-Flow Packet Application
(M-FPA).
This feature is bundled together with 12078.9 and 12078.13 as a single package
(Enhanced Rev A Feature Bundle) and is controlled by FAF on a per service node
basis.
Important! Only MO-DOS is supported in R28.0.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

8-12

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Feature descriptions: DOrA Application QoS Features

Enhanced Idle State Protocol (FID 12078.13)

In a HRPD data session, the AT switches between the connected state and the idle
state. In the connected state, traffic channels are assigned and data is sent and received.
When there are no data activities for a predefined period, the traffic channels are
de-assigned and the AT is in the idle state. In the Default Idle State operation, the AT
sleeps 12 control channel (CC) cycles (5.12 seconds) during idle and wakes up
periodically to monitor the CC for events such as paging. The AN keeps track of the
AT wake up time and sends paging to the AT via the CC only at the AT wake up time.
This approach has the following drawbacks:

Waking up every 5.12 seconds may be too long for handling paging

To address the issues, Enhanced Idle State adopts the following approach:

The periods that the AT sleeps are variables negotiated between the AT and the AN
during session configuration (or using GAUP)
Three periods are defined with wake up intervals and period duration
AN sends paging to AT via CC only at the AT wake up time (same as Default Idle
State)
Page mask also defined to identify the time that the mobile is not monitoring the
CC for paging (for example, tune away for 3G-1X operation)

The T_Page1 parameter is the paging escalation timer for this feature. When this timer
expires, the AN broadens the area over which it will page the AT. By doing so, it
increases the backhaul load of the network. To minimize the impact to the network
load the parameter value of 60 is used as an off switch. Instead of a broaden page area
after 60 minutes, the paging escalation is turned off when the value is set to 60. So
when the default is set to 60, the default setting is off.
This feature works together with 12078.9 and 12078.12 as a single package (Enhanced
Rev A Feature Bundle) and is controlled by FAF on a per service node basis.
1xEV-DO Revision A (Rev. A): Data Over Signaling Protocol - FL (FID 12078.36)

This feature enables the support of transmission of small amounts of end user data
over the control channel (forward link) using the Data over Signaling (DoS) protocol
defined in the HRPD Rev. A standard. This feature is a complementary feature to FID
12078.12 which enables the support of transmission of small amounts of end user data
over the access channel (reverse link) using the DoS protocol.
1xEV-DO Basic PTT Using 1xEV-DO Rev. A Network (FID 12184.1)

The 1xEV-DO Basic PTT Using 1xEV-DO Rev. A Network feature provides basic PTT
functionality in the HRPD RAN using HRPD Rev. A. The HRPD Rev. A feature is
required to help meet the tight QoS requirements.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-13
Issue 5, May 2008
See notice on first page

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Feature descriptions: DOrA Application QoS Features

The 1xEV-DO Basic PTT Using 1xEV-DO Rev. A Network feature improves PTT
performance by up to three distinct QoS flows for PTT applications to use to provide
differentiated QoS in the RAN. It also provides the ability to provide paging
latency/efficiency tradeoffs by allowing the service provider to individually specify the
paging strategy for different types of QoS flows.
Although PTT applications can function over a best effort EVDO RAN network (e.g.
using Default Packet Application), to be a viable commercial service the QoS
capabilities provided by the Multi-Flow Packet Application are required.
The PTT application resides in the mobile client and the PTT servers. The application
signaling and traffic path are originated/terminated in the mobile clients and controlled
by the PTT server. PTT signaling can be SIP-based or proprietary SIP-like protocol.
The RAN function is to recognize the PTT application and insure minimum delay for
signaling and media, based on the QoS treatment specified.
The PTT requires half-duplex communication so the requirements are different than
full-duplex VoIP requirements: PTT has more stringent signaling delay requirements
while VoIP has more stringent media delay requirements. The feature is based on the
Multiflow Packet Application (MFPA) and does not require header compression. RTP
frame bundling may be used by PTT application to reduce Internal Protocol/Universal
Datagram Protocol/Rate Time Protocol (IP/UDP/RTP) header overhead by allowing
multiple vocoder frames into one IP packet, thereby increasing air interface capacity.
The 1xEV-DO Basic PTT Using 1xEV-DO Rev. A Network feature is intended to be
the initial DO PTT implementation that can be deployed with the first HRPD Rev. A
ATs that might not support Robust Header Compression (ROHC) are required for VoIP.
The 1xEV-DO Basic PTT Using 1xEV-DO Rev. A Network feature is defined to be
independent of the PTT application implementations as long as they comply to the
standard HRPD Rev. A and QoS as defined in TIA TSB-58-G, TIA-856-A-2, and
TIA-835-D. The feature is expected to work with different PTT solutions. If additional
enhancements are required for OMA PoC compliance with a specific PTT application
(for example, OMA POC), a separate feature will be required.
The PTT service performance (setup and media latencies) are heavily dependent on the
different PTT solutions.
The RAN delay component (including backhaul delay) is one of the several elements
that determine the PTT service delay performance. Other components of the overall
delay are: mobile client PTT application, PDSN processing, core network legacy, PTT
servers. These elements are outside the scope of this feature.
RAN QoS Background

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

8-14

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Feature descriptions: DOrA Application QoS Features

The Application Based Quality of Service (QoS) Support for HRPD Rev. A feature
(FID 12078.9) and the RAN Quality of Service Enhancements for HRPD Rev A
feature (FID 12078.10) provide the fundamental capabilities to support the Multi-Flow
Packet Application (MFPA). These features provide support for four Service Categories
(that is, groupings of related application flows that share common QoS controls)

Media Control Signaling (MCS): not delay sensitive


Best effort (BE): not delay sensitive, high capacity
Conversational Speech (CS): delay sensitive, low latency
Conversational Video (CV): delay sensitive, low latency

Each Service Category may contain multiple IP flow types (labeled with a ProfileID)
with similar QoS requirements. Each Service Category is assigned with a dedicated
RLP flow and each RLP flow is one to one mapped to an A10 connection.
The initial PTT feature assumes the use of MFPA and requires separate flows identified
by different ProfileID for PTT signaling and PTT media. TIA TSB-58-G defines the
FlowProfileIDs that can be used for different applications, including PTT. Each
ProfileID maps to a specific FlowProfileID. The PTT application must use a supported
ProfileID to allow the adequate QoS treatment. Verbose negotiation of QoS flow
parameters is not supported.
The PTT application will use a specific ProfileID to allow the adequate QoS treatment.
To meet the unique QoS requirements of PTT, two new service categories are added as
follows:

Low Latency Media Control Signaling (LL-MCS) service category is added to


support PTT signaling
Conversational PTT Speech service category is added to accommodate the different
QoS needs of the PTT bearer

The 1xEV-DO Basic PTT Using 1xEV-DO Rev. A Network feature also introduces four
new Profile IDs for PTT:
Under the LL-MCS Service Category:

PTT Call Setup Signalling ProfileID


PTT In-Call Signalling ProfileID

Under the Conversational PTT Speech Service Category:

PTT Speech Bearer 1 ProfileID


PTT Speech Bearer 2 ProfileID

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-15
Issue 5, May 2008
See notice on first page

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Feature descriptions: DOrA Application QoS Features

These new service categories and ProfileIDs allow the service provider to differentiate
the treatment of PTT related flows with respect to other types of data traffic. With
Feature 12184.1, the mapping between the ProfileID (for example. PTT Speech Bearer
1) and the TSB-58-G FlowProfileID is not fixed, but can be configured. However, the
RAN is configured to best support the following configuration:
FeatureProfileID

FlowProfileID Value

PTT Call Setup Signaling ProfileID

1283

PTT In-Call Signaling ProfileID

Blank

PTT Speech Bearer 1 ProfileID

280

PTT Speech Bearer 2 ProfileID

Blank

If this profile ID is configured, then the


profile ID parameters are applicable to
ProfileID 261.

Important! Whenever a PTT Speech Bearer ProfileID is modified, please contact


Alcatel-Lucent support to update the appropriate header compression capability for
the PTT forward link backhaul bearer traffic processing messages.
In a multi-media model, PTT data arriving for a dormant AT must be treated differently
than the best effort data-only case. PTT introduces data traffic with different QoS
requirements for different flows. Voice applications in general and especially PTT
require lower latency for initial setup. Therefore, paging methods must be more
intelligent and require flexibility to accommodate different classes of traffic.
To accommodate the stringent delays requirements for initial call setup, a new QoS
Paging Strategy is introduced for PTT. The QoS paging strategy is a per ProfileID
strategy that can be configured per attempt for different paging areas. Up to 8 paging
attempts can be specified for each ProfileID. The paging area is defined to be one of
the following types (defined on a per Profile ID/per page attempt basis):

Last_Active_Set
Last_Seen_RNC

Subscriber perspective:The

PTT service fills the average persons need for fast short
communication. The ability to instantaneously communicate at the push of a button
with one and even a group of people appeals to different segments of users from chatty
teenagers to first responders. PTT services are in big demand for commercial networks
(private use and enterprise markets) and public safety networks.
Service-provider perspective:Deploying

PTT services using HRPD air interface is an


evolution allowing operators to take advantage of the VoIP capabilities and enhanced
performance of the new HRPD networks while maintaining the capacity and
performance of legacy circuit voice services. The 1xEV-DO Basic PTT Using
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

8-16

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Feature descriptions: DOrA Application QoS Features

1xEV-DO Rev. A Network feature allows the service providers to offer a competitive
PTT service to their subscribers while increasing the value of their wireless data
package.
The HRPD PTT can be integrated with IMS increasing the set of blended services
offered to subscribers. Blended services are IMS services that share a set of capabilities
and databases allowing different applications to be integrated.
High Rate Packet Data (HRPD) Push-to-Talk (PTT) Paging Enhancements (FID
12184.5)

The HRPD PTT Paging Enhancements feature includes the following functionality:

Priority paging:which allows pages to be scheduled based on certain criteria. The


criteria are ProfileID (for example, PTT versus conversational speech) , page area
(for example Last_Active_Set versus Last_Seen_RNC) and page attempt. The
priority of the criteria is provisionable (for example First Rank Pages based on
ProfileID, then PageAarea, and then Page Attempt).
RNC paging:which allows paging over multiple RNCs. QoS paging introduced by
1xEV-DO Basic PTT Using 1xEV-DO Rev. A Network (FID 12184.1) is extended
to include RNC Group and Neighbor RNC paging areas methods. These methods are
implemented under the RNC Grouping to Improve Idle Hand-off Performance
feature (12456.1), only their use for QoS paging is part of the HRPD PTT Paging
Enhancements feature (FID 12184.5).

QoS Paging De-escalation

The HRPD PTT Paging Enhancements feature improves PTT performance by reducing
the setup delays and media delays for the RAN components (base station, backhaul and
RNC).
It adds the ability to QoS Paging for Priority Paging, Paging Areas that span RNCs in
a Group, and Paging De-escalation.
Deploying PTT services using HRPD air interface is an evolution allowing operators to
take advantage of the VoIP capabilities and enhanced performance of the new HRPD
networks while maintaining the capacity and performance of legacy circuit voice
services. The HRPD PTT Paging Enhancements feature allows the service providers to
offer a competitive PTT service to their subscribers while increasing the value of their
wireless data package.
The HRPD PTT can be integrated with IMS increasing the set of blended services
offered to subscribers. Blended services are IMS services that share a set of capabilities
and databases allowing different applications to be integrated.
PTT Enhancements (FID 12184.7)

Distance based paging allows the paging area to be defined based on distance from the
last registered cell. The radius of the paging area is defined using 4 tiers and is
provisionable. The first tier is specified to be based on the radius used for
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-17
Issue 5, May 2008
See notice on first page

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Feature descriptions: DOrA Application QoS Features

RouteUpdateRadius. The RouteUpdateRadius parameter, when set to a non-zero

value, is used to require the AT to do distance based registration. The other three tiers
can be defined to provide greater flexibility. Distance based paging is supported within
an RNC group. The 4 Distance based paging tiers are added as additional paging
methods for QoS paging that was introduced in the previous release by features FIDs
12184.1 and 12184.5.
After this feature is implemented, the paging strategy for a ProfileID allows the
following paging methods for each paging attempt:

Last_Active_Set
Last_Seen_RNC
Neighbor_RNC
RNC_Group
Distance_Tier0
Distance_Tier1
Distance_Tier2
Distance_Tier3

Distance based paging is introduced to improve the paging efficiency, especially when
the RNC group capability is supported. Customers can defined a region where AT is
required to report to AN when it has moved out of the region. So AT can be paged
reliably within a distance based region. The distance based paging region can be
optimized to balance the paging efficiency and AT reporting frequency. This is
especially useful when RNC group capability is supported. RNC grouping is introduced
by FID 12456.1, see Chapter 11 of this document, as a way to reduce the
UATIRequest ping-ponging and paging failures at RNC borders. At the same time, by
not having UATIRequest at the RNC borders, the RAN looses the ability to be able to
know the location of the AT within the RNC group. Distance based paging allows the
RAN to use a smaller paging area than the entire RNC group.
To allow additional flexibility, the PTT Enhancements feature provides the option to
provision the paging strategy for a ProfileID per RNC group. This is in addition to per
SN/ProfileID provisioning provided by FIDs 12184.1, and 12184.5.
Having the paging strategy for ProfileID be provisionable per RNC group in addition
to per SN allows operators the flexibility of setting QoS Paging Strategy uniformly
across an RNC Group since an SN can support multiple RNC Groups and RNC
Groups are allowed to span multiple SNs.
Distance based paging is controlled by the Distance Paging Enable control field. See
Activating the feature (p. 8-54) for details.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

8-18

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Feature
interactions
...................................................................................................................................................................................................................................
Introduction

The DOrA Application QoS Features interact or depend on the following features.
Important! The 1xEV-DO Rev. A VoIP and Application Pricing FID 12905.0 is the
Application Pricing feature fro R28.0 that FIDs 12078.9, 12078.10, etc. are
dependent on. The FID 12905.1 is the R29 Application Pricing feature. The DOrA
Application QoS Features cannot be activated without the licenses from FIDs
12905.0 and 12905.1.
Basic Revision A (Rev. A) Feature Bundle

FIDs 12078.2, 12078.3, 12078.4, 12078.5 and 12078.7 make up the software collection
referred to as Rev. A Feature Bundle and are activations via a software licensing key
mechanism instead of the usual Feature Activation File/Qualified Feature Activation
File (FAF/QFAF) mechanism.
The Basic DOrA License Key must be purchased in order to enable DOrA Application
functionality. The license key is used for the activation of the DOrA Application
functionality for one or more Rev. A-capable Base Transceiver Station (BTS)-Carriers
served by the RNC.
Basic DOrA License Key is managed by the RNC and is enabled per carrier. For
example:

Base station 1 has one Rev A carrier, therefore, 1 Rev A license is required.
Base station 2 has two Rev A carriers, therefore, 2 Rev A licenses are required.
Base station 3 has three Rev A carriers, therefore, 3 Rev A licenses are required.

The service provider needs to install the license key via Element Management System
(EMS) or EMS or OMC-RAN GUI on the OMP-FX and assign license keys to the
base station carriers to enable the base station carrier(s).
When the Basic Rev. A Features are activated within the Radio Access System they are
referred to as HRPD Rev. A system.
The HRPD Rev. A system supports Release 27.0 FIDs and any new Rev. A features.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-19
Issue 5, May 2008
See notice on first page

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Feature interactions

Enhanced Reverse and Forward Links using Enhanced MAC Protocols with Rev.
A Subtype 2 Physical Layer (FID 12078.2)

This feature is part of the Basic Rev. A Feature Bundle, also referred to as Basic Rev.
A Feature Bundle. This feature introduces the support of the full Rev. A Physical Layer
with the complete set of Rev. A enhanced MAC protocols that is the following MAC
protocols are supported:

Enhanced Control Channel (CC) MAC


Enhanced Forward Traffic Channel (FTC) MAC
Enhanced Access Channel (AC) MAC
Enhanced Subtype 3 Reverse Traffic Channel (RTC) MAC

This feature is supported on all Modular Cell BTS types using the new HRPD Rev. A
modem board, the SB-EVM for Modular Cell 4.0 and variants or the SB-EVMm for
Modular Cell 1-3. This feature is supported only by the Rev. A capable RNC.
Generic Attribute Update Protocol (GAUP) for Dynamic Parameters Update (FID
12078.3)

This feature is part of the Basic Rev. A Feature Bundle. This feature allows
configuration attribute changes without costly session configuration protocol exchange
and without releasing the connection. It allows the AT and the AN to use the GAUP to
update values of the session parameter attributes belonging to different lower and
higher layer protocols and applications.
HRPD Rev. A Support on Modular Cell 1-3 BTS Platforms using SB-EVMm (FID
12078.4)

This feature is part of the Basic Rev. A Feature Bundle and provides the necessary
hardware and software for the Modular Cell 1-3 products to make use of any other
Rev. A feature. This feature supports HRPD Rev. A technology on all Modular Cell
1-3. This feature includes Software, OA&M and Service Measurements support related
to HRPD Rev. A for the Modular Cell 1-3 BTS platforms.
The following Modular Cell 1.0/2.0/3.0 BTS products will be supported:

Modular Cell 3.0


Modular Cell 2.0
Modular Cell 1.0

The term Modular Cell 1-3 is used in this chapter to include the variants listed above.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

8-20

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Feature interactions

HRPD Rev. A Support on Modular Cell 4.0 BTS Platforms using SB-EVM (FID
12078.5)

This feature is part of the Basic Rev. A Feature Bundle and provides the necessary
hardware and software for the Modular Cell 4.0 products to make use of any other
Rev. A feature. This feature supports HRPD Rev. A technology on all Modular Cell 4.0
Platforms. This feature includes Software, OA&M and Service Measurements support
related to HRPD Rev. A for the Modular Cell 4.0 platforms.
The following Modular Cell 4.0 products will be supported:

Modular Cell 4.0


Modular Cell 4.0 B
Compact 4.0
Compact 4.0 B
HD 4.0
HD 4.0 B
Digital Host 4.0
Digital Host 4.0 B

The term Modular Cell 4.0 is used in this chapter to include the variants listed above.
Inter and Intra-RNC Handoff Enhancement (FID 12078.7)

This feature is part of the Basic Rev. A Feature Bundle. The purpose of this feature is
to support, in both Rel 0 systems and in mixed Rel 0/Rev. A systems:

every type of handoff that is currently supported in a Rel 0 system (soft/softer on


traffic channel; hard handoff across carriers on traffic channel; inter-RNC dormant
session handoff)
handoffs from Rev. A PHYsical/Medium Access Control (PHY/MAC) connections
to Rel 0 PHY/MAC connections.

This feature does not include active handoff from Rel. 0 to Rev. A systems.
Application Based Quality of Service (QoS) Support for HRPD Rev. A (FID 12078.9)

FID 12078.9 depends on the Rev. A Basic Feature Bundle (12078.2, 12078.3, 12078.4,
12078.5, 12078.7) for the Basic Rev. A function and interface:

HDR Reverse Link Overload Control (HROC ) (FID 8048.1)


Important! The HROC feature (FID 8048.1) handles the RF overload in the
reverse link. This action takes the user class into account while making decisions.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-21
Issue 5, May 2008
See notice on first page

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Feature interactions

RAN Quality of Service Enhancements for HRPD Rev. A (FID 12078.10)

FID 12078.10 depends on the Rev. A Basic Feature Bundle (12078.2, 12078.3,
12078.4, 12078.5, 12078.7) for the Enhanced DOrA Feature Bundle functions and
interfaces and the basic QoS feature 12078.9. This means that 12078.10 is
automatically dependent on any features the above features depend upon.
This feature is also dependent on 1xEV-DO Backhaul with Multi Link Point-to-Point
Protocol (MLPPP) at Layer 2 Over T1/E1 (FID 12304.11) , Chapter 9, at layer 2 over
T1/E1 links. This essentially means that the operator needs to transition from HDLC to
MLPPP if they would like to take advantage of Quality of Service feature and the
associated applications.
In addition, 1xEV-DO Rev. A VoIP and Application Pricing (FID 12905.0) Chapter 10,
introduces a separate pricing structure based on various QoS applications. This means
that any new QoS application will be priced according an algorithm defined by FID
12905.0. FID 12078.10 has interactions with FID 12905.0 since it supports Video
Telephony application.
More Quality of Service (QoS) Enhancements for the High Rate Packet Data (HRPD) Revision A
(Rev. A) Network (FID 12078.11)

This feature is dependent on the basic Rev. A package (FIDs 12078.2, 12078.3,
12078.4, 12078.5 and 12078.7) and the QoS features. This feature is still automatically
dependent on 1x- EV-DO Backhaul with Mutli Link Point-to-Point Protocol (MLPPP),
FID 12304.11, Chapter 9 of this document. If the backhaul is not upgraded to MLPPP,
customers can not take advantage of QoS features or services.
Data Over Signaling Protocol (FID 12078.12)

FID 12078.12 depends on the Rev. A Basic Feature Bundle (12078.2, 12078.3,
12078.4, 12078.5, 12078.7) for the Enhanced DOrA Feature Bundle functions and
interfaces.
Data over Signaling is part of the Multi-Flow Packet Application (M-FPA). This
feature therefore depends on (FID 12078.9) the QoS feature that supports M-FPA. DoS
cannot be used unless M-FPA is first configured. If quicker handling of DoS over the
control channel is desirable, FID 12078.13 (Enhanced Idle State) is applied.
Enhanced Idle State Protocol (FID 12078.13)

FID 12078.13 depends on the Rev. A Basic Feature Bundle (12078.2, 12078.3,
12078.4, 12078.5, 12078.7) for the Enhanced DOrA Feature Bundle functions and
interfaces.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

8-22

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Feature interactions

1xEV-DO Revision A (Rev. A): Data Over Signaling Protocol - FL (FID 12078.36)

FID 12078.36 depends on the Rev. A Basic Feature Bundle (12078.2, 12078.3,
12078.4, 12078.5, 12078.7) for the Enhanced DOrA Feature Bundle functions and
interfaces. This feature is a complementary feature to FID 12078.12.
1xEV-DO Basic PTT Using 1xEV-DO Rev. A Network (FID 12184.1)

The 1xEV-DO Basic PTT Using 1xEV-DO Rev. A Network (FID 12184.1) introduces
QoS paging using two paging area types: Last Seen Active Set and Last Seen RNC
(Color Code). The HRPD PTT Paging Enhancements (FID 12184.5) feature adds the
ability to have Priority Paging and extends it to include RNC Group and Neighbor
RNC paging areas.
HRPD PTT Paging Enhancements (FID 12184.5)

The HRPD PTT Paging Enhancements feature interacts with the following features:

1xEV-DO Basic PTT Using 1xEV-DO Rev. A Network (FID 12184.1)


Radio Network Controller (RNC) Grouping to Improve Idle Hand-off Performance
(FID 12456.1)

PTT Enhancements (FID 12184.7)

PTT Enhancements interacts with the following features:

HRPD PTT Paging Enhancements (FID 12184.5)


1xEV-DO Revision A (Rev. A): Data Over Signaling Protocol - FL (FID 12078.36)

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-23
Issue 5, May 2008
See notice on first page

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Impacts
on service measurements
...................................................................................................................................................................................................................................
Introduction

The DOrA Application QoS Features affect the following categories of services
measurements:
Application Based Quality of Service (QoS) Support for HRPD Rev. A (FID
12078.9)

The major focuses of the new service measurements for the Application Based Quality
of Service (QoS) Support for HRPD Rev. A feature are to provide information on how
the system supports the QoS applications, and how the service providers can better
engineer the system. The SMs for Application Based Quality of Service (QoS) Support
for HRPD Rev. A feature are grouped into the following categories:

Setup related counts


Connection request relate
Reservation related
Reservation downgrade (priority change) counts
Reservation termination/drop counts
Personality switch counts (minimum)
Overload related counts

The SM counts defined for Application Based Quality of Service (QoS) Support for
HRPD Rev. A feature will be reported as zeros if the feature is disabled. The SM
counts that are required for all Rev A services, are included in Protocols with Rev. A
Physical Layer (12078.2) feature or/and the Inter and Intra-Radio Network Controller
(RNC) Handoff Enhancement (FID 12078.7) feature instead of the Application Based
Quality of Service (QoS) Support for HRPD Rev. A feature. Also, many of the existing
Rel 0 and Basic Rev-A SMs are carried forward in the Application Based Quality of
Service (QoS) Support for HRPD Rev. A feature. What this means is that most (if not
all) of the existing counts remain applicable to measure the system performance in
various aspects when the Application Based Quality of Service (QoS) Support for
HRPD Rev. A feature is enabled, regardless whether the AT is using the QoS services
or not.
RAN Quality of Service Enhancements for HRPD Rev. A (FID 12078.10)

These new service measurements are related to RAN Quality of Service Enhancements
for HRPD Rev. A (FID 12078.10).

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

8-24

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Impacts on service measurements

The RAN Quality of Service Enhancements for HRPD Rev. A (FID 12078.10) feature
affects the service measurements that are identified in Table 8-1, RAN Quality of
Service Enhancements for HRPD Rev. A Feature: New Service Measurements
(p. 8-25)
Table 8-1

RAN Quality of Service Enhancements for HRPD Rev. A Feature:


New Service Measurements

Service measurement
subcategory

Count abbreviation

Count name

CG CONTL

SM_FL_BH_PACKET_LOSS_FL BH Packet Loss Rate


RATE_CPS
for Push-to-Talk

CG CONTL

SM_FL_BH_PACKET_LOSS_FL BH Packet Loss Rate


RATE_CS
for Conversational Speech

CG CONTL

SM_FL_BH_PACKET_LOSS_FL BH Packet Loss Rate


RATE_CV
for Conversational Video

CG CONTL

SM_RL_BH_PACKET_LOSS_RL BH Packet Loss Rate


RATE_CPS
for Push-to-Talk DSCP

CG CONTL

SM_RL_BH_PACKET_LOSS_RL BH Packet Loss Rate


RATE_CS
for Conversational Speech
DSCP

CG CONTL

SM_RL_BH_PACKET_LOSS_RL BH Packet Loss Rate


RATE_CV
for Conversational Video
DSCP

CG EVM

AVG_PERC_FLOWS_MUTED_
Average percentage of RL
BAP
BE flows muted due to
BAP overload

CG EVM

AVG_PERC_FLOWS_MUTED_
Average percentage of RL
BMP
BE flows muted due to
BMP overload

CG EVM

AVG_PERC_PACKETS_
DROPPED_BAP

CG EVM

AVG_PERC_SLOTS_SKIPPED_
Average percentage of FL
BMP
slots skipped in DSP due
to BMP overload

CG EVM

AVG_PERC_WINDOW_
SHRANK_BAP

Average percentage of FL
EF packets dropped due to
BAP overload

Average percentage of FL
BE flows window size
shrank due to BAP
overload

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-25
Issue 5, May 2008
See notice on first page

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Table 8-1

Impacts on service measurements

RAN Quality of Service Enhancements for HRPD Rev. A Feature:


New Service Measurements (continued)

CG EVM

PEAK_PERC_FLOWS_
MUTED_BAP

Peak percentage of RL BE
flows muted due to BAP
overload

CG EVM

PEAK_PERC_FLOWS_
MUTED_BMP

Peak percentage of RL BE
flows muted due to BMP
overload

CG EVM

PEAK_PERC_PACKETS_
DROPPED_BAP

Peak percentage of FL EF
packets dropped due to
BAP overload

CG EVM

PEAK_PERC_SLOTS_
SKIPPED_BMP

Peak percentage of FL
slots skipped in DSP due
to BMP overload

CG EVM

PEAK_PERC_WINDOW_
SHRANK_BAP

Peak percentage of FL BE
flows window size shrank
due to BAP overload

CG OHM

CPS_RESV_CLOSED_PDSN_Push-to-Talk reservations
A11_SESSION_UPDATE
closed due to A11 Session
Update

CG OHM

CS_RESV_CLOSED_PDSN_ Conversational Speech


A11_SESSION_UPDATE
reservations closed due to
A11 Session Update

CG OHM

CV_RESV_CLOSED_PDSN_ Conversational Video


A11_SESSION_UPDATE
reservations closed due to
A11 Session Update

CG OHM

RESV_GRANTED_PDSN_
A11_SESSION_UPDATE

Reservations granted by
A11 session update from
the PDSN

CG OHM

RESV_NULLED_PDSN_
A11_SESSION_UPDATE

Reservations nulled by A11


session update from the
PDSN

SECT-CARR-HCS

EVM_ACCESS_CH_MAC_
PACKETS_19_2

Number of Access MAC


Layer Packets Received on
Access Channel at
19.2kbps

SECT-CARR-HCS

EVM_ACCESS_CH_MAC_
PACKETS_38_4

Number of Access MAC


Layer Packets Received on
Access Channel at
38.4kbps

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

8-26

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Table 8-1

Impacts on service measurements

RAN Quality of Service Enhancements for HRPD Rev. A Feature:


New Service Measurements (continued)

SECT-CARR-HCS

EVM_ACCESS_CH_MAC_
PACKETS_9_6

Number of Access MAC


Layer Packets Received on
Access Channel at 9.6kbps

SECT-CARR-HCS

EVM_AVG_USERS_PER_
MUP

Average Number of Users


per Multiple User Packet

SECT-CARR-HCS

EVM_FL_MUPS

Number of Multiple User


Packets Transmitted on
Forward Link

SECT-CARR-HCS

EVM_RLP_RETXED_FTC_ RLP Octets Retransmitted


BE
on the Forward Traffic
Channels for Best Effort

SECT-CARR-HCS

EVM_RLP_RETXED_FTC_ RLP Octets Retransmitted


DARQ_BE
on Forward Traffic
Channels due to DARQ for
Best Effort

SECT-CARR-HCS

EVM_RLP_RETXED_FTC_ RLP Octets Retransmitted


DARQ_CPS
on Forward Traffic
Channels due to DARQ for
Push-to-Talk

SECT-CARR-HCS

EVM_RLP_RETXED_FTC_ RLP Octets Retransmitted


DARQ_CS
on Forward Traffic
Channels due to DARQ for
Conversational Speech

SECT-CARR-HCS

EVM_RLP_RETXED_FTC_ RLP Octets Retransmitted


DARQ_CV
on Forward Traffic
Channels due to DARQ for
Conversational Video

SECT-CARR-HCS

EVM_RLP_RETXED_FTC_ RLP Octets Retransmitted


DARQ_SMC
on Forward Traffic
Channels due to DARQ for
SMC

SECT-CARR-HCS

EVM_RLP_RETXED_FTC_ RRLP Octets Retransmitted


SMC
on the Forward Traffic
Channels for SMC

SECT-CARR-HCS

EVM_RLP_TXED_FTC_
BE

RLP Octets Transmitted on


the Forward Traffic
Channels for Best Effort

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-27
Issue 5, May 2008
See notice on first page

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Table 8-1

Impacts on service measurements

RAN Quality of Service Enhancements for HRPD Rev. A Feature:


New Service Measurements (continued)

SECT-CARR-HCS

EVM_RLP_TXED_FTC_
CPS

RLP Octets Transmitted on


the Forward Traffic
Channels for Push-to-Talk

SECT-CARR-HCS

EVM_RLP_TXED_FTC_
CS

RLP Octets Transmitted on


the Forward Traffic
Channels for
Conversational Speech

SECT-CARR-HCS

EVM_RLP_TXED_FTC_
CV

RLP Octets Transmitted on


the Forward Traffic
Channels for
Conversational Video

SECT-CARR-HCS

EVM_RLP_TXED_FTC_
SMC

RLP Octets Transmitted on


the Forward Traffic
Channels for SMC

SECT-CARR-HCS

RLP_RCVD_RTC_SMC

RLP Octets Received on


the Reverse Traffic
Channels for SMC

TP

A11_SESSION_UPDATE_
ACCEPTED

A11 session update


accepted

TP

A11_SESSION_UPDATE_
RECEIVED

A11 session update


received

TP

A11_SESSION_UPDATE_
REJECTED

A11 session update


rejected

More QoS Enhancements for the HRPD Rev. A Network (FID 12078.11)

The More QoS Enhancements for the HRPD Rev. A Network (FID 12078.11) feature
includes a number of service measurements meant to measure the QoS capabilities
already implemented in 12078.9 and 12078.10. These SMs can be grouped in to the
following categories:

SBEVM Overload related measurements defined in terms of SES (Special

Engineering Studies) SMs.


Reservation termination are new SMs capturing additional reservation termination
scenarios.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

8-28

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Impacts on service measurements

Personality (especially MFPA) related SMs are MFPA specific SMs that could

not be incorporated in the earlier release, although the corresponding capability is


already implemented. (Note that since Rev. A has distinct personalities, such as
DPA (Default Packet Application), and MFPA (Multi-Flow Packet Application), and
are not always distinguished, MFPA may use Rev. A general SMs defined in other
features.
Usage related SMs include the average and peak open flows of each service
category. Also, since certain service categories have multiple rates, average and
peak bandwidth allocated are collected as well for these categories.
FL Packet Drops in TP for each service category when TP is in overload.
Delays are SMs measuring FL BTS delay , FL RNC delay as well as FL and RL
backhaul delays.

The More QoS Enhancements for the HRPD Rev. A Network (FID 12078.11) feature
affects the service measurements that are identified in the Table 8-2, More QoS
Enhancements for the HRPD Rev. A Network: Modified Service Measurements
(p. 8-29), Table 8-3, More QoS Enhancements for the HRPD Rev. A Network: New
Service Measurements (p. 8-30), Table 8-4, More QoS Enhancements for the HRPD
Rev. A Network: Existing Service Measurements Pegged by Feature (p. 8-38) and
Table 8-5, More QoS Enhancements for the HRPD Rev. A Network: Renamed Service
Measurements (p. 8-38).
Important! The following counts were defined for DBEVM. The names and
descriptions were modified and reused for SBEVM with out creating new counts.
Table 8-2

More QoS Enhancements for the HRPD Rev. A Network: Modified


Service Measurements

Service measurement
subcategory

Count abbreviation

Count name

SNHCS-CTID-EVM

FLM_BAP_AVG_PROC_
OCCUPANCY

FLM/BAP Average
Processor Occupancy

SNHCS-CTID-EVM

FLM_BAP_PEAK_PROC_
OCCUPANCY

FLM/BAP Average
Processor Occupancy

SNHCS-CTID-EVM

FLM_BAP_OVERLOAD_
DURATION

Duration of FLM/BAP in
Overload

SNHCS-CTID-EVM

FLM_BAP_OVERLOAD_
NUM

Number of times
FLM/BAP in Overload

SNHCS-CTID-EVM

RLM_BMP_AVG_PROC_
OCCUPANCY

RLM/BMP Average
Processor Occupancy

SNHCS-CTID-EVM

RLM_BMP_PEAK_PROC_
OCCUPANCY

RLM/BMP Peak Processor


Occupancy

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-29
Issue 5, May 2008
See notice on first page

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Table 8-2

Impacts on service measurements

More QoS Enhancements for the HRPD Rev. A Network: Modified


Service Measurements (continued)

SNHCS-CTID-EVM

RLM_BMP_OVERLOAD_
DURATION

Duration of RLM/BMP in
Overload

SNHCS-CTID-EVM

RLM_BMP_OVERLOAD_
NUM

Number of times
RLM/BMP in Overload

Table 8-3

More QoS Enhancements for the HRPD Rev. A Network: New Service
Measurements

Service measurement
subcategory

Count abbreviation

Count name

SN-HCS-CTID-EVM

TIMES_SLOTS_SKIPPED_ FL slots skipped due to


BMP_10
overload in the BMP is
between 1 to 10 percent.

SN-HCS-CTID-EVM

TIMES_SLOTS_SKIPPED_ FL slots skipped due to


BMP_20
overload in the BMP is
between 11 to 20 percent.

SN-HCS-CTID-EVM

TIMES_SLOTS_SKIPPED_ FL slots skipped due to


BMP_30
overload in the BMP is
between 21 to 30 percent.

SN-HCS-CTID-EVM

TIMES_SLOTS_SKIPPED_ FL slots skipped due to


BMP_40
overload in the BMP is
between 31 to 40 percent.

SN-HCS-CTID-EVM

TIMES_SLOTS_SKIPPED_ FL slots skipped due to


BMP_50
overload in the BMP is
between 41 to 50 percent.

SN-HCS-CTID-EVM

TIMES_SLOTS_SKIPPED_ FL slots skipped due to


BMP_60
overload in the BMP is
between 51 to 60 percent.

SN-HCS-CTID-EVM

TIMES_SLOTS_SKIPPED_ FL slots skipped due to


BMP_70
overload in the BMP is
between 61 to 70 percent.

SN-HCS-CTID-EVM

TIMES_SLOTS_SKIPPED_ FL slots skipped due to


BMP_80
overload in the BMP is
between 71 to 80 percent.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

8-30

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Table 8-3

Impacts on service measurements

More QoS Enhancements for the HRPD Rev. A Network: New Service
Measurements (continued)

SN-HCS-CTID-EVM

TIMES_FLOWS_MUTED_ RL BE flows are muted due


BMP_10
to overload in the BMP is
between 1 to 10 percent.
Note that there is 1 flow per
call in Rev. 0 and multiple
flows per call in Rev. A.

SN-HCS-CTID-EVM

TIMES_FLOWS_MUTED_ RL BE flows are muted due


BMP_20
to overload in the BMP is
between 11 to 20 percent.
Note that there is 1 flow per
call in Rev. 0 and multiple
flows per call in Rev. A.

SN-HCS-CTID-EVM

TIMES_FLOWS_MUTED_ RL BE flows are muted due


BMP_30
to overload in the BMP is
between 21 to 30 percent.
Note that there is 1 flow per
call in Rev. 0 and multiple
flows per call in Rev. A.

SN-HCS-CTID-EVM

TIMES_FLOWS_MUTED_ RL BE flows are muted due


BMP_40
to overload in the BMP is
between 31 to 40 percent.
Note that there is 1 flow per
call in Rev. 0 and multiple
flows per call in Rev. A.

SN-HCS-CTID-EVM

TIMES_FLOWS_MUTED_ RL BE flows are muted due


BMP_50
to overload in the BMP is
between 41 to 50 percent.
Note that there is 1 flow per
call in Rev. 0 and multiple
flows per call in Rev. A.

SN-HCS-CTID-EVM

TIMES_FLOWS_MUTED_ RL BE flows are muted due


BMP_60
to overload in the BMP is
between 51 to 60 percent.
Note that there is 1 flow per
call in Rev. 60 and multiple
flows per call in Rev. A.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-31
Issue 5, May 2008
See notice on first page

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Table 8-3

Impacts on service measurements

More QoS Enhancements for the HRPD Rev. A Network: New Service
Measurements (continued)

SN-HCS-CTID-EVM

TIMES_FLOWS_MUTED_ RL BE flows are muted due


BMP_70
to overload in the BMP is
between 61 to 70 percent.
Note that there is 1 flow per
call in Rev. 0 and multiple
flows per call in Rev. A.

SN-HCS-CTID-EVM

TIMES_FLOWS_MUTED_ RL BE flows are muted due


BMP_80
to overload in the BMP is
between 71 to 80 percent.
Note that there is 1 flow per
call in Rev. 0 and multiple
flows per call in Rev. A.

SN-HCS-CTID-EVM

TIMES_WINDOW_SHRANK_
FL BE flows window size
BAP_10
shrank due to overload in
the BAP is between 1 to 10
percent.

SN-HCS-CTID-EVM

TIMES_WINDOW_SHRANK_
FL BE flows window size
BAP_20
shrank due to overload in
the BAP is between 11 to 20
percent.

SN-HCS-CTID-EVM

TIMES_WINDOW_SHRANK_
FL BE flows window size
BAP_30
shrank due to overload in
the BAP is between 21 to 30
percent.

SN-HCS-CTID-EVM

TIMES_WINDOW_SHRANK_
FL BE flows window size
BAP_40
shrank due to overload in
the BAP is between 31 to 40
percent.

SN-HCS-CTID-EVM

TIMES_WINDOW_SHRANK_
FL BE flows window size
BAP_50
shrank due to overload in
the BAP is between 51 to 60
percent.

SN-HCS-CTID-EVM

TIMES_WINDOW_SHRANK_
FL BE flows window size
BAP_60
shrank due to overload in
the BAP is between 51 to 60
percent.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

8-32

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Table 8-3

Impacts on service measurements

More QoS Enhancements for the HRPD Rev. A Network: New Service
Measurements (continued)

SN-HCS-CTID-EVM

TIMES_WINDOW_SHRANK_
FL BE flows window size
BAP_70
shrank due to overload in
the BAP is between 61 to 70
percent.

SN-HCS-CTID-EVM

TIMES_WINDOW_SHRANK_
FL BE flows window size
BAP_80
shrank due to overload in
the BAP is between 71 to 80
percent.

SN-HCSCTID- EVM

TIMES_FLOWS_MUTED_ RL BE flows are muted due


BAP_10
to overload in the BAP is
between 1 to 10 percent.
Note that there is 1 flow per
call in Rev. 0 and multiple
flows per call in Rev. A.

SN-HCSCTID- EVM

TIMES_FLOWS_MUTED_ RL BE flows are muted due


BAP_20
to overload in the BAP is
between 11 to 20 percent.
Note that there is 1 flow per
call in Rev. 0 and multiple
flows per call in Rev. A.

SN-HCSCTID- EVM

TIMES_FLOWS_MUTED_ RL BE flows are muted due


BAP_30
to overload in the BAP is
between 21 to 30 percent.
Note that there is 1 flow per
call in Rev. 0 and multiple
flows per call in Rev. A.

SN-HCSCTID- EVM

TIMES_FLOWS_MUTED_ RL BE flows are muted due


BAP_40
to overload in the BAP is
between 31 to 40 percent.
Note that there is 1 flow per
call in Rev. 0 and multiple
flows per call in Rev. A.

SN-HCSCTID- EVM

TIMES_FLOWS_MUTED_ RL BE flows are muted due


BAP_50
to overload in the BAP is
between 41 to 50 percent.
Note that there is 1 flow per
call in Rev. 0 and multiple
flows per call in Rev. A.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-33
Issue 5, May 2008
See notice on first page

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Table 8-3

Impacts on service measurements

More QoS Enhancements for the HRPD Rev. A Network: New Service
Measurements (continued)

SN-HCSCTID- EVM

TIMES_FLOWS_MUTED_ RL BE flows are muted due


BAP_60
to overload in the BAP is
between 51 to 60 percent.
Note that there is 1 flow per
call in Rev. 0 and multiple
flows per call in Rev. A.

SN-HCSCTID- EVM

TIMES_FLOWS_MUTED_ RL BE flows are muted due


BAP_70
to overload in the BAP is
between 61 to 70 percent.
Note that there is 1 flow per
call in Rev. 0 and multiple
flows per call in Rev. A.

SN-HCSCTID- EVM

TIMES_FLOWS_MUTED_ RL BE flows are muted due


BAP_80
to overload in the BAP is
between 71 to 80 percent.
Note that there is 1 flow per
call in Rev. 0 and multiple
flows per call in Rev. A.

SN-HCS-CTID-EVM

TIMES_PACKETS_DROPPED_
FL EF packets are dropped
BAP_10
due to overload in the BAP
is between 1 to 10 percent.

SN-HCS-CTID-EVM

TIMES_PACKETS_DROPPED_
FL EF packets are dropped
BAP_10
due to overload in the BAP
is between 11 to 20 percent.

SN-HCS-CTID-EVM

TIMES_PACKETS_DROPPED_
FL EF packets are dropped
BAP_20
due to overload in the BAP
is between 21 to 30 percent.

SN-HCS-CTID-EVM

TIMES_PACKETS_DROPPED_
FL EF packets are dropped
BAP_30
due to overload in the BAP
is between 31 to 40 percent.

SN-HCS-CTID-EVM

TIMES_PACKETS_DROPPED_
FL EF packets are dropped
BAP_40
due to overload in the BAP
is between 31 to 40 percent.

SN-HCS-CTID-EVM

TIMES_PACKETS_DROPPED_
FL EF packets are dropped
BAP_50
due to overload in the BAP
is between 41 to 50 percent.

SN-HCS-CTID-EVM

TIMES_PACKETS_DROPPED_
FL EF packets are dropped
BAP_60
due to overload in the BAP
is between 51 to 60 percent.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

8-34

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Table 8-3

Impacts on service measurements

More QoS Enhancements for the HRPD Rev. A Network: New Service
Measurements (continued)

SN-HCS-CTID-EVM

TIMES_PACKETS_DROPPED_
FL EF packets are dropped
BAP_70
due to overload in the BAP
is between 61 to 70 percent.

SN-HCS-CTID-EVM

TIMES_PACKETS_DROPPED_
FL EF packets are dropped
BAP_80
due to overload in the BAP
is between 71 to 80 percent.

SN-HCS-ANT-CARR

FL_RESV_TERM_DROPPED_
FL reservations terminated
PKTS_EX_THRESH
due to number of dropped
packets exceeding threshold:
Conversational PTT Speech,
Speech, Video

SN-HCS-ANT-CARR

RL_RESV_RM_OPPOSITE_ RL Reservations Terminated


RESV_DROP
due to Termination of
Opposite Reservations:
Conversational PTT Speech,
Speech, Video

SN-HCS-ANT-CARR

FL_RESV_TERM_INV_
BH

FL reservations terminated
due to unacceptable BH type
of newly added sector to
active set: Conversational
PTT Speech, Speech, Video

SN-HCS-ANT-CARR

RL_RESV_TERM_INV_
BH

RL reservations terminated
due to unacceptable BH type
of newly added sector to
active set: Conversational
PTT Speech, Speech, Video

SN-HCS-ANT-CARR

PERS_SWTCH_CONN_
TCA

Traffic Channel Assignments


for Personality Switch

SN-HCS-ANT-CARR

PERS_SWTCH_CONN_
ESTABLISHED

Established Connections for


Personality Switch

SN-IEnd- FMS-OHM

NUM_AT_MFPA_SESS_
ESTABLISHED

ATs with Rev. A/MFPA as


the highest personality
negotiated.

SN-HCS-ANT-CARR

AVG_OPEN_FL_FLOW

Average FL Bandwidth
Allocated for Conversational
PTT Speech, Speech, Video

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-35
Issue 5, May 2008
See notice on first page

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Table 8-3

Impacts on service measurements

More QoS Enhancements for the HRPD Rev. A Network: New Service
Measurements (continued)

SN-HCS-ANT-CARR

AVG_OPEN_RL_FLOW

Average FL Bandwidth
Allocated for Conversational
PTT Speech, Speech, Video

SN-HCS-ANT-CARR

PEAK_OPEN_FL_FLOW

Peak Number of Open FL


Flows: Conversational PTT
Speech, Speech, Video

SN-HCS-ANT-CARR

PEAK_OPEN_RL_FLOW

Peak Number of Open RL


Flows: Conversational PTT
Speech, Speech, Video

SN-HCS-ANT-CARR

AVG_FL_BW_ALLOCATED_
Average FL Bandwidth
CV
Allocated for Conversational
Video

SN-HCS-ANT-CARR

AVG_RL_BW_ALLOCATED_
Average RL Bandwidth
CV
Allocated for Conversational
Video

SN-HCS-ANT-CARR

PEAK_FL_BW_ALLOCATED_
Peak FL Bandwidth
CV
Allocated for Conversational
Video

SN-HCS-ANT-CARR

PEAK_RL_BW_ALLOCATED_
Peak RL Bandwidth
CV
Allocated for Conversational
Video

SN-FMS-TP

A10_PKT_SENT_TO_
RLP

A10 Packets Sent to RLP

SN-FMS-TP

RLP_PKT_SENT_TO_
PCF

RLP Packets Sent to PCF

SN-FMS-TP

FL_PACKETS_DROPPED_ FL EF Packets Dropped


TP_OVLD_EF
when TP is in overload

SN-FMS-TP

FL_PACKETS_DROPPED_ FL SMC Packets Dropped


TP_OVLD_SMC
when TP is in overload

SN-FMS-TP

FL_PACKETS_DROPPED_ FL BE Packets Dropped


TP_OVLD_BE
when TP is in overload

SN-HCS-ANT-CARR

FL_BTS_DELAY_SUM

SN-HCS-ANT-CARR

FL_BTS_DELAY_TOTAL_ FL BTS delay RLP packets


PKTS
sampled: BE, CS, CPS, CV,
LLMCS, and SMC.

FL BTS delay aggregate for


RLP packets: BE, CS, CPS,
CV, LLMCS, and SMC.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

8-36

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Table 8-3

Impacts on service measurements

More QoS Enhancements for the HRPD Rev. A Network: New Service
Measurements (continued)

SN-HCS-ANT-CARR

FL_BTS_DELAY_S_
PEAK

FL BTS delay smoothed


peak for RLP packets: BE,
CS, CPS, CV, LLMCS, and
SMC.

SN-FMS-BTS

FL_RNC_DELAY_SUM

FL RNC delay aggregate for


RLP Packets: BE, CS, CPS,
CV, LLMCS, and SMC.

SN-FMS-BTS

FL_RNC_DELAY_TOTAL_ FL RNC delay RLP Packets


PKTS
sampled: BE, CS, CPS, CV,
LLMCS, and SMC.

SN-FMS-BTS

FL_RNC_DELAY_S_
PEAK

FL RNC Delay smoothed


peak for RLP Packets: BE,
CS, CPS, CV, LLMCS, and
SMC.

SN-HCSCTID

FL_RNC_N_BH_DELAY_
SUM

FL RNC + BH delay
aggregate for RLP packets:
BE, CS, CPS, CV, LLMCS,
and SMC.

SN-HCSCTID

FL_RNC_N_BH_DELAY_
TOTAL_PKTS

FL RNC + BH delay RLP


packets sampled: BE, CS,
CPS, CV, LLMCS, and
SMC.

SN-HCSCTID

FL_RNC_N_BH_DELAY_
S_PEAK

FL RNC + BH delay RLP


packets sampled: BE, CS,
CPS, CV, LLMCS, and
SMC.

SN-FMS-BTS

RL_BTS_N_BH_DELAY_
SUM

RL BTS + BH delay
aggregate for RLP packets:
BE, CS, CPS, CV, LLMCS,
and SMC.

SN-FMS-BTS

RL_BTS_N_BH_DELAY_
TOTAL_PKTS

RL BTS + BH delay RLP


packets sampled: BE, CS,
CPS, CV, LLMCS, and
SMC.

SN-FMS-BTS

RL_BTS_N_BH_DELAY_
S_PEAK

RL BTS + BH delay
smoothed peak for RLP
packets: BE, CS, CPS, CV,
LLMCS, and SMC.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-37
Issue 5, May 2008
See notice on first page

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Table 8-3

Impacts on service measurements

More QoS Enhancements for the HRPD Rev. A Network: New Service
Measurements (continued)

SN-FMS-TP

AVG_CLK_ROOT_
DISPERSION

Average clock root


dispersion

SN-FMS-TP

AC_RL_TP_EF_QUE_
OVLD

Number of RL reservation
admission failures due to TP
EF Queue Overload

SN-HCS-ANT-CARR

EVM_PCNT_RAB_SET_
TO_ONE

Percentage of RAB set to


one during the hour

Table 8-4

More QoS Enhancements for the HRPD Rev. A Network: Existing


Service Measurements Pegged by Feature

Service measurement
subcategory

Count abbreviation

Count name

SN-HCS-ANT-CARR

AHO_PERS_SWTCH_
REVA_TO_REL0

Number of Personality
Switches During Active
Connections from Rev
A/DPA to Rel. 0.

SN-HCS-ANT-CARR

CONN_SETUP_PERS_
SWTCH_REL0_TO_
REVA

Number of Personality
Switches During Connection
Setup From Rel. 0 to Rev
A/DPA.

SN-HCS-ANT-CARR

CONN_SETUP_PERS_
SWTCH_REVA_TO_
REL0

Number of Personality
Switches During Connection
Setup From Rev A/DPA to
Rel 0

SN-HCS-ANT-CARR

Number of Personality
CONN_SETUP_PERS_
SWTCH_UNKNOWN_TO_ Switches During Connection
Setup From Unknown to
REVA
Rev A/DPA

Table 8-5

More QoS Enhancements for the HRPD Rev. A Network: Renamed


Service Measurements

Service measurement
subcategory

Count abbreviation

Count name

SN-IEnd-FMS-OHM

RESV_CLOSED_A11_
SESS_UPDATE_CS

Conversational Speech
reservations closed due to
A11 Session Update.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

8-38

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Table 8-5

Impacts on service measurements

More QoS Enhancements for the HRPD Rev. A Network: Renamed


Service Measurements (continued)

SN-IEnd-FMS-OHM

RESV_CLOSED_A11_
SESS_UPDATE_CV

Conversational Video
reservations closed due to
A11 Session Update.

SN-IEnd-FMS-OHM

RESV_CLOSED_A11_
SESS_UPDATE_CPS

Push-to-Talk reservations
closed due to A11 Session
Update.

SN-IEnd-FMS-OHM

RESV_GRANTED_A11_
SESS_UPDATE

Reservations granted by A11


session update from the
PDSN.

SN-IEnd-FMS-OHM

RESV_NULLED_A11_
SESS_UPDATE

Reservations nulled by A11


session update from the
PDSN.

SN-HCS-ANT-CARR

SM_ENHANCED_AVG_
RSSIRISE

Average Enhanced RSSI Rise


Over An Hour.

SN-HCS-ANT-CARR

EVM_RESV_DWNGRD_
FL_CPS

Number of FL Reservation
Downgraded for
Conversational PTT Speech
reservations.

SN-HCS-ANT-CARR

EVM_RESV_DWNGRD_
FL_CS

Number of FL Reservation
Downgraded for
Conversational Speech
reservations.

SN-HCS-ANT-CARR

EVM_RESV_DWNGRD_
FL_CV

Number of FL Reservation
Downgraded for
Conversational Video
reservations.

SN-HCS-ANT-CARR

EVM_RF_IN_OVLD_FL_ Number of Times FL CS RF


CS
is in Overload.

SN-HCS-ANT-CARR

EVM_RF_IN_OVLD_FL_ Number of Times FL CV RF


CV
is in Overload.

SN-HCS-ANT-CARR

EVM_RF_IN_BLOCK_
RL_CS

Number of Times RL RF
Congestion Overload Control
CS State Machine Enters
Block State from Normal.

SN-HCS-ANT-CARR

EVM_RF_IN_BLOCK_
RL_CV

Number of Times RL RF
Congestion Overload Control
CV State Machine Enters
Block State from Normal.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-39
Issue 5, May 2008
See notice on first page

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Table 8-5

Impacts on service measurements

More QoS Enhancements for the HRPD Rev. A Network: Renamed


Service Measurements (continued)

SN-HCS-ANT-CARR

EVM_RF_IN_OVLD_TOT_Total Duration FL CS RF Is
DUR_FL_CS
In Overload.

SN-HCS-ANT-CARR

EVM_RF_IN_OVLD_TOT_Total Duration FL CV RF Is
DUR_FL_CV
In Overload.

SN-HCS-ANT-CARR

EVM_RF_IN_BLOCK_
TOT_DUR_RL_CS

Total Duration RL RF
Congestion Overload Control
CS State Machine Is In
Block.

SN-HCS-ANT-CARR

EVM_RF_IN_BLOCK_
TOT_DUR_RL_CV

Total Duration RL RF
Congestion Overload Control
CV State Machine Is In
Block.

SN-HCS-ANT-CARR

AT_INIT_CONN_ATMPT_ AT-Initiated Connection


FAIL_ROR_REJECTED
Attempt Failures ReservationOnRequest
rejected.

SN-HCS-ANT-CARR

RESV_DROP_PERS_
SWITCH_CPS

Number of Conversational
PTT SPeech Reservations
Dropped When the
Personality is switched from
Rev. A/MFPA to Rev. A/DPA
or Rev. 0.

SN-HCS-ANT-CARR

RESV_DROP_PERS_
SWITCH_CS

Number of Conversational
Speech Reservations Dropped
Due to Personality Switch.

SN-HCS-ANT-CARR

RESV_DROP_PERS_
SWITCH_CV

Number of Conversational
Video Reservations Dropped
Due to Personality Switch.

SN-HCS-ANT-CARR

RESV_DROP_BH_OVLD_ Number of FL Conversational


FL_CPS
PTT Speech Reservations
Dropped due to Backhaul
Overload.

SN-HCS-ANT-CARR

RESV_DROP_BH_OVLD_ Number of FL Conversational


FL_CS
Speech Reservations Dropped
due to Backhaul Overload.

SN-HCS-ANT-CARR

RESV_DROP_BH_OVLD_ Number of FL Conversational


FL_CV
Video Reservations Dropped
due to Backhaul Overload.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

8-40

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Table 8-5

Impacts on service measurements

More QoS Enhancements for the HRPD Rev. A Network: Renamed


Service Measurements (continued)

SN-HCS-ANT-CARR

AC_RF_RES_FAILURE_
FL_CPS

Number of FL reservation
admission failures for
Conversational PTT Speech
due to FL RF resource.

SN-HCS-ANT-CARR

AC_BH_RES_FAILURE_ Number of FL reservation


FL_CS
admission failures for
Conversational Speech due to
FL Backhaul Resource.

SN-HCS-ANT-CARR

AC_RF_RES_FAILURE_
FL_CS

SN-HCS-ANT-CARR

AC_BH_RES_FAILURE_ Number of FL reservation


FL_CV
admission failures for
Conversational Video due to
FL Backhaul Resource.

SN-HCS-ANT-CARR

AC_RF_RES_FAILURE_
FL_CV

SN-HCS-ANT-CARR

AC_BH_RES_FAILURE_ Number of FL reservation


FL_CPS
admission failures for
Conversatoinal PTT Speech
due to FL Backhaul
Resource.

SN-HCS-ANT-CARR

RESV_ADMITTED_FL_
CPS

Number of FL Reservations
Admitted for Conversational
PTT Speech.

SN-HCS-ANT-CARR

RESV_ADMITTED_FL_
CS

Number of FL Reservations
Admitted for Conversational
Speech.

SN-HCS-ANT-CARR

RESV_ADMITTED_FL_
CV

Number of FL Reservations
Admitted for Conversational
Video.

SN-HCS-ANT-CARR

RESV_REQ_FL_CPS

Number of FL Reservations
Requested for Conversational
PTT Speech.

Number of FL reservation
admission failures for
Conversational Speech due to
FL RF Resource.

Number of FL reservation
admission failures for
Conversational Video due to
FL RF Resource.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-41
Issue 5, May 2008
See notice on first page

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Table 8-5

Impacts on service measurements

More QoS Enhancements for the HRPD Rev. A Network: Renamed


Service Measurements (continued)

SN-HCS-ANT-CARR

RESV_REQ_FL_CS

Number of FL Reservations
Requested for Conversational
Speech.

SN-HCS-ANT-CARR

RESV_REQ_FL_CV

Number of FL Reservations
Requested for Conversational
Video.

SN-HCS-ANT-CARR

RESV_DROP_BH_OVLD_ Number of RL
RL_CPS
Conversational PTT Speech
Reservations Dropped due to
Backhaul Overload.

SN-HCS-ANT-CARR

RESV_DROP_RF_OVLD_ Number of RL
RL_CPS
Conversational PTT Speech
Reservations Dropped due to
RL RF Overload.

SN-HCS-CTID-EVM

RESV_DROP_RF_OVLD_ Number of RL
RL_CV
Conversational Rate Video
Reservations Dropped due to
RL RF Overload.

SN-HCS-ANT-CARR

RESV_DROP_BH_OVLD_ Number of RL
RL_CS
Conversational Speech
Reservations Dropped due to
Backhaul Overload.

SN-HCS-ANT-CARR

RESV_DROP_RF_OVLD_ Number of RL
RL_CS
Conversational Speech
Reservations Dropped due to
RL RF Overload.

SN-HCS-ANT-CARR

RESV_DROP_BH_OVLD_ Number of RL
RL_CV
Conversational Video
Reservations Dropped due to
Backhaul Overload.

SN-HCS-ANT-CARR

AC_BH_RES_FAILURE_ Number of RL reservation


RL_CPS
admission failures for
Conversational PTT Speech
due to RL Backhaul
Resource.

SN-HCS-ANT-CARR

AC_RF_RES_FAILURE_
RL_CPS

Number of RL Reservation
admission failures for
Conversational PTT Speech
due to RL RF Resource.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

8-42

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Table 8-5

Impacts on service measurements

More QoS Enhancements for the HRPD Rev. A Network: Renamed


Service Measurements (continued)

SN-HCS-ANT-CARR

AC_BH_RES_FAILURE_ Number of RL reservation


RL_CS
admission failures for
Conversational Speech due to
RL Backhaul Resourceo.

SN-HCS-ANT-CARR

AC_RF_RES_FAILURE_
RL_CS

SN-HCS-ANT-CARR

AC_BH_RES_FAILURE_ Number of RL reservation


RL_CV
admission failures for
Conversational Video due to
RL Backhaul Resource.

SN-HCS-ANT-CARR

AC_RF_RES_FAILURE_
RL_CV

Number of RL reservation
admission failures for
Conversational Video due to
RL RF Resource.

SN-HCS-ANT-CARR

RESV_ADMITTED_RL_
CPS

Number of RL Reservations
Admitted for Conversational
PTT Speech.

SN-HCS-ANT-CARR

RESV_ADMITTED_RL_
CS

Number of RL Reservations
Admitted for Conversational
Speech.

SN-HCS-ANT-CARR

RESV_ADMITTED_RL_
CV

Number of RL Reservations
Admitted for Conversational
Video.

SN-HCS-ANT-CARR

RESV_REQ_RL_CPS

Number of RL Reservations
Requested for Conversational
PTT Speech.

SN-HCS-ANT-CARR

RESV_REQ_RL_CS

Number of RL Reservations
Requested for Conversational
Speech.

SN-HCS-ANT-CARR

RESV_REQ_RL_CV

Number of RL Reservations
Requested for Conversational
Video.

SN-HCS-ANT-CARR

RLP_RCVD_RTC_CPS

RLP Octets Received on


Reverse Traffic Channels for
Conversational PTT Speech.

Number of RL reservation
admission failures for
Conversational Speech due to
RL RF Resource.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-43
Issue 5, May 2008
See notice on first page

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Table 8-5

Impacts on service measurements

More QoS Enhancements for the HRPD Rev. A Network: Renamed


Service Measurements (continued)

SN-HCS-ANT-CARR

RLP_RCVD_RTC_CS

RLP Octets Received on


Reverse Traffic Channels for
Conversational Speech.

SN-HCS-ANT-CARR

RLP_RCVD_RTC_CV

RLP Octets Received on


Reverse Traffic Channels for
Conversational Video.

SN-HCS-ANT-CARR

RL_LOLAT_PKTS_MISSED_
Total number of RL loLat
TARGET
Packets Missed Termination
Target.

SN-FMS-TP

RL_LOLAT_PKTS_
RCVD

Total number of RL loLat


Packets Received at TP..

SN-FMS-TP

EF_PKTS_DROP_EF_
QUE_OVLD

Number of EF Packets
Dropped from EF Queue Due
to EF Queue Full.

SN-FMS-TP

TP_AC_FAILURE_EF_
QUE_OVLD

TP Admission evaluation
failure due to TP EF Queue
Overload.

Data Over Signaling Protocol (FID 12078.12)

These new service measurements are related to Data Over Signaling Protocol (FID
12078.12).
The Data Over Signaling Protocol (FID 12078.12) feature affects the service
measurements that are identified in Table 8-6, Data Over Signaling Protocol Feature:
New Service Measurements (p. 8-44)
Table 8-6

Data Over Signaling Protocol Feature: New Service Measurements

Service measurement
subcategory

Count abbreviation

Count name

SECT-CARR-HDRC

MO_DOS_BE

Mobile Originated DoS BE


Messages Received

SECT-CARR-HDRC

MO_DOS_CMCS

Mobile Originated DoS


CMCS Messages Received

SECT-CARR-HDRC

MO_DOS_LL_MCS

Mobile Originated DoS


LL_MCS Messages
Received

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

8-44

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Impacts on service measurements

1xEV-DO Basic PTT Using 1xEV-DO Rev. A Network (FID 12184.1)

The 1xEV-DO Basic PTT Using 1xEV-DO Rev. A Network feature affects the
following categories of services measurements:

RNC sector carrier short interval counts


HCS sector carrier short interval counts
HDR sector carrier short interval counts

RNC sector carrier service measurements

The DOrA Application QoS Features feature affects the RNC sector carrier service
measurements that are identified in Table 8-7, RNC sector carrier service
measurements (p. 8-45).
Table 8-7

RNC sector carrier service measurements

Service measurement
subcategory

Count
abbreviation

CG RNC-PGPROFID

PAGE_REQ_DROPPED_
Number of FL Reservation
Downgraded for Conversational
AP_OVLD

Count name

PTT Speech reservations

HCS sector carrier service measurements

The DOrA Application QoS Features feature affects the HCS sector carrier service
measurements that are identified in Table 8-8, HCS sector carrier service
measurements (p. 8-45).
Table 8-8

HCS sector carrier service measurements

Service measurement
subcategory

Count
abbreviation

Count name

SECT-CARR-HCS

EVM_NUM_FL_
RESERVATION_
DOWNGRADED_CPS

AN-Initiated Connection
Requests for Predictive Flow
Admission

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-45
Issue 5, May 2008
See notice on first page

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Impacts on service measurements

HDR sector carrier service measurements

The DOrA Application QoS Features feature affects the HDR sector carrier service
measurements that are identified in Table 8-9, HDR sector carrier service
measurements (p. 8-46).
Table 8-9

HDR sector carrier service measurements

Service measurement
subcategory

Count
abbreviation

SECT-CARR-HDRC

CONV_PTT_SPCH_ Number of Conversational PTT


RESV_DRPD_PER_ Speech Reservations Dropped
SWITCH_MFPA_DPA_ When the Personality is
switched from Rev A/MFPA to
R0

Count name

Rev A/DPA or Rev 0


SECT-CARR-HDRC

FL_RESV_ADMT_
CONV_PTT_
SPEECH

Number of FL Reservations
Admitted for Conversational
PTT Speech

SECT-CARR-HDRC

FL_RESV_ADMT_
FAIL_CONV_PTT_
SPCH_FL_BKHAUL_
RES

Number of FL reservation
admission failures for
Conversational PTT Speech due
to FL Backhaul Resource

SECT-CARR-HDRC

FL_RESV_ADMT_
FAIL_CONV_PTT_
SPCH_FL_RF_RES

Number of FL reservation
admission failures for
Conversational PTT Speech due
to FL RF resource

SECT-CARR-HDRC

FL_RESV_DRPD_
CONV_PTT_SPCH_
BKHAUL_OVL

Number of FL Conversational
PTT Speech Reservations
Dropped due to Backhaul
Overload

SECT-CARR-HDRC

FL_RESV_REQ_
CONV_PTT_
SPEECH

Number of FL Reservations
Requested for Conversational
PTT Speech

SECT-CARR-HDRC

RLP_OCT_RX_RTC_ RLP Octets Received on


CONV_PTT_SPCH_ Reverse Traffic Channels for
Conversational PTT Speech
CPS

(CPS)
SECT-CARR-HDRC

RL_RESV_ADMT_
CONV_PTT_
SPEECH

Number of RL Reservations
Admitted for Conversational
PTT Speech

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

8-46

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Table 8-9

Impacts on service measurements

HDR sector carrier service measurements

(continued)

Service measurement
subcategory

Count
abbreviation

Count name

SECT-CARR-HDRC

RL_RESV_ADMT_
FAIL_CONV_PTT_
SPCH_RL_BKHAUL_
RES

Number of RL reservation
admission failures for
Conversational PTT Speech due
to RL Backhaul Resource

SECT-CARR-HDRC

RL_RESV_ADMT_
FAIL_CONV_PTT_
SPCH_RL_RF_RES

Number of RL Reservation
admission failures for
Conversational PTT Speech due
to RL RF Resource

SECT-CARR-HDRC

RL_RESV_DRPD_
CONV_PTT_SPCH_
BKHAUL_OVL

Number of RL Conversational
PTT Speech Reservations
Dropped due to Backhaul
Overload

SECT-CARR-HDRC

RL_RESV_DRPD_
CONV_PTT_SPCH_
RL_RF_OVL

Number of RL Conversational
PTT Speech Reservations
Dropped due to RL RF Overload

SECT-CARR-HDRC

RL_RESV_DRPD_
CONV_PTT_SPCH_
TP_EF_Q_OVL

Number of RL Conversational
PTT Speech Reservations
Dropped due to TP EF Queue
Overload

SECT-CARR-HDRC

RL_RESV_REQ_
CONV_PTT_
SPEECH

Number of RL Reservations
Requested for Conversational
PTT Speech

HRPD PTT Paging Enhancements (FID 12184.5)

The HRPD PTT Paging Enhancements feature affects the following categories of
services measurements:

Overhead Manager (OHM)-PageableProfileID counts


Overhead Manager (OHM)-PageableProfileID-PageAttempt counts

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-47
Issue 5, May 2008
See notice on first page

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Impacts on service measurements

OHM-PageableProfileID service measurements

The HRPD PTT Paging Enhancements feature modify these existing the OHM-Profile
ID service measurements introduced by DOrA Application QoS Features identified in
Table 8-10, OHM-PageableProfileID service measurements (p. 8-48).
Table 8-10

OHM-PageableProfileID service measurements

Service measurement
subcategory

Count
abbreviation

Count name

OHM-PGPROFID

PAGE_ABORT_
HIGHER_PID

Page Aborts Due to Higher


Priority ProfileID Override

OHM-PGPROFID

PAGE_ESC

Paging Escalations

OHM-PageableProfileID-PageAttempt service measurements

The HRPD PTT Paging Enhancements feature modify these existing the OHM-Profile
ID service measurements introduced by DOrA Application QoS Features identified in
Table 8-11, OHM-PageableProfileID-PageAttempt service measurements (p. 8-48).
Table 8-11

OHM-PageableProfileID-PageAttempt service measurements

Service measurement
subcategory

Count
abbreviation

Count name

OHM-PGPROFID-PGAT

PAGES

Pages

OHM-PGPROFID-PGAT

PAGE_CR_RCVD

Connection Requests Received

PTT Enhancements (FID 12184.7)

The PTT Enhancements feature affects the following categories of services


measurements:

Overhead Manager (OHM)-PageableProfileID counts


Overhead Manager (OHM)-PageableProfileID-PageAttempt counts
RNC pgpf counts

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

8-48

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Impacts on service measurements

OHM-PageableProfileID service measurements

The HRPD PTT Paging Enhancements feature adds new counts to the
OHM-PageableProfileID service measurements introduced by DOrA Application QoS
Features are identified in Table 8-12, OHM-PageableProfileID service measurements
(p. 8-49).
Table 8-12

OHM-PageableProfileID service measurements

Service measurement
subcategory

Count
abbreviation

Count name

OHM-PGPROFID

PAGE_DE_ESC

Paging De-Escalations

OHM-PGPROFID

PAGE_DE_ESC_
RESP

Paging De-Escalation Responses

OHM-PGPROFID

PAGE_ESC_RESP

Paging Escalation Responses

OHM-PageableProfileID-PageAttempt service measurements

The HRPD PTT Paging Enhancements feature modifies this new and existing counts in
the OHM-PageableProfileID-PageAttempt service measurements introduced by DOrA
Application QoS Features are identified in Table 8-13, OHM-PageableProfileIDPageAttempt service measurements (p. 8-49).
Table 8-13

OHM-PageableProfileID-PageAttempt service measurements

Service measurement
subcategory

Count
abbreviation

Count name

PAGE_ESC

Paging Escalations

PAGE_SECTORS

Page Sectors

Existing Count

OHM-PGPROFID-PGAT
New Count

OHM-PGPROFID-PGAT

RNC-pgpf service measurements

The HRPD PTT Paging Enhancements feature adds new counts to the RNC-pgpf
service measurements introduced by DOrA Application QoS Features identified in
Table 8-14, RNC-pgpf service measurements (p. 8-49).
Table 8-14

RNC-pgpf service measurements

Service measurement
subcategory

Count
abbreviation

Count name

SN-RNC-pgpf

RNC_GROUP_ID

RNC Group ID

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-49
Issue 5, May 2008
See notice on first page

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Impacts on service measurements

References

For detailed information about service measurements, see

CDMA2000 1xEV-DO Network Service Measurements, 401-614-326

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

8-50

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Issues
and caveats
...................................................................................................................................................................................................................................
Introduction

The features described in this document are subject to the following special issues
and/or caveats.
Caveats

The PTT features will be delivered in several phases. The 1xEV-DO Basic PTT Using
1xEV-DO Rev. A Network (FID 12184.1), is the first feature available. It is using the
Multiflow Packet Application without header compression in order to work with the
first HRPD Rev. A ATs. The 1xEV-DO Basic PTT Using 1xEV-DO Rev. A Network
(FID 12184.1) feature integration with different PTT servers will be done based on
customer demands/configurations.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-51
Issue 5, May 2008
See notice on first page

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Implementing
the features
...................................................................................................................................................................................................................................
Process

This procedure activates the DOrA Application QoS Features and related features in a
CDMA2000 1xEV-DO Network.
For detailed procedure, see 401-614-101, CDMA2000 1xEV-DO Network Radio
Access System.
Implementing the DOrA Application QoS Features

The PTT features are optional features controlled by PTT FAF on Service Node basis.
The 1xEV-DO Basic PTT Using 1xEV-DO Rev. A Network (FID 12184.1) is
controlled by the PTT FAF per Service Node basis. The PTT FAF can be activated
only if the Enhanced HRPD Rev. A bundle FAF is activated.
These DOrA Application QoS Features are required for PTT:

Application Based Quality of Service (QoS) Support for HRPD Rev. A (FID
12078.9)
RAN Quality of Service Enhancements for HRPD Rev A (FID 12078.10)
More Quality of Service (QoS) Enhancements for the High Rate Packet Data
(HRPD) Revision A (Rev. A) Network (FID 12078.11)
Data over Signaling Protocol (FID 12078.12)
Enhanced Idle State Protocol (FID 12078.13)
1xEV-DO Basic Push-To-Talk (PTT) Using 1xEV-DO Rev. A Network (FID
12184.1)
High Rate Packet Data (HRPD) Push-to-Talk (PTT) Paging Enhancements (FID
12184.5)
Push-to-Talk (PTT) Enhancements (FID 12184.7)
1xEV-DO Revision A (Rev. A): Data Over Signaling Protocol - FL (FID 12078.36)

In addition to FAF control the operator will have the ability to turn the feature ON/OFF
on Service Node basis.
Operations and Maintenance Center - Radio Access Network (OMC-RAN) configuration
management

For more information about the different 1xEV-DO OA&M interfaces that are used in
performing OA&M tasks on the EV-DO controller and its managed resouces,
including the purpose of each interface and how to access it, see Alcatel-Lucent 9271
EV-DO Radio Network Controller, 401-614-102, Chapter 3, User Interfaces.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

8-52

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Implementing the features

See Appendix 7 of Alcatel-Lucent 9271 EV-DO Radio Network Controller,


401-614-102 for basic information in order to:

understand the OMC-RAN,


understand the layout of EV-DO information on the OMC-RAN, and
provisioning activities on EV-DO network and elements from the OMC-RAN.

Also see the About this information product at the beginning of this document for
the most commonly-used ways to find certain information on EMS and where to find
the equivalent information on the OMC-RAN, or CDMA2000 1xEV-DO
Configurations Parameters Guide, 401-614-324.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-53
Issue 5, May 2008
See notice on first page

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Activating
the feature
...................................................................................................................................................................................................................................
Purpose

Activation of the DOrA Application QoS Features depends on the 1xEV-DO Basic Rev.
A Feature Bundle, this means the 1xEV-DO Basic Rev. A Feature Bundle needs to be
activated before the activation of the DOrA Application QoS Features. In other words,
the DOrA Application QoS Features depend on the 1xEV-DO Basic Rev. A Feature
Bundle.
All the DOrA Application QoS Features are enabled by the DOrA Application
Licenses. The FAF entries for all of these features are now enabled in all customers
Feature Activation Files (FAF). FAFs are not used to manage ANY of these features.
The only FAF legacy situation exists is that the 12078.x series of FIDs has a single
FAF entry, while the 12184.x FIDs have separate entries. However, it is not the
mechanism to turn on these features - the DOrA Application Licenses are the
mechanism.
For detailed procedures, see CDMA2000 1xEV-DO Radio Access System Planning
and Implementation Guide, 401-614-101.
Procedure

Perform the following steps:


...................................................................................................................................................................................................

Ensure the correct FAF entry is activated.


Ask your account executive to activate the following entry in your Feature Activation
File (FAF):

FAF entry for FID 12078.9 and FID 12078.10 is


1xEV-DO Application based Quality of Service (QoS) support for HRPD
RevA (QOS_REVA). See Step 3.

FAF entry for FID 12078.11 is


1xEV-DO Application based Quality of Service (QoS) support for HRPD
RevA (QOS_REVA). See Step 4.

FAF entry for FID 12078.12 is


1xEV-DO Application based Quality of Service (QoS) support for HRPD
RevA (QOS_REVA). See Step 5.

Important!

The Enhanced Idle State Protocol (FID 12078.13) feature shares the
same FAF with FIDs 12078.9, 12078.10, and 12078.12 yet is not included in the
DOrA Application QoS Features application license applied features. To enabe FID
12078.13, see Step 6.
FAF entry for FID 12184.1 is
1xEV-DO Basic PTT using 1xEV-DO RevA Networks. See Step 7.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

8-54

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Activating the feature

FAF entry for FID 12184.5 is HRPD PTT Paging Enhancement (1xEV-DO RevA).
The FAF entry for FID 12184.5 requires the FAF entry for 1xEV-DO RNC
Grouping Infrastructure FID 12456.1. See Step 9.

There is no separate FAF entry for FID 12184.7. It uses the FID 12184.5 FAF
entry HRPD PTT Paging Enhancement (1xEV-DO RevA). See Step 10.
FAF entry for FID 12078.36 is HRPD PTT Paging Enhancement (1xEV-DO RevA).
See Step 11.

...................................................................................................................................................................................................

Go to EMS GUI Configuration Data Page and provision the required translations for
the corresponding feature.
...................................................................................................................................................................................................

For Application Based Quality of Service (QoS) Support for HRPD Rev. A (FID
12078.9) and RAN Quality of Service Enhancements for HRPD Rev A (FID
12078.10):
1. From EMS Configuration Data Page, click on Service Nodes.
2. Click on Service Node ID to provision, then click on General Section 3 from
the scroll box.
3. From the General Service Node Attributes - section 3 page, set Per Application
QOS feature Enable field to Enabled.
4. Click onSubmit at the bottom of the page.
...................................................................................................................................................................................................

For More Quality of Service (QoS) Enhancements for the High Rate Packet Data
(HRPD) Revision A (Rev. A) Network (FID 12078.11):
1. No new translations are required if FIDs 12078.9 and 12078.10 in Step 3 are
already provisioned.
...................................................................................................................................................................................................

For Data over Signaling Protocol (FID 12078.12):


1. From EMS GUI Configuration Data Page, click on Service Nodes.
2. Click on the Service Node ID to provision, then click on General Section 1 from
the scroll box.
3. From the General Service Node Attributes - section 1 Page, set Data Over
Signaling Enable field to Yes.
4. Go back to EMS GUI Configuration Data Page, click on Service Categories.
5. Click on Best Effort from the Service Categories Page.
6. Click on General from the scroll box.
7. Set AT originated DoS Message filed to Yes.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-55
Issue 5, May 2008
See notice on first page

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Activating the feature

8. Click on Submitat the bottom of the page.


9. Go back to Service Categories Page, repeat above sub-steps 5 through 8 to set AT
originated DoS Message filed to Yes for each of the following service categories:
Signaling Media Control, Conversational PTT Speech and Low Latency Media
Control Signaling
...................................................................................................................................................................................................

Important! The Enhanced Idle State Protocol (FID 12078.13) shares the same FAF
with FIDs 12078.9, 12078.10, and 12078.12 yet it is not included in the 1xEV-DO
Rev. A QoS application license applied features:
To enable Enhanced Idle State Protocol (FID 12078.13), proceed with the following:
1. Ensure the FAF entry of
1xEV-DO Application based Quality of Service (QoS) support for HRPD
RevA (QOS_REVA) is activated.

2. From EMS GUI Configuration Data Page, click on Service Nodes.


3. Click on the Service Node ID to provision, then click on Enhanced Idle State
Protocol from the scroll box.
4. From the Enhanced Idle State Protocol Page, set Enhanced Idle State Protocol
Enabled field to Yes.
5. Click on Submit at the bottom of the page.
...................................................................................................................................................................................................

For 1xEV-DO Basic Push-To-Talk (PTT) Using 1xEV-DO Rev. A Network (FID
12184.1):
1. From EMS GUI Configuration Data Page, click on Service Nodes.
2. Click on the Service Node ID to provision, then click on General Section 1 from
the scroll box.
3. From the General Service Node Attributes - section 1 Page, set Basic PTT
1xEV-DO Rev A Network Enable field to Yes.
4. Access Profile ID view under Configuration Data page, then go to General and
verify that appropriate Profile ID is Enabled
PTT CallSetup Signaling
PTT InCall Signaling
PTT Speech Bearer1
PTT Speech Bearer2
5. Go to the ProfileID Paging Strategy Attributes page and verify the
QoS ProfileID Value is the appropriate value. Repeat this step for each Profile
ID in 4.
6. Populate Use QoS Page Strategy to y

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

8-56

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Activating the feature

7. Configure Paging Areas on the ProfileID Paging Strategy Attributes page with
appropriate values.
The choices for QoS Paging areas:
Two basic paging areas: Last_Active_Set and Last_Seen_RNC
Need to enable FID 12184.5 (Step 9) for enhanced paging areas: Neighbor_RNC
and RNC_Group
Need to enable FID 12184.7 (Step 10) for distance based paging areas:
Distance_Tier0, Distance_Tier1, Distance_Tier2, Distance_Tier3
...................................................................................................................................................................................................

Important! RNC group is not present when RNC grouping FID is not turned on.
For 1xEV-DO Basic Push-To-Talk (PTT) Using 1xEV-DO Rev. A Network (FID
12184.1), the optionally configure the QoS Paging Strategy per RNC Group:
From EMS GUI Configuration Data Page, click on RNC Group Profile IDs.
Click on PTT CallSetUp Signaling for RNC Group ID.
Click on Paging Strategy General from the scroll box.
Set the Use QoS Page Strategy field to Yes.
Click on RNC Group QoS Paging Overridefield to Yes.
Click on Submit at the bottom of the page.
Click on Paging Strategy General from the scroll box.
Specify the DOS method and paging area for each attempt. For a list of valid
combinations for DoS method and paging area settings, see Table 8-15, Valid
Combinations for DoS Method and Paging Area Settings (p. 8-61).
If no DOS method is set, set the paging area field to any of the values listed in
Table 8-15, Valid Combinations for DoS Method and Paging Area Settings
(p. 8-61).
The choices for QoS Paging areas:
Two basic paging areas: Last_Active_Set and Last_Seen_RNC
Need to enable FID 12184.5 (Step 9) for enhanced paging areas: Neighbor_RNC
and RNC_Group
Need to enable FID 12184.7 (Step 10) for distance based paging areas:
Distance_Tier0, Distance_Tier1, Distance_Tier2, Distance_Tier3
9. Click on Submitat the bottom of the page.
10. Go back to the RNC Group Profile IDs page.
11. Repeat sub-steps 2 through 10 for each of the following Profile IDs.
PTT InCall Signaling
PTT Speech Bearer1
PTT Speech Bearer2

1.
2.
3.
4.
5.
6.
7.
8.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-57
Issue 5, May 2008
See notice on first page

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Activating the feature

Important!

The 1xEV-DO RNC Groups that include RNCs from different service
nodes should use the same settings for QoS Paging parameters in the Profile ID or
RNC Group Profile ID views. No cross-checking between service nodes is performed,
but if the settings are different, unexpected results can occur.
Important!

Distance Tiers should not be selected for QoS Paging Areas until all the
RNCs in an RNC Group have been upgraded to R29.0 or a later load. The operation of
distance-based paging may result in unexpected behavior when an RNC in an RNC
Group is not running 1xEV-DO R29.0 or a later RNC load.
...................................................................................................................................................................................................

Important! The FAF entry for FID 12184.5 requires the FAF entry for 1xEV-DO
RNC Grouping Infrastructure FID 12456.1. FID 12184.5 is a dependant feature of
FID 12456.1.
For High Rate Packet Data (HRPD) Push-to-Talk (PTT) Paging Enhancements (FID
12184.5):
1. From EMS GUI Configuration Data Page, click on Service Nodes II.
2. Click on the Service Node ID to provision, then click on General from the scroll
box.
3. From the Service Nodes II General Page, set Paging Enhancements Enable
field to Yes.
4. Click on Submit at the bottom of the page.
...................................................................................................................................................................................................

10

Important! There is no separate FAF entry for FID 12184.7. It uses the FID
12184.5 FAF entry HRPD PTT Paging Enhancement (1xEV-DO RevA).
For Push-to-Talk (PTT) Enhancements (FID 12184.7):
1. From EMS GUI Configuration Data Page, click on Service Nodes II.
2. Click on the Service Node ID to provision, then click on General from the scroll
box.
3. From the General Page, set Distance Paging Enable field to Yes. With
distance-based paging, a page is sent to all sectors within a radius of the last seen
sector. The distance between sectors is calculated from the provisioned Latitude
and/or Longitude of each sector. Only cells in RNCs in the same RNC group as the
session controlling RNC are paged. The paging radius is configureable.
4. Provision Distance_Tier0 settings:
Distance_Tier0 is based on the setting of the Radius for Registration Update
parameter. Provision this parameter at the Service Node level or at the Sector
Level.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

8-58

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Activating the feature

When the Radius for Registration Update parameter is set with a value at the
sector level, it overrides the setting at the service node level.
At the Service Node level, from the Configuration Data Page, click Service
Nodes. Select the ID to provision and then click General Section 1.
At the sector level, from the Configuration Data Page, click Sectors. Specify
values for BTS ID, Sector ID, Service Node ID and FMS Frame ID to filter for
the desired sector IDs. Select the Sector ID to provision, and then click
General.
5. Provision Distance_Tier1, Distance_Tier2, and Distance_Tier3 settings
The following caveats should be noted:
Do not turn on distance based paging unless all sectors have been correctly
provisioned with their latitude and longitude (in the sector view). Otherwise,
paging to sectors with incorrect positions may be affected.
For compatibility with geolocation services, it is recommend that latitude and
longitude be based on the World Geodetic Survey 1984 (WGS-84).
When entering the sizes of distance tiers, note that these are 2D distances based
on the equation from TIA-856-A-2 8.7.6.1.5.4 Route Update Report Rules. This
is NOT a 3D distance that includes the curvature of the earth.
If more than 250 pageable entities (cells or sectors with unique position) are
within the radius provisioned for a distance based tier, only the closest 250
pageable entities will actually be paged.
Distance_Tier1, Distance_Tier2, and Distance_Tier3 values are based on the
settings of the Size of Distance Paging Tier1,
Size of Distance Paging Tier2, and Size of Distance Paging Tier3
parameters, respectively. These parameters can be set at the Service Node, BTS,
and SectorLevels.
At the Service Node level, from the Configuration Data Page, click Service
Node II. Select the ID to provision and then click General.
At the BTS level, from the Configuration Data Page, click BTSs. Specify
values for BTS ID, Service Node ID and FMS Frame ID to filter for the
desired sector IDs. Select the BTS ID to provision, and then click General
Section 1.
At the Sector level, from the Configuration Data Page, click Sectors.
Specify values for BTS ID, Service Node ID and FMS Frame ID to filter for
the desired sector IDs. Select the Sector ID to provision, and then click
General.
The settings of these parameter take precedence in the following order:
a. settings in the Sector page
b. settings in the BTS page
c. settings in the Service Node page
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-59
Issue 5, May 2008
See notice on first page

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Activating the feature

Important!

The 1xEV-DO RNC Groups that include RNCs from different service
nodes should use the same setting for the Distance Paging Enable field. No
cross-checking between service nodes is performed, but if the settings are different,
unexpected results can occur.
...................................................................................................................................................................................................

11

For 1xEV-DO Revision A (Rev. A): Data Over Signaling Protocol - FL (FID
12078.36):
1. From EMS GUI Configuration Data Page, click on Service Nodes.
2. Click on the Service Node ID to provision, then click on General Section 1 from
the scroll box.
3. From the General Service Node Attributes - section 1 Page, set Data Over
Signaling Enable field to Yes.
4. Go back to EMS GUI Configuration Data Page, click on Profile IDs.
5. Click on PTT CallSetup Signaling from the Profile IDs Page.
6. Click on Data Over Signaling from the scroll box.
7. Set First DSCP marking for DoS request to useDoS.
8. Click on Submitat the bottom of the page.
9. Return to the Profile IDs screen.
10. Click on Paging Strategy Areas.
11. Set DoS Method For First Attempt to Direct_DOS, Mixed_DOS, or RUR_DOS.
Specify the DOS method and paging area for each attempt. Set the DoS Method
For First Attempt field to Direct_DOS, Mixed_DOS, or RUR_DOS, then specify a
value for the Paging Area For First Attempt field. For a list of valid combinations
for DoS method and paging area settings, see Table 8-15, Valid Combinations for
DoS Method and Paging Area Settings (p. 8-61).
If no DOS method is set, set the paging area field to any of the values listed in
Table 8-15, Valid Combinations for DoS Method and Paging Area Settings
(p. 8-61).
12. Click on Submitat the bottom of the page.
13. Repeat sub-steps 10 through 12 to configure settings for additional attempts;
configure up to eight attempts.
14. Go back to Profile ID Page, and repeat above sub-steps 5 through 12 to set AT
terminated DoS for each of the following Profile IDs: Best Effort, PTT call Setup
Signalling, PTT InCall Signalling, PTT speech Bearer1 and PTT Speech Bearer
2.
E...................................................................................................................................................................................................
ND OF STEPS

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

8-60

Enhanced Data Only Revision A (DOrA) Application


Quality of Service (QoS) Features

Activating the feature

DoS Method and Paging Area Settings

The Table 8-15, Valid Combinations for DoS Method and Paging Area Settings
(p. 8-61) lists the valid combinations of DoS Method and Paging Area settings. Valid
combinations are indicated by an X.
The choices for QoS Paging areas:

Two basic paging areas: Last_Active_Set and Last_Seen_RNC


Need to enable FID 12184.5 (Step 9) for enhanced paging areas: Neighbor_RNC
and RNC_Group
Need to enable FID 12184.7 (Step 10) for distance based paging areas:
Distance_Tier0, Distance_Tier1, Distance_Tier2, Distance_Tier3

Table 8-15

Valid Combinations for DoS Method and Paging Area Settings

Paging Area Setting

DoS Method setting


Null

Direct_
DoS

Last_Active_Set

Last_Seen_RNC

Mixed_
DoS

RURDoS

Basic Paging Areas

Enhanced Paging Areas


Neighbor_RNC1

RNC_Group

Distance Paging Areas


Distance_Tier02

Distance_Tier12

Distance_Tier2

Distance_Tier3

2
2

1. Specify Neighbor_RNC or RNC_Group only when FID12184.5 is enabled.


2. Specify Distance_Tier# only when FID 12184.7 is enabled.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-61
Issue 5, May 2008
See notice on first page

9 DMA 3G-1x EVolution Data


C
Optimized (1xEV-DO) Backhaul
w/Multi Link Point-to-Point
Protocol at Layer 2 Over T1/E1

Overview
...................................................................................................................................................................................................................................
Purpose

This optional feature description describes the CDMA 3G-1x EVolution Data
Optimized (1xEV-DO) Backhaul with Multi Link Point-to-Point Protocol (MLPPP) at
Layer 2 Over T1/E1 optional feature in CDMA 1xEV-DO networks.
Feature summary

The current data only (DO) backhaul over T1 uses Cisco HDLC (cHDLC) as layer 2
protocol. The EVolution Data Optimized (1xEV-DO) Backhaul with Multi Link
Point-to-Point Protocol (MLPPP) at Layer 2 Over T1/E feature replaces the cHDLC
with Multi Link Point-to-Point Protocol (MLPPP) as layer 2 protocol. Backhaul traffic
load-balance and Quality of Service (QoS) will be handled under MLPPP extension
protocol, which is IETF standard. The MLPPP protocol has been developed 3rd
Generation CDMA Internet Protocol Backhaul (3G1X IPBH) under program so that the
DO will reuse the developed protocol from the Base Transceiver Station (BTS). Edge
router in the DO backhaul should also support the MLPPP protocol.
Feature Identifier (FID)

A unique Feature Identifier (FID) is assigned to each feature. The FID of the CDMA
3G-1x EVolution Data Optimized (1xEV-DO) Backhaul with Multi Link Point-to-Point
Protocol (MLPPP) at Layer 2 Over T1/E1 feature is FID 12304.11.

....................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
9-1
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Backhaul w/Multi Link Point-to-Point Protocol at Layer 2
Over T1/E1

Overview

Impacts on user interfaces

The CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Backhaul with Multi Link
Point-to-Point Protocol (MLPPP) at Layer 2 Over T1/E1 affects the user interfaces that
are listed in the following table.
User interface

Feature impact

Element Management System (EMS) (or


OMC-RAN)

See Element Management System (EMS)


configuration management (p. 9-10).

Service measurements

See Impacts on service measurements


(p. 9-11).

Automatic Message Accounting (AMA)


subsystem

None

Technician Interface (TI) (input/output


messages)

None

Intended audience

This document is intended for technicians, engineers, and system administrators who
implement or maintain the 1xEV-DO Backhaul with MLPPP at Layer 2 Over T1/E1
feature in a CDMA2000 1xEV-DO network.
To obtain technical support, documentation, and training or submit feedback

The Online Customer Support (OLCS) web site (http://support.lucent.com/) provides


access to technical support, related documentation, related training, and feedback tools.
The site also provides account registration for new users.
Contents
Availability

9-4

Prerequisites

9-5

Feature description

9-6

Feature interactions

9-9

Element Management System (EMS) configuration management

9-10

Impacts on service measurements

9-11

Issues and caveats

9-12

Implementing the feature

9-13

Activating the feature

9-14

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

9-2

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Backhaul w/Multi Link Point-to-Point Protocol at Layer 2
Over T1/E1

Provisioning cell2 RC/V form

Overview

9-15

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
9-3
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Backhaul w/Multi Link Point-to-Point Protocol at Layer 2
Over T1/E1

Availability
...................................................................................................................................................................................................................................
Release availability

The 1xEV-DO Backhaul with MLPPP at Layer 2 Over T1/E1 feature is available in
ECP Releases 28.0 and later.
Market availability

The 1xEV-DO Backhaul with MLPPP at Layer 2 Over T1/E1 feature is available in the
North American Region (NAR) market only.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

9-4

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Backhaul w/Multi Link Point-to-Point Protocol at Layer 2
Over T1/E1

Prerequisites
...................................................................................................................................................................................................................................
Introduction

The 1xEV-DO Backhaul with MLPPP at Layer 2 Over T1/E1 feature has the following
prerequisites.
Supported technologies

The 1xEV-DO Backhaul with MLPPP at Layer 2 Over T1/E1 feature is supported in
the following air-interface technologies:

CDMA cellular
CDMA PCS

Software requirements

The 1xEV-DO Backhaul with MLPPP at Layer 2 Over T1/E1 feature requires ECP
Release 28.0 or later. The 1xEV-DO Backhaul with MLPPP at Layer 2 Over T1/E1
feature is not dependent on other features.
Hardware requirements

The 1xEV-DO Backhaul with MLPPP at Layer 2 Over T1/E1 feature requires the edge
router supporting MLPPP/Multi Carrier (MC) protocol instead of HDLC. As network
control protocol, Dynamic Host Configuration Protocol (DHCP) will continue
supporting to assign BTS IP address.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
9-5
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Backhaul w/Multi Link Point-to-Point Protocol at Layer 2
Over T1/E1

Feature
description
...................................................................................................................................................................................................................................
Introduction

The following information describes the functionality, benefits, and operation of the
CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Backhaul with Multi Link
Point-to-Point Protocol (MLPPP) at Layer 2 Over T1/E1 feature.
Functionality

The CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Backhaul with Multi Link
Point-to-Point Protocol (MLPPP) at Layer 2 Over T1/E1 feature replaces the cHDLC
with Multi Link Point-toPoint Protocol (MLPPP) as layer 2 protocol. Backhaul traffic
load-balance and Quality of Service (QoS) will be handled under MLPPP extension
protocol, which is IETF standard.
How the feature operates

Since the current Edge router is configured as cHDLC in layer 2 protocol, the CDMA
3G-1x EVolution Data Optimized (1xEV-DO) Backhaul with Multi Link Point-to-Point
Protocol (MLPPP) at Layer 2 Over T1/E1 feature allows it to be reconfigured with
MLPPP. A significant difference from the cHDLC based backhaul is that one IP
address is assigned to a Multi-Link bundling multiple T1s. The current backhaul over
cHDLC link assigns IP address per T1 link. The MLPPP will provide equivalent or
additional functions to the current cHDLC protocol as follows:

Link continuity verification: MLPPP provides Link Control Protocol (LCP)

message as L2HB

Traffic Load balance within the MLG: MLPPP backhaul also provides the traffic
load balance across T1s within the same Multi-Link Group (MLG) over Forward
Link as well as Reverse Link.

As illustrated in Figure 9-1, EVDO Network Configuration Diagram with a MLPPP


(p. 9-7), the EVDO backhaul will require reconfiguration in the backhaul network
including BTS, Data Only Radio Network Controller (DO RNC) and the aggregation
routers.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

9-6

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Backhaul w/Multi Link Point-to-Point Protocol at Layer 2
Over T1/E1

Feature description

Figure 9-1 EVDO Network Configuration Diagram with a MLPPP

As part of reconfiguration at the BTS, the following are required:

MLG configuration: All T1s at the same Universal Radio Controller (URC) must

be provisioned into the same MLG. Multi-Router Automatic Protection Switching


(MR-APS) should be supported to perform the MLG switch-over in case of router
failure. Under the 1xEV-DO Backhaul with MLPPP at Layer 2 Over T1/E1 feature,
EVDO backhaul supports single MLG configurations only.
IP Address provisioning at the Aggregation Router: As part of MLPPP
connection setup procedure, BTS will receive the IP address via IPCP. The
aggregation router should provision the IP address pool that will be used for the IP
address allocation to the BTS. In order to support for the MR-APS, both
aggregation routers should maintain the same IP address pool
QoS parameters configuration based on DiffServ: DiffServ is the QoS protocol
used in EVDO backhaul. Since the MLPPP will bundle multiple T1s QoS
parameters should be reconfigured based on MLG.

When the layer 2 protocol of EVDO Rev. A backhaul is converted from cHDLC to
MLPPP, base station and edge router should be reconfigured to support MLPPP.
Protocol conversion from cHDLC to MLPPP will be completed without the cellsite
visit. According to the transport network design, T1 lines may need to be
re-provisioned into the same multilink. URC will be rebooted as part of the protocol
conversion.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
9-7
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Backhaul w/Multi Link Point-to-Point Protocol at Layer 2
Over T1/E1

Feature description

The EVDO cell will use IPCP to receive the basic IP addresses including BTS IP
address. When the MLPPP connection is established, it will receive further information
for the operation from the DHCP server. In addition, upon the increase of link
bandwidth assigned on an IP address, backhaul transport QoS parameters and traffic
engineering might be reconfigured at BTS, RNC and Edge router.
Since MLPPP uses different type of backhaul continuity verification methods defined
as part of standard (RFC-1661), instead of SLARP message under cHDLC protocol,
Link Control Protocol (LCP) Echo request and response messages are periodically
exchanged between the BTS and the Edge router. MLPPP also provides a new alarm
upon the loss of the whole MLG member links.
Loss of each T1 link will not turn on the alarm in MLPPP if there is at least another
T1 operating. All existing Service Measurement will continue to be supported over
MLPPP.
Service-provider perspective

The 1xEV-DO Backhaul with MLPPP at Layer 2 Over T1/E1 feature allows the
protocol conversion from cHDLC to MLPPP, or from MLPPP to cHDLC completion
does not require a cellsite visit.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

9-8

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Backhaul w/Multi Link Point-to-Point Protocol at Layer 2
Over T1/E1

Feature
interactions
...................................................................................................................................................................................................................................
Introduction

The 1xEV-DO Backhaul with MLPPP at Layer 2 Over T1/E1 feature does not interact
with other features.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
9-9
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Backhaul w/Multi Link Point-to-Point Protocol at Layer 2
Over T1/E1

Element
Management System (EMS) configuration management
...................................................................................................................................................................................................................................
Configuration management pages

The 1xEV-DO Backhaul with MLPPP at Layer 2 Over T1/E1 feature affects the Recent
Change and Verify (RC/V) forms that are listed in Table 9-1, Related RC/V forms
(p. 9-10).
Table 9-1

Related RC/V forms

Form abbreviation

Form name

SERIES 2 CELL

cell2

cell2 page

The cell2 form is used. The 1xEV-DO Backhaul with MLPPP at Layer 2 Over T1/E1
feature uses a new fields in the cell2 form, as shown in Table 9-2, Related fields in
the cell2 page (p. 9-10).
Table 9-2

Related fields in the cell2 page

Parameter name

Description

Allowed
values

MP Enabled

This parameter is used to indicate whether


MP is used layer 2 protocol on the
backhaul of the cell.

y or n

Default = n

References

For more information about these RC/V forms and fields, see the following
CDMA2000 wireless networks documents:

Database Update Manual, 401-610-036


Text Recent Change and Verify (RC/V) Reference, 401-610-038

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

9-10

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Backhaul w/Multi Link Point-to-Point Protocol at Layer 2
Over T1/E1

Impacts
on service measurements
...................................................................................................................................................................................................................................
Introduction

The 1xEV-DO Backhaul with MLPPP at Layer 2 Over T1/E1 feature affects the
following categories of services measurements:

Data link counts

Data link counts

The 1xEV-DO Backhaul with MLPPP at Layer 2 Over T1/E1 feature affects the
1xEV-DO service measurements that are identified in Table 9-3, 1xEV-DO service
measurements - Data link counts (p. 9-11).
Table 9-3

1xEV-DO service measurements - Data link counts

Count abbreviation

Count name

DL_UPLINK_AVG_THRUPUT

Datalink Uplink with Average Throughput

DL_UPLINK_PEAK_THRUPUT

Datalink Uplink with Peak Throughput

DL_DOWNLINK_AVG_THRUPUT

Datalink Downlink with Average


Throughput

DL_DOWNLINK_PEAK_THRUPUT

Datalink Downlink with Peak Throughput

References

For detailed information about 1xEV-DO service measurements, see CDMA2000


1xEV-DO Service Measurements, , 401-614-326.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
9-11
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Backhaul w/Multi Link Point-to-Point Protocol at Layer 2
Over T1/E1

Issues
and caveats
...................................................................................................................................................................................................................................
Introduction

The 1xEV-DO Backhaul with MLPPP at Layer 2 Over T1/E1 feature is subject to the
following special issues and/or caveats.
Caveats

Mixture configuration of EVDO Revision 0 (Rev. 0) and Revision A (Rev. A) is


supported over a single MLPPP protocol in either a single URC or multiple URCs
configuration. Mixture of 3G1X and EVDO allows different L2 protocols (for example,
FR PP and MLPPP).
The 3G1X IP BH uses IPCP as NCP under MLPPP/MC as layer 2 protocol. Since
EVDO has been used the DHCP as NCP and is used in Ethernet backhaul, EVDO
continues to use DHCP as NCP in addition to IPCP. The following is a typical scenario
regarding IP address assignment: When the EVDO URC boots, it will initially get the
IP address via IPCP, and connect to the BSSA. To get these addresses, it sends a
DHCP request. The response provides these addresses, including the address of the
BSSA.
The LU-EVDO-MLPPP continues to support only Shared Signaling. This means that IP
Signaling continues to be a non-supported setup, even after the change to MLPPP.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

9-12

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Backhaul w/Multi Link Point-to-Point Protocol at Layer 2
Over T1/E1

Implementing
the feature
...................................................................................................................................................................................................................................
Overview

To implement the 1xEV-DO Backhaul with MLPPP at Layer 2 Over T1/E1 feature,
perform the following procedures in sequence:
Implementing the feature (p. 9-13)
Provisioning cell2 RC/V form (p. 9-15)

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
9-13
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Backhaul w/Multi Link Point-to-Point Protocol at Layer 2
Over T1/E1

Activating
the feature
...................................................................................................................................................................................................................................
Purpose

This 1xEV-DO Backhaul with MLPPP at Layer 2 Over T1/E1 feature is a standard
feature that is not controlled by Feature Activation File/Quality Feature Activation File
(FAF/QFAF). In order to enable this feature per cell site, the customer should provision
the RC/V form for a particular cell site.
For details on DOMLPPP conversion, see CDMA Wireless Networks BTS Conversion
from HDLC to ML-PPP over T1/E1, 401-710-104.
For detailed procedures, see CDMA2000 1xEV-DO Radio Access System Planning
and Implementation Guide, 401-614-101.
For detailed procedures regarding the impact of OMC-RAN becoming a mandatory
platform for EV-DO in R29.1 and later, see Appendix 7 of Alcatel-Lucent 9271 EV-DO
Radio Network Controller, 401-614-102.
Procedure

Perform the following steps:


...................................................................................................................................................................................................

Proceed to Provisioning cell2 RC/V form (p. 9-15).


END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

9-14

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Backhaul w/Multi Link Point-to-Point Protocol at Layer 2
Over T1/E1

Provisioning
cell2 RC/V form
...................................................................................................................................................................................................................................
Purpose

This procedure provisions the RC/V cell2 form for the 1xEV-DO Backhaul with
MLPPP at Layer 2 Over T1/E1 feature.
Fields to populate

The fields that you must populate in the cell2 form are described in Table 9-4,
Fields to be populated in the cell2 form (p. 9-15).
Table 9-4

Fields to be populated in the cell2 form

Field name

Text RC/V
name

Value to
be
entered

MP Enabled

mp_enabled

y or n

Default =
n

Restrictions
When updating this
field, a warning
message will populate:
MP Enabled is a
non-updatable
parameter. Any change
must be followed by a
stable clear. It will
affect service.

Steps

Perform the following steps:


...................................................................................................................................................................................................

Launch the RC/V cell2 form.


...................................................................................................................................................................................................

Advance to the screen that contains the MP Enabled field.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
9-15
Issue 5, May 2008
See notice on first page

CDMA 3G-1x EVolution Data Optimized (1xEV-DO)


Backhaul w/Multi Link Point-to-Point Protocol at Layer 2
Over T1/E1

Provisioning cell2 RC/V form

Result: The cell2 form is displayed, as shown in the following example. In this

example, fields that relate to the 1xEV-DO Backhaul with MLPPP at Layer 2 Over
T1/E1 feature are in italics in Figure 9-2, RC/V form cell2 (p. 9-16).
Figure 9-2 RC/V form cell2
FLEXENT
Wireless
Networks

SERIES 2 CELL (cell2)


Screen 35 of 38
Cell ___
IP/Ethernet Backhaul Information
Ethernet Backhaul Enabled...........................@488) n

IP Backhaul Enabled.................................@489) n
Backhaul Offload.....................................490) n
Prim
Alt
RNC Number..............................491) __
496) __
RNC Backhaul Server Number..............492) _
497) _
Switching Module Number (SM)............493) ___
498) ___
Packet Switching Unit Number (PSU)......494) _
499) _
DCS Backhaul Server Number..............495) __
500) __
MLG Loading Bias Translation (BIASMLG)...............501) 0
Enable MLG Sharing for Bearer Traffic................502) n
MP Enabled..........................................@503) n
Subnetwork ID....................................505) ___.___.___.___
Network Mask.....................................510) ___.___.___.___
Default Gateway..................................515) ___.___.___.___

...................................................................................................................................................................................................

In the MP Enabled field, enter


n
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

9-16

10

10
EVolution
Data Only
(1xEV-DO) Revision A (Rev. A)
Voice Over Internet Protocol
(VoIP) and Application Pricing

Overview
...................................................................................................................................................................................................................................
Purpose

This optional feature description describes the EVolution Data Only (1xEV-DO)
Revision A (Rev. A) Voice Over Internet Protocol (VoIP) and Application Pricing and
related optional features in the CDMA2000 1xEV-DO networks.
Feature Identifier (FID)

A unique Feature Identifier (FID) is assigned to each feature:

1xEV-DO Rev. A VoIP and Application Pricing (FID 12905.0)


1xEV-DO Rev A Application Pricing Enhancements (FID 12905.1)

Feature summary
1xEV-DO Rev. A VoIP and Application Pricing (FID 12905.0)

The 1xEV-DO Rev. A VoIP and Application Pricing optional feature introduces a
mechanism for pricing the Radio Access Network (RAN) software that supports Voice
Over Internet Protocol (VoIP), Push-to-Talk (PTT) and other applications which require
unique Quality of Service (QoS) treatment over the High Rate Packet Data Revision A
Radio Access Network (RHRPD Rev. A RAN). This mechanism allows the customer to
pay for QoS applications as demand grows in a similar fashion as in circuit voice. This
feature is introduced corresponding to the Pay As You Grow initiative, allowing a
more attractive pricing option to be offered to the operator for initial deployment. At
initial deployment, the capacity need typically is low. As the capacity demand grows,
the operator can purchase more capacity in step with the growth of its revenue.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
10-1
Issue 5, May 2008
See notice on first page

EVolution Data Only (1xEV-DO) Revision A (Rev. A)


Voice Over Internet Protocol (VoIP) and Application
Pricing

Overview

1xEV-DO Rev A Application Pricing Enhancements (FID 12905.1)

The 1xEV-DO Rev A Application Pricing Enhancements feature is for incorporating


application license key functionalists that were descoped from FID 12905.0 due to
resource constraints. The functionality includes:

generation of a license installation token


providing a special license usage service measurements log
migrating AP base application license into FID 12905.0 infrastructure

Impacts on user interfaces

The 1xEV-DO Rev. A VoIP and Application Pricing and related features affect the user
interfaces that are listed in the following table.
Feature Name

User interface

Feature impact

1xEV-DO Rev. A VoIP and


Application Pricing (FID
12905.0)

Element Management
System (EMS) or
Operations and
Maintenance Center Radio Access Network
(OMC-RAN)

None

Service measurements

See Impacts on service


measurements: 1xEV-DO
Rev. A VoIP and
Application Pricing (FID
12905.0) (p. 10-20).

Automatic Message
Accounting (AMA)
subsystem

None

Technician Interface (TI)


(input/output messages)

None

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

10-2

EVolution Data Only (1xEV-DO) Revision A (Rev. A)


Voice Over Internet Protocol (VoIP) and Application
Pricing

Overview

Feature Name

User interface

Feature impact

1xEV-DO Rev A
Application Pricing
Enhancements (FID
12905.1)

Element Management
System (EMS) or
Operations and
Maintenance Center Radio Access Network
(OMC-RAN)

None

Service measurements

None

Automatic Message
Accounting (AMA)
subsystem

None

Technician Interface (TI)


(input/output messages)

None

Intended audience

This document is intended for technicians, engineers, and system administrators who
implement or maintain the 1xEV-DO Rev. A VoIP and Application Pricing optional
feature in a CDMA2000 1xEV-DO network.
To obtain technical support, documentation, and training or submit feedback

The Online Customer Support (OLCS) web site (http://support.lucent.com/) provides


access to technical support, related documentation, related training, and feedback tools.
The site also provides account registration for new users.
Contents
Availability

10-5

Prerequisites

10-6

Feature description: 1xEV-DO Rev. A VoIP and Application Pricing (FID


12905.0)

10-7

Feature description: 1xEV-DO Rev A Application Pricing Enhancements


(FID 12905.1)

10-13

Feature interactions: 1xEV-DO Rev. A VoIP and Application Pricing


(FID 12905.0)

10-17

Feature interactions: 1xEV-DO Rev A Application Pricing Enhancements


(FID 12905.1)

10-19

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
10-3
Issue 5, May 2008
See notice on first page

EVolution Data Only (1xEV-DO) Revision A (Rev. A)


Voice Over Internet Protocol (VoIP) and Application
Pricing

Overview

Impacts on service measurements: 1xEV-DO Rev. A VoIP and


Application Pricing (FID 12905.0)

10-20

Impacts on service measurements: 1xEV-DO Rev A Application Pricing


Enhancements (FID 12905.1)

10-23

License Key Installation

10-24

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

10-4

EVolution Data Only (1xEV-DO) Revision A (Rev. A)


Voice Over Internet Protocol (VoIP) and Application
Pricing

Availability
...................................................................................................................................................................................................................................
Release availability

The 1xEV-DO Rev. A VoIP and Application Pricing and related optional features are
available in:

1xEV-DO Rev. A VoIP and Application Pricing (FID 12905.0) - Releases 28.0 and
later.
1xEV-DO Rev. A Application Pricing Enhancements (FID 12905.1) - Releases 29.0
and later.

Market availability

The 1xEV-DO Rev. A VoIP and Application Pricing and related optional features are
available in the North American Region (NAR) market only.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
10-5
Issue 5, May 2008
See notice on first page

EVolution Data Only (1xEV-DO) Revision A (Rev. A)


Voice Over Internet Protocol (VoIP) and Application
Pricing

Prerequisites
...................................................................................................................................................................................................................................
Introduction

The 1xEV-DO Rev. A VoIP and Application Pricing and related optional features have
the following prerequisites.
Supported technologies

The 1xEV-DO Rev. A VoIP and Application Pricing and related optional features are
supported in the following air-interface technologies:

CDMA cellular
CDMA PCS

HLR configuration

The 1xEV-DO Rev. A VoIP and Application Pricing and related optional features are
supported by both the Integrated Home Location Register (IHLR) configuration and the
Stand-alone Home Location Register (SHLR) configuration.
Software requirements

The 1xEV-DO Rev. A VoIP and Application Pricing optional feature requires ECP
Release 28.0 or later. The 1xEV-DO Rev. A VoIP and Application Pricing optional
feature is dependent on:

Application Based Quality of Service (QoS) Support for HRPD Rev. A (FID
12078.9)

The 1xEV-DO Rev. A Application Pricing Enhancements (FID 12905.1) optional


feature requires ECP Releases 29.0 and later. The 1xEV-DO Rev. A Application Pricing
Enhancements optional feature is dependent on:

Application Based Quality of Service (QoS) Support for HRPD Rev. A (FID
12078.9)
1xEV-DO Rev. A VoIP and Application Pricing (FID 12905.0)

Hardware requirements

The 1xEV-DO Rev. A VoIP and Application Pricing and related optional features
require no hardware beyond the standard hardware in a CDMA2000 1xEV-DO
network.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

10-6

EVolution Data Only (1xEV-DO) Revision A (Rev. A)


Voice Over Internet Protocol (VoIP) and Application
Pricing

Feature description: 1xEV-DO Rev. A VoIP and Application


Pricing
(FID 12905.0)
...................................................................................................................................................................................................................................
Introduction

The following information describes the functionality, benefits, and operation of the
1xEV-DO Rev. A VoIP and Application Pricing (FID 12905.0) optional feature.
Functionality

The 1xEV-DO Rev. A VoIP and Application Pricing (FID 12905.0) optional feature
provides a generic license key mechanism that can be used to support new and existing
license keys with little or no change to the infrastructure. The license key mechanism
includes a license key generator, license key processing functionality on the RNC, and
license key management capabilities on Element Management System (EMS),
Operations and Maintenance Center/Radio Access Network (OMC/RAN) and
Operations and Maintenance Platform for Flexent (OMP-FX). The license key
generator is for generating software license keys to unlock various resources on an
RNC or BTS and for decoding protected data. The OMP-FX provide the license key
management capabilities such as installing license key, query license key status and
generating license key request form. The RNC application will be responsible for
validating and maintaining license keys, enforce license limit and report problems. The
1xEV-DO Rev. A VoIP and Application Pricing optional feature will support the
following license types. The 1xEV-DO Rev. A VoIP and Application Pricing
Enhancements optional feature introduces AP base application software:

Basic Rev A bundle carrier by FID 12078.2


Generic QoS application new in FID 12905.0
RNC VoIP application new in FID 12905.0
RNC PTT application new in FID 12905.0
RNC Video application new in FID 12905.0
BTS application EQU new in FID 12905.0
AP base application software new in FID 12905.1

The main motivation for using a license key mechanism is to address issues with the
optional FAFable optional feature approach.
The 1xEV-DO Rev. A VoIP and Application Pricing and related optional features have
no feature control FAF or QFAF.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
10-7
Issue 5, May 2008
See notice on first page

EVolution Data Only (1xEV-DO) Revision A (Rev. A)


Voice Over Internet Protocol (VoIP) and Application
Pricing

Feature description: 1xEV-DO Rev. A VoIP and


Application Pricing (FID 12905.0)

Benefits

The 1xEV-DO Rev. A VoIP and Application Pricing and related optional features
introduce a new pricing mechanism for QoS/VoIP applications, supporting the Pay As
You Grow initiative that allows a more attractive pricing option for the service
providers, particularly during the initial deployment phase.
The addresses the critical issue of ensuring technical support receive an ongoing
revenue stream from VoIP analogous to the current revenue stream for 1X circuit
voice. The 1xEV-DO Rev. A VoIP and Application Pricing and related optional features
provide a mechanism for charging applications which requires special QoS treatment in
the HRPD Rev A RAN. This pricing mechanism will supplement the Rev A License
Fee introduced in Enhanced Reverse and Forward Links using Enhanced MAC
Protocols with Rev. A Subtype 2 Physical Layer (FID 12078.2) for the basic Rev A
feature bundle.
How the feature operates

The right to use VoIP, PTT and other QoS based applications over HRPD Rev A RAN
are provided by technical support in the form of RNC and BTS license fees referred to
as Rev. A RAN Application License Fees. This pricing applies to customers who wish
to purchase advanced Rev. A capabilities on top of the basic Rev. A functionality to
transport QoS applications over their HRPD Rev. A RAN. These advanced capabilities
include, but are not limited to, per application QoS, Data Over Signaling, Enhanced
Idle State and Enhanced Multi-Flow Packet Application. This pricing will supplement
the per-subscriber VoIP application pricing defined for the FS5000 Telephony
Application Server (TAS) and associated IP Multimedia Subsystem Telephony
Application Server (IMS TAS) client software, as well as the client/server pricing
structure established for any other application. Customers purchasing the end-to-end
VoIP solution will be charged both the VoIP over HRPD Rev. A pricing, in addition to
the per-subscriber FS5000 VoIP application pricing and any other VoIP-related software
on any IMS or core network elements.
This QoS pricing mechanism over the Rev. A RAN introduces new software licensing
capabilities. The license Keys will contain information such as the number of QoS
application sessions allowed, number of allowed QoS Units per BTS, RNC ID, etc.
that are necessary to enable the purchased application or resources on the appropriate
network elements in the customer network. The license keys will be created and
delivered to customers the same way as for Rev. A license key. Two types of software
licenses will be introduced as part of this feature:

Radio Network Controller (RNC) Application License: to allocate capacity on a


RNC to support application sessions with unique QoS treatment
Base Transceiver Station (BTS) Application License: to allocate capacity on a
BTS to support application sessions with unique QoS treatment

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

10-8

EVolution Data Only (1xEV-DO) Revision A (Rev. A)


Voice Over Internet Protocol (VoIP) and Application
Pricing

Feature description: 1xEV-DO Rev. A VoIP and


Application Pricing (FID 12905.0)

Both Licenses are needed for any QoS application to be granted by the RNC.
RNC Application License

The RNC Application License Key is on a per RNC basis and will include the number
of licenses in each QoS service category. The quantity of licenses used are counted by
the number of open reservations in a QoS service category. One license is counted for
each pair of open reservation in forward and reverse directions for each QoS ProfileID.
For a given application, if a reservation is opened in only one direction (the other
closed or not required), one license is counted. The service category supported in this
feature will include the one in Application Based Quality of Service (QoS) Support for
HRPD Rev. A (FID 12078.9) (conversational speech and video) and DOrA Application
QoS Features (PTT) features. Additional service categories will be introduced in
subsequent releases.
Customers pay an incremental fee for each open reservation in a QoS service category
such as conversational speech (VoIP), conversational video (real time video), etc. Any
combination of open reservations in unique QoS service categories is allowed (for
example 1000 simultaneous VoIP sessions plus 100 simultaneous video sessions, etc.)
up to the engineering limits defined for the RNC. For applications such as video
telephony, which utilize flows in different QoS service categories (for example
conversational speech and conversational video), customers must purchase support for
the appropriate number of open reservations in both of the QoS service categories (for
example to support 100 video telephony sessions, customer must purchase support for
100 conversational speech open reservations and 100 conversational video open
reservations).
Alternatively, for customers with a very uncertain traffic mix, the RNC Application
Licensing mechanism does support purchasing a specific number of generic
reservations which can be used for any application on any QoS service category.
However, the customer must purchase either a number of reservations of each QoS
service category that are simultaneously supported on a RNC or a number of generic
reservations that can be used for any applications (mixed case is not supported). It is
indicated that the price of a generic reservation will be higher than certain reservations
and lower than others (for example the price of a generic reservation will be higher
than the price of a VoIP reservation and lower than a Video reservation). The pricing
for these different types of applications/reservations is beyond the scope of this feature.
The RNC application will check the license usage whenever a new reservation for QoS
flow(s) is requested from the Access Terminal (AT). The RNC will maintain an active
reservation count for each QoS service category. If the active reservation count is less
than the licensed quantity, the new reservation request will be granted (subject to the
QoS admission control mechanism introduced in Application Based Quality of Service
(QoS) Support for HRPD Rev. A (FID 12078.9) to check if there is enough Radio
Frequency (RF) and backhaul resources before accepting a new reservation.
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
10-9
Issue 5, May 2008
See notice on first page

EVolution Data Only (1xEV-DO) Revision A (Rev. A)


Voice Over Internet Protocol (VoIP) and Application
Pricing

Feature description: 1xEV-DO Rev. A VoIP and


Application Pricing (FID 12905.0)

If not, warning messages will be displayed as the purchased capacity for QoS
applications is reached and a grace period is initiated:

Once a grace period is started, new reservations will continue to be granted up to


the physical limitations of the system.
Once the grace period expires, new reservations in excess of the license limit will
be rejected.
The duration of the grace period is currently under consideration. It is believed that
the grace period will be in the length of hours. The final value will be shared with
customers during the request of the License Key.
Once started, a grace period can be terminated by obtaining a new license, that
increases the license limit, or by obtaining a grace period emergency override from
technical support.

BTS Application License

It is based on the portion of a Rev A carrier that is allocated for applications which
require unique QoS treatment.
The BTS application license implementation will be based on an Equivalent QoS Unit
(EQU) method. EQU is an equivalent measure of carrier resources that are required to
support a QoS Profile ID. For convenience, the EQU is normalized to the resource
required to support a VoIP call, such as one EQU is needed for each VoIP call. Other
applications, such as video telephony will require multiple EQUs to support a single
video telephony call. For example, a conversational video (40 kbps) may use four
times the resources of a VoIP call and therefore requires four EQUs. Note that a VoIP
call corresponds to a call made using EM-FPA and ROHC. For a VoIP call made with
MFPA (ROHC is not used) more than one EQU is needed
Customers pay an incremental fee for each QoS Unit used. Customer can purchase a
number of QoS Units per BTS up to the defined engineering limits. These units of
QoS capacity can be used by any QoS sensitive application such as VoIP, PTT and
video telephony. The BTS Application License will include the total allowed QoS
Units per BTS.
The BTS application license is sold in total EQUs for a BTS regardless of the
application type. The total is an aggregate of EQU for individual open reservation pair
(counted once for symmetric application) or reservation (for asymmetric application).
The RNC will maintain a total count of QoS Units used by all active QoS reservations
for each BTS (this apply to all Rev A carriers supported in a BTS, such as, no Rev 0
carriers, as QoS is not supported over Rev 0). When a new reservation is requested
from the AT, the RNC will convert the requested QoS Profile ID to QoS Units and

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

10-10

EVolution Data Only (1xEV-DO) Revision A (Rev. A)


Voice Over Internet Protocol (VoIP) and Application
Pricing

Feature description: 1xEV-DO Rev. A VoIP and


Application Pricing (FID 12905.0)

accept or reject the new request based on the total QoS Units count. Once the number
of purchased EQUs is fully utilized, warning message will be displayed as the
purchased capacity for QoS applications is reached and a grace period is initiated:

Once a grace period is started, new reservations will continue to be granted up to


the physical limitations of the system.
Once the grace period expires, new reservations in excess of the license limit will
be rejected.
Once started, a grace period can be terminated by obtaining a new license, that
increases the license limit, or by obtaining a grace period emergency override from
technical support.

As mentioned previously a grace period will be implemented to allow temporary


overruns of the RNC and/or BTS license limits. During this grace period, the BTS and
RNC will handle QoS traffic (such as VoIP, PTT, video telephony) in any combination
up to the capacity limits of the hardware purchased. During grace period, the customer
must contact technical support and request one of the following actions:

Purchase additional RNC and/or BTS licenses to prevent a future overrun.


Obtain an emergency override license key to extend the grace period until a
specific date to address a onetime emergency situation. This request will be
processed with equal urgency to a severity 1 service affecting outage.

If the customers takes one of these two actions within the grace period, the grace
period will be reset and restarted in the event of the next overrun.
If the customer takes no action within the grace period, and when the grace period
expires the system will enforce the purchased RNC and BTS license limits as hard
limits.
Warning messages will instruct the customer on the action to be taken.
Service Measurements

A set of service measurements related to the RNC and BTS application licenses usage
will be provided. The service measurements defined in this feature serve the purposes
of alerting the service provider that license limits have been exceeded, and also
providing information on usage patterns during the normal time, the grace period, and
the enforcing period. There are two sets of SMs in 1xEV-DO Rev. A VoIP and
Application Pricing feature:

setup counts
usage counts

The setup counts reveal the information on rejections and acceptance when the license
limits are exceeded. The usage counts show in average and peak how many licenses
are being used concurrently. The service provider may also use other service

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
10-11
Issue 5, May 2008
See notice on first page

EVolution Data Only (1xEV-DO) Revision A (Rev. A)


Voice Over Internet Protocol (VoIP) and Application
Pricing

Feature description: 1xEV-DO Rev. A VoIP and


Application Pricing (FID 12905.0)

measurements defined in other features such as Application Based Quality of Service


QoS Support for HRPD Rev. A (FID 12078.9) to get a complete picture of how the
QoS based applications are supported.
Service measurements for 1xEV-DO Rev. A VoIP and Application Pricing (FID
12905.0) are detailed in the Impacts on service measurements: 1xEV-DO Rev. A VoIP
and Application Pricing (FID 12905.0) (p. 10-20) section of this chapter.
Service measurements for Application Based Quality of Service QoS Support for
HRPD Rev. A (FID 12078.9) are detailed in Chapter 7 of this document.
Service-provider perspective

The 1xEV-DO Rev. A VoIP and Application Pricing and related optional features offer
the following advantages:

Lower up-front costs for launching enhanced and QoS based services such VoIP
and PTT over HRPD Rev A
Pay As You Grow - incremental payments as the traffic volume and quantity of
service offerings grows
Pay only for actual services deployed (such as VoIP, or PTT, or Video Telephony,
etc.)

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

10-12

EVolution Data Only (1xEV-DO) Revision A (Rev. A)


Voice Over Internet Protocol (VoIP) and Application
Pricing

Feature description: 1xEV-DO Rev A Application Pricing


Enhancements
(FID 12905.1)
...................................................................................................................................................................................................................................
Introduction

The following information describes the functionality, benefits, and operation of the
1xEV-DO Rev A Application Pricing Enhancements (FID 12905.1) optional feature.
Functionality

The 1xEV-DO Rev A Application Pricing Enhancements (FID 12905.1) optional


feature introduces enhancements to the 1xEV-DO Rev. A VoIP and Application Pricing
(FID 12905.0) feature which include:
SM data collection every 15 minutes for QoS licenses in the following states:

Grace
Override

Handling AP Base Application license:

Overhead Manager (EVDO) (OHM) Initialization


Invalid AP license Alarm

Additional enhancements:

Allowing QoS License quantity reduction


Allow Overdraft capability when license is in Grace State
Token: when a new license key with less quantity is installed over an existing
license key, RNC will generate an installation token.
Audit modifications to allow valid local memory data to overwrite invalid DB data
for given license
OHM Initialization modification for handling AP Base Application license
installation through License Installation Tool (LIT) to LLM License Limit Manager
(LLM)

Benefits

The 1xEV-DO Rev A Application Pricing Enhancements (FID 12905.1) optional


feature provides a Pay As You Grow pricing mechanism for charging the RAN
software that supports applications which require unique QoS treatment over the 1x
EV-DO Rev A RAN such as PTT and VT.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
10-13
Issue 5, May 2008
See notice on first page

EVolution Data Only (1xEV-DO) Revision A (Rev. A)


Voice Over Internet Protocol (VoIP) and Application
Pricing

Feature description: 1xEV-DO Rev A Application Pricing


Enhancements (FID 12905.1)

How the feature operates

The 1xEV-DO Rev A Application Pricing Enhancements (FID 12905.1) optional


feature enhances license mechanisms introduced in Release 28.0 for 1xEV-DO Rev. A
VoIP and Application Pricing (FID 12905.0).
As with the previous feature the customer is able to view their current License
quantities and license order form through a License Installation Tool which resides on
the OA&M Platform for the OMP-FX. The 1xEV-DO Rev A Application Pricing
Enhancements (FID 12905.1) optional feature provides the ability to request a License
Quantity reduction for an existing license and request an AP Base Application license.
Once the order is processed, the license key will be crated and delivered to customers
the same was as for Rev. A license key. The 1xEV-DO Rev A Application Pricing
Enhancements (FID 12905.1) optional feature allows the ability to specify an Overdraft
to be included in generating the license key(s).
The Overdraft option will be enforced when a license is in Grace State. While the
license is in Grace State the system will enforce the purchased RNC and BTS license
limits (with additional Overdraft) as limit.
When the customer invokes the License Installation Tool (LIT) to install the plain-text
licenses file on the appropriate RNC. If LLM License Limit Manager (LLM) detects a
license reduction, a token file is created. The LLM will create an AP Base Application
license in the format and stored in the location introduced by 1xEV FMS Software
Licensing (Phase 1) (FID 9050.0).
Once the customer has access to the License Token file is should be provided to
customer support for cerificate of license reduction. Token files are found under
directory structure: /omp-data/logs/LicenseTools/tokenfiles
The LLM manages the license data and usage information obtained from the License
Limit Agent (LLA) and determines if requests should continue to be allowed. For
licenses that are in Grace, Enforce or Overriding state the Service Measurements (SM)
that are collected in the LLM are written into an SMLog file collection every 15
minutes.
The SMLog files are found under directory structure :
/omp-data/logs/LicenseTools/smlogs directory

The SMLog file is named as follows :


LicenseSMLOGYYMMDDHHMM = LicenseSMLOG +
YY(year)+MM(Month)+DD(day)+HH(Hour)+MM(Minute)

Periodically (every 12 hours) the LIT checks with the LLM for an available SMLog
file. If a log file is available on the AP then the LIT transfers the SMLog file(s) to the
OMP-FX. The SMLog files can be extracted using the command lines:

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

10-14

EVolution Data Only (1xEV-DO) Revision A (Rev. A)


Voice Over Internet Protocol (VoIP) and Application
Pricing

Feature description: 1xEV-DO Rev A Application Pricing


Enhancements (FID 12905.1)

For collecting SMLogs from all RNCs use:

licenseSMLog

For collecting individual RNCs use:

omppclo root> licenseSMLog -r 26

Starting the SM Log Retrieval

Executing function:

Create_RNC_list
List of RNCs from HdrNeConfig.dat file are 23 24 26 25
/opt/fasttrack/docs/ems/classes/com/lucent/autoplex/ems/cm/frames_to_
version.map does not exist, copy all the RNC to valid RNC list

List of valid RNCs are 23 24 26 25

Pulling Files for RNC ID 26

RNC 26:

Primary AP - flx251, IP 172.32.13.80


Secondary AP - flx252, IP 172.32.13.81

Using 172.32.13.80 for all the Licensing operations

The resultOffset = 1
The return code from evLIT is SM_FILE_NOT_EXIST
licenseSMLog exiting with status 0

The AP initialization and OHM Initialization are modified to check for a valid AP Base
application license during OHM Initialization. The License Audit is modified to
validate the local image and update the Database image if applicable.
Service-provider perspective

The service provider must apply an AP Base application license(s) for any AP growth
using 1xEV-DO Rev A Application Pricing Enhancements (FID 12905.1)
(ompLicenseTool) or 1xEV-DO RNC SW Licensing (Phase 2) (FID 9050.1). If the
license is not available during OHM Initialization an Alarm report is triggered to notify
the customer and OHM initialization will be complete, but no call processing is
allowed.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
10-15
Issue 5, May 2008
See notice on first page

EVolution Data Only (1xEV-DO) Revision A (Rev. A)


Voice Over Internet Protocol (VoIP) and Application
Pricing

Feature description: 1xEV-DO Rev A Application Pricing


Enhancements (FID 12905.1)

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
**46 REPT: EVDO: AP 221, ALARM
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
AP 221 Base Software License Key is not installed or invalid
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
PERCEIVED SEVERITY: MAJ, CAUSE: Software Error
1234567890123456789012345678901212345678901234567890123456789
2007-06-19 13:46:56 REPORT #000001 FINAL
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
04 REPT: EVDO: AP 221, ALARM CLEARED
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
AP 221 Base Software License Key is not installed or Invalid
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
2007-06-19 14:04:49 REPORT #000001 FINAL
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

10-16

EVolution Data Only (1xEV-DO) Revision A (Rev. A)


Voice Over Internet Protocol (VoIP) and Application
Pricing

Feature interactions: 1xEV-DO Rev. A VoIP and Application


Pricing
(FID 12905.0)
...................................................................................................................................................................................................................................
Introduction

The 1xEV-DO Rev. A VoIP and Application Pricing (FID 12905.0) optional feature
interacts with the following features:

Enhanced Reverse and Forward Links using Enhanced MAC Protocols with Rev. A
Subtype 2 Physical Layer (FID 12078.2)
Application Based Quality of Service (QoS) Support for HRPD Rev. A (FID
12078.9)
DOrA Application QoS Features

The 1xEV-DO Rev. A VoIP and Application Pricing (FID 12905.0) and the 1xEV-DO
Rev. A Application Pricing Enhancements optional feature are dependent on the
Application Based Quality of Service (QoS) Support for HRPD Rev. A (FID 12078.9)
optional feature that will create the Rev A QoS infrastructure for Multiflow Packet
Application (MFPA). The Application QoS Support for HRPD Rev. A feature supports
conversational speech (CS) and conversational video (CV) QoS service categories and
selected QoS Profile ID under those service categories. Although service provider is
unlikely to provide VoIP or video telephony application based on MFPA, CS and CV
QoS capabilities it will be supported by Application QoS Support for HRPD Rev. A
(FID 12078.9) feature and therefore the 1xEV-DO Rev. A VoIP and Application Pricing
(FID 12905.0) will provide the license key capability for those QoS service categories.
The DOrA Application QoS Features is available at the same release as 1xEV-DO Rev.
A VoIP and Application Pricing (FID 12905.0). The Application QoS Support for
HRPD Rev. A (FID 12078.9) feature will also provide the license key infrastructure
support for CS and CV QoS service categories operating in the EM-FPA mode. For the
1xEV-DO Rev. A VoIP and Application Pricing optional feature (FID 12905.0), the
main difference between application operating in MFPA and EM-FPA mode is in the
BTS resources, such as how EQU is used. The 1xEV-DO Rev. A VoIP and Application
Pricing (FID 12905.0) will need to count EQU in accordance with the mode the
application is supported with.
The License Key mechanism for 1xEV-DO Rev. A VoIP and Application Pricing (FID
12905.0) optional feature will be developed based on the License Key implementation
provided in Enhanced Reverse and Forward Links using Enhanced MAC Protocols
with Rev. A Subtype 2 Physical Layer (FID 12078.2).

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
10-17
Issue 5, May 2008
See notice on first page

EVolution Data Only (1xEV-DO) Revision A (Rev. A)


Voice Over Internet Protocol (VoIP) and Application
Pricing

Feature interactions: 1xEV-DO Rev. A VoIP and


Application Pricing (FID 12905.0)

Enhanced Reverse and Forward Links using Enhanced MAC Protocols with Rev.
A Subtype 2 Physical Layer (FID 12078.2)

This optional feature is part of the Rev. A mandatory package of features, also referred
to as Mandatory Rev. A Feature Bundle. This optional feature introduces the support of
the full Rev. A Physical Layer with the complete set of Rev. A enhanced Medium
Access Control (MAC) protocols that is the following MAC protocols are supported:

Enhanced Control Channel (CC) MAC


Enhanced Forward Traffic Channel (FTC) MAC
Enhanced Access Channel (AC) MAC
Enhanced Subtype 3 Reverse Traffic Channel (RTC) MAC

This optional feature is supported on all Modular Cell BTS types using the new HRPD
Rev. A modem board, the SB-EVM for Modular Cell 4.0 and variants or the
SB-EVMm for Modular Cell 1-3. This optional feature is supported only by the Rev. A
capable RNC.
Application Based Quality of Service (QoS) Support for HRPD Rev. A (FID
12078.9)

This optional feature is not part of the Rev. A mandatory package of features. It
supports QoS per application flow based on request from the user, user QoS profile
and allocatable resource at the system. This optional feature only includes the Radio
Access Network (RAN) network elements. This optional feature is supported on both
existing FMS and next generation RNC platforms. Also this optional feature is
supported on any base station that supports the mandatory package for Rev. A. This
optional feature will be configured on both OMC-RAN and OMP-FX platforms.
DOrA Application QoS Features

The Basic PTT on HRPD-A optional feature provides the basic PTT functionality in
the HRPD RAN using HRPD Rev. A. HRPD Rev. A is required to help meet the tight
delay requirements.
The Basic PTT on HRPD-A optional feature includes paging enhancements that can be
used to increase the effectiveness of paging. Paging effectiveness is defined as the
ability to locate the terminating user with minimum paging attempts. For PTT, locating
the users on the first paging attempt is crucial for minimizing the initial setup delay.
The Basic PTT on HRPD-A optional feature introduces QoS paging using two paging
area types:

Last Seen Active Set


Last Seen RNC (such as Color Code)

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

10-18

EVolution Data Only (1xEV-DO) Revision A (Rev. A)


Voice Over Internet Protocol (VoIP) and Application
Pricing

Feature interactions: 1xEV-DO Rev A Application Pricing


Enhancements
(FID 12905.1)
...................................................................................................................................................................................................................................
Introduction

The 1xEV-DO Rev A Application Pricing Enhancements optional feature interacts with
the following features:

1xEV-DO Rev. A VoIP and Application Pricing (FID 12905.0)


1xEV FMS Software Licensing (Phase 1) (FID 9050.0)
1xEV-DO RNC SW Licensing (Phase 2) (FID 9050.1)

The 1xEV-DO Rev A Application Pricing Enhancements optional feature builds upon
the functionality introduced in 1xEV-DO Rev. A VoIP and Application Pricing (FID
12905.0), specifically the new LLM Virtual Cluster Virtual Machine (VCVM) process
in RNC OA&M. This The 1xEV-DO Rev A Application Pricing Enhancements optional
feature also uses the check_key function introduced by FIDs 9050.0 and 9050.1 which
verify that the AP Base Application license is formatted properly. Once the 1xEV-DO
Rev A Application Pricing Enhancements optional feature is introduced and the feature
is enabled, the check_key function is called during OHM Initialization. If the feature is
not introduced the function is called during AP bring up as currently implemented.
1xEV FMS Software Licensing (Phase 1) (FID 9050.0)

The feature introduces a license key within the 1xEV software running on the 1xEV
FMS to prevent customers from replicating 1xEV software on multiple servers without
paying our per copy RTU fee. The 3G-1X PCF IWF has an implementation based on
MD5 shareware that can be used.
1xEV FMS Software Licensing (Phase 2) (FID 9050.1)

This feature is an enhancement to the 1xEV FMS Software Licensing (Phase 1) (FID
9050.0) feature that modifies the result of key validation failure on a DO RNC AP.
This feature aborts the initialization process when a key is invalid resulting in all DO
AP application software becoming out of service.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
10-19
Issue 5, May 2008
See notice on first page

EVolution Data Only (1xEV-DO) Revision A (Rev. A)


Voice Over Internet Protocol (VoIP) and Application
Pricing

Impacts on service measurements: 1xEV-DO Rev. A VoIP and


Application
Pricing (FID 12905.0)
...................................................................................................................................................................................................................................
Introduction

The 1xEV-DO Rev. A VoIP and Application Pricing (FID 12905.0) optional feature
affects the following categories of services measurements:

HDR counts
HDRC counts
RNC counts

HDR counts

The 1xEV-DO Rev. A VoIP and Application Pricing optional feature affects the
1xEV-DO service measurements that are identified in Table 10-1, 1xEV-DO service
measurements - BTS-HDR Counts (p. 10-20).
Table 10-1

1xEV-DO service measurements - BTS-HDR Counts

Count abbreviation

Count name

AVG_BTS_EQU_LICENSE_USAGE

Average BTS EQU License Usage

BTS_EQU_LICENSE_STATE

BTS EQU License State

PEAK_BTS_EQU_LICENSE_USAGE

Peak BTS EQU License Usage

HDRC counts

The 1xEV-DO Rev. A VoIP and Application Pricing optional feature affects the
1xEV-DO service measurements that are identified in Table 10-2, 1xEV-DO service
measurements - SECT-CARR-HDRC counts (p. 10-20).
Table 10-2

1xEV-DO service measurements - SECT-CARR-HDRC counts

Count abbreviation

Count name

CS_RESV_DROPPED_HO_NO_EQU_
LICENSE_KEY

Conversational Speech Reservations


Dropped during soft handoff when a
sector in a BTS without valid EQU
license key is added to the active set

CV_RESV_DROPPED_HO_NO_EQU_
LICENSE_KEY

Conversational Video Reservations


Dropped during soft handoff when a
sector in a BTS without valid EQU
license key is added to the active set
exceeded

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

10-20

EVolution Data Only (1xEV-DO) Revision A (Rev. A)


Voice Over Internet Protocol (VoIP) and Application
Pricing

Table 10-2

Impacts on service measurements: 1xEV-DO Rev. A VoIP


and Application Pricing (FID 12905.0)

1xEV-DO service measurements - SECT-CARR-HDRC counts


(continued)

Count abbreviation

Count name

PTT_RESV_DROPPED_HO_NO_EQU_
LICENSE_KEY

Conversational PTT Speech Reservations


Dropped during soft handoff when a
sector in a BTS without valid EQU
license key is added to the active set

ROR_REJECTED_RNC_LICENSE_LIMIT_ Reservation On Requests Rejected -- RNC


EXCEEDED
License Limit
ROR_REJECTED_TOTAL_BTS_EQU_
LIMIT_EXCEEDED

Reservation On Requests Rejected -- Total


BTS EQU Limit Exceeded

RNC counts

The 1xEV-DO Rev. A VoIP and Application Pricing optional feature affects the
1xEV-DO service measurements that are identified in Table 10-3, 1xEV-DO service
measurements - SN-RNC counts (p. 10-21).
Table 10-3

1xEV-DO service measurements - SN-RNC counts

Count abbreviation

Count name

AVG_RNC_LICENSE_USAGE_CS

Average RNC Conversational Speech


License Usage

AVG_RNC_LICENSE_USAGE_CV

Average RNC Conversational Video


License Usage

AVG_RNC_LICENSE_USAGE_GENERIC

Average RNC Generic License Usage

AVG_RNC_LICENSE_USAGE_PTT

Average RNC Conversational PTT Speech


License Usage

PEAK_RNC_LICENSE_USAGE_CS

Peak RNC Conversational Speech License


Usage

PEAK_RNC_LICENSE_USAGE_CV

Peak RNC Conversational Video License


Usage

PEAK_RNC_LICENSE_USAGE_
GENERIC

Peak RNC Generic License Usage

PEAK_RNC_LICENSE_USAGE_PTT

Peak RNC Push-To-Talk License Usage

RNC_LICENSE_STATE_CS

RNC Conversational Speech License State

RNC_LICENSE_STATE_CV

RNC Conversational Video License State

RNC_LICENSE_STATE_GENERIC

RNC Generic License State

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
10-21
Issue 5, May 2008
See notice on first page

EVolution Data Only (1xEV-DO) Revision A (Rev. A)


Voice Over Internet Protocol (VoIP) and Application
Pricing

Table 10-3

Impacts on service measurements: 1xEV-DO Rev. A VoIP


and Application Pricing (FID 12905.0)

1xEV-DO service measurements - SN-RNC counts

(continued)

Count abbreviation

Count name

RNC_LICENSE_STATE_PTT

RNC Conversational PTT Speech License


State

References

For detailed information about 1xEV-DO service measurements, see 401-614-326,


CDMA Wireless Networks 1xEV-DO Service Measurements.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

10-22

EVolution Data Only (1xEV-DO) Revision A (Rev. A)


Voice Over Internet Protocol (VoIP) and Application
Pricing

Impacts on service measurements: 1xEV-DO Rev A Application


Pricing
Enhancements (FID 12905.1)
...................................................................................................................................................................................................................................
Introduction

The 1xEV-DO Rev A Application Pricing Enhancements (FID 12905.1) optional


feature affects no additional services measurements:
References

For detailed information about 1xEV-DO service measurements, see 401-614-326,


CDMA2000 Wireless Networks 1xEV-DO Service Measurements.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
10-23
Issue 5, May 2008
See notice on first page

EVolution Data Only (1xEV-DO) Revision A (Rev. A)


Voice Over Internet Protocol (VoIP) and Application
Pricing

License
Key Installation
...................................................................................................................................................................................................................................
Reference

Regarding license key installation, refer to the license installation tool on the OMP-FX.
For detailed installation procedures see CDMA2000 / Wireless Networks Operations
and Management Platform (OMP-FX), 401-662-108document and the 1xEV-DO RAS
Planning and Implementation Guide, 401-614-101document.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

10-24

11

11
Radio
Network Controller
(RNC) Grouping to Improve
Idle Hand-off Performance

Overview
...................................................................................................................................................................................................................................
Purpose

This optional feature description describes the Radio Network Controller (RNC)
Grouping to Improve Idle Hand-off Performance optional feature in CDMA2000
1xEV-DO networks.
Feature summary

The RNC Grouping to Improve Idle Hand-off Performance optional feature improves
the idle handoff performance by cutting down the session transfers and eliminating the
session transfer ping-ponging for ATs moving around RNC borders within the same
RNC Group. It also allows the operator to detect packet loss between RNCs.
Feature Identifier (FID)

A unique Feature Identifier (FID) is assigned to each optional feature. The FID of the
RNC Grouping to Improve Idle Hand-off Performance optional feature is FID 12456.1.
Impacts on user interfaces

The RNC Grouping to Improve Idle Hand-off Performance optional feature affects the
user interfaces that are listed in the following table.
User interface

Feature impact

Feature Element Management System


(EMS)

See Radio Network Controller (RNC)


Group Setup Scenarios in Element
Management System (EMS) (p. 11-19)

Operations and Maintenance Center Radio Access Network (OMC-RAN)

See Radio Network Controller (RNC)


Group Setup Scenarios in Operations and
Maintenance Center - Radio Access
Network (OMC-RAN) (p. 11-26)

....................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
11-1
Issue 5, May 2008
See notice on first page

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Overview

User interface

Feature impact

Service measurements

See Impacts on service measurements


(p. 11-10).

Automatic Message Accounting (AMA)


subsystem

None

Technician Interface (TI) (input/output


messages)

See Impacts on TI messages (p. 11-13)

Intended audience

This document is intended for technicians, engineers, and system administrators who
implement or maintain the RNC Grouping to Improve Idle Hand-off Performance
optional feature in a CDMA2000 1xEV-DO network.
To obtain technical support, documentation, and training or submit feedback

The Online Customer Support (OLCS) web site (http://support.lucent.com/) provides


access to technical support, related documentation, related training, and feedback tools.
The site also provides account registration for new users.
Contents
Availability

11-3

Prerequisites

11-4

Feature description

11-5

Feature interactions

11-9

Impacts on service measurements

11-10

Impacts on TI messages

11-13

Issues and caveats

11-15

Implementing the feature

11-18

Radio Network Controller (RNC) Group Setup Scenarios in Element


Management System (EMS)

11-19

Radio Network Controller (RNC) Group Setup Scenarios in Operations


and Maintenance Center - Radio Access Network (OMC-RAN)

11-26

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

11-2

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Availability
...................................................................................................................................................................................................................................
Release availability

The RNC Grouping to Improve Idle Hand-off Performance optional feature is available
in ECP Releases 28.0 and later. See Issues and caveats (p. 11-15) for more details
relating to cell releases.
Market availability

The RNC Grouping to Improve Idle Hand-off Performance optional feature is available
in all markets.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
11-3
Issue 5, May 2008
See notice on first page

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Prerequisites
...................................................................................................................................................................................................................................
Introduction

The RNC Grouping to Improve Idle Hand-off Performance optional feature has the
following prerequisites.
Supported technologies

The RNC Grouping to Improve Idle Hand-off Performance optional feature is


supported in the following air-interface technologies:

in any band class

HLR configuration

The RNC Grouping to Improve Idle Hand-off Performance optional feature does not
use a Home Location Register (HLR) configuration.
Software requirements

The RNC Grouping to Improve Idle Hand-off Performance optional feature requires
ECP Release 28.0 or later.
Hardware requirements

The RNC Grouping to Improve Idle Hand-off Performance optional feature requires no
hardware beyond the standard hardware in a CDMA2000 1xEV-DO network.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

11-4

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Feature
description
...................................................................................................................................................................................................................................
Introduction

The following information describes the functionality, benefits, and operation of the
RNC Grouping to Improve Idle Hand-off Performance optional feature.
Important! The Radio Network Controller (RNC) Grouping to Improve Idle
Hand-off Performance optional feature will be referred to as RNC Grouping
throughout this section.
Functionality

The RNC Grouping to Improve Idle Hand-off Performance optional feature allows
multiple RNCs to form a group in which the AT can be served by one RNC but
controlled by another RNC in the group. The PCF entity with the A10 termination
sends page messages across RNC boundaries to any cell within the group. The RNC
Grouping to Improve Idle Hand-off Performance optional feature provides the
capability so that the AT does not have to register when crossing an RNC boundary. If
the group is configured so the AT does register when it crosses an RNC boundary, the
AT is able to keep the same session. The RNC Grouping to Improve Idle Hand-off
Performance optional feature improves the overall system performance by avoiding the
idle handoff ping-ponging and RATI ping-ponging at RNC boundaries.
The RNC Grouping to Improve Idle Hand-off Performance optional feature allows the
RNCs to send messages to other RNCs in the group, or all RNCs configured in the
Color Code Map table, for the purpose of detecting dropped packets. A new alarm will
be raised when there are multiple consecutive dropped packets. A new ROP message
periodically reports the percentage of dropped packets.
Benefits

The RNC Grouping to Improve Idle Hand-off Performance gives service providers the
ability to combine multiple RNCs into a group so that an AT can keep its session when
it moves across the RNC borders within the RNC group. This would improve the idle
handoff performance by cutting down the session transfers and eliminating the session
transfer ping- ponging for ATs moving around RNC borders within the same RNC
group.
How the feature operates

The RNC Grouping to Improve Idle Hand-off Performance optional feature provides
options for ATs to send UATI Requests when they cross the RNC boundaries within
the RNC group or for ATs to stay in the dormant state as they move across RNC
borders within the group. By default the SubnetMask is set to 70 for RNCs in a group,
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
11-5
Issue 5, May 2008
See notice on first page

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Feature description

which causes ATs to send UATI Requests when crossing RNC boundaries. The
SubnetMask can be changed to 64 to cause ATs to not send UATI Requests when
staying within the RNC group.
When the AT sends a UATI Request when it crosses an RNC boundary within the
RNC group, the session controlling AP determines whether it will transfer the session.
This determination is based on the session load of the session controlling AP and the
serving AP. If the load on the session controlling AP is greater than the
Session Load Threshold and the load is higher than that of the serving AP by at
least Session Load Differential, the session is transferred. If the session is
transferred, the serving AP assigned a new UATI. If the session is not transferred, the
session controlling AP will reassign the same UATI to the AT. The load balancing
functionality can be disabled by setting the Session Load Threshold to 100.
A new screen is used to create a new RNC group with an RNC Group ID. The
parameters specific to the RNC group, such as Session Load Threshold and
Session Load Differential, are provisioned on this screen. An individual RNC
member in the RNC group is identified by its associated color code. For each member,
there must be a corresponding AN IP Address provisioned in the Color Code Map
page. An RNC can be added to (or removed from) an RNC Group in one of three
ways:

add / remove an RNC group member using RNC Group Member page
modify the Color Code of an existing member using RNC Group Member page
change the AN IP Address associated with a color code in the Color Code Map
page

Messages are exchanged between RNCs of the group to discover the AP IP Addresses,
Service Node ID, and Frame ID of each of the RNCs. For an RNC group with RNCs
from different Service Nodes, the RNC group and RNC group members need to be
created in each of the Service Nodes.
The RNC Grouping to Improve Idle Hand-off Performance optional feature requires
that the contents of the SectorID message broadcast by each cell contain additional
information. For RNCs that are part of a group, there is RNC grouping information
included in the new format of the SectorID message. There is also a new SectorID
Version field included in the SectorID message that can optionally be enabled or
disabled, by using the SectorID Version Included translation on the SN page. When
the Sector ID Version is changed it will force all of the ATs served by that RNC to
re-register. The SectorID Version gets incremented automatically whenever AT session
information is lost or inaccessible (for instance, when RNC reboots or RNC is removed
from an RNC group). The SectorID Version is also synchronized between all members
of an RNC group, so if the SectorID Version changes all of the ATs served by the
entire RNC group are forced to re-register. Otherwise, the EV-DO network would not
be able to reach or alert the ATs with invalid sessions.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

11-6

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Feature description

The RNC Grouping to Improve Idle Hand-off Performance optional feature provides
more paging options to enhance the paging performance. There are four paging
methods available, and four associated paging translations which indicate the number
of times to page using each of the methods. The Paging Strategy translation has been
deprecated since flood paging can now be enabled or disabled using the new
translations

Number of times
Update message
Number of times
last seen RNC)
Number of times
Number of times

to page the last active set of cells obtained from the Last Route
to page the RNC that was last serving the AT (also known as the
to page the Neighbor RNCs (last two seen RNCs)
to page the entire RNC group

A value of zero for any of these paging parameters will indicate that the associated
paging method should be skipped. In addition, the sum of the four paging areas cannot
exceed eight and the number of times to page the last active set plus the number of
times to page the last serving RNC cannot be zero.
The general idea is to page the last active set first, then the last serving RNC, then the
last two seen RNCs, and lastly the entire RNC Group. The RNC Grouping to Improve
Idle Hand-off Performance optional feature will page each area the number of times set
in translation, separated by a Paging Timer (in paging parameters under service node
translation), until the number of times is exhausted, or until the Paging Time-to-Live
Timer (in paging parameters under service node translation) is expired. When the
Paging Time-to-Live Timer expires or the number of times to page all areas is
exhausted, the paging stops.
There are new alarm and ROP messages that have been added:

The Communication Lost alarm is reported when an RNC detects communication


failure with another RNC in the group, which will result in the SectorID Version
being incremented. This alarm is raised by the RNC that is responsible for
managing the SectorID Version for the group. It is raised when it detects an RNC
did not receive the SectorID Version after several attempts. These messages are
controlled by the Heartbeat Timer parameter (RNC Group page).
The AT REREGISTRATION ROP messages are reported whenever all of the ATs are
forced to re-register. The ROP messages include the reasons why the ATs are forced
to re-register.
The Heartbeat Failure alarm is reported when multiple consecutive heartbeats
with other RNCs are missed. The heartbeating is controlled by the Auxiliary
Service Node Control-1 parameter and is explained below.
The periodic NETWORK STAT ROP message indicates the percentage of packets that
were dropped between the RNC and the other RNCs being monitored.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
11-7
Issue 5, May 2008
See notice on first page

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Feature description

The network monitoring performed by the feature is under the control of the Auxiliary
Service Node Control-1 parameter (Service Node II/General page). Monitoring can be
disabled, enabled for just RNCs in the RNC Group, or enabled for all RNCs
provisioned in the Color Code Map table. The rate at which the heartbeat messages are
sent, and the rate of the NETWORK STAT ROP message, are also configured by the same
parameter.
Network monitoring utilizes proprietary messages introduced by this feature, so
monitoring can only be performed with other RNCs running release R28 SU2, or
higher.
The RNC Grouping to Improve Idle Hand-off Performance is intended to improve the
idle handoff performance at RNC boundaries. The RNCs to be grouped are those with
idle handoff ping-ponging problem or RNCs with coverage gaps at their borders.
The following indicators can be used to identify the RNCs for grouping:

RNC
RNC
RNC
RNC
RNC

with
with
with
with
with

high count of Inter-Subnet idle transfer attempts


low inter-Subnet idle transfer success rate
high count of prior session transfer request
high paging failure rate
high count of dangling session

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

11-8

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Feature
interactions
...................................................................................................................................................................................................................................
Introduction

The RNC Grouping to Improve Idle Hand-off Performance optional feature interacts
with no other features.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
11-9
Issue 5, May 2008
See notice on first page

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Impacts
on service measurements
...................................................................................................................................................................................................................................
Introduction

The RNC Grouping to Improve Idle Hand-off Performance optional feature affects the
following categories of services measurements:

HDRC counts

HDRC counts

The RNC Grouping to Improve Idle Hand-off Performance optional feature affects the
1xEV-DO service measurements that are identified in Table 11-1, 1xEV-DO service
measurements - SECT-CARR-HDRC Counts (p. 11-10).
Table 11-1

1xEV-DO service measurements - SECT-CARR-HDRC Counts

Count abbreviation

Count name

INTER_RNC_CONN_ESTABLISHED

Inter-RNC Connection Request


Established

INTER_RNC_CONN_REQ

Inter-RNC Connection Request Received

INTER_RNC_TCA_SENT

Inter-RNC Connection Request - TCA sent

INTRA_RNC_GROUP_BORDER_
CROSSED

Intra RNC Group Border Crossed

INTRA_RNC_GROUP_SESS_TRFR_
ATTEMPT

Intra-RNC Group Session Transfer


Attempt

INTRA_RNC_GROUP_SESS_TRFR_
SUCCESS

Intra-RNC Group Session Transfer


Success

INTRA_RNC_GROUP_SESS_TRFR_UATI_ Intra-RNC Group Session Transfer - UATI


ASSGN_SENT
Assignment Sent
INTRA_RNC_GROUP_SESS_TRFR_UATI_ Intra-RNC Group Session Transfer - UATI
COMPLETE_RCVD
Complete Received

Other Service Measurement Impacts

There may be a decrease in the following Service Measurements due to RNC Grouping
to Improve Idle Hand-off Performance. See Table 11-2, Other Service Measurement
Impacts (p. 11-10) Service Measurements that may be impacted.
Table 11-2

Other Service Measurement Impacts

Count abbreviation

Count name

REQ_WITH_UNRECOGNIZED_UATI

Requests with Unrecognized UATI

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

11-10

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Table 11-2

Impacts on service measurements

Other Service Measurement Impacts

(continued)

Count abbreviation

Count name

DANGLING_SESS_CLOSED

Number of Dangling Sessions Closed

SESS_SETUP_UATI_ASSGNMT_MSG
_SENT

UATI Assignment Messages Sent

SESS_SETUP_UATI_COMPLETE_MSG
_RCVD

UATI Complete Messages Received

AN_INIT_KEEP_ALIVE _REQ

AN-Initiated Keep Alive Requests

INT_SUBNET_IDLE_TRFR_A13_REQ
_RECVD

Inter-Subnet Idle Transfer A13 Requests


Received

ISBNT_IDL_TRFR_A13_SESS_INFO_RSP_ Inter-Subnet Idle Transfer A13-Session


SENT
Information Response Messages Sent
INT_SUBNET_IDLE_TRFR_A13_REJECT_ Inter-Subnet Idle Transfer A13 Reject
SENT
Messages Sent
INT_SUBNET_IDLE_TRFR_A13_CONFIRM_
Inter-Subnet Idle Transfer A13 Confirm
RECVD
Messages Received
INT_SUBNET_IDL_TRFR_PRIOR_SES_
ATTEMPTS

Inter-Subnet Idle Transfer Attempts for


Prior Session

INT_SUBNET_IDL_TRFR_ATTMPT

Inter-Subnet Idle Transfer Attempts

ISBNT_IDL_TRFR_FAIL_SRC_IP_ADR_
NT_FOUND

Inter-Subnet Idle Transfer Attempt Failure


- Source IP address not found

INT_SUBNET_IDLE_TRFR_A13_SIR_
RCVD_LATE

Inter-Subnet Idle Transfer A13 Session


Information Message Received late

ISBNT_IDL_TRFR_FAIL_NO_RSP_PRV_
SBNET

Inter-Subnet Idle Transfer Failures - No


Response from Previous Subnet

ISBNT_IDL_TRFR_FAIL_PRIOR_SES_NO_ Inter-Subnet Idle Transfer Failures - No


RSP
Response from Previous Subnet for Prior
Session
INT_SUBNET_IDL_TRFR_PRIOR_SES_
BAD_REQ

Inter-Subnet Idle Transfer Failures Insufficient Information in AT Prior


Session Configuration Request

ISBNT_IDL_TRFR_FAIL_ORG_PDSN_
CANT_CONN

Inter-Subnet Idle Transfer Failures Original PDSN Cannot Connect

ISBNT_IDL_TRFR_FAIL_RJCT_MSG_
RCVD

Inter-Subnet Idle Transfer Failures Reject Message is received

INT_SUBNET_IDL_TRFR_FAIL_OTHER
_REASON

Inter-Subnet Idle Transfer Failures Other


Reasons

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
11-11
Issue 5, May 2008
See notice on first page

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Table 11-2

Impacts on service measurements

Other Service Measurement Impacts

(continued)

Count abbreviation

Count name

SESS_CLOSE_SESS_TRFR _ABORTED

Session Closed - Session Transfer Aborted

SESS_SETUP_ISBNT_UATI_ASSGN_MSG_ Session Setup - Inter-Subnet Handoff


SENT
UATI Assignment Message Sent
SESS_SETUP_ISBNT_UATI_COMPLETE_ Session Setup - Inter-Subnet Handoff
MSG_RCVD
UATI Complete Message Received

References

For detailed information about 1xEV-DO service measurements, see 401-614-326,


CDMA2000 1xEV-DO Service Measurements.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

11-12

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Impacts
on TI messages
...................................................................................................................................................................................................................................
Introduction

The following information describes the impact of the RNC Grouping to Improve Idle
Hand-off Performance optional feature on input messages and output messages in the
Technician Interface (TI).
Input messages

The following input messages are existing commands and support the RNC Grouping
to Improve Idle Hand-off Performance optional feature:

OP-UATI-STATUS

Execute that input message to request the session status of a given Universal
Access Terminal Identifier (UATI).

OP-ESN-STATUS

Execute that input message to request the session status of a given Electronic Serial
Number (ESN).

OP-IMSI-STATUS

Execute that input message to request the session status of a given International
Mobile Station Identity (IMSI).

OP-MEID-STATUS

Execute that input message to request the session status of a given Mobile
Equipment Identifier (MEID).
Output messages

The output messages of the four above mentioned existing input commands were
modified to also include:

SERVING SN ID
BTS SN ID

The RNC Grouping to Improve Idle Hand-off Performance optional feature added
additional information to the session status output to include SERVING SN ID and
BTS SN ID output messages.
Output messages REPT-EVDO-RNC-AT-RE-REG and REPT-EVDO-RNC-NETWORK-STAT are
introduced by the RNC Grouping to Improve Idle Hand-off Performance optional
feature.
References

For detailed descriptions of those input messages, see 401-610-055, CDMA2000


Wireless Networks Input Messages.
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
11-13
Issue 5, May 2008
See notice on first page

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Impacts on TI messages

For detailed descriptions of those output messages, see 401-610-057, CDMA2000


Wireless Networks Output Messages.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

11-14

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Issues
and caveats
...................................................................................................................................................................................................................................
Introduction

The RNC Grouping to Improve Idle Hand-off Performance optional feature is subject
to the following special issues and/or caveats.
Caveats

Before the RNC Grouping to Improve Idle Hand-off Performance optional feature, all
Connection Requests were handled within the RNC since the AT needed to get a new
UATI once it had moved across the RNC boundary. With the RNC Grouping to
Improve Idle Hand-off Performance optional feature, ATs may have the cell serving AP
and the session controlling AP in different RNCs. The Connection Request is
forwarded from a cell serving AP to a session controlling AP in different RNCs. This
introduces delays if two RNCs are far away from each other which may affect the
success rate of the Connection Request establishment. For best performance, an RNC
must be grouped with RNCs with which they have a low packet loss and delay.
It is also recommended to group RNCs with same feature set, especially with the
capability of supporting Rev. A or Rev 0. When two RNCs with different capabilities
are grouped together, the capability might not be fully utilized. For example, with
mixture of Rev. A and Rev 0 RNCs in the same group, an AT with Rev A capability
might not be able to utilize the Rev A function even if it is in a serving area of a Rev
A RNC. The reason is that this AT might be controlled by another RNC with Rev. 0
within the same RNC Group. However, the mixture of RNCs with different functions
will not result in call failures. The configuration with RNCs with different feature sets
will only be used on a temporary basis, such as on a system upgrading.
There are two options for setting the SubnetMask when an RNC is in a group. It can
be set to 64 or 70. When the subnet mask is set to 64 the AT will not send a UATI
request when it crosses an RNC boundary in the group. When the subnet mask is set to
70 the AT will send a UATI request when it crosses an RNC boundary within the
group.
The advantage of setting the SubnetMask to 64 is that it avoids extra UATI requests.
When a subnet mask of 70 is used, RATI ping-ponging may still occur. This occurs
when there are coverage gaps along an RNC border. In that case the AT might send a
UATIRequest (RATI) and use the prior-session transfer to restore the old session. This
will introduce extra processing and potentially create a dangling session. More
seriously, this may cause the session transfer ping-ponging since a new session is
granted for UATIRequest (RATI).
A disadvantage of setting the SubnetMask to 64 is that the access network is not able
to track the AT when it moves across RNC boundaries within the RNC group. So the
access network needs to page a wider area to locate the AT, which would have a
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
11-15
Issue 5, May 2008
See notice on first page

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Issues and caveats

negative impact on the paging efficiency. With a SubnetMask of 64 the OHM session
load may become unbalanced depending upon the traffic pattern. OHMs controlling
cells along the RNC Group border may control an increased number of sessions.
When using a SubnetMask of 64 there is a risk of overloading the control channel with
page messages. That issue may be mitigated by enabling distance based route updates.
With distance based route updates the AT will send a route update message when it has
moved beyond a predefined radius from the previous sector that it sent a route update
on. By doing this the access network will have a more accurate view of the ATs
location, which would reduce the number of flood pages that have to be sent.
Important! RNCs should only be grouped if all of the cells controlled by the
RNCs are R28 cells, or R27 cells running at least R27.02, or R26 cells running at
least R26.03. These cells have a change which allows the SubnetMask to be
updated dynamically. If an RNC in a group controls cells that are not on one of
these releases, the cells will need to be rebooted for a new SubnetMask value to
take effect.
The RNC Group ID must not be reused by adjacent RNCs outside the group as it is
used to identify the coverage area of the RNC group. When using a SubnetMask of 64
the RNC Group ID defines the RNCs within the group and triggers the AT to send
UATI request when crossing the group border. When using a SubnetMask of 70 the
RNC Group ID ensures the AT will send a UATI request when crossing a border
between two RNCs in separate groups that are using the same RNC Group Member
ID.
The RNC Group size is limited by the total number of sector carriers in the Group.
The service measurements collected by remote processor needs to be transported to the
local processor at the end of each hour. The processor to transport the service
measurements can only support service measurements of 1300 sector carriers within a
RNC Group. If there are more than 1300 sector carriers in the RNC Group some of the
service measurements might be lost during the transport. For example, for RNCs
equipped with 200 sector carriers, only 6 RNCs can be grouped together to guarantee
the complete collection of service measurements.
To limit processor occupancy the heartbeat interval for network monitoring should not
be less than 10 seconds when monitoring more than 60 RNCs.
When setting up an RNC group, the customer needs to check the neighboring markets
to be sure the color code maps in those markets include entries for all RNCs in the
group. With RNC grouping, a neighboring RNC may need to perform an idle handoff
with any RNC in the group, not just the immediate neighbor RNC. The reason for this
is because the ATs session could be located on any RNC within the group. For more
detailed information about the color code map, see CDMA2000 1xEV-DO
Configuration Parameters Guide, 401-614-324.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

11-16

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Issues and caveats

The color code map of a neighboring RNC, which borders an RNC group, needs to be
configured correctly with the color codes of all RNCs in the group. Otherwise, there
may be an increase in idle handoff failures in the neighboring RNCs. This may also
make the performance of the RNC group worse along the RNC group borders. The
customer can monitor the ROP file for occurrences of CP Fail Error Code 20005 to
identify idle handoff failures where the source RNC IP address can not be found due to
a missing color code in the color code map.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
11-17
Issue 5, May 2008
See notice on first page

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Implementing
the feature
...................................................................................................................................................................................................................................
Overview

The RNC Grouping to Improve Idle Hand-off Performance optional feature creates a
new screen for the RNC Group with a RNC Group ID. The parameters specific to the
RNC group, such as Session Load Threshold and Session Load Differential, are
provisioned on the new screen. Each individual RNC in the RNC Group is identified
by its associated color code. For each RNC member, the technician enters the Color
Code of the RNC on a RNC Group Members screen. Before adding an RNC to a
group the technician must verify that the A13 IP address of the RNC is added to the
Color Code Maps screen for the corresponding color code.
The RNC Grouping to Improve Idle Hand-off Performance optional feature is FAFable.
To disable the RNC Grouping to Improve Idle Hand-off Performance optional feature
all RNC Group Members must be deleted, and then all RNC Groups.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

11-18

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Radio Network Controller (RNC) Group Setup Scenarios in


Element
Management System (EMS)
...................................................................................................................................................................................................................................
Purpose

The RNC Grouping to Improve Idle Hand-off Performance setup scenarios cover how
the groups are created and deleted, and how the RNCs are added to the groups and
deleted from the groups in EMS. Also covered are enabling and disabling network
monitoring.
Create a new RNC Group for Two or More RNCs in the Same SN

Important! All the RNCs are in service.


Perform the following steps:
...................................................................................................................................................................................................

Go to the RNC Group screen, and click on the Create new RNCGroup instance link.
...................................................................................................................................................................................................

Enter RNC Group ID and populate all Group specific parameters.


...................................................................................................................................................................................................

Click Submit
...................................................................................................................................................................................................

Go to the RNC Group Members screen, and click on the Create new
RNCGroupMember instance link.
...................................................................................................................................................................................................

Populate the group ID, member ID, and color code parameters.
...................................................................................................................................................................................................

Click Submit
...................................................................................................................................................................................................

Repeat Substeps 4 - 6 to add all RNCs.


Important! The Color Code of the RNC matches the Color Code entry on the RNC
Frame screen and the Color Code in the Color Code to A13 AP IP address table.
...................................................................................................................................................................................................

Optional step to verify and modify SubnetMask, open Configuration Page page.
...................................................................................................................................................................................................

Click on FMS frame and select the table with frame number you want to provision
all the parameters in that Frame.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
11-19
Issue 5, May 2008
See notice on first page

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Radio Network Controller (RNC) Group Setup Scenarios


in Element Management System (EMS)

...................................................................................................................................................................................................

10

Modify the SubnetMask to the desire value based on the guide. See Issues and
caveats (p. 11-15) for more information
...................................................................................................................................................................................................

11

Modify the paging parameters for the service node containing the RNCs added to the
group. Go to the Paging Parameters page on the Service Node screen. Set the
parameters as indicated in Table 11-3, Modify Paging Parameters (p. 11-20):
Table 11-3

Modify Paging Parameters

Parameter

Subnet
Mask =
70

Subnet
Mask = 64

Number of Times to Page the Last Active Set

Number of Times to Page the Last Seen RNC

Number of Times to Page Neighboring RNC

Number of Times to Page Entire RNC Group

...................................................................................................................................................................................................

12

Verify the color code maps (CCMap) of adjacent RNCs include all RNCs in the group.
E...................................................................................................................................................................................................
ND OF STEPS

System behaviors

Performing this procedure will add new info in the SectorID and cause all ATs in the
serving area to send UATI Request. The UATI Request will be handled by the serving
OHM and the serving OHM will assign the same UATI back to the AT.
Create a New RNC Group with RNCs from Different SNs

Important! All RNCs are in service.


...................................................................................................................................................................................................

Start with SN1 and follow the steps in the previous procedure, Create a new RNC
Group for Two or More RNCs in the Same SN (p. 11-19) to add RNC group and
member information into the SN1.
...................................................................................................................................................................................................

Go to each of the other SNs with RNCs in the group and follow the steps in the
previous procedure, Create a new RNC Group for Two or More RNCs in the Same
SN (p. 11-19) to add RNC group and member information into the SN. On each SN

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

11-20

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Radio Network Controller (RNC) Group Setup Scenarios


in Element Management System (EMS)

make sure to use the same member ID for the same RNC.
E...................................................................................................................................................................................................
ND OF STEPS

System behaviors

Performing this procedure will add new info in the SectorID and cause all ATs in the
serving area to send UATI Request. The UATI Request will be handled by the serving
OHM and the serving OHM will assign the same UATI back to the AT.
Add a RNC to an Existing RNC Group (All in the Same SN)

Important! All RNCs are in service.


...................................................................................................................................................................................................

Go to the RNC Group Members screen, and click on the Create new
RNCGroupMember instance link.
...................................................................................................................................................................................................

Populate the group ID, member ID, and color code parameters.
...................................................................................................................................................................................................

Click Submit
...................................................................................................................................................................................................

Verify the color code maps (CCMap) of adjacent RNCs include all RNCs in the group.
E...................................................................................................................................................................................................
ND OF STEPS

System behaviors

The newly added RNC will change the SectorID to include new info so all ATs served
by the newly added RNC will start to send UATI Request. The same UATI will be
assigned back to the ATs. The existing RNCs will exchange info with the newly added
RNC in the background but there is no impact to the ATs served by existing RNC
members.
Add a RNC from a Different SN (SN2) to an Existing RNC Group

Important! All RNC are in service


...................................................................................................................................................................................................

Start with SN2 and follow the steps in the previous procedure, Create a new RNC
Group for Two or More RNCs in the Same SN (p. 11-19) to add RNC group and
member information into the SN2.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
11-21
Issue 5, May 2008
See notice on first page

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Radio Network Controller (RNC) Group Setup Scenarios


in Element Management System (EMS)

...................................................................................................................................................................................................

Go to the other SNs with RNCs in the group and follow the steps in the previous
procedure, Add a RNC to an Existing RNC Group (All in the Same SN) (p. 11-21)
to add RNC member information into the SN.
E...................................................................................................................................................................................................
ND OF STEPS

System behaviors

The newly added RNC will change the SectorID to include new info so all ATs served
by the newly added RNC will start to send UATI Request. The same UATI will be
assigned back to the ATs. The existing RNCs will exchange info with the newly added
RNC in the background but there is no impact to the ATs served by existing RNC
members.
Remove One RNC from the RNC Group (All in the Same SN)

Important! All RNCs are in service


...................................................................................................................................................................................................

Go to the Group Member screen and select the RNC member to be deleted.
...................................................................................................................................................................................................

Click on the Delete link on the RNC Group Member page.


...................................................................................................................................................................................................

Click Submit
...................................................................................................................................................................................................

If there are no longer any RNCs in the SN that are in a group then restore the paging
parameters to the recommended values.
E...................................................................................................................................................................................................
ND OF STEPS

System behaviors

When removing an RNC from the group, the SectorID Version changes for all of the
RNCs that remain in the group. For the RNC being removed, the SectorID Version
does not change, but the SectorID changes.
All ATs in the deleted RNC coverage area will request a new UATI

For ATs with sessions controlled by the RNCs still in the RNC Group, the idle
handoff will be performed and sessions will be transferred to the serving RNC.
For ATs with sessions controlled by the deleted RNC, the same UATI_024 will be
assigned back to the ATs.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

11-22

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Radio Network Controller (RNC) Group Setup Scenarios


in Element Management System (EMS)

All ATs in the coverage area of the remaining RNC Group members will request a new
UATI if the SectorID Version Included flag on the SN page is set to y.

For ATs with sessions controlled by the deleted RNC, the idle handoff will be
performed and sessions will be transferred to the serving RNC.
For ATs with sessions controlled by the other RNCs still in the RNC Group, UATI
Request will be treated as regular UATI Requests when ATs cross the RNC
boundaries within the RNC Group. The session may be transferred to the serving
RNC or stay at the original controlling RNC, depending on the session loads of the
RNCs.

Remove One RNC from the RNC Group Spanning Multiple SNs

Important! All RNCs are in service


...................................................................................................................................................................................................

Note the color code of each RNC that is to be deleted from the group and the RNC
Group Member ID.
...................................................................................................................................................................................................

On each SN that has an RNC in the group follow the steps in the previous procedure,
Remove One RNC from the RNC Group (All in the Same SN) (p. 11-22) to remove
the RNC from the RNC Group Member information for that SN.
E...................................................................................................................................................................................................
ND OF STEPS

System behaviors

The system will behave as described in the previous procedure, Remove One RNC
from the RNC Group (All in the Same SN) (p. 11-22).
Remove an RNC Group

Important! All RNCs are in service


...................................................................................................................................................................................................

Note the color code of each RNC that is to be deleted from the group and the RNC
Group Member ID.
Go to the RNC Group Members screen and verify no members are listed with the
Group ID that is to be deleted. If necessary use the previous procedures Remove One
RNC from the RNC Group (All in the Same SN) (p. 11-22) and Remove One RNC
from the RNC Group Spanning Multiple SNs (p. 11-23) to remove the members.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
11-23
Issue 5, May 2008
See notice on first page

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Radio Network Controller (RNC) Group Setup Scenarios


in Element Management System (EMS)

...................................................................................................................................................................................................

On each SN that has the RNC Group configured go to the RNC Groups screen, select
the ID of the Group to be deleted, and click on the delete button. Click on the OK
button when prompted to confirm deletion.
...................................................................................................................................................................................................

Repeat step two on the remaining service nodes, as applicable.


E...................................................................................................................................................................................................
ND OF STEPS

System behaviors

There is no impact to the operation of the system when RNC Groups are deleted.
System behavior is only affected when members are deleted from the group, as
discussed in the previous two procedures.
Enable or Disable Network Monitoring
...................................................................................................................................................................................................

Go to the Service Node II General screen and enter the desired value for
Auxiliary Service Node Control - 1. Set the values as indicated in Table 11-4,
Values for Auxiliary Service Node Control - 1 (p. 11-24).
Table 11-4
Value

Values for Auxiliary Service Node Control - 1


Enabled/
Disabled

Heartbeat
Interval
(seconds)

ROP
Report
Interval
(minutes)

RNCs Monitored

Disabled

n/a

n/a

n/a

Enabled

15

RNCs in the RNC Group

Enabled

60

RNCs in the RNC Group

Enabled

120

RNCs in the RNC Group

Enabled

10

15

RNCs in the RNC Group

Enabled

10

60

RNCs in the RNC Group

Enabled

10

120

RNCs in the RNC Group

Enabled

60

120

RNCs in the RNC Group

Disabled

n/a

n/a

n/a

Enabled

15

All RNCs in the CCMap

10

Enabled

60

All RNCs in the CCMap

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

11-24

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Table 11-4

Radio Network Controller (RNC) Group Setup Scenarios


in Element Management System (EMS)

Values for Auxiliary Service Node Control - 1

(continued)

11

Enabled

120

All RNCs in the CCMap

12

Enabled

10

15

All RNCs in the CCMap

13

Enabled

10

60

All RNCs in the CCMap

14

Enabled

10

120

All RNCs in the CCMap

15

Enabled

60

120

All RNCs in the CCMap

E...................................................................................................................................................................................................
ND OF STEPS

System behaviors

When the value of Auxiliary Service Node Control 1 is set to 0 or 8 no


network monitoring is performed. Other values enable monitoring of the other RNCs in
the group, or all RNCs with AN IP addresses provisioned in the CCMap table. When
enabled the RNC will send a heartbeat message to the other RNCs at the selected rate,
and report the percentage of packet loss in the ROP at the specified interval.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
11-25
Issue 5, May 2008
See notice on first page

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Radio Network Controller (RNC) Group Setup Scenarios in


Operations and Maintenance Center - Radio Access Network
(OMC-RAN)
...................................................................................................................................................................................................................................
Purpose

The RNC Grouping to Improve Idle Hand-off Performance setup scenarios cover how
the groups are created and deleted, and how the RNCs are added to the groups and
deleted from the groups within the OMC-RAN. Also covered are enabling and
disabling network monitoring.
See Appendix 7 of Alcatel-Lucent 9271 EV-DO Radio Network Controller,
401-614-102 for basic information in order to:

understand the OMC-RAN,


understand the layout of EV-DO information on the OMC-RAN, and
provisioning activities on EV-DO network and elements from the OMC-RAN.

For more information about the different 1xEV-DO OA&M interfaces that are used in
performing OA&M tasks on the EV-DO controller and its managed resources,
including the purpose of each interface and how to access it, see Alcatel-Lucent 9271
EV-DO Radio Network Controller, 401-614-102, Chapter 3, User Interfaces.
Create a new RNC Group for Two or More RNCs in the Same SN

Important! All the RNCs are in service.


In R29 and earlier, FxApx VNE (the FxApx listed at the bottom of the ORCA
Group) gives a global SN general view for all EV-DO RNCs on one FxApx.
In R30 and later, x:R30 Global Config DO where x is the FxApx for the ORCA
Group) gives a global SN general view for all EV-DO RNCs on one FxApx.
Perform the following steps:
...................................................................................................................................................................................................

Go to the Global Config DO tab, and click on left arrow of Global Config DO.
...................................................................................................................................................................................................

Create RNC Group under the Global Config DO tab.


...................................................................................................................................................................................................

Right click on the Global Config DO , and create RNC Group.


...................................................................................................................................................................................................

Configure the parameters within created RNC Group following the guide. The
RNC Group Table folder is created.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

11-26

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Radio Network Controller (RNC) Group Setup Scenarios


in Operations and Maintenance Center - Radio Access
Network (OMC-RAN)

...................................................................................................................................................................................................

Create RNC Group Member, under the RNC Group (in Global Config DO of the
frame).
...................................................................................................................................................................................................

Right click on the RNC Group, and create RNCGroupMember. Repeat for additional
members.
...................................................................................................................................................................................................

Check the color code map by opening the Global Config DO tab by left clicking on
the left arrow of Global Config DO . Ensure the Color Code to AN IP address
mapping is correct in the CCmap.
...................................................................................................................................................................................................

Verify the color code maps (CCmap) of adjacent RNCs include all RNCs in the group.
Repeat for all additional color code maps.
...................................................................................................................................................................................................

Optional step to verify and modify SubnetMask, open DO-RNC:FMS# tab. Click on left
arrow of DO-RNC:FMS# tab, under DO-RNC:FMS# tab of the frame
...................................................................................................................................................................................................

10

Right click on the desired HDRFrame and select the Details.


...................................................................................................................................................................................................

11

In the Details window under the HDRFrame tab, modify the SubnetMask to the desire
value based on the guide. See Issues and caveats (p. 11-15) for more information.
...................................................................................................................................................................................................

12

Modify the paging parameters for the service node containing the RNCs added to the
group. Go to the Global Config DO page (not tab). Right click Global Config DO and
select Details.
...................................................................................................................................................................................................

13

In the Details window Under SN Page tab, select and modify the desired values of
the paging under the Number of Time to Page section. Set the parameters as
indicated in Table 11-5, Modify Paging Parameters (p. 11-27):
Table 11-5

Modify Paging Parameters

Parameter

Subnet
Mask =
70

Subnet
Mask = 64

Number of Times to Page Neighboring RNC

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
11-27
Issue 5, May 2008
See notice on first page

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Table 11-5

Radio Network Controller (RNC) Group Setup Scenarios


in Operations and Maintenance Center - Radio Access
Network (OMC-RAN)

Modify Paging Parameters

(continued)

Number of Times to Page Entire RNC Group

Number of Times to Page the Last Seen RNC

Number of Times to Page the Last Active Set

E...................................................................................................................................................................................................
ND OF STEPS

System behaviors

Performing this procedure will add new info in the SectorID and cause all ATs in the
serving area to send UATI Request. The UATI Request will be handled by the serving
OHM and the serving OHM will assign the same UATI back to the AT.
Create a New RNC Group with RNCs from Different SNs

Important! All RNCs are in service.


...................................................................................................................................................................................................

Start with SN1 and follow the steps in the previous procedure, Create a new RNC
Group for Two or More RNCs in the Same SN (p. 11-26) to add RNC group and
member information into the SN1.
...................................................................................................................................................................................................

Go to each of the other SNs with RNCs in the group and follow the steps in the
previous procedure, Create a new RNC Group for Two or More RNCs in the Same
SN (p. 11-26) to add RNC group and member information into the SN. On each SN
make sure to use the same member ID for the same RNC.
E...................................................................................................................................................................................................
ND OF STEPS

System behaviors

Performing this procedure will add new info in the SectorID and cause all ATs in the
serving area to send UATI Request. The UATI Request will be handled by the serving
OHM and the serving OHM will assign the same UATI back to the AT.
Add a RNC to an Existing RNC Group (All in the Same SN)

Important! All RNCs are in service.


...................................................................................................................................................................................................

Go to the RNC Group Member tab, under the RNC Group (in Global Config DO of
the frame).

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

11-28

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Radio Network Controller (RNC) Group Setup Scenarios


in Operations and Maintenance Center - Radio Access
Network (OMC-RAN)

...................................................................................................................................................................................................

Right click on the RNC Group, and create RNCGroupMember. Repeat for additional
members.
...................................................................................................................................................................................................

Check the color code map by opening the Global Config DO tab by left clicking on
the left arrow of Global Config DO . Ensure the Color Code to AN IP address
mapping is correct in the CCmap.
...................................................................................................................................................................................................

Verify the color code maps (CCmap) of adjacent RNCs include all RNCs in the group.
Repeat for all additional color code maps.
E...................................................................................................................................................................................................
ND OF STEPS

System behaviors

The newly added RNC will change the SectorID to include new info so all ATs served
by the newly added RNC will start to send UATI Request. The same UATI will be
assigned back to the ATs. The existing RNCs will exchange info with the newly added
RNC in the background but there is no impact to the ATs served by existing RNC
members.
Add a RNC from a Different SN (SN2) to an Existing RNC Group

Important! All RNC are in service


...................................................................................................................................................................................................

Start with SN2 and follow the steps in the previous procedure, Create a new RNC
Group for Two or More RNCs in the Same SN (p. 11-26) to add RNC group and
member information into the SN2.
...................................................................................................................................................................................................

Go to the other SNs with RNCs in the group and follow the steps in the previous
procedure, Add a RNC to an Existing RNC Group (All in the Same SN) (p. 11-28)
to add RNC member information into the SN.
E...................................................................................................................................................................................................
ND OF STEPS

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
11-29
Issue 5, May 2008
See notice on first page

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Radio Network Controller (RNC) Group Setup Scenarios


in Operations and Maintenance Center - Radio Access
Network (OMC-RAN)

System behaviors

The newly added RNC will change the SectorID to include new info so all ATs served
by the newly added RNC will start to send UATI Request. The same UATI will be
assigned back to the ATs. The existing RNCs will exchange info with the newly added
RNC in the background but there is no impact to the ATs served by existing RNC
members.
Remove One RNC from the RNC Group (All in the Same SN)

Important! All RNCs are in service


...................................................................................................................................................................................................

Go to the RNC Group Member tab, under the RNC Group (in Global Config DO of
the frame).
...................................................................................................................................................................................................

Right click on the RNC Group, and delete RNCGroupMember. Repeat for additional
members.
...................................................................................................................................................................................................

Click Submit
...................................................................................................................................................................................................

If there are no longer any RNCs in the SN that are in a group then restore the paging
parameters to the recommended values.
E...................................................................................................................................................................................................
ND OF STEPS

System behaviors

When removing an RNC from the group, the SectorID Version changes for all of the
RNCs that remain in the group. For the RNC being removed, the SectorID Version
does not change, but the SectorID changes.
All ATs in the deleted RNC coverage area will request a new UATI

For ATs with sessions controlled by the RNCs still in the RNC Group, the idle
handoff will be performed and sessions will be transferred to the serving RNC.
For ATs with sessions controlled by the deleted RNC, the same UATI_024 will be
assigned back to the ATs.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

11-30

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Radio Network Controller (RNC) Group Setup Scenarios


in Operations and Maintenance Center - Radio Access
Network (OMC-RAN)

All ATs in the coverage area of the remaining RNC Group members will request a new
UATI if the SectorID Version Included flag on the SN page is set to y.

For ATs with sessions controlled by the deleted RNC, the idle handoff will be
performed and sessions will be transferred to the serving RNC.
For ATs with sessions controlled by the other RNCs still in the RNC Group, UATI
Request will be treated as regular UATI Requests when ATs cross the RNC
boundaries within the RNC Group. The session may be transferred to the serving
RNC or stay at the original controlling RNC, depending on the session loads of the
RNCs.

Remove One RNC from the RNC Group Spanning Multiple SNs

Important! All RNCs are in service


...................................................................................................................................................................................................

Note the color code of each RNC that is to be deleted from the group and the RNC
Group Member.
...................................................................................................................................................................................................

On each SN that has an RNC in the group follow the steps in the previous procedure,
Remove One RNC from the RNC Group (All in the Same SN) (p. 11-30) to remove
the RNC from the RNC Group Member information for that SN.
E...................................................................................................................................................................................................
ND OF STEPS

System behaviors

The system will behave as described in the previous procedure, Remove One RNC
from the RNC Group (All in the Same SN) (p. 11-22).
Remove an RNC Group

Important! All RNCs are in service


...................................................................................................................................................................................................

Note the color code of each RNC that is to be deleted from the group and the RNC
Group Member.
Go to the RNC Group Member tab and verify no members are listed with the
RNC Group that is to be deleted. If necessary use the previous procedures Remove
One RNC from the RNC Group (All in the Same SN) (p. 11-30) and Remove One
RNC from the RNC Group Spanning Multiple SNs (p. 11-31) to remove the
members.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
11-31
Issue 5, May 2008
See notice on first page

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Radio Network Controller (RNC) Group Setup Scenarios


in Operations and Maintenance Center - Radio Access
Network (OMC-RAN)

...................................................................................................................................................................................................

On each SN that has the RNC Group configured go to the RNC Group Member tab,
select the RNC Group to be deleted, and right click on the desired RNC Group Member
and select delete.
...................................................................................................................................................................................................

Repeat Step 2 on the remaining service nodes, as applicable.


E...................................................................................................................................................................................................
ND OF STEPS

System behaviors

There is no impact to the operation of the system when RNC Groups are deleted.
System behavior is only affected when members are deleted from the group, as
discussed in the previous two procedures.
Enable or Disable Network Monitoring
...................................................................................................................................................................................................

Go to the Global Config DO page (not tab) and right click on the text
Global Config DO and select Details.
...................................................................................................................................................................................................

From the Details window, under Current Engr select and modify
Auxiliary Service Node Control 1 with the appropriate value. Set the values as
indicated in Table 11-6, Values for Auxiliary Service Node Control - 1 (p. 11-32).
Table 11-6
Value

Values for Auxiliary Service Node Control - 1


Enabled/
Disabled

Heartbeat
Interval
(seconds)

ROP
Report
Interval
(minutes)

RNCs Monitored

Disabled

n/a

n/a

n/a

Enabled

15

RNCs in the RNC Group

Enabled

60

RNCs in the RNC Group

Enabled

120

RNCs in the RNC Group

Enabled

10

15

RNCs in the RNC Group

Enabled

10

60

RNCs in the RNC Group

Enabled

10

120

RNCs in the RNC Group

Enabled

60

120

RNCs in the RNC Group

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

11-32

Radio Network Controller (RNC) Grouping to Improve Idle


Hand-off Performance

Table 11-6

Radio Network Controller (RNC) Group Setup Scenarios


in Operations and Maintenance Center - Radio Access
Network (OMC-RAN)

Values for Auxiliary Service Node Control - 1

(continued)

Disabled

n/a

n/a

n/a

Enabled

15

All RNCs in the CCMap

10

Enabled

60

All RNCs in the CCMap

11

Enabled

120

All RNCs in the CCMap

12

Enabled

10

15

All RNCs in the CCMap

13

Enabled

10

60

All RNCs in the CCMap

14

Enabled

10

120

All RNCs in the CCMap

15

Enabled

60

120

All RNCs in the CCMap

E...................................................................................................................................................................................................
ND OF STEPS

System behaviors

When the value of Auxiliary Service Node Control 1 is set to 0 or 8 no


network monitoring is performed. Other values enable monitoring of the other RNCs in
the group, or all RNCs with AN IP addresses provisioned in the CCMap table. When
enabled the RNC will send a heartbeat message to the other RNCs at the selected rate,
and report the percentage of packet loss in the ROP at the specified interval.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
11-33
Issue 5, May 2008
See notice on first page

12

12
EVolution
Data Optimized
(EV-DO) Performance
Monitoring Tools Enhancements

Overview
...................................................................................................................................................................................................................................
Purpose

This chapter describes the following features in CDMA2000 1xEV-DO Networks.


Unique Feature Identifiers (FIDs) are assigned to each feature:

1xEV-DO Performance Monitoring Tools Enhancements (FID 9253.1)


1xEV-DO Tool Interface between Operations and Maintenance Platform for
Flexent (OMP-FX) and 1xEV-DO Radio Network Controller (RNC) (FID 9253.2)
Access Terminal (AT) Trace Enhancement for Customer Use (FID 9253.3)

Feature summary

The following summarizes the features covered in this document.


1xEV-DO Performance Monitoring Tools Enhancements (FID 9253.1)

The 1xEV-DO Performance Monitoring Tools Enhancements adds Special Engineering


Studies (SMS) tools to provide histogram counts of performance data for capacity
planning purposes including Reverse Link Short and Long Term RSSI, Forward Link
Traffic Percent Busy Slots and Datalink Utilization.
1xEV-DO Tool Interface between OMP-FX and 1xEV-DO RNC (FID 9253.2)

The 1xEV-DO Tool Interface between OMP-FX and 1xEV-DO RNC feature provides a
new interface between the OMP-FX and the Optimized Reconfigurable Chip
Architecture Radio Network Controller (ORCA-RNC) for Operations and Maintenance
Center - Radio Access Network (OMC-RAN) managed RNCs.
AT Trace Enhancement for Customer Use (FID 9253.3)

The Access Terminal (AT) Trace Enhancement for Customer Use feature is a call
tracing tool that is anchored on EV-DO RNC. It logs messages traversed through the
major control functions in RNC such as Overhead Management (OHM), Selected

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
12-1
Issue 5, May 2008
See notice on first page

EVolution Data Optimized (EV-DO) Performance


Monitoring Tools Enhancements

Overview

Function Main (SFM), and Packet Control Function (PCF). These messages are
pertained to EV-DO standards, including A11/A12/A13 and the HDR Air Interfaces
(HAI).
This feature allows the customer to use the tool to trace multiple ATs, no matter if they
are in active, dormant or idle state, across multiple RNCs under the same Service Node
(SN). The header of the logged messages are enhanced in such a way that they provide
adequate information to allow re-construction of the call flows along the time line. As
a result, the messages logged is translated to the call flows among cell site, RNC
(including OHM, SFM and PCF), Packet Data Serving Node (PDSN), and Ran-AAA,
which facilitate fault detection and error diagnosis.
Impacts on user interfaces

The 1xEV-DO Performance Monitoring Tools Enhancements optional feature affects


the user interfaces that are listed in the following table.
Feature

User interface

Feature impact

1xEV-DO Performance
Monitoring Tools
Enhancements (FID
9253.1)

Element Management
System (EMS) or
Operations and
Maintenance Center Radio Access Network
(OMC-RAN)

None

Service measurements

See CDMA2000
1xEV-DO Network Service
Measurements,
401-614-326 for a sample
copy of the SES histogram
and full descriptions of the
SES counts.

Automatic Message
Accounting (AMA)
subsystem

None

Technician Interface (TI)


(input/output messages)

See Impacts on TI
Messages

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

12-2

EVolution Data Optimized (EV-DO) Performance


Monitoring Tools Enhancements

Overview

Feature

User interface

Feature impact

1xEV-DO Tool Interface


between OMP-FX and
1xEV-DO RNC (FID
9253.2)

Element Management
System (EMS) or
Operations and
Maintenance Center Radio Access Network
(OMC-RAN)

None

Service measurements

None

Automatic Message
Accounting (AMA)
subsystem

None

Technician Interface (TI)


(input/output messages)

None

Element Management
System (EMS) or
Operations and
Maintenance Center Radio Access Network
(OMC-RAN)

None

Service measurements

None

Automatic Message
Accounting (AMA)
subsystem

None

Technician Interface (TI)


(input/output messages)

None

AT Trace Enhancement for


Customer Use (FID
9253.3)

To obtain technical support, documentation, and training or submit feedback

The Online Customer Support (OLCS) web site (http://support.lucent.com/) provides


access to technical support, related documentation, related training, and feedback tools.
The site also provides account registration for new users.
Contents
Availability

12-5

Prerequisites

12-6

Feature description: 1xEV-DO Performance Monitoring Tools


Enhancements (FID 9253.1)

12-8

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
12-3
Issue 5, May 2008
See notice on first page

EVolution Data Optimized (EV-DO) Performance


Monitoring Tools Enhancements

Overview

Feature description: 1xEV-DO Tool Interface between OMP-FX and


1xEV-DO RNC (FID 9253.2)

12-11

Feature description: AT Trace Enhancement for Customer Use (FID


9253.3)

12-13

Feature interactions

12-15

Impacts on service measurements

12-16

Impacts on TI messages

12-17

Implementing the feature

12-26

Activating the feature: 1xEV-DO Performance Monitoring Tools


Enhancements

12-27

Activating the feature: AT Trace Enhancement for Customer Use

12-28

Manual Pages: AT Trace Enhancement for Customer Use

12-29

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

12-4

EVolution Data Optimized (EV-DO) Performance


Monitoring Tools Enhancements

Availability
...................................................................................................................................................................................................................................
Release availability

The following table identifies the AMPS/PCS software releases in which the 1xEV-DO
Performance Monitoring Tools Enhancements feature and related features are available.
Feature

Available in

1xEV-DO Performance Monitoring Tools


Enhancements (FID 9253.1)

Releases 27.0 and later

1xEV-DO Tool Interface between OMP-FX and


1xEV-DO RNC (FID 9253.2)

Releases 28.0 and later

AT Trace Enhancement for Customer Use (FID


9253.3)

Releases 30.0 and later

Market availability

The 1xEV-DO Performance Monitoring Tools Enhancements feature and related


features are available in the following markets:
Feature

Available in

1xEV-DO Performance
Monitoring Tools Enhancements
(FID 9253.1)

1xEV-DO markets only

1xEV-DO Tool Interface between


OMP-FX and 1xEV-DO RNC
(FID 9253.2)

1xEV-DO markets only

AT Trace Enhancement for


Customer Use (FID 9253.3)

1xEV-DO markets only

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
12-5
Issue 5, May 2008
See notice on first page

EVolution Data Optimized (EV-DO) Performance


Monitoring Tools Enhancements

Prerequisites
...................................................................................................................................................................................................................................
Introduction

The 1xEV-DO Performance Monitoring Tools Enhancements feature and related


features have the following prerequisites.
Supported technologies
1xEV-DO Performance Monitoring Tools Enhancements (FID 9253.1)

The 1xEV-DO Performance Monitoring Tools Enhancements optional feature is


supported in the following air-interface technologies:

in any band class

1xEV-DO Tool Interface between OMP-FX and 1xEV-DO RNC (FID 9253.2)

The 1xEV-DO Tool Interface between OMP-FX and 1xEV-DO RNC feature is
supported in the following air-interface technologies:

in any band class

AT Trace Enhancement for Customer Use (FID 9253.3)

The AT Trace Enhancement for Customer Use optional feature is supported in the
following air-interface technologies:

in any band class

HLR configuration
1xEV-DO Performance Monitoring Tools Enhancements (FID 9253.1)

The 1xEV-DO Performance Monitoring Tools Enhancements feature independent on


the Home Location Register (HLR) configuration.
1xEV-DO Tool Interface between OMP-FX and 1xEV-DO RNC (FID 9253.2)

The 1xEV-DO Tool Interface between OMP-FX and 1xEV-DO RNC feature is
independent on the HLR configuration.
AT Trace Enhancement for Customer Use (FID 9253.3)

The AT Trace Enhancement for Customer Use feature is independent on the HLR
configuration.
Software requirements
1xEV-DO Performance Monitoring Tools Enhancements (FID 9253.1)

The 1xEV-DO Performance Monitoring Tools Enhancements feature requires ECP


Release 27.0 or later.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

12-6

EVolution Data Optimized (EV-DO) Performance


Monitoring Tools Enhancements

Prerequisites

1xEV-DO Tool Interface between OMP-FX and 1xEV-DO RNC (FID 9253.2)

The 1xEV-DO Tool Interface between OMP-FX and 1xEV-DO RNC feature requires
ECP Release 28.0 or later. For OMC-RAN managed 1xEV-DO RNCs:

The 1xEV-DO OMC-RAN CORBA Agent - Radio Network Controller


(ORCA-RNC) (FID-12080.4) must be deployed. There is no feature dependency for
OMP-FX EMS managed 1xEV-DO RNCs.
Dependencies on 1xEV-DO Infrastructure for OMC-RAN CORBA Agent - Radio
Network Controller (ORCA-RNC) (FIDs 12080.1) feature and the OMC-RAN
EV-DO Radio Network Controller (RNC) Maintenance (FID 8017.14) feature.

AT Trace Enhancement for Customer Use (FID 9253.3)

The AT Trace Enhancement for Customer Use feature requires Release 30.0 or later.
The OMC-RAN must manage the 1xEV-DO RNC.
Hardware requirements
1xEV-DO Performance Monitoring Tools Enhancements (FID 9253.1)

The 1xEV-DO Performance Monitoring Tools Enhancements feature requires the


standard hardware in a CDMA Network and the following additional hardware:

OMP-FX v2

1xEV-DO Tool Interface between OMP-FX and 1xEV-DO RNC (FID 9253.2)

This 1xEV-DO Tool Interface between OMP-FX and 1xEV-DO RNC is supported on
both the OMP-FX and OMP-FX2.
AT Trace Enhancement for Customer Use (FID 9253.3)

The AT Trace Enhancement for Customer Use feature requires the standard hardware in
a CDMA Network and the following additional hardware:

OMP-FX
OMP-FX v2

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
12-7
Issue 5, May 2008
See notice on first page

EVolution Data Optimized (EV-DO) Performance


Monitoring Tools Enhancements

Feature description: 1xEV-DO Performance Monitoring Tools


Enhancements
(FID 9253.1)
...................................................................................................................................................................................................................................
Introduction

The following information describes the functionality, benefits, and operation of the
1xEV-DO Performance Monitoring Tools Enhancements (FID 9253.1) feature .
Functionality

The EV-DO Performance Monitoring Tools Enhancements feature introduces the


enhancement, Special Engineering Studies (SES) which provides data in histogram
form. It collects histogram metrics from cell sites supporting 1xEV carriers for capacity
planning purposes. The following data can be collected:

Datalink Downlink Throughput


Datalink Uplink Throughput
Percent busy
Short Term RSSI
Long Term RSSI

Each histogram is an hourly histogram. It shows the number of times each value was
pegged at the 10 second scan, not the distribution throughout the hour. To run a new
EVDO SES study, the FAF must be active.
Benefits

The 1xEV-DO Performance Monitoring Tools Enhancements feature collects and stores
user-specified counts in the form of histograms used for further study. These counts are
not traditional SM counts; they are collected and saved only when the SES command
is executed to collect these counts.
How the feature operates

The EVDO SES commands are executed on the OMP-FX II, which is required to run
this tool. These are not traditional TI commands and should not be confused as such.
The commands to start, stop, and collect a SES study are in /omp/bin on the OMP.
The studies are run directly on the OMP in either prompt mode or command line
mode.
Commands can also be run directly from the EMS CLI. Examples of the commands
are:

START:SES; RNC a [,DURATION b] [,HIST c] [,BTS d] - which means the data


will be collected for a given RNC and one BTS.
START:SES; RNC a [,DURATION b] [,HIST c] - by default all the BTSs.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

12-8

EVolution Data Optimized (EV-DO) Performance


Monitoring Tools Enhancements

Feature description: 1xEV-DO Performance Monitoring


Tools Enhancements (FID 9253.1)

Pegging begins when the user enters the following command at the UNIX prompt:

evstartses

Executing the above command causes all equipped RNCs to clear the data and start
collecting data. If a user attempts to start a new EVDO SES study before the
completion of the study that is currently running, the program will not start. The
current study needs to be stopped before a new SES study can start.
Specifying Duration of EVDO SES

The study runs for 1 hour by default and then automatically stops. The study can also
be run for durations from 1 hour to 24 hours with 1 hour increments. This is done by
adding a -t option, followed by the number of hours to run the study.
For example to run for 2 hours enter the following:

evstartses -t 2

The SES counts are collected for two hours and then the study stops.
Specifying Data Collection

The study collects all data by default. This study can also collect a subset of data by
adding a d Hist_List option where Hist_List can be:

1
2
3
4
5
6

Datalink DL throughput
Datalink UL throughput
Percent Busy
Short Term RSSI
Long Term RSSI
all, which is default

User may choose multiple data collections separated by commas or with a Hyphen (for
example: 1,2,4,5 or 1-3), but a combination of 6 with another number (1 to 5) will be
denied.
For example to run Datalink DL throughput and Percent Busy enter the following:

evstartses d 1,3

To run Percent Busy, Short Term RSSI, and Long Term RSSI enter the following:

evstartses d 3-5

Specifying RNC/BTSs to Collect Data

The study collects data from all RNCs on the service node by default. This study can
also collect data from a subset of RNCs or BTSs by using the r and b options. The
options r and b are mutually exclusive, meaning that if a user chooses the r option
to collect data from a subset of RNCs, data will be collected from all the BTSs on
those RNCs. If a user chooses the b option to collect data for a particular BTS, data
will be collected only from that particular BTS.
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
12-9
Issue 5, May 2008
See notice on first page

EVolution Data Optimized (EV-DO) Performance


Monitoring Tools Enhancements

Feature description: 1xEV-DO Performance Monitoring


Tools Enhancements (FID 9253.1)

For example, to run on RNCs 1, 2, and 3 on the service node enter the following:

evstartses r 1-3

To run on BTS xxx enter the following

evstartses bxxx

Specifying Prompt Mode

The user chooses the prompt mode option by entering:

evstartses P

The user will be prompted to enter data for command line options (-t, -d, -r, -b, and
o). The option P can not be used in combination with other command line options.
Specifying the Output File

Data is saved in an output file in the directory, /omp_data/logs/ses/evdo_files


with a default of yyyyMMddhhmmss.ServiceNode, where yyyyMMddhhmmss is the
time the data collection was started. A user can end the name of output file for the
study (add suffix to the name) by adding o option to the evstartses command.
For example, to add sesDatasuffix, run the following command:

evstartses o sesData

Then the output file appears as yyyyMMddhhmmss.sesData.


Specifying Usage Option

A user can get a Help Message for the usage of the command by adding h option.
SES Man Pages

Refer to Impacts on TI messages section for manual pages for evstatusses and
evstartses and for usage information on evstartses and the format of the output
file.
Only one SES session is allowed to be run on a service node

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

12-10

EVolution Data Optimized (EV-DO) Performance


Monitoring Tools Enhancements

Feature description: 1xEV-DO Tool Interface between OMP-FX


and
1xEV-DO RNC (FID 9253.2)
...................................................................................................................................................................................................................................
Introduction

The following information describes the functionality, benefits, and operation of the
1xEV-DO Tool Interface between OMP-FX and 1xEV-DO RNC feature.
Functionality

The 1xEV-DO Tool Interface between OMP-FX and 1xEV-DO RNC provides a new
interface between the OMP-FX and the ORCA-RNC for OMC-RAN managed RNCs.
Additionally, the TA tool user interface changes from an EMS CLI based interface to
an OMP-FX UNIX command interface for OMC-RAN managed 1xEV-DO RNCs.
This is supported on both the OMP-FX and OMP-FX v2 and is a standard feature.
Benefits

The 1xEV-DO Tool Interface between OMP-FX and 1xEV-DO RNC changes to AT
Trace tool user interface from an EMS CLI based interface to a OMP-FX UNIX
command interface for OMC-RAN managed 1xEV-DO RNCs. The interface changes
impact HOM and SES, with no noticeable difference to the subscriber.
How the feature operates

Some 1xEV-DO tools can be run from the OMP-FX. The SNMP interface between the
OMP-FX EMS and OMP-FX EMS managed 1xEV-DO RNCs is used for
communicating commands and responses. When the 1xEV-DO RNC is managed by the
OMC-RAN, the 1xEV-DO tools are still operated from the OMP-FX; however the
1xEV-DO RNC SNMP agent on that RNC is disabled. The 1xEV-DO Tool Interface
between OMP-FX and 1xEV-DO RNC feature provides a new interface between the
OMP-FX and the 1xEV-DO RNC so that the OMP-FX based 1xEV-DO tools will
continue to operate for OMC-RAN managed RNCs. As expected, these tools continue
to operate on the OMP-FX EMS managed 1xEV-DO RNCs also. The tools that use
this new interface are:

1xEV-DO Handoff Matrix (HOM)


1xEV-DO Special Engineering Studies (SES)
Test Application (TA)
AT Trace (Note that the AT Trace tool is available only to Technical Support)

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
12-11
Issue 5, May 2008
See notice on first page

EVolution Data Optimized (EV-DO) Performance


Monitoring Tools Enhancements

Feature description: 1xEV-DO Tool Interface between


OMP-FX and 1xEV-DO RNC (FID 9253.2)

Subscriber perspective

The 1xEV-DO Tool Interface between OMP-FX and 1xEV-DO RNC feature provides a
new interface between the OMP-FX and the ORCA-RNC for OMC-RAN managed
RNCs, but does not reflect the user impact of the feature. The old interface is SNMP
and this interface is not supported on OMC-RAN 1xEV-DOs. With this feature the
HOM tool supports both the legacy SNMP interface for EMS managed 1xEV-DO
RNCs and a new prorietary interface for OMC-RAN managed 1xEV-DO RNCs.
Without this feature the HOM tool could not be run against OMC-RAN managed
1xEV-DO RNCs.
Service provider perspective

The 1xEV-DO Tool Interface between OMP-FX and 1xEV-DO RNC feature also has
the following impacts:

For OMC-RAN managed RNCs, the service provider must use an OMP-FX UNIX
command to initiate/stop the Test Application (TA) tool instead of the EMS-CLI TA
command
For OMC-RAN managed RNCs, the service provider must use an OMP-FX UNIX
command to initiate/stop the AT Trace tool instead of the EMS-CLI AT Trace
command.
AT Trace data is automatically pulled by the OMP-FX and the post-processing tool
is available on the OMP-FX. Therefore Technical Support normally is not required
to login to the RNC to analyze the trace data.

These changes are made so that the service provider can run the TA and AT Trace tools
and analyze the data from the OMP-FX without having to login to the OMC-RAN or
the DO RNC.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

12-12

EVolution Data Optimized (EV-DO) Performance


Monitoring Tools Enhancements

Feature description: AT Trace Enhancement for Customer Use


(FID
9253.3)
...................................................................................................................................................................................................................................
Introduction

The following information describes the functionality, benefits, and operation of the AT
Trace Enhancement for Customer Use feature.
Functionality

The AT Trace Enhancement for Customer Use feature provides the capablilty of tracing
multiple ATs across the RNC boundaries under the same Service Node (SN), and be
capable of tracing an AT through A12/A13 interfaces in addition to the air interface
and A11 interface.
Benefits

The AT Trace Enhancement for Customer Use feature enhances internal use in the
follow aspects:

The logging and decoding of internal messages among major controlling functions,
Overhead Manager (OHM), Selector Function Manager (SFM), and Packet Control
Function (PFC)) in EV-DO RNC, which do not contain proprietary information.

How the feature operates

The AT Trace Enhancement for Customer Use feature is driven by external customers
who have requested the access to the AT Trace tool. Customers indicated that current
tools readily available do not provide the level of detailed information and visibility on
the EV-DO device activity. This AT Trace data helps to diagnose possible deficiencies
in protocol design and implementation and helps to understand the ever complicated
call processing activities, which include but not limited to Inter-frequency Handoff
(IFHO), RNC Grouping, and Radio Access Network (RAN) Authentication
Modifications.
By extending the infrastructure built under 1xEV-DO Tool Interface between OMP-FX
and 1xEV-DO RNC (FID 9253.2) feature wherein the AT Trace commands are
executed from the OMP-FX and the logged data is automatically pulled from APs
every 15 minutes, the enhanced AT Trace can trace target ATs across the whole Service
Node (SN) and users can enter either Unicast Access Terminal Identifier (UATI) or
Hardware ID (HW ID) or International Mobile Station Identity (IMSI) to start tracing
target ATs.
The AT Trace Enhancement for Customer Use feature provides AT Trace infrastructure
at the OMP and DO RNC for customer use. There is only one set of AT Trace
commands entered at the OMP-FX.
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
12-13
Issue 5, May 2008
See notice on first page

EVolution Data Optimized (EV-DO) Performance


Monitoring Tools Enhancements

Feature description: AT Trace Enhancement for Customer


Use (FID 9253.3)

The AT Trace Enhancement for Customer Use feature is under FAF control and
provides the following capabilities:

Tracing an AT across RNCs (within the Service Node) and in active/dormant/idle


states
Tracing multiple ATs, with a maximum number of four
Logging and decoding messages over the standard interfaces, such as HAI,
A11/12/13, which are used by the EV-DO RAN to talk to external entities such as
ATs, PDSNs, the AN-AAA, and neighboring RNCs
Enriching message headers to include rich ancillary information, such as (source),
(destination), (interface_id), (hw_id), (imsi), (uati_num), (proc_name), (year),
(month), (day), (hr), (min), (sec), (micro_sec), (time_zone), (AP/TP),
(hdrsnId.fmsId.apOrTPId), (message_name), (msgBytes)
There are 25 files allocated with size of 20MB each at an RNC to log the AT Trace
data.
If one file is filled up, a second file is used. Both are identified with the same
ATID but with different indices.
If all of the 25 files are used up, the files are over-written in chronological order.
Each evsrattr command starts writing into a new file even if the ATID remains
the same. The ATID and the time stamp are used to differentiate one file from the
other.

Performance

The OMP-FX is the control point for starting and stopping the AT Trace. There
currently is NO post-processing or parser tool available for AT Trace.
The start and stop commands are sent to all RNCs under the control of the OMP-FX
and the RNCs log the designated messages that pertain to the AT(s) based on the given
AT IDs. The logged messages are sent back from RNCs to the OMP-FX and stored at
the OMP-FX under the AT IDs to facilitate the data retrieving and post-processing.
The OMP-FX facilitates the access request for AT Trace data, either in raw or ASCII
format for a GUI based postprocessing tool such as MTA.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

12-14

EVolution Data Optimized (EV-DO) Performance


Monitoring Tools Enhancements

Feature
interactions
...................................................................................................................................................................................................................................
Introduction

The following feature interactions exist for these features.


1xEV-DO Performance Monitoring Tools Enhancements (FID 9253.1)

The 1xEV-DO Performance Monitoring Tools Enhancements feature interacts with no


other features.
1xEV-DO Tool Interface between OMP-FX and 1xEV-DO RNC (FID 9253.2)

The 1xEV-DO Tool Interface between OMP-FX and 1xEV-DO RNC feature interacts
with no other features.
AT Trace Enhancement for Customer Use (FID 9253.3)

The AT Trace Enhancement for Customer Use feature is dependent on the following
features:

1xEV-DO Trace Tool (FID 9253.0)


1xEV-DO Tool Interface between OMP-FX and 1xEV-DO RNC (FID 9253.2)

1xEV-DO Trace Tool (FID 9253.0)

This feature will allow tracing of all the network elements involved in a specific user
session including cell, RNC and PDSN.
1xEV-DO Tool Interface between OMP-FX and 1xEV-DO RNC (FID 9253.2)

The 1xEV-DO Tool Interface between OMP-FX and 1xEV-DO RNC feature provides a
new interface between the OMP-FX and the ORCA-RNC for OMC-RAN managed
RNCs.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
12-15
Issue 5, May 2008
See notice on first page

EVolution Data Optimized (EV-DO) Performance


Monitoring Tools Enhancements

Impacts
on service measurements
...................................................................................................................................................................................................................................
Introduction

For detailed information about the 1xEV-DO Performance Monitoring Tools


Enhancements feature service measurements, see CDMA2000 1xEV-DO Network
Service Measurements, 401-614-326.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

12-16

EVolution Data Optimized (EV-DO) Performance


Monitoring Tools Enhancements

Impacts
on TI messages
...................................................................................................................................................................................................................................
Introduction

The following information describes the impact of the 1xEV-DO Performance


Monitoring Tools Enhancements feature on input messages and output messages in the
Technician Interface (TI).
Collecting the EVDO SES Data. SES session status

Once the evstartses process starts a study, the data is ready to be collected after one
hour of automatic completion of the study or stopping the study by a user. A user can
determine if a SES session is currently running by entering

evstatusses

Specifying Stop Option

A user can stop a study gracefully by adding s option to the evstartses command.
The following command stops a study which has already been started:

evstartses s

The early stop command collects files from RNCs and aggregates them on an hourly
basis.
EVDO SES Output Format

The output file consists of header lines and records. The output file may have a
Warning line if there is an error such as incomplete data. The header lines contain the
file content and version, the service node, the requested duration, start and end times,
whether the session terminated normally or not, a list of requested histograms in the
study, and a list of RNCs/BTSs that participated in the study. The Warning line is used
to specify that an error occured during the collection of the data.
Files generated by the SES tool on the OMP are kept for no longer than 10 days and
purged if not otherwise removed. The user can prevent a file from being deleted by
moving it into a different directory or renaming the file.
Manual Page for evstatusses
ABSTRACT
evstatusses - A tool to query the status of an EVDO Special
Engineering Study (SES).
USAGE
evstatusses [ -h ] | [ -o File_name
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
12-17
Issue 5, May 2008
See notice on first page

EVolution Data Optimized (EV-DO) Performance


Monitoring Tools Enhancements

Impacts on TI messages

DESCRIPTION
This program queries the status of an SES session throughout
all 1xEV RNCs in the service node. The result is displayed
at the users terminal or may be directed to a file using
standard UNIX directives.
The 1xEV-DO Performance Monitoring Special Engineering Studies
Tool FAF takes no effect on the execution of this program.
NOTE: The status query will execute even when there was no
evstartses process running on the OMP. In this case, a message
will be printed on the users terminal to indicate that no SES
session was running. evstatusses always queries the session status
on all 1xEV RNCs, even if they had never participated in the SES
session.
OPTIONS
The following options are available:
-h displays the usage of the command.
NOTE: Option -h cannot be used together with
another option.
-o File_Name is used to specify the name of the status query report
file.
The file name is a string that could be up to
255 characters long. Valid values for characters are: A-Z, a-z, 0-9, .(dot), _(underscore) and -(hyphen).
If an invalid character is used and an error
message will be printed indicating invalid
file name.
Valid file name examples: Genius,
EVses.status, evses_011106.rpt,
temp.01-11-06
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

12-18

EVolution Data Optimized (EV-DO) Performance


Monitoring Tools Enhancements

Impacts on TI messages

Invalid file name examples: evses 01-11-06,


evses-01/11/06
NOTE: Option -o cannot be used together with another option.
EXAMPLES
evstatusses
Query the session status and print the
result to the users terminal.
evstatusses -o SESstatus
SESstatus Query the session status and store the status report in file
/omp-data/logs/ses/evdo_files/SESstatus.
FILES
/omp/bin/evstatusses
/omp-data/logs/ses/evdo_files: where status report file is
stored when -o option is given in command line.
DIAGNOSTICS
If the status query completes successfully on at least one
1xEV RNC, evstatusses exits with an exit code of zero. Otherwise
1 will be returned to indicate that the attempt of
status query failed.
The following table lists some of the possible error messages.
Exit Code Message
1 ERROR: Duplicated option -%c prohibited
1 ERROR: Invalid syntax
1 ERROR: Invalid option - -%c
1 ERROR: Option -%c requires an argument
1 ERROR: Invalid argument for option -o.
Refer to man page of evstatusses for the naming convention of a UNIX
file
1 ERROR: Option -%c cannot be duplicated,
or be used together with another option
1 Usage: evstatusses [-h] | [-o FILE_NAME] for example:
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
12-19
Issue 5, May 2008
See notice on first page

EVolution Data Optimized (EV-DO) Performance


Monitoring Tools Enhancements

Impacts on TI messages

1. evstatusses
2. evstatusses -o evses.status
3. evstatusses -h
1 ERROR: Failed to query status of the session

Manual Page for evstartses


ABSTRACT
evstartses - A tool to start or stop an EVDO Special
Engineering Study (SES)
USAGE
evstartses [ [-t Time] [-d Hist_List] [ [-r RNC_List] | [-b
BTS_Num] ] [-o Suffix_Name] ] | [-h] | [-s] | [-P]
DESCRIPTION
This program starts an EVDO Special Engineering Study on
1xEV RNCs, which are either specified by the user or, as the
default, all RNCs that are configured in SMconfig.data file
User can also stop the current study prematurely by running
this program with -s option, study data generated by that
time on participating RNCs will be collected.
If a user attempts to start a new EVDO SES study before the
end of currently running study, the request will be refused.
The early stop to a living SES session is allowed only when
the SES study is running on RNCs. Under the condition that
session has not yet been started successfully on RNCs or has
changed to collection status, command evstartses -s exits
with error.
The 1xEV-DO Performance Monitoring Special Engineering Studies
Tool FAF must be active to start EVDO SES study. When
the FAF is off, however, user can still run command
evstartses -s to stop a running SES study and start collection
immediately.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

12-20

EVolution Data Optimized (EV-DO) Performance


Monitoring Tools Enhancements

Impacts on TI messages

NOTE: Raw data files retrieved from all participating RNCs


will be aggregated into one study report file on hourly
basis on OMP. A hourly aggregated study report file may consume
maximum of 5.7 megabytes of disk space on the OMP-FX in
the directory /omp-data/logs/ses/evdo_files. The output
files will be removed after 10 days. As a result, if the
maximum configured EVDO RNC number is 6, there will be maximum
240 files if the user collects 24 hours every day for
10 days, and the total disk space occupied by SES aggregation files may be around 1.4GB. The disk_audit tool can be
used to ensure that space is available on the OMP.
OPTIONS
The following options are available:
-t Time The Duration of study in hours (1 - 24). The
default is 1 hour.
-d Hist_List The histogram counts list separated by commas
or hyphen (e.g. 1,2,4,5 or 1-3). The list may
contain one or more of the following numbers:
1 - Datalink DL throughput
2 - Datalink UL throughput
3 - Percent busy
4 - Short Term RSSI
5 - Long Term RSSI
6 - all, which is the default
NOTE: Number 6 is mutually exclusive with
other numbers.
-r RNC_List The RNC number list separated by commas or
hyphen (e.g. 1,10,15 or 20-22,18). Value of
the number ranges from 1 to 28. No more than
6 RNCs can be included in the list.
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
12-21
Issue 5, May 2008
See notice on first page

EVolution Data Optimized (EV-DO) Performance


Monitoring Tools Enhancements

Impacts on TI messages

NOTE: This option is mutually exclusive with


option -b.
-b BTS_Num The BTS number. Value of the number ranges
from 1 to 600.
NOTE: This option is mutually exclusive with
option -r.
-o Suffix_Name Suffix name of SES study report file.
When suffix name is given in command line,
the aggregation file name is composed of this
suffix name together with time stamp prefix,
looking like: yyyyMMddhhmmss.suffix_name. The
file name is a string that could be up to 255
characters long. Valid values for characters
are: A-Z, a-z, 0-9, .(dot), _(underscore) and
-(hyphen).
If an invalid character is used an error
message will be printed indicating invalid
file name.
Valid suffix name examples: Genius,
EVses.dat, evses_011106.rpt, 01-11-06,
Invalid suffix name examples: evses 01-1106, evses-01/11/06
-h displays the usage of the command.
NOTE: Option -h cannot be used together with
other options.
-s Stop the SES study prematurely.
NOTE: Option -s cannot be used together with
NOTE: Option -P Retrieve arguments for option -t, -d, -r, -b
and -o in prompt mode.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

12-22

EVolution Data Optimized (EV-DO) Performance


Monitoring Tools Enhancements

Impacts on TI messages

NOTE: Option -P cannot be used together with


another options.
EXAMPLES
evstartses starts an EVDO SES study for 1 hour on
all configured RNCs and BTSs in the service node.
The study covers all histo-gram counts.
Final study report file is with name in format:
yyyyMMddhhmmss.ServiceNode.
evstartses -t 10 starts an EVDO SES study for 10 hours
evstartses -d 5,1-3 -r 1,10,15-17 -o omptech
starts an EVDO SES study for 1 hour on
RNC1, 10, 15, 16, 17. The study covers
all histogram counts except Short Term
RSSI. Report file has the name of
yyyyMMddhhmmss.omptech.
evstartses -h displays the usage message for the user
FILES
/omp/bin/evstartses
/omp-data/logs/ses/evdo_files: where aggregated files are
stored
/omp-data/logs/ses/log_files: where log files are stored
/omp-data/logs/ses/raw_files: where raw data files are
stored
/omp-data/logs/ses/temp_files: where temporary files are
stored
DIAGNOSTICS
If the session starts successfully on at least one 1xEV RNC,
evstartses exits with an exit code of zero. Otherwise 1 will
be returned to indicate that the attempt to start the session failed.
In both cases, a list of RNCs on which the study started and some
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
12-23
Issue 5, May 2008
See notice on first page

EVolution Data Optimized (EV-DO) Performance


Monitoring Tools Enhancements

Impacts on TI messages

error messages are sent to the standard out.


The following table lists some of the possible error messages.
Exit Code Message
1 ERROR: Duplicated option -%c prohibited
1 ERROR: Invalid syntax
1 ERROR: Invalid option - -%c
1 ERROR: Option -%c requires an argument
1 ERROR: Option -%c and option -%c cannot be
used together
1 ERROR: Invalid value for option -t. Valid
range is from 1 to 24. Try again

1 ERROR: Invalid value for option -d. Valid


list can only include comma, hyphen and
number from 1 to 6. Try again
1 ERROR: Invalid value for option -r. Valid
list can only include comma, hyphen and
number from 1 to 28 and no more than total 6
1 ERROR: Invalid value for option -b. Valid
range is from 1 to 600. Try again
1 ERROR: Invalid argument for option -o. Refer
to man page of evstartses for the naming convention
of a UNIX file
1 ERROR: Option -%c cannot be used with other
options
1 ERROR: Failed on receiving valid argument of
option -%c for three times. evstartses exits
1 Usage: evstartses [ [-t Time] [-d Hist_List]
[-r RNC_List] [-b BTS_List] [-o file] ] | [h] | [-s] | [-P] for example:
1. evstartses
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

12-24

EVolution Data Optimized (EV-DO) Performance


Monitoring Tools Enhancements

Impacts on TI messages

2. evstartses -t 10 -d 1,2 -r 1-5 -o Genius


3. evstartses -t 24 -d 6 -b 599
4. evstartses -h
5. evstartses -s
6. evstartses -P
1 ERROR: Failed to input argument for option
-%c for up to %d times, evstartses exits
1 ERROR: Failed to initiate evstartses process
1 ERROR: Feature activation access failure,
evstartses exits
1 ERROR: 1xEV SES feature is not active,
evstartses exits
1 ERROR: Another evstartses process exists.
Wait for it to stop before trying again or run
evstartses -s command to stop it prematurely
1 ERROR: Failed to start a new SES session,
evstartses exits
1 ERROR: Failed to stop the SES session,
evstartses exits
1 ERROR: Failed to retrieve raw data files on
RNCs, evstartses exits
1 ERROR: Failed to do aggregation on OMP for
the session, evstartses exits

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
12-25
Issue 5, May 2008
See notice on first page

EVolution Data Optimized (EV-DO) Performance


Monitoring Tools Enhancements

Implementing
the feature
...................................................................................................................................................................................................................................
Overview

To implement the 1xEV-DO Performance Monitoring Tools Enhancements features,


perform the following procedure:
Activating the feature: 1xEV-DO Performance Monitoring Tools Enhancements
(p. 12-27)
Activating the feature: AT Trace Enhancement for Customer Use (p. 12-28)

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

12-26

EVolution Data Optimized (EV-DO) Performance


Monitoring Tools Enhancements

Activating the feature: 1xEV-DO Performance Monitoring


Tools
Enhancements
...................................................................................................................................................................................................................................
Purpose

This procedure activates the 1xEV-DO Performance Monitoring Tools Enhancements


feature in a 1xEV-DO Network.
Procedure

Perform the following steps:


...................................................................................................................................................................................................

Ask your account executive to activate the following entry in your Feature Activation
File (FAF):
1xEV-DO Performance Monitoring Special Engineering Studies Tool
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
12-27
Issue 5, May 2008
See notice on first page

EVolution Data Optimized (EV-DO) Performance


Monitoring Tools Enhancements

Activating the feature: AT Trace Enhancement for Customer


Use
...................................................................................................................................................................................................................................
Purpose

This procedure activates the AT Trace Enhancement for Customer Use feature in a
1xEV-DO Network.
Procedure

Perform the following steps:


...................................................................................................................................................................................................

Ask your account executive to activate the following entry in your Feature Activation
File (FAF):
1xEV-DO AT Trace Enhancement
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

12-28

EVolution Data Optimized (EV-DO) Performance


Monitoring Tools Enhancements

Manual
Pages: AT Trace Enhancement for Customer Use
...................................................................................................................................................................................................................................
Manual Page for evstarttr
evompfx100> evstarttr -h
USAGE
/omp/bin/evstarttr <-u uati|-i imsi|-e esn|-m meid> [-d duration]
[-r RAN_Interface_List] [-l] [-o] [-v]} [-h]
WHERE
-u uati - UATI # as 8-digit hex number with 0x prefix
-i imsi - IMSI # as 15 digit decimal number
-e esn - ESN # as 8-digit hex number with 0x prefix
-m meid - MEID # as 14 digit hex number with 0x prefix
-d duration - ATTrace test duration, 1..60 (min), this parameter will
default to 15 mins if omitted
-r intf_list - RNC interface list to trace - HAI, A11, A12, A13.
Default is all of these
-l - Enable Raw Format Logging of messages. Default is to log all
messages, including the ancillary information in ASCII format
-o - Override the overload rejection. This option forces the execution
of AT Trace start command even though one or more APs and/or TPs in an
RNC report overload conditions. Default behaviour when overload is
detected is to stop the trace in case the ATID being traced in UATI.
-v - Enables verbose mode that prints additional details contained in
the AT Trace response.
-h - prints the above help message
Note: If evstarttr with the -o option is used, then later, the TP used
in the AT Trace reports overload conditions, AT Trace data collection
will stop at the TP (SFM) only.

Manual Page for evstoptr


evompfx100> evstoptr -h
USAGE
/omp/bin/evstoptr <-u uati| -i imsi | -e esn | -m meid> [-h] [-v]
WHERE
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
12-29
Issue 5, May 2008
See notice on first page

EVolution Data Optimized (EV-DO) Performance


Monitoring Tools Enhancements

Manual Pages: AT Trace Enhancement for Customer Use

-u uati - UATI # as 8-digit hex number with 0x prefix


-i imsi - IMSI # as 15 digit decimal number
-e esn - ESN # as 8-digit hex number with 0x prefix
-m meid - MEID # as 14 digit hex number with 0x prefix
-v - Enables verbose mode that displays additional information
regarding the AT Trace RNC responses on the screen.
-h - display on-line help

Manual Page for evstatustr


evompfx100 root> evstatustr -h
USAGE
evstatustr [-x|-c] [-h]
WHERE
-x - prints details of the recently completed evstarttr commands (max
10)
-c - print details of currently running AT trace sessions
-h - prints this usage message
Default is to provide both the -x and -c outputs if no command line
arguments are present

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

12-30

13

13
Intra-Radio
Network Controller
(RNC) Session Resource
Balancing in EVolution Data
Optimized (1xEV-DO)

Overview
...................................................................................................................................................................................................................................
Purpose

This document describes the Intra-Radio Network Controller (RNC) Session Resource
Balancing in EVolution Data Optimized (1xEV-DO) optional feature in the
CDMA2000 1xEV-DO network.
Feature summary

The Intra-RNC Session Resource Balancing in 1xEV-DO allows the system to transfer
the control Overhead Manager (OHM) function from the Serving OHM, if the session
loading of the Serving OHM exceeds a certain threshold, minimizing the chance of
draining the session resource of a few Adjunct Processors (APs) while other APs still
have ample capacity. The session resource balance function in Intra-RNC Session
Resource Balancing in 1xEV-DO covers the intra-RNC case.
Feature Identifier (FID)

A unique Feature Identifier (FID) is assigned to each feature:

Intra-RNC Session Resource Balancing in 1xEV-DO (FID12458.0)

Impacts on user interfaces

The Intra-RNC Session Resource Balancing in 1xEV-DO affects the user interfaces that
are listed in the following table.
User interface

Feature impact

Feature Element Management System


(EMS) or Operations and Maintenance
center - Radio Access Network
(OMC-RAN)

None

....................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
13-1
Issue 5, May 2008
See notice on first page

Intra-Radio Network Controller (RNC) Session Resource


Balancing in EVolution Data Optimized (1xEV-DO)

Overview

User interface

Feature impact

Service measurements

See Impacts on service measurements


(p. 13-8).

Automatic Message Accounting (AMA)


subsystem

None

Technician Interface (TI) (input/output


messages)

See Impacts on TI messages (p. 13-11)

Intended audience

This document is intended for technicians, engineers, and system administrators who
implement or maintain the Intra-RNC Session Resource Balancing in 1xEV-DO
(FID12458.0) feature in a CDMA2000 1xEV-DO network.
To obtain technical support, documentation, and training or submit feedback

The Online Customer Support (OLCS) web site (http://support.lucent.com/) provides


access to technical support, related documentation, related training, and feedback tools.
The site also provides account registration for new users.
Contents
Availability

13-3

Prerequisites

13-4

Feature description

13-5

Feature interactions

13-7

Impacts on service measurements

13-8

Impacts on TI messages

13-11

Implementing the feature

13-14

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

13-2

Intra-Radio Network Controller (RNC) Session Resource


Balancing in EVolution Data Optimized (1xEV-DO)

Availability
...................................................................................................................................................................................................................................
Release availability

The Intra-RNC Session Resource Balancing in 1xEV-DO feature is available in ECP


Releases 29.0 and later.
Market availability

The Intra-RNC Session Resource Balancing in 1xEV-DO feature is available in all


markets.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
13-3
Issue 5, May 2008
See notice on first page

Intra-Radio Network Controller (RNC) Session Resource


Balancing in EVolution Data Optimized (1xEV-DO)

Prerequisites
...................................................................................................................................................................................................................................
Introduction

The Intra-RNC Session Resource Balancing in 1xEV-DO feature has the following
prerequisites.
Supported technologies

The Intra-RNC Session Resource Balancing in 1xEV-DO feature is supported in the


following air-interface technologies:

1xEV-DO

HLR configuration

The Intra-RNC Session Resource Balancing in 1xEV-DO feature does not use a Home
Location Register (HLR) configuration.
Software requirements

The Intra-RNC Session Resource Balancing in 1xEV-DO feature requires ECP Release
29.0 or later.
Hardware requirements

The Intra-RNC Session Resource Balancing in 1xEV-DO feature requires no hardware


beyond the standard hardware in a CDMA2000 1xEV-DO network.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

13-4

Intra-Radio Network Controller (RNC) Session Resource


Balancing in EVolution Data Optimized (1xEV-DO)

Feature
description
...................................................................................................................................................................................................................................
Introduction

The following information describes the functionality, benefits, and operation of the
Intra-RNC Session Resource Balancing in 1xEV-DO (FID12458.0) feature.
Functionality

The Intra-RNC Session Resource Balancing in 1xEV-DO feature replaces existing


session establishment/releases related per AP Service Measurement (SM) counts with
per OHM SM counts, improving data correlation. It also balances sessions.
Benefits

The Intra-RNC Session Resource Balancing in 1xEV-DO improves the RNC to handle
UATI session resource more efficiently, minimizing the chance of draining the session
resource of a few APs while other APs in the system still have ample capacity to serve
user sessions. The Intra-RNC Session Resource Balancing in 1xEV-DO focuses mainly
on improving the UATI session resource loading distribution, processor loading and
performance impacts are also taken into consideration in the balancing algorithm.
How the feature operates

The Intra-RNC Session Resource Balancing in 1xEV-DO provides greater flexibility in


balancing session use within each RNC. The Intra-RNC Session Resource Balancing in
1xEV-DO implements an UATI session balancing scheme to mitigate the UATI session
imbalance that may occur across OHMs due to an imbalance in cell traffic, and
changes in the session distribution due to AT mobility. Each OHM keeps track of its
session loading, which is the ratio of open UATI sessions to total UATI sessions an
OHM can support. When a new session is requested, if the cell serving OHMs session
loading exceeds a threshold, it may choose to transfer the session to another less
loaded OHM in the RNC.
The Intra-RNC Session Resource Balancing in 1xEV-DO provides:

a convenient mechanism for enabling, disabling, and configuring session balancing,


accomplished via operator configured parameters.
warnings and alarms when the session loading is reaching critical levels.
mechanisms to observe real time session loading status, accomplished via new CLI
commands.
Important! These commands supplement the Service Measurements which provide
tools for trending.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
13-5
Issue 5, May 2008
See notice on first page

Intra-Radio Network Controller (RNC) Session Resource


Balancing in EVolution Data Optimized (1xEV-DO)

Feature description

The Intra-RNC Session Resource Balancing in 1xEV-DO is an optional feature. A FAF


entry is implemented along with a parameter that allows the operator to enable/disable
the feature on per RNC basis.
Each OHM is in three different session load states:

Normal state session load is below Intra-RNC UATI session balance threshold
Balance State session load is between Intra-RNC UATI session balance threshold

and UATI session overload threshold


Session Overload State session load is above the UATI session overload
threshold

The OHM considers a session balance only when it is in Balance State or in Session
Overload State. The OHM only transfers a session to another OHM that is in a lower
session load state. When the OHM is in 100% load, it will consider all available
OHMs that are not 100% loaded as an candidate for balancing.
The operator can also view the OHM session loading via two new CLI commands:

OP:EVDORNC-SESSIONLOAD

- provides an RNC wide UATI session loading report


OP:AP-SESSIONLOAD - provides a UATI session loading report for the OHM
assigned to the specified AP, and for the OHM assigned to the mate AP.

Alarms

The Intra-RNC Session Resource Balancing in 1xEV-DO feature introduces two new
alrams:

UATI session overload alarm threshold:

If the OHMs session loading


exceeds this threshold, the RNC generates a major alarm. It is recommended that
the operator set this threshold above the UATI session overload threshold when the
feature is enabled.
RNC UATI session overload alarm threshold: If the average aggregate UATI
session loading across all OHMS in the RNC exceeds this threshold, the RNC
generates a critical alarm.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

13-6

Intra-Radio Network Controller (RNC) Session Resource


Balancing in EVolution Data Optimized (1xEV-DO)

Feature
interactions
...................................................................................................................................................................................................................................
Introduction

The Intra-RNC Session Resource Balancing in 1xEV-DO feature interacts with no


other features.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
13-7
Issue 5, May 2008
See notice on first page

Intra-Radio Network Controller (RNC) Session Resource


Balancing in EVolution Data Optimized (1xEV-DO)

Impacts
on service measurements
...................................................................................................................................................................................................................................
Introduction

The Intra-RNC Session Resource Balancing in 1xEV-DO feature affects the following
categories of services measurements:

OHM counts
HDRC SI counts
HDRC counts

OHM counts

The Intra-RNC Session Resource Balancing in 1xEV-DO feature affects the 1xEV-DO
service measurements that are identified in Table 13-1, 1xEV-DO service
measurements - OHM Counts (p. 13-8).
Table 13-1

1xEV-DO service measurements - OHM Counts

Count abbreviation

Count name

AVG_SESS_LOAD_OHM

Average Session Loading

OHM_SESS_CAPACITY

OHM_SESS_CAPACITY

SESS_BAL_REQ_INTRA_RNC_ORIG_
OHM

Intra-RNC Session Balance Requests at


Originating OHM

SESS_BAL_UATI_COMPLETE_RCVD_
ORIG_OHM

Intra-RNC Session Balance - UATI


Complete Message Received

SESS_BAL_SUCCESS_INTRA_RNC_ORIG_Intra-RNC Successful Session Balances at


OHM
Originating OHM

HDRC counts

The Intra-RNC Session Resource Balancing in 1xEV-DO feature affects the 1xEV-DO
service measurement counts in that the OHM is performing the work of making the
count, peg be the Target OHM, instead of the Originating OHM. The affected counts
are identified inTable 13-2, 1xEV-DO service measurements - SECT-CARR-HDRC
Counts (p. 13-8).
Table 13-2

1xEV-DO service measurements - SECT-CARR-HDRC Counts

Count abbreviation

Count name

INT_SUBNET_IDLE_TRFR_A13_SIR_
RCVD_LATE

Inter-subnet idle transfer A13 sess info rsp


msg rcvd late

INT_SUBNET_IDL_TRFR_ATTMPT

1xEV inter-subnet idle transfer attempt

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

13-8

Intra-Radio Network Controller (RNC) Session Resource


Balancing in EVolution Data Optimized (1xEV-DO)

Table 13-2

Impacts on service measurements

1xEV-DO service measurements - SECT-CARR-HDRC Counts


(continued)

Count abbreviation

Count name

INT_SUBNET_IDL_TRFR_FAIL_OTHER_ Inter-Subnet Idle Transfer Failures Due to


REASON
Other Reasons
ISBNT_IDL_TRFR_FAIL_NO_RSP_PRV_
SBNET

Inter-Subnet Idle Transfer Failures Due to


No Response from Previous Subnet

ISBNT_IDL_TRFR_FAIL_ORG_PDSN_
CANT_CONN

Inter-Subnet Idle Transfer Failures


Because the Original PDSN Cannot
Connect

ISBNT_IDL_TRFR_FAIL_RJCT_MSG_
RCVD

Inter-Subnet Idle Transfer Failure Because


a Reject Message is Received

ISBNT_IDL_TRFR_FAIL_SRC_IP_ADR_
NT_FOUND

Inter-subnet idle transfer attempt fail-Srce


IP addr not found

SESS_SETUP_ISBNT_UATI_ASSGN_MSG_ Inter-subnet idle transfer attempt fail-Srce


SENT
IP addr not found
SESS_SETUP_ISBNT_UATI_ASSGN_MSG_ Session Setup - Inter-Subnet Handoff
SENT
UATI Assignment Message Sent
SESS_SETUP_UATI_COMPLETE_MSG_
RCVD

Session Setup - Inter-Subnet Handoff


UATI Complete Message Received

SESS_SETUP_UATI_ASSGNMT_MSG_
SENT

Session Setup - Inter-Subnet Handoff


UATI Assignment Message Sent

SESS_SETUP_UATI_COMPLETE_MSG_
RCVD

Session Setup - Inter-Subnet Handoff


UATI Complete Message Received

HDRC SI counts

The Intra-RNC Session Resource Balancing in 1xEV-DO feature affects the 1xEV-DO
service measurement counts in that the OHM is performing the work of making the
count, peg be the Target OHM, instead of the Originating OHM. The affected counts
are identified in Table 13-3, 1xEV-DO service measurements - SECT-CARR-HDRC
CI Counts (p. 13-9).
Table 13-3

1xEV-DO service measurements - SECT-CARR-HDRC CI Counts

Count abbreviation

Count name

SESS_SETUP_UATI_ASSGNMT_MSG_
SENT_Q

Session Setup - UATI Assignment


Message Sent

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
13-9
Issue 5, May 2008
See notice on first page

Intra-Radio Network Controller (RNC) Session Resource


Balancing in EVolution Data Optimized (1xEV-DO)

Table 13-3

Impacts on service measurements

1xEV-DO service measurements - SECT-CARR-HDRC CI Counts


(continued)

Count abbreviation

Count name

SESS_SETUP_UATI_COMPLETE_MSG_
RCVD_Q

Session Setup - UATI Complete Message


Received

References

For detailed information about 1xEV-DO service measurements, see, CDMA2000


1xEV-DO Service Measurements, 401-614-326.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

13-10

Intra-Radio Network Controller (RNC) Session Resource


Balancing in EVolution Data Optimized (1xEV-DO)

Impacts
on TI messages
...................................................................................................................................................................................................................................
Introduction

The following information describes the impact of the Intra-RNC Session Resource
Balancing in 1xEV-DO feature on input messages and output messages in the
Technician Interface (TI).
Input messages

The following input messages are new commands and support the Intra-RNC Session
Resource Balancing in 1xEV-DO feature:

OP:EVDORNC-SESSIONLOAD

The 1xEV-DO RNC supports a command to retrieve the UATI Session Loading
status for the RNC.

OP:AP-SESSIONLOAD

The 1xEV-DO RNC supports a command to retrieve the UATI session loading
status for the OHM assigned to the AP and the OHM assigned to the APs mate
AP.
Output messages

In response to the OP:EVDORNC-SESSIONLOAD command, if successful, the RNC


provides the following information in its output report.
Important! The following information is provided if the Intra-RNC Session
Resource Balancing in 1xEV-DO (FID12458.0) feature is enabled RNC UATI
Session Loading (percentage; averaged across the RNC).
The following information is provided if the Intra-RNC UATI Session Status Reporting
Enable is y:

Intra-RNC UATI session balance threshold

UATI session overload threshold


Number of OHMs with session loading status = Normal
Number of OHMs with session loading status = Balance
Number of OHMs with session loading status = Overload
Number of open (UATI) sessions - aggregated across the RNC
Number of open (UATI) sessions without R-P sessions - aggregated across the
RNC
Number of active sessions - aggregated across the RNC

The following per-OHM information is provided regardless of whether the Intra-RNC


Session Resource Balancing in 1xEV-DO (FID12458.0) feature is enabled and
regardless of the Intra-RNC UATI Session Status Reporting Enable setting.
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
13-11
Issue 5, May 2008
See notice on first page

Intra-Radio Network Controller (RNC) Session Resource


Balancing in EVolution Data Optimized (1xEV-DO)

Impacts on TI messages

For each active OHM that is assigned to an equipped AP, provide:

OHM Number
AP the OHM is active on
Session loading status: Normal, Balance, Overload, or Unavailable
Session load (shown as a percentage)
Number of open (UATI) sessions
Number of open (UATI) sessions without R-P sessions
Important! If the RNC cannot provide any of the above information, a report an
error message is run with an appropriate reason. If the RNC cannot provide
information for one or more OHM or if an OHM is not responding, then that OHM
is omitted.

In response to the OP:AP-SESSIONLOAD command, if successful, the RNC provides the


following information in its output report for the OHM assigned to the AP and the
OHM assigned to the mate AP.
The following information is provided if the Intra-RNC UATI Session Status Reporting
Enable is y:

Intra-RNC UATI session balance threshold


UATI session overload threshold

Per OHM information included in the OP:EVDORNC-SESSIONLOAD report is provided


regardless of whether Intra-RNC Session Resource Balancing in 1xEV-DO
(FID12458.0) is enabled and regardless of the Intra-RNC UATI Session Status
Reporting Enable setting session reporting is enabled:

List of other OHMs assigned to equipped APs in the RNC


Session loading status for each OHM

If the OHM is in a pool, but not being used, include the reason why. Valid reasons
include:

OHM session load is 100%


AP is in overload Intra-RNC
Session balance feature is disabled

If the RNC cannot provide the above information, it report an error message with an
appropriate reason.
If an OHM is not responding, then that OHM is omitted.
References

For detailed descriptions of those input messages, see CDMA2000 Wireless Networks
Input Messages, 401-610-055.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

13-12

Intra-Radio Network Controller (RNC) Session Resource


Balancing in EVolution Data Optimized (1xEV-DO)

Impacts on TI messages

For detailed descriptions of those output messages, see CDMA2000 Wireless


Networks Output Messages, 401-610-055.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
13-13
Issue 5, May 2008
See notice on first page

Intra-Radio Network Controller (RNC) Session Resource


Balancing in EVolution Data Optimized (1xEV-DO)

Implementing
the feature
...................................................................................................................................................................................................................................
Overview

The Intra-RNC Session Resource Balancing in 1xEV-DO feature is FAFable.


An operator configurable parameter, Intra-RNC UATI Session Resource Balancing
Enable, at the FMS Frame level, is used to enable/disable the feature when the
Intra-RNC Session Resource Balancing in 1xEV-DO (FID 12458.0) FAF entry exists.
Thresholds to configure the balance algorithm: UATI session load balance threshold
UATI session overload threshold Alarm thresholds: OHM UATI session overload alarm
threshold RNC UATI session overload alarm threshold
Important! While this feature is FAFable, it is also disabled as a default, and needs
to be enabled at the FMS Frame level for implementation.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

13-14

14

14
Inter-User
Priority for Best
Effort Data Applications
(IUPBEDA)

Overview
...................................................................................................................................................................................................................................
Purpose

This chapter describes Inter-User Priority for Best Effort Data Applications
(IUPBEDA) feature in the CDMA2000 1xEV-DO network.
Feature summary

The IUPBEDA feature provides levels of Best Effort (BE) data service on the Forward
Link based upon the Inter-User Priority attribute assigned to each user in the
Accounting, Authentication, and Authorization (AAA) subscriber profiles. Service
providers can set the relative weights associated with each Inter-User Priority value.
This feature is available on the CDMA2000 1xEV-DO network.
Feature Identifier (FID)

The Feature Identifier (FID) of the IUPBEDA feature is FID 12171.4.


Impacts on user interfaces

Important! The OMC-RAN is the only recommended method for enabling the IUP
and JP features.
The IUPBEDA feature affects the user interfaces that are listed in the following table:
User interface

Feature impact

Accounting,
Authentication, and
Authorization
(AAA)

See Impacts on the AAA network element (p. 14-15).

Automated Message
Accounting (AMA)

None

....................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
14-1
Issue 5, May 2008
See notice on first page

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Overview

User interface

Feature impact

Element
Management System
(EMS)

None

Operations and
Maintenance Center
- Radio Access
Network
(OMC-RAN)

See Impacts on the OMC-RAN network element (p. 14-17).

Service
measurements

See Impacts on service measurements (p. 14-23).

Technician Interface
(TI) (input/output
messages)

None

Intended audience

This document is intended for technicians, engineers, and system administrators who
implement or maintain the Public Security feature and/or related features in a
CDMA2000 1xEV-DO network.
To obtain technical support, documentation, and training or submit feedback

The Online Customer Support (OLCS) web site (http://support.lucent.com/) provides


access to technical support, related documentation, related training, and feedback tools.
The site also provides account registration for new users.
Contents
Availability

14-4

Prerequisites

14-5

Feature description

14-6

Feature interactions

14-9

Sample call scenarios

14-10

Impacts on the AAA network element

14-15

Impacts on the OMC-RAN network element

14-17

Impacts on service measurements

14-23

Configuration and implementation considerations

14-26

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

14-2

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Overview

Implementing the feature

14-29

Activating the feature

14-30

Confirming feature activation

14-31

Adjusting the IUP weight assignments for the Service Node

14-32

Adjusting the IUP weight assignments for a BTS

14-34

Setting Inter-User Priority attribute in AAA subscriber profile

14-36

Enabling the feature

14-37

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
14-3
Issue 5, May 2008
See notice on first page

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Availability
...................................................................................................................................................................................................................................
Release availability

The IUPBEDA feature is available in EVDO Release 29.0 SU29-0002 and later.
Market availability

The IUPBEDA feature is only available for the North American Region (NAR) Public
Safety application.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

14-4

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Prerequisites
...................................................................................................................................................................................................................................
Introduction

The IUPBEDA feature has the following prerequisites.


Supported technologies

The IUPBEDA feature is supported in the following air-interface technology:

1xEV-DO

Software requirements

The IUPBEDA feature has the following software requirements:

The Base Transceiver System (BTS) software release must be R29.1 or later
The Radio Network Controller (RNC) software release must be R29.0 SU29-0002
or later
The Operations and Maintenance Center - Radio Access Network (OMC-RAN)
software release must be R29.0 SU2 or later
The 1xEV-DO Application based Quality of Service (QoS) support for High Rate
Packet Data Revision A (Rev. A) (HRPD Rev. A) (FID 12078.9) must be activated

Hardware requirements

The IUPBEDA feature requires no other hardware beyond the standard hardware in a
CDMA2000 1xEV-DO network.
Interface requirements

The IUPBEDA feature has the following interface requirements:

The AAA network element must be capable of supporting the Inter-User Priority
attribute in the Subscriber Profile.
The Packet Data Packet Data Serving Node (PDSN) must be capable of supporting
the Inter-User Priority attribute in the Subscriber QoS Profile.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
14-5
Issue 5, May 2008
See notice on first page

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Feature
description
...................................................................................................................................................................................................................................
Introduction

The following information describes the functionality, benefits, and operation of the
IUPBEDA feature.
Functionality

The IUPBEDA feature provides different levels of Best Effort (BE) data service on the
Forward Link based upon the inter-user priority in a users AAA subscriber profile.
The objective is to provide higher though-put for general purpose BE service category
data traffic to certain users relative to other users (given similar Radio Frequency (RF)
conditions).
A set of 8 different inter-user priorities (0 to 7) are supported. Service providers can
assign a weight to each of these inter-user priority values and these weights are used to
adjust scheduling of the transmission of data packets on the Forward Link (data
downloaded to a users terminal) of 1xEV-DO Best Effort data connections.
Benefits

The IUPBEDA feature allows service providers to assign priorities for individual users
and the network will take those priorities into consideration when transmitting packets
on the Forward Link. In general, users with a high priority will have improved data
throughput versus users with lower priorities (given similar RF conditions) especially
under conditions where network usage is unusually high.
How the feature operates

The IUPBEDA feature involves the following activities:


1. The RNC receives the Inter-User Priority value from the PDSN as part of the
subscriber profile from AAA. The Inter-User Priority value is saved for the users
session.
2. The RNC calculates the Inter-User Priority weight associated with each call leg by
doing the following:
a. Use the Inter-User Priority Weight value for the serving BTS if a weight value
has been provisioned for the current Inter-User Priority value in the associated
Cell Site table.
b. Otherwise, use the Inter-User Priority Weight value for the current Inter-User
Priority value for the Service Node (SN).

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

14-6

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Feature description

3. The RNC passes the Inter-User Priority Weight to each BTS that supports a data
connection when the connection is established or when a new call leg is added.
4. The BTS accepts the Inter-User Priority Weight and uses this value when
scheduling data packet transmission on the Forward Link of Best Effort data
connections. This weight is used in conjunction with other factors that affect data
packet transmission scheduling (signal strength).
Subscriber perspective

The IUPBEDA feature allows subscribers with higher priority weights to receive higher
data throughput on the Forward Link of Best Effort data connections than other
subscribers with lower priority weights given the same RF conditions. Subscribers with
the same priority weights and equal signal strength will be given equal treatment by
the BTS when transmitting data packets.
These priority weights have an impact on data throughput only when subscribers with
different priority weights are served by the same BTS. Please note that the full impact
of these priority weights is most evident when there is a high level of data traffic on
the Forward Link.
Service-provider perspective

The IUPBEDA feature allows the service provider to give select subscribers higher
priority access to Best Effort data services.
Example of feature operation

To illustrate how this feature operates, please consider the following example.
1. A subscriber is assigned an Inter-User Priority of 6 for Best Effort Data in the
AAA server.
2. The subscriber initiates a 1xEV-DO Rev A connection using an Access Terminal
(AT).
3. The AT is served by BTS 1, BTS 2, and BTS 3, but the Forward Link (FL) is only
transmitted by the serving (primary) BTS which can provide the AT with the
strongest signal.
Figure 14-1, Example Application of the Inter-User Priority for Best Effort Data
Applications feature (p. 14-8) shows the AT with an active connection served by the
three BTSs and the associated priority-to-weight mappings. In this example, we shall
observe the effect of these priority-to-weight mappings when support of the Forward
Link switches from one BTS to another.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
14-7
Issue 5, May 2008
See notice on first page

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Feature description

Figure 14-1 Example Application of the Inter-User Priority for Best Effort Data
Applications feature

BTS 2

BTS 1
BTS 3

Subscribers Inter-User Priority = 6

Resulting IUP weight on FL for Best Effort Flow *


BTS 1 = 3,
BTS 2 = 7,
BTS 3 = 6
* = when BTS handles FL transmission

Inter-User Priority Weight

Inter-User
Priority

BTS 1

BTS 2

BTS 3

SN

0.25

0.50

Blank

0.50

Blank

Blank

Blank

Blank

Blank

Blank

Blank

unknown

Blank

Table A: Inter-User Priority Weights

In this example, the priority-to-weight mappings for BTS 1 yield an Inter-User Priority
Weight of 3. The mappings defined for BTS 2 yield a weight of 7.
Please note that BTS 3 has no priority-to-weight mappings defined. In this case, we
must use the system-wide mappings for the SN. Consequently, a weight of 6 will be
used on BTS 3.
It should also be noted that in this example different priority weights are being sent to
each of the BTSs associated with the call. The priority weight associated with the
serving BTS is the value that will affect scheduling for the FL. If another BTS
becomes the serving BTS, then the priority weight associated with the new serving
BTS will then affect the FL scheduling.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

14-8

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Feature
interactions
...................................................................................................................................................................................................................................
Introduction

The following information describes the interactions that may occur between the
IUPBEDA feature and the following features:

Application Based Quality of Service (QoS) Support for HRPD Rev. A (FID
12078.9)
Jurisdictional Priority for Public Safety Users for Best Effort Data (FID 12171.5)

Application Based Quality of Service (QoS) Support for HRPD Rev. A (FID
12078.9) feature

The IUPBEDA feature depends on FID 12078.9 for the basic Rev. A interfaces. For
example, the Inter-User Priority attribute is part of the Subscriber QoS Profile passed
by the PDSN and FID 12078.9 provides the support of the Subscriber QoS Profile in
the CDMA2000 1xEV-DO network. However, there is no other feature interaction.
The IUPBEDA feature has no impact on the operation of the Application Based
Quality of Service Support for HRPD Rev. A (FID 12078.9) feature.
Jurisdictional Priority for Public Safety Users for Best Effort Data (FID 12171.5)
feature

Although the IUPBEDA feature does not depend on JPPSUBEDA FID 12171.5, the
operation of the IUPBEDA feature can be affected by FID 12171.5. The IUPBEDA
feature calculates the Inter-User Priority Weights to be used for calls (based on the
Inter-User Priority associated with a user) and handles the adjustment of data packet
transmission scheduling in the BTS based on these priority weights. However,
JPPSUBEDA FID 12171.5 may adjust the Inter-User Priority values associated with
individual users based upon the defined jurisdictional policies. The adjustment of the
Inter-User Priority values will, in turn, cause changes in the level of service various
users will receive on the Forward Link of Best Effort data connections.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
14-9
Issue 5, May 2008
See notice on first page

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Sample
call scenarios
...................................................................................................................................................................................................................................
Introduction

The following information describes call scenarios for the IUPBEDA feature.
Establishment of New Data Session

The call flow in Figure 14-2, Establishment of New Data Session with Inter-User
Priority (p. 14-11) describes the successful in initial establishment of a data session in
which the Inter-User Priority attribute was included in the subscriber profile.
Note, that only the numbered messages are affected by the IUPBEDA feature.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

14-10

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Sample call scenarios

Figure 14-2 Establishment of New Data Session with Inter-User Priority


AT

RAN

PDSN

AAA

Session Configuration
Traffic Channel Establishment
XonRequest

A11 RRQ
A11 RRP

XonResponse

A11 RRQ
A11 RRP

PPP Configuration and Authentication

[1] RADIUS
Request
[2] RADIUS Accept

[3] A11 Session Update

(with Inter-User Priority)

(with Inter-User Priority)

[4] Get QoS Profile

A11 SU ACK

IP Address Assignment
AttributeUpdateRequest

(ReservationKKQoSRequestFWD and Rev)

AttributeUpdateAccept
AttributeUpdateRequest

(1 per each bidirectional reservation)

AttributeUpdateAccept

A11 RRQ
A11 RRP

Resv (Traffic Flow Template)


ResvConf

Message
Label

Establishment of New Data Session with Inter-User Priority

[1]

During the establishment of a data session, the PDSN sends a RADIUS


Request to the AAA server order to retrieve the subscriber profile of the
user.

[2]

AAA responds to the RADIUS Request with a RADIUS Response. The


RADUIS Response includes the subscriber profile. The 3GPP2-Inter-UserPriority attribute is included in the subscriber profile.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
14-11
Issue 5, May 2008
See notice on first page

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Sample call scenarios

Message
Label

Establishment of New Data Session with Inter-User Priority

[3]

The PDSN accepts the RADIUS Response and forwards the subscriber
profile information to the RAN in the A11 Session Update message. The
Inter-User Priority attribute is included as part of the Subscriber QoS
Profile attribute.

[4]

The RAN (the RNC component of the RAN) receives the A11 Session
Update message and stores the Inter-User Priority with the users session
data.

Reactivation of Existing Data Session

The call flow in Figure 14-3, Reactivation of existing data session with IUPBEDA
enabled (p. 14-13) describes the successful establishment of a new data connection in
which an Inter-User Priority value has been specified for the user. In this case, the data
session was established previously, but the active connection was dropped when the
data session became dormant prior to this effort to re-establish the active connection

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

14-12

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Sample call scenarios

Figure 14-3 Reactivation of existing data session with IUPBEDA enabled


RNC

BTS1

AT
[1] RU+CR+RoR

BTS 2

[2] ACPI (RU+CR+RoR)


[3] AllocateTrafficChannelReq

[4] AllocateTrafficChannelReq

(InterUserPriority &
1)
InterUserPriority Weight
AllocateTrafficChannelRsp
TCA+ReservationAccept
(on Control Channel)

AllocateTrafficChannelRsp

SCCPC(TCA+RA)

MobileAcquiredInd
RTCAck

(InterUserPriority &
2)
InterUserPriority Weight

SFPC(RTCAck)

MobileAcquiredInd
SFPC(RTCAck)

RTCAck
TCC (on RTC)
TCC (on RTC)

RPI(TCC)

RPI(TCC)

Message
Label

Reactivation of Existing Data Session with IUPBEDA Enabled

[1]

The AT sends ConnectionRequest, RouteUpdate, and


ReservationOnRequest messages to request the establishment of a Best
Effort data connection.

[2]

The BTS will then forward the received ConnectionRequest,


RouteUpdate, and ReservationOnRequest messages on to the RNC.

[3]

The RNC will calculate Inter-User Priority Weight to be sent to BTS1


using the Inter-User Priority value in the users session data and
priority-to-weight mappings that have been defined for BTS1. If no
priority-to-weight mappings have been defined for BTS1, then the
priority-to-weight mappings for the SN will be used. The calculated
Inter-User Priority Weight will be passed to the BTS within the
AllocateTrafficChannelReq message.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
14-13
Issue 5, May 2008
See notice on first page

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Sample call scenarios

Message
Label

Reactivation of Existing Data Session with IUPBEDA Enabled

[4]

The RNC will calculate Inter-User Priority Weight to be sent to BTS2


using the Inter-User Priority value in the users session data and
priority-to-weight mappings that have been defined for BTS2. If no
priority-to-weight mappings have been defined for BTS2, then the
priority-to-weight mappings for the SN will be used.
Note: that Inter-User Priority Weight associated with BTS2 will be
different than Inter-User Priority Weight, associated with BTS1 if
different priority-to-weight mappings are defined for BTS1 and BTS2.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

14-14

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Impacts
on the AAA network element
...................................................................................................................................................................................................................................
Introduction

The following information describes the impact of the IUPBEDA feature on the AAA
network element.
AAA subscriber profile attribute

The IUPBEDA feature affects the AAA subscriber profile attribute that is listed in
Table 14-1, Related AAA subscriber profile attributes (p. 14-15).
Table 14-1

Related AAA subscriber profile attributes

AAA subscriber profile attribute

Impacted by

3GPP2-Inter-User-Priority

IUPBEDA - FID 12171.4


JPPSUBEDA - FID 12171.5

3GPP2-Inter-User-Priority attribute

The IUPBEDA feature utilizes the 3GPP2-Inter-User-Priority attribute to hold the


inter-user priority for BE data within a subscriber profile. Users that do not have this
attribute provisioned in their subscriber profile will be given the defined treatment for
users with an unknown inter-user priority.
See Table 14-2, 3GPP2-Inter-User-Priority attribute format (p. 14-15) for the detailed
format of the 3GPP2-Inter-User-Priority attribute format. This attribute is defined by
3GPP2 standards.
Table 14-2

3GPP2-Inter-User-Priority attribute format

Attribute Name:

3GPP2-Inter-User-Priority

Attribute Type:

26

Vendor ID:

5535

Vendor Type:

139

Vendor Length:

Vendor Value:

32 bit integer with low order 3 kilobits indicating inter-user


priority for BE

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
14-15
Issue 5, May 2008
See notice on first page

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Impacts on the AAA network element

Important! Some Packet Data Serving Nodes (PDSNs) provide default values for
attributes if the PDSN receives no attribute value in the subscriber profile from the
AAA network element. In this case, the PDSN is configured to specify a default
value for the Inter-User Priority attribute that is consistent with the service
providers needs. Please consult the PDSN documentation for more information.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

14-16

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Impacts
on the OMC-RAN network element
...................................................................................................................................................................................................................................
Introduction

The following information describes the impact of the IUPBEDA feature on the
OMC-RAN network element.
Provisioning for this feature must be through OMC-RAN. Provisioning for this feature
cannot be done using ECPC RC/V or EMS.
Introduction

The IUPBEDA feature affects the following OMC-RAN forms:

FxApx Details EvDO RNC FAF tab


FxApx Details SN General tab
Cell Site Table Details Configuration tab

FxApx Details EvDO RNC FAF tab

This feature adds a new read-only field to the EvDO RNC FAF tab of the FxApx Details
view that displays the FAF activation status for the feature.
Important! The Enhanced Rev.A feature bundle on this screen must be enabled.
A more detailed description is shown in Table 14-3, Related fields in EvDO RNC
FAF form (p. 14-17).
Table 14-3

Related fields in EvDO RNC FAF form

Field Name

Description

Allowed Values

Inter-user priority

This read-only field displays the FAF


activation status of the feature.

Yes,
No

Note that the Enhanced Rev A feature


bundle on this screen must be enabled.

See Figure 14-4, Snapshot of portion of EvDO RNC FAF form (p. 14-18) for an
example of the contents of the EvDO RNC FAF tab where the field related to this feature
is located.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
14-17
Issue 5, May 2008
See notice on first page

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Impacts on the OMC-RAN network element

Figure 14-4 Snapshot of portion of EvDO RNC FAF form

FxApx Details SN General tab

This feature adds new fields to the SN General tab of the FxApx Details view. The
new fields added are the feature enable field for the feature and the SN wide weights
associated with the various Inter-User Priority values. The new fields appear near the
bottom of the form.
A more detailed description is shown in Table 14-4, Related fields in EvDO RNC
FAF form (p. 14-18).
Table 14-4

Related fields in EvDO RNC FAF form

Field Name

Description

Allowed Values

Enable Inter-user Priority

This field is used to enable or disable


the feature.

Yes,
No

Note that the QOS_REVA and


IUPBEDA FAFs must be activated
before this feature can be enabled.
BE service category flow
weight for inter-user
priority: priority
unknown

This field indicates the BE inter-user


priority weight to be used for users
with no available inter-user priority
value.

0.25, 0.5, 1-8

BE service category flow


weight for inter-user
priority: priority 0

This field indicates the BE inter-user


priority weight to be used for users
with an inter-user priority of 0.

0.25, 0.5, 1-8

BE service category flow


weight for inter-user
priority: priority 1

This field indicates the BE inter-user


priority weight to be used for users
with an inter-user priority of 1.

0.25, 0.5, 1-8

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

14-18

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Impacts on the OMC-RAN network element

Table 14-4

Related fields in EvDO RNC FAF form

(continued)

Field Name

Description

Allowed Values

BE service category flow


weight for inter-user
priority: priority 2

This field indicates the BE inter-user


priority weight to be used for users
with an inter-user priority of 2.

0.25, 0.5, 1-8

BE service category flow


weight for inter-user
priority: priority 3

This field indicates the BE inter-user


priority weight to be used for users
with an inter-user priority of 3.

0.25, 0.5, 1-8

BE service category flow


weight for inter-user
priority: priority 4

This field indicates the BE inter-user


priority weight to be used for users
with an inter-user priority of 4.

0.25, 0.5, 1-8

BE service category flow


weight for inter-user
priority: priority 5

This field indicates the BE inter-user


priority weight to be used for users
with an inter-user priority of 5.

0.25, 0.5, 1-8

BE service category flow


weight for inter-user
priority: priority 6

This field indicates the BE inter-user


priority weight to be used for users
with an inter-user priority of 6.

0.25, 0.5, 1-8

BE service category flow


weight for inter-user
priority: priority 7

This field indicates the BE inter-user


priority weight to be used for users
with an inter-user priority of 7.

0.25, 0.5, 1-8

Important! If the serving BTS does not have a priority-to-weight mapping defined
(in the Cell Site Configuration Form) for a given Inter-User Priority then the
priority-to-weight mapping defined in the FxAPX SN General Form is used.
See Figure 14-5, Snapshot of portion of SN General form (p. 14-20) for an example
of the contents of the SN General tab where the fields related to the feature are
located.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
14-19
Issue 5, May 2008
See notice on first page

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Impacts on the OMC-RAN network element

Figure 14-5 Snapshot of portion of SN General form

Cell Site Table Details Configuration tab

This feature adds new fields to the Configuration tab of the Cell Site Table Details
view. These fields provide a way to override the system-wide weights on a per BTS
basis. The new fields appear at the bottom of the form.
A more detailed description is shown in Table 14-5, Related fields in Cell Site
Configuration form (p. 14-20).
Table 14-5

Related fields in Cell Site Configuration form

Field Name

Description

Allowed Values

BE service category flow


weight for inter-user
priority: priority
unknown

This field indicates the BE inter-user


priority weight to be used for users
with no available inter-user priority
value when they are served by this cell.

blank, 0.25,
0.5, 1-8

BE service category flow


weight for inter-user
priority: priority 0

This field indicates the BE inter-user


priority weight to be used for users
with an inter-user priority of 0 when
they are served by this cell.

blank, 0.25,
0.5, 1-8

BE service category flow


weight for inter-user
priority: priority 1

This field indicates the BE inter-user


priority weight to be used for users
with an inter-user priority of 1 when
they are served by this cell.

blank, 0.25,
0.5, 1-8

BE service category flow


weight for inter-user
priority: priority 2

This field indicates the BE inter-user


priority weight to be used for users
with an inter-user priority of 2 when
they are served by this cell.

blank, 0.25,
0.5, 1-8

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

14-20

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Impacts on the OMC-RAN network element

Table 14-5

(continued)

Related fields in Cell Site Configuration form

Field Name

Description

Allowed Values

BE service category flow


weight for inter-user
priority: priority 3

This field indicates the BE inter-user


priority weight to be used for users
with an inter-user priority of 3 when
they are served by this cell.

blank, 0.25,
0.5, 1-8

BE service category flow


weight for inter-user
priority: priority 4

This field indicates the BE inter-user


priority weight to be used for users
with an inter-user priority of 4 when
they are served by this cell.

blank, 0.25,
0.5, 1-8

BE service category flow


weight for inter-user
priority: priority 5

This field indicates the BE inter-user


priority weight to be used for users
with an inter-user priority of 5 when
they are served by this cell.

blank, 0.25,
0.5, 1-8

BE service category flow


weight for inter-user
priority: priority 6

This field indicates the BE inter-user


priority weight to be used for users
with an inter-user priority of 6 when
they are served by this cell.

blank, 0.25,
0.5, 1-8

BE service category flow


weight for inter-user
priority: priority 7

This field indicates the BE inter-user


priority weight to be used for users
with an inter-user priority of 7 when
they are served by this cell.

blank, 0.25,
0.5, 1-8

Important! Note: If the serving BTS has a priority-to-weight mapping defined (in
the Cell Site Configuration Form) for a given Inter-User Priority then the
priority-to-weight mapping defined in the Cell Site Configuration Form is used.
Otherwise the priority-to-weight mapping defined in the FxAPX SN General Form
is used.
See Figure 14-6, Snapshot of portion of Cell Site Configuration form (p. 14-22)
.for an example of the contents of the Cell Site Configuration Form where the
fields associated with this feature are located.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
14-21
Issue 5, May 2008
See notice on first page

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Impacts on the OMC-RAN network element

Figure 14-6 Snapshot of portion of Cell Site Configuration form

References

For more information about these forms and fields, see the following CDMA2000
1xEV-DO network documents:

CDMA2000 1xEV-DO RAS Planning and Implementation Guide, 401-614-101


Alcatel-Lucent 9271 EV-DO Radio Network Controller, 401-614-102

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

14-22

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Impacts
on service measurements
...................................................................................................................................................................................................................................
Introduction

The IUPBEDA feature affects the following category of service measurements:

HCS service measurements

The new service measurements are included in the HCS service measurement files
stored in the /omp-data/logs/HDR/sm_summary_files directory on the OMP-FX.
The HCS service measurement file names have the format of timestamp.HCSFMSframeNum. For example, an HCS service measurement file named
200707271100CDT.HCSFMS026 will hold counts for the hour following 11:00 AM
(CDT) on July 27, 2007 for the HCSs supported by RNC frame number 26.
HCS service measurements

The IUPBEDA feature introduces the HCS service measurements that are identified in
Table 14-6, HCS service measurements (p. 14-23). The FL_RLP_RATE_PRI counts
are measured in kilobits per second.
Important! FL_RLP_RATE_PRI and NUM_PRI SM counts are pegged per sector
of BTS. There are 12 Active BTS in NCR and 36 instances of
FL_RLP_RATE_PRI_0 and same with NUM_PRI_0 per hourly SM file.
Table 14-6

HCS service measurements

Service measurement count


label

Description

FL_RLP_RATE_PRI_0

The average Best Effort service category data rate


on the Forward Link for users with inter-user
priority 0.

FL_RLP_RATE_PRI_1

The average Best Effort service category data rate


on the Forward Link for users with inter-user
priority 1.

FL_RLP_RATE_PRI_2

The average Best Effort service category data rate


on the Forward Link for users with inter-user
priority 2.

FL_RLP_RATE_PRI_3

The average Best Effort service category data rate


on the Forward Link for users with inter-user
priority 3.

FL_RLP_RATE_PRI_4

The average Best Effort service category data rate


on the Forward Link for users with inter-user
priority 4.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
14-23
Issue 5, May 2008
See notice on first page

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Table 14-6

Impacts on service measurements

HCS service measurements

Service measurement count


label

(continued)

Description

FL_RLP_RATE_PRI_5

The average Best Effort service category data rate


on the Forward Link for users with inter-user
priority 5.

FL_RLP_RATE_PRI_6

The average Best Effort service category data rate


on the Forward Link for users with inter-user
priority 6.

FL_RLP_RATE_PRI_7

The average Best Effort service category data rate


on the Forward Link for users with inter-user
priority 7.

FL_RLP_RATE_PRI_8

The average Best Effort service category data rate


on the Forward Link for users with an unknown
inter-user priority.

NUM_PRI_0

The number of times a Best Effort service category


data channel was opened for users with inter-user
priority 0.

NUM_PRI_1

The number of times a Best Effort service category


data channel was opened for users with inter-user
priority 1.

NUM_PRI_2

The number of times a Best Effort service category


data channel was opened for users with inter-user
priority 2.

NUM_PRI_3

The number of times a Best Effort service category


data channel was opened for users with inter-user
priority 3.

NUM_PRI_4

The number of times a Best Effort service category


data channel was opened for users with inter-user
priority 4.

NUM_PRI_5

The number of times a Best Effort service category


data channel was opened for users with inter-user
priority 5.

NUM_PRI_6

The number of times a Best Effort service category


data channel was opened for users with inter-user
priority 6.

NUM_PRI_7

The number of times a Best Effort service category


data channel was opened for users with inter-user
priority 7.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

14-24

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Table 14-6

Impacts on service measurements

HCS service measurements

Service measurement count


label
NUM_PRI_8

(continued)

Description
The number of times a Best Effort service category
traffic channel was opened for users with an
unknown inter-user priority.

See Figure 14-7, Sample HCS service measurement report (p. 14-25) for sample
contents of an HCS service measurements file that includes the new counts that are
related to this feature.
Figure 14-7 Sample HCS service measurement report
FL_BTS_DELAY_TOTAL_PKTS_BE, 70464
FL_BTS_DELAY_TOTAL_PKTS_CS, 3070
FL_BTS_DELAY_TOTAL_PKTS_CV, 1023
FL_BTS_DELAY_TOTAL_PKTS_CPS, 0
FL_BTS_DELAY_TOTAL_PKTS_LLMCS, 0
FL_BTS_DELAY_TOTAL_PKTS_SMC, 618
FL_BTS_DELAY_S_PEAK_BE, 236
FL_BTS_DELAY_S_PEAK_CS, 27
FL_BTS_DELAY_S_PEAK_CV, 20
FL_BTS_DELAY_S_PEAK_CPS, 0
FL_BTS_DELAY_S_PEAK_LLMCS, 0
FL_BTS_DELAY_S_PEAK_SMC, 19
EVM_PCNT_RAB_SET_TO_ONE, 0
EVDO_SEC_CARR_HCS_CE_1, -336
EVDO_SEC_CARR_HCS_CE_2, -336
EVDO_SEC_CARR_HCS_CE_3, -336
FL_RLP_RATE_PRI_0, 0
FL_RLP_RATE_PRI_1, 88156
FL_RLP_RATE_PRI_2, 0
FL_RLP_RATE_PRI_3, 254860
FL_RLP_RATE_PRI_4, 0
FL_RLP_RATE_PRI_5, 0
FL_RLP_RATE_PRI_6, 0
FL_RLP_RATE_PRI_7, 0
FL_RLP_RATE_PRI_8, 0
NUM_PRI_0, 0
NUM_PRI_1, 17
NUM_PRI_2, 0
NUM_PRI_3, 9
NUM_PRI_4, 0
NUM_PRI_5, 0
NUM_PRI_6, 0
NUM_PRI_7, 0
NUM_PRI_8, 0

References

For detailed information about service measurements, see

CDMA2000 1xEV-DO Service Measurements, 401-614-325.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
14-25
Issue 5, May 2008
See notice on first page

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Configuration
and implementation considerations
...................................................................................................................................................................................................................................
Introduction

This section provides recommendations and guidelines to be considered prior to


configuring and activating the IUPBEDA feature.
Define consistent meanings for Inter-User Priority values

It is recommended that each Inter-User Priority value be associated with a specific


class of user and these meanings for Inter-User Priority values should be used
consistently across the wireless network. 3GPP2 standards define the Inter-User
Priority values 0 to 3 to be used for commercial service and reserve priorities 4 to 7
for future use. However, the full range of priorities (0 to 7) can be used on
non-commerical wireless networks created for applications such as public safety.
For an example of assignments of Inter-User Priority values to specific user classes,
see Table 14-7, Example assignment of Inter-User Priority values (p. 14-26).
Table 14-7

Example assignment of Inter-User Priority values

Inter-User Priority Value

User Type

IUP Weight

Low priority commercial service

0.5

Standard commercial service

Gold level commercial service

Platinum level commercial


service

General public safety use

Police

Fire

Disaster response coordinator

Table 14-7, Example assignment of Inter-User Priority values (p. 14-26) also shows
the Inter-User Priority Weights that could be associated with each priority value. This
approach would cause the wireless network to give incrementally higher priority to
Best Effort data connections for users as the Inter-User Priority value is increased.
Setting of IUP weight for unknown IUP value

Although one can provision the system to assign an IUP weight less than 1 to the
unknown IUP value to give such users a below normal priority, this should be done
only after it has been determined that all expected users have the IUP attribute
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

14-26

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Configuration and implementation considerations

provisioned in their subscriber profiles. The unknown IUP value only indicates that
the IUP attribute is not currently available for a user. It does not necessarily indicate
that the user should have below-normal priority.
Until the service provider has checked the AAA subscriber profiles for all expected
users, it is recommended that the IUP weight for unknown users should remain set to
1.
Ensure consistent inter-user priority weight assignments

If service providers use the IUPBEDA feature and plan to provide service to roamers
from other Service Nodes (SNs), it is recommended that the IUP weights be assigned
consistently across all SNs. This will ensure all SNs treat IUP values in a consistent
manner.
However, if another SN has assumed different meanings for the IUP values and has
significantly different IUP weight assignments, one could use the jurisdictional policies
of the Jurisdictional Priority for Public Service Users for Best Effort Data
(JPPSUBEDA) feature to account for this difference between the SNs.
Adjusting IUP weights to balance impact of priorities

The IUPBEDA feature allows service providers to adjust the weights associated with
individual Inter-User Priority values. Although the default weights can be used in many
circumstances, one may encounter situations where it is desirable to adjust the weights
that are assigned to the various priority values.
One reason for adjusting the inter-user priority weight assignments is to reduce/increase
the difference between the top and bottom weights in order to balance the impact of
the IUPBEDA feature on the overall user population. For example, if one wishes to
give users with lower priorities a larger share of the data throughput capacity, then the
weights for the higher priorities should be reduced. An example of how this can be
done is shown in Table 14-8, Example of adjusting Inter-User Priority Weights to
reduce impact of priorities (p. 14-27).
Table 14-8

Example of adjusting Inter-User Priority Weights to reduce impact


of priorities

Inter-User Priority Value

User Type

IUP Weight

Low priority commercial service

0.5

Standard commercial service

Gold level commercial service

Platinum level commercial


service

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
14-27
Issue 5, May 2008
See notice on first page

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Table 14-8

Configuration and implementation considerations

Example of adjusting Inter-User Priority Weights to reduce impact


of priorities (continued)

Inter-User Priority Value

User Type

IUP Weight

General public safety use

Police

Fire

Disaster response coordinator

Please note that one can adjust the default weight assignments for the SN and/or adjust
the weight assignments for a specific BTS.
Adjusting IUP weights to give different treatment for user classes based on location

Another reason for adjusting the IUP weight assignments is to give different treatment
for specific classes of users based on location (for a specific BTS or set of BTSs).
For an example of this type of adjustment of IUP weights, see Table 14-9, Example
of adjusting Inter-User Priority Weights for specific user classes (p. 14-28). In this
example, users with priority 5 are given better data service than users with priority 6
for this specific BTS.
Table 14-9

Example of adjusting Inter-User Priority Weights for specific user


classes

Inter-User Priority Value

User Type

IUP Weight

Low priority commercial service

0.5

Standard commercial service

Gold level commercial service

Platinum level commercial


service

General public safety use

Police

Fire

Disaster response coordinator

Please note that one can adjust the default weight assignments for the SN and/or adjust
the weight assignments for a specific BTS.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

14-28

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Implementing
the feature
...................................................................................................................................................................................................................................
Introduction

The following information describes the procedures for implementing the IUPBEDA
feature on a CDMA2000 1xEV-DO network.
Complete configuration and implementation requirements

Ensure that all configuration and implementation considerations have been reviewed
before implementing the IUPBEDA feature. For more information, see Configuration
and implementation considerations (p. 14-26).
Procedures

To implement the IUPBEDA feature, perform the following procedures in sequence:


Activating the feature (p. 14-30)
Confirming feature activation (p. 14-31)
Adjusting the IUP weight assignments for the Service Node (p. 14-32)
Adjusting the IUP weight assignments for a BTS (p. 14-34)
Setting Inter-User Priority attribute in AAA subscriber profile (p. 14-36)
Enabling the feature (p. 14-37)

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
14-29
Issue 5, May 2008
See notice on first page

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Activating
the feature
...................................................................................................................................................................................................................................
Purpose

This procedure activates the IUPBEDA feature in a CDMA2000 1xEV-DO Revision


A wireless network.
Execution of this procedure will activate the IUPBEDA feature so the other procedures
for implementing this feature can be executed.
Important! The feature will not be enabled (call processing will not be affected)
until the Enabling the feature (p. 14-37) is executed.
Procedure

Perform the following steps:


...................................................................................................................................................................................................

Ask your account executive to activate the following entry in your Feature Activation
File (FAF):
IUPBEDA
...................................................................................................................................................................................................

Proceed to Confirming feature activation (p. 14-31)


END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

14-30

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Confirming
feature activation
...................................................................................................................................................................................................................................
Purpose

This procedure activates the IUPBEDA feature in a CDMA2000 1xEV-DO Revision


A wireless network.
Procedure

Perform the following steps:


...................................................................................................................................................................................................

Go to the FxApx Details view from the OMC-RAN Network Manager. The Details
view can be accessed using either of the following techniques:

Right click on the FxApx object and select the Details item from the pop-up
menu.
Double click on the FxApx object.

...................................................................................................................................................................................................

Left click on the EvDO RNC FAF tab of the FxApx Details view and verify the FAF
entry has been activated. The IUPBEDA FAF status is displayed at the bottom of the
page as shown below:

END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
14-31
Issue 5, May 2008
See notice on first page

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Adjusting
the IUP weight assignments for the Service Node
...................................................................................................................................................................................................................................
Purpose

This procedure is used to adjust the IUP weight assignments used by the IUPBEDA
feature for the entire SN.
Note: These steps are performed using the OMC-RAN Network Manager.
Note: This is an optional step. In some cases, there will be no need to change the IUP
weight assignments for a network. This procedure is provided in case there is a need to
change the weights.
Procedure

Perform the following steps:


...................................................................................................................................................................................................

Go to the FxApx Details view for the network. The Details view can be accessed
using either of the following techniques:

Right click on the FxApx object and select the Details item from the pop-up
menu.
Double click on the FxApx object.

...................................................................................................................................................................................................

Left click on the SN General tab of the FxApx Details view.


...................................................................................................................................................................................................

Left click on the Modify button at the bottom of the SN General page as shown
below:

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

14-32

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Adjusting the IUP weight assignments for the Service


Node

...................................................................................................................................................................................................

Left click on the priority field to be changed and select the desired value from the
menu.
...................................................................................................................................................................................................

Repeat Step 4 as needed to update other IUP weight fields.


...................................................................................................................................................................................................

Left click on the OK button of the SN General page.


END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
14-33
Issue 5, May 2008
See notice on first page

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Adjusting
the IUP weight assignments for a BTS
...................................................................................................................................................................................................................................
Purpose

This procedure is used to adjust the IUP weight assignments used by the Inter-User
Priority feature for a specific BTS. The IUP weights assignments set for a BTS will
override the IUP weight assignments defined for the SN.
Note: These steps are performed using the OMC-RAN Network Manager.
Note: This is an optional step. In many cases, there will be no need to change the IUP

weight assignments on a BTS. This procedure is provided in case there is a need to


change the weights for a specific BTS
Procedure

Perform the following steps:


...................................................................................................................................................................................................

Expand the ORCA Group (if necessary) by performing a left click on the + next to the
ORCA Group object.
...................................................................................................................................................................................................

Right click on ORCA Groups do object and select ShowOnTree item from the pop-up
menu.
...................................................................................................................................................................................................

Expand the Cell Site Table with a left click on the + next to the Cell Site Table
object.
...................................................................................................................................................................................................

Go to the Cell Site Table Details view of the selected BTS from the list of BTSs
under the Cell Site Table. One can access the Details view using either of the
following techniques:

Right click on the Cell Site Table object and select the Details item from the
pop-up menu.
Double click on the selected Cell Site.

...................................................................................................................................................................................................

Left click on the Configuration tab of the Cell Site Details view.
...................................................................................................................................................................................................

Left click on the Modify button at the bottom of the Cell Site Configuration page as
shown below:

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

14-34

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Adjusting the IUP weight assignments for a BTS

...................................................................................................................................................................................................

Left click on the priority field to be changed and select the desired value from the
menu.
Note: If the weight for a priority is blank, then the weight for the SN will be used for
this priority.
...................................................................................................................................................................................................

Repeat Step 7 as needed to update other IUP weight fields.


...................................................................................................................................................................................................

Left click on the OK button at the bottom of the Cell Site Configuration page.
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
14-35
Issue 5, May 2008
See notice on first page

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Setting
Inter-User Priority attribute in AAA subscriber profile
...................................................................................................................................................................................................................................
Purpose

This procedure is used to include the Inter-User Priority attribute in AAA subscriber
profiles.
Important! The exact procedures will vary depending on the specific AAA system
being used. Please refer to the documentation for your AAA system for more
information.
Procedure

Perform the following steps:


...................................................................................................................................................................................................

Verify that the AAA dictionary includes the definition for the 3GPP2 vendor ID. The
definition for the 3GPP2 vendor ID will appear as follows on the VitalAAA system:
<vendor name=3GPP2 number=5535 format=RFC />
...................................................................................................................................................................................................

Verify that the AAA dictionary includes the definition of the 3GPP2-Inter-User-Priority
attribute as a 3GPP2 Vendor Specific Attribute (VSA). The definition for this attribute
will appear as follows on the VitalAAA system:.
<avp name=3GPP2-Inter-User-Priority vendor=3GPP2>
...................................................................................................................................................................................................

Update subscriber profiles as needed to include the 3GPP2-Inter-User-Priority attribute.


The following example shows a sample subscriber profile for VitalAAA system:

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
CLIENT_IUP1
User-Password=PASSWORD1 Auth-Type=Local
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
3GPP2-Inter-User-Priority=1
1234567890123456789012345678901212345678901234567890123456789
Cisco-AVPair=lcp:cdma-user-class=1
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Cisco-AVPair=ip:addr-pool=pdsn-pool
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Callback-Id=0111113137147635
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
3GPP2-ESN=60302db4
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

14-36

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Enabling
the feature
...................................................................................................................................................................................................................................
Purpose

This procedure enables the Inter-User Priority for Best Effort Data Applications
(IUPBEDA) feature in a CDMA2000 1xEvDO network.
Execution of this procedure will cause the network to adjust the priority of data
transmission on the Forward Link for Best Effort service category data connections
based upon the Inter-User Priority value assigned to users.
Important! The Activating the feature (p. 14-30) procedure must be completed
before this procedure can be executed.
Procedure

Perform the following steps:


...................................................................................................................................................................................................

Go to the FxApx Details view from the OMC-RAN Network Manager. The Details
view can be accessed using either of the following techniques:

Right click on the FxApx object and select the Details item from the pop-up
menu.
Double click on the FxApx object.

...................................................................................................................................................................................................

Left click on the SN General tab of the FxApx Details view.


...................................................................................................................................................................................................

Left click on the Modify button at the bottom of the SN General page as shown
below:

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
14-37
Issue 5, May 2008
See notice on first page

Inter-User Priority for Best Effort Data Applications


(IUPBEDA)

Enabling the feature

...................................................................................................................................................................................................

Left click on the Enable Inter-User Priority field and select Yes.
...................................................................................................................................................................................................

Left click on the OK button at the bottom of the SN General page.


END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

14-38

15

15
Jurisdictional
Priority for Public
Safety Users of Best Effort Data
Applications (JPPSUBEDA)

Overview
...................................................................................................................................................................................................................................
Purpose

This chapter describes Jurisdictional Priority for Public Safety Users of Best Effort
Data Applications (JPPSUBEDA) feature in the CDMA2000 1xEV-DO network.
Feature summary

The JPPSUBEDA feature allows service providers to divide their CDMA2000


1xEV-DO network into geographic jurisdictions and adjust the Inter-User Priority value
associated with users from other jurisdictions based upon policies created for the
serving jurisdiction. This feature works in conjunction with the Inter-User Priority for
Best Effort Data Applications (IUPBEDA) feature. By adjusting the effective Inter-User
Priority values for users, the JPPSUBEDA feature affects each users priority for Best
Effort (BE) data service on the Forward Link (as supported by the IUPBEDA feature).
This feature is available on the CDMA2000 1xEV-DO network supporting Revision A
of the 1xEV-DO standard.
Feature Identifier (FID)

The Feature Identifier (FID) of the JPPSUBEDA feature is FID 12171.5.


Impacts on user interfaces

The JPPSUBEDA feature affects the user interfaces that are listed in the following
table:
User interface

Feature impact

Accounting,
Authentication, and
Authorization
(AAA)

See Impacts on the AAA network element (p. 15-16).

....................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-1
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Overview

User interface

Feature impact

Automated Message
Accounting (AMA)

None

Element
Management System
(EMS)

None

Operations and
Maintenance Center
- Radio Access
Network
(OMC-RAN)

See Impacts on the OMC-RAN network element (p. 15-18).

Service
measurements

None

Technician Interface
(TI) (input/output
messages)

None

Intended audience

This document is intended for technicians, engineers, and system administrators who
implement or maintain the Public Security feature and/or related features in a
CDMA2000 1xEV-DO network.
To obtain technical support, documentation, and training or submit feedback

The Online Customer Support (OLCS) web site (http://support.lucent.com/) provides


access to technical support, related documentation, related training, and feedback tools.
The site also provides account registration for new users.
Contents
Availability

15-4

Prerequisites

15-5

Feature description

15-6

Feature interactions

15-10

Sample call scenarios

15-11

Impacts on the AAA network element

15-16

Impacts on the OMC-RAN network element

15-18

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-2

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Overview

Configuration and implementation considerations

15-27

Implementing the feature

15-34

Activating the feature

15-35

Confirming feature activation

15-36

Creating jurisdictions

15-37

Creating OMC-RAN user account restricted to jurisdiction

15-39

Creating jurisdictional policies

15-45

Updating jurisdictional policies

15-47

Making jurisdictional policy assignments

15-49

Making BTS assignments for a jurisdiction

15-56

Viewing BTS assignments for a jurisdiction

15-59

Setting Subscriber Home Area attribute in AAA

15-62

Enabling the feature

15-64

Deactivating the feature

15-66

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-3
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Availability
...................................................................................................................................................................................................................................
Release availability

The JPPSUBEDA feature is available in EVDO Release 29.0 SU29-0002 and later.
Market availability

The JPPSUBEDA feature is available only in the North American Region (NAR)
Public Safety application.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-4

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Prerequisites
...................................................................................................................................................................................................................................
Introduction

The JPPSUBEDA feature has the following prerequisites.


Supported technologies

The JPPSUBEDA features are supported in the following air-interface technology:

1xEV-DO

Software requirements

The JPPSUBEDA feature has the following software requirements:

The BTS software release must be R29.1 or later


The RNC software release must be R29.0 SU29-0002 or later
The OMC-RAN software release must be R29.0 SU2 or later
The 1xEV-DO Application based Quality of Service (QoS) support for High Rate
Packet Data Revision A (Rev. A) (HRPD Rev. A) (FID 12078.9) must be enabled
The Inter-User Priority for Best Effort Data Applications (IUPBEDA) (FID
12171.4) must be activated

Hardware requirements

The JPPSUBEDA feature requires no other hardware beyond the standard hardware in
a CDMA2000 1xEV-DO network.
Interface requirements

The JPPSUBEDA feature has the following interface requirements:

The AAA network element must be capable of supporting the Inter-User Priority
and Subscriber Home Area attributes in the Subscriber Profile.
The Packet Data Serving Node (PDSN) must be capable of supporting the
Inter-User Priority and Subscriber Home Area attributes in the Subscriber QoS
Profile.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-5
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Feature
description
...................................................................................................................................................................................................................................
Introduction

The following information describes the functionality, benefits, and operation of the
JPPSUBEDA feature.
Functionality

The JPPSUBEDA feature allows the network to be divided into geographical


jurisdictions and allows each jurisdiction to manage the jurisdiction assets (BTS
equipment) and adjust the priority for visiting subscribers from other jurisdictions. This
feature works in conjunction with the IUPBEDA feature.
At high level, the feature can be divided into two areas:

general support for management of jurisdiction equipment.


support for different levels of BE data service depending on users home
jurisdiction.

This feature allows each jurisdiction to define policies to be applied to visiting


subscribers from other jurisdictions. These policies indicate how the inter-user priority
for visiting subscribers should be adjusted while being served in the visited
jurisdiction. The policies are defined per jurisdiction and will apply to all visiting
subscribers served by that jurisdiction.
Up to 18 jurisdictions are supported in a network. Each jurisdiction is defined as a set
of cells. All jurisdictions in the network can share the RNC, PDSN, HA and AAA. The
OMC-RAN supports the creation of jurisdictions and jurisdictional policies and allows
only authorized groups to manage the jurisdiction equipment and update data
associated with the jurisdiction. The shared equipment is managed separately by
network-level administrators.
The management of the PDSN, HA, and AAA are outside the scope of this document.
Benefits

The JPPSUBEDA feature provides the ability to control priority given to users for BE
data service based upon jurisdictional policies. In addition, administrators for specific
jurisdictions can be given access to administer only the equipment associated with their
jurisdiction. These capabilities are especially needed to support data networks to be
used by Public Safety agencies.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-6

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Feature description

How the feature operates

The JPPSUBEDA feature involves the following activities:


1. The RNC receives the Inter-User Priority and Subscriber Home Area values from
the PDSN as part of the subscriber profile from AAA. These values are saved for
the users data session along with other subscriber profile attributes.
2. The RNC determines the jurisdiction of the BTS serving each call leg.
3. If the BTS is associated with a jurisdiction and the subscribers Home Area is not
equal to the jurisdiction of the BTS, then the RNC will adjust the Inter-User
Priority value for the subscriber by applying the appropriate jurisdictional policy as
described below:
a. If an entry in the Roaming Policy Assignment table matches the subscribers
Home Area, apply the policy that is specified by the Roaming Policy
Assignment entry.
b. Otherwise, apply the Default policy for the jurisdiction associated with the
BTS.
4. The adjusted Inter-User Priority value is then given the normal treatment by the
IUPBEDA feature. The RNC calculates the Inter-User Priority Weight for the
effective Inter-User Priority value and the RNC passes the Inter-User Priority
Weight to each BTS that supports the data connection.
5. The BTS accepts the Inter-User Priority Weight and uses this value when
scheduling data packet transmission on the Forward Link of Best Effort data
connections. This weight is used in conjunction with other factors that affect data
packet transmission scheduling such as signal strength
Subscriber perspective

The JPPSUBEDA feature can adjust the priority level given to subscribers visiting
another jurisdiction. A subscriber that is roaming (visiting another jursidition) may be
given a lower (or higher) priority than what they normally receive in their home
jurisdiction. Otherwise, this feature is transparent to the subscriber.
Please note that this feature does not affect the priority level given to subscribers
within their home jurisdictions. This feature also does not affect the priority level if the
serving BTS is not associated with a jurisdiction.
Service-provider perspective

The JPPSUBEDA feature allows the service provider to divide a wireless network into
jurisdictions and define policies to adjust the priorities for subscribers that are visiting
from other jurisdictions.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-7
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Feature description

Example of feature operation

To illustrate how this feature operates, please consider the following example
1. A subscriber is assigned an Inter-User Priority value of 6 for Best Effort Data in
the AAA server.
2. The Home Area for subscriber is defined to be jurisdiction 3.
3. The subscriber initiates a 1xEV-DO Rev A connection using an Access Terminal
(AT).
4. The AT is served by BTS 1, BTS 2, and BTS 3. The Forward Link (FL) is only
transmitted by the serving (primary) BTS.
Figure 15-1, Example Application of the Jurisdictional Priority feature (p. 15-9)
shows the BTSs serving a users AT, the jurisdictional policies, the policy assignments,
and the associated priority-to-weight mapping for this example.
In this example, the Serving Inter-User Priority for each serving BTS is determined as
follows:
1. Policy A of jurisdiction 1 is applied on BTS 1 and yields an adjusted priority
value of 6.
2. Policy C of jurisdiction 2 is applied on BTS 2 and yields an adjusted priority
value of 3.
3. No policy is applied on BTS 3 since BTS 3 is in the subscribers home jurisdiction.
Consequently, the priority value remains unchanged (6).
The priority-to-weight mapping for priority 6 on BTS 1 yields a priority weight of 3.
The mapping for BTS 2 yields a priority weight of 3 given a priority value of 3. Since
BTS 3 has no priority-to-weight mappings defined, we must use the system-wide
mappings for the SN. Consequently, a priority weight of 6 will be used on BTS 3.
To review the results, please consider the following:

A priority weight of 3 will be used on BTS 1 due to the priority-to-weight


mappings on that BTS. The user is visiting another jurisdiction when it is served by
BTS 1. However, the policy applied (Policy A) didnt change the users
Inter-User Priority value.
A priority weight of 3 will also be used on BTS 2, but for very different reasons.
In this case, the jurisdictional policy applied (Policy C) changed the Inter-User
Priority from 6 to 3.
A priority weight of 6 will be used on BTS 3 because BTS 3 is the users home
jurisdiction. Consequently, no policy will be applied and the Inter-User Priority will
not be changed.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-8

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Feature description

Figure 15-1 Example Application of the Jurisdictional Priority feature


Serving
Jurisdiction

Roamer Home
Jurisdiction

Roamer Policy

J1
J1
J2
J2

J2
J3
J1
J3

A
A
B
C

Table B1: Jurisdictional Roamer Policy Assignment

BTS 2
(J2)
BTS 1
(J1)
BTS 3
(J3)

Serving Inter-User Priority

Home
Inter-User
Priority

J1 Policy
A

J2 Policy
B

J2 Policy
C

0
1
2
3
4
5
6
7

0
1
2
3
4
5
6
7

0
1
2
3
4
5
5
5

0
1
1
2
2
3
3
4

Table B2: Jurisdictional Roamer Policy

Subscribers Inter-User Priority = 6


Subscribers Home Area = J3

Resulting IUP weights on FL for Best Effort Flow *


BTS 1 = 3,
BTS 2 = 3,
BTS 3 = 6
* = when BTS handles FL transmission

Inter-User Priority Weight

Inter-User
Priority

BTS 1

BTS 2

BTS 3

SN

0
1
2
3
4
5
6
7

0.25
1
1
2
2
3
3
4

0.50
1
2
3
5
6
7
8

Blank
Blank
Blank
Blank
Blank
Blank
Blank
Blank

0.50
1
2
3
4
5
6
7

unknown

Blank

Table B3: Inter-User Priority Weights

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-9
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Feature
interactions
...................................................................................................................................................................................................................................
Introduction

The following information describes the interactions that may occur between the
JPPSUBEDA feature and the following features:

Application Based Quality of Service (QoS) Support for HRPD Rev. A (FID
12078.9)
Inter-User Priority for Best Effort Data Applications (IUPBEDA) (FID 12171.4)

Application Based Quality of Service (QoS) Support for HRPD Rev. A (FID
12078.9) feature

The IUPBEDA feature depends on FID 12078.9 for the basic Rev. A interfaces. For
example, the Inter-User Priority attribute is part of the Subscriber QoS Profile passed
by the PDSN and FID 12078.9 provides the support of the Subscriber QoS Profile in
the CDMA2000 1xEV-DO network. However, there is no other feature interaction.
The IUPBEDA feature has no impact on the operation of the Application Based
Quality of Service Support for HRPD Rev. A (FID 12078.9) feature.
Inter-User Priority for Best Effort Data Applications (IUPBEDA) (FID 12171.4)
feature

The JPPSUBEDA feature depends on IUPBEDA (FID 12171.4) for support of different
priority access on the Forward Link for Best Effort data connections. The
JPPSUBEDA feature adjusts the Inter-User Priority value associated with individual
users, but the calculation of the Inter-User Priority Weights and the adjustment of the
scheduling of data packet transmission in the BTS is based on these priority weights
that are supported by the IUPBEDA (FID 12171.4).

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-10

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Sample
call scenarios
...................................................................................................................................................................................................................................
Introduction

The following information describes call scenarios for the JPPSUBEDA feature.
Establishment of New Data Session

The call flow in Figure 15-2, Establishment of New Data Session with Home Area
Attribute (p. 15-12) describes the successful initial establishment of a data session in
which the Inter-User Priority and Home Area attributes are included in the subscriber
profile.
Note: Only the numbered messages are affected by the JPPSUBEDA feature.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-11
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Sample call scenarios

Figure 15-2 Establishment of New Data Session with Home Area Attribute
AT

RAN

PDSN

AAA

Session Configuration
Traffic Channel Establishment
XonRequest

A11 RRQ
A11 RRP

XonResponse

A11 RRQ
A11 RRP

PPP Configuration and Authentication

[1] RADIUS
Request
[2] RADIUS Accept

[3] A11 Session Update


(with Inter-User Priority
& Home Area)
[4] Get QoS Profile

(with Inter-User Priority


& Home Area)

A11 SU ACK

IP Address Assignment
AttributeUpdateRequest

(ReservationKKQoSRequestFWD and Rev)

AttributeUpdateAccept
AttributeUpdateRequest

(1 per each bidirectional reservation)

AttributeUpdateAccept

A11 RRQ
A11 RRP

Resv (Traffic Flow Template)


ResvConf

Message
Label

Establishment of New Data Session with Home Area Attribute

[1]

During the establishment of a data session, the PDSN sends a RADIUS


Request to the AAA server order to retrieve the subscriber profile of the
user.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-12

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Sample call scenarios

Message
Label

Establishment of New Data Session with Home Area Attribute

[2]

An AAA responds to the RADIUS Request with a RADIUS Response.


The RADUIS Response includes the subscriber profile. The
3GPP2-Inter-User-Priority and Lucent-Vendor ID (VID)-Subscriber-Home
Area attributes are included in the subscriber profile.

[3]

The PDSN accepts the RADIUS Response and forwards the subscriber
profile information to the RAN in the A11 Session Update message. The
Inter-User Priority and Home Area attributes are included as part of the
Subscriber QoS Profile attribute.

[4]

The RAN (the RNC component of the RAN) receives the A11 Session
Update message and stores the Inter-User Priority and Home Area
attributes with the users session data.

Reactivation of Existing Data Session

The call flow in Figure 15-3, Reactivation of existing data session with JPPSUBEDA
enabled (p. 15-14) describes the successful establishment of a new data connection in
which the JPPSUBEDA feature has adjusted the Inter-User Priority value for the user.
In this case, the data session was established previously, but the active connection was
dropped when the data session became dormant prior to this effort to re-establish the
active connection.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-13
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Sample call scenarios

Figure 15-3 Reactivation of existing data session with JPPSUBEDA enabled


RNC

BTS1

AT
[1] RU+CR+RoR

[2] ACPI (RU+CR+RoR)


[3] AllocateTrafficChannelReq
(InterUserPriority1 &
InterUserPriority Weight1)
AllocateTrafficChannelRsp

TCA+ReservationAccept
(on Control Channel)

[4] AllocateTrafficChannelReq
(InterUserPriority2 &
InterUserPriority Weight2)
AllocateTrafficChannelRsp

SCCPC(TCA+RA)

MobileAcquiredInd
RTCAck

BTS 2

SFPC(RTCAck)

MobileAcquiredInd
SFPC(RTCAck)

RTCAck
TCC (on RTC)
TCC (on RTC)

RPI(TCC)

RPI(TCC)

Message
Label

Reactivation of Existing Data Session with JPPSUBEDA Enabled

[1]

The AT sends ConnectionRequest, RouteUpdate, and


ReservationOnRequest messages to request the establishment of a Best
Effort data connection.

[2]

The BTS will then forward the received ConnectionRequest,


RouteUpdate, and ReservationOnRequest messages on to the RNC.

[3]

The RNC will apply the appropriate jurisdictional policy given the users
Home Area. It will also calculate Inter-User Priority Weight to be sent to
BTS1 using the adjusted Inter-User Priority value and priority-to-weight
mappings that have been defined for BTS1. If no priority-to-weight
mappings have been defined for BTS1, then the priority-to-weight
mappings for the SN will be used.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-14

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Sample call scenarios

Message
Label

Reactivation of Existing Data Session with JPPSUBEDA Enabled

[4]

The RNC will apply the appropriate jurisdictional policy given the users
Home Area. It will also calculate Inter-User Priority Weight to be sent to
BTS2 using the adjusted Inter-User Priority value and priority-to-weight
mappings that have been defined for BTS2. If no priority-to-weight
mappings have been defined for BTS2, then the priority-to-weight
mappings for the SN will be used.
Inter-User Priority (2) can be different than Inter-User Priority (1) if
BTS1 and BTS2 are in different jurisdictions and would consequently be
affected by different policies.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-15
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Impacts
on the AAA network element
...................................................................................................................................................................................................................................
Introduction

The following information describes the impact of the JPPSUBEDA feature on the
AAA network element.
AAA subscriber profile attribute

The JPPSUBEDA feature affects the AAA subscriber profile attribute that is listed in
Table 15-1, Related AAA subscriber profile attributes (p. 15-16).
Table 15-1

Related AAA subscriber profile attributes

AAA subscriber profile attribute

Impacted by

3GPP2-Inter-User-Priority

IUPBEDA - FID 12171.4


JPPSUBEDA - FID 12171.5

Lucent-VID-Home-Area

JPPSUBEDA - FID 12171.5

3GPP2-Inter-User-Priority attribute

The IUPBEDA and JPPSUBEDA features use the 3GPP2-Inter-User-Priority attribute


to hold the inter-user priority for BE data within an AAA subscriber profile. Users that
do not have this attribute provisioned in their subscriber profile will be given the
defined treatment for users with an unknown inter-user priority.
See Table 15-2, 3GPP2-Inter-User-Priority attribute format (p. 15-16) for the detailed
format of the 3GPP2-Inter-User-Priority attribute format. This attribute is defined by
3GPP2 standards.
Table 15-2

3GPP2-Inter-User-Priority attribute format

Attribute Name:

3GPP2-Inter-User-Priority

Attribute Type:

26

Vendor ID:

5535

Vendor Type:

139

Vendor Length:

Vendor Value:

32 bit integer with low order 3 bits indicating inter-user


priority for BE

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-16

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Impacts on the AAA network element

Important! Some Packet Data Serving Nodes (PDSNs) provide default values for
attributes if the PDSN receives no attribute value in the subscriber profile from the
AAA network element. In this case, the PDSN is configured to specify a default
value for the Inter-User Priority attribute that is consistent with the service
providers needs. Please consult the PDSN documentation for more information.
Lucent-VID-Home-Area attribute

The JPPSUBEDA feature utilizes the Lucent-VID-Home-Area attribute to hold the


jurisdiction ID of the subscribers home area.
See Table 15-3, Lucent-VID-Home-Area attribute format (p. 15-17) for the detailed
format of the Lucent-VID-Home-Area attribute. This attribute is a vendor-specific
attribute.
Table 15-3

Lucent-VID-Home-Area attribute format

Attribute Name:

Lucent-VID-Home-Area

Attribute Type:

26

Vendor ID:

3729

Vendor Type:

11

Vendor Length:

Vendor Value:

16 bit integer identifying subscriber home jurisdiction

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-17
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Impacts
on the OMC-RAN network element
...................................................................................................................................................................................................................................
Introduction

The following information describes the impact of the JPPSUBEDA feature on the
OMC-RAN network element. Please note that more detailed information is also
available in the 401-380-835R29 (OA&M) and 401-380-092R29 (OMC-RAN CLI)
documents.
Provisioning for this feature must be through OMC-RAN. Provisioning for this feature
cannot be done using ECPC RC/V or EMS.
Introduction

The IUPBEDA feature affects the following OMC-RAN forms:

FxApx Details EvDO RNC FAF tab


FxApx Details SN General tab
Jurisdiction Group Serving Jurisdiction Details Main tab
Jurisdiction Group Serving Jurisdiction Details BTS Allocation tab
Jurisdiction Group Serving Jurisdiction Subtree BERoamPolTable Details
Jurisdiction Group Serving Jurisdiction Subtree RoamPolAssgn Details
User & Session Manager - User Profile screen

FxApx Details EvDO RNC FAF tab

This feature adds a new read-only field to the EvDO RNC FAF tab of the FxApx Details
view that displays the FAF activation status for the feature.
A more detailed description is shown in Table 15-4, Related fields in EvDO RNC
FAF form (p. 15-18).
Table 15-4

Related fields in EvDO RNC FAF form

Field Name

Description

Allowed Values

Jurisdictional Priority for


Public Safety Users

This read-only field displays the FAF


activation status of the feature.

Yes,
No

See Figure 15-4, Snapshot of portion of EvDO RNC FAF form (p. 15-19) for an
example of the contents of the EvDO RNC FAF tab where the fields related to
IUPBEDA and JPPSUBEDA are located.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-18

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Impacts on the OMC-RAN network element

Figure 15-4 Snapshot of portion of EvDO RNC FAF form

FxApx Details SN General tab

This feature adds new fields to the SN General tab of the FxApx Details view. A
feature enable field is added for this feature. The new field appears near the bottom of
the form.
A more detailed description is shown in Table 15-5, Related fields in SN General
form (p. 15-19).
Table 15-5

Related fields in SN General form

Field Name

Description

Allowed Values

Enable Jurisdictional
Priority for Public Safety
Users

This field is used to enable or disable


the feature.

Yes,
No

Note: The QOS_REVA, IUPBEDA, and

JPPSUBEDA FAFs must be activated


before this feature can be enabled.

See Figure 15-5, Snapshot of portion of SN General form (p. 15-20) for an example
of the contents of the SN General tab where the fields related to the feature are
located.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-19
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Impacts on the OMC-RAN network element

Figure 15-5 Snapshot of portion of SN General form

Serving Jurisdiction Details Main tab

The JPPSUBEDA feature introduces the Jurisdiction Group and allows up to 18


Serving Jurisdictions to be created under the Jurisdiction Group. The Main tab of the
Serving Jurisdiction Details view includes only read-only fields since these fields can
only be set when a Serving Jurisdiction is created.
A Serving Jurisdiction instance can be created via the Create Serving Jurisdiction
operation which is available at the Jurisdiction Group level.
A more detailed description is shown in Table 15-6, Related fields in Serving
Jurisdiction Main Details form (p. 15-20).
Table 15-6

Related fields in Serving Jurisdiction Main Details form

Field Name

Description

Allowed Values

Jurisdiction Id

This read-only field is used to display


the numeric Jurisdiction ID associated
with the selected Serving Jurisdiction.

1-65535

Jurisdiction name

This read-only field is used to display


the name of the selected Serving
Jurisdiction.

string up to 25
characters

See Figure 15-6, Snapshot of Serving Jurisdiction Main Details form (p. 15-21) .for
an example of the contents of the Main tab of the Serving Jurisdiction Details form.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-20

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Impacts on the OMC-RAN network element

Figure 15-6 Snapshot of Serving Jurisdiction Main Details form

Serving Jurisdiction Details BTS Allocation tab

The JPPSUBEDA feature allows one or more BTS to be associated with each Serving
Jurisdiction. The BTS Allocation tab of the Serving Jurisdiction Details view lists
the BTSs that have been assigned to the selected Serving Jurisdiction. This view
includes only read-only fields since these fields can only be set using the BTS
Allocation operation which is available at the Serving Jurisdiction instance level.
A more detailed description is shown in Table 15-7, Related fields in Serving
Jurisdiction BTS Allocation Details form (p. 15-21).
Table 15-7

Related fields in Serving Jurisdiction BTS Allocation Details form

Field Name

Description

Allowed Values

Assigned BTS List

This read-only field is used to display


the list of BTSs that are assigned to the
selected Serving Jurisdiction

List of strings

See Figure 15-6, Snapshot of Serving Jurisdiction Main Details form (p. 15-21) for
an example of the contents of the BTS Allocation tab of the Serving Jurisdiction
Details form.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-21
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Impacts on the OMC-RAN network element

Figure 15-7 Snapshot of Serving Jurisdiction BTS Allocation Details form

Serving Jurisdiction subtree

The JPPSUBEDA feature allows the jurisdictional policies and policy assignments to
be managed using the Serving Jurisdiction subtree. From the subtree view, policies can
be viewed, created, changed and deleted and the policies can be assigned to specific
Jurisdiction IDs.
The Serving Jurisdiction subtree can be accessed by invoking the ShowOnTree
operation on a Serving Jurisdiction instance under the Jurisdiction Group object.
A more detailed description is shown in Table 15-8, Objects in Serving Jurisdiction
subtree (p. 15-22).
Table 15-8

Objects in Serving Jurisdiction subtree

Object Name

Description

BERoamPolTable

This object holds a list of BERoamPolTable instances.

BERoamPolTable
instances

Each policy defined for this Serving Jurisdiction is


represented by an instance in the BERoamPolTable subtree.
Each of these instances is identified by its assigned Policy
Name.

RoamPolAssgn

This object holds the set of Roamer Policy Assignments for


this Serving Jurisdiction.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-22

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Impacts on the OMC-RAN network element

See Figure 15-8, Snapshot of of Serving Jurisdiction subtree (p. 15-23) for an
example of a Serving Jurisdiction subtree used to provision data related to the
JPPSUBEDA feature. In the example shown below, the Serving Jurisdiction named
J1 has two policies named A and B.
Figure 15-8 Snapshot of of Serving Jurisdiction subtree

Serving Jurisdiction BERoamPolTable Instance Details

The JPPSUBEDA feature allows one or more BE Roaming Policies to be associated


with each Serving Jurisdiction. The BERoamPolTable Details view displays the
mappings of inter-user priority values that make up the selected policy.
A BE Roaming Policy instance can be created by invoking the Create BE Roaming
Policy operation on a Serving Jurisdiction object. BE Roaming Policy instances may
also be changed.
A more detailed description is shown in Table 15-9, Related fields in the
BERoamPolTable Instance Details form (p. 15-23).
Table 15-9

Related fields in the BERoamPolTable Instance Details form

Field Name

Description

Allowed Values

Name

This field is the name of a BE Roamer Policy of


the current Serving Jurisdiction. The name is set
when policy is created.

string up to 25
characters

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-23
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Table 15-9

Impacts on the OMC-RAN network element

Related fields in the BERoamPolTable Instance Details form


(continued)

Field Name

Description

Allowed Values

Home
Inter-user
Priority (9
rows in
table)

These read-only fields identify the original


inter-user priority that is being adjusted.

0-7, unknown

Serving
Inter-user
Priority (9
rows in
table)

These fields indicate the inter-user priority that


will result when this policy is applied for the
associated home inter-user priority for the current
Serving Jurisdiction.

0-7

See Figure 15-9, Snapshot of of Serving Jurisdiction BERoamPolTable Details form


(p. 15-24) for an example of the contents of the Serving Jurisdiction BERoamPolTable Details form. In this example, the Default policy maps all Inter-User Priority
values to 1.
Figure 15-9 Snapshot of of Serving Jurisdiction BERoamPolTable Details form

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-24

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Impacts on the OMC-RAN network element

Serving Jurisdiction RoamPolAssgn Details

The JPPSUBEDA feature allows a BE Roaming Policy to be assigned for subscribers


from other jurisdictions. If a subscribers Home Area matches the Roaming Jurisdiction
ID field of an entry in this table, then the associated policy will be applied. The
RoamPolAssgn Details view displays the set of policy assignments that have been
defined for a specific Serving Jurisdiction.
Roaming Policy Assignment (RoamPolAssgn) instances can be created via the Add
buttons of the form. RoamPolAssgn instances may also be changed or deleted.
A more detailed description is shown in Table 15-10, Related fields in Serving
Jurisdiction RoamPolAssgn Details form (p. 15-25).
Table 15-10

Related fields in Serving Jurisdiction RoamPolAssgn Details form

Field Name

Description

Allowed Values

Roaming
Jurisdiction
Id (17 rows
in table)

These fields identify a jurisdiction to which the


associated policy should be assigned.

1-65535

Policy name
(17 rows in
table)

These fields indicate the policy that will be


applied to subscribers with a Home Area that
matches the associated Jurisdiction Id.

string up to 25
characters

See Figure 15-10, Snapshot of Serving Jurisdiction RoamPolAssgn Details form


(p. 15-26) for an example of the contents of the Serving Jurisdiction RoamPolAssgn
Details form. In this simple example, Policy A will be applied to all users visiting
from jurisdictions 2 and 3.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-25
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Impacts on the OMC-RAN network element

Figure 15-10 Snapshot of Serving Jurisdiction RoamPolAssgn Details form

References

For more information about these forms and fields, see the following CDMA2000
1xEV-DO network documents:

CDMA2000 1xEV-DO RAS Planning and Implementation Guide, 401-614-101


Alcatel-Lucent 9271 EV-DO Radio Network Controller, 401-614-102

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-26

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Configuration
and implementation considerations
...................................................................................................................................................................................................................................
Introduction

This section provides recommendations and guidelines to be considered prior to


configuring and activating the JPPSUBEDA feature.
Dividing network into jurisdictions

It is recommended that the process of provisioning the JPPSUBEDA feature begin with
planning how the wireless network will be divided into jurisdictions. Since a
jurisdiction must be defined (created via OMC-RAN) before it can be referenced by
another jurisdiction, it is recommended that the complete set of jurisdictions be created
before proceeding with creation of jurisdictional policies and policy assignments..
When determining the number of jurisdictions required and the exact boundaries of the
jurisdictions, the following factors should be considered:

ownership or funding source of BTS equipment,


state, county, and city boundaries,
location of major facilities (for example, airports, sports stadiums),
terrain and other factors that affect RF propagation.

When planning how a network will be divided into jurisdictions, it is important to


consider that the geographical territory of a jurisdiction is defined by the set of BTSs
assigned to it. One also needs to consider the geographical area in which each BTS
will be providing the strongest RF signal. Since the Forward Link for each data
connection is generally transmitted by the BTS that provides the strongest signal, the
geographical area where the policies of a jurisdiction are in effect is the cumulative
footprint where the associated BTSs are providing the strongest signal for the users.
Addressing jurisdiction border issues

In some cases, the availability of suitable sites for cellular towers and other
considerations related to RF engineering may cause the desired geographic boundary
for a jurisdiction to not fall cleanly on the border of one or more BTSs. The intended
geographic border may split the service area of multiple BTSs. An example of this
situation is illustrated by Figure 15-11, Example of geographic border splitting BTS
service areas (p. 15-28).

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-27
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Configuration and implementation considerations

Figure 15-11 Example of geographic border splitting BTS service areas

East Centerville

West Centerville

In this example, it is planned to create separate jurisdictions for the towns of East
Centerville and West Centerville. However, in order to get proper RF coverage, the
cellular towers had to be positioned so that the border between these two towns crosses
the primary service area of multiple BTSs.
One method for resolving jurisdiction border issues is the creation of an additional
jurisdiction for the set of BTSs that lie on the border. A separate set of jurisdictional
policies can be created and assigned for this border jurisdiction that treats users from
either of the adjoining jurisdictions as if they were in their home jurisdiction. Please
note that these border jurisdictions would not generally be assigned as the Home
Area for subscribers.
If this technique was applied to the example, the assignment of BTSs to jurisdictions
would be as shown in Figure 15-12, Example use of border jurisdiction (p. 15-29).

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-28

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Configuration and implementation considerations

Figure 15-12 Example use of border jurisdiction


J2

J1
J1

J1

J3

J1

J2

East Centerville

J1

J3

J1
J1
J1

J2
J3

J2

West Centerville

J2
J2

J3
J3

J3

J3
J3

In this example, jurisdiction 1 is for East Centerville territory, jurisdiction 3 is created


for the West Centerville territory, and jurisdiction 3 is created for the border area
between these two towns. Subscribers from these two towns would be assigned a
Home Area of either J1 or J3. No users would be given a Home Area of J2.
Ensure unique Jurisdiction IDs across all linked wireless networks

If service providers use the JPPSUBEDA feature and plan to provide service to
roamers from other Service Nodes (SNs), it is critical to ensure that Jurisdiction IDs
are assigned uniquely across all SNs. If more than one SN uses a Jurisdiction Id, the
system will assume this jurisdiction spans the associated SNs.
If a user has a Home Area value that matches the Jurisdiction Id of the serving BTS,
they are treated as a home subscriber and no jurisdictional policy is applied. If multiple
SNs use the same Jurisdiction Id, then a user will be treated as a home subscriber in
any of those locations where that Jurisdiction Id is used.
It is recommended that the high order digits of the Jurisdiction Id be used to indicate
the region of the jurisdiction (for example city, county, etc.). For example, one region
could use Jurisdiction IDs 101 to 118 and another region could use 201 to 218. Since
the maximum Jurisdiction Id value is 65,535, a total of 655 jurisdiction regions could
be supported using this simple convention.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-29
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Configuration and implementation considerations

Determining the set of jurisdictional policies required

After the complete set of jurisdictions has been defined for the network, the set of
jurisdictional policies that will be required to deal with users visiting from other
jurisdictions should be determined.
Each jurisdiction can create up to four policies that can be assigned for roamers from
specific jurisdictions. In addition, a default policy exists to address the following types
of visiting users:

users without a Home Area specified in their AAA subscriber profile,


users visiting from a jurisdiction for which a policy has not been assigned.

In order to get started defining jurisdiction policies, it is recommended to first divide


the set of jurisdictions into groups based upon the treatment to be given to visitors
from those jurisdictions. Jurisdictional policies to provide the desired treatment for
each of these jurisdiction groups can then be created.
The following are examples of jurisdictional policies that could be created:

TreatAsLocal for roamers to be treated as if they were local users


AdjustedService for roamers that should receive better than standard priority

service

StandardService for roamers that should only receive standard priority service
BasicService for roamers that should only receive lowest priority service

The adjustments of the IUP values for the sample TreatAsLocal policy are shown in
Table 15-11, Sample Jurisdictional Policy TreatAsLocal (p. 15-30).
Note: This policy gives the visiting users their original Inter-User Priority values (as

long as the priority is known).


Table 15-11

Sample Jurisdictional Policy TreatAsLocal

Subscribers Home Inter-User


Priority

Inter-User Priority given by Serving


Jurisdiction

unknown

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-30

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Configuration and implementation considerations

The adjustments of the IUP values for the sample AdjustedService policy are shown
in Table 15-12, Sample Jurisdictional Policy AdjustedService (p. 15-31).
Note: This policy gives visiting users lower Inter-User Priority values than local users.
Table 15-12

Sample Jurisdictional Policy AdjustedService

Subscribers Home Inter-User


Priority

Inter-User Priority given by Serving


Jurisdiction

unknown

The adjustments of the IUP values for the sample StandardService policy are shown
in Table 15-13, Sample Jurisdictional Policy StandardService (p. 15-31).
Note: This policy gives visiting users an Inter-User Priority value of 1 (standard

priority service).
Table 15-13

Sample Jurisdictional Policy StandardService

Subscribers Home Inter-User


Priority

Inter-User Priority given by Serving


Jurisdiction

unknown

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-31
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Configuration and implementation considerations

The adjustments of the IUP values for the sample BasicService policy are shown in
Table 15-14, Sample Jurisdictional Policy BasicService (p. 15-32).
Note: This policy gives visiting users an Inter-User Priority value of 0 (lowest priority

service).
Table 15-14

Sample Jurisdictional Policy BasicService

Subscribers Home Inter-User


Priority

Inter-User Priority given by Serving


Jurisdiction

unknown

In some cases, service providers may wish to configure the Default policy like the
BasicService policy shown above. The Default policy will cover all visiting users
that dont have a defined Home Area and visiting users with a Home Area that is not
listed in the Policy Assignment table. However, it is strongly recommended that service
providers verify that the Home Area attribute has been included in the subscriber
profiles for all expected users before such changes are made to the Default policy.
Creating OMC-RAN user accounts restricted to specific jurisdictions

The JPPSUBEDA feature allows the System Administrator to create additional


OMC-RAN user accounts that are restricted to operate within a specific jurisdiction.
Administrators using these restricted accounts will be able to manage the jurisdictional
policies for their own jurisdiction, but they will not be able to change or view the
jurisdictional policy information for any other jurisdiction.
Important! The creation of these restricted OMC-RAN user accounts is optional.
Any user account with System Administrator permissions is able to manage data
for all jurisdictions.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-32

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Configuration and implementation considerations

The tasks allowed for these two types of OMC-RAN user accounts is presented in
Table 15-15, Tasks permitted for OMC-RAN user account types (p. 15-33).
Table 15-15

Tasks permitted for OMC-RAN user account types

Procedure

Allowed for
System
Administrator
accounts?

Allowed for
Jurisdiction
User Group
accounts?

Activating the feature

Confirming feature activation

Creating jurisdictions

Creating OMC-RAN user account restricted to


jurisdiction

Creating jurisdictional policies

Updating jurisdictional policies (if necessary)

Making jurisdictional policy assignments

Making BTS assignments for a jurisdiction

Viewing BTS assignments for a jurisdiction

N/A

N/A

Setting Subscriber Home Area attribute in AAA


subscriber profiles
Enabling the feature

Deactivating the feature

Perform maintenance operations on BTSs


(pokes)

+ = Service provider must contact their Alcatel-Lucent account representative to

activate the feature.


*= User account can only perform maintenace operations for BTSs assigned to

jurisdiction.
N/A = Not applicable to OMC-RAN. Task is performed on AAA system.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-33
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Implementing
the feature
...................................................................................................................................................................................................................................
Introduction

The following information describes the procedures for implementing the JPPSUBEDA
(FID 12171.5) on an existing Rev. A network with the Per Application QoS feature
(FID 12078.9) and the IUPBEDA (FID 12171.4) enabled.
Complete configuration and implementation requirements

Ensure that all configuration and implementation considerations have been reviewed
before implementing the JPPSUBEDA feature. For more information, see
Configuration and implementation considerations (p. 15-27).
Procedures

To implement the JPPSUBEDA feature, perform the following procedures in sequence:


Activating the feature (p. 15-35)
Confirming feature activation (p. 15-36)
Creating jurisdictions (p. 15-37)
Creating OMC-RAN user account restricted to jurisdiction (p. 15-39)
Creating jurisdictional policies (p. 15-45)
Updating jurisdictional policies (p. 15-47)
Making jurisdictional policy assignments (p. 15-49)
Making BTS assignments for a jurisdiction (p. 15-56)
Viewing BTS assignments for a jurisdiction (p. 15-59)
Setting Subscriber Home Area attribute in AAA (p. 15-62)
Enabling the feature (p. 15-64)
Deactivating the feature (p. 15-66)

Important! When implementing the JPPSUBEDA feature it is recommended that


jurisdictions, jurisdictional policies, policy assignments and BTS assignments are
created before the JPPSUBEDA feature is enabled. These provisioning steps can be
performed if the JPPSUBEDA FAF entry is active. This approach allows
provisioning to be completed and verified before the feature is enabled.
Jurisdictions (and related data) can be added to the system after the JPPSUBEDA
feature is enabled.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-34

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Activating
the feature
...................................................................................................................................................................................................................................
Purpose

This procedure activates the JPPSUBEDA feature in a CDMA2000 1xEV-DO


network.
Execution of this procedure will activate the JPPSUBEDA feature so the other
procedures for implementing this feature can be executed.
Important! The feature will not be enabled (call processing will not be affected)
until the Enabling the feature (p. 15-64) is executed.
Procedure

Perform the following steps:


...................................................................................................................................................................................................

Ask your account executive to activate the following entry in your Feature Activation
File (FAF):
JPPSUPBEDA
...................................................................................................................................................................................................

Proceed to Confirming feature activation (p. 15-36)


END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-35
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Confirming
feature activation
...................................................................................................................................................................................................................................
Purpose

This procedure activates the JPPSUBEDA feature in a CDMA2000 1xEV-DO


network.
Procedure

Perform the following steps:


...................................................................................................................................................................................................

Go to the FxApx Details view from the OMC-RAN Network Manager. The Details
view can be accessed using either of the following techniques:

Right click on the FxApx object and select the Details item from the pop-up
menu.
Double click on the FxApx object.

...................................................................................................................................................................................................

Left click on the EvDO RNC FAF tab of the FxApx Details view and verify the FAF
entry has been activated. The features FAF status is displayed at the bottom of the
page as shown below

END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-36

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Creating
jurisdictions
...................................................................................................................................................................................................................................
Purpose

This procedure creates jurisdictions that are related to the JPPSUBEDA feature. A
jurisdiction must be created before any jurisdictional policies and policy assignments
can be added.
Procedure

Perform the following steps:


...................................................................................................................................................................................................

If the Jurisdiction Group does not exist for the current network, create it by performing
a right click on the network object and select the Create then select the
Jurisdiction Group item from the pop-up menu.
...................................................................................................................................................................................................

Right click the Jurisdiction Group object and select the Create then select the
Serving Jurisdictionitem from the pop-up menu.
...................................................................................................................................................................................................

Enter the desired Jurisdiction ID and Jurisdiction Name in the pop-up form.
Then left click the OK button as shown below:

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-37
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Creating jurisdictions

...................................................................................................................................................................................................

Left click on the + next to the Jurisdiction Group object. This will expand the list
of Serving Jurisdictions under the Jurisdiction Group.
...................................................................................................................................................................................................

Repeat steps Step 2 through Step 3 to create the other Serving Jurisdictions for
your network.
Important! Up to 18 Serving Jurisdictions can be created.
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-38

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Creating
OMC-RAN user account restricted to jurisdiction
...................................................................................................................................................................................................................................
Purpose

This procedure creates an OMC-RAN user account with access restricted to a specific
jurisdiction. Administrators using this type of user account will be able to perform
tasks such as creating jurisdictional policies and perform policy assignments, but they
will not be able to perform tasks that affect data beyond the scope of the jurisdiction.
Important! These steps are performed using the OMC-RAN User & Session
Manager.
Important! This is an optional step. Any task can be performed with the existing
System Administration user accounts.
Procedure

Perform the following steps:


...................................................................................................................................................................................................

Open the User & Session Manager by performing a left click on the System item of
the menu bar of the OMC-RAN Desktop and selecting the User & Session Manager
item from the pop-up menu as shown below:

...................................................................................................................................................................................................

Left click on the Actions item on the menu bar of the User & Session Manager and
select the Create then select the User item from the pop-up menu as shown below:

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-39
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Creating OMC-RAN user account restricted to jurisdiction

...................................................................................................................................................................................................

Populate fields of the user profile on the Create User form. Then left click the Next
button as shown below:

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-40

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Creating OMC-RAN user account restricted to jurisdiction

...................................................................................................................................................................................................

Left click on a JurisdictionUserGroup in the Not Assigned column as shown


below.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-41
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Creating OMC-RAN user account restricted to jurisdiction

Important! The first number after JurisdictionUserGroup_ is the SN Id and the

second number is the jurisdiction Id. The JurisdictionUserGroup is created when the
jurisdiction is created.
...................................................................................................................................................................................................

Left click on right arrow button as shown below:

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-42

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Creating OMC-RAN user account restricted to jurisdiction

The selected JurisdictionUserGroup is moved from the Not Assigned


column to the Assigned column as shown in the example below:
Result:

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-43
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Creating OMC-RAN user account restricted to jurisdiction

...................................................................................................................................................................................................

Left click on the Finish button of the Create user form


END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-44

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Creating
jurisdictional policies
...................................................................................................................................................................................................................................
Purpose

This procedure creates jurisdictional policies that are used by the JPPSUBEDA feature.
Important! These steps are performed using the OMC-RAN Network Manager.
Procedure

Perform the following steps:


...................................................................................................................................................................................................

Select the jurisdiction for which the policy will be created by performing a right click
on the Serving Jurisdiction object and select the ShowOnTree item from the pop-up
menu.
Result:

The jurisdiction subtree is displayed as shown in the following example.

...................................................................................................................................................................................................

Right click on the jurisdiction name at top of the subtree (shown highlighted above)
and select the Create then select the BE Roaming Policy item from the pop-up menu.
...................................................................................................................................................................................................

Enter the Policy Name and the adjusted Inter-User Priority values on the pop-up form.
Then left click the OK button as shown below:

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-45
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Creating jurisdictional policies

...................................................................................................................................................................................................

Repeat steps Step 1 through Step 3 to create the other jurisdictional policies for your
network.
Important! Up to 4 policies can be created per Serving Jurisdiction (in addition to

Default).
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-46

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Updating
jurisdictional policies
...................................................................................................................................................................................................................................
Purpose

This procedure updates jurisdictional policies that are used by the JPPSUBEDA
feature.
Important! These steps are performed using the OMC-RAN Network Manager.
Procedure

Perform the following steps:


...................................................................................................................................................................................................

Select the jurisdiction for which the policy will be created by performing a right click
on the Serving Jurisdiction object and select the ShowOnTree item from the pop-up
menu.
Result:

The jurisdiction subtree is displayed as shown in the following example.

...................................................................................................................................................................................................

Right click on the policy to be updated and select the Details item from the pop-up
menu
...................................................................................................................................................................................................

Left click the Modify button of the Details form. In this example shown below, we are
updating the Default policy.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-47
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Updating jurisdictional policies

...................................................................................................................................................................................................

Update the Inter-User Priority values on the form. Then left click the OK button.
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-48

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Making
jurisdictional policy assignments
...................................................................................................................................................................................................................................
Purpose

This procedure makes jurisdictional policy assignments that control the behavior of the
JPPSUBEDA feature.
Important! These steps are performed using the OMC-RAN Network Manager.
Procedure

Perform the following steps:


...................................................................................................................................................................................................

Select the jurisdiction for which the policy will be updated by performing a right click
on the Serving Jurisdiction object and select the ShowOnTree item from the pop-up
menu.
Result:

The jurisdiction subtree is displayed as shown in the following example.

...................................................................................................................................................................................................

Right click on RoamPolAssgn and select the Details item from the pop-up menu.
...................................................................................................................................................................................................

Left click the Modify button of the Roaming Policy Assignment form.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-49
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Making jurisdictional policy assignments

...................................................................................................................................................................................................

Left click the Add button of the Roaming Policy Assignment form.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-50

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Making jurisdictional policy assignments

...................................................................................................................................................................................................

Left click on the fields of the Roaming Policy Assignments pop-up form and select
the desired values. Then left click the Add button to add this entry to the Roaming
Policy Assignment table as shown below:

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-51
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Result:

Making jurisdictional policy assignments

The entry is added to the Roaming Policy Assignment table as shown below:

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-52

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Making jurisdictional policy assignments

...................................................................................................................................................................................................

Repeat step Step 5 until all required policy assignment entries have been added.
...................................................................................................................................................................................................

Left click the Cancel button to close the Roaming Policy Assignments pop-up form.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-53
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Making jurisdictional policy assignments

...................................................................................................................................................................................................

Left click the OK button on the main Roaming Policy Assignment form to close the
form.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-54

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Making jurisdictional policy assignments

END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-55
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Making
BTS assignments for a jurisdiction
...................................................................................................................................................................................................................................
Purpose

This procedure assigns BTSs to a jurisdiction.


Note: These steps are performed using the OMC-RAN Network Manager.

Important! The policies associated with a jurisdiction will be enabled to affect


calls as soon as a BTS has been assigned (assuming the JPPSUBEDA feature is
also enabled). It is recommended that policies and policy assignments be reviewed
before any BTSs are assigned.
Procedure

Perform the following steps:


...................................................................................................................................................................................................

Right click on the Serving Jurisdiction object to which BTSs are to be assigned and
select the BTS Allocation item from the pop-up menu as shown below:

Result:

The BTS Manager is displayed as shown in the following example.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-56

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Making BTS assignments for a jurisdiction

...................................................................................................................................................................................................

Select the BTS to be assigned and left click the Add button as shown below.

...................................................................................................................................................................................................

Result: The selected BTS is moved from the Available BTSs column to the Assigned
BTSs column as shown in the example below: button as shown below.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-57
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Making BTS assignments for a jurisdiction

...................................................................................................................................................................................................

Repeat step Step 2 as needed to assign all required BTSs to the currently selected
jurisdiction.
...................................................................................................................................................................................................

Left click the OK button on the BTS Allocation Manager.


END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-58

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Viewing
BTS assignments for a jurisdiction
...................................................................................................................................................................................................................................
Purpose

This procedure allows the user to view the set of BTSs that are currently assigned to a
jurisdiction.
Note: These steps are performed using the OMC-RAN Network Manager.
Note: This is an optional step. This procedure is provided in case there is a need to
view the list of BTSs that are assigned to a jurisdiction.
Procedure

Perform the following steps:


...................................................................................................................................................................................................

Go to the Jurisdiction Details view from the OMC-RAN Network Manager. The
Details view for a specific jurisdiction can be accessed using either of the following
techniques:

Right click on the Jurisdictionobject and select the Details item from the pop-up
menu.
Double click on the Jurisdiction object.

Result:

The Jurisdiction Details view is displayed as shown in the following example.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-59
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Viewing BTS assignments for a jurisdiction

...................................................................................................................................................................................................

Left click on the BTS Allocation tab of the Jurisdiction Details view.
The BTS Allocation information is displayed as shown in the following
example.
Result:

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-60

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Viewing BTS assignments for a jurisdiction

...................................................................................................................................................................................................

Left click on the OK button of the Jurisdiction Details page.


END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-61
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Setting
Subscriber Home Area attribute in AAA
...................................................................................................................................................................................................................................
Purpose

This procedure is used to include the Subscriber Home Area attribute in AAA
subscriber profiles. This attribute is used by the JPPSUBEDA feature.
Important! The exact procedures will vary depending on the specific AAA system
being used. Please refer to the documentation for your AAA system for more
information.
Important! This a vendor-specific attribute. Please contact your PDSN vendor to
verify that your PDSN supports this attribute.
Procedure

Perform the following steps:


...................................................................................................................................................................................................

Verify that the AAA dictionary includes the definition for the Lucent-VID. The
definition for the Lucent-VID will appear as follows on the VitalAAA system:
<vendor name=Lucent-VID number=3729 format=rfc/>
...................................................................................................................................................................................................

Verify that the AAA dictionary includes the Lucent-VID-Home-Area definition as a


Vendor Specific Attribute (VSA) with the Lucent-VID. This attribute definition will
appear as follows on the VitalAAA system:.
<avp name=Lucent-VID-Home-Area vendor=Lucent-VID code=11 type=
short/>
</avp>
...................................................................................................................................................................................................

Update subscriber profiles as needed to include the Lucent-VID-Home-Area attribute.


The following example shows a sample subscriber profile for VitalAAA system:

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-62

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Setting Subscriber Home Area attribute in AAA

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
CLIENT_IUP1_J3
User-Password=PASSWORD1 Auth-Type=Local
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Lucent-VID-Home-Area=3
1234567890123456789012345678901212345678901234567890123456789
3GPP2-Inter-User-Priority=1
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Cisco-AVPair=lcp:cdma-user-class=1
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Cisco-AVPair=ip:addr-pool=pdsn-pool
1234567890123456789012345678901212345678901234567890123456789
Callback-Id=0111113137147635
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-63
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Enabling
the feature
...................................................................................................................................................................................................................................
Purpose

This procedure enables the Jurisdictional Priority for Public Safety Users of Best Effort
Data Applications (JPPSUBEDA) (FID 12171.5) feature in a CDMA2000 1xEvDO
network.
Execution of this procedure will cause the network to adjust the Inter-User Priority of
users visting from other jurisdictions based upon the defined jurisdictional policies.
This adjustment of Inter-User Priority values for visiting users will affect their priority
of data transmission on the Forward Link for Best Effort service category data
connections.
Important! The Activating the feature (p. 15-35) procedure must be completed
before this procedure can be executed.
Important! Jurisdictional Priority and Inter-User Priority must be turned on only
from the OMC-RAN.
Procedure

Perform the following steps:


...................................................................................................................................................................................................

Go to the FxApx Details view from the OMC-RAN Network Manager. The Details
view can be accessed using either of the following techniques:

Right click on the FxApx object and select the Details item from the pop-up
menu.
Double click on the FxApx object.

...................................................................................................................................................................................................

Left click on the SN General tab of the FxApx Details view.


...................................................................................................................................................................................................

Left click on the Modify button at the bottom of the SN General page as shown
below:

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-64

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Enabling the feature

...................................................................................................................................................................................................

Left click on the Enable Jurisdictional Priority for Public Safety Users
field and select Yes the menu.
...................................................................................................................................................................................................

Left click on the OK button at the bottom of the SN General page.


END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-65
Issue 5, May 2008
See notice on first page

Jurisdictional Priority for Public Safety Users of Best


Effort Data Applications (JPPSUBEDA)

Deactivating
the feature
...................................................................................................................................................................................................................................
Purpose

This procedure deactivates the JPPSUBEDA feature in a CDMA2000 1xEV-DO


network.
Important! The order of these steps is important. The provisioned jurisdictional
data must be removed before the FAF is deactivated.
Procedure

Perform the following steps:


...................................................................................................................................................................................................

Change the Enable Jurisdictional Priority for Public Safety Users field to no.
...................................................................................................................................................................................................

Delete the Jurisdiction Group object and all jurisdiction data under it.
...................................................................................................................................................................................................

Ask your Alcatel-Lucent account executive to deactivate the following entry in your
Feature Activation File (FAF):
JPPSUPBEDA
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

15-66

16

16
Universal
Traffic Processor
(UTP) Protocol Acceleration in
Hardware

Overview
...................................................................................................................................................................................................................................
Purpose

This chapter describes the Universal Traffic Processor (UTP) Protocol Acceleration in
Hardware feature in CDMA2000 1xEV-DO networks.
Feature summary

The UTP Protocol Acceleration in Hardware feature supports hardware acceleration for
Revision A (Rev. A) Forward Link bearer processing to Signaling Bus-1xEV-DO
Modem (SB-EVM).
Feature Identifier (FID)

A unique Feature Identifier (FID) is assigned to each feature. The FID of the UTP
Protocol Acceleration in Hardware feature is FID 12780.3.
Impacts on user interfaces

The UTP Protocol Acceleration in Hardware affects the user interfaces that are listed in
the following table.
User interface

Feature impact

Configuration management: Element


Management System (EMS) and
Operations and Maintenance Center Radio Access Network (OMC-RAN)

See Configuration management (p. 16-7)

Service measurements

See Impacts on service measurements


(p. 16-8)

Automatic Message Accounting (AMA)


subsystem

None

....................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
16-1
Issue 5, May 2008
See notice on first page

Universal Traffic Processor (UTP) Protocol Acceleration in


Hardware

Overview

User interface

Feature impact

Technician Interface (TI) (input/output


messages)

None

Intended audience

This document is intended for technicians, engineers, and system administrators who
implement or maintain the UTP Protocol Acceleration in Hardware feature in a
CDMA2000 1xEV-DO network.
To obtain technical support, documentation, and training or submit feedback

The Online Customer Support (OLCS) web site (http://support.lucent.com/) provides


access to technical support, related documentation, related training, and feedback tools.
The site also provides account registration for new users.
Contents
Availability

16-3

Prerequisites

16-4

Feature description

16-5

Feature interactions

16-6

Configuration management

16-7

Impacts on service measurements

16-8

Activating the feature

16-9

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

16-2

Universal Traffic Processor (UTP) Protocol Acceleration in


Hardware

Availability
...................................................................................................................................................................................................................................
Release availability

The UTP Protocol Acceleration in Hardware feature is available in Releases 30.0 and
later.
Market availability

The UTP Protocol Acceleration in Hardware feature is available in the North American
Region (NAR) market only.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
16-3
Issue 5, May 2008
See notice on first page

Universal Traffic Processor (UTP) Protocol Acceleration in


Hardware

Prerequisites
...................................................................................................................................................................................................................................
Introduction

The UTP Protocol Acceleration in Hardware feature has the following prerequisites.
Supported technologies

The UTP Protocol Acceleration in Hardware feature is supported in the following


air-interface technologies:

CDMA cellular
CDMA PCS

Software requirements

The UTP Protocol Acceleration in Hardware feature requires Release 30.0 or later.
Hardware requirements

The UTP Protocol Acceleration in Hardware feature requires that the Node Card
Resource Monitor (NCRM) must be enabled before any UTPs are installed in the
frame. There are no new hardware upgrades needed for currently installed UTPs from
Release 29.0 to Release 30.0.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

16-4

Universal Traffic Processor (UTP) Protocol Acceleration in


Hardware

Feature
description
...................................................................................................................................................................................................................................
Introduction

The following information describes the functionality, benefits, and operation of the
UTP Protocol Acceleration in Hardware feature.
Functionality

The Universal Traffic Processor (UTP) is a next generation traffic processor. The
primary difference in capability is the addition of a new Fast Protocol Processor (FPP)
that performs much of the protocol processing in hardware rather than in software.
How the feature operates

The UTP Protocol Acceleration in Hardware feature capability is defined as delivering


additional hardware acceleration by extending the Release 29.0 Forward Link Rev. 0
bearer processing to all types of Rev. A Forward Link bearer processing including
Multiflow Packet Application (MFPA) and Default Packet Application (DPA)
capabilities. The Rev. A processing supports some additional capabilities that are not
present in Rev. 0 such as optional per flow RMI header compression, Quality of
Service (QoS), and multiple flows per connection. The UTP hardware acceleration
capabilities are identical whether the UTP is deployed in a R1SR frame or Universal
Network Cabinet (UNC) frame. The inter-connectivity advantages of the UNC allows
the UTP to operate at a much higher performance level but no additional acceleration
is performed in the UNC.
Important! Only UTPs are supported in UNCs (that is no 690s or 752s).
The UTP hardware accelerated traffic processing is being delivered in phases. The first
set of functionality was defined in feature, UTP Protocol Acceleration in Hardware
Requirements- Phase 1 (12780.0) and was completed in feature, UTP Protocol
Acceleration in Hardware Delivery- Phase 1 (12780.1). The second set of functionality
is defined in feature, UTP Protocol Acceleration in Hardware Requirements - Phase 2
(12780.2) and delivered in this feature, UTP Protocol Acceleration in Hardware
(12780.3).

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
16-5
Issue 5, May 2008
See notice on first page

Universal Traffic Processor (UTP) Protocol Acceleration in


Hardware

Feature
interactions
...................................................................................................................................................................................................................................
Introduction

The UTP Protocol Acceleration in Hardware feature is dependent on the following


phase features:

UTP Protocol Acceleration in Hardware Requirements - Phase 1 (12780.0)


UTP Protocol Acceleration in Hardware - Phase 1 (12780.1)
UTP Protocol Acceleration in Hardware - Phase 2 (12780.2)

UTP Protocol Acceleration in Hardware Requirements- Phase 1 (12780.0)

The UTP Protocol Acceleration in Hardware Requirements - Phase 1 feature integrates


the new UTP board into the R1SR frame of the 1xEV-DO RNC. This includes
Operations, Administration and Maintenance (OA&M) support for the UTP, as well as
moving the Revision 0 (Rev. 0) forward bearer call processing from the host processor
to the Functional Programmable Gate Array (FPGA) to be hardware accelerated.
UTP Protocol Acceleration in Hardware Delivery- Phase 1 (12780.1)

The UTP Protocol Acceleration in Hardware Delivery - Phase 1 feature delivers Phase
1 of the 1xEV-DO UTP in the R1SR frame. The protocol stack processing in and out
is performed by the hardware as well as the application forward link processing for
Rev. 0 calls.
UTP Protocol Acceleration in Hardware Requirements - Phase 2 (12780.2)

The UTP Protocol Acceleration in Hardware Requirements - Phase 2 feature continues


the second set of requirements for hardware acceleration capabilities of Phase 1 which
includes:

Forward Link Rev A Processing with Default Packet Application (DPA)


Forward Link Rev A Processing with Multiflow Packet Application (MFPA) and
Quality of Service (QoS) applications
Forward Link RMI compression for Rev. A only capabilities on-demand (optional
per flow)

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

16-6

Universal Traffic Processor (UTP) Protocol Acceleration in


Hardware

Configuration
management
...................................................................................................................................................................................................................................
Element Management System (EMS) configuration management

Important! Element Management System (EMS) does not support UTP. The
customer must have an OMC-RAN if they want a UTP.
Operations and Maintenance Center - Radio Access Network (OMC-RAN) configuration
management

For more information about the different 1xEV-DO OA&M interfaces that are used in
performing OA&M tasks on the EV-DO controller and its managed resouces,
including the purpose of each interface and how to access it, see Alcatel-Lucent 9271
EV-DO Radio Network Controller, 401-614-102, Chapter 3, User Interfaces.
See Appendix 7 of Alcatel-Lucent 9271 EV-DO Radio Network Controller,
401-614-102 for basic information in order to:

understand the OMC-RAN,


understand the layout of EV-DO information on the OMC-RAN, and
provisioning activities on EV-DO network and elements from the OMC-RAN.

Also see the About this information product at the beginning of this document for
the most commonly-used ways to find certain information on EMS and where to find
the equivalent information on the OMC-RAN, or CDMA2000 1xEV-DO
Configurations Parameters Guide, 401-614-324.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
16-7
Issue 5, May 2008
See notice on first page

Universal Traffic Processor (UTP) Protocol Acceleration in


Hardware

Impacts
on service measurements
...................................................................................................................................................................................................................................
Introduction

The Release 30.0 UTP Protocol Acceleration in Hardware is backwards compatible


with the Release 29.0 capable UTPs for existing service measurements.
References

For detailed information about 1xEV-DO service measurements, see CDMA2000


1xEV-DO Service Measurements, , 401-614-326.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

16-8

Universal Traffic Processor (UTP) Protocol Acceleration in


Hardware

Activating
the feature
...................................................................................................................................................................................................................................
Purpose

This UTP Protocol Acceleration in Hardware feature uses no licensing and no FAF. If
the Release 30 software is purchased and UTPs are already on the system, then the
UTP Protocol Acceleration in Hardware feature is included. The UTP provisioning
procedure is similar to the TP-752i hardware provisioning procedure and is found in
CDMA2000 1xEV-DO Radio Network Controller, 401-614-102.
The Release 30.0 UTP Protocol Acceleration in Hardware feature is backwards
compatible with the Release 29.0 capable UTPs for existing operations, administration,
maintenance and provisioning functions.
For details on the Application Licensing Process procedures, see CDMA2000
1xEV-DO Radio Access System Planning and Implementation Guide, 401-614-101.
For detailed procedures regarding the impact of OMC-RAN becoming a mandatory
platform for EV-DO in R29.1 and later, see Appendix 7 of Alcatel-Lucent 9271 EV-DO
Radio Network Controller, 401-614-102.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
16-9
Issue 5, May 2008
See notice on first page

17

17
Backhaul
Enhancement in
Support of Small Packets on the
Reverse and Forward Links in
1xEV-DO

Overview
...................................................................................................................................................................................................................................
Purpose

This document describes the following optional features in CDMA2000 1xEV-DO


networks.

Backhaul Enhancement in Support of Small Packets on the Reverse Link in


1xEV-DO (Phase 1a) (FID 12102.5)
Backhaul Enhancement in Support of Small Packets on the Forward Link in
1xEV-DO (Phase 1b) (FID 12102.14)

Feature summary

The following summarizes the features covered in this document.


Backhaul Enhancement in Support of Small Packets on the Reverse Link in
1xEV-DO (Phase 1a) (FID 12102.5)

The Backhaul Enhancement in Support of Small Packets on the Reverse Link in


1xEV-DO (Phase 1a) (FID 12102.5) feature improves the backhaul utilization on the
reverse link of a CDMA 3G-1x Evolution Data Optimized (1x EVDO) Revision A
(Rev. A) network for applications that are characterized by small packets sizes such as
Voice Over IP (VOIP), and Push To Talk (PTT).
The current EV DO Backhaul design is not appropriate for carrying small packets such
as VOIP, and PTT applications where the voice frames are much smaller than the IP
packets of a data application. Moreover, the majority of the current Rev. A, and
Revision 0 (Rev. 0) BE traffic on the reverse link contains Positive Acknowledge/Not
Acknowledged (ACK/NAK) frames that are even smaller in size than a voice frame.
Therefore, for the EV DO Rev. A network to carry the small bearer traffic efficiently
the backhaul overhead must be reduced. As Phase 1a, this feature provides header
compression of the reverse link backhaul bearer traffic processing messages between
the Base Transceiver Station (BTS), and the Radio Network Controller (RNC).

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
17-1
Issue 5, May 2008
See notice on first page

Backhaul Enhancement in Support of Small Packets on


the Reverse and Forward Links in 1xEV-DO

Overview

This header compression is transparent to the edge router, since it is application layer
functionality.
Backhaul Enhancement in Support of Small Packets on the Forward Link in
1xEV-DO (Phase 1b) (FID 12102.14)

The Backhaul Enhancement in Support of Small Packets on the Forward Link in


1xEV-DO (Phase 1b) (FID 12102.14) feature improves the backhaul utilization on the
forward link of a 1x EVDO Rev. A network for applications that are characterized by
small packets sizes such as VOIP, and PTT.
The current EV DO Backhaul design is not appropriate for carrying small packets such
as VOIP, and PTT applications where the voice frames are much smaller than the IP
packets of a data application.
Therefore, for the EV DO Rev. A network to carry the small bearer traffic efficiently
the backhaul overhead must be reduced.
As Phase 1b, this feature provides selective header compression of the PTT forward
link backhaul bearer traffic processing messages between the RNC, and the BTS. This
functionality is extendable to include the VOIP application when it becomes available
in later releases. This header compression is transparent to the edge router, since it is
application layer functionality.
Impacts on user interfaces

The features that are described in this document impact the following user interfaces:
Feature

User interface

Feature impact

Backhaul Enhancement in
Support of Small Packets
on the Reverse Link in
1xEV-DO (Phase 1a) (FID
12102.5)

Element Management
System (EMS)
configuration management
and the Operations and
Maintenance Center Radio Access Network
(OMC-RAN).

See Implementing the


features (p. 17-14).

Service measurements

None

Automatic Message
Accounting (AMA)
subsystem

None

Technician Interface (TI)


(input/output messages)

None

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

17-2

Backhaul Enhancement in Support of Small Packets on


the Reverse and Forward Links in 1xEV-DO

Overview

Feature

User interface

Feature impact

Backhaul Enhancement in
Support of Small Packets
on the Forward Link in
1xEV-DO (Phase 1b) (FID
12102.14)

Element Management
System (EMS)
configuration management
and the OMC-RAN.

See Implementing the


features (p. 17-14).

Service measurements

None

Automatic Message
Accounting (AMA)
subsystem

None

Technician Interface (TI)


(input/output messages)

None

Intended audience

This document is intended for technicians, engineers, and system administrators who
implement or maintain the Backhaul Enhancement in Support of Small Packets on the
Reverse and Forward Links in 1xEV-DO feature and/or related features in a
CDMA2000 1xEV-DO network.
To obtain technical support, documentation, and training or submit feedback

The Online Customer Support (OLCS) web site (http://support.lucent.com/) provides


access to technical support, related documentation, related training, and feedback tools.
The site also provides account registration for new users.
Contents
Availability

17-5

Prerequisites

17-7

Feature description: Backhaul Enhancement in Support of Small Packets


on the Reverse Link in 1xEV-DO (Phase 1a) (FID 12102.5)

17-9

Feature description: Backhaul Enhancement in Support of Small Packets


on the Forward Link in 1xEV-DO (Phase 1b) (FID 12102.14)

17-10

Feature interactions: Backhaul Enhancement in Support of Small Packets


on the Reverse and Forward Links in 1xEV-DO features

17-11

Implementing the features

17-14

Activating the Backhaul Enhancement in Support of Small Packets on


the Reverse and Forward Links in 1xEV-DO features via EMS

17-15

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
17-3
Issue 5, May 2008
See notice on first page

Backhaul Enhancement in Support of Small Packets on


the Reverse and Forward Links in 1xEV-DO

Overview

Deactivating the Backhaul Enhancement in Support of Small Packets on


the Reverse and Forward Links in 1xEV-DO feature via EMS

17-17

Activating the Backhaul Enhancement in Support of Small Packets on


the Reverse and Forward Links in 1xEV-DO features via OMC-RAN

17-18

Deactivating the Backhaul Enhancement in Support of Small Packets on


the Reverse and Forward Links in 1xEV-DO features via OMC-RAN

17-20

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

17-4

Backhaul Enhancement in Support of Small Packets on


the Reverse and Forward Links in 1xEV-DO

Availability
...................................................................................................................................................................................................................................
Release availability

The following table identifies the Advanced Mobile Phone Service/Personal


Communications Services (AMPS/PCS) software releases in which the Backhaul
Enhancement in Support of Small Packets on the Reverse and Forward Links in
1xEV-DO and related features are available.
Feature

Available in

Backhaul Enhancement in Support of Small


Packets on the Reverse Link in 1xEV-DO
(Phase 1a)

Releases 29.0 and later

Backhaul Enhancement in Support of Small


Packets on the Forward Link in 1xEV-DO
(Phase 1b) (FID 12102.14)

Releases 29.0 and later

Market availability

The Backhaul Enhancement in Support of Small Packets on the Reverse and Forward
Links in 1xEV-DO and related features are available in the following markets:
Feature

Available in

Backhaul Enhancement in
Support of Small Packets on the
Reverse Link in 1xEV-DO (Phase
1a)

North American Region (NAR) markets

Backhaul Enhancement in
Support of Small Packets on the
Forward Link in 1xEV-DO
(Phase 1b)

North American Region (NAR) markets

Restricted Availability

The features that this document describes have Restricted Availability (RA). Restricted
Availability means that a feature has been developed for specific customers only.
Restricted Availability features have been tested in specific environments for those
select customers and have not been designated as Generally Available (GA). These
features may be made available to other customers, but additional development may be

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
17-5
Issue 5, May 2008
See notice on first page

Backhaul Enhancement in Support of Small Packets on


the Reverse and Forward Links in 1xEV-DO

Availability

needed. Please contact your customer team to determine whether additional


development is necessary to activate these features and arrange for testing of these
features in your network.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

17-6

Backhaul Enhancement in Support of Small Packets on


the Reverse and Forward Links in 1xEV-DO

Prerequisites
...................................................................................................................................................................................................................................
Introduction

The Backhaul Enhancement in Support of Small Packets on the Reverse and Forward
Links in 1xEV-DO and related features have the following prerequisites.
Supported technologies

The Backhaul Enhancement in Support of Small Packets on the Reverse and Forward
Links in 1xEV-DO and related features are supported in the following air-interface
technology:

1xEV-DO

Software requirements

The following summarizes the features described in this document.


Backhaul Enhancement in Support of Small Packets on the Reverse Link in
1xEV-DO (Phase 1a) (FID 12102.5)

The Backhaul Enhancement in Support of Small Packets on the Reverse Link in


1xEV-DO (Phase 1a) feature requires Release 29.0 or later. The activation of the
Backhaul Enhancement in Support of Small Packets on the Reverse Link in 1xEV-DO
(Phase 1a) feature is dependent on the 1xEV-DO Basic Rev. A Feature Bundle, this
means the 1xEV-DO Basic Rev. A Feature Bundle needs to be activated before the
activation of any of these features.
Backhaul Enhancement in Support of Small Packets on the Forward Link in
1xEV-DO (Phase 1b) (FID 12102.14)

The Backhaul Enhancement in Support of Small Packets on the Forward Link in


1xEV-DO (Phase 1b) feature requires Release 29.0 or late. The activation of the
Backhaul Enhancement in Support of Small Packets on the Forward Link in 1xEV-DO
(Phase 1b) feature is dependent on the 1xEV-DO Basic Rev. A Feature Bundle, this
means the 1xEV-DO Basic Rev. A Feature Bundle needs to be activated before the
activation of any of these features.
Hardware requirements

The following summarizes the features described in this document.


Backhaul Enhancement in Support of Small Packets on the Reverse Link in
1xEV-DO (Phase 1a) (FID 12102.5)

The Backhaul Enhancement in Support of Small Packets on the Reverse Link in


1xEV-DO (Phase 1a) feature is restricted to SBEVM boards.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
17-7
Issue 5, May 2008
See notice on first page

Backhaul Enhancement in Support of Small Packets on


the Reverse and Forward Links in 1xEV-DO

Prerequisites

Backhaul Enhancement in Support of Small Packets on the Forward Link in


1xEV-DO (Phase 1b) (FID 12102.14)

The Backhaul Enhancement in Support of Small Packets on the Forward Link in


1xEV-DO (Phase 1b) feature is restricted to SBEVM boards.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

17-8

Backhaul Enhancement in Support of Small Packets on


the Reverse and Forward Links in 1xEV-DO

Feature description: Backhaul Enhancement in Support of


Small Packets on the Reverse Link in 1xEV-DO (Phase 1a)
(FID
12102.5)
...................................................................................................................................................................................................................................
Introduction

The following information describes the functionality, benefits, and operation of the
Backhaul Enhancement in Support of Small Packets on the Reverse Link in 1xEV-DO
(Phase 1a) feature.
Functionality

The Backhaul Enhancement in Support of Small Packets on the Reverse Link in


1xEV-DO (Phase 1a) feature provides header compression of the reverse link backhaul
bearer traffic processing messages between the BTS, and the RNC. This header
compression is transparent to the edge router, since it is application layer functionality.
Benefits

Although the initial intent of Backhaul Enhancement in Support of Small Packets on


the Reverse Link in 1xEV-DO (Phase 1a) feature was to improve the backhaul
utilization in the reverse direction for the applications that are characterized by small
packet sizes, for example, VOIP and PTT, it applies to all reverse link flows, including
Rev. A BE and Rev. 0 flows in an 1xEV-DO Rev. A network.
Important! This feature is restricted to SBEVM boards.
How the feature operates

Once the FAF is activated, the Backhaul Enhancement in Support of Small Packets on
the Forward Link in 1xEV-DO (Phase 1b) feature is enabled or disabled via either the
EMS or the OMC-RAN. Please refer to Implementing the features (p. 17-14) for
more details.
Important! This feature is restricted to SBEVM boards.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
17-9
Issue 5, May 2008
See notice on first page

Backhaul Enhancement in Support of Small Packets on


the Reverse and Forward Links in 1xEV-DO

Feature description: Backhaul Enhancement in Support of


Small Packets on the Forward Link in 1xEV-DO (Phase 1b)
(FID
12102.14)
...................................................................................................................................................................................................................................
Introduction

The following information describes the functionality, benefits, and operation of the
Backhaul Enhancement in Support of Small Packets on the Forward Link in 1xEV-DO
(Phase 1b) feature.
Functionality

The Backhaul Enhancement in Support of Small Packets on the Forward Link in


1xEV-DO (Phase 1b) feature provides selective header compression of the PTT
forward link backhaul bearer traffic processing messages between the RNC, and the
BTS. This functionality is extendable to include the VOIP application when it becomes
available in later releases. This header compression is transparent to the edge router,
since it is application layer functionality.
Benefits

This feature improves the backhaul utilization in the forward direction for two specific
applications that are characterized by small packet sizes, namely VOIP, and PTT.
Important! This feature is restricted to SBEVM boards.
How the feature operates

Once the FAF is activated, the Backhaul Enhancement in Support of Small Packets on
the Forward Link in 1xEV-DO (Phase 1b) feature is enabled or disabled via either the
EMS or the OMC-RAN. Please refer to Implementing the features (p. 17-14) for
more details.
Important! This feature is restricted to SBEVM boards.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

17-10

Backhaul Enhancement in Support of Small Packets on


the Reverse and Forward Links in 1xEV-DO

Feature interactions: Backhaul Enhancement in Support of


Small Packets on the Reverse and Forward Links in 1xEV-DO
features
...................................................................................................................................................................................................................................
Introduction

Backhaul Enhancement in Support of Small Packets on the Reverse and Forward Links
in 1xEV-DO features are dependent on the 1xEV-DO Basic Rev. A Feature Bundle and
the 1xEV-DO Enhanced DOrA Feature Bundle. This means that the 1xEV-DO Basic
Rev. A Feature Bundle and the 1xEV-DO Enhanced DOrA Feature Bundle need to be
activated before the activation of any of these features:

1xEV-DO Basic Rev. A Feature Bundle consists of FIDs 12078.2, 12078.3,


12078.4, 12078.5 and 12078.7

1xEV-DO Basic Rev. A Feature Bundle

The 1xEV-DO Basic Rev. A Feature Bundle consists of FIDs 12078.2, 12078.3,
12078.4, 12078.5 and 12078.7.
Enhanced Reverse and Forward Links using Enhanced MAC Protocols with Rev.
A Subtype 2 Physical Layer (FID 12078.2)

This feature is part of the Rev. A Basic package of features, also referred to as Basic
Rev. A Feature Bundle. This feature introduces the support of the full Rev. A Physical
Layer with the complete set of Rev. A enhanced Medium Access Control (MAC)
protocols that is the following MAC protocols are supported:

Enhanced Control Channel (CC) MAC


Enhanced Forward Traffic Channel (FTC) MAC
Enhanced Access Channel (AC) MAC
Enhanced Subtype 3 Reverse Traffic Channel (RTC) MAC

This feature is supported on all ModCell BTS types using the new HRPD Rev. A
modem board, the SB-EVM for ModCell 4.0 and variants or the SB-EVMm for
ModCell 1-3. This feature is supported only by the Rev. A capable RNC.
Generic Attribute Update Protocol (GAUP) for Dynamic Parameters Update (FID
12078.3)

This feature is part of the Rev. A Basic package of features. This feature allows
configuration attribute changes without costly session configuration protocol exchange
and without releasing the connection. It allows the AT and the AN to use the GAUP to
update values of the session parameter attributes belonging to different lower and
higher layer protocols and applications.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
17-11
Issue 5, May 2008
See notice on first page

Backhaul Enhancement in Support of Small Packets on


the Reverse and Forward Links in 1xEV-DO

Feature interactions: Backhaul Enhancement in Support


of Small Packets on the Reverse and Forward Links in
1xEV-DO features

HRPD Rev. A Support on ModCell 1-3 BTS Platforms using SB-EVMm (FID
12078.4)

This feature is part of the Rev. A Basic package of features and provides the necessary
hardware and software for the ModCell 1-3 products to make use of any other Rev. A
feature. This feature supports HRPD Rev. A technology on all ModCell 1-3. This
feature includes Software, OA&M and Service Measurements support related to HRPD
Rev. A for the ModCell 1-3 BTS platforms.
The following ModCell 1.0/2.0/3.0 BTS products will be supported:

ModCell 3.0
ModCell 2.0
ModCell 1.0

The term ModCell 1-3 is used in this chapter to include the variants listed above.
HRPD Rev. A Support on ModCell 4.0 BTS Platforms using SB-EVM (FID 12078.5)
This feature is part of the Rev. A Basic package of features and provides the necessary
hardware and software for the ModCell 4.0 products to make use of any other Rev. A
feature. This feature supports HRPD Rev. A technology on all ModCell 4.0 Platforms.
This feature includes Software, OA&M and Service Measurements support related to
HRPD Rev. A for the ModCell 4.0 platforms.
The following ModCell 4.0 products will be supported:

ModCell 4.0
ModCell 4.0 B
Compact 4.0
Compact 4.0 B
HD 4.0
HD 4.0 B

Digital Host 4.0


Digital Host 4.0 B

The term ModCell 4.0 is used in this chapter to include the variants listed above.
Inter and Intra-RNC Handoff Enhancement (FID 12078.7)

This feature is part of the Rev. A Basic package of features. The purpose of this feature
is to support, in both Rel 0 systems and in mixed Rel 0/Rev. A systems:

every type of handoff that is currently supported in a Rel 0 system (soft/softer on


traffic channel; hard handoff across carriers on traffic channel; inter-RNC dormant
session handoff)
handoffs from Rev. A PHYsical/Medium Access Control (PHY/MAC) connections
to Rel 0 PHY/MAC connections.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

17-12

Backhaul Enhancement in Support of Small Packets on


the Reverse and Forward Links in 1xEV-DO

Feature interactions: Backhaul Enhancement in Support


of Small Packets on the Reverse and Forward Links in
1xEV-DO features

This feature does not include active handoff from Rel 0 to Rev. A systems.

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
17-13
Issue 5, May 2008
See notice on first page

Backhaul Enhancement in Support of Small Packets on


the Reverse and Forward Links in 1xEV-DO

Implementing
the features
...................................................................................................................................................................................................................................
Process

To implement the Backhaul Enhancement in Support of Small Packets on the Reverse


and Forward Links in 1xEV-DO features, go to the following section:
Activating the Backhaul Enhancement in Support of Small Packets on the Reverse and
Forward Links in 1xEV-DO features via EMS (p. 17-15)
Deactivating the Backhaul Enhancement in Support of Small Packets on the Reverse
and Forward Links in 1xEV-DO feature via EMS (p. 17-17)
Activating the Backhaul Enhancement in Support of Small Packets on the Reverse and
Forward Links in 1xEV-DO features via OMC-RAN (p. 17-18)
Deactivating the Backhaul Enhancement in Support of Small Packets on the Reverse
and Forward Links in 1xEV-DO features via OMC-RAN (p. 17-20)

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

17-14

Backhaul Enhancement in Support of Small Packets on


the Reverse and Forward Links in 1xEV-DO

Activating the Backhaul Enhancement in Support of Small


Packets on the Reverse and Forward Links in 1xEV-DO
features
via EMS
...................................................................................................................................................................................................................................
Purpose

This section explains the activation of the Backhaul Enhancement in Support of Small
Packets on the Reverse and Forward Links in 1xEV-DO features in a CDMA2000
1xEV-DO network.
Procedure

The FAF for the feature must be installed or activated on the OMP before the feature
could be enabled.
...................................................................................................................................................................................................

From the Service Node screen go to General Section 3 screen.


...................................................................................................................................................................................................

To enable the Backhaul Enhancement in Support of Small Packets on the Reverse Link
in 1xEV-DO (Phase 1a) feature, select the Yes radio button for RMI HC Feature RL
Enable field. Refer to Figure 17-1, EMS SN General Screen (p. 17-16).

To enable the Backhaul Enhancement in Support of Small Packets on the Forward


Link in 1xEV-DO (Phase 1b) feature, select the Yes radio button for RMI HC Feature
FL Enable field. Refer to Figure 17-1, EMS SN General Screen (p. 17-16).

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
17-15
Issue 5, May 2008
See notice on first page

Backhaul Enhancement in Support of Small Packets on


the Reverse and Forward Links in 1xEV-DO

Activating the Backhaul Enhancement in Support of Small


Packets on the Reverse and Forward Links in 1xEV-DO
features via EMS

Figure 17-1 EMS SN General Screen

END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

17-16

Backhaul Enhancement in Support of Small Packets on


the Reverse and Forward Links in 1xEV-DO

Deactivating the Backhaul Enhancement in Support of Small


Packets on the Reverse and Forward Links in 1xEV-DO feature
via
EMS
...................................................................................................................................................................................................................................
Purpose

This section explains the deactivation of the Backhaul Enhancement in Support of


Small Packets on the Reverse and Forward Links in 1xEV-DO features in a
CDMA2000 1xEV-DO network.
Procedure

If the FAF for the feature is not installed or activated on the OMP, the feature is by
default deactivated or disabled. Otherwise:
...................................................................................................................................................................................................

The FAF for the feature must be installed or activated on the OMP before the feature
could be enabled.
...................................................................................................................................................................................................

From the Service Node screen go to General Section 3 screen.


...................................................................................................................................................................................................

To disable the Backhaul Enhancement in Support of Small Packets on the Reverse


Link in 1xEV-DO (Phase 1a) feature, select the No radio button for RMI HC Feature
RL Enable field. Refer to Figure 17-1, EMS SN General Screen (p. 17-16).

To disable the Backhaul Enhancement in Support of Small Packets on the Forward


Link in 1xEV-DO (Phase 1b) feature, select the No radio button for RMI HC Feature
FL Enable field. Refer to Figure 17-1, EMS SN General Screen (p. 17-16).
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
17-17
Issue 5, May 2008
See notice on first page

Backhaul Enhancement in Support of Small Packets on


the Reverse and Forward Links in 1xEV-DO

Activating the Backhaul Enhancement in Support of Small


Packets on the Reverse and Forward Links in 1xEV-DO
features
via OMC-RAN
...................................................................................................................................................................................................................................
Purpose

This section explains the activation of the Backhaul Enhancement in Support of Small
Packets on the Reverse and Forward Links in 1xEV-DO features in a CDMA2000
1xEV-DO network.
Procedure

The FAF for the feature must be installed or activated on the OMP before the feature
could be enabled.
...................................................................................................................................................................................................

Once the OMC-RAN is open, click on Global Config DO


...................................................................................................................................................................................................

Click on SN General, and scroll down to General Section 4 section.


...................................................................................................................................................................................................

To enable the Backhaul Enhancement in Support of Small Packets on the Reverse Link
in 1xEV-DO (Phase 1a) feature, select the Yes from the drop down option menu RMI
HC Feature RL Enable field. Refer to Figure 17-2, OMC General Screen (p. 17-19).

To enable the Backhaul Enhancement in Support of Small Packets on the Forward


Link in 1xEV-DO (Phase 1b) feature, select the Yes from the drop down option menu
RMI HC Feature FL Enable field. Refer to Figure 17-2, OMC General Screen
(p. 17-19).

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

17-18

Backhaul Enhancement in Support of Small Packets on


the Reverse and Forward Links in 1xEV-DO

Activating the Backhaul Enhancement in Support of Small


Packets on the Reverse and Forward Links in 1xEV-DO
features via OMC-RAN

Figure 17-2 OMC General Screen

END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
17-19
Issue 5, May 2008
See notice on first page

Backhaul Enhancement in Support of Small Packets on


the Reverse and Forward Links in 1xEV-DO

Deactivating the Backhaul Enhancement in Support of Small


Packets on the Reverse and Forward Links in 1xEV-DO
features
via OMC-RAN
...................................................................................................................................................................................................................................
Purpose

This section explains the activation of the Backhaul Enhancement in Support of Small
Packets on the Reverse and Forward Links in 1xEV-DO features in a CDMA2000
1xEV-DO network.
Procedure

If the FAF for the feature is not installed or activated on the OMP, the feature is by
default deactivated or disabled. Otherwise:
...................................................................................................................................................................................................

Once the OMC-RAN is open, click on Global Config DO


...................................................................................................................................................................................................

Click on SN General, and scroll down to General Section 4 section.


...................................................................................................................................................................................................

To disable the Backhaul Enhancement in Support of Small Packets on the Reverse


Link in 1xEV-DO (Phase 1a) feature, select the No from the drop down option menu
RMI HC Feature RL Enable field. Refer to Figure 17-2, OMC General Screen
(p. 17-19).
To disable the Backhaul Enhancement in Support of Small Packets on the Forward
Link in 1xEV-DO (Phase 1b) feature, select the No from the drop down option menu
RMI HC Feature FL Enable field. Refer to Figure 17-2, OMC General Screen
(p. 17-19).
END OF STEPS

...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

17-20

Glossary

....................................................................................................................................................................................................................................

Numerics
1xEV-DO

CDMA 3G-1x EVolution Data Optimized


1x evolution, data only (CDMA2000 ) has been recognized as a 3G IMT-2000 standard.
3G1X

3rd Generation CDMA


....................................................................................................................................................................................................................................

AAA

Accounting, Authentication and Authorization


ACK

Positive Acknowledge
AMA

Automatic Message Accounting


AMPS

Advanced Mobilel Phone Service


AMPS/PCS

Advanced Mobile Phone Service/Personal Communication Services


AN

Access Network
AP

Application Processor
ASCII

Access and Cross Connect System II

....................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
GL-1
Issue 5, May 2008
See notice on first page

Glossary

AT

Access Terminal
....................................................................................................................................................................................................................................

BCMCS

Broadcast/Multicast Service
BE

Best Effort
BP

Bulk Provisioning
BSN

Broadcast Serving Node


BTS

Base Transceiver System


BTS is the industry standard for base station. It is the physical equipment that provides
the air interface to subscriber access terminals. It is the box that contains the digital and
RF equipment. It does not included the antennas or cabling to them. The EMS GUI uses
BTS to mean Base Transceiver System.
....................................................................................................................................................................................................................................

CARR

Carrier
CCU

Channel Control Unit


CDM

CDMA Digital Module


CDMA

Code Division Multiple Access


CF

Call Forwarding
CFC

Connection Final Class


CFCQ

Connection Final Class Qualifier


cHDLC

Cisco HDLC
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

GL-2

Glossary

CLI

Command Line Interface


CLIP

Calling Line Identification Presentation


CLIR

Calling Line Identification Restriction


CN

Cellular Networking
CP

Call Processing
CS

Conversational Speech
CTA

Customer Technical Advocate


CTS

Lucent Customer Technical Support


CV

Conversational Video
CW

Call Waiting
....................................................................................................................................................................................................................................

DHCP (Dynamic Host Configuration Protocol)

An Internet protocol for automating the configuration of computers on a network that


uses TCP/IP.
DO

Data Only
DOrA

Data Only Revision A (Rev. A)


DoS

Data Over Signal


DPA

Default Packet Application

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
GL-3
Issue 5, May 2008
See notice on first page

Glossary

DRC

Data Rate Control


....................................................................................................................................................................................................................................

ECP

Executive Cellular Processor


EINE

Ethernet Interface Node


EMS

Element Management System


The EMS is used for configuration of managed objects and to enter commands from the
EMS Graphical User Interface (EMS-GUI) or Command Line Interface (CLI).
EMS GUI

Element Management System Graphical User Interface


EQU

Equivalent QoS Unit


ESN

Electronic Serial Number


EV-DO

EVolution Data Optimized


EV-DO Rev. A

EVolution Data Optimized Rev. A (2 Mbps Peak using 1.25 Mhz, packet voice)
EVM

1xEV-DO Modem
EVT/EVR

External Voice Terminal Assembly/Vacuum Regulator


....................................................................................................................................................................................................................................

FAF

Feature Activation File


FID

Feature Identifier
FL

Forward Link
FMS

Flexent Mobility Server


...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

GL-4

Glossary

FMS

File Transfer Protocol


FPGA

Functional Programmable Gate Array


FPP

Fast Protocol Processor


FSC

Flexible Scheduler Choice


....................................................................................................................................................................................................................................

GAUP

Generic Attribute Update Protocol


GMT

Greenwich Mean Time


GUI

Graphical User Interface


GZIP

GNU Zip
....................................................................................................................................................................................................................................

HAI

HDR Air Interfaces


HLR

Home Location Register


HOM

Handoff Matrix
HRPD

High Rate Packet Data


Commonly known as 1xEV-DO, HRPD stands for high rate packet data. It is a
high-speed CDMA-based wireless data technology developed by Qualcomm. It was also
known as HDR (high data rate) at one point. IS-856 is the official international standard
designation.
HRPD RAN

High Rate Packet Data Radio Access Network


HRPD-A

High Rate Packet Data Revision A (Rev. A)


...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
GL-5
Issue 5, May 2008
See notice on first page

Glossary

HSC

Hardware System Commands


HW ID

Hardware ID
....................................................................................................................................................................................................................................

IFHO

Inter-frequency Handoff
IMS

IP Multimedia Subsystem
IMS TAS

IP Multimedia Subsystem Telephony Application Server


IMSI

International Mobile Station Identity


IOS

Interoperability Specification
IP

Internet Protocol
IP/UDP/RTP

Internal Protocol/Universal Datagram Protocol/Rate Time Protocol


IPBH

Internet Protocol Backhaul


ISP

Internet Service Provider


ISUP

Integrated Services User Part


IUP

Inter-User Priority
....................................................................................................................................................................................................................................

LCP

Link Control Procotol


LIT

License Installation Tool

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

GL-6

Glossary

LL-MCS

Low Latency Media Control Signaling


LLM

License Limit Manager


....................................................................................................................................................................................................................................

MAC

Medium Access Control


MC

Multi Carrier
MCS

Media Control Signaling


MDCR

Measurement Data in Call Record


MEID

Mobile Equipment Identifier


MFPA

Multi-flow Packet Application


MIM

Management Information Model


MIN

Mobile Identification Number


MLG

Multi-Link Group
MLPPP

Mutli Link Point-to-Point Protocol


MM-AP

Mobility Manager Application Processor


MN-ID

Mobile Node Identifier


MR-APS

Multi-Router Automatic Protection Switching


MSC

Mobile Switching Center


...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
GL-7
Issue 5, May 2008
See notice on first page

Glossary

MSID

Mobile Station Identification


MTMR

Maximum Sector Throughput after meeting Minimum User Rate Target


....................................................................................................................................................................................................................................

NAK

Not Acknowledged
NAR

North American Region


NCRM

Node Card Resource Monitor


....................................................................................................................................................................................................................................

OA&M

Operations, Administration and Maintenance


Generic name given to functions such as diagnostics, service measurements, and status
reports.
OFDM

Orthogonal Frequency Division Multiplexing


OHM

Overhead Manager
OHM-SFM

Overhead Management-Selected Function Main


OHMAT

Overhead Manager Access Terminal


OLCS

Online Customer Support


OMC-RAN

Operations and Maintenance Center - Radio Access Network


OMC-RAN CORBA

Operations and Maintenance Center - Radio Access Network CORBA Agent


OMC-RAN CORBA Agent (ORCA is an agent process that provides a bridge between
legacy OA&M infrastructure and OMC-RAN. This is called mediation. It mediates
UX_messages into Management Information Model (MIM), receives events, alarms, and
status information from cells/base stations, switches, trunk groups/members,
reports/delivers alarm, status, and command responses to the OMC-RAN.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

GL-8

Glossary

OMP

Operations and Maintenance Platform


OMP-FX

Operations and Maintenance Platform for Flexent


This component provides a centralized point of access for wireless systems operation
and maintenance. The OMP-FX provides a dedicated processor from which system
operators can perform multiple operations, administration, and maintenance (OA&M)
tasks simultaneously.
OMP-FX v.2

Flexent Operations and Management Platform


ORCA-RNC

OMC-RAN CORBA Agent - Radio Network Controller


OTAF

Over-the-Air Activation Function


....................................................................................................................................................................................................................................

PAF

Physical Antenna Face


PCF

Packet Control Function


PCMD

Per Call Measurement Data


PCS

Personal Communication Services


PDSN

Packet Data Serving Node


PDSN-AAA

Packet Data Serving Node-Accounting, Authentication and Authorization


PF

Proportional Fair
PFMR

Proportional Fair after meeting Minimum User Rate Target


PHY

PHYsical

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
GL-9
Issue 5, May 2008
See notice on first page

Glossary

PPP

Point-to-Point Protocol
PSMM

Pilot Strength Measurement Message


PTT

Push-to-Talk
....................................................................................................................................................................................................................................

QFAF

Qualified Feature Activation File


QoS

Quality of Service
....................................................................................................................................................................................................................................

RAB

Reverse Activity Bit


RAN

Radio Access Network


RC/V

Recent Change and Verify


Used by CDMA users to access and update their database.
Rev. 0

Revision 0
Rev. A

(EVolution Data Optimized) Revision A (2 Mbps Peak using 1.25 Mhz, packet voice)
RF

Radio Frequency
RNC

Radio Network Controller


ROHC

Robust Header Compression


ROP

Read-Only-Printer
RoR

Reservation On Request
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

GL-10

Glossary

RRL

Restricted Root Login


RSSI

Received Signal Strength Indication


RTM

Rate Transition Matrix


RTP

Rate Transition Protocol


RTU

Right To Use
RUM

Route Update Message


....................................................................................................................................................................................................................................

SB-EVM

Single Board-1xEV-DO Modem


SC

Service Class
SES

Special Engineering Studies


SFM

Selector Function Manager


SHLR

Stand-alone Home Location Register


SIP

Session Initiation Protocol


SM

Service Measurements
SMS

Short Message Service


SN

Service Node
SNID

Service Node Identification


...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
GL-11
Issue 5, May 2008
See notice on first page

Glossary

SSIR

Session Status Information Record


SU

Software Update
....................................................................................................................................................................................................................................

TA

Test Application
TAS

FS5000 Telephony Application Server


TCSI

Traffic Channel Supervision Interval


TI

Technician Interface
TP

Traffic Processor
....................................................................................................................................................................................................................................

UATI

Unicast Access Terminal Identifier


UDP

Universal Database Protocol


UNC

Universal Network Cabinet


UNIX

Registered Trademark for the UNIX Operating System


An interactive time-sharing operating system.
URC

Universal Radio Controller


UTP

Universal Traffic Processor


....................................................................................................................................................................................................................................

VoIP

Voice Over IP

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

GL-12

Glossary

VT

Video Telephony
VT/VoIP

Video Telephony and Voice over IP


....................................................................................................................................................................................................................................

WSP

Wireless Service Provider

...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
GL-13
Issue 5, May 2008
See notice on first page

Index

Symbols

/etc/inetd.conf file, 5-14


/etc/services file, 5-13
.............................................................
Numerics

401-662-102, OMP-FX
Operation, Administration, &
Maintenance Guide, 5-68
.............................................................
A availability of the feature, 4-5

Availability of the feature, 6-3


availability of the feature, 8-6
Availability of the feature, 9-4,
10-5, 11-3, 12-5, 13-3
availability of the feature, 14-4,
15-4
Availability of the feature, 16-3
availability of the feature, 17-5
.............................................................
B B-Server, 5-11

command line
options, 5-70
Comments, to submit, 1-1, 2-2,
3-2, 4-3, 6-2, 7-4, 8-5, 9-2,
10-3, 11-2, 12-3, 13-2

Example 3, post-processing
tool, 5-15
.............................................................

comments, to submit, 14-2,


15-2

H hardware requirements, 1-4,

Comments, to submit, 16-2

Hardware requirements, 6-4

comments, to submit, 17-3

hardware requirements, 8-7

Configured OMP ports, 5-13

Hardware requirements, 9-5,


10-6, 11-4, 12-7, 13-4

2-4, 4-8, 5-13

.............................................................

hardware requirements, 14-5,


15-5

D Data delivery path diagram for

OMP, 5-11

Hardware requirements, 16-4

delimited ASCII version, 5-13


Documentation, to order, 1-1,
2-2, 3-2, 4-3, 6-2, 7-4, 8-5,
9-2, 10-3, 11-2, 12-3, 13-2
documentation, to order, 14-2,
15-2
Documentation, to order, 16-2
documentation, to order, 17-3
.............................................................

.............................................................
C Caveats and issues, 5-10

Example 2, post-processing
tool, 5-15

E EINE, 5-11

hardware requirements, 17-7


human readable format, 5-13
.............................................................
I

Issues and caveats, 5-10

.............................................................
M MDCR data record, 5-27, 5-27,

5-27, 5-27, 5-27, 5-27, 5-27,


5-27, 5-36
MDCR Version, 5-27

CFC Qualifier field, 5-21

Ethernet Interface Node


(EINE), 5-11

Move a 1xEV-DO cell


(inter-RNC), 3-44

circuit data and packet data


applications, 5-7

Example 1, post-processing
tool, 5-15

Move and Rename a cell


(inter-RNC), 3-108

....................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
IN-1
Issue 5, May 2008
See notice on first page

Index

.............................................................
P packet data applications, 5-7

pcmdviewer command, 5-70


Port 5050 is, 5-13
Port 5051 is, 5-13
.............................................................
R Raw data example, 5-47

raw format, 5-13


requirements of the feature
hardware, 1-4, 2-4, 4-8
Requirements of the feature
hardware, 6-4
requirements of the feature
hardware, 8-7
Requirements of the feature
hardware, 9-5, 10-6, 11-4,
12-7, 13-4
requirements of the feature
hardware, 14-5, 15-5
Requirements of the feature
hardware, 16-4
requirements of the feature
hardware, 17-7

Support, to obtain technical,


1-1, 2-2, 3-2, 4-3, 6-2, 7-4,
8-5, 9-2, 10-3, 11-2, 12-3,
13-2
support, to obtain technical,
14-2, 15-2
Support, to obtain technical,
16-2
support, to obtain technical,
17-3
.............................................................
T Technical support, to obtain,

1-1, 2-2, 3-2, 4-3, 6-2, 7-4,


8-5, 9-2, 10-3, 11-2, 12-3,
13-2
technical support, to obtain,
14-2, 15-2
Technical support, to obtain,
16-2
technical support, to obtain,
17-3
Training, to order or register
for, 1-1, 2-2, 3-2, 4-3, 6-2,
7-4, 8-5, 9-2, 10-3, 11-2,
12-3, 13-2
training, to order or register
for, 14-2, 15-2

Requirements of the feature

Training, to order or register


for, 16-2

software, 6-4, 9-5, 10-6,


11-4, 12-6, 13-4, 16-4

training, to order or register


for, 17-3

.............................................................

.............................................................

S Serial number, 5-27

V Verbose data example, 5-48

Software requirements, 6-4,


9-5, 10-6, 11-4, 12-6, 13-4,
16-4
stop the mdcrviewer tool, 5-68

verbose format, 5-13


Verify that service
measurements are reported on
new RNC, 3-132

Storage of one hour of data,


5-12

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008

IN-2

S-ar putea să vă placă și