9222-2400 System Engineering Translations and Maintenance PDF

3
U ser Interfaces
3
Overview
...................................................................................................................................................................................................................................
Purpose
The purpose of this chapter is to enable you to communicate with the CDMA Modular
Cell. To understand and perform operation and maintenance tasks, the technician must
be able to do the following:
Recognize the functions of the different types of user interfaces.

Demonstrate how to access the different user interfaces.
Enter Modular Cell commands through the various user interfaces.
Interpret Modular Cell responses for appropriate action, using appropriate user
documentation.
In addition, this unit enables the reader to make use of Modular Cell documentation,
including customer documentation on CD-ROM and schematic diagrams.
Contents
Modular Cell Documentation
3-3
Schematic diagrams
3-4
Documentation CD
3-6
Documents of interest
3-8
Selecting a Modular Cell user interface
3-9
How to Choose the Right Interface
3-10
ECP-based interface: Recent Change/Verify screens
3-12
RC/V access manager forms
3-13
Selected RC/V Forms
3-16
...................................................................................................................................................................................................................................
401-703-487
Alcatel-Lucent - Proprietary
3-1
Issue 2, April 2008
See notice on first page
User Interfaces
Overview
ECP-based interface: Craftshell interface and Read-Only Printer

basics
3-19
Craftshell command syntax
3-20
Useful maintenance commands
3-22
Craftshell command syntax changes
3-26
Output messages
3-28
Read-Only Printer
3-30
Non-Volatile Memory
3-31
ECP-Based Interface: Status Display Pages
3-33
Video States of SDP Display
3-34
Status Display Page appearance
3-35
SDP system architecture
3-37
Status Display Pages
3-39
Application processor command line interface
3-43
Application processor architecture
3-44
Access the EMS CLI
3-46
Access TI CLI via OMP
3-48
Access TI CLI via AP (FMM-AP or Alcatel-Lucent CDMA AP)
3-50
The Remote Maintenance Tool (RMT) interface
3-51
RMT operation
3-52
Integrated power software
3-53
PowCom Software
3-54
....................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
3-2
User Interfaces
Modular Cell Documentation

Overview
...................................................................................................................................................................................................................................
Purpose
The Alcatel-Lucent CDMA documentation provides the information support necessary

for the operation and maintenance of a Modular Cell.
The documentation is composed of two document sets:
Modular Cell schematic diagrams that depict component connectivity

Customer documentation on CD-ROM
Contents
Schematic diagrams
3-4
Documentation CD
3-6
Documents of interest
3-8
...................................................................................................................................................................................................................................
401-703-487
3-3
Issue 2, April 2008
User Interfaces
Schematic
diagrams
...................................................................................................................................................................................................................................
Overview
Schematic diagrams (SDs) are multi-page documents that support particular

applications. Of direct interest to maintenance personnel will be the SDs that relate to
cabling and connections.
Schematic diagrams sample
Diagram identification information is located in the lower right corner of all schematic
diagrams, as shown below.
Schematic Drawings
Drawing Size
Sheet Number
Proprietary Information
Issue Number
Product Identification
Schematic
Drawing Number
Coordinates
G
H
6
Layout
All SDs provide an SD number, a sheet number, and an issue number. Coordinates to
items in the SD are provided in the margin.
Additional information includes proprietary information and product names.
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
3-4
User Interfaces
Schematic diagrams
SD sheets
SD sheets are arranged alphabetically from A to H, and contain information as listed in

the following table.
SD
Sheets
Sheet Name
Sheet Contents
Index
Issue date(s), sheet indices to all SD pages
FSs (Functional
Schematics)
Graphic information about the circuit(s)
Apparatus Figures
Component-specific information, such as

Alcatel-Lucent comcodes and manufacturer
numbers
Circuit Notes
Explanation of notes referenced within FSs
Circuit Description
(CD)
Text description of the circuits appearing in

SD-2R603-01 (Note that most SDs do not
contain a CD)
Not used in this SD
Not used in this SD
CADs (Cabling
Diagrams)
Specific interconnection cabling information
BDs (Block
Diagrams)
High-level interconnections between major

units
The SD issue number is located on the top right corner of sheet A1.
In the lower right corner, sheet A1 contains a count of the total number of SD sheets
in the set.
Page designations, such as A1 or B17, are located on the lower right of each sheet.
Important! Schematic diagrams can be ordered in paper format or downloaded
from the Alcatel-Lucent CIC internet web site:
http://www.lucentdocs.com
....................................................................................................................................................................................................................................
401-703-487
3-5
Issue 2, April 2008
User Interfaces
Documentation
CD
...................................................................................................................................................................................................................................
Before you begin
Customer documentation is available on the AUTOPLEX/Wireless CD-ROM or over

the Extranet at (https://wireless.support.lucent.com/documentation). The documentation
is presented on the computer screen in an Acrobat Reader browser.
Description of the display
The documentation CD-ROM when installed displays a pane which gives you the
option to either View the installation notes, Install the Wireless Network Systems
Documentation (Disk 1) or View the Wireless Network Systems Documentation (Disk
1). To access the documentation, use the list of topics to perform which function you
desire.
View the installation notes:
...................................................................................................................................................................................................
Select View the installation Notes to display instructions on installing the

documentation as well as an overview of what software is needed in order to display
the documentation.
...................................................................................................................................................................................................
Select Install Wireless Network Systems Documentation to install the documentation

onto the hard drive of your computer.
Result:The system will display a setup display screen in order to execute the
installation of the documentation.
...................................................................................................................................................................................................
From the Start menu, select Programs-Lucent Technologies. A screen will be displayed
showing the various menu selections of documentation. .
...................................................................................................................................................................................................
In order to search for a specific document, select the search button located in the top
left hand corner of the screen.
...................................................................................................................................................................................................
In order to display from the CD-ROM the selected documentation, select View
Wireless Network Systems Documentation (Disk 1).
Result:The system will prompt you to install Disk 2 and then a menu will be displayed
in which you can select the category and/or search for the particular document of
interest.
E...................................................................................................................................................................................................
ND OF STEPS
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
3-6
User Interfaces
Documentation CD
Wireless documents description of the display
The documentation display is a single-pane layout. To access the documentation, use

the list of displayed in the middle of the screen.
Accessing the display
...................................................................................................................................................................................................
Select a topic from the pane.

...................................................................................................................................................................................................
Select the requested documentation from the group displayed.

Result:The screen displayed has a running list of documents displayed.
...................................................................................................................................................................................................
Select an item in the list to display the corresponding text.

...................................................................................................................................................................................................
Click on the Find button and enter a string into the dialog box to enable a full text
search.
Result:The first occurrences of the string are highlighted on the right side of the
display.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-703-487
3-7
Issue 2, April 2008
User Interfaces
Documents
of interest
...................................................................................................................................................................................................................................
Overview
A technician uses many different documents while maintaining a cell. Some documents
are referred to more often than others.
Document list
The following list contains documents of specific interest to Modular Cell site
technicians.
Content
Document reference
SDPs and Fault Isolation
CDMA Executive Cellular Processor (ECP) Operation, Administration, and Maintenance

Guide, (401-610-160)
Tests and diagnostics
CDMA Cellular Telecommunications Systems System 1000 Cell Site Diagnostic Test
Descriptions, (401-660-101)
Cell Input message formats
Wireless Network Executive Cellular Process

(ECP) Input Messages, (401-610-055)
Cell Output message formats
Wireless Network Executive Cellular Process

(ECP) Output Messages, (401-610-057)
Modular Cell 1.0 - 3.0 OA&M
Alcatel-Lucent CDMA and PCS CDMA Modular

Cell 1.0, 2.0, 3.0 and Compact Modular Cell 3.0
Operation, Administration, and Maintenance,
(401-710-122)
Modular Cell 4.0 OA&M
Alcatel-Lucent CDMA Base Stations - 4.0, 4.0B,

8400, 4400, and 2400 Series Operations,
Administration and Maintenance, (401-703-407)
Translations forms
5E13 and Later Software Releases, (235-080-100)

Located in the5ESS Switch Recent Change
Procedures
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
3-8
User Interfaces
Selecting a Modular Cell user interface

Overview
...................................................................................................................................................................................................................................
Purpose
In order to monitor the status of a cell and control its operation using commands, the
technician will access user interfaces.
Contents
3-10
...................................................................................................................................................................................................................................
401-703-487
3-9
Issue 2, April 2008
User Interfaces
How
to Choose the Right Interface
...................................................................................................................................................................................................................................
Overview
The MSC-based interface uses the AUTOPLEX system commands.

Interface choice
Each interface has advantages and limitations over the other in terms of features,
capabilities, and ease of use. As a result, the choice of the right interface may be
dictated by operating requirements rather than by operators preference.
RMT vs. ECP interfaces
The RMT interface supports a specific set of commands, while the ECP interface
enables both scripted and command line interactions.
RMT-Based interface
The RMT-based interface is an optional, self-contained software package that executes

scripted operation and maintenance routines (macros). It is designed to interact with the
cell offline from the MSC.
The RMT provides two sets of functions:
Connections to the MSC through the Application Processor Cluster (APC) to

monitor the modular cell
MSC emulation to test modular cell health without requiring actual connection to
the MSC (because the RMTs stand-alone operation)
Important! Depending on the version of software, the user must use the
appropriate version of the RMT in order to boot the cell. The RMT 1.50 is no
longer supported for the Modular cell Growth Cabinets. To retrieve the RMT 1.51a
or later software, please contact CommNet for the CD-ROM or download the
software from the NAR web page at: http://emns.lucent.com/install/pc-updates/
index.html.
ECP-Based interface
The craftshell interface and the SDPs are two different ways to seek and act upon
information pertinent to Modular Cell performance.
Although the interface behavior and display are not the same, the information that is
returned is identical in scope. Craftshell results are displayed in real time, while SDP
displays are updated at preset intervals.
Output to both interfaces is recorded on the read-only printer (ROP), which is a
continuous listing of all system activities.
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
3-10
User Interfaces
The functions provided by the ECP interface are as follows:
SDP: This is primarily a GUI. SDPs are specifically designed to provide a snapshot
of the status of a Modular Cell and of its system environment.
Craftshell: The craftshell interface, also referred to as the technician interface (TI)
is exclusively a UNIX-based, command line interface. The craftshell is specifically
designed for command line input and message output. Craftshell commands can be
run from the SDPs.
Read-only printer (ROP): This is exclusively a running report of system activities.
The functions of these interfaces are complementary. In particular, the interpretation of

a cell condition reported by an SDP will often require reference to the ROP to identify
the cause of that condition. For instance, the ROP will indicate what event (for
example, manual command) resulted in a component to be shown on an SDP as being
out of service.
....................................................................................................................................................................................................................................
401-703-487
3-11
Issue 2, April 2008
User Interfaces
ECP-based interface: Recent Change/Verify screens

Overview
...................................................................................................................................................................................................................................
Purpose
Modular Cell configurations are stored in the databases of the ECP, called a
translations database. To modify them, one must interact with the database. This is
done through Recent Change and Verify (RC/V) screens. The craftshell and SDPs do
not affect the operating parameters of a Modular Cell. These parameters are stored in a
database.
Purpose of the RC/V screens
RC/V screens provide the user interface to a Modular Cell database, and are used to
change and check on the configuration of a cell. Some of the changes are
service-affecting.
Contents
3-13
Selected RC/V Forms
3-16
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
3-12
User Interfaces
RC/V
access manager forms
...................................................................................................................................................................................................................................
Forms layout
All ECP RC/V forms share the same look and feel. All database forms utilize the
screen areas shown below.
RC/V Forms
Form Name
User Prompt
Screen Number
Form Fields
Help Message
or System Status
Common elements
All RC/Vforms display the following three essential elements:

1. User prompt - An AUTOPLEX system feature that points you to a field in which
you may enter information
2. RC/V form fields - Placeholders that store and display RC/V information
3. Help message or system status - Context-sensitive text that prompts you to enter a
value in a field or provides system-level information
The common look
Access Manager RC/V forms share the same look and feel, and have the following
characteristics:
Forms are arranged in screens, and each screen contains several fields.
Screen numbers are displayed on the top right corner.
...................................................................................................................................................................................................................................
401-703-487
3-13
Issue 2, April 2008
User Interfaces
Fields are assigned field numbers. Their names and assigned numbers are arranged
in columns on the left of the form, and corresponding data is displayed on the
right.
Position of a given field name, on a given screen or field number, may change
periodically to accommodate different software releases.
Form access procedure
Important! Help is available at any time from any RC/V form screen. To access
the help screens, enter a question mark (?) at the prompt that is displayed at the
bottom of the screen.
Use the following procedure to access an RC/V form, and to change the field values:
...................................................................................................................................................................................................
Type the form name at the prompt. Press Enter.

The system displays the Insert, Review, Update (IRU) form.
...................................................................................................................................................................................................
Select the I option in the IRU form. There are three modes of access to an RC/V
screen.
These are as follows:
1. Insert - Enables entries in fields of the form
2. Review - Enables read-only display of the field values in the form
3. Update - Enables confirmation of inserted data
The system displays the unpopulated form.
Important! The left most option on the Enter field indicates the mode selected in
this step.
...................................................................................................................................................................................................
Some fields need to be populated with required data before the form can display the
contents of the modular cell database. These required fields are indicated by an asterisk
(*).
The system displays the populated form.
...................................................................................................................................................................................................
Change system parameters by filling out the appropriate field. Then exit that form by
typing the < (Shifted comma) key. This returns the display to the IRU form.
...................................................................................................................................................................................................
Select the U option to accept the changes.
....................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
3-14
User Interfaces
The database is updated with the new information.

E...................................................................................................................................................................................................
ND OF STEPS
Reference
For more information on the RC/V forms, refer to the CDMA Wireless Networks
Executive Cellular Processor (ECP) Database Update Manual, (401-610-036).
....................................................................................................................................................................................................................................
401-703-487
3-15
Issue 2, April 2008
User Interfaces
Selected
RC/V Forms
...................................................................................................................................................................................................................................
RC/V forms
The list below shows some of the forms accessed for the Modular Cell.
Screen
Screen Title
Description
apeqp
Application Processor
Equipment
defines the physical DS1/DS0 on the

application processor, the link protocol, and
the far-end point code for the link sets
associated with the application processor
btseqp
CDMA OneBTS
ModCell Assemblage
Equipage
equipage of components and parameters

associated with the Modular Cell 4.0 digital
shelf
cdhfl
CDMA Direct Handoff

Neighbor List
used to populate the directed frequency or

target band class in order to perform directed
semisoft handoffs.
cdhnl
CDMA Directed
Handoff Neighbor List
Form
specifies a list of neighbor cell candidates for

inter-frequency handoffs and hand downs
cdmeqp
CDMA Digital Module

Equipage
equipage of components and parameters

associated with a CDMA Digital Module
(CDM) of CDMA Modular Cell 1.0/2.0/3.0
cell2
Basic Cell Equipage
number of radios, cell status, location

equipped faces, overhead stream information,
system codes, etc.
cell3g
3G1X Cell Equipage
Operational Fault Detection (OFD), Cell and

Cell Site configuration, and Power Control
(PC) for voice and data-related fields
ceqface
Modular Cell Operating

Parameters
cell equipage and multiple component

assignment
ceqface3g
Cell Equipage Face for

3G
form should be viewed as an adjunct to the

existing equipment forms (i.e.
ceqcom2/crcseq/cmodeqp)
cgsa
Cellular Geographic
Service Area Form
information for the system on a CGSA basis,

for example, roamer information, combined
paging and access, and the list of cell sites.
cmodeqp
CDMA Modular Cell

Equipage
equipage of TXAMPs, RXAMPs, RF Tests,

TFUs, TDUs and user alarms for all versions
of the Modular Cell
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
3-16
User Interfaces
Selected RC/V Forms
Screen
Screen Title
Description
cmodpptm
CDMA Modular Cell

RCS Form
used to enter Alcatel-Lucent CDMA Modular

Cell packet pipe trunk group member
information
crcseq
Specific Modular Cell

Equipage
populate Alcatel-Lucent CDMA RCS (Cell)

equipment configurations
ecp
Executive Cellular
Processor
information used by the system to process

calls, make service measurements, and provide
Automatic Message Accounting (AMA)
information
ecp3g
Executive Cellular
Processor for 3G
used for 3g data and 3g voice, there are also

feature release fields which can be turned on
and off.
fci
Face Code Information

Form
information used by the cell site in the handoff

function based on (1) Server Group (SG), (2)
Antenna Face Number (also known as Physical
Antenna Face or PAF)
sub
Subscriber and Feature

Information
used to populate the individual mobile

information and 3G data, allows for mobile to
call other mobiles
RC/V field to differentiate CDMA cell type
On the CMODEQP form there exists a field to distinguish between cell type. This
parameter specifies the cell configuration since this form supports both CDMA
Modular Cell and Modular Cell 4.0.
flex_mod indicates a Stand-Alone Modular Cell

1bts_mod indicates a Stand-Alone Modular Cell 4.0
mixed_frm indicates a Mixed Frame Configuration
New fields in R21 for Power Control
This feature adds a more complete set of Power Control translations to help in the
performance tuning of Power Control and Call Processing. In particular, RC4
parameters will be decoupled from the RC3 Power Control parameters. This feature
also provides the F-FCH and F-SCH to have a different number of active set members.
....................................................................................................................................................................................................................................
401-703-487
3-17
Issue 2, April 2008
User Interfaces
Selected RC/V Forms
The forward link channel elements can be configured as any of the following channels:
pilot, page, sync, quick paging, fundamental, and supplemental. Reverse link channel
elements can be configured as any of the following channels: fundamental,
supplemental, and access. In addition, the signal processing for PSTD is implemented
in both units.
A change to the Maximum Number of Active Set Pilots translation or to the
Maximum Number of Active Set Pilots for 3G-1X Data Call in a sector shall apply
only to those corresponding calls that add that sectors pilot to the calls Active Set
after the translation change has taken place, or to calls that begin after the translation
change has taken place.
Reference
For more information on the RC/V forms, refer to the CDMA Wireless Networks
Executive Cellular Processor (ECP) Database Update Manual, (401-610-036).
....................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
3-18
User Interfaces
ECP-based interface: Craftshell interface and

Read-Only Printer basics
Overview
...................................................................................................................................................................................................................................
Purpose
The craftshell provides the most flexible means to input commands and to retrieve
output messages from a Modular Cell.
Standard craftshell
Use craftshell commands to perform the following tasks:
Identify operational status

Remove and restore a unit from service
Diagnose a unit
Download Non-Volatile Memory
Stop a command
Initialize a site
Reference
More information on the craftshell can be found in Wireless Networks Executive

Cellular Processor (ECP) Input Messages, (401-610-055).Wireless Networks Executive
Cellular Processor (ECP) Output Messages, (401-610-057)
Contents
3-20
3-22
3-26
Output messages
3-28
Read-Only Printer
3-30
Non-Volatile Memory
3-31
...................................................................................................................................................................................................................................
401-703-487
3-19
Issue 2, April 2008
User Interfaces
Craftshell
command syntax
...................................................................................................................................................................................................................................
Craftshell syntax
Entering commands at the craftshell requires attention to precise syntax.

Outline of craftshell structure
A sample command line and explanations of the various elements are shown below.
Craftshell Command Syntax

Structure: 4 fields
action: identification;options:data
Action: command
Identification: cell and object
Options (if applicable)
Data (if applicable)
Example
dgn: cell 21,cdm 1, tfu 1;ucl:tlp

-
Craftshell syntax
Craftshell commands follow strict syntax, punctuation, spacing (space before

numerals), and capitalization rules. The commands share a common structure of four
elements:
1. Action The command name followed by a colon (:)
2. Identification:
target The cell affected by the command
object (if applicable) The Modular Cell unit affected by the command
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
3-20
User Interfaces
For example:
The target cell is identified cell #, with a space between the word cell and
the cell number.
The object is identified cdm #, with a space between the word cdm and the
cdm number.
A comma between elements
3. Options (if applicable) Options associated with the command preceded by a
colon (:) or a semicolon (;)
4. Data (if applicable), for example, tlp, preceded by a :
Reference
More information on the craftshell can be found in Wireless Networks Executive

Cellular Processor (ECP) Input Messages, (401-610-055).Wireless Networks Executive
Cellular Processor (ECP) Output Messages, (401-610-057)
....................................................................................................................................................................................................................................
401-703-487
3-21
Issue 2, April 2008
User Interfaces
Useful
maintenance commands
...................................................................................................................................................................................................................................
Overview
Some commands are used more frequently than other commands. This section is not
intended to include only those commands experience has shown are necessary to
maintain a cell site.
Remove - rmv
Remove is a maintenance action that changes the state of a maintenance unit from
active to out-of-service. It schedules an event or process to place the specified
maintenance unit to out-of-service assuming that it is NOT busy (in active state and
currently performing its intended purpose), such as a CE supporting an active call.
Conditions that will cause the conditional remove to abort with no action taken are
described as follows:
If placing the unit out-of-service would result in exceeding the out-of-service

threshold limit for that type of unit, the conditional remove action is not permitted.
If the CDM OOS threshold is exceeded. This limit is to prevent a large percentage
of CDMs being knocked OOS when performing CDM diagnostics.
If the unconditional remove action is targeted for a busy CMU, the remove is deferred
for up to 5 minutes. If the unit is still busy after 5 minutes, MRA drops the calls and
removes the unit from service.
Unconditional rmv
CAUTION
Service Affecting
The lack of restrictions associated with an unconditional remove may be

service-affecting.
Restore - rst
Restore is a maintenance action that brings a unit back to service. The restrictions
associated with a remove are also associated with a restore.
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
3-22
User Interfaces
Conditional
The conditional restore maintenance action changes the state of a maintenance unit
from out-of-service to active. It schedules an event or process to restore the specified
maintenance unit after the unit passes a diagnostic test. If the unit fails the diagnostic
test, the conditional restore aborts. The failed unit remains in the out-of-service state.
Unconditional
Similar to a conditional restore command the first step in an unconditional restore

maintenance action is the automatic execution of an unconditional remove.
Conditional vs. Unconditional Restore
The primary difference between a conditional and an unconditional restore is that the
conditional restore runs a diagnostic first, while the unconditional does not.
Conditions Applying to Restore Requests
The technician must be aware of the following conditions pertaining to conditional and
unconditional restore requests:
For data links (DLs) a conditional restore request reverts to unconditional if there is
no link currently in-service; no diagnostic test is run.
No action is performed if an unconditional restore request is made on the currently
in-service link.
Cannot restore some units unless the parent is in service.
Stop - stop
Stop is a maintenance action that stops a maintenance activity on a maintenance unit.

If the maintenance activity request is still in the job queue, MRA removes the request
from the queue. If the maintenance activity is running, MRA aborts the activity.
Diagnose - dgn
Diagnose performs diagnostic tests on a unit in the out-of-service state.

If the unit is in an active state, the MRA puts that unit in the OOS state and then
executes the diagnostics. The unit is left in the OOS state.
Configuration request - cfr
CFR is a tool used to perform Radio Frequency (RF) testing at a cell site. The CFR
command is invoked by the technician from the ECP.
The usual sequence of CFR commands involve starting the CFR session, configuring
one or more MCRs into the session, configuring a number of traffic CEs into the
session for each MCR, turning on the transmitter, and stopping the CFR session.
....................................................................................................................................................................................................................................
401-703-487
3-23
Issue 2, April 2008
User Interfaces
Operational Status - op
The Operational Status maintenance action (OP) determines the status (state) of a
maintenance unit.
That is, the Maintenance Request Administrator (MRA) reads the recorded status from
the equipment status table and forwards the status to the Access Manager.
In addition, MRA automatically reports the maintenance status of the equipment to the
Access Manager whenever the status changes. A status display page is refreshed with
new maintenance status every 15 seconds.
Inhibit tasks - inh
Inhibits a specific software or hardware action at specified cell site(s). This command
prevents the execution of various commands including FT, OFD PG, PHMON,
RTDIAG, SCSM, and others. This command can also inhibit CP (call processing) with
the effect of putting the cell in a maintenance/growth state and turning off the
transmitters with no calls active.
Allow tasks - alw
Allows a specific software or hardware action at specified cell site(s). This command
allows the actions inhibited by inh.
Out-of-service threshold
System considerations place threshold limits to the number of CDMA channel elements
(CEs) that can be out-of-service. That number is no longer specified in the RC/V form
cell2 for Modular Cell 4.0.
For OOS limits, Modular Cell 4.0 uses the 3G-1X OOS Limit fields in the ecp3g and
cell3g forms. Modular Cell 4.0 does not use the Total OOS limit fields. The default
3G-1X OOS limit is 100 for major alarms and 49 for minor alarms.
Camp-on
Many of the maintenance commands use a procedure called camp-on. Camp-on

procedures are used to give stable calls a chance to finish normally before drastic
action is taken on a maintenance object (for example, removal from service). Two
different kinds of camp-on procedures are supported. One is the standard 5-minute
camp-on. The other is the Extended Time Camp-on (EC) of 30 minutes. This
extended camp-on period applies only to manually-requested unconditional removes.
....................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
3-24
User Interfaces
References
For more information on the remove maintenance action, refer to the RMV CELL
commands section in Wireless Networks Executive Cellular Processor (ECP) Input
Messages, (401-610-055) and Wireless Networks Executive Cellular Processor (ECP)
Output Messages, (401-610-057).
....................................................................................................................................................................................................................................
401-703-487
3-25
Issue 2, April 2008
User Interfaces
Craftshell
command syntax changes
...................................................................................................................................................................................................................................
Command changes
The following table lists the changes made to craftshell commands for Modular Cell
4.0.
Input Command
Changes
ALW:CELL-FT
Increased range for CCU and CE.

Support automatically run antenna tests for TDU.
CFR:CELL-MULTI, [XMITC]
New parameters for specifying carrier number.

Carrier is an optional parameter and defaults to all
carriers for CONFIG/CDMADPC commands,
carrier is a required parameter for ADDCE/DELCE
commands.
DGN:CELL-CDM, [CRC]
[CCU][CBR]
Increased range for CBR and CCU.
EXC:CELL-FT
Support manually run antenna tests for TDU.
INH:CELL-FT
Support automatically run antenna tests for TDU.
MOVE:CELL-OC
Increased CE range.
MOVE:DN-CELL
MOVE:MIN-CELL
MOVE:IMSI-CELL
Increased CE and CCU range.
OP:CELL
OP:CELL-CDM
Increased range for CBR, CCU
OP:CELL-CDM-CBR
OP:CELL-CDM-CCU
OP:CELL-OC
New input command to request Overhead channel

status.
OP:CELL-TDU
New command.
OP:CELL-TXAMP
Generic name TXAMP for all transmit amps.
RMV:CELL-CDM[CRC][CCU][CBR]
Increased ranges for CBR and CCU.
STOP:CELL
Increased CCU, CBR, TDU, and TXAMP range.

ULAM name changed to TXAMP.
STOP:CELL a, TDU Supported for OneBTS
Modular Cell only.
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
3-26
User Interfaces
Input Command
Changes
STOP:EXC;CELL-FT
Support manually run antenna tests for TDU.
STOP:MOVE-CELL
Increased CBR, CCU, CE range.
....................................................................................................................................................................................................................................
401-703-487
3-27
Issue 2, April 2008
User Interfaces
Output
messages
...................................................................................................................................................................................................................................
Overview
Output messages are formatted system responses to technician commands or events in

the system.
Craftshell Output Sample
An example of output from the DGN craftshell command and explanations of the
fields are shown below.
Output Messages
Command issued
M 52 DGN:CELL 21 CDM 1 TFU 1 ATP

05/14/98
08:52:45
#034389
M 52 REPT:CELL 21 CDM 1 TFU 1 OOS. MANUAL. RMVD
05/14/98
08:52:45
#034390
Date and Time

exc:cell 96,cdm 1,ft pl IP all specified cells ACT
M 51 EXC:CELL 96 CDM 1 FT PL, STARTED
M 53 EXC:CELL 96 FT PL, COMPLETED
CDM 1 PL COMPLETED
ALL TESTS PASSED
CDM 1 PL CARRIER 1 COMPLETED
ALL TESTS PASSED
PILOT LEVEL: ACTL = -50.4 dBm EXP = -50.2 dBm
Message Body
M 51 EXC:CELL 95 FT PL, COMPLETED

CDM 1 PL COMPLETED
SOME TESTS FAILED
CDM 1 PL CARRIER 1 COMPLETED
OUT OF RANGE
PILOT LEVEL: ACTL = -54.6 dBm EXP = 23.8 dBm
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
3-28
User Interfaces
Output messages
Output messages syntax
Output messages result from a technician request or an event in the system (for
example, alarm). Output messages include the following fields:
Priority: Alarm (*C = Critical, ** = Major, * = Minor); M = Manual, A =

Automatically generated. This field is blank for informational messages.
Abbreviated time, message body, date, sequence number
Reference
Output messages are explained in detail in the Wireless Networks Executive Cellular
Procsssor (ECP) Input Messages, (401-610-055).
Wireless Networks Executive Cellular Processor (ECP) Output Messages,
(401-610-057)
....................................................................................................................................................................................................................................
401-703-487
3-29
Issue 2, April 2008
User Interfaces
Read-Only
Printer
...................................................................................................................................................................................................................................
Sample ROP output
A selected portion of the ROP output is shown below. The output is shown as a sample
of the messages displayed.
M 05 RST:CELL 169 CDM 2 CRC, COMPLETED, ALL TESTS PASSED10/22/96
14:05:20 #084038
* 05 OP:CELL 169, CDM 3, CBR 3, ACTIVE10/22/96 14:05:20 #084039
Description
The read-only printer (ROP) provides a continuous report of system activities. It can be
configured through the use of a Selectable Cell Site Messaging (SCSM) command to
only display data related to the operation of a specific Modular Cell, or data related to
a group of Modular Cells.
Appearance
The ROP appears as a craftshell output.

Report types
There are two types of output reports: solicited and spontaneous. Solicited reports are
generated in response to the commands entered by the technician. Spontaneous reports
are generated without any input from the technician; they are initiated automatically by
system events or conditions. An example of a spontaneous report is the reporting of a
cell site hardware error and corresponding automatic recovery action.
Report access
The Hardware Error Handler (HEH) and CP Fail messages are printed at the ROP and
may reflect problems not displayed on the SDPs. The ROP printouts should be
reviewed at least once a day for CDMA-related messages. To make this easier, tools
(such as selective cell site messaging) allow these messages to be filtered from the
normal stream of ROP messages. These tools will also analyze the messages, and sort
and summarize them by specific equipment unit.
Reference
Format and meaning of ROP output are explained in.Wireless Networks Executive
Cellular Processor (ECP) Input Messages, (401-610-055)
Wireless Networks Executive Cellular Processor (ECP) Output Messages,
(401-610-057).
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
3-30
User Interfaces
Non-Volatile
Memory
...................................................................................................................................................................................................................................
Overview
The NVM Update requirements in this section are specific to functionality associated
with the MSC. NVM Update (otherwise known as NVM download or software
download) is an important capability relating to Alcatel-Lucent CDMA System 1000
configuration management. NVM is used for local storage of software images executed
by Modular Cell processors.
Advantages of cell site storage
The fact that these images are stored locally in non-volatile form allows a Modular
Cell to be booted faster than if software were to be downloaded from the application
processor as part of each Modular Cell initialization event. This strategy helps
minimize not only overall cell site downtime but also downtime, on an individual
carrier basis.
Downtime is further minimized by virtue of the fact that NVM is used only for storage
purposes, while ordinary RAM is used for the actual execution of software. In other
words, a given CDM processors software image may be updated in terms of a version
stored in NVM, while the current version of that processors software executes in
RAM.
Download an executable image to NVM
An AUTOPLEX System 1000 software generic consists of, among other things, a
packaged set of executable images for both an RCS and its corresponding cell site
equipment (for the sake of this discussion, cell site equipment refers to Modular Cell
equipment). These generics reside on application processor disk. A TI input command
(SEND:CELL) initiates the transfer of a specified generic (i.e., the cell site
executables) from the application processor to the cell over a DS0 Signaling Link via
FTP. (The RCS responds to the TI input command by sending a message to the target
URC, which prompts that URC to initiate the FTP session.)
In the case of a duplex application processor configuration, downloading takes place
over the spare Signaling Link (call processing is thus not affected, and the target URC
is able to remain in service).
In the case of a simplex application processor configuration, downloading takes place
over the only available Signaling Link which, of course, is also used by call processing
and all other CDM OA&M activities, and there is contention for that downstream DS0.
Because software downloading is given a lower priority than call processing (i.e., the
FTPs TCP/IP connection operates at a lower priority than the higher-level LAPD
connection), the only way to reliably minimize the download interval is by first
removing all calls from the target URC.
...................................................................................................................................................................................................................................
401-703-487
3-31
Issue 2, April 2008
User Interfaces
Non-Volatile Memory
Cell site storage
Within a target URC, the downloaded executables are stored in a special NVM device
called the Flash File System (FFS). The FFS device mimics a hard disk, and in doing
so supports basic file I/O capabilities (open/close, read/write, compress/uncompress,
create/delete directory, etc.). These FFS capabilities allow for some degree of
sophistication especially in terms of economy in the way software images are
maintained in NVM, on the basis of not only whole generics but also selective portions
of generics.
....................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
3-32
User Interfaces
ECP-Based Interface: Status Display Pages

Overview
...................................................................................................................................................................................................................................
Purpose
To access and/or view a Modular Cells operating condition, utilize the Status Display
Pages (SDPs). SDPs present the user with pre programmed input (command structures)
scenarios.
Reference
More information on the SDPs can be found in Wireless Networks Executive Cellular
Processor (ECP) - Operation, Administration, and Maintenance Guide, (401-610-160).
Contents
Video States of SDP Display
3-34
3-35
3-37
3-39
...................................................................................................................................................................................................................................
401-703-487
3-33
Issue 2, April 2008
User Interfaces
Video
States of SDP Display
...................................................................................................................................................................................................................................
Samples of video state color coding
The most common SDP video states and their colors are shown below.
Top 10 SDP Video States

White on red steady: CRITICAL
Critical
White on red steady: Major
MAJOR
Black on yellow steady:

Black on red steady:
INDT
Indeterminate
oos
O.O.S.
MINOR
White on red steady: Minor
Black on purple steady: Unavail.

unav
<none>
Black on green steady: Normal
White on red flashing: Alarm

alarm
act
Black on green steady: Active
White on red steady:
Trouble
trbl
Full listing of SDP video states: 401-610-160
Color scheme
In the CDMA Modular Cell, the color red on an SDP generally signifies an abnormal
condition; the color green denotes normalcy. Other background colors are used to
signify specific conditions that may or may not require attention.
Reference
For more information on SDPs, refer to Wireless Networks Executive Cellular

Processor (ECP) - Operation, Administration, and Maintenance Guide, (401-610-160).
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
3-34
User Interfaces
Status
Display Page appearance
...................................................................................................................................................................................................................................
Overview
SDPs provide a user-friendly tool to monitor the status of a Modular Cell, using a
consistent display format.
Sample of SDP display
Shown below is a sample of the 2131 SDP that provides Modular Cell equipment
status.
Header area
First line - ECP location, generic release, terminal ID, date, time, and time
zone
Second and third lines - system status
Command entry line (CMD<) for poke commands
Page contents area
Scrolling system response area/craftshell area
...................................................................................................................................................................................................................................
401-703-487
3-35
Issue 2, April 2008
User Interfaces
Information Displayed on SDPs
SDPs provide a graphical view of the Modular Cell site status. Use SDPs to view the
following:
Monitor all major component groups.

Obtain snapshot views of system and alarms.
SDP usefulness
SDPs show the technician/operator the inner workings of the modular cell system. The
SDPs allow the technician to do the following:
View system status

Enter commands
Receive system responses
The commands entered by the technician/operator offer the ability to communicate

detailed and specific instructions to any of the modular cell sites serving the ECP. If
the ECP receives a fault from any modular cell site in the network, that fault is
graphically indicated using colors to indicate levels of severity. While the fault is in
progress, the technician invokes one or more SDPs to further isolate the modular cell
site that communicated the fault condition.
For more information on the video states, see Video States of SDP Display (p. 3-34).
Modes of interaction
Two modes of interaction are available to the technician:
Scripted poke commands on the command line

Calls to the craftshell in the bottom window
The valid poke commands allowed on a given page are listed in a matrix format, each
row corresponding to the unit that can be poked, and the actions that can be
performed on that unit.
It is possible to toggle between the command line and craftshell prompt. Actual
keystrokes for this operation depend on laptop settings.
System delays
As displays are updated at preset intervals, there may be a delay between completion
of a command and its acknowledgment on the SDP.
....................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
3-36
User Interfaces
SDP
system architecture
...................................................................................................................................................................................................................................
Overview
SDPs, sometimes referred to as cartoon pages, graphically represent the hardware and
software subsystems of the Modular Cell site and of the various components of the
MSC.
Important! Prior to Release 18.0, SDP 2139 displayed packet pipe information on
the form. For Release 18.0 and higher, the SDP 2139 no longer supports packet
pipe information, just CMU information. For more information regarding the
Unrestricted access to all URC PPs for each CMU, see Universal Radio Controller
(URC) (p. 1-48).
SDP links diagram
SDPs are linked according to a hierarchy as outlined below. The figure shows the links
between the more common pages used with Modular Cells, and the information
associations between pages. The highlighted pages have screen components unique to
the Alcatel-Lucent CDMA Modular Cell.
2100
2100
Index
Index
TRUNK
TRUNKAlarm
Alarm
CELL
CELLAlarm
Alarm
2120
2120
APX
APX System
System Status
Status
2150
2150
TRKGRP
TRKGRP
2151
2151
TRKGRP
TRKGRPStatus
Status
2130
2130
Cell
Status
Cell Status Summary
Summary
2121
2121
System
Equipage
System Equipage Summary
Summary
2135
2135
LC/SU/BC
LC/SU/BC
2136
2136
AMP/GPS/TFU
AMP/GPS/TFU
2131
2131
Cell
Equipment
Cell Equipment Status
Status
2137
2137
OTU/LMT
OTU/LMT
2138
2138
CDMA
CDMA
DCS Trouble
Cell Trouble
2152
2152
TRKGRP
TRKGRP
CDM Trouble
2139
2139
CCU
CCU
CMU
2154
2154
Alarms
Alarms
...................................................................................................................................................................................................................................
401-703-487
3-37
Issue 2, April 2008
User Interfaces
SDPs used with the CDMA Modular Cell
There are dozens of SDPs that are available at the Maintenance CRT ( MCRT) for
analyzing equipment. To analyze Alcatel-Lucent CDMA Modular Cell performance, use
the following SDPs:
101 - System Index Page

2100 - APX Index Page
2120 - APX System Status
2121 - System Equipage Summary
2130 - Cell Status Summary
2131 - Cell Equipment Status
2132 - Cell Software Status
2136 - Cell AMP/GPS/CTU Status
2138 - CDMA Equipment Status Page
2139 - CMU Status Page
2150 - TRKGRP Summary Page
2152 - DCS TRKGRP Status Page
2154 - Trunk Group Alarms
....................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
3-38
User Interfaces
Status
Display Pages
...................................................................................................................................................................................................................................
2136 - Cell Amplifier Status
The 2136 - Cell Amplifier Status page displays the summary state of the transmit
amplifier and receiver equipment at a CDMA Modular Cell. Overall Cell Summary
status, TFU Status, GPS Status, and Oscillator Flywheel Status are indicated on this
SDP.
The following graphic shows the first screen of the CDMA BTS2400 SDP 2136.
The following graphic shows the second screen of the CDMA SDP 2136. This screen
shows the TDU and Antenna Functional Test status.
...................................................................................................................................................................................................................................
401-703-487
3-39
Issue 2, April 2008
User Interfaces
2138 - Alcatel-Lucent CDMA Modular Equipment Status
The 2138 page shows the status of the following components.
CRC
CBR
Serving DCS
Packet Pipe Trunk Group
The Global Positioning System (GPS)
Transmit AMP Alarm
Receive AMP Alarm
Diversity Imbalance status
The following graphic shows the first screen of the CDMA Modular Cell SDP 2138.
The first screen shows M# 1-6 and the second screen shows M#s greater than 7.
....................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
3-40
User Interfaces
2139 - CDMA Modular Cell CRC CCU Status
The 2139 page shows the following information:
Personality of CE
Physical Antenna Face (PAF) associated with overhead or busy traffic CE
CDMA carrier number associated with PAF
Blocking (if any) of the CDMA cluster/packet pipe.
The CDMA SDP 2139 contains additional screens to list the additional CEs on the
CCU.
....................................................................................................................................................................................................................................
401-703-487
3-41
Issue 2, April 2008
User Interfaces
Reference
Executive Cellular Processor (ECP) Operations, Administration and Maintenance

Guide, (401-610-160).
....................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
3-42
User Interfaces
Application processor command line interface

Overview
...................................................................................................................................................................................................................................
Purpose
This section introduces the Application Processor (AP) Command Line Interface (CLI).
Contents
3-44
Access the EMS CLI
3-46
3-48
Access TI CLI via AP (FMM-AP or Alcatel-Lucent CDMA AP)
3-50
...................................................................................................................................................................................................................................
401-703-487
3-43
Issue 2, April 2008
User Interfaces
Application
processor architecture
...................................................................................................................................................................................................................................
Application processor description
An application processor is a central processing unit (CPU) that provides generic

computing facilities to host a wide range of applications in a Alcatel-Lucent CDMA
wireless network. The application processor perform the call-processing and underlying
OA&M functions for the Microcells and Modular Cells in a CDMA network. Pairs of
application processor host the Radio Cluster Server (RCS) application for CDMA
Microcells and Modular Cells. The application processor provide an integrated
high-availability hardware and software platform that offers increased reliability,
availability, and maintainability for its subtending network elements.
Application Processor Architecture

Modular
Cell
5ESS DCS
signaling
Modular
Cell
signaling
RCS
AP
OMP
AP
traffic
RCS
ECP
Mobile Switching
Center (MSC)
DS1s
Modular
Cell
PCS
Minicell
Series II
CL5610 L3 23
9/15/2000
Lucent Technologies - Proprietary
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
3-44
User Interfaces
Alcatel-Lucent CDMA Element Management System Interface
The Alcatel-Lucent CDMA Element Management System command interfaces are:
Graphical User Interface (EMS GUI)

Command Line Interface (EMS CLI)
Technician Interface Command Line Interface (TI CLI)
The Alcatel-Lucent CDMA Management System now implements two types of CLIs.
EMS CLI is used for Alcatel-Lucent CDMA AP Processor Administrator. It is a
separate set of input commands for AP, DS1, RCS, and all applications in the AP. CLI
is run on Alcatel-Lucent CDMA AP and MM-AP.
TI CLI is a Alcatel-Lucent CDMA Mobility Manager feature that moves input
command interface handling from the ECP to the MM-AP. TI CLI can be run on
MM-AP or OMP and it improves the response time over the existing CLI. It
centralizes security, logins, and provides consistency of user interface. Prior to TI
feature activation, these input commands could only be run on ECP Craftshell
interface.
Element Management System (EMS) GUI
The preferred way to execute the commands is from the EMS GUI. The EMS CLI is
intended to be used primarily when you want to create a script that will issue a series
of individual commands sequentially when the EMS GUI is unavailable. For example,
in the event you are using an ASCII terminal rather than an X-terminal.
....................................................................................................................................................................................................................................
401-703-487
3-45
Issue 2, April 2008
User Interfaces
Access
the EMS CLI
...................................................................................................................................................................................................................................
Overview
The EMS CLI interface provides access to RCS instances running on the application
processor. This interface is similar in appearance to the craftshell.
To access the EMS CLI from OMP menus
To launch the EMS CLI from OMP menus, perform the following procedure:
...................................................................................................................................................................................................
From an OMP X Terminal, launch the AUTOPLEX(R) OMP Technician menu.

...................................................................................................................................................................................................
Select the Alcatel-Lucent CDMA Element Management System menu item.

...................................................................................................................................................................................................
Select the EMS Command Line Interface menu item.

An EMS CLI session is invoked in a new console window and an EMS CLI prompt
(and session number) is displayed.
E...................................................................................................................................................................................................
ND OF STEPS
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
3-46
User Interfaces
Access the EMS CLI
To script application processor OA&M CLI commands
The EMS CLI and application processor CLI allow you to create scripts to execute sets
of individual commands sequentially. Commands that normally need a confirmation
response during a CLI session (that is, when you issue one CLI command from the
UNIX shell) do not require a confirmation in script mode. For details about how to
create EMS CLI scripts, refer to the Element Management System (EMS) Users Guide,
(401-710-110).
Reference
For more information on the Application Processor, refer to Application Processor

Cluster (APC) Operation, Administration, and Maintenance (OA&M), (401-710-101)
and Wireless Networks Mobility Manager Application Processor Cluster (MM-APC)
Operation, Administration, and Maintenance, (401-710-201). The associated course is
the Alcatel-Lucent CDMA Wireless Networks Application Processor Cluster OA&M,
(CL5100).
....................................................................................................................................................................................................................................
401-703-487
3-47
Issue 2, April 2008
User Interfaces
Access
TI CLI via OMP
...................................................................................................................................................................................................................................
Purpose
Use this procedure to access TI CLI via the OMP menu or OMP shell when the
FMM-TI feature is enabled.
Before you begin
Before accessing TI CLI, make sure of the following:
User is part of the OMP user group, craftsh.

FMM-ROP feature is enabled.
Related documentation
For more information on the OMP user group, craftsh, see Operations and
Management Platform (OMP-FX) Operations, Administration, and Maintenance
(OA&M), (401-662-102) and Mobility Manager Technician Interface Implementation,
(401-710-210).
Steps
Perform the following procedure to access the TI CLI:

...................................................................................................................................................................................................
Login as root to the OMP.

Result:The OMP menu displays.
...................................................................................................................................................................................................
Select Miscellaneous Applications.

...................................................................................................................................................................................................
Access TICLI by doing one of two ways:

1. Select TICLI Access.
2. Select OMP Shell and access TI CLI by entering
TICLI
See figure below.
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
3-48
User Interfaces
Result: The TICLI> prompt is displayed.

E...................................................................................................................................................................................................
ND OF STEPS
Close out TICLI sessions
To close an open TICLI session, press [CTRL-D] or [CTRL-C].

Important! This closes one open TICLI session at a time. For example, if you have
three sessions open and you do a [CTRL-D] or [CTRL-C] on just one, the remaining two
sessions continue to run.
....................................................................................................................................................................................................................................
401-703-487
3-49
Issue 2, April 2008
User Interfaces
Access
TI CLI via AP (FMM-AP or Alcatel-Lucent CDMA AP)
...................................................................................................................................................................................................................................
Purpose
Use this procedure to access TICLI on any AP.

Access TICLI
The way to access the TI CLI is via the AP.

Before you begin
Before accessing TICLI, make sure of the following:
FMM-ROP feature is enabled.

Steps-Acess TICLI via AP

...................................................................................................................................................................................................
From the OMP terminal, bring up an OMP menu window.

Result: The OMP menu is displayed.
...................................................................................................................................................................................................
Access TICLI by doing one of two ways:

1. Select Flexent (TM) AP Access:
a. Select <Frame x>.
b. Select <APx (apxx) UNIX Shell>.
c. Login to AP by entering username and password.
d. At the <apxx> prompt, enter TICLI.
2. Select Miscellaneous Applications then OMP Shell:
a. At the OMP shell, login as root to the AP by entering rlogin <apname> -l root
b. At the ap<xx> prompt, access TICLI by entering TICLI
E...................................................................................................................................................................................................
ND OF STEPS
Close out TICLI session
To close an open TICLI session, press [CTRL-D] or [CTRL-C].

Important! This closes one open TICLI session at a time. For example, if you
have three sessions open and you do a [CTRL-D] or [CTRL-C] on just one, the
remaining two session continue to run.
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
3-50
User Interfaces
The Remote Maintenance Tool (RMT) interface

Overview
...................................................................................................................................................................................................................................
Purpose
This section introduces the Remote Maintenance Tool.

Description
The RMT-based diagnostics and testing mode is designed to facilitate the performance
of maintenance tasks through a point-and-click graphical interface.
The RMT is connected to the modular cell through the Maintenance Test port located
on the PIM. That port is accessible through a connector in the Remote Maintenance
Panel.
Contents
RMT operation
3-52
...................................................................................................................................................................................................................................
401-703-487
3-51
Issue 2, April 2008
User Interfaces
RMT
operation
...................................................................................................................................................................................................................................
Functions supported by the RMT
Access the task bar to perform the following functions supported by the RMT:
Configuration of the modular cell

Download of software
Communication control
Modular Cell equipage inventory
Testing
Status display
Report generation
Security
Booting the cell
To select follow-up actions and/or the element on which a task is to be performed, use
the drop-down menus.
Tool and information sources
The RMT may be obtained through Alcatel-Lucent CIC.

The documentation support is provided by Commnet.
Detailed procedure using the RMT are documented in Alcatel-Lucents Installation
Engineering handbooks.
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
3-52
User Interfaces
Integrated power software

Overview
...................................................................................................................................................................................................................................
Purpose
This section introduces the software specific to the power supply rectifiers. Read the
rectifier manual for more information.
Contents
PowCom Software
3-54
...................................................................................................................................................................................................................................
401-703-487
3-53
Issue 2, April 2008
User Interfaces
PowCom
Software
...................................................................................................................................................................................................................................
Ordering the software
Access to the power system via the RS-232 port requires PowCom Software and User
Documentation available from the Alcatel-Lucent customer information center. The
order number is 300630241, PowCom Software for CDMA Modular Cell Products PowCom Software and User Documentation.
Description
This software has extensive capabilities beyond the requirements of the Alcatel-Lucent
CDMA products. Therefore, not all of the features are utilized in this application.
In addition, the alarm relay assignments and system setting have been optimized to
work with the Mobility Solutions products.
PowCom Software Main Display Page
The following figure shows the PowCom Software Main Display Page. This figure
shows the main display and the alarm relay assignments for the 3.0 and 4.0 Modular
Cell applications.
Alarm relay 1
Power Major
Alarm relay 2
Power Minor
Alarm relay 3
AC Fail
Alarm relay 4
Fuse Fail
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
3-54
User Interfaces
PowCom Software
Alarm relay 5
Battery on Discharge 1
Alarm relay 6
Battery on Discharge 2
Alarm relay 7 through 12
not equipped.
Important! These settings must not be changed without the approval of

Alcatel-Lucent Technical Support.
Power System Default Parameters Display
The following figure shows the system parameters setting page. The factory default
settings for the 3.0 and 4.0 Modular Cell are displayed. These settings are optimized
for Alcatel-Lucent use and may not match what is depicted in the PowCom Software
User Document provided with the software.
....................................................................................................................................................................................................................................
401-703-487
3-55
Issue 2, April 2008
F eatures
4
Overview
...................................................................................................................................................................................................................................
Purpose
The following Chapter contains information regarding features which are provided for
the system. These features will be indicated by the release of the software.
Contents
Automated Neighbor Selection for Neighbor Cells in Co-location
Partnership
4-3
Shared Equipment Status Display for 1xEV-DO CDMA OneBTS

Modular Cell 4.0
4-7
Power Throttling of PHPAM (P2PAM) and CHPAM (C2PAM) Amplifiers
4-9
Support of both IS-95 and IS-2000 (Rev. 0 and A) Overhead Channels

on the same carrier
4-14
IOS BSC - Support for Access Handoff, Access Probe Handoff, and
Access Entry Handoff
4-15
EV-DO Cell OA&M Shared Indicators
4-19
IP Backhaul
4-24
Support for Subnet ID
4-27
Inter-band idle mode load balancing
4-29
Enhanced Reverse Link Monitoring - Service Measurements
4-30
Virtual Private Network (VPN) Connection Support for RMT Laptop at

BTS via IP Backhaul
4-31
Converging mixed-mode and DO-only cells
4-32
Intelligent Antennas/PTSD for CDMA Modular Cell 4.0B
4-33
Six Access Channels per Paging Channel
4-50
...................................................................................................................................................................................................................................
401-703-487
4-1
Issue 2, April 2008
Features
Overview
OneBTS platform support for Advanced Wireless Spectrum (Band Class

15)
4-52
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
4-2
Features
Automated Neighbor Selection for Neighbor Cells in

Co-location
Partnership
...................................................................................................................................................................................................................................
Feature Description
This feature eliminates the need to populate both/all co-located cells as the neighbors
(of other cells) using alternate neighbor list on RC/V. With this feature, it is required to
only populate the principle neighbor list if a cell is neighboring with cells that in a
co-location partnership. This feature is provided in Release 23.0 of the software.
This capability makes it possible to only populate one member of the co-located
partnership in the Principle Neighbor List and still provides handoff capability to both
partners for all carriers on the serving sector. It eliminates the need to populate any
Alternate Neighbor Lists when neighbors are in any co-located configuration (i.e. HD
4.0).
In order to alleviate the need an Alternate Neighbor list for a co-located neighbor cell,
the base station software will determine the appropriate partner, based on the serving
frequency and band class when the capability is active for the owning sector of the
neighbor list where the candidate pilot is found (note that this owning sector may be
an active secondary leg on the call and not the primary). When the mobile reports a
pilot PN that meets the criteria to perform a soft handoff, the base station software will
determine the initial cell site/sector of the pilot using the Principle Neighbor List as
currently is done today. If it is determined that the given candidate in the neighbor list
(i.e. the cell) does not support the serving frequency, but its partner does support the
serving frequency, the base station software will automatically change the candidate to
the partner cell. This will allow the customer to enter either cell number from the
partnership in the neighbor list and removes the need to populate Alternate Neighbor
lists.
When the capability is activated for the sector owning the neighbor list, there is no
need for any references to the S2 side of the co-located partnership if ones convention
is to use the HD side as the reference cell number for all neighbor lists.
Note that the neighbor list for a S2 in partnership still needs to be entered to match
that of its HD partner. This feature does not automatically translate the HD neighbor
list entries to both the S2 and HD cell in a partnership. The S2 neighbor list in the
partnership must be manually entered to match the HD neighbor list.
The following is an example set of cells that illustrates the population of the neighbor
list and the logic the cell will use to determine the appropriate secondary sector to add:
Cell 10 is a S2 cell supporting F1-F6

Cell 20/200 is co-located partnership where:
Cell 20 is Modular Cell 4.0 supporting F1-F2
Cell 200 is S2 supporting F3-F6
...................................................................................................................................................................................................................................
401-703-487
4-3
Issue 2, April 2008
Features

Co-location Partnership
Cell 30/300 is co-located partnership where:
Cell 30 is Modular Cell 4.0 supporting F1-F3

Cell 300 is S2 supporting F4-F7
For the co-located neighbors of cell 10, the Principle Neighbor Lists will contain 20
and 30.
For the co-located neighbor of cells 20 and 200, the Principle Neighbor Lists will
contain 30.
For the co-located neighbor of cells 30 and 300, the Principle Neighbor Lists will
contain 20.
If a mobile is on cell 10 and is on F1 or F2, the soft handoff request will be sent to
cell 20 or 30.
If the mobile is on F3 of cell 10 and the pilot of cell 20/200 is reported by the mobile,
the handoff request will be sent to cell 200. This will occur since the base station
software determines that 20 does not serve the frequency, but 200 does have it
available.
If the mobile is on F3 of cell 30 and the pilot of 20/200 is reported, again the soft
handoff request will actually be sent to cell 200 since the base station software
determines it is the appropriate candidate for the given serving frequency and band
class.
Note that this capability is controlled via a translation in the ceqface form, field
auxiliary sector: control-3, bit 6 which the value is 64 and must be set at the
primary cell in order for the Modular Cell to automatically determine the candidate for
the soft handoff from the co-located neighboring cell.
This feature will not work with Modular Cells that have pre-Release 23.0 software.
If the primary sector is on a release that does not have this capability available (i.e.
pre-R23.0 cell release), then this primary will not know how to calculate the candidate
sector for the given pilot and serving frequency for co-located neighbors if only one
entry in the partnership is entered. Therefore, sectors that exchange neighbor lists with
cell releases prior to R23.0 should not activate this capability since this pre-R23.0
primary may end up using a neighbor list of a secondary active sector running R23.0.
A buffer of sectors running R23.0 without the capability activated should always exist
between R23.0 sectors using the capability and pre-R23.0 sectors.
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
4-4
Features

Backward compatibility issues
If cell 10 is using the feature and only has a Principle Neighbor List with cell 20, then
soft handoffs requested from cell 40 in this example for F3-F6 may end up incorrectly
going to cell 20. This will occur since cell 10s neighbor list will be sent back to cell
40 and cell 40 may use this neighbor list when the pilot of 20/200 is reported above
T_ADD by the mobile
For this reason, this capability should be rolled out using the following procedure:
...................................................................................................................................................................................................
Update a cluster of cells to release R23.0.

...................................................................................................................................................................................................
Activate the feature using the Auxiliary Control Bit on a set of sectors that will not be
exchanging neighbor list information with pre-R23.0 cells. Leave a buffer of R23.0
sectors without the feature active between those that are active and pre-R23.0 cells.
These buffer sectors will understand how to automatically determine candidates for
co-located neighbors if they receive a neighbor list with the feature active from an
R23.0 sector.
...................................................................................................................................................................................................
Verify no CCP 669 (45669) and CCP 670 (45670) asserts are occurring on these cells.
This is a new informational assert that will be added as part of this capability to
indicate a sector with feature active is sending a neighbor list to a pre-R23.0 cell.
...................................................................................................................................................................................................
If no asserts are observed in step 3, update Neighbor List data so that only Principle
Neighbor List is populated. If asserts occur, either update the neighbor cell in question
to R23.0 or deactivate the capability and do not remove Alternate Neighbor List.
E...................................................................................................................................................................................................
ND OF STEPS
...................................................................................................................................................................................................................................
401-703-487
4-5
Issue 2, April 2008
Features

In step number 2 above, these buffer sectors will understand how to automatically
determine candidates for co-located neighbors if they receive a neighbor list with the
feature active from an R23.0 sector. These buffer cells neighbor lists must be
provisioned in the pre-R23.0 method. In the above example: the auxiliary control bit
for cell 10 should be set to 0 and cell 10 should have a principle neighbor list (cell
20) and an alternate neighbor list (cell 200).
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
4-6
Features
Shared Equipment Status Display for 1xEV-DO CDMA

OneBTS
Modular Cell 4.0
...................................................................................................................................................................................................................................
Overview
This feature allows the shared equipment status and alarms to be displayed on the
1xEV-DO Element Management System (EMS) for CDMA OneBTS Modular Cell 4.0.
3G-1X and 1xEV-DO applications may reside in the same OneBTS Modular Cell 4.0.
With this configuration, the 3G-1X and 1xEV-DO applications share the BTS
equipment such as the radio, timing units, test units and amplifiers. Since there are
separate OA&M interfaces for the two applications, both applications need to report
status of this shared equipment. The 3G-1X application already provides status of the
shared equipment through the Status Display Page (SDP), the Technician Interface (TI)
and the Read-only Printer (ROP). With this feature, Shared Equipment Status Display
for 1xEV-DO CDMA OneBTS Modular Cell 4.0 will be available through the
1xEV-DO EMS Graphical User Interface (GUI), Alarm List, and Command Line
Interface (CLI). Below is an example of the EMS GUI Alarm Report.
...................................................................................................................................................................................................................................
401-703-487
4-7
Issue 2, April 2008
Features
Shared Equipment Status Display for 1xEV-DO CDMA

OneBTS Modular Cell 4.0
Prior to Release 23.0, only an active/out-of-service indication was provided. Now the
1xEV-DO system provides shared equipment alarm status information including the
alarm description. When the 1xEV-DO EMS is running on a shared OMP-FX (shared
with 3G-1X), only the shared equipment alarms generated by the 3G-1X system are
sent to the ROP-AP, which results in duplicate alarms being suppressed. In a mixed
mode configuration, OneBTS frame alarms and user alarms are also shared. With this
feature, alarm status on shared radios and RxAmps, plus the frame alarms and
provisioned user defined alarms are reported on the EMS interfaces. The 1xEV-DO
application autonomously reports these alarms on the ROP in both mixed mode and
stand-alone applications. In a shared OMP configuration, duplicate user defined alarms
can be suppressed by not configuring them on the 1xEV-DO cell.
This feature also allows the operator to assign a 1xEV-DO carrier to either transmit
(Tx) port on a shared radio without assigning a 3G-1X carrier to that port. The
1xEV-DO system reports the CLGC functions and status for that Tx port.
If a 1xEV-DO carrier shares a radio with 3G-1X carriers, but does not share a radio Tx
port with a 3G-1X carrier, the 3G-1X application still maintains control over the radio,
including control over the CLGC functions.
This feature is applicable to the CDMA OneBTS Modular Cell 4.0, in mixed mode
configurations.
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
4-8
Features
Power Throttling of PHPAM (P2PAM) and CHPAM (C2PAM)

Amplifiers
...................................................................................................................................................................................................................................
Overview
This feature allows a Modular Cell 4.0 equipped with the high power/high efficient
amplifiers (PHPAMs and CHPAMs) the option to control how much of the power
capability of these amplifiers can be used. The initial power output for the CHPAM is
20 Watts. The initial power output for a PHPAM is 16 Watts. For the CHPAM the
feature allows the first 20W to be accessible by the customer and the options to use the
remaining 20W via a Right To Use (RTU) fee. The customer is able to purchase the
extra 20W in increments of 10W. If the Modular Cell is equipped with PHPAM
amplifiers, the customer will be allowed to use the first 16W in each amplifier and the
remaining 16W can be purchased as needed in increments of 8W per amplifier via a
RTU fee. The feature is enabled via FAF/QFAF on a per ECP basis starting with
release 22.0 and higher.
RC/V Impact
The system creates two Internal Parameters generated via the FAFGEN function to
keep track of how much power is being used on an ECP that contains Cell Sites with
Modular Cell 4.0s equipped with PHPAM (P2PAM) and/or CHPAM (C2PAM). These
two internal parameters are named: PHPAM Total Wattage and CHPAM Total Wattage.
PHPAM Total Wattage
The wattage allowed for MCAs with type PHPAM in a BTS is controlled by the QFAF
value stored in the PHPAM Total Wattage variable. This parameter specifies the
maximum wattage (in blocks of 8) that can be activated on PHPAM MCAs at the ECP
level. The variable has a range of value from 0 - 28,800 which is based on the
following estimation:
16 Watts per MCA, times 24 MCAs per cell, times 600 cells per ECP (230400)
divided by 8.
The QFAF counter only gets incremented/decremented if the user exceeds the allocated
total power on the MCA.
CHPAM Total Wattage
The wattage allowed for MCAs with type CHPAM is controlled via QFAF value stored
in the CHPAM Total Wattage variable. This parameter specifies the maximum wattage
(in blocks of 10) that can be activated on CHPAM MCAs at the ECP level. The
variable has a range of value from 0 - 28,800 which is based on the following
estimation:
...................................................................................................................................................................................................................................
401-703-487
4-9
Issue 2, April 2008
Features
Power Throttling of PHPAM (P2PAM) and CHPAM

(C2PAM) Amplifiers
20 Watts per MCA, times 24 MCAs per cell, times 600 cells per ECP (288000)
divided by 10.
RC/V Equipage Rules
The following restrictions apply to the BTSEQP form:
When the MCA assigned to the port has type CHPAM if {the sum of Maximum
Output Power for Forward Link for all carriers on this Radio - [20W * #TXAMPs
in the MCA assigned to this Tx Port + 20W * # of TXAMPs in an MCA assigned
to the other equipped Tx Port on this radio]) is >0, then the resultant must be
rounded to the nearest 10 and subtracted from the ECP level QFAF counter (QFAF
counter is stored as Watts/10).
If the QFAF Counter value computed in above bullet is greater than the value
stored in the CHPAM Total Wattage parameter, the configuration is rejected.
When the MCA assigned to the port has type PHPAM, if {the sum of Maximum
Output Power for Forward Link for all carriers on this radio - [16W * #TXAMPs
in MCA assigned to this Tx Port + 16W * # of TXAMPs in an MCA assigned to
the other equipped Tx Port on this Radio]} is >0, then the resultant must be
rounded to the nearest 8 and subtracted from the ECP level QFAF counter (QFAF
If the QFAF Counter value computed in above bullet is greater than the value
stored in the PHPAM Total Wattage parameter, the configuration will be rejected.
When an MCA type CHPAM is un-assigned from a Tx Port, if {the sum of
Maximum Output Power for Forward Link for all carriers on this Radio - [20W *
#TXAMPs in MCA assigned to this Tx Port + 20 W * # of TXAMPs in an MCA
assigned to the other Tx Port on this Radio]} is >0, then the resultant must be
rounded to the nearest higher 10 and added to the ECP level QFAF counter (QFAF
When an MCA Type PHPAM is un-assigned from a Tx Port, if {the sum of
Maximum Output Power for Forward Link for all carriers on this Radio - [16W *
#TXAMPs in MCA assigned to this Tx Port + 16 * # of TXAMPs in an MCA
assigned to the other equipped Tx Port on this Radio]} is >0, then the resultant
must be rounded to the nearest 8 and added to the ECP level QFAF counter (QFAF
The above rules use the Forward Link Maximum Power field on the BTSEQP
(column 179 in the BTSEQP form for each radio), to compute usage against the
allowed value. The system takes all the forward link power assigned to the carrier(s)
on this radio to compute the total allowed power in the MCA(s) assigned to the radio,
the system takes all the TXAMPs in all the MCAs assigned to this CBR (1 or 2 MCAs
type CHPAM or PHPAM) and multiplies this number by 20 for cellular or by 16 for
PCS. The computation is made when the user inserts or updates the BTSEQP form.
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
4-10
Features

(C2PAM) Amplifiers
When the MCA assigned to the port has type CHPAM, if the Carrier(s) Forward Link
Total Watts carried on radio - [20W * #TXAMPs in MCA(s) assigned to the radio] is
>0, then the resultant must be rounded to the nearest greater 10 and subtracted from
the ECP level QFAF counter. If the result is less than 0, an error shall occur because
the user has not purchased enough QFAF TXWATT units to support this configuration.
When the MCA assigned to the port has type PHPAM, if the Carrier(s) Forward Link
Total Watts on the radio - [16W * #TXAMPs in MCA(s)] is >0, then the resultant
must be rounded to the nearest 8 and subtracted from the ECP level QFAF counter. If
the result is less than 0, an error shall occur because the user has not purchased enough
QFAF TXWATT units to support this configuration.
Example of the TXWATT number stored in the CHPAM TOTAL WATTAGE and what
this number represents in Watts:
Table 4-1
Cellular Amplifiers (CHPAMs)
Stored value in
TX Watt Units
Actual Watts
10
20
30
X/10
Example of the TXWATT number stored in the PHPAM TOTAL WATTAGE and what
this number represents in Watts:
Table 4-2
PCS Amplifiers (PHPAMs)
Stored value in
TX Watt Units
Actual Watts
16
24
X/8
Examples
Below are configuration examples.
...................................................................................................................................................................................................................................
401-703-487
4-11
Issue 2, April 2008
Features

(C2PAM) Amplifiers
Example Number One
The following examples illustrate how this feature manages the power usage on an
ECP that has 10 cell sites with Modular Cell 4.0 equipped with PHPAM (P2PAM)s.
Each Modular cell is equipped with 3 radios and each radio has one PHPAM
(P2PAM). The feature has been enabled on this ECP and the customer has not
purchased additional TXWATTS units. One TXWATT unit is equal to 8W.
The Customer can equip and set one carrier on these cell sites to operate at 16 W per
carrier on each of the three sectors supported by each BTS. The system performs the
calculation based on the equipped MCAs(3) per cell site, the number of TXAMPs in
each MCA(1) and the total number of cells (10) divided by 8. This computation result
is : 60 TXAMP units.
The system performs the calculation of the wattage usage based on the forward link
maximum power settings: Three (3) carriers per cell site at 16 W time the number of
cell sites divided by 8 = (3 * 16 * 10)/8 = 60 TXWATT units.
Since the usage is less or equal the allowed capacity, the system would allow this
configuration to go through.
Example Number Two
Same as before except the customer equipped two carriers on one of the cell sites and
each carrier at 16W: the total capacity calculation would not change since the number
of MCAs or TXAMP or Cell Sites have not changed.
When the system computes the total usage, this is the result:
Nine (9) cell sites with 3 carriers at 16W is equal to: (9 * 3* 16)/8 = 54 TXWATT
units. The total usage for the tenth cell site is: Six carriers (6) * one cell * 16W per
carrier: (6 * 16 * 1)/8 = 12 TXWATT units.
The total usage for all the cell site is: 54 + 12 = 66. Since this number is greater than
the total allowed capacity, this configuration will be denied.
Example Number Three
Same as before except the customer equipped two carriers on one of the cell site and
each carrier at 8W:
The total capacity calculation would not change since the number of MCAs or
TXAMP or Cell Sites has not changed.
When the system computes the total usage, this is the result:
Nine (9) cell sites with 3 carriers at 16W is equal to: (9 * 3* 16)/8 = 54 TXWATT
units. The total usage for the tenth cell site is: Six carriers (6) * one cell * 8W per
carrier: (6 * 8 * 1)/8 = 6 TXWATT units.
The total usage for all the cell site is: 54 + 6 = 60. Since this number is less or equal
to the total allowed capacity, this configuration would not be rejected by the system.
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
4-12
Features

(C2PAM) Amplifiers
Important! The system is managing the total wattage capacity on a per ECP basis,
but it is actually managed at a BTS level. To be more precise it is managed at a Tx
Path Level. The network might have extra Transmit Power capacity on one cell site
and no extra capacity on another cell site. In this case, if the customer tries to
configure the BTS that has no extra capacity (i.e. The BTS is equipped with only
three PHPAM type amplifiers and the BTS is already supporting two (2) carriers on
each sector at 16 W), the system will reject the configuration because it would
exceed the MCA total capacity of a single PHPAM (P2PAM).
New TI Command and Report
This feature provides a new TI command to retrieve from the ECP how much capacity
the ECP has; how much power has been used and how much can be purchased. Below
is an example of the TI command to retrieve the total wattage capacity in the ECP
system.
OP:CELL a TXWATTS
where a is the cell site number.

The output report of this command is shown below:
MCA
TYPE
PURCHASED
WATTS
PER ECP
PHPAM
60
PURCHASED
WATTS AVAIL
PER ECP
0
CELL WATTS
AVAIL FOR
PURCHASE
6
CELL
WATTS
PURCHASED
0
The Purchased Watts per ECP is based on the total number of TXAMPs in all the
Cell Sites.
The Purchased Watts Available per ECP is the difference between the Purchased
value and the total usage.
The Cell Watts Available for Purchase is base on the extra 16W capacity of each
equipped PHPAM (P2PAM) in cell site a.
The Cell Watts Purchase is base on the QFAF TXWATT units allocated to this cell
Site; each increment above the standard power is counted as x/8 TXWATT units.
...................................................................................................................................................................................................................................
401-703-487
4-13
Issue 2, April 2008
Features
Support of both IS-95 and IS-2000 (Rev. 0 and A) Overhead

Channels
on the same carrier
...................................................................................................................................................................................................................................
Overview
The purpose of this feature is to allow IS-95, IS-2000 and IS-2000A overhead channels
on the came sector-carrier. This IS-5 Overhead Channels are Paging Channel (PCH),
Reverse Access Channel (RACH), IS-2000 Rev. 0 introduced Quick Paging Channel
(QPCH), IS-2000A introduced Reverse Enhanced Access Channel (REACH), and
Broadcast Channel (BCCH).
This feature is dependent on feature SDB over 3G-1X Basic Access Mode with
minimum channel set (Base Station work only) for Packet Core Architecture. This
feature provides Base Station support for 3G-1X Enhanced Access using the Basic
Mode with the following overhead channel set: Forward Broadcast Channel, and
Reverse Enhanced Access Channel. The feature covers all URC equipped CDMA
Modular Cell platforms using the Packet Core RNC Architecture. For this feature, on
SDP Page 2139, the special purpose channels for IS-2000A are in the following
manner.
1. REACH (fr1)
2. BCCH/REACH (b1r1)
3. BCCH only (b1).
This feature is also dependent on IS-2000 Rev 0 and Rev A Overhead Channels
Co-existence per Cell feature. This feature further builds on the above feature and
ensures that all overhead channels used for both Rev 0 and Rev A can co-exist in the
same CDMA Base Station. The feature also includes the IS-2000 Sync Channel
Interoperability.
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
4-14
Features
IOS BSC - Support for Access Handoff, Access Probe Handoff,

and
...................................................................................................................................................................................................................................
Overview
The IOS BSC - Support for Access Handoff, Access Probe Handoff, and Access Entry
Handoff feature improves mobile access performance by allowing an IS-95B (or above)
mobile handoff to an IS-95B (or above) cell within the same IOS BSC during the
System Access state.
The IS-95 mobiles are capable of re-tuning to different pilots during the various
transient states of an access attempt. Pilot strength information from multiple cells or
sectors is provided by the mobile in access channel messages. This information is used
to send paging channel messages to the mobile from multiple cells or sectors and to
initially bring a call up in the handoff state. The access functions include access
handoff, access probe handoff and access entry handoff.
The IOS BSC - Support for Access Handoff, Access Probe Handoff, and Access Entry
Handoff feature ensures that the access functions run properly when the cells are
located within one IOS BSC.
Feature Operation
Access Entry Handoff (AEHO), Access Handoff (AHO), and Access Probe Handoff
(APHO) comprise the access functions that operate within a cell. All three of these
access functions are supported when the cells are located within the same IOS BSC.
Access Entry Handoff (AEHO) improves the termination performance for mobile
station termination scenarios. When AEHO is enabled in the IOS BSC, if an IS-95B
(or above) Mobile Station (MS) receives a General Page message from a cell that is
AEHO enabled, the MS is allowed to send a Page Response message and to receive
subsequent paging channel messages to and from another cell in the same IOS BSC.
A cell that supports AEHO is AEHO enabled if the Access Entry Handoff feature is
turned on at the IOS BSC. A neighbor cell of an AEHO enabled cell is AEHO allowed
if a MS is allowed to send a Page Response message to this cell without receiving a
page from this cell. When a page is received from an AEHO enabled cell, the IS-95B
(or above) MS performs an AEHO to the AEHO allowed neighbor pilot, if this pilot is
stronger than the active pilot. By default, all intra-BSC neighbors are AEHO allowed
via RC/V, unless the service provider overrides them through RC/V. All inter-BSC
neighbors are disabled for AEHO and the service provider is not allowed to override
them.
...................................................................................................................................................................................................................................
401-703-487
4-15
Issue 2, April 2008
Features
IOS BSC - Support for Access Handoff, Access Probe

Handoff, and Access Entry Handoff
When the AEHO value is updated for the neighboring cell in the fci form, it is checked
to see whether the abutting cell is located under the same IOS BSC. If it is not, then
an error message is printed that indicates the corresponding field can not be set to aeho
allow for inter-BSC cells.
When the AEHO FAF is turned on and the Access Entry Handoff Enable field in the
ecp form is set to y, the Access Entry Handoff feature is enabled for this ECP. The
AEHO field in the fci form indicates whether a mobile is permitted to perform Access
Entry Handoff to a neighboring sector. All inter-BSC neighbors are disabled for AEHO.
Access Handoff
Access Handoff (AHO) allows a IS-95B (or above) mobile transfer reception of the
paging channel from one cell to another after a successful access attempt. A successful
attempt is made when the mobile station sends a message to a cell and receives an
acknowledgement. The handoff can occur when the mobile enters the following
substates within the System Access state:
Page Response substate

Origination Attempt substate
When updating the AHO field for the neighboring cell in the fci form, check to see
whether the abutting cell is located under one BSC, if it is not, an error message is
printed that indicates the corresponding field can not be set to aho_allow for inter-BSC
cells.
Access Probe Handoff
Access Probe Handoff (APHO) allows an IS-95B or 3G-1X mobile station to handoff
to a stronger CDMA pilot while waiting for the BSC acknowledgement during an
access attempt to a Page Response or Origination. A cell is APHO enabled if the
Access Probe Handoff feature is turned on at the IOS BSC. A neighbor cell of an
APHO enabled cell is APHO allowed if a mobile is allowed to perform APHO to this
cell from the APHO enabled cell.
If an APHO origination arrives and the same mobile is already busy with another
origination, then the APHO origination is dropped. If an APHO termination arrives and
the same mobile is already busy with another termination, then the APHO termination
is dropped.
APHO Glare
If a call attempt on first cell (primary or secondary) is successful but the

acknowledgement to the mobile is delayed or dropped (and the call setup continues),
the mobile initiates a call attempt on another cell (secondary) of the pilot list. This may
cause a primary/secondary or secondary/secondary glare. When a glare is detected, IOS
BSC Call Processing Data Node (CDN) releases the second call.
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
4-16
Features

Feature interactions
The IOS BSC - Support for Access Handoff, Access Probe Handoff and Access Entry
Handoff feature interacts with the CDMA Enhancements for Geo-Location.
Mobile Origination
When a origination message is received from the cell site, if the access secondary cell
is included, then the IOS BSC uses the access secondary cell with the round trip delay
measurement to format the CDMA serving one way delay parameter in the IOS CM
Service Request message.
Mobile Termination
When a termination message is received from the cell site, if the access secondary cell
is included, then the IOS BSC uses the access secondary cell with the round trip delay
measurement to format the CDMA serving one way delay parameter in the IOS Page
Response message.
If a call is initiated on an APHO secondary cell, the measurements for geo-location are
taken by the secondary cell. The secondary cell number and face are set as the serving
cell number/sector in the CDMA Serving One Way Delay Information Element in the
IS-634 message, CM Service Request and Paging Response. The secondary cell
number and face are passed on to the IOS Mobile Switching Station (MSC) to
correctly calculate the location of the mobile.
Error Messages
For IOS-BSC configurations, Inter-BSC cells cannot be configured in the fci neighbor
list (primary or secondary) for AHO, AEHO, or Channel Assignment into Soft Handoff
(CAMSHO). If there is an attempt to configure AHO, AEHO, or CAMSHO in the fci
neighbor list for an Inter-BSC cell, the following warning messages are generated:
AEHO can only be set for intra-BSC cells
AHO can only be set for intra-BSC cells

CAMSHO can only be set for intra-BSC cells.
Feature Implementation
For information on how to provision the AHO, AEHO, or APHO features, see the
following documents:
Wireless Networks Executive Cellular Processor Access Entry Handoff Optional

Feature Description, (401-612-364)
Wireless Networks Executive Cellular Processor Access Handoff Optional Feature
Description, (401-612-367).
For more information on IOS BSC, refer to the Lucent Interoperability Specifications
Base Station Controller Operations, Administration and Maintenance, (401-704-400).
...................................................................................................................................................................................................................................
401-703-487
4-17
Issue 2, April 2008
Features

Important! In the above reference documents some of the contents are not applied
to IOS BSC feature. AHO, APHO and AEHO are a base feature of IOS BSC and
do not need to be activated by Alcatel-Lucent account executives. This feature is
active by default with Release 24.0 software.
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
4-18
Features
EV-DO
Cell OA&M Shared Indicators
...................................................................................................................................................................................................................................
Overview
This feature is used to improve user awareness of 1xEV-DO service in a mixed mode
configuration (a cell supporting both 1xEV-DO and CDMA). This feature supports the
display of read-only indicators on the CDMA SDP screens through the use of:
1. The DO Cell Indicator (a general label that shows DO service is supported in the
cell).
2. The DO Component Indicator (a component specific label that shows DO is
supported in the specified radio or TxAMP).
This feature applies only to a mixed mode configuration. Mixed mode cells are
supported on the OneBTS, the Modular Cell and the Mixed Frame (Modular Cell
Primary frame and OneBTS Growth Frame). Mixed mode cells can optionally support
shared radio (OneBTS only) and shared TxAMPs (Modular Cell or OneBTS). All
mixed mode cells share TFU/OMs with or without shared radio or TxAMPs. The
DO-only cell will continue to use the EMS only.
This feature impacts RC/V and SDP subsystems. SDP pages have been modified to
provide information to identify the characteristics of the mixed mode cell if all types of
indicators is enabled or just the DO cell indicator through the RC/V forms:
This feature impacts RC/V and SDP subsystems. SDP pages have been modified to
provide information to identify the characteristics of the mixed mode cell if all types of
indicators is enabled or just the DO cell indicator through the RC/V forms:
By equipping the 1xEV-DO Mixed Mode Cell Indicator located in the

CMODEQP page, the DO Cell Indicator will be presented on SDP pages: 2131,
2136, 2138, and 2121 (when 600 Cell feature is enabled) for a specified cell.
If the user elects to equip TxAMPs with DO TxAMP Indicator set to yes
through the CMODEQP form, then the DO Shared TxAMPs Indicators will be
displayed on SDP Pages 2136 and 2138 for the specified components and cell.
If the user elects to equip shared radios with DO Radio Indicator set to yes
through the BTSEQP form, the DO Shared Radio Indicators will be displayed on
SDP Page 2138 for the specified component and cell.
The 1xEV-DO service indicator appears as a yellow text on a blue background. Below
is an example of this indicator shown on SDP Page 2121.
...................................................................................................................................................................................................................................
401-703-487
4-19
Issue 2, April 2008
Features
Below is an example of SDP Page 2131.
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
4-20
Features
There are two screens associated with this SDP Page depending on the configuration.
The one below indicates the use of a URC. There is another screen which is used
when CRCs are present. Below is an example of the indicator on SDP Page 2136.
...................................................................................................................................................................................................................................
401-703-487
4-21
Issue 2, April 2008
Features
There are two screens associated with this SDP Page. One screen showing just Mixed
Mode cell. The one below shows the Shared TxAMPs screen. Below is an example of
the indicator on SDP Page 2138.
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
4-22
Features
...................................................................................................................................................................................................................................
401-703-487
4-23
Issue 2, April 2008
Features
IP
Backhaul
...................................................................................................................................................................................................................................
Overview
The IP Backhaul (IPBH) feature uses IP protocol as a standard network layer for
transferring signaling and bearer traffic between base transceiver stations (BTS) and the
mobile switching center (MSC).
IP Backhaul is available on all Alcatel-Lucent CDMA platforms. IPBH utilizes
Multi-Link/Multi-Class PPP (ML/MC-PPP) to group multiple T1/E1s into a single
large pipe called a Multi-Link Group (MLG) for backhaul transport. Each MLG
consists of 1 or more T1/E1 facilities per URC, configurable by the customer.
For more information regarding IP Backhaul, refer to Wireless Networks IP Backhaul
for CDMA Voice and Packet Data, (401-710-090).
Related features
The following FIDs are required in order for IP Bachaul to function:
FID-10666.0: IP Backhaul for CDMA (Modcells 1, 2, 3)--This feature supports IP

Backhaul between the BTS and the MSC for the CDMA application. (FAF/QFAF).
This feature is required.
In order to perform IP Backhaul conversion remotely, the following feature must be

activated:
FID-12170.0: RMT capability at the MSC--The full installation RMT software

version is required to reconfigure a BTS from FR to IPBH. This may be RMT at
the cell or RMT at the MSC. This feature supports IP Backhaul (10665.0/10666.0)
by allowing the remote maintenance terminal (RMT) to communicate with a cells
URC via a LAN connection of a particular AP, and change the backplane
parameters from frame relay (FR) to IP Backhaul (IPBH) without having to make a
cell site visit.
Prerequisites
The following technologies are supported for IP Backhaul:
CDMA Cellular
CDMA PCS
What is IP Backhaul
Internet Protocol (IP) is the standard protocol that forms the basis of the internet as
defined by the Internet Engineering Task Force (IETF). IP works in networks with
numerous and varied types of hardware and software, and it allows full peer-to-peer
communications between any nodes in the network. Backhaul is the means by which
the base transceiver stations (BTSs) connect to the mobile switching center (MSC).
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
4-24
Features
IP Backhaul
IP Backhaul (IPBH) utilizes Multi-Link/Multi-Class PPP (ML/MC-PPP) to group

multiple DS1s into single large pipe called a Multi-Link Group (MLG) for backhaul
transport. Each MLG consists of 1 or more DS1 facilities per URC, configurable by
the customer.
IP Backhaul Feature
With IPBH, both signaling and user traffic are multiplexed over IP over unchannelized
DS1s.
Traffic from the BTS terminates on an edge router.

The backhaul routers send the signaling traffic to the radio cluster server
application processor (RCS-AP).
The bearer traffic is delivered directly to a Backhaul Server (BHS), located in the
PSU2e or 1XRNC, over Ethernet links.
TSI ports used for packet pipe trunks are freed because of direct termination of
backhaul facilities to the BHS, meaning that the TS1 ports can be used for network
trunking thereby increasing the 5ESS DCS switching module (SM) call capacity. In
addition, frame relay protocol handlers (FRPHs) currently being used for frame relay
backhaul are not needed for IPBH.
Advantages
IPBH provides the following advantages versus frame relay (FR) backhaul:
Provides increased and improved capacity:

Frees 5ESS DCS time slot interchange (TSI) capacity for up to 40% more voice
calls per SM
Improves T1 utilization through the use of unchannelized DS1s and a more
efficient protocol
Increases voice call leg density per PSU2e slot to 2000 (from 240)
Simplifies planning and configuration:
Reduces operating expenses for backhaul provisioning and maintenance
Simplifies backhaul and switch facilities engineering and provisioning
Eliminates DS0 grooming
Enables packet data traffic to be separated from voice traffic ahead of a DCS and
routed directly to an RNC
Ethernet backhaul for both CDMA and 1xEV-DO
This feature provides Ethernet backhaul for BTS2400 series for both CDMA and
EVDO applications. As one of L1/L2 options that IP backhaul offers, Ethernet
backhaul will be an alternative to T1/E1 backhaul facility with broad bandwidth ranged
up to 100 Mbps. Ethernet backhaul will benefit the cell site where multiple T1s are
...................................................................................................................................................................................................................................
401-703-487
4-25
Issue 2, April 2008
Features
IP Backhaul
more costly. In addition, customer will also benefit from simplified provisioning over
Ethernet backhaul transport. Ethernet backhaul is offered using a URC and URCII.
Each URC or URCII can be assigned for 3G1X or EVDO, but not mixed. An Ethernet
Interface Unit (EIU) which replaces the existing IOU will provide each URC or URCII
with a 100 Base-TX connection. Manual configuration and auto negotiation on each
Ethernet interface will be supported. Below is a diagram depicting the Ethernet
backhaul reference transport network:
For more information regarding IP Backhaul and Ethernet Backhaul see Wireless
Networks IP Backhaul for CDMA Voice and Packet Data, (401-710-090).
SSH/SFTP Services for IP BH
This feature provides SSH/SFTP service between BTS and RCS-AP replacing Telnet
and FTP services. It supports the RSA key provisioning required by SSH. This service
is required to be operated under the Basic secure mode or above. SSH/SFTP is an
option under insecure mode while Telnet and FTP are still available. It will also
provide the ability to download the generic to the BTS via sftp.
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
4-26
Features
Support
for Subnet ID
...................................................................................................................................................................................................................................
Description
The 1xEV-DO network uses Subnet ID instead of System ID (SID) as the network
identification. Subnet ID is the 104 Most Significant Bits of the Sector ID or UATI and
is broadcast over the air as part of network overhead information in Sector Parameters
Message.
Begining with Release 23.0 each cell configuration has the ability to turn on or off the
Subnet ID feature via the EMS GUI. Subnet ID parameters which are dynamically
updateable.
If the Subnet ID feature is ON, the individual should choose the desired format
(ANSI-41 -OR- GSM/UMTS -OR- IPv4 -OR- Reserved). Currently only ANSI-41
format is supported.
On selecting ANSI-41 the user should enter values for SID (possible values filling 15
bits) and Position of 1s bit (possible values are 9 - 55).
Procedure to turn on the Subnet ID
Subnet ID is turned on from the Service Node Container with the following steps:
...................................................................................................................................................................................................
Go to the Service Node Container.

...................................................................................................................................................................................................
Under General Service Node Attributes - section 1, set your System Identifier (SID) to
the desired SID.
This SID is turned on a per Service Node basis.
Important! The System Identifier can also be provisioned on a per RNC Frame Basis.
If you select the SID on the Frame, this provisioning will replace the SID defined
under General Service Node Attributes - section 1.
...................................................................................................................................................................................................
Go to the SectorID Provisioning Parameters in the Service Node Page

...................................................................................................................................................................................................
Select Enable on the SectorID Provisioning. This turns the Subnet Id feature on the
Service Node.
...................................................................................................................................................................................................
Select the desired position for SectorID Position. The default value is 9 but you can
select values (9- 55)
...................................................................................................................................................................................................................................
401-703-487
4-27
Issue 2, April 2008
Features
Support for Subnet ID
...................................................................................................................................................................................................
For Parameter: SectorID Type, the default value is ANSI-41.

Important! R23 currently provides support only for ANSI-41 even though GUI shows
other formats as well.
...................................................................................................................................................................................................
Select submit, this will enable the Subnet ID feature.

END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
4-28
Features
Inter-band
idle mode load balancing
...................................................................................................................................................................................................................................
Overview
This feature provides a mechanism to redirect idle mobiles from one band class to
another when the source band class is more heavily loaded than the other band class in
dual band deployments. Dual band deployments can be via dual band cells or
co-located cells or overlaid cells. Enhancements to dual band environments that are
being developed in standards will help new mobiles when implemented in the future.
This feature provides a solution to improve the performance of dual band deployments
by balancing the distribution of idle eligible dual band mobiles across both band
classes for current/legacy mobiles.
Load balancing will be done based on paging channel occupancy and RF loading on a
location area wide (cluster of cells) basis for each band class. When the loading on one
band class exceeds an activation threshold while the loading on the second band class
is below an acceptance threshold, a percentage of eligible dual band mobiles that
registered on the first band class will be redirected to paging channels on the second
band class. Criteria for eligible mobiles for redirection will include mobile type,
supported band classes, and time of last redirection.
This feature will optimize performance of dual-band deployments by balancing paging
and access channel occupancy across the two bands.
Idle Mode Inter Band Load Balancing between the Band Classes 0 and 1 (i.e., Cellular
& PCS) for Alcatel-Lucent family of URC/URC-II/URCm based Alcatel-Lucent
CDMA and SII platforms deployed via overlay, co-location and Dual Band cells.
...................................................................................................................................................................................................................................
401-703-487
4-29
Issue 2, April 2008
Features
Enhanced
Reverse Link Monitoring - Service Measurements
...................................................................................................................................................................................................................................
Overview
This feature provides improvements for monitoring the health of the reverse link so
that a bad reverse path (one or both diversities) can be detected.
It provides a number of new Service Measurements to better monitor the health of the
reverse link. The reverse link service measurements provide customers better visibility
into dropped calls due to reverse link problems, and to understand and optimize
network performance better.
Some of the measurements added will be accumulated at the RCS by the DPC
subsystem. Every second, the RCS receives reverse loading information from the CBRs
through the CRCs. The modcell CBR sends the BIU_RSSI_AUTO message. The MCR
on the 1BTS platform sends the CR_RSSI_INFO_MSG message. These messages
contain 5 samples of 200 msec average RSSI on each path. This information will be
passed into a new TE function to determine the Peak and Average Reverse RSSI on
both paths. The TE function will also determine the Average Differential between the
paths and the Hourly Low on the two different paths.
A separate function will be called to determine the Thermal Noise Floor on the two
Diversity paths. This information is received every 10 seconds in DPC. DPC will call
the new function which will take the lowest value of Thermal Noise Floor for the hour.
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
4-30
Features
Virtual Private Network (VPN) Connection Support for RMT

Laptop
at BTS via IP Backhaul
...................................................................................................................................................................................................................................
Overview
This feature provides for IP communication between an RMT locally connected to the
test port of the BTS and IP endpoints or hosts in the customers network. This feature
with IP Backhaul will enable to facilitate a data networking application running on a
RMT Laptop (i.e. Instant Messenger) that can communicate with the central office
without the use of a POTS line. This feature will also enable the field technician to get
access to technical resources from the cell site in real-time so that the turnaround time
to resolve field issues will be significantly reduced.
Specifically this feature adds routes to the BTS that will allow IP communication to
and from the RMT, and IP destinations on the customer network. This feature is
dependent upon a Citrix Meta Server application and the Citrix client side software
which is installed on the RMT laptop.
Below is the scenario for provisioning the RMT to communicate with the UMC and
LIU to add routs for communicating between the RMT laptop and the IP endpoints in
the network.
Connect the RMT laptop to the Ethernet port of a BTS.

Start the RMT software application.
Within the RMT application, a screen shall be provided so the end-customer can
enter up to 10 IP addresses. These entries will remain in a database and used
whenever this application is re-run. If the end-customer wishes to change the
entries they can then edit them and save them to the database.
The technician shall be able to determine the link status from the BTS to the edge
router and AP from the Link Connection Status GUI screen.
Once the link status is determined to be available the technician can then start the
RMT software application for adding a route.
A GUI button, to initiate the process of adding a routes to provide IP
communication between the RMT laptop and the customer network is provided.
Once the GUI button is selected, the RMT software application will attempt to
transparently add routes which will facilitate IP communication between the RMT
laptop, and the end-customer network associated with an IP address that was
previously provided. When each route is added, the RMT will attempt to
communicate with IP endpoint in the end-customers network.
If there is a problem with heavy downloads or data transfers, a warning indicating
will be displayed indicating a potential problem.
The technician can then communicate to the Citrix server using the Citrix client
installed on the RMT laptop.
...................................................................................................................................................................................................................................
401-703-487
4-31
Issue 2, April 2008
Features
Converging
mixed-mode and DO-only cells
...................................................................................................................................................................................................................................
Purpose
This section provides a brief description of Cell Convergence and references the
document that covers the procedures. Cell Convergence is a Release 25,0 (FID
11003.1) feature.
45Description
The Cell Convergence feature migrates data from the 1xEV-DO RNC, in a
mixed-mode cell, to the ECP so that the ECP can have control over both the CDMA
and 1xEV-DO sections in a mixed-mode cell.
Convergence procedure
To converge a Release 24 mixed-mode or DO-only cell, refer to the Wireless Networks

Cell Generic Update Procedures, (401-614-327).
Wireless Network IP Network
1xEV-DO
BTS
1xEV-DO
BTS
T1/E1
1xEV-DO
BTS
Ethernet
Lucent VPN
Firewall
OMP-FX
1xEV-DO EMS
CDMA20001x EMS
Ethernet
DO-RNC
R-P
(A10-A11)
PCF
Controller
Channelized Ds3
Dual Mode
BTS
1xEV-DO
RCS/AP
CDMA
20001X
Internet
PDSN
R-P
(A10-A11)
Ethernet
PCF
DCS
CDMA
20001X
NMS-Network Management System

PCF-Packet Control Function
PDSN-Packet Data Service Node
ECP
CDMA
20001X
CDMA
20001X
HLR
SMSC
1xEV-DO
Components
CDMA
20001X
Broadband
IP
Shared
Components
...................................................................................................................................................................................................................................
401-703-487
Issue 2, April 2008
4-32

9222-2400 System Engineering Translations and Maintenance PDF

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

9222-2400 System Engineering Translations and Maintenance PDF

Încărcat de

Drepturi de autor:

Formate disponibile

3

Recognize the functions of the different types of user interfaces.

Selecting a Modular Cell user interface

How to Choose the Right Interface

ECP-based interface: Recent Change/Verify screens

RC/V access manager forms

Selected RC/V Forms

ECP-based interface: Craftshell interface and Read-Only Printer

Craftshell command syntax

Useful maintenance commands

Craftshell command syntax changes

ECP-Based Interface: Status Display Pages

Video States of SDP Display

Status Display Page appearance

SDP system architecture

Status Display Pages

Application processor command line interface

Application processor architecture

Access the EMS CLI

Access TI CLI via OMP

Access TI CLI via AP (FMM-AP or Alcatel-Lucent CDMA AP)

The Remote Maintenance Tool (RMT) interface

Integrated power software

Modular Cell Documentation

The Alcatel-Lucent CDMA documentation provides the information support necessary

Modular Cell schematic diagrams that depict component connectivity

Schematic diagrams (SDs) are multi-page documents that support particular

SD sheets are arranged alphabetically from A to H, and contain information as listed in

Issue date(s), sheet indices to all SD pages

Graphic information about the circuit(s)

Component-specific information, such as

Explanation of notes referenced within FSs

Text description of the circuits appearing in

Not used in this SD

Not used in this SD

Specific interconnection cabling information

High-level interconnections between major

Customer documentation is available on the AUTOPLEX/Wireless CD-ROM or over

Select View the installation Notes to display instructions on installing the

Select Install Wireless Network Systems Documentation to install the documentation

Wireless documents description of the display

The documentation display is a single-pane layout. To access the documentation, use

Select a topic from the pane.

Select the requested documentation from the group displayed.

Select an item in the list to display the corresponding text.

SDPs and Fault Isolation

CDMA Executive Cellular Processor (ECP) Operation, Administration, and Maintenance

Tests and diagnostics

Cell Input message formats

Wireless Network Executive Cellular Process

Cell Output message formats

Wireless Network Executive Cellular Process

Modular Cell 1.0 - 3.0 OA&M

Alcatel-Lucent CDMA and PCS CDMA Modular

Modular Cell 4.0 OA&M

Alcatel-Lucent CDMA Base Stations - 4.0, 4.0B,

5E13 and Later Software Releases, (235-080-100)

Selecting a Modular Cell user interface

The MSC-based interface uses the AUTOPLEX system commands.

The RMT-based interface is an optional, self-contained software package that executes

Connections to the MSC through the Application Processor Cluster (APC) to

How to Choose the Right Interface