05 icell iic notes

iCell IICCDMA iCell Base Station System Training

5-1© 2010 Global Star Solutions International Inc.

Enabling networks to reach new markets

CDMA iCellTM Base Station SystemTraining

iCell™ Initial Installation & ConfigurationOctober 2010

Notes



Confidential Information5‐2Enabling networks to reach new markets

Module Introduction

• This module provides a summary of the configurable parameters for the iCell™ BTS and BSC.

• The emphasis is on those parameters that affect system performance, and as such may require optimization before and during commercial operation.

• Understanding the appropriate settings of these components is necessary in order to successfully operate and administrate BTS and BSC.

• Understanding ACM Basic Provisioning Tasks• Installation Notes

Note: Please consult Star Solutions® customer supportbefore changing any of the parameters

Notes




Installation Notes

Notes




Common Installation Practices

• RF cables should not bend on a radius of less than 6 times the outside diameter of the cable.

• Avoid sharp bends in wires that have been marked with the hot stamping process.

• All wiring needs to be protected from damage. Coaxial and triaxial cables are particularly vulnerable to certain types of damage.

• Personnel should exercise care while handling or working around coaxial. Coaxial cables can be damaged if they are clamped too tightly, if they are bent sharply (normally at or near connectors).

• Coaxial can be severely damaged on the inside without any evidence of damage on the outside.

NEVER:• “kink” a coaxial cable.• drop anything on a coaxial cable.• step on a coaxial cable.• bend a coaxial cable sharply.• loop a coaxial cable tighter than the allowable bend radius.• pull on coaxial cable except in a straight line.• use coaxial cable for a handle, lean on it, or hang things on it (or any other wire).




Installation Prerequisites

• Make sure power breakers are turned off

• Required personnel and support documentation are available

• Required tools and hardware are available

• Required software is available

• Network planning requirements are complete

• Adhere to proper grounding recommendations

Installation, removal or replacing a HW unit generally requires access to both the front and the rear of the rack




Site Readiness ‐ External Grounding

Grounding of the site is the responsibility of the customer. All grounding and power connections should be made according to local standards.

Several factors affect external grounding. The most significant factor is the resistance of ground rods, which is directly related to soil resistivity in the immediate vicinity of the rod. The resistivity of the soil determines how many rods are needed and their dimensions.

To provide maximum external site grounding for the Macro BSS rack, a ground ring must be installed around the site structure. The ring must be buried at least 77 cm (30 in.) below grade or below the frost line of the installation, whichever is greater. The ring must be a buried, horizontal wire completely encircling the equipment shelter. This wire must be made of solid tinned copper of #2 AWG or larger.

The AC power ground conductor must be bonded to the ground rod located at the service entrance. Ground lugs provided in all service entrance equipment must be bonded to the service ground conductor. The system ground and neutral must be bonded at one location only, as close as is practical to the service entrance. All service grounding must conform to local electrical codes.




Pico BTS Wiring Diagram (Example)

There are different form factors of the Pico BTS including Pico BTS Wall Mount and Pico BTS Rack Mount.

Note: Make sure required documentation and installation & testing tools are available. Refer to the documentation for detailed requirements.

Note: The shielding of all coaxial connections must be grounded.




Antenna Cable Connection Points

Sectors, FA, and Macro BTS (MCPA Version)

The antenna cable connection points are on the rack bulkhead (top of rack). There is a single connection plate for all antenna cables. The antenna cables are connected to the rack at the antenna and GPS cable connection plate.

There is a separate antenna connector for each sector (ALPHA, BETA, GAMMA) and two ports (MAIN, DIVERSITY) per sector for a total of six antenna connectors. The number of supported FA does not change the number of antenna cables. The Antenna Combining System (ACS) in the BSS rack manages the signals. A BTS processes the signals for a single FA. The BSS rack will have a BTS for each FA.




ACS Connections

BTS RxDBTS RxM

BTS Tx

1

2

3

4

1

3

2

4

PA - OUT

PA - IN1 2

iCell 800 MHZ ACS

Latch

BTS RX Diversity

Cable (SMA)

BTS RX Main Cable (SMA)

BTS TX Cable (SMA)

PA IN Cable

(N-Type)

PA OUT Cable

(N-Type)

Guide Holes

D-Sub Connector

Main

Diversity

Main Antenna Cable Connection

Diversity Antenna Cable Connection

ACS(Front View)

ACS(Rear View)

Within the two FA system, the FA transmit power is not combined and the power is radiated on different antennas.

The figure above shows that for a two FA system, the transmit power of FA1 is radiating on the main antenna, while the transmit power of FA2 is radiating on the diversity antenna.

The BSC detects a multi�carrier cell by comparing the cell identifiers, frequency and band class of each cell defined through the Abis interfaces from the BTSs.




ACS Connection Points

ACS Connections in 2FA System

SCPA

SCPA

Split

ter

Split

ter

Within the two FA system, the FA transmit power is not combined and the power is radiated on different antennas.

The figure above shows that for a two FA system, the transmit power of FA1 is radiating on the main antenna, while the transmit power of FA2 is radiating on the diversity antenna.

The BSC detects a multi�carrier cell by comparing the cell identifiers, frequency and band class of each cell defined through the Abis interfaces from the BTSs.




Compact Macro BTS Wiring – Front Panel

Compact Macro BTS Front Panel Interface ConnectionsETHERNET: Provides Ethernet IP connection to a BSC.COMM IN: Attached to additional sectors and should remain disconnected.COMM OUT: Used in conjunction with a PC to configure the IP address of the unit.




Compact Macro BTS Wiring – Rear Panel

Compact BTS Connector TypeEthernet: RJ45 SocketCOMM IN, COMMOUT: RJ45 SocketGPS Antenna: Connector N�Type (male) or TMA (male)

Note: for the TMA, use the provided adapter.1 PPS IN: BNC (male)1 PPS OUT: BNC (male)AC Input module: YC�12Diversity Antenna: 7/16 DIN (male)Main Antenna: 7/16 DIN (male)Sector 1 and 2 (TX, RXM, RXD): QMA (male)




BTS‐SNTP Interface

Primary BTS with GPS Connection

BTSs with Chaining 1PPS Signal Primary BTS Without GPS Connection

For the BTS, configuring the BTS SNTP interface requires configuring the SNTP server IP address. A single BTS acts as an SNTP server for the other BTSs attached to the same BSC. The first BTS to be configured should act as the SNTP server (sntpServerIp = 0.0.0.0).

In the case of multiple BTSs, the primary BTS acts an SNTP server for the other BTSs attached to the same BSC. Set the value of sntpserverIp on subsequent BTSs to the IP address of the initial BTS (SNTP server).

Warning: BTS time configuration without GPS is not recommended by Star Solutions. The transmitted frequency may drift over time violating local (for example, FCC) regulatory standards.




BSC Provisioning

Notes




BSC IP Configuration

For the BSC server, IP configuration needs to be performed on the OS (Linux) level. Files involved in this process are:

• /etc/hosts• /etc/sysconfig/network-scripts/ifcfg-eth0• /etc/sysconfig/network• Stop the application and reboot the server in order for the changes to take effect

Note: You need root privilege to modify these files




BSC Provisioning Objects

• BSC– BSC ID– BSC IP

• CDMA– Pilot database– PDSN Table (IP Address, Port Number, SPI, Secret, ESN

Format)• Interfaces

– MSC ID/IP address– SNTP Server IP Address

• Call Properties– BSC Maximum Call Number

• Commands– Save Configuration– Apply Configuration

Notes




BSC ID

This parameter is for administrative identification for the BSC.




BSC IP

The textual representation of the BSC IP address is internally gathered from the Linux operating system using the miscellaneous bscEtherDev parameter.




CDMA Objects

• The pilot database includes information about all the cells connected to the BSC.

• The BSC uses the pilot database to perform soft-handoffs and hard-handoffs.

• The sectorInfoTable and the neighborListTable are a snapshot of the internal pilot database.

The pilot database includes the information of all the cells connected to the BSC. Each cell connected to the BSC periodically sends to the BSC a set of Abis messages including the list of active sectors and their neighbors. All this information is organized in the pilot database. The BSC uses the pilot database to perform soft-handoffs and hard-handoffs.

The sectorInfoTable, neighborListTable and the cfsNeighborTable (to follow) are a snapshot representation of the internal pilot database. These tables are refreshed every few seconds to show a relatively updated view of the pilot database for the manager.

The pilot database is automatically maintained by the BSC with the assistance of the information uploaded from the deployed cells. The manager is not able to modify the pilot database in any form. Therefore, the handoff mechanisms at the BSC rely on the configuration of the cells.




Sector Info Table

sectorInfoTableTable of cells and sectors. This table is read-only and includes an entry for each active sector in the cells connected to the BSC. The information related to each active sector is periodically uploaded from the BTS configuration via specific Abis messages. The table of sectors is indexed by the Cell ID and Sector Number parameters.




Neighbor List Table

The BSC can have a maximum of 3072 neighbors. Table of neighbors associated with each cell and sector. This table includes an entry for each neighbor associated with every cell, which is connected to the BSC. The information related to the neighbors is periodically uploaded from the BTS configuration via specific Abis messages.




System Indication

The SID field is provided by the first successfully connecting BTS. The value 0 is reserved. SIDs are allocated by the national communications authority in each country (e.g., FCC in U.S. and Industry Canada in Canada).




Network Indication

Network identification. This field serves as a sub-identifier of a system as defined by the owner of the SID. This field shall be set to the network identification number for this network.

The NID field is provided by the first successfully connecting BTS.

The NID is a number that is common to all sectors of any given BTS. Different BTSs may have different NID numbers. However, all BTS units connected to the same BSC should have the same NID.

The NID number 0 is a reserved value indicating all base stations that are not included in any network.

The NID number 65535 is a reserved value the mobile station may use for roaming status determination to indicate that the mobile station considers the entire SID (regardless of NID) as home (i.e., non roaming).




Mobile Country Code

The MCC and IMSI_11_12 fields are “read-only” in the BSC and are provided by the first successfully connecting BTS.

IMSI_11_12: 11th and 12th digits of the IMSI, which determine the mobile network code (MNC).

All the BTS and BSC elements in the network shall be configured with the same MCC and IMSI_11_12 values.




PDSN Table

Define PDSNs, working with the BSC.

a11PdsnSpi: Security parameter index, passed to PDSN for BSC authentication.

a11PdsnSecret: Shared secret string passed to PDSN for BSC authentication.

a11EsnFormat: Format for ESN used in A11 messaging, specifically the Air Link Setup record. This parameter should be set as required by the PDSN or AAA.




MSC IP

Address of the Soft Switch connected to the BSC. Can be IP Address or host name.




ABIS Links

This table lists all the BTSs connected to the BSC.




SNTP Server IP

The SNTP server IP Address is typically the BTS IP address who is connected to GPS




BSC Max Call Number

The maximal number of calls that are allowed to be setup on the BSC up to the licensed limit.

The purpose of this parameter is to provide a soft limit on the number of calls that may be set up.

Typically this parameter should have the same value as the licensed limit.




BSC Test Call

Autonomously processing of test calls in the BSC. In normal operation, this is always set to “msc”.

When it is set to “bsc”, then any initiated call will be looped back from the BSC. This is useful to test the BSS connectivity and functionality without connection to the core system.




Commands

This page is used, as the name suggests, to issue commands on the Network Element.Commands apply only to the Network Element being managed.




BTS Provisioning

Notes




BTS Boot Configuration

Steps to configure BTS boot menu:• Access the BTS console• Reboot the BTS by “Ctrl+x”• Interrupt the booting by pressing any key when asked• List the boot configuration by typing ……• Change the boot configuration by typing ……• Boot the BTS by typing ……

BTS Boot Parametersboot device: Do not change defaultunit number: Do not change defaultprocessor number: Do not change defaulthost name: Do not change defaultfile number: Relative path to the root of the operating system. Do not change default.inet on ethernet (e): IP address of the BTS.host inet (h): IP address of the FTP server (BSC)user (u): FTP user name. Do not change default.ftp password (pw): FTP password. Do not change default.flags (f): Do not change default.target name (tn): BTS name. This name is used as the corresponding .cfg file name. Do not change default.startup script (s): BTS startup script, taken from BSC. Contains boot-up parameters. Do not change default.




Essential iCell BTS MIB Objects

• HW– Number of CSMs– PP1S Source– GPS Connection

• CDMA– Sector(s) Configuration (PN Offset, Max Tx Power, Power Amplifier

Type)– Cell Information (Cell ID, Band Class, CDMA Frequency Channel,

ACM IP Address)– System Information (SID, NID, MCC, IMSI_11_12, Registration)– Neighbor List

• Interface– BSC IP Address– SNTP Server IP Address

• Commands– Save Configuration– Apply Configuration

Notes




CSM

numberOfInstalledCsms: Number of CSM ASICs in the BTS. Generally, a 3-sectors BTS would contain 6 CSM ASICs, and a 1-sector BTS would contain 2 CSM ASICs.

The BTS only uses the number of CSM ASICs defined in this parameter, starting from CSM ASIC number 0 (zero). During startup, the BTS initializes and configures each CSM ASIC (starting from CSM ASIC number 0) until all the CSM ASICs defined by this parameter have been successfully initialized and configured, or until the BIT of a CSM ASIC fails. If a BIT of a specific CSM ASIC n fails, then only the CSM ASICs from 0 to n-1 will be used.




PP1S Source

PP1S signal source selection. The BTS synchronizes to the external PP1S signal coming from the interface defined in this parameter. The BTS is able to synchronize to the external PP1S signal generated by the GPS receiver, and that signal can be transported over a COAX cable or over an LVDS mechanism (using spare CAT5 lines).

Note: The LVDS interface is not formally supported. InternalPP1S is for Star Solutions use only.




GPS Connection Indicator

If GPS signal get disconnected, the holdover time the GPS module provides is about 8 to 10 hours.

The Compact Macro BTS GPS module does not support holdover time.




Sector Info Table

The sector information parameters include a set of tables, which define the properties of every sector in the cell. Each table contains certain parameters related to different aspects of the sector configuration, such as the general sector parameters, neighbors, Sync Channels, Pilot Channels, Paging Channels, Quick Paging Channels, etc. The sector tables include an entry for each available sector in the BTS. Each sector is identified by its number (from 1 to 6), which is represented by the table index. The picoCellBTS supports only one sector, and the iCell BTS supports up to 3 sectors. Each sector in the BTS shall be configured by the manager.

NOTE: The table of sectors is not automatically constructed by the BTS according to its physical configuration. If a sector is physically available but it is not properly configured in the sector table, then the sector is not used by the BTS.




PN Offset

Pilot PN sequence offset in units of 64 PN chips.

PILOT_PN values should be set consistent with the setting of PILOT_INC. The maximum number of possible PILOT_PN values is equal to 512 / PILOT_INC. The actual absolute values for the PILOT_PN do not matter, as long as they are spaced by a minimum of PILOT_INC. The network should be planned so that numerically close PILOT_PN values do not appear geographically near by. This could cause problems where timing errors and large multipath delays make different (but close) PILOT_PN values to appear to be the same. Where reuse of the PILOT_PN values is required, there should be sufficient geographic separation to ensure that their coverage areas are sufficiently separated.

All pilots shall be a multiple of PILOT_INC.




Max TX PWR

The value of this parameter depends on network planning and HW capability. The value must not be greater than the HW capability which is given by the parameter maxAvailableTxPwr.




Power Amplifier

For Pico BTS use “none”. For the Compact Macro BTS use “uTSiPA2”.

External iPA configuration. The iPA is a combination of a high power forward link power amplifier and a reverse link low noise amplifier. The iPA may or may not be frequency converting.




CDMA Cell Information

The cell information parameters define the certain properties of the BTS. Some of the properties relate to the identity of the cell while others relate to things that are global to the BTS and not a sector.




CDMA Cell Identifier

Cell identifier of the BTS - The cell identifier represents the 12 most significant bits of the IOS Cell Identifier, as defined in TIA/EIA/IS-2001.4-B. The coding of the cell identity is the responsibility of the operator and has to be data-filled in the MSC.




CDMA FREQ

CDMA channel frequency of the BTS. This field shall be set to the CDMA channel number corresponding to the CDMA frequency assignment for the CDMA channel. This parameter determines the center frequency of the sector transmit waveform. It determines (along with BAND_CLASS) the exact CDMA center frequency.

Note that using an invalid channel will prevent the system from starting up properly.




Band Class

This parameter shall be configured according to the band class supported by the RF front end of the BTS.




ACM IP Address

This parameter specifies the IP address of the ACM for the BTS to connect to when externalPA is set to UTSiPA




System Indication

The SID field is included in the Sync Channel Message (SCHM), System Parameters Message (SPM).

SIDs are allocated by the national communications authority in each country (e.g., FCC in U.S. and Industry Canada in Canada).




Network Indication

Network identification. This field serves as a sub-identifier of a system as defined by the owner of the SID. This field shall be set to the network identification number for this network.

The NID field is included in the Sync Channel Message (SCHM), System Parameters Message (SPM).

The NID is a number that is common to all sectors of any given BTS. Different BTSs may have different NID numbers.

The NID number 65535 is a reserved value the mobile station may use for roaming status determination to indicate that the mobile station considers the entire SID (regardless of NID) as home (i.e., non roaming).




Mobile Country Code

The MCC parameter specifies the mobile country code (As determined by ITU recommendation E.212). The MCC field is included in the Extended System Parameters Message (ESPM).




IMSI_11_12

The IMSI_11_12 parameter specifies the 11th and 12th digits of the IMSI, which determine the mobile network code (MNC). It is set as determined by network operator. The IMSI_11_12 field is included in the Extended System Parameters Message (ESPM).




LTM Offset

As determined by local time offset from universal time (UTC). Set automatically according to the date information in the autoDaylightSaving parameters.

The LTM_OFF field is included in the Sync Channel Message (SCHM).

Only the range -24,..,+23 should ever be used since the local time offset is at most ± 12 hours from UTC.




Registration Period

The lower end for mobile networks, the higher end for fixed wireless networks.

The REG_PRD field is included in the System Parameters Message (SPM).

The regPrdInd parameter shall be set to regPrdEnabled(1) for the regPrd to take effect.

This parameter should be set a value 3 to 4 times less than the corresponding VLR timeout. This is so that mobile stations have the opportunity to make multiple registration attempts to prevent the VLR from throwing away its record.




Home Registration

Autonomous registrations are power-up, power down, timer, zone, and distance based registration.

The HOME_REG field is included in the System Parameters Message (SPM).




Power UP Registration

Power-up registration is performed when the mobile station is turned on. Power up and power down registrations are always required to be enabled for the network to be aware of the mobile station status.

Notes:The POWER_UP_REG field is included in the System Parameters Message (SPM). To prevent multiple registrations when power is quickly turned on and off, the mobile station delays 20 seconds before registering after entering the Mobile Station Idle State. The mobile station maintains a power-up/initialization timer. While the power-up/initialization timer is active, the mobile station does not make registration access attempts.




Power Down Registration

Power-down registration is performed when the user directs the mobile station to power off. The POWER_DOWN_REG field is included in the System Parameters Message (SPM).

If power-down registration is performed, the mobile station does not power down until after completing the registration attempt.

The mobile station does not perform power down registration if it has not previously registered in the system that corresponds to the current SID and NID.




Interfaces Objects

• The BTS is configured with a list of BSC units in the cluster. For each configured BSC, the BTS establishes an Abis connection.

• The list of BSC units shall be ordered in such a way that the first BSC in the list is recognized as the "primary“ BSC, which serves the calls for this specific BTS.

• All new incoming registrations and call originations (i.e., Access Channel messages) are routed by the BTS to its "primary" BSC.

• Although the BTS is connected to all the BSC units in the cluster, only the "primary" BSC is in charge of the call processing functions for the BTS.

• All other Abis connections to other BSC units in the Cluster are used for soft-handoff or for redundancy.

If an Abis connection to the first BSC in the list cannot be established, or if the Abisconnection fails, then the BTS uses the next BSC in the list as its "primary“ BSC. New incoming registrations and call originations (i.e., Access Channel messages) are routed to the new "primary" BSC (the second BSC in the list).

If the second BSC in the list fails, then the BTS selects the third BSC in the list, and so forth. Once the Abis connection to the first BSC in the list is re-established, the BTS starts using the first BSC as its "primary" BSC again. This mechanism provides some level of redundancy for BSC units. In case of failures, the BTS selects another BSC to route new incoming calls.




BSC List Table

Table of Abis connections includes an entry for each BSC, which is connected to the BTS under consideration. The first entry in the table is considered the "primary" BSC of the BTS, which is responsible for processing calls. There is only one table under Abis which is bscListTable




SNTP Table

Definition of the Simple Network Time Protocol (SNTP) interface parameters

The BTS uses the Time-Of-Day (TOD) and the 1 second signal to synchronize the CDMA system time. The TOD can be retrieved from an external GPS receiver (see parameter gpsPeripheral) or from an SNTP server in the local IP network.

If parameter gpsConnectedIndicator is set to gpsNotConnected(0), meaning that the external GPS receiver is not directly connected to the BTS, the BTS tries to retrieve the TOD from the SNTP server defined herein.

If the GPS receiver is not directly connected to the BTS so the BTS tries to retrieve the TOD from the SNTP server, but the IP address is set to 0.0.0.0, then the BTS will use the system time defined in systemTimeHigh and systemTimeLow. These parameters define the initial system time during the BTS initialization procedure when no external Time-Of-Day (TOD) source is used. These parameters are for debug purposes only, and should be used for special cases only.




Neighbor List Table

Neighbor list table for each individual sector in the BTS. Each entry in this table defines a specific neighboring cell of the specific sector. Every sector in the BTS has its own neighbor list table.




Commands

This page is used, as the name suggests, to issue commands on the Network Element.Commands apply only to the Network Element being managed.




Dynamic Parameters

• Those are divide into 3 groups:

1. OTF – “on the fly” Parameters2. Config Parameters3. Access Parameters

• Saving the config file is mandatory in order to permanent reserve the changes.

BTS Dynamic Parameters set of parameters that can adjusted during system operation without restarting the BTS.




OTF Dynamic Parameters

• fchMaxPwrRc4

• fchMaxPwrRc3

• fchMinPwrRc5

• fchMinPwrRc4

• fchMinPwrRc3

• dayltltmOfflpSec



• ecIoHhoTriggerThreshold

• ecIoHhoTrigger

• rtdCalibrationValue

• rtdHhoTriggerThreshold

• rtdHhoTrigger

• borderSector

• hhoTargetSectorNumber

• hhoTargetCellId

• hhoTargetMscId

• sectorAdministrativeState

• btsAdministrativeState

• logPointTable

• isBscAllowedPrimary

• bscAdministrativeState

• accChangeRandTimer

• sch16xGainOffsetFromFchRc4





• schFpcStepDownSizeRc4

• schFpcStepUpSizeRc4

• schFpcMaxPwrRc4

• schFpcMinPwrRc4

• fchStepDownSizeRc5



• fchStepUpSizeRc5



• fchMaxPwrRc5

Any change in those parameters effect immediately on the BTS behavior




Config Dynamic Parameters

• timingIncl

• nghbrFreq

• nghbrBand

• nghbrFreqIncl

• srchWinNghbr

• nghbrSearchPriority

• nghbrCellId

• nghbrSectorNo

• nghbrPn

• nghbrConfig

• srchOffsetIncl

• globalTxPeriod

• globalTxDuration

• globalTimingIncl

• useTiming

• freqFieldsIncl

• nghbrConfigPnIncl

• nghbrSrchMode

• pilotInc

• homeReg

• multNids

• multSids

• zoneTimer

• totalZones

• regZone

• analogNeighborListTableRowStatus

• analogNghbrSysAb

• analogNghbrBandClass

• neighborListTableRowStatus

• nghbrAccessHoAllowed

• nghbrAccessEntryHo

• srchOffsetNghbr

• nghbrTdPowerLevel

• nghbrPilotRecType

• addPilotRecIncl

• nghbrTxPeriod

• nghbrTxDuration

• nghbrTxOffset

UpdateConfigParams command is necessary In order to apply any change to those parameters.




Config Dynamic Parameters

• softSlope

• extChanList

• extGlobalRedirect

• priNghbrList

• globalRedirect

• tTdrop

• tComp

• tDrop

• tAdd

• rescan

• nghbrMaxAge

• srchWinR

• srchWinN

• srchWinA

• regDist

• baseLong

• baseLat

• regPrd

• regPrdInd

• parameterReg

• powerDownReg

• powerUpReg

• forNidReg

• forSidReg

• cdmaChannelListTableRowStatus

• channelFreq

• pwrRepDelay

• pwrPeriodEnable

• pwrThreshEnable

• pwrRepFrames

• pwrRepThresh

• rlgainTrafficPilot

• sdbSupported

• broadcastGpsAsst

• maxNumProbeHo

• accProbeHoOtherMsg

• accHoListUpd

• accessProbeHo

• accessHoMsgRsp

• accessHo

• nghbrSetEntryInfo

• pilotReport

• ecIoThresh

• ecThresh

• reselectIncluded

• maxNumAltSo

• dropIntercept

• addIntercept

Notes




Access Dynamic Parameters

• psist15

• psist14

• psist13

• psist12

• psist11

• psist10

• psist09

• numStep

• pwrStep

• initPwr

• nomPwrExt

• nomPwr

• auth

• maxRspSeq

• maxReqSeq

• bkoff

• probeBkoff

• accTmo

• probePnRan

• regPsist

• msgPsist

UpdateAccessParams command is necessary In order to apply any change to those parameters.




ACM Provisioning Overview

Notes




Alarm & Control Module (ACM)

ACM2

• In Macro iCell, ACM resides on the rear side of the RF Shelf (RFS)

• Notice the difference between ACM1, ACM2 and ACMJR

The ACM1 automatically communicates and obtains information from external devices from signals connected to the ACM1 ports. In addition, the 12 serial ports are used as console port accesses to internal rack devices such as the BTSs, BSC and the Ethernet switch.

ACM1 Digital Output port controls a CMOS input device between pin 2 and pin 3 of the Terminal connector.ACM1 Digital Input port accepts CMOS relay contact output or a CMOS output device on pin 2 and 3.




ACM Ports

• ACM1– 16 Digital Input ports– 8 Digital Output ports– 4 Analog Input ports– 12 Serial Data ports– 1 Ethernet port

• ACM2– RFS 1A, RFS 1B and RFS 2A, RFS 2B– RFS 1 and RFS 2– J1 to J10– S1 to S12– External I/O– Ethernet

ACM2 Connections Descriptions

RFS xA/B: SCSI connector for RFS signals containing serial ports, digital inputs and digital outputs to the RFS1 back plane (control and reset ACS/PA and initiate the socket between ACM and them)

RFS 1/2: 25-pin cable connectors for analog signals to RFS1 and RFS2 back plane (read analog information (power level, etc.))

J1 – J10: Each has one digital output and three digital inputs (alarm input from BSC and BTS)

S1 –S12: RS-232 serial connector for device consol access

External I/O: SCSI connector carrying digital inputs and digital outputs of customer external alarm interface




External Alarms Configuration

• Telnet to ACM and login as root• Go to directory /usr/local/acm/etc/ and list the file AcmConfig.csv• Make a backup copy of the file• Open the file using vim• Verify that SNMP IP address & port number are correct• External alarm can be defined using the following format:

DI<port>=<Severity>,<ActiveState>,<Type>,<ProbableCause>,<Description>

• Get the ACM process number by running “ps -ef |grep acm” and note the PID down

• Stop the application by “kill -9 pid”• Start the ACM application by “/usr/local/acm/bin/acmd”

Related parameters in AcmConfig.csv file:snmpip: IP Address of the SNMP Manager (OMC)snmpport: Port used (e.g. 2162)

Note that ACM status can be also checked from the BTS Element Manager cdma1xcdma cdmaSectorInfo sectorInfoTable sectorRfsOperationalState

05 icell iic notes

Documents