No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 21-09-2023.

Administering Radio Network for AirScale
BSC

DN223226912
Issue 04
Approved on 2023-02-10

AirScale BSC

Rel. FP23R3
Operating Documentation, Issue 02

© 2023 Nokia. Nokia Condential Information. Use subject to agreed restrictions on disclosure and use.
Administering Radio Network for AirScale BSC

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 21-09-2023.
Nokia is committed to diversity and inclusion. We are continuously reviewing our customer
documentation and consulting with standards bodies to ensure that terminology is inclusive
and aligned with the industry. Our future customer documentation will be updated
accordingly.

This document includes Nokia proprietary and condential information, which may not be
distributed or disclosed to any third parties without the prior written consent of Nokia. This
document is intended for use by Nokia’s customers (“You”/”Your”) in connection with a
product purchased or licensed from any company within Nokia Group of Companies. Use this
document as agreed. You agree to notify Nokia of any errors you may nd in this document;
however, should you elect to use this document for any purpose(s) for which it is not
intended, You understand and warrant that any determinations You may make or actions
You may take will be based upon Your independent judgment and analysis of the content of
this document.

Nokia reserves the right to make changes to this document without notice. At all times, the
controlling version is the one available on Nokia’s site.

No part of this document may be modied.

NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE
CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE FOR ANY DAMAGES,
INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR
CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT,
REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE
FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF
ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.

Copyright and trademark: Nokia is a registered trademark of Nokia Corporation. Other

product names mentioned in this document may be trademarks of their respective owners.

© 2023 Nokia.

2 © 2023 Nokia. Nokia Confidential Information Issue 04

Use subject to agreed restrictions on disclosure and use.

Administering Radio Network for AirScale BSC

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 21-09-2023.
Table of Contents

Summary of changes .................................................................................................................... 4

1 Radio network configuration for Packet Abis ........................................................................... 5

1.1 Creating BCF ...................................................................................................................... 5
1.2 Creating BTS ...................................................................................................................... 8
1.3 Creating TRX ...................................................................................................................... 9
1.4 Deleting network elements ........................................................................................... 11
1.4.1 Deleting a TRX from the BTS ............................................................................. 11
1.4.2 Deleting a BTS from the AirScale BSC .............................................................. 12
1.4.3 Deleting a BCF from the AirScale BSC ............................................................. 14
1.5 Modifying the BTS site type .......................................................................................... 14
1.6 Hopping modes activation of a BTS ............................................................................ 15
1.7 Modifying the BCCH frequency .................................................................................... 16
1.8 Modifying the frequencies other than the BCCH frequency ................................... 18
1.9 Adding an external input and output text .................................................................. 19
1.10 Locking and unlocking radio network elements ...................................................... 21
1.10.1 Locking radio network objects ........................................................................ 21
1.10.2 Unlocking radio network objects .................................................................... 22
1.11 Activating GPRS ............................................................................................................. 24
1.12 Modifying the location area or the cell identity of a BTS ...................................... 25

Issue 04. © 2023 Nokia. Nokia Confidential Information 3

Use subject to agreed restrictions on disclosure and use.

Administering Radio Network for AirScale BSC

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 21-09-2023.
Summary of changes

A list of changes between document issues. You can navigate through the respective changed
topics.

Changes between issues 03 (2019-11-15, AirScale BSC 20 FP2) and 04

(2023-02-10, AirScale BSC FP23R1)
Creating BCF

The note regarding EEP link is modified.

Changes between issues 02 (2019-07-29, AirScale BSC 20 FP1) and 03

(2019-11-15, AirScale BSC 20 FP2)
Radio network configuration for Packet Abis

Note is modified.

Changes between issues 01 (2018-08-30, AirScale BSC 19 FP2) and 02

(2019-07-29, AirScale BSC 20 FP1)
Radio network configuration for Packet Abis

Added a note about the "ActivityState" of the BSC.

4 © 2023 Nokia. Nokia Confidential Information Issue 04

Use subject to agreed restrictions on disclosure and use.

Administering Radio Network for AirScale BSC

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 21-09-2023.
1. Radio network configuration for Packet Abis

Describes the steps to configure radio network on Packet Abis.

Before configuring the radio network, the Packet Abis interface must be configured as described
in the Configuring IP interfaces document.

Note:
If the RC0701: AirScale BSC Georesiliency feature is active, the radio network
configuration changes can be done only when the value of the activityState
parameter is Active.

1.1 Creating BCF

The EFC command is used to create BCF.

Procedure
1 Create BCF with command EFC.

Issue 04. © 2023 Nokia. Nokia Confidential Information 5

Use subject to agreed restrictions on disclosure and use.

Administering Radio Network for AirScale BSC

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 21-09-2023.
EFC: <BCF identification>,

<site type>,

[ <BTS site subtype><option>,

<abis interface connection type> <option> | 0 def,

<packet abis BCF Group ID> <option> | NU def]:

[ AC = <autoconfigure> <option> | N def |

BR = <bit rate> <option> |

AU = <automatic unlock allowed> | 1 def |

REF = <reference BCF identification> |

RXDL = <RX difference limit> | 10 def |

SCTPS = <SCTP parameter set> <option> | AFAST def |

SCTPP = <minimum SCTP port> <option> | 49152 def |

BCXU = <BCXU index> | ND def ] ... :

[ TEST = <identification of test equipment> | NOT def ] :

[ BBU = <BTS battery backup procedure> | ALL def |

NTIM = <TRX shutdown timer> | 0 def |

NTIM2 = <TRX shutdown timer 2> <option> | 0 def |

NTIM3 = <TRX shutdown timer 3> <option> | 0 def |

BTIM = <BCCH TRX shutdown timer> <option> | 0 def ] ... :

[[ CS = <clock source> | NOT USED def |

ADD = <add BCF to chain> ... |

SENA = <synch enabled> | F def ] ... |

[ MCBCF = <master clock BCF identification> ]] :

[ TRS1 = <abis over IP ignalin usage> <option> | 0 def |

TRS2 = <additional 2 E1/T1 if> <option> | 0 def |

TRS3 = <TRS abis grooming usage> <option> | 0 def |

TRS4 = <TRS loop protection usage> <option> | 0 def |

TRS5 = <packet TRX E1/T1 usage> <option> | 0 def ] |

ERPP = < ignalin ring/path protection> <option> |0 def |

QOSA = <QoS aware ignalin switch usage> <option> |0 def |

EOAME = < ignalin OAM enable> <option> |0 def |

RAT = < RAT RF sharing enabled> <option> | 0 def |

[ETMEID = <ETME hardware index> <option> | 255 def |

BCUIP = <BTS C/U-plane IP address>,

6 © 2023 Nokia. Nokia Confidential Information Issue 04

Use subject to agreed restrictions on disclosure and use.

Administering Radio Network for AirScale BSC

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 21-09-2023.
SMCUP = <BTS Ipv4 subnet mask length for C/U-plane>,

BMIP = <BTS M-plane IP address>,

SMMP = <BTS Ipv4 subnet mask length for M-plane>]::

Step example
Example for Packet Abis over Ethernet:

Example with ETMEID:

ZEFC:311,E,,2,:BCXU=0,::::BCUIP="10.1.1.1",BMIP="10.1.1.1",SMCUP
=24,SMMP=24,ETMEID=1,;

Example without ETMEID:

ZEFC:311,M,R,2,:BCXU=0,::::BCUIP="10.1.1.1",BMIP="10.1.1.1",SMCU
P=24,SMMP=24,::;

Note:
This step is executed for each BCF.
New Packet Abis parameters are shown to the operator if Packet Abis over
Ethernet license is in ON or CONF state.
ETMEID is an optional parameter. If not given, system selects the least loaded ETME
for the BCF.
As the system creates the EEP link (ETME-ETMA connection) automatically, do not
create or administer the static route for the AirScale BSC.

2 Attach software package to BCF with the EWA command.

ZEWA:<number of BCF>:<build status>:<build id>;

ZEWA:311:NW:EX4_BL063:;

3 Activate the BCF with the software build with the EWV command.

ZEWV:<number of BCF>:<build status>;

ZEWV:311:NW:;

Has to CONFIRM COMMAND EXECUTION: Y/N ?

Issue 04. © 2023 Nokia. Nokia Confidential Information 7

Use subject to agreed restrictions on disclosure and use.

Administering Radio Network for AirScale BSC

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 21-09-2023.
4 Verify the BCF software attached.

ZEWO:311:;

1.2 Creating BTS

Describes how to add a new BTS to the AirScale BSC.

Procedure
1 Create BTS with the EQC command.

ZEQC:BCF=<BCF identification>,BTS=<BTS identification>,NAME=<BTS

name>,SEG=<SEG identification>,SEGNAME=<SEG name>,REF=<reference
BTS identification>,RNAME=<reference BTS name>:CI=<cell
identity>,BAND=frequency band in use,NCC=<network colour
code>,BCC=<BTS colour code>:MCC=<mobile country
code>,MNC=<mobile network code>,LAC=<location area
code>:HOP=<BTS hopping mode>,HSN1=<hopping sequence number
1>,HSN2=<hopping sequence number 2>,<underlay hopping sequence
number>:GENA=<GPRS enabled>,RAC=<routing area
code>,NSEI=<network service entity identifier>,TRAT=<transport
type>,PSEI=<packet service entity identifier>,PCU=<packet
control unit>RCC=<radio frequency color code>;

Step example
Example for Packet Abis over Ethernet:

ZEQC:BCF=20,BTS=1,SEGNAME=BIGCENTRUM020,NAME=CENTRUM1:CI=12,BAND
=900,NCC=2,BCC=4:MCC=111,MNC=22,LAC=34567:HOP=N,HSN1=3,HSN2=1:GE
NA=Y,RAC=10;

2 Create HOC with the EHC command.

ZEHC:<BTS identification>,<BTS name>,<SEG identification>,<SEG

name>:<reference BTS identification>,<reference
BTSname>,<reference SEG identification>,<reference SEG name>;

8 © 2023 Nokia. Nokia Confidential Information Issue 04

Use subject to agreed restrictions on disclosure and use.

Administering Radio Network for AirScale BSC

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 21-09-2023.
ZEHC:BTS=1,:;

3 Create POC with the EHC command.

ZEUC:<BTS identification>,<BTS name>,<SEG identification>,<SEG

name>:<reference BTS identification>,<reference BTS
name>,<reference SEG identification>,<reference SEG name>:;

ZEUC:BTS=1,:;

1.3 Creating TRX

The ERS command is used to create TRX.

Procedure
1 Create TRX with command ERC.

ERC: ( BTS = <BTS identification> |

NAME = <BTS name> ) ,

TRX = <transceiver identification> :

[[ PREF = <preferred BCCH TRX> | N def ] |

[ ETRX = <E-TRX type> <option> | N def ] |

[ GTRX = <GPRS enabled TRX> <option> | Y def ] |

[ DAP = <dynamic Abis pool id> <option> | N def ] |

FREQ = <frequency> ,

TSC = <training sequence code> ,

BCXU = <BCXU index> | not defined def ] :

[[ LEV = <optimum RX level uplink> | N def ] |

[ LEVD = <optimum RX level downlink> | N def ] |

Issue 04. © 2023 Nokia. Nokia Confidential Information 9

Use subject to agreed restrictions on disclosure and use.

Administering Radio Network for AirScale BSC

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 21-09-2023.
[ FRT = <TRX frequency type> <option> | 0 def ] |

[ DAL = <direct access level> <option> | N def ] |

[ HRS = <TRX half rate support> <option> | Y def ] |

[ RFHA = <RF hopping allowed> <option> | Y def ] |

[ CH0 = <RTSL type 0> | TCHF def ] |

[ CH1 = <RTSL type 1> | TCHF def ] |

[ CH2 = <RTSL type 2> | TCHF def ] |

[ CH3 = <RTSL type 3> | TCHF def ] |

[ CH4 = <RTSL type 4> | TCHF def ] |

[ CH5 = <RTSL type 5> | TCHF def ] |

[ CH6 = <RTSL type 6> | TCHF def ] |

[ CH7 = <RTSL type 7> | TCHF def ]] ... =

[TCHF ... TRAFFIC CHANNEL (FULL RATE)

TCHH ... TRAFFIC CHANNEL (HALF RATE), OPTION

TCHD ... TRAFFIC CHANNEL (DUAL RATE), OPTION

NOTUSED ... RTSL DO NOT HAVE RADIO DEFINITION OR ABIS ALLOCATION

SDCCH ... DEDICATED CONTROL CHANNEL (SDCCH/8)

MBCCH ... BROADCAST CONTROL CHANNEL

MBCCHC ... COMBINED BROADCAST CONTROL CHANNEL (BCCH + SDCCH/4)

MBCCB ... COMBINED BROADCAST CONTROL CHANNEL WITH CELL BROADCAST

CHANNEL (BCCH+CCCH+SDCCH+CBCH)]

[[ DTRX = <dual TRX usage> <option> | def = 0 ] |

[ SDG = <TRX shutdown group> <option> ]] ... :

10 © 2023 Nokia. Nokia Confidential Information Issue 04

Use subject to agreed restrictions on disclosure and use.

Administering Radio Network for AirScale BSC

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 21-09-2023.
Step example
ZERC:BTS=6,TRX=1::FREQ=702,TSC=0,:BCXU=0:CH0=MBCCHC,::::;

1.4 Deleting network elements

Describes the procedure to delete network elements such as TRX, BTS, BCF, and so on from the
AirScale BSC.

1.4.1 Deleting a TRX from the BTS

The user can delete a TRX from a non-hopping, DFCA hopping, or an RF hopping BTS without
disturbing the ongoing calls of the other TRXs of the BTS. If the BTS has an activated BB or
antenna hopping facility, deleting a TRX requires locking the BTS. To save time, several TRXs can
be locked with the same command.

Before you start

Before deleting a TRX, apply the forced handover procedure to minimise traffic in the TRX. As a
result of the system's forced handover procedure, the TRX is barred, no new calls are established
on the TRX, and the system tries to hand over the possible ongoing calls to the neighbouring
TRXs. When all calls on the TRX are handed over to other cells or the time limit controlling the
forced handover procedure expires, the administrative state of the TRX is updated to LOCKED.

Procedure
1 Lock the TRX (ERS) by using the ERS command.

ZERS:<BTS identification or BTS name>,<transceiver

identification>:<administrative state>, <transceiver
identification with frequency(&), <radio time slot
identification ( &,&& )>:;

Several TRXs can be locked at the same time with the wild card characters & and &&.

Issue 04. © 2023 Nokia. Nokia Confidential Information 11

Use subject to agreed restrictions on disclosure and use.

Administering Radio Network for AirScale BSC

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 21-09-2023.
Step example
Lock the TRX with forced handover.

ZERS:BTS=24,TRX=2:L;

or

ZERS:BTS=24,TRX=2&3:L; meaning TRXs 2 and 3,

or

ZERS:BTS=24,TRX=2&&6:L; meaning TRXs from 2 to 6.

2 Delete the TRX (ERD) by using the ERD command.

ZERD:<BTS identification or BTS name>,<transceiver

identification>, <transceiver identification with frequency>;

Step example
Delete the TRX.

ZERD:BTS=24,TRX=2;

The user can also delete a TRX by specifying the TRX frequency (IFREQ) in the command
instead of the TRX identification.

The command deletes the TRX and the related RTSLs from the BSDATA. The D-channel,
which was created during the TRX creation gets deleted.

1.4.2 Deleting a BTS from the AirScale BSC

Before deleting a BTS, apply the forced handover procedure to minimise traffic in the BTS.

Before you start

As a result of the system's forced handover procedure the BTS is barred, no new calls are
established on the BTS, and the system tries to hand over the possible ongoing calls to the
neighbouring BTSes. When all calls on the BTS have been handed over to other cells or the time
limit controlling the forced handover procedure expires, the administrative state of the BTS is

12 © 2023 Nokia. Nokia Confidential Information Issue 04

Use subject to agreed restrictions on disclosure and use.

Administering Radio Network for AirScale BSC

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 21-09-2023.
updated to LOCKED.

Procedure
1 Lock the BTS (EQS).

ZEQS:BTS=<BTS identification>:<administrative state>:<forced

handover>;

Step example
Lock the BTS with forced handover.

ZEQS:BTS=24:L:FHO;

2 Check the state of the BTS (EEI).

ZEEI:BTS=<BTS identification>;

Step example
Wait until the BTS is in the LOCKED state. Check the state.

ZEEI:BTS=24;

3 Delete the BTS (EQD).

ZEQD:BTS=<BTS identification>;

The command deletes the BTS and all related lower-level radio network object instances from
the BSDATA. The D-channel, which was created during the TRX creation gets deleted.

Incoming adjacent cells are not deleted, but the system saves the adjacent cell definitions as
inter-BSS adjacencies. This is useful, for example, in case of a BSS split.

The user can also define in a parameter that the incoming adjacency relations concerning the
deleted BTS are deleted from the BSDATA. The command is then ZEQD:BTS=24:Y;

Step example
ZEQD:BTS=24;

Issue 04. © 2023 Nokia. Nokia Confidential Information 13

Use subject to agreed restrictions on disclosure and use.

Administering Radio Network for AirScale BSC

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 21-09-2023.
1.4.3 Deleting a BCF from the AirScale BSC

Before deleting a BCF, the operator must delete the BTS.

Procedure
1 Lock the BCF before deleting the BCF.

ZEFS:<identify base control function>:<administrative state>:;

Step example
ZEFS:6:L;;

2 Delete the BCF (EFD).

ZEFD:<BCF identification>;

Step example
ZEFD:2;

The command deletes the BCF from the BSDATA. The D-channel, which was created during
the BCF creation gets deleted.

1.5 Modifying the BTS site type

Modifying the BCF type is useful when reconfiguring the radio network.

Purpose
The operator can modify the site type from Flexi Multiradio BTS and Flexi EDGE BTS to Flexi
Compact BTS without deleting the BCF object. The operator can modify Flexi Multiradio 10 BTS to
Flexi Compact BTS by deleting and re-creating BCF.

Modification from Flexi Compact BTS to any other site types than Flexi Multiradio 10 BTS is not
possible.

14 © 2023 Nokia. Nokia Confidential Information Issue 04

Use subject to agreed restrictions on disclosure and use.

Administering Radio Network for AirScale BSC

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 21-09-2023.
If the operator modifies the site to another type, the OMU link of the BCF cannot be in the
working state.

If the operator modifies the site from Flexi EDGE to Flexi Multiradio, the Double Power TRXs
(DPTRX) cannot be configured.

Note:
Flexi EDGE is available only when the Flexi EDGE licence state is ON or CONFIG and Flexi
Multiradio is available only when the Flexi Multiradio licence state is ON or CONFIG.

The system also checks for unsupported software in connection with the modification command
and rejects the command if necessary.

Procedure
1 Lock the BCF by using the following command.

ZEFS:<IDENTIFY BASE CONTROL FUNCTION>:<administrative state>:;

Step example
ZEFS:6:L:;

2 Modify the BCF using the following command.

ZEFM:<IDENTIFY BASE CONTROL FUNCTION>::<BTS SITE SUBTYPE>::::::;

Step example
ZEFM:6::SUBTYPE=F,::::::;

1.6 Hopping modes activation of a BTS

The operator can activate the hopping modes of a BTS by activating BB hopping mode, RF
hopping mode, antenna hopping mode, and DFCA hopping mode.

Issue 04. © 2023 Nokia. Nokia Confidential Information 15

Use subject to agreed restrictions on disclosure and use.

Administering Radio Network for AirScale BSC

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 21-09-2023.
Before you start
To activate the hopping modes, the user must lock the BTS.

Steps for activating the hopping modes of a BTS

To activate the hopping modes, refer the following documents from GSM Supported features for
instructions.

For Antenna hopping mode, see Antenna Hopping in BSS11134: Antenna Hopping. Antenna
hopping can be used with or without RF frequency hopping.
For DFCA (Dynamic Frequency and Channel Allocation) hopping mode, see Activating and
Testing BSS11052: Dynamic Frequency and Channel Allocation.

1.7 Modifying the BCCH frequency

When modifying the BCCH TRX or when frequency hopping is used on the BTS, the BTS must be
locked.

Purpose
When modifying the BCCH TRX or when frequency hopping is used on the BTS, the BTS must be
locked.

Procedure
1 Lock the BTS (EQS).

ZEQS:BTS=<BTS identification or BTS name>:<administrative

state>:;

Step example
ZEQS:BTS=24:L:;

2 Lock the BCCH TRX (ERS).

ZERS:BTS=<BTS identification or BTS name>,TRX=<TRX

identification with frequency>:<administrative state>;

16 © 2023 Nokia. Nokia Confidential Information Issue 04

Use subject to agreed restrictions on disclosure and use.

Administering Radio Network for AirScale BSC

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 21-09-2023.
Step example
Identify the TRX by the old BCCH frequency.

ZERS:BTS=6,TRX=1,:L:;;

3 Modify the BCCH frequency (ERM).

ZERM:BTS=<BTS identification>,TRX=<TRX identification with

frequency>:FREQ=<frequency>;

Step example
ZERM:BTS=6,TRX=1:FREQ=704;

4 Check that the frequency and the BSIC (NCC+BCC) of adjacent cells of all the BTSs remain
unique (EAT).

ZEAT;

The command has no parameters.

Step example
ZEAT;

Check that the frequency and the BSIC (Base Station Identity Code, NCC + BCC) of the
adjacent cells of all the BTSs in the BSDATA remain unique after the BCCH frequency
modification.

5 Unlock the TRX (ERS).

ZERS:BTS=<BTS identification or BTS name>,TRX=<TRX

identification>,<administrative state>;

Step example
ZERS:BTS=5,TRX=1,U;

6 Unlock the BTS (EQS).

ZEQS:BTS=<BTS identification or BTS name>:<administrative

state>;

Issue 04. © 2023 Nokia. Nokia Confidential Information 17

Use subject to agreed restrictions on disclosure and use.

Administering Radio Network for AirScale BSC

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 21-09-2023.
Step example
ZEQS:BTS=24:U;

1.8 Modifying the frequencies other than the BCCH

frequency

When modifying the TRX frequency, the TRX must first be locked by applying the forced
handover procedure.

Purpose
When modifying the TRX frequency, the TRX must first be locked by applying the forced handover
procedure. When frequency hopping is used on the BTS, the BTS must first be locked.

Procedure
1 Lock the BTS if hopping is used (EQS).

ZEQS:BTS=<BTS identification or BTS name>:<administrative

state>:;

Step example
ZEQS:BTS=24:L:;

2 Lock the TRX (ERS).

ZERS:BTS=<BTS identification or BTS name>,IFREQ=<TRX

identification with frequency>:<administrative state>:;

Step example
Identify the TRX by the old frequency.

ZERS:BTS=24,IFREQ=45:L:;

or

ZERS:BTS=24,IFREQ=45:L; (if the BTS was locked in step 1; that is, if frequency
hopping is used.)

18 © 2023 Nokia. Nokia Confidential Information Issue 04

Use subject to agreed restrictions on disclosure and use.

Administering Radio Network for AirScale BSC

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 21-09-2023.
3 Modify the frequency value (ERM).

ZERM:BTS=<BTS identification>,<TRX identification with

frequency>:<frequency>;

Step example
Identify the TRX by the old frequency.

ZERM:BTS=24,IFREQ=45:FREQ=120;

4 Unlock the TRX (ERS).

ZERS:BTS=<BTS identification or BTS name>,IFREQ=<TRX

identification with frequency>:<administrative state>;

Step example
Unlock the TRX.

ZERS:BTS=24,IFREQ=120:U;

5 Unlock the BTS if hopping is used (EQS).

ZEQS:BTS=<BTS identification or BTS name>:<administrative

state>;

Step example
ZEQS:BTS=24:U;

1.9 Adding an external input and output text

The operator can define external input texts for some BTS alarms. In the Nokia Flexi EDGE and
Flexi Multiradio BTSes, the operator can define the texts at the AirScale BSC using the IO_TEXT
object.

Issue 04. © 2023 Nokia. Nokia Confidential Information 19

Use subject to agreed restrictions on disclosure and use.

Administering Radio Network for AirScale BSC

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 21-09-2023.
Procedure
1 Check if a suitable text already exists (EFP).

ZEFP;

Step example
Check if a suitable text already exists.

ZEFP;

As a default, the command outputs all texts in the BSDATA.

2 If there is no suitable text, create a new text (EFE).

ZEFE:<text ID>:<text string>;

Step example
If there is no suitable text, create a new text.

ZEFE:TID=10:TEXT=”SMOKE ALARM”;

3 Connect the text to the BCF.

3.1 Connect the input parameters into BSDATA (EFX).

ZEFX:<BCF identification>:<external input

number>:<route>:<text ID>;

Step example
Connect the text to the BCF. The user can do this online; that is, the BCF does not
have to be locked.

Connect the input parameters into BSDATA.

ZEFX:2:INBR=3:ROU=ACT:TID=10;

3.2 Connect the output parameters (EFM).

ZEFM:<BCF identification>:<text ID of the output from OUT1

to OUT6>;

20 © 2023 Nokia. Nokia Confidential Information Issue 04

Use subject to agreed restrictions on disclosure and use.

Administering Radio Network for AirScale BSC

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 21-09-2023.
Step example
Connect the output parameters.

ZEFM:2:OUT1=10;

1.10 Locking and unlocking radio network elements

Provides the commands to lock and unlock the radio network elements.

1.10.1 Locking radio network objects

The commands to lock the TRX, BTS, and BTS site are ERS, EQS, and EFS commands respectively.

Locking the TRX

The user can lock the TRX with the command ERS.

Locking the TRX sets the TRX and its RTSLs to the administrative state LOCKED. No traffic is
carried on a LOCKED TRX.

Locking the TRX is needed when modifying some TRX-specific parameters in the radio network;
for instance, when modifying the frequencies, or when deleting a TRX.

To save time, several TRXs can be locked with the same command.

To avoid calls getting disconnected, in the network, lock the TRX by applying the system's forced
handover procedure, controlled by the forced handover (FHO) parameter. In a forced
handover, the TRX is barred, no new calls are established on the TRX, and the system tries to
hand over the possible ongoing calls to the other TRXs of the BTS. When all calls on the TRX have
been handed over to other cells or the time limit controlling the forced handover procedure
expires, the administrative state of the TRX is updated to LOCKED.

Locking the BTS

The user can lock the BTS with command EQS.

Locking the BTS sets the BTS to the administrative state LOCKED. All TRXs under the BTS change

Issue 04. © 2023 Nokia. Nokia Confidential Information 21

Use subject to agreed restrictions on disclosure and use.

Administering Radio Network for AirScale BSC

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 21-09-2023.
to the BL-USR (blocked-user) operational state, but remain UNLOCKED if they have not been
locked with their own locking command. No traffic is carried on a LOCKED BTS.

Locking the BTS is needed when modifying some BTS-specific parameters in the radio network;
for instance, when modifying the location areas, cell identities, frequencies, and hopping modes or
when deleting the BTS.

To avoid calls getting disconnected in the network, lock the BTS by applying the system's forced
handover procedure, controlled by the forced handover (FHO) parameter. In a forced
handover, the BTS is barred, no new calls are established on the BTS, and the system tries to
hand over the possible ongoing calls to the neighbouring BTSs. When all calls on the BTS have
been handed over to other cells or the time limit controlling the forced handover procedure
expires, the administrative state of the BTS is updated to LOCKED.

Locking the BTS site

The user can lock the BTS site with the EFS command.

Locking the BTS site sets the BCF in the administrative state LOCKED. All lower-level objects under
the BCF change to the BL-USR (blocked-user) operational state, but remain UNLOCKED if they
have not been locked with their own locking commands. No traffic is carried on a LOCKED BCF.

Locking the BCF is rarely needed when modifying the radio network, but when modifying the BTS
site type; for instance, the BCF has to be locked after the BTSes have been locked by applying
forced handover. The BCF also needs to be locked before it can be deleted.

1.10.2 Unlocking radio network objects

ERS, EQS, and EFS commands are used to unlock the network elements.

Unlocking the TRX

The user can unlock the TRX with the ERS command.

Unlocking an object causes a reset. Unlocking a higher-level object also resets all the UNLOCKED
lower-level objects under it.

The user can monitor the operational states of the TRXs and RTSLs with the EEI, EEL, and ERO
commands. Active alarms concerning the TRXs are cancelled in the initialization. If the TRX is still
found faulty after the initialisation, the corresponding alarm indications are generated again to the
AirScale BSC alarm printer, sent to NetAct, and automatic radio network recovery actions are

22 © 2023 Nokia. Nokia Confidential Information Issue 04

Use subject to agreed restrictions on disclosure and use.

Administering Radio Network for AirScale BSC

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 21-09-2023.
initiated.

Possible fatal anomalies in the communication between the BTS and the AirScale BSC during the
initialisation phase are indicated using the AirScale BSC alarm printer and NetAct.

The user can unlock several TRXs with the same command if the BTS or BCF is in the LOCKED
admistrative state.

If the related BCF and BTS are in the administrative state UNLOCKED, the TRX state transition
from LOCKED to UNLOCKED causes a reset of the TRX on the BTS site.

The system sets the operational states of the TRX and UNLOCKED RTSLs to BL-RST (BLOCKED -
RESET). After the successful TRX reset procedure, the operational states of the TRXs and the
RTSLs receive the value WORKING. The operational state value WORKING indicates that the objects
have been initialized and are available for call control purposes.

Unlocking the BTS

The user can unlock the BTS with the EQS command.

Unlocking an object causes a reset. Unlocking a higher-level object also resets all the UNLOCKED
lower-level objects under it.

The user can monitor the operational states of the BTS, TRXs, and the RTSLs with the EEI,EEL,
EQO, and ERO commands. Active alarms concerning the TRXs of the BTS are cancelled in the
initialization. If some of these TRXs are still found faulty after the initialization, the corresponding
alarm indications are generated again to the AirScale BSC alarm printer, sent to NetAct, and
automatic radio network recovery actions are initiated.

Possible fatal anomalies in the communication between the BTS and the AirScale BSC during the
initialisation phase are indicated using the AirScale BSC alarm printer and NetAct.

If the related BCF is in the administrative state UNLOCKED, the BTS state transition from LOCKED
to UNLOCKED causes resets on the BTS site for all UNLOCKED TRXs of the BTS.

The system sets the operational states of the BTS, UNLOCKED TRXs, and the RTSLs to BL-RST
(BLOCKED - RESET). After a successful BTS reset procedure, the operational states of the BTSes,
TRXs, and RTSLs receive the value WORKING. The WORKING state value means that the objects
have been initialized and are available for call control purposes.

Unlocking the BTS site

The user can unlock the BTS site with the EFS command.

Unlocking an object causes a reset. Unlocking a higher-level object also resets all the UNLOCKED

Issue 04. © 2023 Nokia. Nokia Confidential Information 23

Use subject to agreed restrictions on disclosure and use.

Administering Radio Network for AirScale BSC

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 21-09-2023.
lower-level objects under it.

The user can monitor the operational states of the BCF, BTSs, TRXs and RTSLs with the EEI,
EEL, EFO, EQO, and ERO commands. Active alarms concerning the BSS are cancelled in the
initialisation. If faults still exist in the BSS after the initialisation, the corresponding alarm
indications are generated again to the AirScale BSC alarm printer, sent to NetAct, and automatic
BSS radio network recovery actions are initiated.

The user can also monitor various phases of BCF operations on the display of the service terminal
with the service terminal extension BCF Reset Phase Monitoring.

Possible fatal anomalies in the communication between the BTS and the AirScale BSC during the
initialisation phase are indicated using the AirScale BSC alarm printer.

The system downloads the default software build of the BCF to the BTS site if the build is not
available in the non-volatile memory of the BCF. The logical radio network configuration is sent to
the BTS site according to the BSDATA.

The system sets the operational states of the BCF, UNLOCKED BTSes, TRXs and the RTSLs to BL-
RST (BLOCKED-RESET) state. After a successful BTS site reset procedure, the operational states of
the BCF, BTSes, TRXs and RTSLs receive the value WORKING. The WORKING state value means
that the objects have been initialised and are available for call control use.

1.11 Activating GPRS

Describes the procedure to activate GPRS.

Procedure
1 Activate GPRS with command EQV.

ZEQV:BTS=<BTS identification>:<GPRS enabled>,<routing area

code>:<network service entity identifier>:<DTM enabled>;

Step example
ZEQV:BTS=21:GENA=Y,RAC=10,BFG=1,EXKEEP=10::EAW=MO&WE&FR,EAS=08-0
0, EAE=18-00:DENA=Y;

24 © 2023 Nokia. Nokia Confidential Information Issue 04

Use subject to agreed restrictions on disclosure and use.

Administering Radio Network for AirScale BSC

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 21-09-2023.
1.12 Modifying the location area or the cell identity of a BTS

Steps to modify the location area and cell identity of a BTS.

Procedure
1 Lock the BTS by applying the forced handover procedure.

ZEQS:BTS=24:L:FHO;

2 Wait until the BTS is in the LOCKED state (check the state with the EEI command) and then
modify the location area or the cell identity of the BTS.

ZEQE:BTS=24:LAC=3344,CI=13000;

or

ZEQE:SEG=124:LAC=3344,CI=13000;

3 Disable GPRS in the cell.

ZEQV:BTS=24:GENA=N;

or

ZEQV:SEG=124:GENA=N;

4 Wait untill the GPRS disabled in the cell (check the state with the EQO command).

Step example
ZEQO:BTS=24:GPRS;

or

ZEQO:SEG=124:GPRS;

5 Modify the cell LA or CI information to the adjacent cell lists of the other cells in the AirScale
BSC and in the other AirScale BSCs of the network which have the modified cell defined as an
adjacent cell.

Give the command for each BTS ID or SEG ID, which have the modified cell defined as an
adjacent cell:

Issue 04. © 2023 Nokia. Nokia Confidential Information 25

Use subject to agreed restrictions on disclosure and use.

Administering Radio Network for AirScale BSC

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 21-09-2023.
ZEAM:BTS=250::LAC=3344,CI=14000:NEWLAC=3344,NEWCI=13000;

ZEAM:BTS=269::LAC=3344,CI=14000:NEWLAC=3344,NEWCI=13000;

or:

ZEAM:SEG=124::LAC=3344,CI=14000:NEWLAC=3344,NEWCI=13000;

ZEAM:SEG=245::LAC=3344,CI=14000:NEWLAC=3344,NEWCI=13000;

6 Enable GPRS in the cell.

ZEQV:BTS=24:GENA=Y;

or

ZEQV:SEG=124:GENA=Y;

7 Unlock the BTS.

ZEQS:BTS=24:U;

26 © 2023 Nokia. Nokia Confidential Information Issue 04

Use subject to agreed restrictions on disclosure and use.