EFT CHECK

Document number: DS/BSS/APP/0004

Document issue: 07.01 / EN
Document status: Standard
Date: 11/Aou/2003

Copyright

2000 Nortel Networks, All Rights Reserved

Printed in France
NORTEL NETWORKS CONFIDENTIAL:
The information contained in this document is the property of Nortel Networks. Except as specifically authorized in
writing by Nortel Networks, the holder of this document shall keep the information contained herein confidential
and shall protect same in whole or in part from disclosure and dissemination to third parties and use same for
evaluation, operation and maintenance purposes only.
The content of this document is provided for information purposes only and is subject to modification. It does not
constitute any representation or warranty from Nortel Networks as to the content or accuracy of the information
contained herein, including but not limited to the suitability and performances of the product or its intended
application.
The following are trademarks of Nortel Networks: *NORTEL NETWORKS, the NORTEL NETWORKS corporate
logo, the NORTEL Globemark, UNIFIED NETWORKS. The information in this document is subject to change
without notice. Nortel Networks assumes no responsibility for errors that might appear in this document.
All other brand and product names are trademarks or registered trademarks of their respective holders.
EFT CHECK
DS/BSS/APP/0004 07.01 / EN Standard 11/Aou/2003 Page 3/27
PUBLICATION HISTORY
VERSION DATE COMMENTS AUTHOR
01.01 / EN 28/04/97 Creation
T. Portois
03.01 / EN 05/04/98 Update for V11 release
T. Portois
04.01 / EN 09/04/99 Update for V12 version
VT. Chu
05.01 / EN 01/03/01 Update for V13 version
S.Gouverne
05.02 / EN 29/01/01 Fix CR Q00216710-01
S.Gouverne
06.01 / EN 08/02/02 V14
S.Gouverne
07.01 / EN 11/08/03 V15
S.Gouverne

EFT CHECK
DS/BSS/APP/0004 07.01 / EN Standard 11/Aou/2003 Page 4/27
CONTENTS
1. INTRODUCTION.........................................................................................................................5
1.1. OBJECT.................................................................................................................................5
1.2. SCOPE ..................................................................................................................................5
1.3. INTERVAL...............................................................................................................................5
1.4. SYSTEM IMPACT .....................................................................................................................5
1.5. CHECK RESULT REPORT..................................................................................................5
2. RELATED DOCUMENTS............................................................................................................6
2.1. APPLICABLE DOCUMENTS........................................................................................................6
2.2. REFERENCE DOCUMENTS .......................................................................................................6
3. GENERAL DESCRIPTION..........................................................................................................7
3.1. PLEASE READ CAREFULLY.......................................................................................................7
3.2. PREREQUISITES................................................................................................................7
3.3. RESOURCES..........................................................................................................................7
4. OPERATION DETAILED DESCRIPTION ...................................................................................8
4.1. UPGRADE OPERATION SEQUENCE TABLE..................................................................................8
5. SHEETS......................................................................................................................................9
6. ABBREVIATIONS & DEFINITIONS..........................................................................................17
6.1. ABBREVIATIONS..............................................................................................................17
6.2. DEFINITIONS....................................................................................................................21
6.3. TYPOGRAPHIC CONVENTIONS................................................................................................25
6.3.1 GENERAL CONVENTIONS ...............................................................................................25
6.3.2 INTERACTIVE TERMINAL SESSIONS .................................................................................25
6.3.3 INTERACTIVE GRAPHIC SESSIONS...................................................................................26
6.4. SEQUENCE TABLE CONVENTION.............................................................................................26

EFT CHECK
DS/BSS/APP/0004 07.01 / EN Standard 11/Aou/2003 Page 5/27
1. INTRODUCTION
1.1. OBJECT
This procedure describes the way to run the EFTs DELIVERY check tool. This tool allows to check at
any moment, the EFTs DELIVERY's consistency between the OMC-R and the BSC. This tool
provides only a check and doesnt perform any change in the OMC-R or BSS configuration. It gives
a report showing all detected errors or warnings about EFT DELIVERY consistency.

1.2. SCOPE
This procedure is applicable from V15 OMC-R version.
1.3. INTERVAL
Several factors determine how often you should perform this procedure on your site, for example :
Before/after the OMC-R upgrade.
After a BSC disk replacement.

You must perform this procedure any time you have got EFTs DELIVERY consistency problems on
the BSS.

1.4. SYSTEM IMPACT
The circular file for observation are closed tehn re-opened, if the OMC-R is running.
This procedure can last several hours when it is launched to check all the BSC EFTs DELIVERY ,
depending on different factors (number of BSC, network traffic).

1.5. CHECK RESULT REPORT
The check tool provides on each machine two data sources for the check result report :
Screen output (main check points status results).
Log file (main check points status results, with explanations):
/var/local/oam/ds_checkEft.log

The check tool gives a result on each check point. Messages are self-explanatory and can have four
status :
SUCCESS (no error detected).
ERROR (major error detected).
WARNING (minor error detected).
INFO (information given when a test was not performed).


EFT CHECK
DS/BSS/APP/0004 07.01 / EN Standard 11/Aou/2003 Page 6/27
2. RELATED DOCUMENTS
2.1. APPLICABLE DOCUMENTS
(none)

2.2. REFERENCE DOCUMENTS
(none)


EFT CHECK
DS/BSS/APP/0004 07.01 / EN Standard 11/Aou/2003 Page 7/27
3. GENERAL DESCRIPTION

3.1. PLEASE READ CAREFULLY
The utmost care was taken to prevent any unexpected event to occur during this procedure. However,
nothing on earth is 100% secure. Thus, if you feel you have to cope with a problem or a situation the
procedure does not explicitly or accurately deal with, call for help (according to your level of
expertise).

3.2. PREREQUISITES
This procedure must be performed on the preferential active server.
The BSC equipment must be running, to access to their disks with OSI FTAM.

3.3. RESOURCES
One operator at the OMC-R site is required to carry out the check.


EFT CHECK
DS/BSS/APP/0004 07.01 / EN Standard 11/Aou/2003 Page 8/27
4. OPERATION DETAILED DESCRIPTION
4.1. UPGRADE OPERATION SEQUENCE TABLE


Step Operation description (Total 13+? mn) mn Sheet
page
OK /
NOK
NOK
step
Input Parameters
ALL PREREQUISITES HAVE BEEN CHECKED
S1 How to ... 1 10
S2 Oam user creation 1 12
S3 FTAM transfer stop on the OMC-R/BSC link 5 16
S4 EFT consistency check ? 14
S5 FTAM transfer restore on the OMC-R/BSC link 5 17
S6 Oam user deletion 1 13
THE UPGRADE IS SUCCESSFULLY COMPLETED






EFT CHECK
DS/BSS/APP/0004 07.01 / EN Standard 11/Aou/2003 Page 9/27
5. SHEETS
The sheets of operations are not in the order of execution. Always refer to the sequence table of the operations to
determine the sheet to execute and the values of its input parameters.
The sheets used in this specific procedure are applicable in other procedures (other hardware configurations). For
this reason, it is possible to find some conditional sections or sentences available only in other procedures.

EFT CHECK
DS/BSS/APP/0004 07.01 / EN Standard 11/Aou/2003 Page 10/27
HOW TO . . .
PRESENTATION
The purpose of this sheet is to describe how to perform some basic operations, which you
will have to achieve all along your procedure.
INITIAL STATUS
The OMC-R is running and the MMI is accessible on the local machine.
The BSS is operational.
ACTIONS

ON A LOCAL OMC-R WORKSTATION:

O1. How to open an omc shell window on a workstation:

In the background menu:

SELECT Access to UNIX

then, enter your username (omc, root ...) and password.

O2. How to remotely log in on the active server from a workstation:

O2.1. Open an omc shell window.

O2.2. Go into this window and remotely log in on the active server:
Under omc login:
... (omc) % rlogin actServerName

actServerName : hostname of the active server

O3. How to open a session log:

GOTO OMC-R Browser
SET View = Logical
SELECT Administration
SELECT user session log...

O4. How to find the active server:

GOTO OMC-R Browser
SET View = Logical
SELECT_OBJ MD-R
SELECT Objects - Display|Set

Locate the managerServer parameter.
The value of this parameter is the hostname of the active server.

O5. How to open a notification window:
EFT CHECK
DS/BSS/APP/0004 07.01 / EN Standard 11/Aou/2003 Page 11/27

GOTO OMC-R Browser
SET View = Logical
SELECT Fault
SELECT Notification monitor...

O6. How to go to oam directory:

O6.1. Create oam directory if not already done in previous steps.
Under omc login:
... (omc) % mkdir /home/omc/oam

O6.2. Go to oam directory.
Under omc login:
... (omc) % cd /home/omc/oam

FINAL STATUS
Now you know how to perform all above basic operations.


EFT CHECK
DS/BSS/APP/0004 07.01 / EN Standard 11/Aou/2003 Page 12/27
OAM USER CREATION
PRESENTATION
The purpose of this sheet is to create an OMC-R oam user for executing the automatic
part of the upgrade, or maintenance.
INITIAL STATUS
The OMC-R is operational.
ACTIONS
1. If not already done, open a shell session under omc user, on the active server.

2. Execute the tool on the active server:
Under omc login on the active server:
... (omc) % /usr/local/oam/bin/ds_createOamUser.sh -
PadministratorPassword

administratorPassword : password of the OMC-R user administrator

Note: The oam OMC-R user password can be found in the log file of the tool
(/var/local/oam/ds_createOamUser.log)
TROUBLE SHOOTING
1. If you do not know the administrator password, contact the customer administrator to
get it!
2. See the log file /var/local/oam/ds_createOamUser.log.
3. The shell may exit with the following error:
...
Error 7 during mmiExecute command
Oam user creation: KO
...
This is due to the Administrator Password Expiration. In this case only, log to the MMI
under administrator user. This action will lead to the password sequence then you
should restart the sheet.
FINAL STATUS
The OMC-R oam user has been created.


EFT CHECK
DS/BSS/APP/0004 07.01 / EN Standard 11/Aou/2003 Page 13/27
OAM USER DELETION
PRESENTATION
The purpose of this sheet is to delete the OMC-R oam user created in previous steps.

WARNING: All command files of the oam user will be deleted by the
OMC-R.

INITIAL STATUS
The OMC-R is operational.
ACTIONS
1. If not already done, open a shell session under omc user, on the active server.
2. Execute the tool on the active server:
Under omc login on the active server:
... (omc) % /usr/local/oam/bin/ds_deleteOamUser.sh -
PadministratorPassword

administratorPassword : password of the OMC-R user administrator
TROUBLE SHOOTING
1. If you do not know the administrator password, contact the customer administrator to
get it !
2. See the log file /var/local/oam/ds_deleteOamUser.log.
3. The shell may exit with the following error:
...
Error 7 during mmiExecute command
Oam user creation: KO
...
This is due to the Administrator Password Expiration. In this case only, log to the MMI
under administrator user. This action will lead to the password sequence then you
should restart the sheet.
FINAL STATUS
The OMC-R oam user has been deleted.


EFT CHECK
DS/BSS/APP/0004 07.01 / EN Standard 11/Aou/2003 Page 14/27
EFT CONSISTENCY CHECK
PRESENTATION
The purpose of this sheet is to describe how to check the consistency of EFTs between
OMC-R and BSCs.
INITIAL STATUS
The OMC-R is running and the MMI is accessible on the local machine.
The OMC-R/BSC link is operational.
ACTIONS

ON A LOCAL OMC-R
WORKSTATION:

1. If not yet done, log in to the OMC-R under administrator user.

2. Remotely log in on the active server if not already done ( sheet How to...).

3. Execute the tool :

- To check all EFTs of all BSCs :
Under omc login:
... (omc) % /usr/local/oam/bin/ds_checkEft.sh -Dall

- To check all EFTs of one BSC (bscNumber) :
Under omc login:
... (omc) % /usr/local/oam/bin/ds_checkEft.sh -Dall -BbscNumber

- To check one EFT software type of all BSCs:
Under omc login:
... (omc) % /usr/local/oam/bin/ds_checkEft.sh -Dall -SsoftwareType

- To check one EFT software type on one BSC :
Under omc login:
... (omc) % /usr/local/oam/bin/ds_checkEft.sh -Dall -BbscNumber -
SsoftwareType

softwareType = TB (for transcoderBoard)
BSM (for btsSiteManager)
TE (for transceiverEquipment)
B (for bsc 2G & e3)
T (for TCU e3)

EFT CHECK
DS/BSS/APP/0004 07.01 / EN Standard 11/Aou/2003 Page 15/27
Watch the screen display for the main check points status results.
Read the log file "/var/local/oam/ds_checkEft.log" for more information on detected errors.
Previous log file is /var/local/oam/ds_checkEft.log.old
TROUBLE SHOOTING
1. See the log file : /var/local/oam/ds_checkEft.log
2. If an on-site version upgrade has been performed on BSS, BSC, BTS and/or TCU, an
ERROR on sWVersionFallBack parameter occurs. Disregard it, since this information is
not available on the system.
FINAL STATUS
The EFT consistency between OMC-R and BSCs is now checked.


EFT CHECK
DS/BSS/APP/0004 07.01 / EN Standard 11/Aou/2003 Page 16/27
FTAM TRANSFER STOP ON THE OMC-R/BSC LINK
PRESENTATION
The purpose of this sheet is to describe how to stop the FTAM transfer on the OMC-R/BSC
link.
(With impact on BSS Maintenance & Operation).

WARNING : 1- All observations will not be lost, just delayed. They
continue to be stored on BSC disks and will be sent to OMC-R
once circular files are re-opened.
This tool performs the following jobs:
Close Observation and InstrumentPanel circular files on all BSCs.
Lock traceControl and callPathTrace on all BSCs.
Create a command file named "/root/oam/restoreTraffic.cmd", used by the
FTAM restoring tool to reopen the traffic later.
Note: - The "restoreTraffic.cmd" file is created after each execution of the tool.
- The FTAM restoring tool uses the last created "restoreTraffic.cmd" file.
INITIAL STATUS
The OMC-R is running. The OMC-R/BSC link is operational.
ACTIONS

ON A LOCAL OMC-R
WORKSTATION:

1. If not yet done, log in to the OMC-R under administrator user.

2. Remotely log in on the active server if not already done ( sheet How to...).

3. Execute the tool:
Under omc login:
... (omc) % /usr/local/oam/bin/ds_reduceTraffic.sh

- Ignore error messages about circular file closing, if any.
TROUBLE SHOOTING
1. See the log file: /var/local/oam/ds_reduceTraffic.log.
FINAL STATUS
The FTAM transfer on the OMC-R/BSC link is now stopped.



EFT CHECK
DS/BSS/APP/0004 07.01 / EN Standard 11/Aou/2003 Page 17/27
FTAM TRANSFER RESTORE ON THE OMC-R/BSC LINK
PRESENTATION
The purpose of this sheet is to describe how to restore the FTAM transfer on the OMC-
R/BSC link (which has been previously stopped by the FTAM transfer stop tool).
This tool performs the following jobs, using the /root/oam/restoreTraffic.cmd file
previously created by the FTAM transfer stop tool:
Open Observation and InstrumentPanel circular files on all BSCs.
Unlock traceControl and callPathTrace on all BSCs.
INPUT PARAMETERS
None.
INITIAL STATUS
The FTAM transfer on the OMC-R/BSC link has been stopped in previous actions.
The OMC-R is running and the MMI is accessible on the local machine.
ACTIONS

ON A LOCAL OMC-R
WORKSTATION:

1. If not yet done, log in to the OMC-R under administrator user.

2. Remotely log in on the active server if not already done ( sheet How to...).

3. Execute the tool:
Under omc login:
... (omc) % /usr/local/oam/bin/ds_restoreTraffic.sh

Ignore error messages about circular file opening, if any.
TROUBLE SHOOTING
See the log file: /var/local/oam/ds_restoreTraffic.log.
FINAL STATUS
The FTAM transfer on the OMC-R/BSC link is now restored.


6. ABBREVIATIONS & DEFINITIONS
6.1. ABBREVIATIONS
Abis ETSI generic name for BSC-BTS interface
EFT CHECK
DS/BSS/APP/0004 07.01 / EN Standard 11/Aou/2003 Page 18/27
Agprs NORTEL generic name for BSC-PCU interface
AIX IBM UNIX operating system
ALA ALArm regrouping board (in BSC)
AMR Adaptive Multi Rate
Ater ETSI generic name for BSC-TCU interface
ATM Asynchronous Transfer Mode
ASCI Advanced Speech Call Items
A5000 Sun StorEdge A5000
BCC Base Color Code
BCCH Broadcast Control Channel
BCF Base Common Functions
BDA BSC application database
BDE OMC-R operations database
BIST Built-In Self Test
BSC Base Station Controller
BSCB BTS Signalling Concentration Board
BSIC Base Station Identity Code
BSS Base-station Sub-System
BSSGP Base Station System GPRS Protocol
BTS Base Transceiver Station
CAS Component Administration System
CCS7 Common Channel Signalling number 7
CC1 CAM Controller. This is the ATM switch composed of a CC1-SBC and a
CC1-TM
CC1-SBC ATM switch for the ALPHA Platform
CC1-TM Adapter for the CC1-SBC
CCS7 Common Channel Signalling number 7
CDROM Compact Disk Read Only Memory
CEM Common Equipment Module
CGI Cell Global Identity
CN Control Node
CP Control Processor
CPUE Central Processor Unit Esclave
CPUM Central Processor Unit Matre
CRC Cyclic Redundancy Check
CSR Customer Service Request
CTB Cable Transition Board
CTM Cable Transition Module
CTU Cable Transition Unit
DAT Digital Audio Tape
DCU Dual Channel Unit
DDTI Dual Digital Trunk Interface
DELIVERY set of EFT
DLCI Data-Link Connection Identifier
DLU DownLoading Unit
ECI Equipment Cabinet Interface
EDGE Data rates for GSM Evolution
EFR Enhanced Full Rate
EFT Ensemble de Fichiers Transfrables (set of downloadable files)
EFT CHECK
DS/BSS/APP/0004 07.01 / EN Standard 11/Aou/2003 Page 19/27
ETF Enhanced TRAU Frame
ETSI European Telecommunications Standards Institute
E1 European Standard PCM link nickname
E4xxx Sun Enterprise server family (E4002, E4500)
FPRX Front Processor for Reception
FHS Frequency Hopping System
FPC Frequency Plan Change
FR Full Rate
FRATM Frame Relay Asynchronous Transfer Mode
Gb ETSI generic name for SGSN- PCUSN interface
GGSN Gateway GPRS Support Node
GPRS General Packet Radio System
GUI General User Interface
HC100 High Capacity kit (IDE MMU and CPU133 OMU)
HR Half Rate
HSN Hopping Sequence Number
IEM Interface Electronic Module
IN Interface Node
LAC Location Area Code
LAPD Link Access Protocol D-Channel
LP Logical Processor
LSA Low Speed Access
LSA RC Low Speed Access Resource Complex
L1M Layer 1 Management
MCC Mobile Country Code
MD Mediation Device
MDM Preside Multiservice Data Manager
MDP Magellan Data Provider
MIM Module Information Memory
MMI Man Machine interface
MMS Memory Mass Storage
MNC Mobile Network Code
MOD Managed Object Dictionary (BSC / MD interface)
MPU Main Processor Unit (BSC chain)
MSW Main SWitching matrix
MTM Module Test and Maintenance
NCC Network Color Code
NMS Network Management System
NRP Network Reconfiguration Procedure
NSE Network Switch Element
NSVC Network Switch Virtual Circuit
NTP Nortel Telecom Publications
OAM Operation Administration and Maintenance
OC-3 Optical Carrier level 3 (SONET)
ODIAG Observation DIAGnostic
OMC-R Operation and Maintenance Centre - Radio part
OML OAM link
OMN Operation and Maintenance Network (BSC-MD Link, also known as the
"REM" link)
EFT CHECK
DS/BSS/APP/0004 07.01 / EN Standard 11/Aou/2003 Page 20/27
OMU Operation and Maintenance Unit composed of an OMU-SBC and an OMU-
TM
OMU-SBC VME SBC used for the OMU
OMU-TM ATM Adapter for the OMU
PCCCH Packet Common Control Channel
PCGTL
PCM Pulse Code Modulation
PCU Packet Control Unit
PCUOAM Packet Control Unit Operation Administration and Maintenance server
PCUSN Packet Control Unit Support Node
PDCH Packet Data Channel
PDP Packet Data Protocol, eg. IP or X25
PDTCH Packet Data Traffic Channel
PEC PCM Error Correction
PLMN Public Land Mobile Network
PROM Programmable Read Only Memory
QoS Quality of service
Q3 MD manager interface
RAC Routing Area Code
RAM Random Access Memory
RM Resource Module
RSL Radio Signalling Link
SAI Service Area Interface
SBC Single Board Computer : Regular VME processor boards
SDO Serveur de DOnnes
SDS Software Distribution Site
SFH Synthesised Frequency Hopping
SGSN Serving GPRS Support Node
SICD Serial Interface Controller for lapD protocol
SICX Serial Interface Controller for X25 protocol
SIM Shelf Interface Module
SLS Serial Link Switch (BSC board supporting the serial link with OMC-R
SLS2 Serial Link Switch, second generation
SMS-CB Short Message Service Cell Broadcast
SS1000 Sun SPARCserver 1000
SSA Sun SPARCstorage Array
SS7 Common Channel Signalling number 7
SUP SUPervision board
SUP2 SUPervision board, second generation
SWACT SWap of ACTivity
SWC SWitching matrix Controller
TCB TranscoderBoard Card
TCB2 2nd generation TranscoderBoard Card
TCP Transmission Control Protocol
TCU TransCoder Unit
TDMA Time Division Multiple Access
TEI Terminal Equipment Identifier
TIC Terminal for Installation and Commissioning
TML Local maintenance terminal (Terminal de Maintenance Locale)
EFT CHECK
DS/BSS/APP/0004 07.01 / EN Standard 11/Aou/2003 Page 21/27
TMU Traffic Management Unit composed of a TMU-SBC and a TMU-TM
TMU-SBC VME SBC used for the TMU
TMU-TM ATM Adapter for the TMU
TO Temporary Observation
TRAU Transcoder/rate Adaptator Unit
TRM Transcoding Resource Module
TRX Transmitter/Receiver
TS Time Slot
TTY Text Telephone
T1 American Standard PCM link nickname
VRTX Operating system used in CEM modules
VxWorks Operating system used in TMU modules
e3 BSC evolution 3rd generation BSC
e3 TCU evolution 3rd generation TCU
e3 TML evolution 3rd generation TML
2G BSC other BSC than e3 BSC
2G TCU other TCU than e3 TCU



6.2. DEFINITIONS
Active (respectively passive) server
Term that designates the actual active (respectively passive) server on an
operational OMC-R, in case of dual servers configuration. For a single
server configuration, only the active server exists.
BCCH conflict The set of attributes bCCHFrequency and bsIdentityCode must be
unique in the set constituted by the cell and its neighbouring cells
(adjacentCellHandOverNortel object class only).
BSIC Code used to identify a base station, which allows mobile stations to
distinguish the cells sharing the same BCCH frequency. A BSIC is defined
by an (NCC, BCC) combination.
CAS Is the command and control system that takes network management
requests, passes them to the appropriate components for action, and returns
the results to the requester. The CAS is responsible for all provisioning and
control commands, and the management of provisioning data on the
Passport.
CGI Global identifier of a mobile network cell. The CGI contains the Location
Area Code (LAC), Mobile Country Code (MCC), Mobile Network Code
(MNC) and the cell identifier in the location area
Concentric A cell is defined as concentric if two pools of resources (TDMAs) are defined
using Rxlev and optionally Timing Advance as allocation criteria. One or two
types of TRXs can be used.
Delivery Set of EFT
Dualzone A cell is defined as dualzone if it exists TRXs configured to transmit at
different power resulting in two different coverage areas.
EFT CHECK
DS/BSS/APP/0004 07.01 / EN Standard 11/Aou/2003 Page 22/27
Dualcoupling A cell is defined as dualcoupling if the TRXs are not combined with the same
type of combiner and thus have not the same coupling loss resulting in two
different coverage areas. Linked to stepped coupling feature.
Dualband A cell is defined as dualBand if GSM900 TRXs and DSC1800 TRXs coexist
and share the shame BCCH. The propagation loss being different, it results
in two different coverage areas.
DS0 one TS at 64kbps of one PCM
without joker TS, one TDMA uses 2 DS0, which are configured on one PCM
Erlang international (dimensionless) unit of traffic intensity defined as the ratio of
time a facility is occupied to the time it is available for occupancy. One
erlang is equal to 36 ccs. In the US, it is also known as a traffic unit.
E1 Is a primary PCM group, which consists in an assembly, by digital using
multiplexing, of PCM signals occupying 32 channels time-slots in order to
generate a signal with a digit rate of 2048 kbit/s, in both transmission
directions.
GPRS Wireless packet data service that is an extension to the GSM network. It
allows providing multiple radio channels to one user (high data user rate) as
to share one radio channel between multiple users (radio resource
optimization).
Joker DS0 On Abis, 64 kbps timeslot used as joker for an EDGE TDMA. The total
number of DS0 used for an EDGE TDMA consists in 2 DS0 called main DS0
plus joker(s) DS0.
MDM Preside Multiservice Data Manager. Product developed by Passport Product
Line. This product can configure a Passport, collect alarms and real time
counters from a Passport node.
MDP Preside MDM Management Data Provider. Product developed by Passport
Product Line. This product can collect spooled counters from a Passport
node, convert them into ASCII files and send these ones to external devices.
Old-version Represents the old edition N-2, N-1 or N to be upgraded.
OMC-R The OMC-R software installed on an OMC-R server or an OMC-R
workstation.
OMC-R machine
A machine running the OMC-R software (an OMC-R server or an OMC-R
workstation).
Preferential active (respectively passive) server
Term that designates the server administratively declared as active
(respectively passive). The preferential passive server can become the
operational active server after a switchover on an operational OMC-R. For a
single server configuration, only the preferential active server exists.
PCUOAM (server/workstation) added on the OMC-R LAN to host MDP and NMS
software and also OMC-R process which handles PCUSN alarms and
counters collection. One PCUOAM can only be linked to only one OMC-R.
EFT CHECK
DS/BSS/APP/0004 07.01 / EN Standard 11/Aou/2003 Page 23/27
PCUSN Separate node in the BSS in order to provide the specific packet processing
of the GPRS. There is only 1 PCU per BSC, but a PCUSN can be shared
with several BSCs.
SDS A Software Distribution Site is a FTP server that handles the GPRS Passport
software. It is used during the upgrade procedure.
SMS-CB Short messages broadcast at a cell level.
TDMA Abbreviation used to designate a transmission frame on the radio interface,
divided into eight timeslots (TS) or channels.
TRAU frame frames (speech/data) with a fixed length of 320 bits (20 msec).
T1 (or DS1) is a primary PCM group, which consists in an assembly, by digital
multiplexing, of PCM signals using 24 channels time-slots in order to
generate a signal with a digit rate of 1544 kbit/s, in both transmission
directions.

2G equipment:
2G BSC Other BSC than e3 BSC
2G TCU Other TCU than e3 TCU
BDA BSC application database
Active and Passive chain of a 2G BSC
The BSC MPU (Main Processing Unit) processing chain is duplicated for
reliability and operates in matched pairs (MPUA and MPUB). In duplex
mode, the chain in service is called the active chain and provides the
functions of the rack. The other chain, called passive chain, takes over if
the first one fails.
Duplex mode State of a 2G BSC when both chains are on-line.
Simplex mode State of a 2G BSC when only one chain is on-line.
Control cabinet
A 2G BSC is composed of 2 cabinets. The control cabinet contains the
processing chains MPUA and MPUB.
Equipment cabinet
A 2G BSC is composed of 2 cabinets. The equipment cabinet contains
the boards shared by both chains and their switching units.
Data mirroring Process whereby the data is updated on the passive chain while
changing on the active chain, when the 2G BSC is in duplex mode
operational state.
Switch-over Process whereby the passive chain becomes active, because the
previously active chain is not able to maintain the 2G BSC in its
operational state. It happens when the active chain is simply powered
down, or when it is having hardware or software problem.
Type 3 upgrade
This type of upgrade is performed when there is a change of BDA format
EFT CHECK
DS/BSS/APP/0004 07.01 / EN Standard 11/Aou/2003 Page 24/27
between the previous software version and the new software version.
The service is lost.
Type 4 upgrade
This type of upgrade is performed when there is a change of BSC
application software only. A BSC switchover is performed to activate the
new software version. The service is not lost but call established for more
than 5 minutes are lost.
Type 5 upgrade
This type of upgrade is performed when there is a change of BDA format
between the previous software version and the new software version. But
contrary to type 3 there is only one small service impact thanks to a
mechanism called BDA n+1.
E3 equipment
e3 BSC Evolution 3rd generation BSC
e3 TCU Evolution 3rd generation TCU
MIB Managed Information Base. But even if the e3 BSC database is named
MIB, the term of BDA is commonly used to name 2G and e3 BSC
database.
Swact SWitch of ACTivity. It applies to CEM of Interface Node, CEM of TCU and
to OMU of Control Node.
Type 3 upgrade
This type of upgrade is performed when there is a compatibility break
with a change of MIB format between the previous software version and
the new software version. There is a build off line. The service is lost
(important downtime).
Type 4 upgrade
This type of upgrade is performed when there is a change of BSC
application software without change of MIB and without compatibility
break. There is no build. The service is not lost (no downtime).
Type 6 upgrade
This type of upgrade is performed when when there is a compatibility
break with change of MIB format between the previous software version
and the new software version. There is a build on line. The service is
lost following upon a BSC restart (downtime during few minutes).
Type 7 upgrade
This type of upgrade is performed when there is a compatibility break
without change of MIB format between the previous software version and
the new software version. There is no build. The service is lost following
upon a BSC restart (downtime during few minutes).



EFT CHECK
DS/BSS/APP/0004 07.01 / EN Standard 11/Aou/2003 Page 25/27
6.3. TYPOGRAPHIC CONVENTIONS
6.3.1 GENERAL CONVENTIONS
Words in italic style (italic) means a parameter to substitute by its value.

The following syntax indicates on which machine the actions should be run:

ON A LOCAL OMC-R
WORKSTATION:

Conditional commands are indicated with the following syntax:
For all the unlocked bscMdInterface objects:
{
.....
}

6.3.2 INTERACTIVE TERMINAL SESSIONS
An interactive session on a terminal can be obtained using two methods:
Choosing the "Access to Unix" option of the background menu on the
server or the station,
Open a remote connection to the server or the station from a shell window on
any other machine, using the telnet or rlogin command.

An interactive session on a terminal (line terminal or Command Tool window)
is described with the following syntax:

Convention used Meaning
Courier New All characters of a terminal session are in Courier New font.
Bold
The lines, commands, or parameters entered with the keyboard
are in bold style.
Italic A variable output display is in italic style. Words in italic have to
be substituted by real values.
italic-bold
An input parameter, which should be substituted by its value, is in
italic and bold style.
The ENTER key has to be pressed.
[STOP],[a] The STOP and a keys have to be pressed simultaneously.
.......... A group of dots replace a certain number of lines.
A command line is truncated and continues on the next line.
% or (user) % The C shell prompt
$ or (user) $ The Bourne and Korn shell prompt
# or (root) # The root super-user prompt in any shell

Terminal session sample:
EFT CHECK
DS/BSS/APP/0004 07.01 / EN Standard 11/Aou/2003 Page 26/27
Under omc login:
/ (omc) % cd my_directory
my_directory (omc) % ls
a.out
i_am_a_short_file_with_a_really_i_mean_really_no_but_unbelievably_"
long_name
........
toto.o
my_directory (omc) % vi my_file
my_directory (omc) %

The typographic conventions of a terminal session are also used to display the content
of a UNIX file.

6.3.3 INTERACTIVE GRAPHIC SESSIONS
The graphic interactive commands are described with the following syntax:

Convention used Meaning
GOTO Title Go to the window named "Title"
SELECT Save - OK Click with the mouse on the buttons or options
named "Save", then "OK".
SELECT_OBJ omc Select the object omc
SET State = locked
T2 = 30s
Enter with the keyboard the values of the
parameters
CLOSE Title Close the window named "Title"



6.4. SEQUENCE TABLE CONVENTION
For each major step of the procedure, a sequence table lists the operation
steps to perform. Each operation step is described completely in the sheet
referenced by its page number.
A sheet may have to be executed at different stages of the procedure and in
different contexts; in that case, a set of input parameters for the sheet
indicates the context.
A sequence table provides for each operation step the time required to
perform it. The time indicated for an operation step corresponds to a maximum
network configuration, and may change depending on the hardware
configuration.

Since the sheets are not in the execution order and can be executed
several times, the sequence tables should be considered as the
reference guide during the procedure.

EFT CHECK
DS/BSS/APP/0004 07.01 / EN Standard 11/Aou/2003 Page 27/27
A sequence table has the following format:

Step Operation description (Total 115 mn + ? mn) mnSheet
page
OK /
NOK
NOK
step
Input Parameters
STATUS COMMENT
S1 Description of the operation 1 30 12
OK
F1
Parameter1 = value
Parameter2 : explanations

S2 Description of the operation 2 80 14
OK
F1
S3 Description of the operation 3 5 17
OK
F6
Parameter1 = value








Each time an operation has been performed, the operator should note the
result in the OK / NOK column.
- If the result is OK , the next operation is described in the following
line of the table,
- If the result is NOK , the procedure can not be continued. The next
operation could be indicated in the last column of the current line and
is either a fallback or a trouble-shooting step. In case of a fallback
(indicated with a "F"), the fallback procedure should be started at the
specified step.



END OF DOCUMENT
Result of the operation,
filled in by the operator
Fallback or trouble shooting step to execute (if
any), if the result of the operation is NOK
Sheet page number
Maximum elapsed time of the operation step
with a maximum configuration
Comment indicating the status at
this stage of the major step
Name and value of input para-
meters of the sheet (optional or
none for no argument)