Abis Integration of BTSplus at Flexi BSC

Short-Term Plan (STP) COO - Overall InstructionsRG10 ED (BTSplus@FlexiBSC family Delta) Course
RN2404-14N
Intellectual Property Rights
All copyrights and intellectual property rights for Nokia Siemens Networks training documentation, product documentation and slide presentation material, all of which are forthwith known as Nokia Siemens Networks training material, are the exclusive property of Nokia Siemens Networks. Nokia Siemens Networks owns the rights to copying, modification, translation, adaptation or derivatives including any improvements or developments. Nokia Siemens Networks has the sole right to copy, distribute, amend, modify, develop, license, sublicense, sell, transfer and assign the Nokia Siemens Networks training material. Individuals can use the Nokia Siemens Networks training material for their own personal self-development only, those same individuals cannot subsequently pass on that same Intellectual Property to others without the prior written agreement of Nokia Siemens Networks. The Nokia Siemens Networks training material cannot be used outside of an agreed Nokia Siemens Networks training session for development of groups without the prior written agreement of Nokia Siemens Networks.
© Nokia Siemens Networks RN24045EN14GLN0
After studying this module the trainee will be able to:
Understand the BTSplus Integration Procedure in BSC3i/FlexiBSC
Understand the BSS Radio Network Object Model
Understand the steps of Abis-Integration
Interrogate the radio network parameters and RNW objects with MML Commands
Create the Abis-Interface, radio network objects, and control parameters
Change the administrative states of the objects
Monitor the restart phases of a base station
BTS Plus Creation
BTS plus creation is not different so much from Nokia Flexi BTS creation from the BSC3i prospective. Differences are:
Multiplexed links (MML cmd interrogation: ZDSB, ZDTI)
Instead of creating OMU-link to TSL 31, TRX-1 link to TSL 30 etc. all links can be created in one (or two, depending on the number of TRXs) TSL using the parameter link type "multiplexed"
Port Id (MML cmd interrogation: ZEFO)
When creating BCF it is necessary to define Port Id parameter. There are 8 PCM connections on the BTS, ports 0…7. In BSC you use the port 0…port 7 parameter, depending on which one/ones you're connected to
The value of the port number is the number of ET-PCM used for that connection
Cell number in BTS HW (CHW) parameter (MML cmd interrogation:ZEQO)
Cell number in BTS HW (CHW) parameter must be the same index as cell index in LMT BTSplus
Creating a base station and initialising its parameter
Attaching BCF Software build to BCF
Taking Base Station into use
Start
BS type: X
End
Only for the Base Station type Talk Family Hardware Database is stored in BSC. All other BS types do not have a Hardware Database handling. The Hardware Database Handling (Command group ZEV) is similar to the BCF Software handling (Command group ZEW).
Create ET plug-in unit
ET connected to
the right IF
End
Create an ET with the ZWT command group. Connect the ET with the ZWUC command. If necessary, modify the ET settings with the ZYEC command and change the working state (ZUSC) to WO-EX.
512 BCSU SC7PRB ETPCM - - VIRTUAL_PCMS
33H 01B1H 0000H 0000H 0100H 1280
528 BCSU ERATES ETPCM - -
30H 01BFH 0000H 0000H 0000H 1792 - 1799
TOTAL OF 3 PCM CIRCUITS
If the ET is already connected, it has a controlling BCSU (Base Station Controller Signalling Unit) and process info. The controlling process can be
SC7PRB A interface
ABIPRB Abis interface
Start
End
Create neighbouring cell information
TRXSIG
BCFSIG
TCH
BTSplus
MFDUAMCO: Multi-Standard Flexible Duplex Amplifier Multicoupler
FlexCU: Flexible Carrier Unit
TMA. Tower Mounted Amplifier
OVPT: Over Voltage protection
Each BTS has one O&M channel, OMUSIG (or BCFSIG)
- it is a LAPD link connected to the BCF unit in the BTS
- the bit rate is 16, 32 or 64 kbit/s
Note: With Metrosite equipment, the function of the BCF is taken over by a TRX.
One TRX can handle 8 x 16 kbit/s Traffic Channels (TCHs)
- it needs two PCM timeslots for TCHs in Abis
- one TRX has one LAPD link, TRXSIG; bit rate of the TRXSIG is 16, 32 or 64 kbit/s
Note: MetroSite, UltraSite and InSite can manage a combined TRXSIG/OMUSIG SAPI: 63!
Adj. Cell
BCF and HW DB attachments have to be handled in a TALK FAMILY BTS. In Metrosites and Ultrasites its not needed.
BCF Base Control Function, ZEF...
Creation of NOKIA PrimeSite differs in commands ZEFC and ZERC
BTS Base Transceiver Station, ZEQ...
FHS Frequency Hopping System
BTS SW BTS Software Package, ZEW...
HW DB Hardware Database, used only for NOKIA Talk Family Base Station! ZEV...
HOC Handover Control Parameters, ZEH...
POC Power Control Parameters, ZEU...
Adj. Cell Adjacent Cells Parameter, ZEA...
UMTS Adj. Cell WBTS Adjacent Cells Parameter, ZEA...
SITE TYPE ............................ X - BTSPLUS
ADMINISTRATIVE STATE ................. UNLOCKED
OPERATIONAL STATE .................... WO
BCCH TRX SHUTDOWN TIMER ......(BTIM).. 0 min
FACCH LAPDM T200 .............(T200F). 0 (BCF PREDEFINED VALUES)
SDCCH LAPDM T200 .............(T200S). 0 (BCF PREDEFINED VALUES)
PCM PORT ID 0 ................(PORT0). 576
PCM PORT ID 1 ................(PORT1). ND (NOT DEFINED)
BTS UNDER THIS BCF ARE:
SEG-0400
MML cmd: ZEFO
BTSplus specific parameter -PCM port ID (PORTO) is mapped to the Abis PCM index
ADMINISTRATIVE STATE ................. UNLOCKED
OPERATIONAL STATE .................... WO
BCCH TRX SHUTDOWN TIMER ......(BTIM).. 0 min
MASTER CLOCK BCF .............(MCBCF). --
FACCH LAPDM T200 .............(T200F). 0 (BCF PREDEFINED VALUES)
SDCCH LAPDM T200 .............(T200S). 0 (BCF PREDEFINED VALUES)
ABIS OVER IP ETHERNET USAGE ..(TRS1).. 0 (NOT IN USE)
ADDITIONAL 2 E1/T1 USAGE .....(TRS2).. 0 (NOT IN USE)
TRS ABIS GROOMING USAGE ......(TRS3).. 0 (NOT IN USE)
TRS LOOP PROTECTION USAGE ....(TRS4).. 0 (NOT IN USE)
BTS UNDER THIS BCF ARE:
SEG-0310
Start
Create BTS software build
Activate the build
Refer to S11 Documentation:
Reference\ Commands\ Service Terminal Commands\ BCF Remote User’s Manual\ Introduction to BCF Remote MMI
Refer to Man-Machine Interface User's Guide (B6Z063067AE) included in the latest BTS release documentation
3 ways to handle HW database:
Create a HW database package from an existing file on WDU (directory HWDATA) and attach it to the BTS (ZEVC, ZEVA, ZEVV)
Upload the existing HW database from the BTS (ZEVU), continue as in 1)
Create and download the package via remote MML
BTSplus - BCF SW Interrogation
------------------------------------------------------------------
SWL_0900.041 19.9-3 16/10/09 RU
VAM_0900.041 19.9-3 16/10/09 RU
BCX_0900.011 19.9-3 16/10/09 RU
BCX_0900.031 19.9-3 16/10/09 RU
BIX_0900.091 19.9-3 16/10/09 RU
BIX_0900.101 19.9-3 16/10/09 RU
BIX_0900.011 19.9-3 16/10/09 RU
--------------------------------------------------------------------------------
FB BR10_TEST 19.51-3 /PACK_20
“Figure A” shows an LAPD link configuration for the Abis interface, when used to connect a BSS BTS (e.g. Flexi EDGE BTS) with a Flexi BSC
In this configuration, a dedicated physical LAPD link is provided for each TRX. A physical LAPD link is associated with an LAPD signaling channel assigned to a PCM timeslot, and can have a throughput of 16, 32 or 64 kbit/s
Flexi BTS - LAPD Multiplexing
BTS plus - LAPD Multiplexing
“Figure B” shows how the LAPD configuration is done on the Abis interface connecting a BTSplus base station with the Flexi BSC
The LAPD signaling data related to several TRXs is multiplexed onto one physical LAPD link, defined by a 16, 32 or 64 kbit/s PCM timeslot
The maximum number of physical LAPD channels that can be configured per base station is 11. However, the Flexi BSC can manage up to 32 TRXs per BTSplus (i.e. per BCF object)
Therefore, several TRXs belonging to a BTSplus base station can be configured on a common physical LAPD link. For this purpose, up to 16 simultaneous signaling data link connections, or logical LAPD links, can be multiplexed onto one physical LAPD link
This method allows for optimized use of the available LAPD channels, and therefore reduces the signaling bandwidth required
BTS plus
– LAPD link Interrogation
----- --- ------- --------- ----------- ---- -------
COMMAND EXECUTED
----- --- ------- --------- ----------- ---- -------
COMMAND EXECUTED
INTERROGATING BASE STATION CONTROLLER D-CHANNEL DATA
EXT SUB TERM LOG INT PAR
----- --- ---- --- -- ----------- --- ---------------- ---- ------- ---
B50 27 62 1 64 522-31 M BCSU-0 14 25 27 292-25 2
T501 28 0 1 64 522-31 M BCSU-0 14 25 28 292-25 2
T502 29 0 2 64 522-31 M BCSU-0 14 25 29 292-25 2
T503 30 0 3 64 522-31 M BCSU-0 14 25 30 292-25 2
T504 31 0 4 64 522-31 M BCSU-0 14 25 31 292-25 2
COMMAND EXECUTED
CELL NUMBER IN BTS HW....................(CHW).... 1
BS IDENTITY CODE.........................(BSIC)
COMMAND EXECUTED
Cell number in BTS HW (CHW) parameter required
CHW must be the same index as cell index in LMT BTSplus
BSC3i BSC13 2009-10-23 11:38:09
BS IDENTITY CODE.........................(BSIC)
PS: -
HOPPING SEQUENCE NUMBER 1.............(HSN1)... 0
HOPPING SEQUENCE NUMBER 2.............(HSN2)... 0
COMMAND EXECUTED
BTSplus and FLEXI BTS at the FLEXI BSC product family
BSC3i BSC13 2009-10-23 15:59:38
E P B
F T R C D-CHANNEL BUSY
AD OP R ET- BCCH/CBCH/ R E S O&M LINK HR FR
===================== == ====== ==== == ==== =========== = = == ===== == === ===
00013 13310 BTS-0310 U WO 0 0
-/- 3
TRX-002 U WO 121 0 523 ERACH E 0
TRX-003 L BL-USR 119 0 523 0
TRX-004 L BL-USR 117 0 523 0
00013 13311 BTS-0311 L BL-USR 0 0
-/- 0
TRX-006 U BL-USR 694 0 523 0
TRX-007 U BL-USR 700 0 523 0
TRX-008 U BL-USR 704 0 523 0
BCF-0040 BTSPLUS-M U WO 0 B40 WO
00013 13400 BTS-0400 U WO 0 0
-/- 3
EDGE TRX-002 U WO 87 0 576 ERACH E 0
00013 13401 BTS-0401 U WO 0 0
-/- 0
EDGE TRX-004 U WO 703 0 576 0
COMMAND EXECUTED
ETRX N HRS Y PREF N
FREQ 703 TSC 0 FRT 0 (REGULAR) LEV N (NOT USED)
DAL N (NOT USED) DAP 400 LEVD N (NOT USED)
DDU INDEPENDENT SDG 1
SIGN 0 RFHA Y
RTSL PCM-TSL SUB_TSL TYPE I.LEV ADM.STATE OP.STATE CH.STATUS
------------------------------------------------------------------------------
TRANSCEIVER HAS NO INTERFERING CELLS
COMMAND EXECUTED
ETRX N HRS Y PREF N
DDU INDEPENDENT SDG -
------------------------------------------------------------------------------
2 576- 5 2 TCHF 0 UNLOCKED WO ID
MML cmd: ZERO
ADM.STATE OP.STATE
ETRX E HRS Y PREF N
DDU INDEPENDENT SDG 1
SIGN 0 RFHA Y
------------------------------------------------------------------------------
6 576- 4 2 EGTCH 1 UNLOCKED WO GP
7 576- 4 3 EGTCH 1 UNLOCKED WO GP
COMMAND EXECUTED
ETRX N HRS Y PREF N
DDU INDEPENDENT SDG -
------------------------------------------------------------------------------
7 576- 2 3 TCHF 0 UNLOCKED WO GP
MML cmd: ZERO
Start
Unlock TRX
Unlock BTS
End
Unlock BCF
The Service Terminal Restart Phase Monitoring can be used for monitor the restart signalling transferred on BCFSIG. More Information about Restart Phase Monitoring see Course Module Restart Phase Monitoring.
Exercise 1: Abis Integration
Exercise
Create an Abis connection according to your testbed requirements and/or similar to the picture above & right
Create LAPD channels (Multiplexed/Normal)
Unlock TRXs
Unlock BTSs
Unlock BCFs
Interrogating Commands:
Check the radio network status with the command ZEEI (all units should be in working state)
Check the D-Channel states with the command ZDTI
Check the BTS alarms with the command ZEOL (To interpret alarms,
Abis Integration is described in RG10 Documentation:
Integrate\ BSS integration\
Creating Normal D-channels
Activating D- channels
Creating Multiplexed D-channels
Activating D-channels
Creating Dynamic Abis
Creating BCF object
ZEFC:40,X,M:DNAME=B40:::::PORT0=#pcm#,;
Creating BTS object
ZEQC:BCF=40,BTS=400,:CI=#ci#400,BAND=900,CHW=0:NCC=0,BCC=0:MCC=262,MNC=03,LAC=#ci#:
ZEQC:BCF=40,BTS=401,:CI=#ci#401,BAND=1800,CHW=1:NCC=0,BCC=0:MCC=262,MNC=03,LAC=#ci#::
Creating TRX objects
ZERC:BTS=400,TRX=1:DAP=400:FREQ=89,TSC=0,PCMTSL=#pcm#-1:DNAME=T401:CH0=MBCCH,CH1=SDCCH:
ZERC:BTS=400,TRX=2:DAP=400:FREQ=87,TSC=0,PCMTSL=#pcm#-3:DNAME=T402
ZERC:BTS=401,TRX=3:DAP=400:FREQ=701,TSC=0,PCMTSL=#pcm#-5:DNAME=T403:CH0=MBCCH,CH1=SDCCH:
ZERC:BTS=401,TRX=4:DAP=400:FREQ=703,TSC=0,PCMTSL=#pcm#-7:DNAME=T404
Examples:
Flexi BSC: Creating HO & PC paramaters and Starting up BTSplus
Creating handover parameters
Load the Service Terminal extension RPHASESX
Start Restart Phase Monitoring for all sites
Restart one or more sites and observe the restart Phases
Start Restart Phase Monitoring for one site
Restart the BCF and observe the restart Phases
Exercise: RPHASE; Duration ca 20min
HW requirements: 2 working BTS
You are working on BTS……
Load the Service Terminal extension RPHASESX
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________
-BCF restart: example

Abis Integration of BTSplus at Flexi BSC

Documents

Transcript of Abis Integration of BTSplus at Flexi BSC