MOTOROLA equipment commonly used commands

MOTOROLA equipment commonly used commands

Reminder: 使用 Ctrl + F to find you to be content or instructions. please press Ctrl + F to find what you wanted.

MOTOROLA equipment:

1.GSM 900 common command set:

1) BTS OR BSC commonly used commands

> Disp_site see BTS station number

> Disp_act # see warning

> Disp_cell_s # to see the base station call each sector the situation is accounted for on the channel (3 different sectors of the BCCH FREQ)

> Disp_equ # see if the station data

> State # dri * * look at the carrier frequency is up, when the ALARM BAR is NONE, that enter the state of BU

> Disp_rtf_ch # * * look at the occupancy status of TIMESLOT

> Chg_l (3stooges 4beatles) change the password to enter the LEVEL2, LEVEL3.

> Lock # dri (msi mms gclk ksw, etc.) * *

lock # pchn * * # (ts): lock timeslot

> Unlock # dri (msi mms gclk ksw, etc.) * *

unlock # pchn * * # (ts): unlock timeslot

> Ins # dri (mms msi gclk ksw, etc.) * *: to enter the service state.

> State # dev (dri msi mms gclk, etc.) to see the state

> Disp_p # read processor state.

> Disp_bss look at the code (BCCH transmit power).

> Disp_cal # dri * * see carrier frequency linear.

> Disp_equ # dev (rtf dri msi gclk, etc.): see devices data

> Disp_mms_ts_usage # * * see transmission.

> Reattempt_pl # 0 tone clock (when GCLK PHASE LOCK FAIL appears)

> Iir_mod 7 30h: upload object code from mcu to PCMCIA card. (To operate the MMI-EMON%)

> State 0 site * *: see all sites' status of BSC.

> In the BSC or BTS RESET, press CTRL + N into the MMI-EMON% state, see GPROC process, and then CTRL + N retreat out.

> Rlogin 1 0115H Login BSC 0115H PROCESSOR, press CTRL + D to exit BSC (MMI-EMON% in the next login).

> State 0 rsl * * to see whether the communication link for all SITE, General for the 64K LINK.

> Disp_equ 0 path # 0 SITE of the MMS port to see the path.

> Status 0 on or status_mode 0 on / off on / off the alarm status of the BSC.

> Chg_rtf_freq <freq> <site> 0 0 located within the district of the frequency carrier.

> Swap_devices # <old device> * * <new device> * * Switch primary / backup devices.

> Disp_neighbor <src_cell_desc> [<neighbor_cell_id> | "all"]: display information of a specific neighbor cell or all neighbor cells.

> Device_audit: audit test and display status of audit.

> Disp_bss_conn: display which RXCDR MMS is connected to which BSC MMS.

> Disp_time chg_time <year> <month> <hour> <minute> <second>: New station irrigation data, should CHANGE TIME to the current time, otherwise they will LOADING FAIL.

> Disp_cell MNC LAC CI: LOOK SITE'S CELL'S BSAE DATA. (+ ALL)

> Disp_ele to see parameters of the device can change parameters (such as: opc dpc cell_number, etc.) Example: disp_ele opc 0

> Chg_ele change device parameters.

> Status_mode

Command: status_mode <location> [<location> ...]

[<mode>]

Function: Display or enable / disable device or function status notification

Security Level: Can be executed from any security level.

Sysgen Mode: Can be executed in or out of sysgen mode.

<location> "bsc" or 0 Specifies the BSC.

1 to 120 Specifies a BTS.

"All" Specifies all locations.

"All" cannot be part of a list.

<mode> "off" disable functioning.

"On" enable functioning.

Example 1: Enable CA state change status notification for site 6.

status_mode 6 on

Example 2: Display current status modes for sites 3 and 5.

status_mode 3 5

Example 3: Disable status notification for all equipped sites.

status_mode all off.

> Dynet_retry_time: The dynet_retry_time parameter specifies the amount of time, measured in milliseconds, that the BTS waits for a response from the BSC when the BTS requests a terrestrial backing source. The value for the parameter depends on whether satellites are used to connect the BSC to the BTS.

* Systems that do not use satellites should use the minimum retry value of 150 milliseconds.

* Satellite systems should use a value 1.2 seconds greater, such as 1.35 seconds. Satellites introduce a one way delay of 600 milliseconds.

The retry value affects call setup and handover times. This parameter only applies to sites that support dynamic allocation.

> Hdsl_modem_setting: This parameter changes the setting of an integrated HDSL modem. The possible settings are slave and master.

2) DATABASE adjustment <chg_element>

> Rxlev_min_cell This is a HO parameter, into the adjacent cell is used to indicate the most low value NEIGHBOUR LIST.

> Max_tx_bts This is a base station transmit power control parameters, each of said OFFSET 2dB attenuation.

> Ho_margin the parameters are set when the ADD NEIGHBOR, use it to control the adjustment of the signal caused by switching threshold level value.

> Ms_max_range This parameter is used to control traffic base station coverage, the range of 0-63, each OFFSET said 0.5KM.

> Modify CELL RTF FREQUENCY (BCCH), should be under in CONFIGURATION BSS-RTF directory changes.

3) Calibration GCLK COMMAND

disp_eq state # gclk * * disp_ele phase_lock_gclk <location>

chg_ele phase_lock_gclk <flag> <location> clear_gclk_avgs <location> <gclk id>

<Flag --- 0 or 1 (phase_lock_gclk funcation off or on), location is cell id .>---- incell

mcell mcu gclk calibration

* At the MMI-RAM 1015 prompt type:

gclk_cal_mode

The gclk_cal_mode command is used to tell the sync function and MCU software that a calibration is to be performed.

* The user will then be prompted with the following:

Frequency Counter Connected, Enter y when ready, or a to abort test y

If the user replies with anything other than y, the command is aborted, and the calibration mode exited.

* Adjust the OCXO control voltage using the + / - and 0 to 3 keys until the measured frequency

is exactly 8000,000000 Hz.

* Save the results by typing s

* To calibrate the OCXO, gain, enter the measured frequency value from the counter after the value has settled in response to the MMI prompts.

* On completion the user should ensure that the Calibration Gain is between 0 and 1.5. Values other than this may indicate a poor OCXO, or an error in performing the procedure. The most common error is in reading the counter when locating the decimal point by eye. (3.865560e-01)

4) handover algorithm

* Type 1: adaptive handover

Adaptive handovers have been implemented for power budget handovers, uplink and downlink quality handovers, and uplink and downlink level handovers.

chg_element adap_ho_pbgt, chg_element adap_rxlev, etc.

* Type 3: arroud the corner handover

The current type 3 handover algorithm is based on absolute level thresholds and does not take the changing transmit power from the BTS into account. Therefore, the handover point for type 3 neighbours varies depending on the dynamic status of the transmitted power. The trigger point may therefore be different for different carriers. To prevent this variation, this optimization forces the type 3 handover threshold to be in terms of path loss instead of absolute level.

chg_element pathloss_type3_ho

* Type 5: hand-down calls from macrocells to microcells

Since hand-downs are based on a relatively high threshold (based on the outdoor situation) a hand-down from a macrocell to a microcell might not take place, weven though the microcell is the correct cell for the call to be in. To avoid this problem, this optimization causes the type 5 handover algorithm to ignore the level threshold when the power budget between the serving cell and the neighbour cell meets a new, settable, handover margin.

Example:

To set the new type 5 handover margin in neighbouring cell 0010112 of cell 0010114 to 10, enter the following:

modify_neighbor 0 0 1 0 1 1 4 0 0 1 0 1 1 2 ho_margin_type5 10

Note:

(1) is 155M Optical fiber bundle, that is a bunch of fiber optic cable can carry 77 SITE.

(2) Full Rate Traffic Channel traffic (blocking rate of 2%)

District prepared to receive machine 1234567

Business Channels 7142230374553

Volume of business "ERL" 2.9 8.2 15 22 28 35.5 43

Channel utilization 0.41 0.57 0.68 0.73 0.76 0.79 0.81

(3) Devices as used in commands

BSP: BASE SITE PROCESSOR (AT BSC) BTP: BASE TRANCEIVER PROCESSOR (AT BTS)

CBL: CELL BROADCAST LINK CBUS: CLOCK BUS

CIC: CIRCUIT IDENTITY CODE DHP: DIGITAL RADIO HOST PROCESSOR

DRI: DIGITAL RADIO INTERFACE EAS: EXTERNAL ALARM SYSTEM

MTL: MESSAGE TRANSFER LINK PBUS: PROCESSOR (MCAP) BUS

PCHN: PHYSICAL CHANNEL RSL: RADIO SYSTEM LINK (ABIS)

SBUS: SERIAL BUS TBUS: TDM BUS

TDM: TIME DIVISION MULTIPLEX XBL: RXCDR TO BSC FAULT MANAGEMENT LINK

(4) MCELL SITE in the T43 # J1, J2 for the base station of the "0" mouth, J7.J8 to "1" port; INCELL SITE T43 # J13.J14 for the base station in the "0" mouth, J16.J17 "1 "port.

(5) power: the power to ensure that each sector of the same; urban general 17.5W 15W suburbs 18W; ANT emission generally 100W, 50dBm (room gain)

TCU in the TX POWER generally 42dBm .17 w; ANT reflected power can not be greater than 0.3W.

(6) adjusting the PIX (EAS external alarm) when, TCU should already be BU.

(7) TOUBLE SHOOTING

* When in a range of mobile phone base station can not incoming, not outgoing, you can reset to the carrier frequency.

* When the base station SDCCH average occupancy within the sector for too long, and CHANNEL_RECONFIGURATION_SWITCH feature is turned on, as well as obstruction.

Can be turned off and reset the CHANNEL_RECONFIGURATION_SWITCH all the carrier frequency, which returned to normal.

(8) IADU SWITCH

Only MCELL base station EXT1, EXT2 port is used when, IADU SWITCH only use it to expand a DLNB only in that one on the set SWITCH "ON"

For signal transmission.

(9) Antenna lightning: a lightning rod antenna 45 'to avoid the cloud-to-under, but could not avoid the lightning, it is the best in 30' the next.

(10) The command tcu_clock 0 forces the TCU onto fibre link A for its reference clock source

(11) DLNBs obtain a +12 V DC supply from RX2 of the TCU_B

(12) Handover / Power control feature implemention

Handover and power control features in the BSS affect the cell sites, Features which affect the GSR4 BSS software include:

* Receive quality measurements processing.

* Handover decision algorithm (algorithms).

* Microcellular handovers.

* SDCCH handovers.

* Directed retry / congestion relief.

* Missing report.

* Power control.

* Fast initial MS power down.

* All channels at full power.

* Handover performance statistics enhancements.

* RXQUAL handover microcell enhancements.

* BA lists.

* Congestion relief.

(13) The BSS supports up to 100 BTS sites, 250 cells, 384 carriers and 1920 trunks. This feature increases the LCF capacity on a GPROC2. The MTL limit has been increased from a maximum of one MTL, on an original GPROC, to two MTLs on a GPROC2. The number of BTS sites is also increased from a maximum of eight BTS sites (15 RSLs), on an original GPROC, to 15 BTS sites (29 RSLs) on a GPROC 2. ----( GSR4 ). At 2% blocking on the air interface, this corresponds to approximately 820 Erlangs of traffic, or around 33 000 subscribers (at 25mE per subscriber ).---( one BSC)

(14) The CBL (CELL broadcast link) can be connected directly from the X.25 network into the BSC via an E1/T1 link. Alternatively, it may be connected via a 64 kbit / s cross-connect in the RXCDR.

(15) GCLK MODE

There are four GCLK board operational modes:

* Free run.

When a GCLK is inserted into the digital cage (or on power up), a 30 minute warm-up period is required for the ovenised crystal oscillator (OXCO) to reach the correct operating temperature. During this time the GCLK is in free run mode and the input to the DAC is set to 80 (hex). The value 80 (hex) cannot be changed. The OXCO in free run mode will produce a clock output accurate to 0.05ppm.

* Hold frequency.

The hold frequency mode is used to maintain a specific clock frequency in the event that the 1.544 MHz or 2.048 MHz reference should fail. This mode uses the last 8 bit word output from the ADC to set the DAC. The hold frequency mode is a transitional mode (typically 10 seconds) until the set frequency mode is activated by the software.

* Set frequency.

The set frequency mode allows the software to use the LTA to set the DAC to control the output of the OXCO during loss of the 2.048 MHz or 1.544 MHz reference signal. (This is after the transitional hold frequency mode).

* Closed loop.

Within the closed loop mode there are two sub-modes or states:

# The acquiring frequency lock state is the operating condition where the GCLK PLL output is converging towards the long term frequency of the E1/T1 link. The time spent in this state is dependant on the hardware revision level of the GCLK board. Once this state is reached (that is, the output is within GSM specifications) the second sub state is activated.

# The frequency lock state is again dependent on the GCLK hardware revision level, and is used to confirm that the GCLK output is stable within the GSM specification for the set period (2 / 10 minutes).

(16) HDSL Application

* The connections supported by the HDSL interface are best applied in microcellular applications where a relatively large number of sites that are to be interconnected are located in a small area.

* HDSL modems either operate as a Master or as a Slave. Each HDSL link requires one Master at one end and a Slave at the other end. External Remote HDSL Modems can provide a HDSL to E1 conversion for connecting the HDSL to other network equipment. These External Remote Modems are controlled using the HDSL link from the NIU, and are required to be Slave modems. Internal HDSL modems default as Master on MMS0 and Slave on MMS1, enabling daisy chain BTS configurations to be realised.

The NIU automatically selects the type of interface to use, either E1 or HDSL, dependent on which interface has been utilized.

2.get data

1). Get 002 code

usr / gsm / ne_data / dbroot /

(1). BSS / BSS specific

(2). RXCDR / RXCDR specific

2). Get performance data

usr / gsm / ne_data / pm_reports / tabular

username: mtoptr

password: mt1999

QZ_UNICOM

username: omcadmin

password: Qmcadmin

msg_send 80 0 0 0 1978h

SO get performance data (to a: floppy)

XTERM interface in the input volcheck - A plate to confirm the existence of OMCR.

cd / usr / gsm / ne * / pm * / de *-- all the columns into the PM REPORT items.

mv file name / f * / f *-- PM REPORT transferred to the A disk is used to copy PM REPORT CP file name / f * / f * command.

SO set performance referance

In PERFORMANT interface operation, set the output data type and time.

Note: (1) omcr reboot operation: stop + a and then enter boot. (2) cd f * / f * or ls f * / f *: look a: disk's file list.

3.DATA SETUP

1). Site data structure

equ site

equ cab

add_cell

bsic =* *

ccch_conf = 0 (non_combine max_number_sdcchs_preferred = 8 <multi>)

or ccch_conf = 1 (combine number_sdcchs_preferred = 8 +1 / 2 * 8 <multi>)

eq 0 path

eq 0 rsl

eq # rtf

eq # dri

add_neighbor

2). Del site data stage

del_n all 4 6 0 0 1 LAC CI

del_n 4 6 0 0 1 LAC CI all

lock site #

lock dri * *

uneq dri * *

uneq rtf * *

lock rsl

uneq rsl

uneq path

del_cell

uneq site

3). Batch data process

* For data

* The data to be copied to the directory batch

volcheck

cd / f * / f *

ls ----- view all filename

cp filename / usr / gsm / groble / batch

* Access to relogin, click btsdata where bsc, enter the batch

* Click the necessary directories, find and click the filename, and then determine the output directory

* Click on the run, but also can change the data here

Note: 1) hardware device: cabinet, cage, EAS, IAS, processor (gproc bsp csfp), gclk, ksw, lan, msi, TDM

2) sofeware function: BTF, LCF, OMF (OMF GPROC Functions)

3) logical links: RSL, PATH

4) Radio Frequency: RTF, DIR, CELL, FREQHOPSYS, SMSCBMSG, NEIGHBOR, HANDOVER CONTROL, POWER CONTROL

INTERFERLG (INTERFERENCE algorithm-interference calculation rule)

5) Code object

The Motorola BSS software is made up of a number of different files, called Code Objects, which are downloaded into a site by a variety of methods. These downloaded Code Object Files are received by all the processors resident in a cabinet and stored in the processor RAM. Each Code Object File has the capability of becoming a system application process, such as the BSS radio subsystem software and BSS call processing software; exceptions include the:

* Database.

* Executive.

* Object list.

* Options database.

* Library files.

With the exception of the Executive, these Code Object files are read-only.

6) layer 1: Physical channel hardware layer

layer 2: protocol layer

layer 3: Application layer

7) Channel reconfiguration

* Conditions for TCH to SDCCH reconfiguration to occur:

# Number of SDCCHs after reconfiguration must not exceed max_number_of_sdcch.

# Idle number of free SDCCHs must be lower than sdcch_need_high_water_mark.

# Current number of idle TCHs must be greater than tch_full_need_low_water_mark.

* Conditions for SDCCH to TCH reconfiguration to occur:

# Total number of SDCCHs after the reconfiguration must not be lower than number_sdcch_preferred.

# Present number of free SDCCHs must be greater than sdcch_need_low_water_mark.

# Sdcch_need_low_water_mark number_sdcch_preferred

8) BSC & XCDR Database note

* Equip bsc msi MSI should pay attention to the type (0-MSI ,1-XCDR ,2-GDP) and the MSI properties (cases) are:

modify_value 0 nbit 0 mms 35 0 0

modify_value 0 ber_oos_mon_period 1 mms 35 0 0

modify_value 0 ber_restore_mon_period 6000 mms 35 0 0 (a MTL of the MSI board MMS port should be 1200)

modify_value 0 phase_lock_duration 0 mms 35 0 0

modify_value 0 mms_priority 0 mms 35 0 0 (with OML's MMS port should be 255 <main> 254 <Preparation>)

* It should be noted bsc - xcdr between the link and bss_conn (disp_link, disp_bss_conn)

* Equip bsc msi occur after "remote alarm oos device" can use the command "chg_ele mms_config_type 0or1 0

Then reset the appropriate board on it.

* In XCDR after the equip bsc msi should be a corresponding increase in channel (add_channel)

4. Adjusted test and analysis

1). Drive test

- DRIVE TEST entire urban areas, test, test and optimize routes before the test to be exactly the same route.

- Each phone hold for two minutes, 10 seconds apart between the two phones.

- EXPORT by TEMS in the LOG file into the FMT file.

- The FMT files into the corresponding through TMS2N97 RXLEV, RXQUAL, TA, TXPWR file, TEMSMATE software into RXLEV,

RXQUAL, TA, TXPWR diagram, with different colors represent different values.

- LOG file with the FICS software for statistics, to STA file.

2). Get the system adjusted OMC statistics - PERFORMENCE DATA.

3). Based on the above test data, the adjusted system analysis, evaluation.

5. Extracurricular books for reference

1) frequency-hopping unit

According to GSM recommendations, the base station's frequency-hopping radio channel for each physical channel is based, therefore, the base station system, each transceiver (TRX)

Should be based on physical channel used for communication in each time slot on a different frequency hopping scheme according to the jump. Realize there are two frequency hopping scheme, base-band

Frequency hopping and frequency hopping synthesizers. But the switching frequency hopping synthesizers for too long, does not meet the requirements of GSM frequency hopping (less than a switching guard time slot

About 0.3 microseconds), so the base station system uses GSM baseband frequency hopping, and its basic principle is the carrier frequency in the frame unit and between units by adding a time slot for the

Based exchange unit, to a time slot to the corresponding wireless signal switching frequency up to achieve frequency hopping.

FH unit consists of a switch module, the main processor and the time from the unit. Switching module to allow according to the control from the processor unit of a frame

A time slot to send the exchange of information on request to the appropriate carrier frequency. Timer unit is based on the clock from the main unit (MCLU) to the frame clock on the exchange

Time interface to read and write, while the main processor unit is receiving from the master clock (MCLU) to the frame number (FN) and from the OMU (operation and maintenance unit)

to the hopping

Serial number, the exchange calculated for each time slot interface configuration parameters, to control the switching module from the processor to achieve the exchange of control.

2) frequency master clock unit (MFGE / MCLU)

GSM provides recommendations, BTS baseband part of the wireless segment and should use the same reference clock source for the wireless part and the baseband part of the same frequency

Time accuracy. So each base transceiver station BTS configuration of two frequency generator unit as a primary backup, it uses oven-controlled crystal oscillator (OCXO)

To generate the reference frequency source.

6.OMC-R

1) The Scaleable OMC system configuration is shown in Figure 1-2. It is suitable for GSM networks

with low-end (5k) or high-end (20k) traffic channels (TCHs). Each processor is a complete UNIX

system, comprising the following:

* A System Processor.

* Several MMI processors (which also provide colour operator workstations).

* A GUI Server that is configured as an MMI.

* A laser printer

2) The OMC MMI has two user interfaces to operate the OMC system:

* The Graphical User Interface (GUI).

The GUI presents the user with a Front Panel displaying icons that represent all the

modules of the OMC.

* Command line interface.

The UNIX-based system utilities are executed at the command line of an Xterm window.

3) The OMC performs the following functions:

* Direct management of BSS and RXCDR and the links between them.

* Management of the NE devices associated with the links (on the RXCDR side) between the

MSC, the BSSs and RXCDRs. This is all done using the O & M data packets sent to / from the NE.

* Monitoring of events and alarms, performing fault handling, NE re-configuration, NE

software uploading and downloading, and performance data collection and reporting for

all the NE under its control.

* Provides a centralized facility for network management of up to 64 NEs with up to 20,000

traffic channels for the Scaleable OMC.

4) Performance note event

(1) Performance Management (PM) allows the operator to produce and collect performance related

data from Network Elements (NEs), and present the information in report format. PM provides

the operator with the information necessary to perform the following network management

functions:

* Monitoring of network traffic and equipment loading.

* Quality of service measurement and analysis.

* Efficient network management and planning.

* A historical record of network performance.

* Device management of statistics for any cell under OMC control.

* Fault management.

(2) performance management

Performance data is generated at the BSS and the RXCDR, and stored as a PM data file.

Performance measurements include traffic measurements within the telecommunications

system (both user and signalling traffic), quality of service measurements (delays in

call setup) and availability measurements (the beginning and end times of service

unavailability). At 30 or 60 minute intervals (defined by the user), the PM files are

sent to the OMC. The OMC processing software (known as the parser) then converts the

data in the files into raw statistics suitable for storing in the INFORMIX database at

the OMC.

(3) The selections window (performance)

The Selections window is the starting point for the creation of a new report, or the running of a previously saved selection with or without modifications, and for performing device management operations.

(4) custom statistics manipulation (self-defined statistical operation)

A summary of how a new custom statistic is created is described below:

* Select Custom Statistics Manipulation from the Performance Management window, the Custom Statistics Manipulation window is opened

* Select File - New. The Statistics Manipulation window is displayed.

* Select the required device from the Device Type menu. Raw Statistics can be selected using the left mouse button. The relationship between the selected Raw Statistics and the Custom Statistic is displayed within the Formula list box.

* To create a Custom Statistic formula, select the required Raw Statistic and the required formulae relationships from the buttons located between the two list boxes in the centre of the window.

* Enter a suitable description in the Description field located at the end of the window.

* Select File - Save As from the menu bar and, when prompted, enter a name for the new custom statistic

5) configuration management

Configuration management at the OMC provides a centralized facility for performing the following tasks:

* Network configuration.

* NE software load management.

* NE software download:

* Conventional download (monitoring and aborting only).

* CSFP (Code Storage Facility Processor) download (initiating, monitoring and aborting).

* Supplemental download.

* NE operational database backup (monitoring and aborting only).

* Network re-configuration.

6) load management

* The database to be downloaded must be loaded using the activate_db script. The database can be loaded onto the OMC using the load_db script and then moved into the CSFP directory using the activate_db script.

* Swap codeload

The Swap CodeLoad option causes a fast reset of the NE. SITES that contain a CSFP device boot from the software installed at this device. SITES that do not contain a CSFP device download software from the BSC and boot with this new software. The result of this operation is displayed on the status line of this form. The progress can be monitored on the CSFP Status form. To swap a code load, select the required NE from the Software Load Management window, then select CSFP - Swap Code Load from the menu bar. A dialogue box is displayed, requesting confirmation. The dialogue box also displays the load name and load version that will be installed at the BSC. On clicking OK, the changes are executed.

* Download monitoring

The main methods used to monitor the CSFP download are:

Monitoring the download events via the Event window.

Monitoring the progress of objects downloading via the Download Status window.

* Fallback (return) to backup database

The fallback_db utility automatically performs a fallback to a specified backup database for a specific NE (<NE_Name>).

* Database status

The following list details the status of the operational database in the OMC and BSS.

A backup of the active database and a fallback database are maintained at the OMC for each node in the network.

A BSS configuration database uses approximately 4.5 Mb of memory.

All backup databases on the OMC are automatically compressed to save disk space, this reduces the size to 250 Kb.

Backup databases for NEs are contained in backup directories, (dbDDMMYYYYhhmmss), in $ DBROOT / NETYPE / NEspecific / <NE_Name>.

* DataGen

DataGen is a GSM product used to create BSS databases off-line. DataGen can store past, current, and future versions in an Informix database. These databases can be transferred to the OMC, then they are downloaded to the live BSSs. DataGen runs on its own SPARC and can be integrated with the OMC if they are both on the same LAN.

DataGen is generally used to make major changes to a network, for example, upgrades to the BSS software, frequency replans, and network expansion.

(See also: adding a BSS can be entered into the CM MIB by running an Audit procedure; smaller changes, such as changing parameters, can be performed directly via Detailed Views.)

* The batch_rlogin utility (Remote login window)

This facility uses a command file to execute a sequence of BSS MMI commands. The command file is a text file containing a sequence of BSS MMI commands, which can be sent to the BSS and executed at any convenient time. Batch is available both as a GUI and as a utility, batch_rlogin, which can be run from the UNIX command line.

The batch_rlogin utility enables the operator at the OMC to execute multiple BSS MMI commands from a pre-edited file via a remote login connection to a NE (BSS or RXCDR). The batch_rlogin utility has a user interface which can be selected from the RLogin window . Alternatively it can be run as a Motorola utility, batch_rlogin, which can be run from the UNIX command line.

The batch window allows the user to select, view, edit and run batch files.A template file is available to allow easy access to add BTS on line.

The contents of the BatchInput file are:

# Demonstration (demonstration) of batch facility

# Command file

disp_time

state 0 OML 1 0 0

# End of commands

************************************************

This example describes the KSWX fiber optic connections for a standard 4 cage expanded BSC with redundancy. The chg_ksw_config commands for configuring the expanded setup are described.

CAGE 0:

KSW 0 0 and KSW 0 1 (KSW Pair 0) are equipped in CAGE 0

KSWX in slot U21 is connected to KSWX in cage 1 slot U21






CAGE 1:

KSW 1 0 and KSW 1 1 (KSW pair 1) are equipped in CAGE 1







CAGE 2:








CAGE 3:








The commands for configuring the expansion are:

chg_ksw_config 0 0 0 1 2 3




************************************************** ******

The RSS includes five processes:

1.Configuration and fault management.

2.Layer 1 interface.

3.Layer 2 protocol.

4.Abis interface.

5.Handover Detection and Power Control

CONCENTRIC CELL HANDOVER AND ASSIGNMENT ALGORITHMS

February 6, 1996by G Eastwick & J Hopkinson

Introduction

With the rapid growth of cellular systems, such as time division multiplexed communication systems, it is becoming increasingly difficult to provide sufficient capacity in busy city centres using conventional frequency reuse techniques. Bearing in mind the limited (and fixed) spectrum available to each communication system operator, novel frequency planning techniques must be employed by system operators if these operators are to provide sufficient capacity to support high volumes of traffic (per square kilometre) in densely populated (city) environments. One such technique is the use of a concentric cell system in which different frequency re-use patterns may be employed between a macro (upper) level and a concentric (lower) level. However, in order to use the concept of concentric cells effectively, new handover and assignment algorithms need to be developed.

This paper describes an improved handover and assignment algorithm.

Concentric cells

A concentric cell will have frequencies assigned to it that exhibit good interference isolation when a mobile user is closely located (proximal) to a base station in a coverage area. However, at the limits of the coverage area, these frequencies will suffer severe interference and will therefore be unusable. As such, the allocation of traffic to these "carrier" frequencies needs to be carefully controlled to ensure that these carriers are only used at acceptable levels of C/I.

Handover and Assignment Algorithm

When using concentric cells (or a system employing low power transmission in the vicinity of a base station), inner cell carriers are used for mobile units closely located to a base station, while outer cell carriers are used for the more distantly located mobile units. It is therefore necessary to ensure that a mobile unit is not handed to an inner cell carrier when that mobile unit is in a pool of coverage away from the base station, otherwise the mobile unit could suffer co-channel interference. This problem is illustrated in FIG. 1 below.

Proposed Algorithm

The concept behind the proposed algorithm is to estimate co-channel interference likely to be experienced by a mobile unit (at its current position) on an inner cell carrier in response to signal level measurements for outer cell channels that are known to possess co-channel inner cell carriers (frequencies). This technique is possible since the inner and outer cell carriers share the same antenna, and thus the signal level on the inner cell carriers can be directly determined from measurements of the outer cell carriers. One possible algorithm is given below:

Check if the radio signal level from the serving cell exceeds the GSM parameter (RXLEV_ACCESS_MIN + X), where: RXLEV_ACCESS_MIN is the minimum allowable received signal level at a mobile unit required for access to the communication system through a base station (as specified in GSM rec. 5.08) and X is an additional signal level margin defined by a system operator and is specified such as to require a mobile unit to have a stronger radio signal level that the minimum level specified in GSM rec. 5.08); and

If the radio signal level of the serving cell exceeds the linear average signal level of all specified neighbouring cells by an amount Y (where Y is an operator definable margin similar to X), then a handover/assignment is allowed to take place to a proposed inner cell because the very strong radio signal level measured at the mobile unit indicates that the mobile unit is in close proximity to the base station. As will be understood, the specified neighbouring cells will be those cells with inner cell frequencies likely to give co-channel interference to the proposed inner cell.

In mathematical form, a handover/assignment to the inner cell carrier is triggered if:

Serving cell radio signal level > RXLEV_ACCESS_MIN + X (eqn. 1)

where X is the additional signal level margin defined by a system operator; and

(eqn. 2)

where: Y is the operator definable margin; an ith Neighbour is a neighbouring cell known to possess a co-channel inner cell carrier; and all levels are measured in dBm.

Summary

This proposed algorithm will therefore prevent a mobile unit handing into (or being assigned to) an inner cell/carrier if that mobile unit is likely to suffer from interference from nearby co-channel (inner) cells. The algorithm can be also used to effect a handover from the inner cell to the macro level before interference is experienced. As such, the algorithm enables a more aggressive frequency reuse pattern to be established for the inner (concentric) cell frequencies and hence increases a volume of traffic that can be carried by a network (whilst retaining the same number of frequencies and site locations).

Documents

MOTOROLA equipment commonly used commands