Professional Documents
Culture Documents
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
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
.......................................................................................................................................................................................
Intended audience
...................................................................................................................................................................
xxiii
............................................
xxiii
..................................................................................................................................................................
xxiv
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
....................................................................................................................................................................
......................................................................................................................................................................................
Availability
..................................................................................................................................................................................
Prerequisites
................................................................................................................................................................................
1-1
1-3
1-4
Feature description
...................................................................................................................................................................
1-5
Feature interactions
..................................................................................................................................................................
1-7
..............................................................................................
...............
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
....................................................................................................................................................
1-24
...........................................................................................................................................................
1-25
..........................................................................
1-26
..............................................................................
1-28
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
..........................................................................................................................................................
2-10
................................................................................................................................
2-11
...................................................................................................................................
2-16
................................................................................................................................
2-1
.....................................................................................................
2-17
2-18
......................................................................................................................................................................................
Availability
..................................................................................................................................................................................
Prerequisites
................................................................................................................................................................................
3-4
3-5
3-7
................................................................................................................................................................
3-19
..................................................................................................................................................................
3-22
Feature interactions
Issues and caveats
......................................................................................
3-1
..................................................................................................................................................
3-23
...........................................................................................................................................................
3-24
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
iv
Contents
...........................................................................................................................................
3-26
.........................................................................................................................................................
3-27
...............................................................................................................................
......................................................................................
3-44
.........................................................
3-61
..........................................................................................................................................................................
3-79
3-29
..........................................................................................................................
........................................................................................................................
3-108
.......................................................................................................................................
3-126
.................................................................................
3-129
.......................................................................................................................
3-132
....................................................................................................................................
3-134
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
................................................................................................................................................................................
......................................................................
.................................................................
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
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
..................................................................................................................................................................
5-10
..................................................................................................................
5-11
........................................................................................................................................
5-15
...................
5-26
...................................................
5-47
.............................................................................................................
5-63
..............................................................................................................
5-64
.................................................................................................................
5-66
.........................................................................
5-68
..............................................................................................
5-70
................................................................................................................................................................
5-72
....................................................................................................................................................
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
.......................................................................................................................................................
...........................................................................................................................................................
6-9
6-10
...........................................................................................................
6-11
.......................................................................................................................................................
6-13
......................................................................................................................................................................................
Availability
..................................................................................................................................................................................
Prerequisites
................................................................................................................................................................................
.....................................................................................................
................................................................................................................................................................
7-5
7-6
7-7
7-14
7-15
..................................................................................................................................................
7-30
...........................................................................................................................................................
7-31
7-1
...................................................................................................................................
6-4
Feature description
6-3
Enhanced Data Only Revision A (DOrA) Application Quality of Service (QoS) Features
Overview
......................................................................................................................................................................................
Availability
..................................................................................................................................................................................
Prerequisites
................................................................................................................................................................................
................................................................................................................................................................
8-6
8-7
8-9
8-19
...................................................................................................................................
8-24
..................................................................................................................................................................
8-51
............................................................................................
8-1
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
vii
Issue 5, May 2008
See notice on first page
Contents
..................................................................................................................................................
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
....................................................................................................................................................
9-13
...........................................................................................................................................................
9-14
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
10-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
...................................................................................................................................................
10-24
....................................................................................................................................................................................
Availability
................................................................................................................................................................................
Prerequisites
..............................................................................................................................................................................
11-1
11-3
11-4
Feature description
.................................................................................................................................................................
11-5
Feature interactions
................................................................................................................................................................
11-9
.................................................................................................................................
11-10
....................................................................................................................................................
11-13
................................................................................................................................................................
11-15
..................................................................................................................................................
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
....................................................................................................................................................................................
Availability
................................................................................................................................................................................
Prerequisites
..............................................................................................................................................................................
...............
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
.................................................................................................................................
12-16
....................................................................................................................................................
12-17
..................................................................................................................................................
...................................
12-26
12-27
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
ix
Issue 5, May 2008
See notice on first page
Contents
12-28
................................................................................
12-29
....................................................................................................................................................................................
Availability
................................................................................................................................................................................
Prerequisites
..............................................................................................................................................................................
13-1
13-3
13-4
Feature description
.................................................................................................................................................................
13-5
Feature interactions
................................................................................................................................................................
13-7
...................................................................................................................................
....................................................................................................................................................
.................................................................
..................................................................................................................................................
13-8
13-11
13-14
....................................................................................................................................................................................
Availability
................................................................................................................................................................................
Prerequisites
..............................................................................................................................................................................
14-1
14-4
14-5
Feature description
.................................................................................................................................................................
14-6
Feature interactions
................................................................................................................................................................
14-9
.........................................................................................................................................................
........................................................................................................................
14-17
.................................................................................................................................
14-23
.................................................................................................
14-26
..................................................................................................................................................
14-29
.........................................................................................................................................................
14-30
14-15
..........................................................................................................
14-10
.........................................................................................................................................
...........................................................................
14-31
14-32
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
Contents
.................................................................................................
.......................................................................
14-36
............................................................................................................................................................
14-37
14-34
Jurisdictional Priority for Public Safety Users of Best Effort Data Applications
(JPPSUBEDA)
Overview
....................................................................................................................................................................................
Availability
................................................................................................................................................................................
Prerequisites
..............................................................................................................................................................................
Feature description
.................................................................................................................................................................
Feature interactions
.............................................................................................................................................................
.........................................................................................................................................................
........................................................................................................................
..........................................................................................................
15-5
15-6
15-10
15-11
15-16
15-18
15-27
..................................................................................................................................................
15-34
.........................................................................................................................................................
15-35
.........................................................................................................................................
15-36
.........................................................................................................................................................
15-37
15-4
.................................................................................................
15-1
..............................................................................
15-39
.......................................................................................................................................
15-45
.....................................................................................................................................
15-47
.................................................................................................................
15-49
.............................................................................................................
15-56
............................................................................................................
15-59
...................................................................................................
15-62
............................................................................................................................................................
15-64
....................................................................................................................................................
15-66
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
xi
Issue 5, May 2008
See notice on first page
Contents
16
....................................................................................................................................................................................
Availability
................................................................................................................................................................................
Prerequisites
..............................................................................................................................................................................
16-3
16-4
Feature description
.................................................................................................................................................................
16-5
Feature interactions
................................................................................................................................................................
16-6
Configuration management
................................................................................................................................................
16-7
...................................................................................................................................
16-8
...........................................................................................................................................................
16-9
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
................................................................................................................................................
xxiv
1-2
1-3
1-4
1-5
............................................................................................................................
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
........................................................................................................................
2-8
CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Handoff Matrix (HOM) Tool and
Related Features
4-1
.........................................................................................................
4-20
4-2
.........................................................................................................
4-25
4-3
...............................................................................................
4-26
4-4
...............................................................................................
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
5-3
5-4
CFC values
5-5
5-6
5-7
5-8
5-9
5-10
5-11
5-12
5-13
.......................................................................................
5-31
5-14
........................................................................................
5-36
5-15
5-16
5-17
5-18
5-19
5-20
Flow Final Classes (FFC) and FFC Qualifiers for Flow Reservation
5-21
.................................................................................................................................................
.................................................................................................................................
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
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
8-7
.......
8-30
...............................................
8-44
...................................................................................................
8-45
8-8
...................................................................................................
8-45
8-9
...................................................................................................
8-46
8-10
8-11
8-12
8-13
8-14
8-15
.......................................................................................
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
9-2
9-3
9-4
.............................................................................................................................................
....................................................................................................................
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
.........................................................................
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
.....................................................
10-20
10-3
.............................................................................
10-21
11-10
...........................................................................................................
11-10
...............................................................................................................................
11-20
11-1
11-2
11-3
11-4
11-5
11-6
......................................................................................
11-24
...............................................................................................................................
11-27
......................................................................................
11-32
13-2
13-3
.....................................................................................
......................................................
................................................
13-8
13-8
13-9
................................................................................................
14-15
14-2
...............................................................................................
14-15
14-3
...................................................................................................
14-17
14-4
...................................................................................................
14-18
14-5
14-6
14-7
14-8
14-9
.......................................................................................
14-20
.............................................................................................................................
14-23
................................................................................
14-26
....................
14-27
...............................
14-28
Jurisdictional Priority for Public Safety Users of Best Effort Data Applications
(JPPSUBEDA)
15-1
................................................................................................
15-16
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
xviii
List of tables
15-2
...............................................................................................
15-16
15-3
................................................................................................
15-17
15-4
...................................................................................................
15-18
15-5
..............................................................................................................
15-19
15-6
15-7
15-8
15-9
..................................................................
15-20
.............................................
15-21
......................................................................................................
15-22
.........................................................
..............................................
15-25
..........................................................................................
15-30
15-23
.....................................................................................
15-31
.....................................................................................
15-31
...........................................................................................
15-32
.............................................................................
15-33
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
xix
Issue 5, May 2008
See notice on first page
List of figures
1-2
1-3
1-4
14
.................................................................................................................................................
1-9
1-12
......................................................................................
1-16
.................................................................................................................................................
1-19
CDMA 3G-1x EVolution Data Optimized (1xEV-DO) Radio Access Network Authentication
(RAN)
2-1
........................................................................................
.................................................................................................
2-6
Per Call Measurement Data (PCMD) for CDMA 3G-1x EVolution Data Optimized
(1xEV-DO)
5-12
5-1
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
9-2
........................................................................
.....................................................................................................................................................
9-7
9-16
Example Application of the Inter-User Priority for Best Effort Data Applications feature
14-2
....
...........................................................
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
........................................................
14-13
14-4
.......................................................................................
14-18
14-5
..................................................................................................
14-20
14-6
14-7
...........................................................................
14-22
.................................................................................................
14-25
Jurisdictional Priority for Public Safety Users of Best Effort Data Applications
(JPPSUBEDA)
15-1
15-2
15-3
15-4
15-5
15-6
15-7
15-8
15-9
..................................................................
15-14
.......................................................................................
15-19
..................................................................................................
15-20
...........................................................................
15-21
......................................................
15-22
.............................................................................................
15-23
............................................
15-24
.......................................................
15-26
..............................................................
15-28
..............................................................................................................
15-29
17
15-12
..................................................
.....................................................
15-9
Backhaul Enhancement in Support of Small Packets on the Reverse and Forward Links
in 1xEV-DO
..................................................................................................................................
17-16
.........................................................................................................................................
17-19
17-1
17-2
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
xxii
Purpose
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
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
xxiii
Issue 5, May 2008
See notice on first page
,
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
Feature
Identification (FID)
Number
Base Release/SU
Release
Chapter Number
Issue
Addition of
OMC-RAN
Procedures
Multiple Chapters
throughout the
document
FID 8219.9
Chapter 4
FID 9253.3
Chapter 12
FID 10737.9
Chapter 3
FID 12102.5
Chapter 17
(new)(was
document
401-614-416)
FID 12102.14
Chapter 17 (new)
(was document
401-614-416)
FID 12885.1
Chapter 3, see
Feature Interactions
FID 12370.1
Chapter 5
FID 12766.2
Chapter 5
FID 12780.3
Chapter 16 (new)
FID 13181.0*
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
Chapter distribution
This document contains the following CDMA 3G-1x EVolution Data Optimized
(1xEV-DO) procedural chapters which cover the CDMA2000 1xEV-DO networks.
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
xxv
Issue 5, May 2008
See notice on first page
,
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
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
,
Starting out
Desktop
Base Transceiver
Systems (BTSs) screen
Base Transceiver
Systems (BTSs) screen
Alarm Manager
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
,
xxviii
Starting out
Desktop
Monitoring all
EV-DO RNCs in a
Service Node
Monitoring an
individual EV-DO
RNC
Working with
configuration data for
a BTS
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
xxix
Issue 5, May 2008
See notice on first page
,
Starting out
Desktop
Working with
configuration data for
a Service Node
Working with
configuration data
single frame
Configuration Data
tables
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
Conventions used
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
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
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
,
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:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
,
xxxii
History of revisions
The following list summarizes the major changes or additions in this document for
1xEV-DO Release 29.1:
Issue 4
The following list summarizes the major changes or additions in this document for
1xEV-DO Release 29.0:
Issue 3
The following list summarizes the major changes or additions in this document for
1xEV-DO Release 28.1:
Issue 2.2
The following list summarizes the major changes or additions in this document for
1xEV-DO Release 28.0:
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
,
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
Issue 1
The following list summarizes the major changes or additions in this document for
1xEV-DO Release 27.0:
How to comment
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
,
xxxiv
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 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
Service measurements
None
None
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
1-1
Issue 5, May 2008
See notice on first page
Overview
1-3
Prerequisites
1-4
Feature description
1-5
Feature interactions
1-7
1-8
1-16
1-23
1-24
1-25
1-26
1-28
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
1-2
Availability
...................................................................................................................................................................................................................................
Release availability
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
1-3
Issue 5, May 2008
See notice on first page
Prerequisites
...................................................................................................................................................................................................................................
Introduction
CDMA cellular
CDMA PCS
Software 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
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:
The default choice and the algorithm in use before this feature was available.
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.
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.
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.
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
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
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
Impacts
on the Element Management System (EMS)
...................................................................................................................................................................................................................................
Configuration Management pages
The Flexible Scheduler feature affects these Configuration Management pages in the
Element Management System:
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
Parameter name
Flexible Scheduler
Choice
Description
Allowed values
PF (default)
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
1-9
Issue 5, May 2008
See notice on first page
Table 1-1
Parameter name
Minimum Throughput
Target (Rmin)
Restrict Throughput
After Reaching Rmax
(continued)
Description
Allowed values
0 to 64 kbps in steps of
4k
Unspecified
Default = 0
Non-strict (default)
Strict
Out-of-Range
Unspecified
h(x)=x(proportional_
fair)
(default)
h(x)=2*x
h(x)=4*x
Out-of-Range
Unspecified
PFMR (default)
MTMR
Out-of-Range
1-10
Table 1-1
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
Off (default)
1.5 to 2.5 in steps of
0.1
Out-of-Range
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
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
1-12
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
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.
Allowed values
Unspecified (default)
Proportional Fair
Min/Max Rate Control
G-Fair
Random Activity Factor
Unspecified (default)
PFMR
MTMR
Out-of-Range
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
1-13
Issue 5, May 2008
See notice on first page
Table 1-2
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
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
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:
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
1-15
Issue 5, May 2008
See notice on first page
FxApx
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
1-16
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
Parameter name
Flexible Scheduler
Choice
Minimum Throughput
Target (Rmin)
Restrict Throughput
After Reaching Rmax
Description
Allowed values
PF (default)
0 to 64 kbps in steps of
4k
Unspecified
Default = 0
Non-strict (default)
Strict
Out-of-Range
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
1-17
Issue 5, May 2008
See notice on first page
Table 1-3
Impacts on the Operations and Maintenance Center Radio Access Network (OMC-RAN)
(continued)
Parameter name
Description
Allowed values
Unspecified
h(x)=x(proportional_
fair)
(default)
h(x)=2*x
h(x)=4*x
Out-of-Range
Unspecified
PFMR (default)
MTMR
Out-of-Range
2457.6 (default)
9.6 to 2457.6 kbps in
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
Impacts on the Operations and Maintenance Center Radio Access Network (OMC-RAN)
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
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
1-19
Issue 5, May 2008
See notice on first page
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
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.
Allowed values
Unspecified (default)
Proportional Fair
Min/Max Rate Control
G-Fair
Random Activity Factor
Unspecified (default)
PFMR
MTMR
Out-of-Range
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
1-20
Table 1-4
Impacts on the Operations and Maintenance Center Radio Access Network (OMC-RAN)
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
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
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:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
1-22
Impacts
on service measurements
...................................................................................................................................................................................................................................
Introduction
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
Count abbreviation
Brief description
EVM_AVG_PCNT_SLOTS_BELOW_RMIN
EVM_AVG_PCNT_SLOTS_ABOVE_RMAX
EVM_AVG_ELIG_USER
EVM_TOTAL_BUSY_PCNT_SLOT
EVM_TOTAL_PCNT_SLOTS_RMIN_HOGGING_
EFFECTIVE
References
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
1-23
Issue 5, May 2008
See notice on first page
Implementing
the feature
...................................................................................................................................................................................................................................
Overview
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
1-24
Activating
the feature
...................................................................................................................................................................................................................................
Purpose
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
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
Access the Operations and Maintenance Platform (OMP) Web page according to your
local practices.
...................................................................................................................................................................................................
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
...................................................................................................................................................................................................
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
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
If you have not already accessed the EMS Configuration Data pages in the following
procedure, do so as follows:
...................................................................................................................................................................................................
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
...................................................................................................................................................................................................
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
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)
Operations and
Maintenance Center Radio Access Network
(OMC-RAN)
Service measurements
Automatic Message
Accounting (AMA)
subsystem
....................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
2-1
Issue 5, May 2008
See notice on first page
User interface
Feature impact
Technician Interface
(TI) (input/output
messages)
None
Overview
2-3
Prerequisites
2-4
Feature description
2-5
Feature interactions
2-7
2-8
2-9
2-10
2-11
2-16
2-17
2-18
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
2-2
Availability
...................................................................................................................................................................................................................................
Release availability
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
2-3
Issue 5, May 2008
See notice on first page
Prerequisites
...................................................................................................................................................................................................................................
Introduction
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
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
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
2-4
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
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.
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
Feature description
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
Feature
interactions
...................................................................................................................................................................................................................................
Introduction
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
2-7
Issue 5, May 2008
See notice on first page
Impacts
on service measurements
...................................................................................................................................................................................................................................
Introduction
The 1xEV-DO RAN Authentication feature affects the following categories of services
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
Count abbreviation
Count name
RAN_AUTH_TOTAL_ATTMPT
RAN_AUTH_SUCCESSFUL_ATTMPT
RAN_AUTH_FAILURE_AAA_REJECT_RSP
RAN_AUTH_FAILURES_STREAM_SELECTION_
FAILED
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_AUTH_FAILURES_NO_AT_CHALLENGE_
RSP
AAA_SERVER_FAILURES
References
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
2-8
Implementing
the feature
...................................................................................................................................................................................................................................
Overview
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)
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:
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
Activating
the Feature
...................................................................................................................................................................................................................................
Purpose
Contact your Customer Technical Advocate (CTA) about the generation of an OMP
Feature Activation File (FAF).
...................................................................................................................................................................................................
Ask your account executive to activate the following entry in your FAF:
A12 RAN Authentication
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
2-10
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
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.
...................................................................................................................................................................................................
configured.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
2-11
Issue 5, May 2008
See notice on first page
...................................................................................................................................................................................................
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
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
2-12
...................................................................................................................................................................................................
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.
...................................................................................................................................................................................................
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
...................................................................................................................................................................................................
10
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
2-13
Issue 5, May 2008
See notice on first page
Result: The RAN Authentication Instance Page for that service node appears.
...................................................................................................................................................................................................
11
...................................................................................................................................................................................................
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
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
Provisioning
the Access Terminal
...................................................................................................................................................................................................................................
Purpose
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.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
2-16
Provisioning
the RAN AAA server
...................................................................................................................................................................................................................................
Purpose
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
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
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
Overview
...................................................................................................................................................................................................................................
Purpose
Overview
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
Element Management
System (EMS) and
Operations and
Maintenance Center Radio Access Network
(OMC-RAN)
Service measurements
None
Automatic Message
Accounting (AMA)
subsystem
None
None
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
3-2
Overview
Contents
Availability
3-4
Prerequisites
3-5
3-7
Feature interactions
3-19
3-22
3-23
3-24
3-26
3-27
3-29
3-44
3-61
Rename a cell
3-79
3-93
3-108
3-126
3-129
3-132
3-134
3-136
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-3
Issue 5, May 2008
See notice on first page
Availability
...................................................................................................................................................................................................................................
Release availability
Feature
Available in
Market availability
Feature
Available in
all markets
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
3-4
Prerequisites
...................................................................................................................................................................................................................................
Introduction
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:
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
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
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
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.
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:
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-7
Issue 5, May 2008
See notice on first page
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
evdoswing
evdomkdir
evdonetwork
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
Logfiles
evdodump.log
evdoswing.log
evdonetwork.log
runBPmmddyyyy.log
Preliminary setup
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-9
Issue 5, May 2008
See notice on first page
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
cell_file
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
3-10
-c
-h
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;
Key Fields
Cell
Sector
NeighborSector
IFHOTarget
SectorCarrier
Key Fields
SectorCarrier
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-11
Issue 5, May 2008
See notice on first page
Key Fields
IFHOTarget
NeighborSector
CDM
Sector
CellCabinet
Cell
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.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
3-12
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 .
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
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:
Where:
evdo_dumpdir
cell_file
sn_file
-v
-h
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
evdonetwork
The evdonetwork tool is run once on the Source OMP. The evdonetwork tool creates
scripts that
Scriptnames
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.
and NthIp
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-15
Issue 5, May 2008
See notice on first page
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
network_file
sn_file
-h
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
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
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.
Non-key attributes of the BTS and its contained managed objects may be modified.
These attributes are:
When moving cells, the Cell Swing tools user should be familiar with:
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-17
Issue 5, May 2008
See notice on first page
Bulk Provisioning
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
3-18
Feature
interactions
...................................................................................................................................................................................................................................
Cell Swing Capability for 1xEV-DO feature
The Cell Swing Capability for 1xEV-DO feature interacts with the following features:
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
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
Feature interactions
When the 1xEV-DO Gold BCMCS feature is aligned with a cell swing:
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-21
Issue 5, May 2008
See notice on first page
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
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
3-22
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
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:
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
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
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-25
Issue 5, May 2008
See notice on first page
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.
...................................................................................................................................................................................................
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
Determining
the NthIP
...................................................................................................................................................................................................................................
Purpose
This procedure calculates the NthIP variable used by the evdonetwork command.
When to perform
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:
...................................................................................................................................................................................................
...................................................................................................................................................................................................
255.255.255.224
#Cell 155
10.200.35.200
255.255.255.252
10.200.35.204
255.255.255.252
10.200.35.208
255.255.255.252
10.200.35.212
255.255.255.252
...................................................................................................................................................................................................
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
Example: 10.200.35.200
...................................................................................................................................................................................................
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
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
3-28
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
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
To use the Bulk Provisioning tool, you must have the following:
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-29
Issue 5, May 2008
See notice on first page
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:
...................................................................................................................................................................................................
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
mkdir p /roles/rsysadm/dbbackup
cd /roles/rsysadm/dbbackup
$HDRROOT/release/util/dbunload
...................................................................................................................................................................................................
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:
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.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-31
Issue 5, May 2008
See notice on first page
...................................................................................................................................................................................................
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
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.
...................................................................................................................................................................................................
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
10
cell_file
-c
-h
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
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
cell_file
sn_file
-v
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
files.
...................................................................................................................................................................................................
18
Where:
XXX
YY
created.
...................................................................................................................................................................................................
19
20
1. cd /var/dhcp
2. get SUNWfiles1_dhcptab
Result: Copy of the SUNWfiles1_dhcptab file is obtained.
...................................................................................................................................................................................................
21
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
Enter: cd $bpPath
...................................................................................................................................................................................................
24
At the prompt,
Enter: evdonetwork -n evdo_dumpdir -i network_file -s sn_file
Where:
evdo_dumpdir
network_file
sn_file
Result: The evdonetwork script files for deleting, creating, and adding the network
25
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
the cluster.
...................................................................................................................................................................................................
26
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
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-37
Issue 5, May 2008
See notice on first page
Result: The scripts used to update the Neighbor sectors on Neighboring RNCs/SNs
are transferred.
...................................................................................................................................................................................................
28
is in the format
<element><SNID><FMSID>Add<BPfile#>
<element><SNID><FMSID>Delete<BPfile#>
<element><SNID><FMSID>Replace<BPfile#>
NeighborSector<SNID><FMSID>Replace<BPfile#>
...................................................................................................................................................................................................
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
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
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
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
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#>
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
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
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-41
Issue 5, May 2008
See notice on first page
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
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
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
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
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
To use the Bulk Provisioning tool, you must have the following:
Important
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
3-44
For information on setting up a login on the OMP, 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:
...................................................................................................................................................................................................
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
mkdir p /roles/rsysadm/dbbackup
cd /roles/rsysadm/dbbackup
$HDRROOT/release/util/dbunload
...................................................................................................................................................................................................
Back up the network files that may/will be modified on the lead FMS-APs.
In RRL off mode:
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.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
3-46
...................................................................................................................................................................................................
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.
...................................................................................................................................................................................................
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
10
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-47
Issue 5, May 2008
See notice on first page
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
1. exec /usr/bin/ksh
2. . BP_user_setup
3. Enter: Y
Result: The BP tools environment is enabled.
...................................................................................................................................................................................................
13
cell_file
-c
-h
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
3-48
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
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
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
cell_file
sn_file
-v
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
Where:
evdo_dumpdir
network_file
sn_file
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
3-50
files.
...................................................................................................................................................................................................
23
created.
...................................................................................................................................................................................................
24
25
1. cd /var/dhcp
2. get SUNWfiles1_dhcptab
Result: Copy of the SUNWfiles1_dhcptab file is obtained.
...................................................................................................................................................................................................
26
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
...................................................................................................................................................................................................
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
network_file
sn_file
Result: The evdonetwork script files for deleting, creating, and adding the network
31
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
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
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
34
Change permissions on the script files (transferred in Step 32 for the Target RNC).
Example:
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
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
3-54
Result: The scripts used to update the Neighbor sectors on Neighboring RNCs/SNs
are transferred.
...................................................................................................................................................................................................
36
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#>
...................................................................................................................................................................................................
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
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
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
3-56
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
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
3-58
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
Result: The Neighbor sectors on the Neighboring SNs/OMPs are updated for the
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
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
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
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
To use the Bulk Provisioning tool, you must have the following:
Important
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-61
Issue 5, May 2008
See notice on first page
For information on setting up a login on the OMP, 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:
...................................................................................................................................................................................................
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
mkdir p /roles/rsysadm/dbbackup
cd /roles/rsysadm/dbbackup
$HDRROOT/release/util/dbunload
...................................................................................................................................................................................................
Back up the network files that may/will be modified on the lead FMS-APs.
In RRL off mode:
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.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-63
Issue 5, May 2008
See notice on first page
...................................................................................................................................................................................................
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.
...................................................................................................................................................................................................
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
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
3-64
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
1. exec /usr/bin/ksh
2. . BP_user_setup
3. Enter: Y
Result: The BP tools environment is enabled.
...................................................................................................................................................................................................
13
cell_file
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-65
Issue 5, May 2008
See notice on first page
-c
-h
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
...................................................................................................................................................................................................
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
Where:
evdo_dumpdir
cell_file
sn_file
-v
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
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-67
Issue 5, May 2008
See notice on first page
Where:
evdo_dumpdir
network_file
sn_file
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
created.
...................................................................................................................................................................................................
23
24
1. cd /var/dhcp
2. get SUNWfiles1_dhcptab
Result: Copy of the SUNWfiles1_dhcptab file is obtained.
...................................................................................................................................................................................................
25
1. cd /etc
2. get netmasks
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
3-68
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
29
network_file
sn_file
Result: The evdonetwork script files for deleting, creating, and adding the network
30
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
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
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
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
33
34
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
Result: The scripts used to update the Neighbor sectors on Neighboring RNCs/SNs
are transferred.
...................................................................................................................................................................................................
36
Where:
scriptname
is in the format
<element><SNID><FMSID>Delete<BPfile#>
...................................................................................................................................................................................................
37
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
3-72
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
NeighborSectorXXXYYReplace<BPfile#>
Where:
NeighborSectorXXXYYReplace<BPfile#> contains:
XXX
YY
...................................................................................................................................................................................................
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
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
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
3-74
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
Where:
XXX
YY
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
3-76
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
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
...................................................................................................................................................................................................
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
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
To use the 1xEV-DO cell swing tools, you must have the following:
root
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.
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
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:
...................................................................................................................................................................................................
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
...................................................................................................................................................................................................
Backup the network files that may/will be modified on the lead FMS-APs.
In RRL off mode:
3-80
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:
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
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
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.
...................................................................................................................................................................................................
10
cell_file
-h
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
Rename a cell
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
cell_file
sn_file
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-83
Issue 5, May 2008
See notice on first page
-v
Rename a cell
...................................................................................................................................................................................................
17
Where:
evdo_dumpdir
network_file
sn_file
files.
...................................................................................................................................................................................................
18
Example:
cd $bpPath/sXXX/fYY
Where:
XXX
YY
created.
...................................................................................................................................................................................................
19
20
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
3-84
Rename a cell
2. get SUNWfiles1_dhcptab
Result: Copy of the SUNWfiles1_dhcptab file is obtained.
...................................................................................................................................................................................................
21
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
network_file
sn_file
Result: The dhcp, netmask, and t1 deletion, creation, and addition scripts are
created.
...................................................................................................................................................................................................
26
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-85
Issue 5, May 2008
See notice on first page
Rename a cell
Where:
XXX
YY
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
3-86
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
Result: The scripts used to update the Neighbor sectors on Neighboring RNCs/SNs
are transferred.
...................................................................................................................................................................................................
29
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
Rename a cell
32
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
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
Rename a cell
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
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
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
3-90
Rename a cell
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
Result: The Neighbor sectors on the Neighboring SNs/OMPs are updated for the
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
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
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
To use the 1xEV-DO cell swing tools, you must have the following:
root
To use the Bulk Provisioning tool, you must have the following:
Important
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-93
Issue 5, May 2008
See notice on first page
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.
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:
...................................................................................................................................................................................................
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
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
...................................................................................................................................................................................................
Back up the network files that may/will be modified on the lead FMS-APs.
In RRL off mode:
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-95
Issue 5, May 2008
See notice on first page
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.
...................................................................................................................................................................................................
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
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.
...................................................................................................................................................................................................
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
3. Enter: Y
Result: The BP tools environment is enabled.
...................................................................................................................................................................................................
10
evdodump -d
evdo_dumpdir
-i cell_file
Where:
evdo_dumpdir
cell_file
-c
-h
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
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
Where:
evdo_dumpdir
cell_file
sn_file
-v
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
3-98
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
Where:
evdo_dumpdir
network_file
sn_file
files.
...................................................................................................................................................................................................
18
Where:
XXX
YY
created.
...................................................................................................................................................................................................
19
20
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
21
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
network_file
sn_file
Result: The evdonetwork script files for deleting, creating, and adding the network
26
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
3-100
YY
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
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
Result: The scripts used to update the Neighbor sectors on Neighboring RNCs/SNs
are transferred.
...................................................................................................................................................................................................
29
is in the format
<element><SNID><FMSID>Delete<BPfile#>
<element><SNID><FMSID>Add<BPfile#>
<element><SNID><FMSID>Replace<BPfile#>
NeighborSector<SNID><FMSID>Replace<BPfile#>
...................................................................................................................................................................................................
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
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
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
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
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
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
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
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
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
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
To use the 1xEV-DO cell swing tools, you must have the following:
root
To use the Bulk Provisioning tool, you must have the following:
Important
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
3-108
For information on setting up a login on the OMP, see Alcatel-Lucent 9271 EV-DO
Radio Network Controller, 401-614-102.
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:
...................................................................................................................................................................................................
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
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
...................................................................................................................................................................................................
Back up the network files that may/will be modified on the lead FMS-APs.
In RRL off mode:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
3-110
...................................................................................................................................................................................................
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
10
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-111
Issue 5, May 2008
See notice on first page
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
1. exec /usr/bin/ksh
2. . BP_user_setup
3. Enter: Y
Result: The BP tools environment is enabled.
...................................................................................................................................................................................................
13
evdodump -d
evdo_dumpdir -i cell_file
Where:
evdo_dumpdir
cell_file
-c
-h
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
3-112
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
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
cell_file
sn_file
-v
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
Where:
evdo_dumpdir
network_file
sn_file
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
3-114
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
created.
...................................................................................................................................................................................................
23
24
1. cd /var/dhcp
2. get SUNWfiles1_dhcptab
Result: Copy of the Source SUNWfiles1_dhcptab file is obtained.
...................................................................................................................................................................................................
25
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
...................................................................................................................................................................................................
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
29
network_file
sn_file
Result: The evdonetwork script files for deleting, creating, and adding the network
30
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
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
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
In RRL on mode:
the cluster.
...................................................................................................................................................................................................
32
Change permissions on the deletion script files (transferred in Step 30 for the Source
RNC).
In RRL off mode:
33
Change permissions on the addition script files (transferred in Step 31 for the Target
RNC).
In RRL off mode:
3-118
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
Result: The scripts used to update the Neighbor sectors on Neighboring RNCs/SNs
are transferred.
...................................................................................................................................................................................................
35
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
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-119
Issue 5, May 2008
See notice on first page
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
...................................................................................................................................................................................................
37
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
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
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
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
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
/etc/init.d/dhcp stop
/etc/init.d/dhcp start
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:
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
...................................................................................................................................................................................................
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 backout procedure
...................................................................................................................................................................................................................................
Purpose
This procedure moves the stand alone modular cell back to the original FMS-AP pair.
Required skills and personnel
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:
...................................................................................................................................................................................................
Repeat Step 2 for the Target RNC if an inter-RNC swing or an inter-RNC move and
rename is being backed out.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
3-126
Where: A_B_C_D are determined by searching the Source RNCs netmasks files
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
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:
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
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
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
Verify
OA&M on moved and/or renamed converged cell
...................................................................................................................................................................................................................................
Purpose
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:
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
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:
...................................................................................................................................................................................................
Enter:OP:CELL BTS_ID
Where:
BTS_ID
Where:
BTS_ID
CDM ID
Where:
BTS_ID
Result: The status of the amplifiers associated with the moved cell is displayed.
...................................................................................................................................................................................................
Where:
BTS_ID
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
3-130
Result: The status of the cell generic/generics installed on the moved cell is/are
displayed.
...................................................................................................................................................................................................
Where:
BTS_ID
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
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:
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
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
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
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 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
...................................................................................................................................................................................................
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/
...................................................................................................................................................................................................
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
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
3-135
Issue 5, May 2008
See notice on first page
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
Overview
...................................................................................................................................................................................................................................
Purpose
Feature summary
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
Overview
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
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
Overview
Feature
User interface
Feature impact
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
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
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
4-3
Issue 5, May 2008
See notice on first page
Overview
4-5
Prerequisites
4-6
4-9
4-12
4-14
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
4-33
4-34
4-37
4-38
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
4-4
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
Market availability
The 1xEV-DO HOM Tool feature and related features are available in the following
markets:
Feature
Available in
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
4-5
Issue 5, May 2008
See notice on first page
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)
1xEV-DO
The BC0/BC1 Dual Band 1xEV-DO feature is supported in the following air-interface
technologies:
1xEV-DO
1xEV-DO
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
Prerequisites
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 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
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
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:
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
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 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
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
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
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:
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:
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
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
4-12
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
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
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
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
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.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
4-16
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
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
evstarthom
command
...................................................................................................................................................................................................................................
Abstract
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
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
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
Invalid arguments
20
Other errors
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
4-20
evstarthom command
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
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>
Display the data only separated by colons. This option cannot be used with the -s
option unless the -w option is also used.
-h
-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
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
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
evdisphom command
Study stopped or data is collected from at least one RNC but not all
RNCs
Invalid arguments
10
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
4-25
Issue 5, May 2008
See notice on first page
Table 4-2
Error Code
evdisphom command
(continued)
Message
20
Other errors
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
Variable
<REL>
Description
Example
26.0
<START_DATE>
20050104142045
<STOP_DATE>
20050104143045
<SN>
<RNC_LIST>
12
1|3|4
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
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
Variable
<FROM_CELL>
<FROM_SECTOR>
<TO_SECTOR_DECL>
<TO_CELL_
PNOFFSET>
<TO_SECTOR_CHAN>
<TO_ACTIVE_IP>
Description
Example
or
n
112
135.5.143.6
<SOFT_ADD_
COMPLETE>
<SOFT_ADD_
ATTEMPT>
12
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
4-27
Issue 5, May 2008
See notice on first page
Table 4-4
Variable
evdisphom command
(continued)
Description
Example
<SOFT_DROP_
COMPLETE>
12
<SOFT_DROP_
ATTEMPT>
13
<HARD_ADD_
COMPLETE>
14
<HARD_ADD_
ATTEMPT>
15
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
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
DECL: DECL:
TO
CELL
TO
SECT
UNDEC: UNDEC:
PN
TO
ADD
ADD
DROP
DROP
HARD
HARD
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
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:
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
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
4-30
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
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:
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
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
Service measurement
subcategory
Count abbreviation
Count name
SECT-CARR-HDRC
SECT-CARR-HDRC
SECT-CARR-HDRC
SECT-CARR-HDRC
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
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
DECL: DECL:
TO
CELL
TO
SECT
UNDEC: UNDEC:
PN
TO
ADD
ADD
DROP
DROP
HARD
HARD
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
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:
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
DECL: DECL:
TO
CELL
TO
PN
CHAN#
SECT
UNDEC: UNDEC:
TO
ADD
ADD
DROP
DROP
HARD
HARD
OFFSET
132
FROM FROM
TO
133
DECL: DECL:
TO
CELL
TO
SECT
UNDEC: UNDEC:
PN
10.2.5.1
TO
ADD
ADD
DROP
DROP
HARD
HARD
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
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
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
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
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
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
....................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-1
Issue 5, May 2008
See notice on first page
Overview
A unique Feature Identifier (FID) is assigned to each feature. This document supports
the following features:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
5-2
Overview
The PCMD for 1xEV-DO affects the user interfaces that are listed in the following
table.
User interface
Feature impact
Service measurements
None
Contents
Availability
5-4
Prerequisites
5-5
PCMD terminology
5-6
Feature description
5-7
5-10
5-11
5-15
5-26
5-47
5-63
5-64
5-66
5-68
5-70
Feature interactions
5-72
5-73
5-74
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-3
Issue 5, May 2008
See notice on first page
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
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
5-4
Prerequisites
...................................................................................................................................................................................................................................
Introduction
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:
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:
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-5
Issue 5, May 2008
See notice on first page
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
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
Table 5-1
EV-DO terminology
Feature description
(continued)
3G1X
EV-DO
termination
AN-Initiated Connection
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.
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
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
5-8
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
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
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
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
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
/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
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
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
5-14
Post-processing
tool guidelines
...................................................................................................................................................................................................................................
Introduction
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
Page
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
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
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
Table 5-2
(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
Table 5-2
(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
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
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
dropped connection
11
20
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
5-20
Table 5-4
CFC values
(continued)
Value
Meaning
Additional information
22
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
Value
Qualifier
Additional Information
001
002
This is an indication of a
user-initiated connection end or
Hybrid AT hand-down to 1X
005
021
022
023
024
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-21
Issue 5, May 2008
See notice on first page
Table 5-6
Value
Qualifier
Additional Information
100
Dropped connection
106
Lost Connection
120
RNC Disconnect
122
AT Tune-Away
Timeout
Table 5-7
Value
Qualifier
Additional Information
Possible
secondary
qualifier
300
AT/AN-Initiated
Connection
inhibited
temporary account
suspension
1=RAN-authentication failure
304
Configuration
Negotiation Failure
305
Communication
failed with AT
310
AT-Initiated Session
Close
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
5-22
Table 5-8
Value
Qualifier
Additional Information
Possible
secondary
qualifiers
901
Traffic channel
confirmation failure
0 = No indication that AT
confirmation received
902
Resource Mismatch
903
Traffic channel
unavailable
904
Internal cell
processing error
Undetermined hardware or
software error
Table 5-9
Value
Qualifier
Additional Information
2001
AP-related software
failure
2002
Configuration
Failure
2003
Internal RNC
communication
failure
2004
No TP available
2007
TP protocol failure
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-23
Issue 5, May 2008
See notice on first page
Table 5-10
Value
Qualifier
Additional Information
2202
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
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
5-24
Table 5-10
Value
Qualifier
Additional Information
2206
PDSN-initiated
closure
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
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
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
Table 5-20, Flow Final Classes (FFC) and FFC Qualifiers for Flow Reservation
(p. 5-46)
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
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
2.
Length
3.
4.
Field description
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-27
Issue 5, May 2008
See notice on first page
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
Field
Verbose output
number Length field name
1.
2
bytes
PCMD software
data format version
Field description
Range of values
2.
4
bytes
Sequence Number
(assigned at OMP)
3.
2
bytes
4.
8
bytes
Duplicate Record
Sequence Number
Always zero in
Release 27.0.
5.
1 byte
Mobile ID Type
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
Table 5-11
Field
Verbose output
number Length field name
7.
8
bytes
Table 5-12
International
Mobile Station
Identifier
(continued)
Field description
Range of values
International Mobile
Station Identifier (IMSI)
15 digits
(maximum)
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.
9.
4
bytes
UATI Complete
Message
Received Time
Timestamp of
when UATI
Complete
Message
received at the
RNC from the
AT.
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
Table 5-12
Verbose
output field
Field
number Length name
12.
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
Table 5-12
Verbose
output field
Field
number Length name
14.
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
Verbose
output field
Field
number Length name
Field description
Range of values
17.
4
bytes
Connection
Request Time
18.
4
bytes
Connection
Established
Time
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-31
Issue 5, May 2008
See notice on first page
Table 5-13
Verbose
output field
Field
number Length name
(continued)
Field description
Range of values
19.
4
bytes
A12 RAN
Authentication
Time
20.
4
bytes
A10 Link
Established
Time
21.
4
bytes
Connection
Duration
22.
1 byte
Connection
Final Class
23.
2
bytes
CFC Qualifier
24.
4
bytes
Secondary CFC
Qualifier
25.
1 byte
AT- or
AN-Initiated
Connection
Request
0 = AT-Initiated
1 = AN-Initiated
2 = Fast Connect
26.
1 byte
Silent
Reorigination
Flag
Always zero in
R26.
27.
1 byte
Service Node
ID
0-255
28.
4
bytes
TP for
Connection
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
5-32
Table 5-13
Verbose
output field
Field
number Length name
(continued)
Field description
Range of values
29.
4
bytes
PDSN IP No.
30.
2
bytes
Seizure Cell
Number
1-maximum number
of cells supported
31.
1 byte
Seizure Sector
Number
0-6
32.
2
bytes
Last
DRC-Pointed
Cell
0-maximum number
of cells supported
33.
1 byte
Last
DRC-Pointed
Sector Number
0-6
34.
1 byte
Number of DO
pages
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
Table 5-13
Verbose
output field
Field
number Length name
36.
1 byte
Configuration
Negotiation
Failure Code
(continued)
Field description
Range of values
37.
4
bytes
Configuration
Negotiation
End Time
Timestamp
38.
1 byte
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
0-2047 in
increments of 1
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
5-34
Table 5-13
Verbose
output field
Field
number Length name
40.
1 byte
Assigned Band
Class
(continued)
Field description
Range of values
0 = Cellular: 850
band class
1 = PCS: 1900
band class
4 = Korea PCS
5 = 450
6 = China 2100
41.
2
bytes
Assigned
Channel
Number
0-2047 in
increments of 1
42.
1 byte
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
0-2047 in
increments of 1
44.
1 byte
Connection
Established
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:
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-35
Issue 5, May 2008
See notice on first page
Table 5-14
Field
number Length
Verbose output
field name
Field description
Range of values
45.
4 bytes
RLP Bytes
Transmitted to AT
46.
4 bytes
RLP Bytes
Received from AT
47.
4 bytes
RLP Bytes
Retransmitted
(NAKed) to AT
48.
4 bytes
RLP Bytes
Re-received from
AT
Table 5-15
Verbose
output field
Field
number Length name
Field description
Range of values
49.
1 byte
Number of SM
Counts (One
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
Table 5-15
Verbose
output field
Field
number Length name
52.
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
Table 5-16
Verbose
output field
Field
number Length name
56.
1 byte
Personality
Type
Field description
Range of values
0 = Rev 0
1 = Rev A
2 = MFPA
Table 5-17
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
Table 5-17
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.
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
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
Table 5-17
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
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
Table 5-17
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
Table 5-17
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
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
Field Number
Description of data
Sector Number
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
5-42
Table 5-18
(continued)
Field Number
Description of data
RNC ID
SN ID
10
11
12
13
14
15
16
17
18
Sector Number
19
RNC ID
20
SN ID
21
22
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
Table 5-18
(continued)
Field Number
Description of data
26
are currently part of the active set at the moment the RUM
message was received at the RNC.
27
28
29
30
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
Field Number
Description of data
Reservation Label
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
5-44
Table 5-19
(continued)
Field Number
Description of data
Reservation Denied
0 - False
1 - True
10
11
12
SpareFlow(01)
13
SpareFlow(02)
14
SpareFlow(03)
15
SpareFlow(04)
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
Table 5-20
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
Value
001
002
(FRF) - QoS
Requirements Not
Met
003
FRF - Resource
Problem - TP
004
FRF - Resource
Problem - Cell
Service Denial
(Authorization
Exception)
006
General System
Error
Null
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
5-46
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
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
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
5-52
5-54
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
3:
3:
3:
3:
3:
3:
3:
3:
4:
4:
4:
4:
4:
4:
4:
4:
4:
4:
4:
4:
4:
5:
5:
5:
5:
5:
5:
5:
5:
5:
5:
5-56
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
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:
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:
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:
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
pilots
3:
3:
3:
4:
4:
4:
4:
4:
4:
4:
4:
4:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
5-58
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
1:
1:
1:
2:
2:
2:
2:
2:
2:
2:
2:
2:
2:
2:
2:
2:
3:
3:
3:
3:
3:
3:
3:
3:
3:
3:
3:
3:
3:
4:
4:
4:
4:
4:
4:
4:
4:
4:
4:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
5-60
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:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
5-62
How
data is accessed from the OMP-FX v.2
...................................................................................................................................................................................................................................
Introduction
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
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-63
Issue 5, May 2008
See notice on first page
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
Where:
[omp machine]
[port]
is either 7050 for human readable format or 7051 through 7054 for delimited
format.
[>filename]
Example:
telnet ompa 7050
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
5-64
...................................................................................................................................................................................................
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
Using
FTP to retrieve EV-DO PCMD data
...................................................................................................................................................................................................................................
Purpose
Verify that the activation of the PCMD for 1xEV-DO feature is complete. For
activation details, see Implementing the feature (p. 5-73).
Steps
Where:
[hostname]
Example:
ftp ompa
Use the cd command to go to the directory location where the stored files are located:
cd /omp-data/logs/evdo_pcmd
...................................................................................................................................................................................................
= year
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
5-66
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)
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.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-67
Issue 5, May 2008
See notice on first page
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
Enter the evdo_pcmdaemon command to generate the desired data format. For example:
evdo_vpcmdviewer
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
Result: The EV-DO PCMD viewer immediately starts to display the data that is
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
EV-DO
PCMD viewer command format and syntax
...................................................................................................................................................................................................................................
Introduction
This section describes the format and syntax of the evdo_pcmdaemon UNIX command.
Description
Availability
Syntax conventions
The options for the evdo_pcmdaemon command are described in Table 5-21,
evdo_pcmdaemon command options (p. 5-70).
Table 5-21
Option
Description
-n
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
5-70
Table 5-21
(continued)
Option
Description
-h
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
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-71
Issue 5, May 2008
See notice on first page
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:
The Inter and Intra-RNC Handoff Enhancement feature adds the following new cases
to the set of PCMD events:
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
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
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)
activated.
Procedure
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
...................................................................................................................................................................................................
Activate any other control form the EMS FMS Frame view (such as,
PCMD Normal Connections, PCMD Normal Sessions, PCMD RUM Collections).
Click Submit.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
5-75
Issue 5, May 2008
See notice on first page
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:
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
....................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
6-1
Issue 5, May 2008
See notice on first page
Overview
User interface
Feature impact
Service measurements
None
None
None
6-3
Prerequisites
6-4
Feature description
6-5
Feature interactions
6-7
6-8
6-9
6-10
6-11
6-13
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
6-2
Availability
...................................................................................................................................................................................................................................
Release 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
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 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 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
Feature
description
...................................................................................................................................................................................................................................
Introduction
The following information describes the functionality, benefits, and operation of the
HRPD RNC Performance and Capacity Improvements feature.
Functionality
R25.0
R26.0
AP
TP
TP
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
Feature description
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
Feature
interactions
...................................................................................................................................................................................................................................
Introduction
The HRPD RNC Performance and Capacity Improvements feature interacts with the
following features:
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
Issues
and caveats
...................................................................................................................................................................................................................................
Introduction
The HRPD RNC Performance and Capacity Improvements feature is subject to the
following special issues and/or caveats.
Issues
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
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
6-8
Implementing
the feature
...................................................................................................................................................................................................................................
Overview
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:
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
Activating
the feature
...................................................................................................................................................................................................................................
Purpose
This procedure activates the HRPD RNC Performance and Capacity Improvements
feature in a CDMA2000 1xEV-DO network.
Procedure
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
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
6-10
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
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 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
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
6-12
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
Procedure
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
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
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
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:
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
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:
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:
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
Overview
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
None
Service measurements
None
None
7-5
Prerequisites
7-6
7-7
Feature interactions
7-14
7-15
7-30
7-31
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
7-4
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
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
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
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
7-7
Issue 5, May 2008
See notice on first page
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:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
7-8
Customer installs license key(s) per procedures found in document 1xEV-DO RAS
Planning and Implementation Guide, 401-614-101.
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)
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).
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
7-9
Issue 5, May 2008
See notice on first page
Enhanced FTC MAC allows MAC Layer Packing and Multi-Users Packet (MUP):
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 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
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
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:
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
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:
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)
This feature supports both Rel 0 systems and in mixed Rel 0/Rev. A systems:
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
7-13
Issue 5, May 2008
See notice on first page
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:
All the Rev. A features that impact the RNC, result in new requirements for the
following features:
Enhanced Reverse and Forward Links using Enhanced MAC Protocols with Rev. A Subtype 2
Physical Layer (FID 12078.2)
HRPD Rev. A Support on Modular Cell 4.0 BTS Platforms using SB-EVM (FID 12078.5)
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
Impacts
on service measurements
...................................................................................................................................................................................................................................
Introduction
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
Service
measurement
subcategory
Count abbreviation
Count name
SECT-CARRHCS
EVM_DRC_ERASURE
SECT-CARRHCS
EVM_DRC_RATE_0
SECT-CARRHCS
EVM_DRC_RATE_1228_8
SECT-CARRHCS
EVM_DRC_RATE_1228_8_L
SECT-CARRHCS
EVM_DRC_RATE_1536
SECT-CARRHCS
EVM_DRC_RATE_153_6
SECT-CARRHCS
EVM_DRC_RATE_1843_2
SECT-CARRHCS
EVM_DRC_RATE_2457_6
SECT-CARRHCS
EVM_DRC_RATE_3072
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
7-15
Issue 5, May 2008
See notice on first page
Table 7-1
Service
measurement
subcategory
Count abbreviation
Count name
SECT-CARRHCS
EVM_DRC_RATE_307_2
SECT-CARRHCS
EVM_DRC_RATE_307_2_L
SECT-CARRHCS
EVM_DRC_RATE_38_4
SECT-CARRHCS
EVM_DRC_RATE_614_4
SECT-CARRHCS
EVM_DRC_RATE_614_4_L
SECT-CARRHCS
EVM_DRC_RATE_76_8
SECT-CARRHCS
EVM_DRC_RATE_921_6
SECT-CARRHCS
EVM_FTC_NUM_SLOT_1228_8
SECT-CARRHCS
EVM_FTC_NUM_SLOT_1536
SECT-CARRHCS
EVM_FTC_NUM_SLOT_153_6
SECT-CARRHCS
EVM_FTC_NUM_SLOT_1843_2
SECT-CARRHCS
EVM_FTC_NUM_SLOT_19_2
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
7-16
Table 7-1
Service
measurement
subcategory
Count abbreviation
Count name
SECT-CARRHCS
EVM_FTC_NUM_SLOT_2457_6
SECT-CARRHCS
EVM_FTC_NUM_SLOT_3072
SECT-CARRHCS
EVM_FTC_NUM_SLOT_307_2
SECT-CARRHCS
EVM_FTC_NUM_SLOT_38_4
SECT-CARRHCS
EVM_FTC_NUM_SLOT_4_8
SECT-CARRHCS
EVM_FTC_NUM_SLOT_614_4
SECT-CARRHCS
EVM_FTC_NUM_SLOT_76_8
SECT-CARRHCS
EVM_FTC_NUM_SLOT_921_6
SECT-CARRHCS
EVM_FTC_NUM_SLOT_9_6
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
7-17
Issue 5, May 2008
See notice on first page
Table 7-1
Service
measurement
subcategory
Count abbreviation
Count name
SECT-CARRHCS
EVM_FTC_TOT_BYTES_1228_8
SECT-CARRHCS
EVM_FTC_TOT_BYTES_1536
SECT-CARRHCS
EVM_FTC_TOT_BYTES_153_6
SECT-CARRHCS
EVM_FTC_TOT_BYTES_1843_2
SECT-CARRHCS
EVM_FTC_TOT_BYTES_19_2
SECT-CARRHCS
EVM_FTC_TOT_BYTES_2457_6
SECT-CARRHCS
EVM_FTC_TOT_BYTES_3072
SECT-CARRHCS
EVM_FTC_TOT_BYTES_307_2
SECT-CARRHCS
EVM_FTC_TOT_BYTES_38_4
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
7-18
Table 7-1
Service
measurement
subcategory
Count abbreviation
Count name
SECT-CARRHCS
EVM_FTC_TOT_BYTES_4_8
SECT-CARRHCS
EVM_FTC_TOT_BYTES_614_4
SECT-CARRHCS
EVM_FTC_TOT_BYTES_76_8
SECT-CARRHCS
EVM_FTC_TOT_BYTES_921_6
SECT-CARRHCS
EVM_FTC_TOT_BYTES_9_6
SECT-CARRHCS
EVM_CALL_MUTE_STATE_NUM
Number of Times in
Call Mute State
SECT-CARRHCS
EVM_CALL_MUTE_STATE_PEAK_
DUR
SECT-CARRHCS
EVM_CALL_MUTE_STATE_TOT_
DUR
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
Table 7-1
Service
measurement
subcategory
Count abbreviation
Count name
SECT-CARRHCS
SECT-CARRHCS
EVM_FWD_PACKETS_153_6_TOTAL_
COUNT
SECT-CARRHCS
SECT-CARRHCS
SECT-CARRHCS
SECT-CARRHCS
EVM_FWD_PACKETS_307_2_TOTAL_
COUNT
SECT-CARRHCS
EVM_FWD_PACKETS_38_4_TOTAL_
COUNT
SECT-CARRHCS
SECT-CARRHCS
EVM_FWD_PACKETS_614_4_TOTAL_
COUNT
SECT-CARRHCS
EVM_FWD_PACKETS_76_8_TOTAL_
COUNT
SECT-CARRHCS
EVM_FWD_PACKETS_921_6_TOTAL_
COUNT
SECT-CARRHCS
SM_LT_NOISE_FLOOR_EST
SECT-CARRHCS
SM_SILENCE_INT_NOISE_FLOOR_
EST
SECT-CARRHDRC
(Modified)
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
7-20
Table 7-1
Service
measurement
subcategory
Count abbreviation
Count name
SECT-CARRHDRC
SECT-CARRHDRC
AVG_ACTIVE_CONN_PER_SECTOR_
Rev. A
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
Table 7-1
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
Table 7-1
Service
measurement
subcategory
Count abbreviation
Count name
SECT-CARRHDRC
SECT-CARRHDRC
REVERSE_FRAME_ERROR_COUNT
SECT-CARRHDRC
REV_LINK_FRAME_ERROR_COUNT_
153_6_KBPS
SECT-CARRHDRC
REV_LINK_FRAME_ERROR_COUNT_
19_2_KBPS
SECT-CARRHDRC
REV_LINK_FRAME_ERROR_COUNT_
38_4_KBPS
SECT-CARRHDRC
REV_LINK_FRAME_ERROR_COUNT_
76_8_KBPS
SECT-CARRHDRC
REV_LINK_FRAME_ERROR_COUNT_
9_6_KBPS
SECT-CARRHDRC
REV_OL_PC_TOTAL_SETPOINT_1024
SECT-CARRHDRC
REV_OL_PC_TOTAL_SETPOINT_
12288
SECT-CARRHDRC
REV_OL_PC_TOTAL_SETPOINT_128
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
7-23
Issue 5, May 2008
See notice on first page
Table 7-1
Service
measurement
subcategory
Count abbreviation
Count name
SECT-CARRHDRC
REV_OL_PC_TOTAL_SETPOINT_1536
SECT-CARRHDRC
REV_OL_PC_TOTAL_SETPOINT_2048
SECT-CARRHDRC
REV_OL_PC_TOTAL_SETPOINT_256
SECT-CARRHDRC
REV_OL_PC_TOTAL_SETPOINT_3072
SECT-CARRHDRC
REV_OL_PC_TOTAL_SETPOINT_4096
SECT-CARRHDRC
REV_OL_PC_TOTAL_SETPOINT_512
SECT-CARRHDRC
REV_OL_PC_TOTAL_SETPOINT_6144
SECT-CARRHDRC
REV_OL_PC_TOTAL_SETPOINT_768
SECT-CARRHDRC
REV_OL_PC_TOTAL_SETPOINT_8192
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
7-24
Table 7-1
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
Table 7-1
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
SECT-CARRHDRC
REV_PACKETS_12288_TOTAL_
COUNT
SECT-CARRHDRC
REV_PACKETS_128_TOTAL_COUNT
SECT-CARRHDRC
REV_PACKETS_1536_TOTAL_COUNT
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
7-26
Table 7-1
Service
measurement
subcategory
Count abbreviation
Count name
SECT-CARRHDRC
REV_PACKETS_2048_TOTAL_COUNT
SECT-CARRHDRC
REV_PACKETS_256_TOTAL_COUNT
SECT-CARRHDRC
REV_PACKETS_3072_TOTAL_COUNT
SECT-CARRHDRC
REV_PACKETS_4096_TOTAL_COUNT
SECT-CARRHDRC
REV_PACKETS_512_TOTAL_COUNT
SECT-CARRHDRC
REV_PACKETS_6144_TOTAL_COUNT
SECT-CARRHDRC
REV_PACKETS_768_TOTAL_COUNT
SECT-CARRHDRC
REV_PACKETS_8192_TOTAL_COUNT
SECT-CARRHDRC
TOTAL_REVERSE_FRAME_COUNT
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
7-27
Issue 5, May 2008
See notice on first page
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
Service measurement
subcategory
Count abbreviation
Count name
AP
NUM_AT_REL0_SESS_
ESTABLISHED
AP
NUM_AT_Rev.
A_SESS_ESTABLISHED
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
Reference
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
7-29
Issue 5, May 2008
See notice on first page
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
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
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
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:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
8-2
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:
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
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
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:
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
Overview
The features that are described in this document impact the following user interfaces:
Feature
User interface
Feature impact
Service measurements
See Impacts on
service measurements
(p. 8-24)
Automatic Message
Accounting (AMA)
subsystem
None
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
8-6
Prerequisites
8-7
8-9
Feature interactions
8-19
8-24
8-51
8-52
8-54
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-5
Issue 5, May 2008
See notice on first page
Availability
...................................................................................................................................................................................................................................
Release availability
The following table identifies the AMPS/PCS software releases in which the DOrA
Application QoS Features are available.
Feature
Available in
Market availability
The DOrA Application QoS Features are available in the following market:
Feature
Available in
All markets
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
8-6
Prerequisites
...................................................................................................................................................................................................................................
Introduction
The DOrA Application QoS Features support the following air-interface technologies:
EV-DO
Software requirements
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
Prerequisites
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)
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
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
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
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:
The Session State Information Record will be enhanced to include Rev A protocols
and MFPA information.
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
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
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
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
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)
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:
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:
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-15
Issue 5, May 2008
See notice on first page
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
1283
Blank
280
Blank
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
8-16
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:
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
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
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
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:
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:
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
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:
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:
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:
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-21
Issue 5, May 2008
See notice on first page
Feature interactions
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
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:
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-23
Issue 5, May 2008
See notice on first page
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:
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
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
Service measurement
subcategory
Count abbreviation
Count name
CG CONTL
CG CONTL
CG CONTL
CG CONTL
CG CONTL
CG CONTL
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
Table 8-1
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
CG OHM
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
SECT-CARR-HCS
EVM_ACCESS_CH_MAC_
PACKETS_19_2
SECT-CARR-HCS
EVM_ACCESS_CH_MAC_
PACKETS_38_4
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
8-26
Table 8-1
SECT-CARR-HCS
EVM_ACCESS_CH_MAC_
PACKETS_9_6
SECT-CARR-HCS
EVM_AVG_USERS_PER_
MUP
SECT-CARR-HCS
EVM_FL_MUPS
SECT-CARR-HCS
SECT-CARR-HCS
SECT-CARR-HCS
SECT-CARR-HCS
SECT-CARR-HCS
SECT-CARR-HCS
SECT-CARR-HCS
SECT-CARR-HCS
EVM_RLP_TXED_FTC_
BE
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-27
Issue 5, May 2008
See notice on first page
Table 8-1
SECT-CARR-HCS
EVM_RLP_TXED_FTC_
CPS
SECT-CARR-HCS
EVM_RLP_TXED_FTC_
CS
SECT-CARR-HCS
EVM_RLP_TXED_FTC_
CV
SECT-CARR-HCS
EVM_RLP_TXED_FTC_
SMC
SECT-CARR-HCS
RLP_RCVD_RTC_SMC
TP
A11_SESSION_UPDATE_
ACCEPTED
TP
A11_SESSION_UPDATE_
RECEIVED
TP
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:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
8-28
Personality (especially MFPA) related SMs are MFPA specific SMs that could
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
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
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-29
Issue 5, May 2008
See notice on first page
Table 8-2
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
SN-HCS-CTID-EVM
SN-HCS-CTID-EVM
SN-HCS-CTID-EVM
SN-HCS-CTID-EVM
SN-HCS-CTID-EVM
SN-HCS-CTID-EVM
SN-HCS-CTID-EVM
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
8-30
Table 8-3
More QoS Enhancements for the HRPD Rev. A Network: New Service
Measurements (continued)
SN-HCS-CTID-EVM
SN-HCS-CTID-EVM
SN-HCS-CTID-EVM
SN-HCS-CTID-EVM
SN-HCS-CTID-EVM
SN-HCS-CTID-EVM
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-31
Issue 5, May 2008
See notice on first page
Table 8-3
More QoS Enhancements for the HRPD Rev. A Network: New Service
Measurements (continued)
SN-HCS-CTID-EVM
SN-HCS-CTID-EVM
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
Table 8-3
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
SN-HCSCTID- EVM
SN-HCSCTID- EVM
SN-HCSCTID- EVM
SN-HCSCTID- EVM
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-33
Issue 5, May 2008
See notice on first page
Table 8-3
More QoS Enhancements for the HRPD Rev. A Network: New Service
Measurements (continued)
SN-HCSCTID- EVM
SN-HCSCTID- EVM
SN-HCSCTID- EVM
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
Table 8-3
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
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
SN-HCS-ANT-CARR
PERS_SWTCH_CONN_
ESTABLISHED
SN-IEnd- FMS-OHM
NUM_AT_MFPA_SESS_
ESTABLISHED
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
Table 8-3
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
SN-HCS-ANT-CARR
PEAK_OPEN_RL_FLOW
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
SN-FMS-TP
RLP_PKT_SENT_TO_
PCF
SN-FMS-TP
SN-FMS-TP
SN-FMS-TP
SN-HCS-ANT-CARR
FL_BTS_DELAY_SUM
SN-HCS-ANT-CARR
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
8-36
Table 8-3
More QoS Enhancements for the HRPD Rev. A Network: New Service
Measurements (continued)
SN-HCS-ANT-CARR
FL_BTS_DELAY_S_
PEAK
SN-FMS-BTS
FL_RNC_DELAY_SUM
SN-FMS-BTS
SN-FMS-BTS
FL_RNC_DELAY_S_
PEAK
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
SN-HCSCTID
FL_RNC_N_BH_DELAY_
S_PEAK
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
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
Table 8-3
More QoS Enhancements for the HRPD Rev. A Network: New Service
Measurements (continued)
SN-FMS-TP
AVG_CLK_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
Table 8-4
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
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
Table 8-5
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
SN-IEnd-FMS-OHM
RESV_NULLED_A11_
SESS_UPDATE
SN-HCS-ANT-CARR
SM_ENHANCED_AVG_
RSSIRISE
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
SN-HCS-ANT-CARR
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
Table 8-5
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
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
SN-HCS-ANT-CARR
SN-HCS-ANT-CARR
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
8-40
Table 8-5
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
SN-HCS-ANT-CARR
AC_RF_RES_FAILURE_
FL_CS
SN-HCS-ANT-CARR
SN-HCS-ANT-CARR
AC_RF_RES_FAILURE_
FL_CV
SN-HCS-ANT-CARR
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
Table 8-5
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
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
Table 8-5
SN-HCS-ANT-CARR
SN-HCS-ANT-CARR
AC_RF_RES_FAILURE_
RL_CS
SN-HCS-ANT-CARR
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
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
Table 8-5
SN-HCS-ANT-CARR
RLP_RCVD_RTC_CS
SN-HCS-ANT-CARR
RLP_RCVD_RTC_CV
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
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.
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
Service measurement
subcategory
Count abbreviation
Count name
SECT-CARR-HDRC
MO_DOS_BE
SECT-CARR-HDRC
MO_DOS_CMCS
SECT-CARR-HDRC
MO_DOS_LL_MCS
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
8-44
The 1xEV-DO Basic PTT Using 1xEV-DO Rev. A Network feature affects the
following categories of services 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
Service measurement
subcategory
Count
abbreviation
CG RNC-PGPROFID
PAGE_REQ_DROPPED_
Number of FL Reservation
Downgraded for Conversational
AP_OVLD
Count name
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
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
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
Service measurement
subcategory
Count
abbreviation
SECT-CARR-HDRC
Count name
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
(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
Table 8-9
(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
The HRPD PTT Paging Enhancements feature affects the following categories of
services measurements:
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-47
Issue 5, May 2008
See notice on first page
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
Service measurement
subcategory
Count
abbreviation
Count name
OHM-PGPROFID
PAGE_ABORT_
HIGHER_PID
OHM-PGPROFID
PAGE_ESC
Paging Escalations
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
Service measurement
subcategory
Count
abbreviation
Count name
OHM-PGPROFID-PGAT
PAGES
Pages
OHM-PGPROFID-PGAT
PAGE_CR_RCVD
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
8-48
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
Service measurement
subcategory
Count
abbreviation
Count name
OHM-PGPROFID
PAGE_DE_ESC
Paging De-Escalations
OHM-PGPROFID
PAGE_DE_ESC_
RESP
OHM-PGPROFID
PAGE_ESC_RESP
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
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
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
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
References
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
8-50
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
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
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
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
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
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.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-55
Issue 5, May 2008
See notice on first page
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.
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
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
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
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
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
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:
Table 8-15
Direct_
DoS
Last_Active_Set
Last_Seen_RNC
Mixed_
DoS
RURDoS
RNC_Group
Distance_Tier12
Distance_Tier2
Distance_Tier3
2
2
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
8-61
Issue 5, May 2008
See notice on first page
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
Overview
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
Service measurements
None
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
9-4
Prerequisites
9-5
Feature description
9-6
Feature interactions
9-9
9-10
9-11
9-12
9-13
9-14
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
9-2
Overview
9-15
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
9-3
Issue 5, May 2008
See notice on first page
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
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
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:
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.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
9-6
Feature description
MLG configuration: All T1s at the same Universal Radio Controller (URC) must
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
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
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
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
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
Parameter name
Description
Allowed
values
MP Enabled
y or n
Default = n
References
For more information about these RC/V forms and fields, see the following
CDMA2000 wireless networks documents:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
9-10
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:
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
Count abbreviation
Count name
DL_UPLINK_AVG_THRUPUT
DL_UPLINK_PEAK_THRUPUT
DL_DOWNLINK_AVG_THRUPUT
DL_DOWNLINK_PEAK_THRUPUT
References
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
9-11
Issue 5, May 2008
See notice on first page
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
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
9-12
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
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
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
9-14
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
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
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
9-15
Issue 5, May 2008
See notice on first page
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
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) ___.___.___.___
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
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)
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
Overview
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
Element Management
System (EMS) or
Operations and
Maintenance Center Radio Access Network
(OMC-RAN)
None
Service measurements
Automatic Message
Accounting (AMA)
subsystem
None
None
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
10-2
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
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
10-5
Prerequisites
10-6
10-7
10-13
10-17
10-19
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
10-3
Issue 5, May 2008
See notice on first page
Overview
10-20
10-23
10-24
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
10-4
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
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)
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
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:
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
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:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
10-8
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
If not, warning messages will be displayed as the purchased capacity for QoS
applications is reached and a grace period is initiated:
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
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:
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
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
The following information describes the functionality, benefits, and operation of the
1xEV-DO Rev A Application Pricing Enhancements (FID 12905.1) optional feature.
Functionality
Grace
Override
Additional enhancements:
Benefits
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
10-13
Issue 5, May 2008
See notice on first page
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
licenseSMLog
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
RNC 26:
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
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
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
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:
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:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
10-18
The 1xEV-DO Rev A Application Pricing Enhancements optional feature interacts with
the following features:
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
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
Count abbreviation
Count name
AVG_BTS_EQU_LICENSE_USAGE
BTS_EQU_LICENSE_STATE
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
Count abbreviation
Count name
CS_RESV_DROPPED_HO_NO_EQU_
LICENSE_KEY
CV_RESV_DROPPED_HO_NO_EQU_
LICENSE_KEY
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
10-20
Table 10-2
Count abbreviation
Count name
PTT_RESV_DROPPED_HO_NO_EQU_
LICENSE_KEY
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
Count abbreviation
Count name
AVG_RNC_LICENSE_USAGE_CS
AVG_RNC_LICENSE_USAGE_CV
AVG_RNC_LICENSE_USAGE_GENERIC
AVG_RNC_LICENSE_USAGE_PTT
PEAK_RNC_LICENSE_USAGE_CS
PEAK_RNC_LICENSE_USAGE_CV
PEAK_RNC_LICENSE_USAGE_
GENERIC
PEAK_RNC_LICENSE_USAGE_PTT
RNC_LICENSE_STATE_CS
RNC_LICENSE_STATE_CV
RNC_LICENSE_STATE_GENERIC
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
10-21
Issue 5, May 2008
See notice on first page
Table 10-3
(continued)
Count abbreviation
Count name
RNC_LICENSE_STATE_PTT
References
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
10-22
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
10-23
Issue 5, May 2008
See notice on first page
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
....................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
11-1
Issue 5, May 2008
See notice on first page
Overview
User interface
Feature impact
Service measurements
None
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
11-3
Prerequisites
11-4
Feature description
11-5
Feature interactions
11-9
11-10
Impacts on TI messages
11-13
11-15
11-18
11-19
11-26
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
11-2
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
Prerequisites
...................................................................................................................................................................................................................................
Introduction
The RNC Grouping to Improve Idle Hand-off Performance optional feature has the
following prerequisites.
Supported technologies
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
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
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
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:
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
11-7
Issue 5, May 2008
See notice on first page
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
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
11-8
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
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
Count abbreviation
Count name
INTER_RNC_CONN_ESTABLISHED
INTER_RNC_CONN_REQ
INTER_RNC_TCA_SENT
INTRA_RNC_GROUP_BORDER_
CROSSED
INTRA_RNC_GROUP_SESS_TRFR_
ATTEMPT
INTRA_RNC_GROUP_SESS_TRFR_
SUCCESS
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
Count abbreviation
Count name
REQ_WITH_UNRECOGNIZED_UATI
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
11-10
Table 11-2
(continued)
Count abbreviation
Count name
DANGLING_SESS_CLOSED
SESS_SETUP_UATI_ASSGNMT_MSG
_SENT
SESS_SETUP_UATI_COMPLETE_MSG
_RCVD
AN_INIT_KEEP_ALIVE _REQ
INT_SUBNET_IDLE_TRFR_A13_REQ
_RECVD
INT_SUBNET_IDL_TRFR_ATTMPT
ISBNT_IDL_TRFR_FAIL_SRC_IP_ADR_
NT_FOUND
INT_SUBNET_IDLE_TRFR_A13_SIR_
RCVD_LATE
ISBNT_IDL_TRFR_FAIL_NO_RSP_PRV_
SBNET
ISBNT_IDL_TRFR_FAIL_ORG_PDSN_
CANT_CONN
ISBNT_IDL_TRFR_FAIL_RJCT_MSG_
RCVD
INT_SUBNET_IDL_TRFR_FAIL_OTHER
_REASON
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
11-11
Issue 5, May 2008
See notice on first page
Table 11-2
(continued)
Count abbreviation
Count name
SESS_CLOSE_SESS_TRFR _ABORTED
References
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
11-12
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
Impacts on TI messages
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
11-14
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
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
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
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
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
Go to the RNC Group screen, and click on the Create new RNCGroup instance link.
...................................................................................................................................................................................................
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
...................................................................................................................................................................................................
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
...................................................................................................................................................................................................
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
Parameter
Subnet
Mask =
70
Subnet
Mask = 64
...................................................................................................................................................................................................
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
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
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)
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
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
...................................................................................................................................................................................................
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)
Go to the Group Member screen and select the RNC member to be deleted.
...................................................................................................................................................................................................
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
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
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
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
...................................................................................................................................................................................................
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.
...................................................................................................................................................................................................
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
Heartbeat
Interval
(seconds)
ROP
Report
Interval
(minutes)
RNCs Monitored
Disabled
n/a
n/a
n/a
Enabled
15
Enabled
60
Enabled
120
Enabled
10
15
Enabled
10
60
Enabled
10
120
Enabled
60
120
Disabled
n/a
n/a
n/a
Enabled
15
10
Enabled
60
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
11-24
Table 11-4
(continued)
11
Enabled
120
12
Enabled
10
15
13
Enabled
10
60
14
Enabled
10
120
15
Enabled
60
120
E...................................................................................................................................................................................................
ND OF STEPS
System behaviors
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
11-25
Issue 5, May 2008
See notice on first page
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:
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
Go to the Global Config DO tab, and click on left arrow of Global Config DO.
...................................................................................................................................................................................................
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
...................................................................................................................................................................................................
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
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
Parameter
Subnet
Mask =
70
Subnet
Mask = 64
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
11-27
Issue 5, May 2008
See notice on first page
Table 11-5
(continued)
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
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)
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
...................................................................................................................................................................................................
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
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
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)
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
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
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
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
...................................................................................................................................................................................................
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.
...................................................................................................................................................................................................
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
Heartbeat
Interval
(seconds)
ROP
Report
Interval
(minutes)
RNCs Monitored
Disabled
n/a
n/a
n/a
Enabled
15
Enabled
60
Enabled
120
Enabled
10
15
Enabled
10
60
Enabled
10
120
Enabled
60
120
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
11-32
Table 11-6
(continued)
Disabled
n/a
n/a
n/a
Enabled
15
10
Enabled
60
11
Enabled
120
12
Enabled
10
15
13
Enabled
10
60
14
Enabled
10
120
15
Enabled
60
120
E...................................................................................................................................................................................................
ND OF STEPS
System behaviors
...................................................................................................................................................................................................................................
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
Feature summary
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
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
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
See Impacts on TI
Messages
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
12-2
Overview
Feature
User interface
Feature impact
Element Management
System (EMS) or
Operations and
Maintenance Center Radio Access Network
(OMC-RAN)
None
Service measurements
None
Automatic Message
Accounting (AMA)
subsystem
None
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
None
12-5
Prerequisites
12-6
12-8
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
12-3
Issue 5, May 2008
See notice on first page
Overview
12-11
12-13
Feature interactions
12-15
12-16
Impacts on TI messages
12-17
12-26
12-27
12-28
12-29
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
12-4
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
Market availability
Available in
1xEV-DO Performance
Monitoring Tools Enhancements
(FID 9253.1)
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
12-5
Issue 5, May 2008
See notice on first page
Prerequisites
...................................................................................................................................................................................................................................
Introduction
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:
The AT Trace Enhancement for Customer Use optional feature is supported in the
following air-interface technologies:
HLR configuration
1xEV-DO Performance Monitoring Tools Enhancements (FID 9253.1)
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)
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
12-6
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 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)
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
The following information describes the functionality, benefits, and operation of the
1xEV-DO Performance Monitoring Tools Enhancements (FID 9253.1) feature .
Functionality
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:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
12-8
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
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
For example, to run on RNCs 1, 2, and 3 on the service node enter the following:
evstartses r 1-3
evstartses bxxx
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
evstartses o sesData
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
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:
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
12-11
Issue 5, May 2008
See notice on first page
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
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.
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
The AT Trace Enhancement for Customer Use feature is under FAF control and
provides the following capabilities:
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
Feature
interactions
...................................................................................................................................................................................................................................
Introduction
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:
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
Impacts
on service measurements
...................................................................................................................................................................................................................................
Introduction
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
12-16
Impacts
on TI messages
...................................................................................................................................................................................................................................
Introduction
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
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
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
Impacts on TI messages
Impacts on TI messages
1. evstatusses
2. evstatusses -o evses.status
3. evstatusses -h
1 ERROR: Failed to query status of the session
12-20
Impacts on TI messages
Impacts on TI messages
12-22
Impacts on TI messages
Impacts on TI messages
12-24
Impacts on TI messages
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
12-25
Issue 5, May 2008
See notice on first page
Implementing
the feature
...................................................................................................................................................................................................................................
Overview
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
12-26
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
This procedure activates the AT Trace Enhancement for Customer Use feature in a
1xEV-DO Network.
Procedure
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
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.
...................................................................................................................................................................................................................................
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)
The Intra-RNC Session Resource Balancing in 1xEV-DO affects the user interfaces that
are listed in the following table.
User interface
Feature impact
None
....................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
13-1
Issue 5, May 2008
See notice on first page
Overview
User interface
Feature impact
Service measurements
None
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
13-3
Prerequisites
13-4
Feature description
13-5
Feature interactions
13-7
13-8
Impacts on TI messages
13-11
13-14
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
13-2
Availability
...................................................................................................................................................................................................................................
Release availability
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
13-3
Issue 5, May 2008
See notice on first page
Prerequisites
...................................................................................................................................................................................................................................
Introduction
The Intra-RNC Session Resource Balancing in 1xEV-DO feature has the following
prerequisites.
Supported 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
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
13-4
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 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
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
13-5
Issue 5, May 2008
See notice on first page
Feature description
Normal state session load is below Intra-RNC UATI session balance threshold
Balance State session load is between Intra-RNC UATI session balance 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
Alarms
The Intra-RNC Session Resource Balancing in 1xEV-DO feature introduces two new
alrams:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
13-6
Feature
interactions
...................................................................................................................................................................................................................................
Introduction
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
13-7
Issue 5, May 2008
See notice on first page
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
Count abbreviation
Count name
AVG_SESS_LOAD_OHM
OHM_SESS_CAPACITY
OHM_SESS_CAPACITY
SESS_BAL_REQ_INTRA_RNC_ORIG_
OHM
SESS_BAL_UATI_COMPLETE_RCVD_
ORIG_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
Count abbreviation
Count name
INT_SUBNET_IDLE_TRFR_A13_SIR_
RCVD_LATE
INT_SUBNET_IDL_TRFR_ATTMPT
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
13-8
Table 13-2
Count abbreviation
Count name
ISBNT_IDL_TRFR_FAIL_ORG_PDSN_
CANT_CONN
ISBNT_IDL_TRFR_FAIL_RJCT_MSG_
RCVD
ISBNT_IDL_TRFR_FAIL_SRC_IP_ADR_
NT_FOUND
SESS_SETUP_UATI_ASSGNMT_MSG_
SENT
SESS_SETUP_UATI_COMPLETE_MSG_
RCVD
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
Count abbreviation
Count name
SESS_SETUP_UATI_ASSGNMT_MSG_
SENT_Q
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
13-9
Issue 5, May 2008
See notice on first page
Table 13-3
Count abbreviation
Count name
SESS_SETUP_UATI_COMPLETE_MSG_
RCVD_Q
References
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
13-10
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
Impacts on TI messages
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.
If the OHM is in a pool, but not being used, include the reason why. Valid reasons
include:
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
Impacts on TI messages
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
13-13
Issue 5, May 2008
See notice on first page
Implementing
the feature
...................................................................................................................................................................................................................................
Overview
...................................................................................................................................................................................................................................
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)
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)
Automated Message
Accounting (AMA)
None
....................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
14-1
Issue 5, May 2008
See notice on first page
Overview
User interface
Feature impact
Element
Management System
(EMS)
None
Operations and
Maintenance Center
- Radio Access
Network
(OMC-RAN)
Service
measurements
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
14-4
Prerequisites
14-5
Feature description
14-6
Feature interactions
14-9
14-10
14-15
14-17
14-23
14-26
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
14-2
Overview
14-29
14-30
14-31
14-32
14-34
14-36
14-37
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
14-3
Issue 5, May 2008
See notice on first page
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
Prerequisites
...................................................................................................................................................................................................................................
Introduction
1xEV-DO
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 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
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
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
14-6
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
Feature description
Figure 14-1 Example Application of the Inter-User Priority for Best Effort Data
Applications feature
BTS 2
BTS 1
BTS 3
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
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
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
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
RAN
PDSN
AAA
Session Configuration
Traffic Channel Establishment
XonRequest
A11 RRQ
A11 RRP
XonResponse
A11 RRQ
A11 RRP
[1] RADIUS
Request
[2] RADIUS Accept
A11 SU ACK
IP Address Assignment
AttributeUpdateRequest
AttributeUpdateAccept
AttributeUpdateRequest
AttributeUpdateAccept
A11 RRQ
A11 RRP
Message
Label
[1]
[2]
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
14-11
Issue 5, May 2008
See notice on first page
Message
Label
[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.
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
BTS1
AT
[1] RU+CR+RoR
BTS 2
[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
[1]
[2]
[3]
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
14-13
Issue 5, May 2008
See notice on first page
Message
Label
[4]
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
14-14
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
Impacted by
3GPP2-Inter-User-Priority
3GPP2-Inter-User-Priority attribute
Attribute Name:
3GPP2-Inter-User-Priority
Attribute Type:
26
Vendor ID:
5535
Vendor Type:
139
Vendor Length:
Vendor Value:
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
14-15
Issue 5, May 2008
See notice on first page
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
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
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
Field Name
Description
Allowed Values
Inter-user priority
Yes,
No
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
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
Field Name
Description
Allowed Values
Yes,
No
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
14-18
Table 14-4
(continued)
Field Name
Description
Allowed Values
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
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
Field Name
Description
Allowed Values
blank, 0.25,
0.5, 1-8
blank, 0.25,
0.5, 1-8
blank, 0.25,
0.5, 1-8
blank, 0.25,
0.5, 1-8
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
14-20
Table 14-5
(continued)
Field Name
Description
Allowed Values
blank, 0.25,
0.5, 1-8
blank, 0.25,
0.5, 1-8
blank, 0.25,
0.5, 1-8
blank, 0.25,
0.5, 1-8
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
References
For more information about these forms and fields, see the following CDMA2000
1xEV-DO network documents:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
14-22
Impacts
on service measurements
...................................................................................................................................................................................................................................
Introduction
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
Description
FL_RLP_RATE_PRI_0
FL_RLP_RATE_PRI_1
FL_RLP_RATE_PRI_2
FL_RLP_RATE_PRI_3
FL_RLP_RATE_PRI_4
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
14-23
Issue 5, May 2008
See notice on first page
Table 14-6
(continued)
Description
FL_RLP_RATE_PRI_5
FL_RLP_RATE_PRI_6
FL_RLP_RATE_PRI_7
FL_RLP_RATE_PRI_8
NUM_PRI_0
NUM_PRI_1
NUM_PRI_2
NUM_PRI_3
NUM_PRI_4
NUM_PRI_5
NUM_PRI_6
NUM_PRI_7
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
14-24
Table 14-6
(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
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
14-25
Issue 5, May 2008
See notice on first page
Configuration
and implementation considerations
...................................................................................................................................................................................................................................
Introduction
User Type
IUP Weight
0.5
Police
Fire
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
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
User Type
IUP Weight
0.5
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
14-27
Issue 5, May 2008
See notice on first page
Table 14-8
User Type
IUP Weight
Police
Fire
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
User Type
IUP Weight
0.5
Police
Fire
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
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
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
14-29
Issue 5, May 2008
See notice on first page
Activating
the feature
...................................................................................................................................................................................................................................
Purpose
Ask your account executive to activate the following entry in your Feature Activation
File (FAF):
IUPBEDA
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
14-30
Confirming
feature activation
...................................................................................................................................................................................................................................
Purpose
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
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
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 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
...................................................................................................................................................................................................
Left click on the priority field to be changed and select the desired value from the
menu.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
14-33
Issue 5, May 2008
See notice on first page
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
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
...................................................................................................................................................................................................
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.
...................................................................................................................................................................................................
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
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
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>
...................................................................................................................................................................................................
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
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
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 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
...................................................................................................................................................................................................
Left click on the Enable Inter-User Priority field and select Yes.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
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 affects the user interfaces that are listed in the following
table:
User interface
Feature impact
Accounting,
Authentication, and
Authorization
(AAA)
....................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-1
Issue 5, May 2008
See notice on first page
Overview
User interface
Feature impact
Automated Message
Accounting (AMA)
None
Element
Management System
(EMS)
None
Operations and
Maintenance Center
- Radio Access
Network
(OMC-RAN)
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
15-4
Prerequisites
15-5
Feature description
15-6
Feature interactions
15-10
15-11
15-16
15-18
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
15-2
Overview
15-27
15-34
15-35
15-36
Creating jurisdictions
15-37
15-39
15-45
15-47
15-49
15-56
15-59
15-62
15-64
15-66
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-3
Issue 5, May 2008
See notice on first page
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
Prerequisites
...................................................................................................................................................................................................................................
Introduction
1xEV-DO
Software requirements
Hardware requirements
The JPPSUBEDA feature requires no other hardware beyond the standard hardware in
a CDMA2000 1xEV-DO network.
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
Feature
description
...................................................................................................................................................................................................................................
Introduction
The following information describes the functionality, benefits, and operation of the
JPPSUBEDA feature.
Functionality
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
Feature description
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
Feature description
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:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
15-8
Feature description
Roamer Home
Jurisdiction
Roamer Policy
J1
J1
J2
J2
J2
J3
J1
J3
A
A
B
C
BTS 2
(J2)
BTS 1
(J1)
BTS 3
(J3)
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
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
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-9
Issue 5, May 2008
See notice on first page
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
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
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
[1] RADIUS
Request
[2] RADIUS Accept
A11 SU ACK
IP Address Assignment
AttributeUpdateRequest
AttributeUpdateAccept
AttributeUpdateRequest
AttributeUpdateAccept
A11 RRQ
A11 RRP
Message
Label
[1]
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
15-12
Message
Label
[2]
[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.
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
BTS1
AT
[1] RU+CR+RoR
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
[1]
[2]
[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
Message
Label
[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
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
Impacted by
3GPP2-Inter-User-Priority
Lucent-VID-Home-Area
3GPP2-Inter-User-Priority attribute
Attribute Name:
3GPP2-Inter-User-Priority
Attribute Type:
26
Vendor ID:
5535
Vendor Type:
139
Vendor Length:
Vendor Value:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
15-16
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
Attribute Name:
Lucent-VID-Home-Area
Attribute Type:
26
Vendor ID:
3729
Vendor Type:
11
Vendor Length:
Vendor Value:
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-17
Issue 5, May 2008
See notice on first page
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
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
Field Name
Description
Allowed Values
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
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
Field Name
Description
Allowed Values
Enable Jurisdictional
Priority for Public Safety
Users
Yes,
No
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
Field Name
Description
Allowed Values
Jurisdiction Id
1-65535
Jurisdiction name
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
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
Field Name
Description
Allowed Values
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
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
Object Name
Description
BERoamPolTable
BERoamPolTable
instances
RoamPolAssgn
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
15-22
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
Field Name
Description
Allowed Values
Name
string up to 25
characters
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-23
Issue 5, May 2008
See notice on first page
Table 15-9
Field Name
Description
Allowed Values
Home
Inter-user
Priority (9
rows in
table)
0-7, unknown
Serving
Inter-user
Priority (9
rows in
table)
0-7
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
15-24
Field Name
Description
Allowed Values
Roaming
Jurisdiction
Id (17 rows
in table)
1-65535
Policy name
(17 rows in
table)
string up to 25
characters
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-25
Issue 5, May 2008
See notice on first page
References
For more information about these forms and fields, see the following CDMA2000
1xEV-DO network documents:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
15-26
Configuration
and implementation considerations
...................................................................................................................................................................................................................................
Introduction
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:
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
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
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
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
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:
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
unknown
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
15-30
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
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
unknown
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-31
Issue 5, May 2008
See notice on first page
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
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
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
15-32
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
Procedure
Allowed for
System
Administrator
accounts?
Allowed for
Jurisdiction
User Group
accounts?
Creating jurisdictions
N/A
N/A
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
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
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
15-34
Activating
the feature
...................................................................................................................................................................................................................................
Purpose
Ask your account executive to activate the following entry in your Feature Activation
File (FAF):
JPPSUPBEDA
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-35
Issue 5, May 2008
See notice on first page
Confirming
feature activation
...................................................................................................................................................................................................................................
Purpose
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
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
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
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
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
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
...................................................................................................................................................................................................
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
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-41
Issue 5, May 2008
See notice on first page
second number is the jurisdiction Id. The JurisdictionUserGroup is created when the
jurisdiction is created.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
15-42
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-43
Issue 5, May 2008
See notice on first page
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
15-44
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
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:
...................................................................................................................................................................................................
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
...................................................................................................................................................................................................
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
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
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:
...................................................................................................................................................................................................
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
...................................................................................................................................................................................................
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
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
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:
...................................................................................................................................................................................................
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
...................................................................................................................................................................................................
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
...................................................................................................................................................................................................
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
Result:
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
...................................................................................................................................................................................................
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
...................................................................................................................................................................................................
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
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-55
Issue 5, May 2008
See notice on first page
Making
BTS assignments for a jurisdiction
...................................................................................................................................................................................................................................
Purpose
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:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
15-56
...................................................................................................................................................................................................
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
...................................................................................................................................................................................................
Repeat step Step 2 as needed to assign all required BTSs to the currently selected
jurisdiction.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
15-58
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
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:
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-59
Issue 5, May 2008
See notice on first page
...................................................................................................................................................................................................
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
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-61
Issue 5, May 2008
See notice on first page
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
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/>
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
15-62
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
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
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 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
...................................................................................................................................................................................................
Left click on the Enable Jurisdictional Priority for Public Safety Users
field and select Yes the menu.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
15-65
Issue 5, May 2008
See notice on first page
Deactivating
the feature
...................................................................................................................................................................................................................................
Purpose
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
Service measurements
None
....................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
16-1
Issue 5, May 2008
See notice on first page
Overview
User interface
Feature impact
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
16-3
Prerequisites
16-4
Feature description
16-5
Feature interactions
16-6
Configuration management
16-7
16-8
16-9
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
16-2
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
Prerequisites
...................................................................................................................................................................................................................................
Introduction
The UTP Protocol Acceleration in Hardware feature has the following prerequisites.
Supported 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
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
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
16-5
Issue 5, May 2008
See notice on first page
Feature
interactions
...................................................................................................................................................................................................................................
Introduction
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)
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
16-6
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:
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
Impacts
on service measurements
...................................................................................................................................................................................................................................
Introduction
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
16-8
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
Feature summary
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
17-1
Issue 5, May 2008
See notice on first page
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 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).
Service measurements
None
Automatic Message
Accounting (AMA)
subsystem
None
None
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
17-2
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.
Service measurements
None
Automatic Message
Accounting (AMA)
subsystem
None
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
17-5
Prerequisites
17-7
17-9
17-10
17-11
17-14
17-15
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
17-3
Issue 5, May 2008
See notice on first page
Overview
17-17
17-18
17-20
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
17-4
Availability
...................................................................................................................................................................................................................................
Release availability
Available in
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)
Backhaul Enhancement in
Support of Small Packets on the
Forward Link in 1xEV-DO
(Phase 1b)
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
Availability
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
17-6
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
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
17-7
Issue 5, May 2008
See notice on first page
Prerequisites
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
17-8
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
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
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
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 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:
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:
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
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
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:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
17-12
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
Implementing
the features
...................................................................................................................................................................................................................................
Process
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
17-14
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.
...................................................................................................................................................................................................
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).
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
17-15
Issue 5, May 2008
See notice on first page
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
17-16
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.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
17-17
Issue 5, May 2008
See notice on first page
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.
...................................................................................................................................................................................................
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).
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
17-18
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
17-19
Issue 5, May 2008
See notice on first page
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:
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
17-20
Glossary
....................................................................................................................................................................................................................................
Numerics
1xEV-DO
AAA
Positive Acknowledge
AMA
Access Network
AP
Application Processor
ASCII
....................................................................................................................................................................................................................................
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
CARR
Carrier
CCU
Call Forwarding
CFC
Cisco HDLC
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
GL-2
Glossary
CLI
Cellular Networking
CP
Call Processing
CS
Conversational Speech
CTA
Conversational Video
CW
Call Waiting
....................................................................................................................................................................................................................................
Data Only
DOrA
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
GL-3
Issue 5, May 2008
See notice on first page
Glossary
DRC
ECP
EVolution Data Optimized Rev. A (2 Mbps Peak using 1.25 Mhz, packet voice)
EVM
1xEV-DO Modem
EVT/EVR
FAF
Feature Identifier
FL
Forward Link
FMS
GL-4
Glossary
FMS
GAUP
GNU Zip
....................................................................................................................................................................................................................................
HAI
Handoff Matrix
HRPD
Glossary
HSC
Hardware ID
....................................................................................................................................................................................................................................
IFHO
Inter-frequency Handoff
IMS
IP Multimedia Subsystem
IMS TAS
Interoperability Specification
IP
Internet Protocol
IP/UDP/RTP
Inter-User Priority
....................................................................................................................................................................................................................................
LCP
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
GL-6
Glossary
LL-MCS
MAC
Multi Carrier
MCS
Multi-Link Group
MLPPP
Glossary
MSID
NAK
Not Acknowledged
NAR
OA&M
Overhead Manager
OHM-SFM
GL-8
Glossary
OMP
PAF
Proportional Fair
PFMR
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
Push-to-Talk
....................................................................................................................................................................................................................................
QFAF
Quality of Service
....................................................................................................................................................................................................................................
RAB
Revision 0
Rev. A
(EVolution Data Optimized) Revision A (2 Mbps Peak using 1.25 Mhz, packet voice)
RF
Radio Frequency
RNC
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
Right To Use
RUM
SB-EVM
Service Class
SES
Service Measurements
SMS
Service Node
SNID
Glossary
SSIR
Software Update
....................................................................................................................................................................................................................................
TA
Test Application
TAS
Technician Interface
TP
Traffic Processor
....................................................................................................................................................................................................................................
UATI
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
WSP
...................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
GL-13
Issue 5, May 2008
See notice on first page
Index
Symbols
401-662-102, OMP-FX
Operation, Administration, &
Maintenance Guide, 5-68
.............................................................
A availability of the feature, 4-5
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
.............................................................
.............................................................
OMP, 5-11
.............................................................
C Caveats and issues, 5-10
Example 2, post-processing
tool, 5-15
E EINE, 5-11
.............................................................
M MDCR data record, 5-27, 5-27,
Example 1, post-processing
tool, 5-15
....................................................................................................................................................................................................................................
401-614-413
Alcatel-Lucent - Proprietary
IN-1
Issue 5, May 2008
See notice on first page
Index
.............................................................
P packet data applications, 5-7
.............................................................
.............................................................
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-614-413
See notice on first page
Issue 5, May 2008
IN-2