Glossary (danh sch, cc t chuyn mn)

BSC CF CON DP IS MO RX TF TG TRXC TS TX pooltraf DCP=dcp DCP1=dcp1 DCP2=dcp2 Base Station Controller Central Functions-nhim v chnh, chc nng trung tm LAPD Concentrator-tp trung Digital Path Interface Switch Managed Object Receiver Timing Function(chc nng nh thi) Transceiver Group Transceiver Controller Time Slot Handler-b iu khin khe thi gian Transmitter-my pht The number of transcoder resources currently used in traffic per pool. Digital connection point number-s im kt ni s Digital Connection Point (DCP) number used for the signalling path to the TRXC Numeral 0 - 511 DCP number used for the speech and data connections to the TRXC Two DCP2s, for TRXCs using 16 Kbps Abis paths, or eight DCP2s, for TRXCs using 64 Kbps Abis paths, must be given. The DCP2s given must be consecutive(lin tc). The DCP2s are sorted into ascending order. If two DCP2s are given, the lower range DCP2 value is associated(kt hp) with TSs 0 to 3, and the higher range DCP2 is associated with TSs 4 to 7. If eight DCP2s are given, the lower range DCP2 value is associated with TS 0 and the higher range DCP2 value is associated with TS 7. Numeral 0 - 511 Signalling type UNCONC Unconcentrated CONC LAPD Concentration MPLEX16

SIG=sig

TEI OML RXD BCCH

16K Multiplex MPLEX32 32K Multiplex Terminal Endpoint Identifier(nhn dng) Operation and Maintenance(bo dng) Link RECEIVER DIVERSITY- nhy thu

Broadcast Control Channel-knh iu khin qung b DCHNO=dchno(TCH) Absolute radio frequency channel number(ng,chnh xc) Maximum 32 Absolute Radio Frequency Channel Number (ARFCNs) per channel group are allowed. (31 if channel group 0). Numeral 128 - 251 (GSM 800) Numeral 1 - 124 (GSM 900, P-band) Numeral 0, 975 - 1023 (GSM 900, G1-band) Numeral 512 - 810 (GSM 1900) Numeral 512 - 885 (GSM 1800) HOP=hop Frequency hopping status OFF The hopping status for the channel group is nonhopping. ON The hopping status for the channel group is hopping for Traffic Channel (TCH) and Stand-alone Dedicated Control Channel (SDCCH). HSN=hsn Hopping sequence number Numeral 0 - 63 CBCH=cbch Cell broadcast channel This parameter indicates if Cell Broadcast Channel (CBCH) is included in the Stand Alone Dedicated Control Channel (SDCCH). YES CBCH will be included in one of the SDCCH/8 for a cell or a channel group NO No SDCCH/8 for a cell or a channel group will include CBCH CELL=cell Cell designation

This is a symbolic name of a defined cell. CHGR=chgr Channel group number Numeral 0 - 15 SDCCH=sdcch Required number of SDCCH/8 Numeral 0 - 32 (with combined BCCH 31) TN=tn Timeslot number Numeral 0 - 7 cgi Cell global identification- nhn dng ton cu(khu vc) Expressed as(biu din,trnh by) mcc-mnc-lac-ci where: mcc Mobile country code mnc Mobile network code lac Location area code ci Cell identity- nhn dng BCCHNO=bcchno Absolute radio frequency channel number for Broadcast Control Channel (BCCH) Absolute Radio Frequency Channel Number (ARFCN) already defined for a dedicated channel cannot be given. Numeral 128 - 251 (GSM 800) Numeral 1 - 124 (GSM 900, P-band) Numeral 975 - 1023, 0 (GSM 900, G1-band) Numeral 512 - 885 (GSM 1800) Numeral 512 - 810 (GSM 1900) BCCHTYPE=bcchtype BCCH type This parameter indicates the combinatons of wanted logical channels on the frequency and timeslot defined for the BCCH in the cell. COMB Combined control channel Indicates that the cell has a combined BCCH and Stand Alone Dedicated Control Channel (SDCCH)/4. COMBC Combined control channel with a Cell Broadcast Channel (CBCH) subchannel

Indicates that the cell has a combined BCCH and SDCCH/4 with a CBCH subchannel. NCOMB Non-combined control channel Indicates that the cell does not have any type of combined BCCH and SDCCH/4. This parameter applies only to internal cells RLCRP:CELL=
64k 64kbit/s Mode Supported CS3CS4 The Basic Physical Channel (BPC) supports General Packet Radio Service (GPRS) CS-3 or CS-4 EGPRS The BPC supports Enhanced(lm tng, nng cao) General Packet Radio Service (EGPRS) NONE The BPC does not support EGPRS or GPRS CS-3 or CS-4 Broadcast Control Channels (BCCHs) This parameter indicates the number of deblocked BCCHs in the cell. Basic Physical Channel individual

bcch bpc

This individual is also printed in the RADIO XCEIVER ADMINISTRATION MANAGED OBJECT CONFIGURATION DATA printout, thus linking the configured logical channels with the Base Transceiver Station (BTS) equipment used for them. cbch Cell Broadcast Channels (CBCHs) This parameter indicates the number of deblocked CBCHs in the cell. cell Cell designation This is a symbolic name of a defined cell. channel Logical channel identity This parameter consists of the channel type and an individual number. chband Channel band This parameter indicates the frequency band for the logical channel. The channel band is printed for deblocked channels. 800 GSM 800 The BPC holding the channel is configured on one or several Absolute Radio Frequency Numbers (ARFCN) within the GSM 800 band in the range 128 - 251. 1800 GSM 1800

1900

The BPC holding the channel is configured on one or several ARFCNs within the GSM 1800 band in the range 512- 885. GSM 1900 The BPC holding the channel is configured on one or several ARFCNs within the GSM 1900 band in the range 512- 810.

P900

Primary GSM 900 The BPC holding the channel is configured on one or several ARFCNs exclusively within the primary GSM 900 band in the range 1 - 124.

Extended GSM 900 The BPC holding the channel is configured on at least one ARFCN in the extended 'G1' GSM 900 band in the range 0, 975 1023. chgr Channel group number chrate Channel rate FR Full rate HR Half rate chtype Channel type BCCH Broadcast Control Channel CBCH Cell Broadcast Channel SDCCH Stand Alone Dedicated Control Channel TCH Traffic Channel icmband Current idle channel interference band The interference is measured on an idle channel and the value range,from negative to positive infinity (dBm), is divided into 5 intervals which are called idle channel interference bands. Interference band 1 is the band with the lowest interference. Interference band 5 is the band with the highest interference. An idle or busy SDCCH or TCH belongs to one of the idle channel interference bands. Numeral 1 - 5 noofch Number of deblocked logical channels A logical channel in state idle, busy or locked is regarded as a deblocked channel. nooftch Number of traffic channels This number can have a lower and an upper limit. This is because there are BPCs configured with the possibility to be

E900

sdcch

spv

state

allocated either as full rate traffic channels (then counted as one channel) or half rate traffic channels (then counted as two channels). These channels are called dual rate channels. In a channel group or a cell, dual rate channels can be mixed with those of a fixed channel rate. Stand Alone Dedicated Control Channel (SDCCH) This parameter indicates the number of deblocked SDCCHs in the cell. Speech version If a traffic channel is configured with the possibility to be allocated for either of several speech versions, this parameter shows all the possible speech versions (for example spv = 1,2). Logical channel state BLOC Blocked BUSY Busy IDLE Idle LOCK Locked If a BPC is configured with the possibility to be allocated either as a full rate traffic channel or two half rate traffic channels, the channel state LOCK is applicable. When one channel rate is allocated to a BPC, the logical channel or channels of the other rate on the same BPC are locked.

NONE

No data existed to be printed. EOT DURING PRINTOUT The operator has cancelled the printout. FAULT INTERRUPT fault type A fault interruption occurred during printing. Fault type: FORMAT ERROR The command was incorrectly specified. UNREASONABLE VALUE details A parameter was specified with an unreasonable value. FAULT CODE 3 CELL NOT DEFINED details

The cell is not defined. FAULT CODE 19 CELL RESOURCES HAVE CHANGED Cell Resources have changed since printout started. FAULT CODE 27 CELL DATA CHANGE IN PROGRESS Modification of cell data by a command is in progress. FAULT CODE 38 COMMAND NOT VALID FOR EXTERNAL CELLS details The command is not valid for external cells. FAULT CODE 120 CELL STATE NOT ACTIVE details The cell has not been activated. BA-list BCCH Allocation list

1.rxtcp:cell=hni,moty=rxotg; xem TG ca trm

Parameters: thng s, tham s, tham bit, gii hn Associated: kt hp, lin kt dedicated to: c tnh cht chuyn mn represented by: trnh by bi, biu din bi

2.dtdii:dip=,snt=,dipp=;
Initiate: bt u, khi u, xng Sequence: trnh t, kt ni

3.ntcop:snt=all; xem lung tha hay thiu

SNT=snt DIPINF Switching network terminal Digital path information related to the Switching Network Terminal (SNT) All switching network terminals

ALL

SNTP=sntp Switching network terminal connection point

4.rlcrp:cell=hni; lnh kim tra thu bao chim knh

- CBCH: Cell Broadcast Channel-knh qung b - NOOFTCH: Number of traffic channels

This number can have a lower and an upper limit. This is because there are BPCs configured with the possibility to be(c kh nng,c th) allocated(phn phi,cp pht,nh r v tr) either as(chn 1 trong hai vn ) full rate traffic channels (then counted as one channel) or half rate traffic channels (then counted as two channels). These channels are called dual(hai, i) rate channels. In a channel group or a cell, dual rate channels can be mixed(ln ln,pha trn,hn hp) withthose of a fixed(ng yn,c nh) channel rate. icmband Current idle channel interference band The interference is measured on an idle channel and the value range,from negative to positive infinity (dBm), is divided into 5 intervals which are called idle channel interference bands. Interference band 1 is the band with the lowest interference. Interference band 5 is the band with the highest interference. An idle or busy SDCCH or TCH belongs to one of the idle channel interference bands. Basic Physical Channel

BPC

5.rxcdp:mo=rxotg-tg;

xem cu hnh ca trm

- arfcn:Absolute Radio Frequency Channel Number: s knh tn s radio chun -txad:TX logical address. Numeric value in the range 0 to 31 C0f Carrier zero filling(lm y,ph y) YES Carrier zero filling is turned on. NO Carrier zero filling is turned off.

6. rxmfp:mo=rxots-TG-TRX-TS0&&-TS7;xem s cuc
gi trn ts. conerrcnt Counter for the number of abnormally(khc thng) terminated connections concnt Counter for the number of connection setup attempts(c gng

lm g)

7. H cu hnh:
-dtstp:dip=m trm;(xem trm nm BSC no) -rxtcp:moty=rxotg,cell=m trm1;(xem TG) (rxmfp:mo=rxotg-TG;) -rxmsp:mo=rxotg-TG,subord;(xem cu hnh ca trm) -rxbli:mo=rxotrx-TG-TRX,subord,force;;(lnh blok TRX) -rxese:mo=rxotrx-TG-TRX,subord;;(lnh xa TRX) rxmoe:mo=RXOTX-125-6 ; rxmoe:mo=RXOTS-125-6-0 ; rxmoe:mo=RXOTS-125-6-1 ; rxmoe:mo=RXOTS-125-6-2 ; rxmoe:mo=RXOTS-125-6-3 ; rxmoe:mo=RXOTS-125-6-4 ; rxmoe:mo=RXOTS-125-6-5 ; rxmoe:mo=RXOTS-125-6-6 ; rxmoe:mo=RXOTS-125-6-7 ; rxmoe:mo=RXORX-125-6 ; rxmoe:mo=RXOTRX-125-6 ; (rxcdp:mo=rxotg-TG;) +execute: thc hin,thc hin ch dn ca my tnh,hnh hnh, hnh quyt. -rxmsp:mo=rxotg-TG,subord;(xem cu hnh ca trm) FORCE Forced blocking indication(s ch dn) SUBORD Subordinate MOs (di quyn) All of the MO instances subordinate to the specified MO are included. Parameter SUBORD may be used for a Transceiver Group (TG) or Transceiver Controller (TRXC) in Base Transceiver Station (BTS) logical model G01 and TG, Central Function (CF) or TRXC in the BTS logical model G12.

8.Tch hp trm:
-rlcfp:cell=m trm;(xem SDCCH,nhy tn) -rldep:cell= m trm;(xem CGI) -dtqup:dip= m trm;(lnh xem h s trt ca bit) -rxmop:mo=rxotg-tg;(ly version) Khai mi: -ntcop:snt=etm...;

-dtdii:dip=m trm,snt=emt...,dipp=...;; -dtbli:dip=m trm;; -dtble:dip=m trm;; -dtstp:dip=m trm;(xem lung c hay cha) Xem ta lung ti BSC: -dtdip:dip=ten tram; i tn dip(khi khai lung nhng b nhm v khi c dip) -dtpnc:dip=m trm mi,newdip=..., -dtble:dip=m trm; -dtstp:dip=m trm; Xa dip: -dtbli:dip=m trm;; -dtdie:dip=m trm;;

Khai inner(bn trong, ni b) cell: ----- Khai bao cell tren MSC----mgcei:cell=M trm1,CGI= mcc-mnc-lac-ci1,BSC=BHNI; mgcei:cell=M trm2,CGI= mcc-mnc-lac-ci2,BSC=BHNI; mgcei:cell=M trm3,CGI= mcc-mnc-lac-ci3,BSC=BHNI;
a, Parameters BSC=bsc Base Station Controller (BSC) name The BSC to which the cell is connected. CELL=cell CGI=cgi See Application Information for block MTRAN. Cell name See Application Information for block MTRAN. Cell Global Identity (CGI) See Application Information for block MBSSD.

b, Function
This command initiates a new mobile telephony cell in the Mobile Services Switching Centre and Visitor Location Register (MSC/VLR) Server. The new cell is connected to a Base Station Controller. When the first cell is defined in location area, it defines the location area as well. The order remains after system restart.

Ch : mgcep:cell=m trm bt k no 1;(lnh in ra) Ch : lnh xa CGI trn MSC: phi print cc cell ny trn BSC xem cell ny cn tn ti khng sau mi thc hin cng vic xo: mgcee:cell=m trm cell1; mgcee:cell=m trm cell2; mgcee:cell=m trm cell3;

Khai GPRS: rlgsi:cell=m trm...;(khai c 3 cell)

Khai outer(bn ngoi) cell(nu cdd yu cu gia cc MSC):

mgoci:cell=HTY3156,cgi=452-04-12121-21926,msc=MHN2; Cc li c th trong CG: Khai bao INTERNAL: + BSIC: phi l hai ch s(v d: 8=08) Khai bao TCH cho cell(xem tht k) +rlcfi:cell=NDH3064,CHGR=1,DCHNO=768&771&774&777&780&7
83&786&789&792&795&798&801&804&807;

+rlcfi:cell=NDH3065,CHGR=1,DCHNO=769&772&775&778 &781&784&787&790&793&796&799&802&805&808; +rlcfi:cell=NDH3066,CHGR=1,DCHNO=770&773&776&779 &782&785&788&791&794&797&800&803&806&809; +relation. Thong tin tram moi: Xem version(thay i version): + RXMOI:MO=RXOTGtg,TRACO=POOL,COMB=HYB,RSITE=m trm,SWVER=B4402R011L; Xem m cell: + RXMOC:MO=RXOTRX-tg-trx0, CELL=m trm...;(i vi trm 1800 s cell c nh l cell4,cell5,cell6). CH : Khai bao POWERCONTROL(ch phin bn phn mm) Khai bao Power UL(ch phin bn phn mm) Khi to dev: BLODI:DEV=RBLT;

(Lnh (Lnh

ny c s dng deblock device s chuyn t trng Idle thi

thnh trng thi ABL(Automatic Block))

EXDAE:DEV=RBLT;
ny c s dng a cc Time Slot (tng ng thut ng

Device) chuyn t trng thi In Service thnh trng thi pre-post service)

EXDAI:DEV=RBLT;(Lnh

ny c s dng a cc Time Slot (tng ng thut ng Device) chuyn t trng thi pre-post service thnh trng thi In Service)

BLODE:DEV=RBLT;(Lnh

ny c s dng deblock device

s chuyn t trng thi ABL(Automatic Block) thnh trng thi Idle)

Chy lnh v Dng li kim tra: + Khi to Abis: RXAPI:MO=RXOTG-tg,DEV=RBLT2513&&-543,DCP=1&&31; (Lnh ny c s dng nh ngha mt hoc nhiu Abis + Lnh active cell.

paths gia mt BSC v mt BTS. RBLT l device (TS) kt ni t BSC ti BTS. DCP l s nhn dng device .)

+ a cc MO sang trng thi In- Service RXESI:MO=RXOTG-28,SUBORD;(ch full cnh bo v) Lnh ny c s dng a MO (bao gm TG, CF, CON, TF, TRX, TX, RX, TS) vo dch v. C ti 32 MO c th nh ngha trong mt lnh. Nh s dng thng s SUBORD m ta ch dng 1 lnh m c th tc ng n tt c cc MO con ca TG-nh v d trn. + Deblock cc MO: RXBLE:MO=RXOTG-28,SUBORD; Lnh ny c s dng deblock MO. RLSTC: CELL=HNIPDL1,STATE=ACTIVE; RLSTC: CELL=HNIPDL2,STATE=ACTIVE; RLSTC: CELL=HNIPDL3,STATE=ACTIVE; Lnh ny c s dng thay i trng thi ca Cell hoc CHGR. C cc trng thi l ACTIVE hoc HALTED.

Ch : nu TCH HP b hin tng local mode c th do cc nguyn nhn sau:

-khai sai TEI(c th do c BSC v BTS) -trong lc tch hp mt kt ni hoc do DXU c vn

-cha active dch v(EXDAI, BLODE, RXAPI) -do di trm BTS cha chuyn sang ch remove +, nu do BSC sai do khai TEI th cch cha li nh sau: -rxbli:mo=rxotg-tg,subord,force; -rxese:mo=rxotg-tg,subord; -rxmoc:mo=rxotg-tg,tei=62(thm nu i sang Con hoc Uncon); -rxesi:mo=rxotg-tg,subord; -rxble:mo=rxotg-tg,subord;

9.Thay i tham s handover:

-RLIHC:CELL=cell,iho=; -RLIHC:CELL=cell, SSOFFSETULP=gi tr dng, SSOFFSETULN=ga tr m, QOFFSETULP=gi tr dng, QOFFSETULN=ga tr m, SSOFFSETDLP= ga tr dng, SSOFFSETDLP= ga tr m, MAXIHO=, TMAXIHO=, TIHO=, -RLLUC:CELL=cell, QLIMUL=;

10.Thay i lac:
-RLSTC:CELL=,STATE=HALTED; -rldep:cell=,cgi= mcc-mnc-lac-ci; -rldec:cell=,cgi= mcc-mnc-lac-ci; -rlsbc:cell=,t3212=; mcc Mobile country code Numeral 3 digits mnc Mobile network code For the number of digits see the Application Information for block ROEPC. lac Location area code Numeral 1 - 65535 ci Cell identity Numeral 0 - 65535 CH : -Xem s lng thu bao(mgsvp;) MSC trc v sau khi thay i LAC(ghi li gi-s thu bao) -phi gim T3212 theo yu cu ca CDD trc khi thay -Nu khng c LAI MSC khi thay i LAC th dng lnh khai: MGLAI:LAI=--; -khai inner cell v outer theo yu cu ca CDD (mgbsp:bsc=all; xem tn BSC)-(mgnmp:msc=all; xem tn MSC)

11.Thay i con-uncon: khi nng cp ri(khng cn thit)

Nu l dng con: -rxmop:mo=rxocon-tg;(xem con) -rxmoc:mo=rxocon-tg,dcp=64&&87;(dng cho con) -rxesi:mo=rxocon-tg;(xa) -rxble:mo=rxocon-tg;(to li con)

12. Lnh reset trm:

-rxbli:mo=rxotg-tg,subord,force;(bloking-ngt i) -rxble:mo=rxotg-tg,subord;(deblok-to li) Lnh reset cell: -rxbli:mo=rxotrx-TG-TRX,subord,force;;(lnh blok TRX) -rxble:mo=rxotrx-TG-TRX,subord;;(deblok-to li TRX)

13. dtbli:dip=m trm;

/ \ |dip...| DTBLI:DIP=+ +; |ALL| \ / a, Parameters DIP=dip Digital path name Identifier(nhn ra, nhn dng) 1 - 7 characters ALL b, Function The command initiates(bt u) blocking of the specified digital path. The order(cp, bc, loi, hng) remains after system restart. All digital paths

14. Lnh deblock dip:

/ \ |dip...|

DTBLE:DIP=+ +; |ALL |
\ /

a, Parameters DIP=dip Digital Path (DIP) name Identifier 1 - 7 characters ALL All DIPs See the Application Information for block DIPST.

b, Function This command deblocks the specified DIPs. The order remains after system restart.

15. Lnh kim tra card(hoc reset):

-exemp:rp=all,em=all; -dirrp:rp=all; -blrpi:rp=RP,forced;(block) -blrpe:rp=RP;(deblock) 16. Lnh khng a vo dch v: a, Command / \ |MO=mo... | RXESE:+ +; |MO=mo[,SUBORD]| \ / b, Parameters MO=mo Managed Object (MO) instance See Application Information for block RXCTA for the format and the value range of this parameter. All MO classes are valid. SUBORD Subordinate MOs All of the MO instances subordinate to the specified MO are included. Parameter SUBORD may be used for a Transceiver

Group (TG) or Transceiver Controller (TRXC) in the Base Transceiver Station (BTS) logical model G01 and TG, Central Function (CF) or TRXC in the BTS logical model G12. c, Function This command orders the removing managed objects from service into prepost service. The MO must be manually blocked, that is in state COM. Up to 32 MOs can be specified. The MO instances(trng hp,v d) from different BTS logical models can not be mixed(hn hp). The answer printout RADIO X-CEIVER ADMINISTRATION MANAGED OBJECT OUT OF SERVICE COMMAND RESULT will be printed giving the result of the command for all specified MO. The subsequent result printout RADIO X-CEIVER ADMINISTRATION MANAGED OBJECT OUT OF SERVICE COMMAND RESULT will be printed giving the result of the command for all specified MO. The appearance of answer or result printout depends on exchange property OSSPRINTVER described in Application Information for block ROEPC. If this MO instance was the last removed object from service in a TG, the observation alarm RADIO X-CEIVER ADMINISTRATION MANAGED OBJECTS IN TRANSCEIVER GROUP MANUALLY BLOCKED will be ceased. The order in which the MOs are brought out of service in BTS logical model G01 is Time Slot (TS) and Receiver (RX) before the corresponding TRXC; TRXC, Timing Function (TF) and Transmitter (TX) before the corresponding TG. The order in which the MOs are brought out of service in BTS logical model G12 is RX, TX and TS before the corresponding TRXC; Interface Switch (IS), Concentrator (CON), TRXC, TF, and Digital Path (DP) before the corresponding CF; CF before the corresponding TG. The parameter SUBORD allows the specified MO instance and its subordinates to be brought out of service. The order remains after system restart.

17. Lnh a vo dch v:

a, Command / \ |MO=mo... | RXESI:+ +; |MO=mo[,SUBORD[,NOPRINT]] | \ / b, Parameters MO=mo Managed Object (MO) instance See Application Information for block RXCTA for format and value range of this parameter. All MO classes are valid. NOPRINT No result printout This parameter suppresses the result printout when parameter SUBORD has been specified. SUBORD Subordinate MOs All of the MO instances subordinate to the specified MO are included. Parameter SUBORD may be used for a Transceiver Group (TG) or Transceiver Controller (TRXC) in the Base Transceiver Station (BTS) logical model G01 and TG, Central Function (CF) or TRXC in the BTS logical model G12. c, Function This command orders bringing Managed Objects into service from prepost service. Up to 32 MOs can be specified. The MOs must be defined, that is, in state DEF. The MO instances from different BTS logical models can not be mixed. Once an MO has been brought into service it will initially be manually blocked, that is, in state COM. An attempt is then made to load the MO. The answer printout RADIO X-CEIVER ADMINISTRATION MANAGED OBJECT IN SERVICE COMMAND RESULT will be printed giving the result of the order for each of the MO instances specified by the MO parameter.

A subsequent result printout RADIO X-CEIVER ADMINISTRATION MANAGED OBJECT IN SERVICE RESULT will be given when the inservice order is completed for all MO instances. If this MO is the first object brought into service in a TG, the observation alarm RADIO X-CEIVER ADMINISTRATION MANAGED OBJECTS IN TRANSCEIVER GROUP MANUALLY BLOCKED will be raised. The order in which the MOs are brought into service in BTS logical model G01 is TG before the corresponding TRXC, Transmitter (TX) and Timing Function (TF); TRXC before the corresponding Time Slot (TS) and Receiver (RX). The order in which the MOs are brought into service in BTS logical model G12 is TG before the corresponding CF; CF before the corresponding Interface Switch (IS), Concentrator (CON), TRXC, TF and Digital Path (DP); TRXC before the corresponding RX, TX and TS. The parameter SUBORD, which may only be used in conjunction with a single MO instance, will print the status of that MO instance and all its subordinates. Upto a maximum of one-hundred and eighty-three MOs can be returned when specifying the SUBORD parameter. When using parameter SUBORD, MO instances will only be processed if their superior MOs are also defined. The parameter NOPRINT, which may only be used in conjunction with parameter SUBORD, suppresses the result printout. The order remains after system restart.

18.Lnh xem lung v xem casce ca trm: rxapp:mo=rxotg-TG; 19.Ch khi nng cp: -nhy tn -Thay i gia con v uncon;(c th phi xem cu hnh trc ca trm l dng con hay uncon bng lnh: rmop:mo=rxotf-

tg;). Nu nng ln cu hnh 4/4/4 th phi dng CON cho tt c cc TRX. RXMOC:MO=RXOCF-TG,TEI=62,SIG=CONC; RXMOI:MO=RXOCON- TG,DCP=64&&87; RXMOI:MO=RXOTRX- TG TEI,DCP1=..,DCP2.., SIG=CONC; (Thm cc TRX c lin quan) RXMOI:MO=RXOTRX- TG -TEI, DCP1=..,DCP2.., SIG=CONC; (Thm cc TRX c lin quan) RXMOC:MO=RXOTRX-TG-TRX,SIG=CONC;(Thay i cc TRX khng lin quan) -Dng lnh halted v active: rlstc:cell=m trm1,state=halted; rlstc:cell=m trm2 ,state=halted; rlstc:cell=m trm3 ,state=halted; rlstc:cell=m trm1,state=active; rlstc:cell=m trm2,state=active; rlstc:cell=m trm3,state=active; Khng dng nhy tn hay nhy tn: -Change cells (when FHOP=BB and cell C has one CHGR=0) RLCCC:CELL=m trm1,SDCCH=2,TN=2; RLCFI:CELL=m trm1,DCHNO=; -when FHOP=SY and cell C has two CHGRs=0,1! RLCCC:CELL= m trm1,CHGR=1,SDCCH=1,TN=1; 20. Xa cell:
rlcrp:cell=cell; rxtcp:cell= cell,moty=rxotg; rlvle:cell= cell,chtype=tch;(xa gim st) rlvle:cell= cell,chtype=sdcch;(xa gim st) rldee:cell= cell(lnh xa)

21. Lnh tng SAE: saaep:sae=502,BLOCK=RTAPH;

saaii:sae=502,BLOCK=RTAPH,ni=2048;(s ni ph thuc vo s thay i ca sae) RXMOI:MO=RXOTRX-67-6, TEI=6, DCP1=146, DCP2=147&148, SIG=UNCONC; rxmoe:mo=rxotrx-67-6; 22. Thm tn s cho cell:
-Them tan so: trm BTS v thay rlccc ging nh rlcfp theo cr: rlcfi:cell=sla0221,CHGR=0,DCHNO=68; rlcfi:cell=sla0222,CHGR=0,DCHNO=72;

Hin tng Unused hoc Block TRX:

-Trm unused c th do thiu tn s. -C th halted li cell ri active nu l Unused.(Xem lnh RXMSP) -Dng lnh RLBDC thay i NUMREQBPC(khi khng th thay i c knh SDCCH) nu l Unused. -Nu khng tng c knh SDCCH do TN(TN=1, hay TN=1&2) -Khi chuyn trm m mt s trm c hin tng block mt s TRX th c th do nhm lung. -Do khai sai bng tn GSM900-GSM1800, cng sut pht 47dbm-45dbm nu Block. -Do gn sai TEI cho cell nn TX b block. -i vi chgr=2 trm chung TG nu TX unused v MISMATCH=cell th c th do li khai sai TRX gn cho mt tn cell ca trm khc.

23. Dng cho trm chung TG: RXMsc:MO=RXOTF-TG1,TFMODE=M;(tram chu) RXMsc:MO=RXOTF-TG2,TFMODE=S,TFCOMPNEG= 4580(do ti u-hi ng cu);
TFCOMPNEG Timing function negative compensation value This is the distribution delay between the master TG and slave TG, plus own TG transmitter chain delay, minus the master TG transmitter chain delay, given in nanoseconds. Numeral 1 - 10000 TFCOMPPOS Timing function positive compensation value This is the distribution delay between the master TG and slave TG,

plus own TG transmitter chain delay, minus the master TG transmitter chain delay, given in nanoseconds. Numeral 0 - 10000 OMT TF compensation value configured from OMT within the TG Synchronization function Timing function synchronization mode This is the mode of the timing function in the TG. M Master, synchronized from the synchronization source and distributed to other TFs The availability of this parameter value depends on commercial agreements. S Slave, synchronized from other TF The availability of this parameter value depends on commercial agreements. SA Standalone, synchronized from synchronization source

TFMODE

24. Xa TCH v thm TCH: Rlstc:cell=,state=halted;

Rlcfe:cell=,chgr=,dchno=; Rlcfi:cell=,chgr=,dchno=;

Rlstc:cell=,state=active; 25. Lnh xa chgr v tn s: Rlstc:cell=,state=halted;

RLCHC:CELL=,CHGR=,HOP=on hoc off,HSN=hoc 0,maio=,bccd=;(thay i Yes hoc No) Rxtce:mo=rxotg-tg,cell=,chgr;(ngt chgr) Rldge:cell=,chgr;(xa chgr)

Rlstc:cell=,state=active; 26. Quan h gia cc cell:

RLNRC:CELL=cell,CELLR=cellr,+ Nu l xa: RLNRE

1, Function a, Format 1 This command changes neighbour relation data for defined relations. Format 1 is used for the Ericsson1 algorithm. See parameter EVALTYPE in command RLLBC. Issuing a command of format 1 with all optional parameters included will result in a too long command line exceeding the maximum input buffer size of 140 characters. In this case, the command needs to be given two times with some optional parameters in the first command and the rest in the second command so that the maximum input buffer size is not exceeded. For details about the default values see Application Information for block RQCD. The order remains after system restart. b, Format 2 This command changes neighbour relation data for defined relations. Format 2 is used for the Ericsson3 locating algorithm. See parameter EVALTYPE in command RLLBC. For details about the default values see Application Information for block RQCD. The order remains after system restart.

27. BA list v Relation: BA list:

1.1 Command:
RLMFC:CELL=cell,MBCCHNO=mbcchno...[,LISTTYPE=listtype] [,MRNIC];

1.2 Parameters
CELL=cell Cell designation

This is a symbolic name of a defined cell. LISTTYPE=listtype Type of measurement frequency list. This parameter indicates in which mode the Mobile Station (MS) will measure on the frequencies in the list. ACTIVE

Measurement frequency list to be used by active MSs

IDLE MBCCHNO=mbcchno

Measurement frequency list to be used by idle MSs

Absolute Radio Frequency (RF) channel number for measurement on Broadcast Control Channel (BCCH) The number is the absolute RF channel number for the BCCH for cells to be measured on by a MS in the cell. Numeral 128 - 251 (GSM 800) Numeral 1 - 124 (GSM 900, P-band) Numeral 975 - 1023, 0 (GSM 900, G1-band) Numeral 512 - 885 (GSM 1800) Numeral 512 - 810 (GSM 1900)

MRNIC

Measurement results not interpreted correctly At updating of the measurement frequencies, measurement results are not interpreted correctly for a period of time.

2 Function
This command initiates or adds frequencies that MSs will measure on in the cell. If the type of measurement frequency list is not specified, then both idle and active lists are changed. The command is only valid for internal cells, which are, cells belonging to the current Base Station Controller (BSC). If MRNIC is specified, or the cell state is halted, then the updating of the measurement frequencies is performed immediately. In this case the measurement results are not interpreted correctly for a period of time. EXECUTED will be printed. If MRNIC is not specified, the updating of the measurement frequencies is performed over a period of time and the measurement results are interpreted correctly. ORDERED will be printed and the result printout ADDITION OF CELL MEASUREMENT FREQUENCIES COMPLETED is received. If the global system type is MIXED, it is possible to add frequencies in the combination of GSM 800 band, GSM 900 band, and GSM 1800 or GSM 1900 band. The frequencies in G1 band can only be defined in a cell if the feature Extended GSM Frequency Band support is available. The availability of this feature depends on commercial agreements. Basically up to 32 measurement frequencies can be defined in a frequency list. If the global system type is MIXED, the following restrictions will apply according to the band in which the BCCH is defined and the combination of measurement frequency bands. The following restrictions apply to both IDLE and ACTIVE list types. In a few cases, when BCCH is in GSM 900 P band or undefined, the restrictions apply to IDLE list only (See Note 5 below). If the list type is not specified, it is set to BOTH. When the list type is set to BOTH, the restrictions are checked for both IDLE and ACTIVE lists.

Li:

EXECUTED ORDERED NOT ACCEPTED fault type Fault type:

FUNCTION BUSY The function is busy. FORMAT ERROR details The command or a parameter was incorrectly specified. UNREASONABLE VALUE details The parameter was specified with an unreasonable value. FAULT CODE 3 CELL NOT DEFINED The cell is not defined. FAULT CODE 14 MBCCHNO ALREADY GIVEN details The measurement frequency has already been given. FAULT CODE 21 MAXIMUM NUMBER OF MBCCHNO EXCEEDED The maximum number of measurement frequencies is exceeded. See chapter "2 Function" in this document for the maximum number of measurement frequencies that can be defined in a measurement frequency list. FAULT CODE 38 COMMAND NOT VALID FOR EXTERNAL CELLS The command must not be used for external cells, which are cells belonging to another BSC. FAULT CODE 50 ACTIVE BA-LIST RECORDING IS ACTIVE It is not possible to change neither the active list nor the idle list when the function Active BA-List Recording is active for the cell. FAULT CODE 171 PARAMETER VALUE NOT SUPPORTED BY THIS EXCHANGE details The possibility to define an MBCCHNO in G1 GSM band depends on commercial agreements. Contact the sales organization.

Relation:
1.1 Command
RLNRI:CELL=cell,CELLR=cellr[,SINGLE];

1.2 Parameters
CELL=cell Cell designation This is a symbolic name of a defined cell. CELLR=cellr Related cell designation This is a symbolic name of a defined related cell. SINGLE Single direction cell relation This parameter defines the relation to be a one way relation between the cell and cellr. It means that handover can only be made from CELL to CELLR When SINGLE is not given, the relation will be mutual, which means that handover in both directions is allowed.

2 Function
This command defines relations between cells. The type of relation between the cells can be either mutual or one-way. When relation is mutual, handover in both directions is allowed. Mutual relation is default. Relation to an external cell, which is a cell in another Base Station Controller (BSC) or a cell using another Radio Access Technology (RAT), must be SINGLE. To change the direction of a relation, the neighbour relation must be deleted using command RLNRE and a new relation defined. It is allowed to define up to 64 Global System for Mobile Communication (GSM) neighbours and 64 UMTS Terrestrial Radio Access Network (UTRAN) Frequency Division Duplex (FDD) neighbours to a cell. The order remains after system restart.

28. Radio Control Cell, Dynamic HR Allocation Data, Change:

RLDHC:CELL=cell+[,DHA=dha][,DTHAMR=dthamr] [,DTHNAMR=dthnamr]+;

29. Thay i nhy tn-BB hoc SY:

In BTS Logical Model G01 / RXMOC:MO=mo...+[,FHOP=fhop][,SWVER=swver][,COMB=comb] \

[,RSITE=rsite][,TRACO=traco][,CONFACT=confact] \ [,CONFMD=confmd][,EMG=emg]+; / In BTS Logical Model G12 / RXMOC:MO=mo...+[,FHOP=fhop][,SWVER=swver][,COMB=comb] \ [,RSITE=rsite][,TRACO=traco][,CONFACT=confact] [,CONFMD=confmd][,SIGDEL=sigdel][,AHOP=ahop] \ [,ABISALLOC=abisalloc]+; /

30. Layer(Tng, lp):

RLLHC:CELL=HNI5093,LAYER=2,LAYERTHR=80,LAYERHYST=2,PSSTEMP= 0,PTIMTEMP=0,FASTMSREG=OFF;

31. Thay i CLS state:

rllci:cell=HTY0032;(active hay inactive)
/ |/ \/ \ RLLCC:CELL=cell+|,CLSLEVEL=clslevel||,CLSACC=clsacc| |\ /\ / \ / \ |,HOCLSACC=hoclsacc| \ / \ / \/ \| |,RHYST=rhyst||,CLSRAMP=clsramp|+; \ /\ /|
/

32. Thay i tham s HR cho cell: RLDMI:Cell=.;(bt hay tt DMSUPP- RLDME)

/ RLDMC:CELL=cell+[,DMQB=dmqb] \[,DMQG=dmqg] [,DMQBAMR=dmqbamr] [,DMQBNAMR=dmqbnamr] [,DMQGAMR=dmqgamr] [,DMQGNAMR=dmqgnamr] [,DMTHAMR=dmthamr] \ [,DMTHNAMR=dmthnamr]+;

33. Xem EM v xem TRX:

EXEMP:RP=ALL,EM=ALL; ntcop:snt=all;

34. Kim tra s TRXs:

Command to check current number of TRXs: RXMSP:MOTY=RXOTRX;
Select the appropriate action according to the fault:

LOF or LOS

Failure(mt kh nng) in receive direction(s iu khin) detected(nhn ra,pht hin ra) by local termination equipment. Go to Step 34.

ALL1 or AIS

Alarm indication(du hiu) signal transmitted by remote(t xa, xa) end termination equipment due to(do , nh c) failure upstreams. Further action is outside the scope of this Operational Instruction. Consult the next level of maintenance support and return to Step 50 in this Operational Instruction.

RDI
Remote defect(mt ht) indication. Failure in transmit(truyn ,pht tn hiu) direction detected by remote end termination equipment. Go to Step 34.

ERATE or CSES
Severe degradation of signal. Go to Step 43. LOMF or REFM Faults related to multiframe signalling (TS16). Go to Step 38.

AISM

Alarm indication signal in TS16 transmitted by remote end termination equipment due to failure affecting the signalling upstreams. Further action is outside the scope of this Operational Instruction. Consult the next level of maintenance support and return to Step 50 in this Operational Instruction. Other faults Further action is outside the scope of this Operational Instruction. Consult the next level of maintenance support and return to Step 50 in this Operational Instruction.

35. Khi to ng dn cuc gi: RAPTI:LCH=2485;

Tracing(dau vet, lan theo) and printing(in ra) of connections using logical channel number 2485 is made.

36. Xem s TG dang hoat dong va so TRX dang su dung: rxmsp:moty=rxotg; rxmsp:moty=rxotrx; 37. Li v LRDEC:
FAULT CODE 50 ACTIVE BA-LIST RECORDING( c ghi) IS ACTIVE

When the cell state is ACTIVE and Active BA-List Recording is active for the cell, it is not possible to change the RF channel for BCCH.

Sa li 1: a, Command
/ \ |rid...| RABRP:RID=+ +; |ALL | \ /

b, Parameters
RID=rid Active BA-list Recording Identity Identifier BARID00 - BARID63 ALL All RIDs

C,Function
This command is used to print the details of one, several or all RIDs. The printout ACTIVE BA-LIST RECORDING DETAILS will be given. The order does not remain after system restart.

Sa li 2: A, Command
RABRE:RID=rid[,MRNIC];

B, Parameters
MRNIC Measurement Results Not Interpreted(trnh din,th hin) Correctly(ng n,ph hp) When re-creating the active BA-lists, Measurement Results are interpreted incorrectly during(trong thi gian) a few minutes. Active BA-list Recording Identity Identifier BARID00 - BARID63

RID=rid

C, Function
This command is used to interrupt a recording for one RID, before the duration time has elapsed. The command is only accepted for RIDs that are in state RECORDING or CONFIGURATION OF BA-LISTS. The state of the interrupted RID will then change to RECORDING COMPLETE. If MRNIC is specified, then the re-creation of the active BA-lists is performed immediately. In this case the measurement results are interpreted incorrectly during a few minutes, e.g. a faulty handover can occur. Otherwise, the re-creation of the active BA-lists is performed over a period of time and the measurement results are

interpreted correctly. The printout ACTIVE BA-LIST RECORDING TERMINATION RESULT will be given when the recording is ended. The printout is routed both to the ordering IO device and to the IO device indicated by the printout category. The order does not remain after system restart.

D, Examples
3.1 Example 1
RABRE:RID=BARID00,MRNIC; The active BA-list recording will be terminated for the RID BARID00. When updating the active BA-lists, measurement result will not be interpreted correctly for a period of time.

38. Lin qua n BA-list(dng khc c th cha dng)

/ \ |,CELL=cell... | | / \| |,CELL=ALL |,CSYSTYPE=csystype|| RABDE:RID=rid + \ /+; | / \ | | |tmbcchno...| | |,TMBCCHNO= + + | | |ALL | | \ /

a, Parameters
CELL=cell Cell designation Symbolic name, maximum 7 characters ALL

All Internal cells CSYSTYPE=csystype System Type Identifier GSM800 GSM 800 GSM900 GSM 900 GSM1800 GSM 1800 GSM1900 GSM 1900 RID=rid Active BA-list Recording Identity Identifier BARID00 - BARID63 TMBCCHNO=tmbcchno Absolute Radio Frequency (RF) channel number for test measurement on BCCH Numeral 128 - 251 (GSM 800)

Numeral Numeral Numeral Numeral

0 - 124 (GSM 900) 975 - 1023 (GSM 900) 512 - 885 (GSM 1800) 512 - 810 (GSM 1900)

The number is the absolute RF channel number for the BCCH for cells to be measured on by a mobile station in the cell. ALL

All TMBCCHNOs connected to the RID

b,Function
This command removes cells or frequencies from an active recording. During the recording the frequencies are included in the active BCCH Allocation (BA) lists, for all cells connected to the RID. It is possible to remove one cell, several cells, all cells or all cells of a specific system type from a RID or remove one frequency, several frequencies or all frequencies from a RID. The command is only accepted for RIDs that are in state ALLOCATED, USED or RECORDING COMPLETE. If all cells are removed from the RID the state is changed to ALLOCATED. The order does not remain after system restart.

C, Examples
- Example 1
RABDE:RID=BARID15,CELL=KNA11; Removes the cell KNA11 from the RID BARID15.

- Example 2
RABDE:RID=BARID25,CELL=ALL,CSYSTYPE=GSM1900; Removes all cells of the system type GSM 1900 from the RID BARID25.

- Example 3
RABDE:RID=BARID37,TMBCCHNO=530&&550; Removes TMBCCHNOs 530 up to 550 from the RIDBARID37.

- Example 4
RABDE:RID=BARID53,TMBCCHNO=ALL; Removes all the test BCCH frequencies from the RID BARID53.

39.Lnh print cc ETM:

1.1 Command
/ \ |SDIP=sdip... | TPSTP:[IO=io,]+ +; |SDIP=ALL[,STATE=state...]| \ /

1.2 Parameters
IO=io SDIP=sdip Input/Output (IO) device name Identifier 1 - 7 characters Synchronous Digital Path (SDIP) name Identifier 1 - 7 characters ALL All SDIPs State of SDIP BLOC Blocked PBLOC Partly blocked TRAFBLOC Traffic blocked TRAFLIM Traffic limited WO Working

STATE=state

2 Function
This command prints the state of specified SDIP on specified or default IO device. Printout SYNCHRONOUS DIGITAL PATH STATE is received. Up to 10 SDIPs can be specified in each command. The order does not remain after system restart.

3 Examples
3.1 Example 1
TPSTP:SDIP=LONDON;

The state of SDIP LONDON is printed.

3.2 Example 2
TPSTP:IO=AT-4,SDIP=LONDON&OSLO; The state of the SDIPs LONDON and OSLO is printed on IO device AT-4.

3.3 Example 3
TPSTP:SDIP=ALL; The state of all SDIPs is printed.

3.4 Example 4
TPSTP:IO=AT-4,SDIP=ALL,STATE=WO&BLOC; All working and all blocked SDIPs are printed on IO device AT-4.

40. Deblock cc ETM: 1.1 Command

/ // \\\ | ||,MS=ms...||| |sdip|+,HP +|| | ||,HP=hp...||| TPBLE:SDIP=+ ||,LP=lp...||+; | \\ //| |sdip... | | | |ALL | \ /

1.2 Parameters
HP=hp Higher order Path (HP) For the value ranges, see the Application Information for SDIP owning block. LP=lp Lower order Path (LP) For the value ranges, see the Application Information for SDIP owning block. MS=ms Multiplex Section (MS) For the value ranges, see the Application Information for SDIP owning block. SDIP=sdip Synchronous Digital Path (SDIP) name Identifier 1 - 7 characters ALL All SDIPs

2 Function
This command deblocks either the whole SDIP including all existing lower layers, or only the MS, the HP, or the LP when they are specified. Result printout SYNCHRONOUS DIGITAL PATH DEBLOCKING RESULT is received. Up to 10 SDIPs can be specified in each command. The order remains after system restart.

3 Examples
3.1 Example 1
TPBLE:SDIP=LONDON; The whole SDIP LONDON is manually deblocked.

3.2 Example 2
TPBLE:SDIP=LONDON,MS=MS-0&-1; The MS-0 and MS-1 within SDIP LONDON are manually deblocked.

3.3 Example 3
TPBLE:SDIP=LONDON,HP; The HP within SDIP LONDON is manually deblocked.

3.4 Example 4
TPBLE:SDIP=LONDON,LP=VC12-0&&-47; The LPs VC12-0 to VC12-47 within SDIP LONDON are manually deblocked.

3.5 Example 5
TPBLE:SDIP=LONDON&OSLO&NACKA; The SDIPs LONDON, OSLO, and NACKA are manually deblocked.

3.6 Example 6
TPBLE:SDIP=ALL; All SDIPs are manually deblocked.

3.7 Example 7
TPBLE:SDIP=CHICAGO,HP=STS1-0&-1 The HPs STS1-0 and STS1-1 within SDIP CHICAGO are manually deblocked.

41. Dng blocking RP:

1.1 Command
BLRPI:RP=rp[,FORCED];

1.2 Parameters
RP=rp Regional Processor (RP) address Numeral 0 - 1023

The maximum value is defined by the Size Alteration Event (SAE) 304 FORCED Blocks RP regardless of Extension Module (EM) state and device state.

2 Function
This command is used when blocking an RP, where the logical state of the RP is set to Manually Blocked (MB). The bus senders are blocked from sending signals on the RP bus. In the case of RPs with an EM bus, the control of the connected equipment, EMs, is transferred automatically, if possible, to the twin RP through local restarts of the EMs. If the control of EMs cannot be transferred, all EMs linked to the RP and all devices connected to the EMs must be manually blocked before the command can be accepted. For some RPs without EM bus it is sufficient that all devices connected to the EMs are manually blocked before the command can be accepted. If the parameter FORCED is given, the RP is blocked regardless of EM state and device state. This parameter shall be used with care as it can result in traffic disturbance. Special checks requested by EM owner to ensure that critical IO-channel system resources are not lost, are still done. For some RP types without an EM bus, the commands for blocking and deblocking of EM are not applicable. The operational state for the EM is then controlled by blocking and deblocking the RP. For these RPs, some checks normally performed at BLEMI are performed at BLRPI instead. The order remains after system restart.

3 Examples
3.1 Example 1
BLRPI:RP=2;

An RP with address 2 is blocked (if EM state and device state are manually blocked).

3.2 Example 2
BLRPI:RP=5,FORCED; An RP with address 5 is blocked regardless of EM state and device state.

42. Remove EM(expension module):

1.1 Command
EXEME:RP=rp[,RPT=rpt],EM=em;

1.2 Parameters
EM=em RP=rp Extension Module (EM) address Numeral 0 - 63 Regional Processor (RP) address Numeral 0 - 1023

Actual maximum value is defined by Size Alteration Event (SAE) 304. RPT=rpt RP address for twin(sinh i, cp i) RP Numeral 0 - 1023 Actual maximum value is defined by SAE304.

2 Function
The command is used in order to remove the definition of an EM. Devices connected to the EM must be manually blocked. Also the EM must be blocked except(tr ra, loi ra) for the RP-types for which EM blocking command is not applicable(c th ng dng c). For these RP-types the RP must be blocked instead(thay vi, thay cho). If the EM is controlled by an RP pair, both the RP addresses must be indicated(chi ra). The order remains after system restart.

3 Examples
3.1 Example 1
EXEME:RP=16,RPT=17,EM=4; The definition of the EM with address 4, in the RP pair which consists of RPs 16 and 17, is removed.

3.2 Example 2
EXEME:RP=50,EM=5; The definition of the EM with address 5, in the single RP 50, is removed.

43. Lnh ny dng xa Regional Software Units (RSU):

1.1 Command
/ \ | / \| | |ALL || / \ |SUNAME=+ +| |RP=rp... | | |suname|| EXRUE:+ +,+ \ /+; |RP=rp,RPT=rpt| | / \ | \ / | |ALL | | |SUID=+ + | | |suid| | | \ / | \ /

1.2 Parameters
RP=rp Regional Processor (RP) address Numeral 0 - 1023 The maximum value is defined by Size Alteration Event (SAE) 304. Regional Processor Twin (RPT) address Numeral 0 - 1023 The maximum value is defined by SAE=304. Software Unit (SU) identity Identifier 1 - 32 characters

RPT=rpt

SUID=suid

If the identifier contains any character, other than letters or digits then the string must be given within quotation marks. SUNAME=suname SU name Identifier 1 - 8 characters

2 Function
Command EXRUE is used to delete defined Regional Software Units (RSU) in an RP (RP pair) or in a suite of RPs. The specified suite of RPs must not consist of more than 128 RPs.

The specified RP or RPs must be manually blocked (not blocked for repair or blocked for function change). Parameter SUID must be specified if more than one version of the specified SU is defined. If a specific SUNAME (SUID) is given, it must be defined in all the specified RPs. The RSUs must be deleted at the same time for both RPs in an RP pair. The two addresses in the pair can be specified in two different ways as follows: With parameters RP and RPT With parameter RP for both addresses

If the command is used to delete definitions of SUs in more than one RP (RP pair) at a time, all the RP addresses (including the RPT addresses) must be specified with parameter RP. An RSU of type Firmware Replacement Package (FRP) shall not be deleted unless it shall be replaced or it is faulty. This is to avoid that, at repair of RPs, an RP board is entered and started with an old FRP RSU. Although an FRP RSU is removed by command EXRUE the FRP RSU will continue to be working in the RP (if it once has been loaded to the RP). The order remains after system restart.

3 Examples
3.1 Example 1
EXRUE:RP=7,RPT=8,SUNAME=RPFDR; The definition of the RSU with name RPFDR in RP 7 and RPT 8 is deleted.

3.2 Example 2
EXRUE:RP=7,SUID="5/CAA1053092/1R1A02"; The definition of an RSU with product identity 5/CAA 105 3092/1 R1A02 in RP 7 is deleted.

3.3 Example 3
EXRUE:RP=7&20,SUNAME=RPFDR; The definition of the RSU with name RPFDR in RP 7 and RP 20 is deleted.

3.4 Example 4
EXRUE:RP=7&&20,SUNAME=RPFDR;

The definition of the RSU with name RPFDR in the RP suite RP 7 through RP 20 is deleted.

3.5 Example 5
EXRUE:RP=7&&20,SUNAME=ALL; All RSU definitions in the RP suite RP 7 through RP 20 are deleted.

3.6 Example 6
EXRUE:RP=25,SUID="9000/CXC 152 001 R1A01"; The FRP RSU definition with product identity 9000/CXC 152 001 R1A01 in RP 25 is deleted. If loaded to the RP, the FRP will not be removed from the RP.

44. Lnh ny dng remove cc RP:

1.1 Command
EXRPE:RP=rp[,RPT=rpt];

1.2 Parameters
RP=rp Regional Processor (RP) address Numeral 0 - 1023

The maximum value is defined by Size Alteration Event (SAE) 304. RPT=rpt RP twin address Numeral 0 - 1023 The maximum value is defined by SAE 304.

2 Function
This command is used in order to remove the definition of an RP or an RP pair. The command requires that the affected RP is manually blocked and and that the definition of associated equipment has been removed. If the RP is loadable, all Software Unit (SU) definitions must also be removed (by command EXRUE). The order remains after system restart.

3 Examples

3.1 Example 1
EXRPE:RP=17; The definition of a single RP, with address 17, is removed.

3.2 Example 2
EXRPE:RP=17,RPT=8; The definition of an RP pair, with addresses 17 and 8, is removed.

45. Khi to li RP:

1.1 Command
EXRPI:RP=rp[,RPT=rpt],TYPE=type[,DEFRSU];

1.2 Parameters
DEFRSU RP=rp Define Regional Software Units Regional Processor (RP) address Numeral 0 - 1023 The maximum value is defined by Size Alteration Event (SAE) 304. RP twin address Numeral 0 - 1023

RPT=rpt

The maximum value is defined by SAE 304. TYPE=type RP type Text string 1 - 7 characters

2 Function
This command initiates RP equipment for the specified RP-address (or addresses) and for the specified type of RP. If parameter DEFRSU is given then default Operating System (OS) Regional Software Units (RSU), as specified in database table RPSDEFOSRSUS, are defined for the RP. The effect of parameter DEFRSU is the same as if these RSUs had been defined by command EXRUI after command EXRPI. Possible RP types are described in Application Information for block RPADM. All valid types of RPs, with characteristics and properties of the different types, can be listed by printing the database tables RPSRPTYPES, RPSTYPESTOPROPS and RPSRPPROPERTIES.Use generic DBS print command DBTSP.

The order remains after system restart. Note: Also an RSU of type Firmware Replacement Package (FRP) can be defined for the RPs by use of parameter DEFRSU. FRP RSUs can be included in the DBS table RPSDEFOSRSUS.

3 Examples
3.1 Example 1
EXRPI:RP=17,TYPE=RPM1A; An RP of type RPM1A is defined. It has RP address 17.

3.2 Example 2
EXRPI:RP=17,RPT=8,TYPE=RPM6A; An RP pair of type RPM6A is defined. The pair will control the same EMs. The pair has RP addresses 17 and 8.

3.3 Example 3
EXRPI:RP=30,RPT=31,TYPE=RPM2B; An RP pair of type RPM2B is defined. It has RP addresses 30 and 31.

3.4 Example 4
EXRPI:RP=20,type=STC1A; A Signalling Terminal Central (STC) with RP address 20 is defined.

3.5 Example 5
EXRPI:RP=40,TYPE=RPI1A,DEFRSU; An RP of type RPI1A is defined. Default OS RSUs are defined for the RP. The RP has RP address 40.

46. Khi to cc kt ni SNT:

1.1 Command
/ |[SNTP=sntp,]SNT=snt...[,IDLEP=idlep] \ |

| | |SNTP=sntp...,SNT=snt[,IDLEP=idlep] | | | NTCOI:+SNTP=sntp,SNT=snt,EQLEV=eqlev,PROT=prot[,IDLEP=idlep] +,SNTV=sntv; | | |SNTP=sntp,SNT=snt[,MODE=mode][,PROT=prot][,IDLEP=idlep]| | | |EXTP=extp,SNT=snt[,MG=mg] | \ /

1.2 Parameters
EQLEV=eqlev Equipping level This parameter is only intended for Switching Network Terminal (SNT) with Subordinate SNTs and protection. For value range, see the Application Information for SNT-owning block. External Hardware Connection Point This parameter is only intended for the connection of SNT to External Hardware Switch. If the SNT-owning block supports parameter MG then the EXTP parameter value has to be written within quotation marks. For string range, see the Application Information for SNT-owning block. IDLEP=idlep Idle pattern For value range, see the Application Information for block SNTH. Media Gateway This parameter is only intended for the connection of SNT to External Hardware Switch. Text string 1 - 7 characters Mode This parameter is only intended for the connection of DL34 SNTs. For value range, see the Application Information for SNT-owning block. Protection This parameter indicates if equipment protection is used. This parameter is only intended for SNT with Subordinate SNTs and protection. For value range, see the Application Information for SNT-owning block. Switching network terminal

EXTP=extp

MG=mg

MODE=mode

PROT=prot

SNT=snt

Expressed as snt-n where: snt Switching network terminal type Identifier 1 - 13 characters n Switching network terminal number Numeral 0 - 65535 The maximum value of the switching network terminal number is determined by Size Alteration Event (SAE) in the SNT-owning block (SAE 529). For alternative expressions, see the Application Information for block TRAN and the relevant SNT-owning block. Switching network terminal connection point Expressed as a-b-c where: a b c

SNTP=sntp

Switch unit name Identifier 1 - 7 characters Switch unit number Switching network terminal point See Application Information for block TRASAD. Expressed as a-b-f or a-d-e-f where:

a Switch unit name Identifier 1 - 7 characters b d e f Switch unit number Switch unit row number Switch unit column number Digital link number

SNTV=sntv

See Application Information for block SNTH Switching network terminal variant For value range, see the Application Information for SNT-owning block.

2 Function
This command connects a Switching Network Terminal (SNT) to a Group Switch (GS), a Subscriber Switch (SS), or an External Switch. For SNTs with subordinate

SNTs or SNTs to be connected to an external switch, one SNT can be connected in one command issue. For SNTs of any other type, the maximum of 32 SNTs can be connected. For an SNT with several hardware connections to the GS, the connection is made in consecutive order according to the designations of these connections. For DL3 SNTs with subordinate SNTs the number of the subordinate SNTs to be connected are indicated by parameter EQLEV. Also the equipment protection can be specified for this type of SNT with parameter PROT . For DL34 SNTs with subordinate SNTs, the number of Multiple Points (MUPs) to be reserved by the GS is indicated by parameter MODE. For SNTs connected to an External Switch, parameter SNTP is not allowed. Parameter EXTP should be used instead indicating the connection point (port) of the External Hardware Switch. If this SNT supports connection to a Media Gateway (MG), parameter MG should be used indicating the MG name. Parameter IDLEP may be specified only when this parameter is supported by the specified SNTs. Note: Three adaptation blocks exist in the AXE, SNTPCD, SNTET and SNTMJ. These are used to connect device types which are not SNT owners. For SNTs connected in adaptation blocks, the SNT type is defined when the first SNT of that type is connected. This is not specified in a separate parameter but is implicit in the command. The order remains after system restart.

3 Examples
3.1 Example 1
NTCOI:SNT=SNTPCD32-2,SNTP=TSM-1-2,SNTV=5; The SNT of type SNTPCD 32, variant 5 and individual 2 is connected to the SNT connection point 2 in Time Switch Module (TSM) 1.

3.2 Example 2
NTCOI:SNT=ET1-0,SNTV=1; The SNT of type ET1, variant 1 and individual 0 is connected to the SNT connection.

3.3 Example 3
NTCOI:SNTP=TSM-12-3&&-4,SNT=ASAM-0,SNTV=1; The SNT of type ASAM, variant 1 and individual 0 is connected to the SNT connection points 3 and 4 in TSM 12.

3.4 Example 4
NTCOI:SNTP=TSM-1-0,SNT=SNTETET8-2&&-4,SNTV=2; The SNTs of type SNTETET8, variant 2, with individuals 2, 3, and 4 are connected in consecutive order to the SNT connection points 0,1 and 2 in TSM 1.

3.5 Example 5
NTCOI:SNTP=TSM-8-13,SNT=SNTETET8-2&&-6,SNTV=2; The SNTs of type SNTETET8, variant 2, with individuals 2,3 and 4 are connected in consecutive order to the SNT connection points 13,14 and 15 in TSM 8. Since connection position 15 is the last position in TSM 8, the sequence continues in TSM 9. Therefore individuals 5 and 6 are connected to connection points 0 and 1 in TSM 9.

3.6 Example 6
NTCOI:SNT=ET155-2,SNTP=TSM-1-0,SNTV=1,EQLEV=1,PROT=1; The SNT ET155, individual 2 of variant 1 is connected to the TSM 1. The EQLEV parameter indicates that one SUBSNT is connected to the switch. Also that the SNT has equipment protection is defined.

3.7 Example 7
NTCOI:SNT=ET155-3,SNTP=TSM-1-0,SNTV=1,EQLEV=3,PROT=3; The SNT ET155, individual 3 of variant 1, is connected in consecutive order to the TSM 1, 2 and 3. The EQLEV parameter indicates that three subordinate SNTs are connected to the switch. Also that the SNT has equipment protection is defined.

3.8 Example 8
NTCOI:SNT=MBTRCS-0,SNTP=TSM-0-0&TSM-1-0,SNTV=1; The SNT MBTRCS, individual 0 of variant 1, is connected to TSM 0 and TSM 1 at the same connection point of both TSMs (0 in this example).

3.9 Example 9
NTCOI:SNT=VET-2, EXTP=32-4-8-5, SNTV=0; The VET SNT, individual 2 of variant 0 is connected to an external hardware connection point which is positioned in subrack 32 in slot 4 on subport 5 of port 8.

3.10 Example 10

NTCOI:SNTP=MUX3-8-4,SNT=SNTETET8-2&&-6,SNTV=2,IDLEP=1; The SNTs of type SNTETET8, variant 2, with individuals 2 to 6, are connected in consecutive order to the access points 4,5,6,7 and 8 in MUX3 8.

3.11 Example 11
NTCOI:SNT=ET155-2,SNTP=XM-1-2-8,SNTV=1,MODE=128,PROT=1; The SNT ET155, individual 2 of variant 1 is connected to the XM in row 1 and column 2. The number of MUPs to be allocated by the GS for this SNT is specified in parameter MODE. Also equipment protection for the SNT is defined.

3.12 Example 12
NTCOI:EXTP="28-2-5-3",SNT=VET-1,MG=AXDWA,SNTV=0; The VET SNT, individual 1 of variant 0, is connected to an external hardware connection point of the MG AXDWA which is positioned in subrack 28 in slot 2 on subport 3 of port 5.

47. Khi to v test cc SNT:

1.1 Command
NTTEI:SNT=snt [,SUBSNT=subsnt];

1.2 Parameters
SNT=snt Switching Network Terminal (SNT) Expressed as snt-n where: snt SNT type Identifier 1 - 13 characters n SNT number Numeral 0 - 65535 The maximum value of the SNT number, is determined by the Size Alteration Event (SAE) in the SNT owning block (SAE 529). For alternative expressions, see the Application Information for block TRAN and the relevant SNT owning block. SUBSNT=subsnt Subordinate switching network terminal For value ranges, see the Application Information for the relevant

SNT owning block.

2 Function
This command initiates testing of a manually blocked SNT or a subordinate SNT. When an SNT with subordinate SNTs is specified in the command, only the specified subordinate SNTs are tested. Otherwise, the complete SNT is tested. Result printout SWITCHING NETWORK TERMINAL TEST RESULT is received. The order does not remain after system restart.

3 Examples
3.1 Example 1
NTTEI:SNT=SNTPCD32-9; SNT 9 of type PCD32 is tested.

3.2 Example 2
NTTEI:SNT=SNTETBT4-2; SNT 2 controlled by device block BT4 is tested.

3.3 Example 3
NTTEI:SNT=ET155-4,SUBSNT=3; Subordinate SNT 3 of ET155 SNT 4 is tested.

48. Deblock cc SNT:

1.1 Command
/ \ |snt... | NTBLE:SNT=+ +; |snt [,SUBSNT=subsnt...]| \ /

49. XM bi block:
1.2 Parameters

SNT=snt

Switching Network Terminal (SNT) Expressed as snt-n where: snt n

Switching network terminal type Identifier 1 - 13 characters Switching network terminal number Numeral 0 - 65535 The maximum value of the switching network terminal number, is determined by the Size Alteration Event (SAE) in the SNT owning block (SAE 529).

For alternative expressions, see the Application Information for block TRAN and the relevant SNT owning block. SUBSNT=subsnt Subordinate switching network terminal For value ranges, see the Application Information for the relevant SNT owning block.

2 Function
This command deblocks an SNT or a subordinate SNT. When an SNT with subordinate SNTs is specified in the command, only the specified subordinate SNTs are deblocked. Otherwise, the complete SNT is deblocked. A maximum of 128 SNTs or 1 SNT with SUBSNTs or specified SUBSNTs, can be specified in one command issue. The supervision is activated for the entire deblocked SNT, or for the deblocked subordinate SNT. Result printout SWITCHING NETWORK TERMINAL DEBLOCKING RESULT is received. The order remains after system restart.

3 Examples
3.1 Example 1
NTBLE:SNT=SNTETBT3-18&&-21; SNT of type SNTETBT3 with individuals 18, 19, 20, and 21 are manually deblocked.

3.2 Example 2
NTBLE:SNT=ET6-27&&-29;

SNT of type ET6 with individuals 27, 28, and 29 are manually deblocked.

3.3 Example 3
NTBLE:SNT=ET155-0,SUBSNT=0&&3; Subordinate SNT 0, 1, 2, and 3 of ET155 SNT 0 are manually deblocked.

3.4 Example 4
NTBLE:SNT=ET155-0&&-2; SNT of type ET155 with individuals 0, 1, and 2 are manually deblocked.

3.5 Example 5
NTBLE:SNT=ET155-10,SUBSNT=1&5; Subordinate SNT 1 and 5 of ET155 SNT 10 are manually deblocked.

1.1 Command
/ / / \ | |UNIT=unit...|,DETAIL| GDSTP|:+ \ / | |TYPE=type \ \ \ | + | / \ | |; | /

1.2 Parameters
DETAIL TYPE=type UNIT=unit Detailed printout Type of Distributed Group Switch unit to be printed Distributed Group Switch unit identifier Expressed as clm-n, mux-p-n, or xm-p-r-c where: c clm mux n p r xm A B

Individual column number Clock module name Multiplexer unit name Unit number Plane identifier Individual row number Switch matrix unit name Plane A

Plane B Note: See Application Information for block GIOH and each unit specific AI.

2 Function
This command prints the state of Distributed Group Switch units. The command accepts the specification of a single unit, multiple units of varying types, all units of a particular type, or all units in the Distributed Group Switch. If parameter TYPE is specified, the state of all the Distributed Group Switch units of the type specified in the command are printed. Repetition is allowed for all unit types. For switch matrix units, repetition is only allowed on the column identifier. When a range of units is specified and if no units are connected to the Distributed Group Switch in the given range then NONE is printed. Otherwise, only the state of the units that are connected are printed. If parameter DETAIL is specified, the states of the whole chain of downstream Distributed Group Switch units connected to the units specified in the command are printed. It is not allowed to specify a Clock unit together with parameter DETAIL. The answer printout DISTRIBUTED GROUP SWITCH STATE is received. The order does not remain after system restart.

1.1 Command
GDBLI:UNIT=unit;

1.2 Parameters
UNIT=unit Distributed Group Switch unit Expressed as clm-n, mux-p-n, or xm-p-r-c where: c clm mux n p A Individual column number Clock Module (CLM) name Multiplexer unit name Unit number Plane identifier Plane A

B r xm

Plane B Individual row number Switch Matrix (XM) unit name

See Application Information for block GIOH and each unit specific AI (CLM, MUX3, MUX34, MUXSP , MUXTS, XM).

1.3 Dialogue Parameters

NO; YES; Manual blocking of the specified CLM is not to take place. Manual blocking of the specified CLM unit is to take place.

2 Function
This command initiates blocking of a unit in the Distributed Group Switch, provided the blocking will not result in traffic restrictions. Result printout DISTRIBUTED GROUP SWITCH UNIT BLOCKING RESULT is received. Manual blocking of automatically blocked units is always permitted, but not in units which are not connected. Manual blocking of a CLM means considerable risk for the exchange as there are only two CLMs in the Distributed Group Switch. For this reason unnecessary blocking must be avoided. In the case of an unnecessary blocking attempt on a CLM, the dialogue procedure starts and answer printout WARNING, ACCEPTANCE MEANS CONSIDERABLE RISK FOR THE WHOLE EXCHANGE, ANSWER WITH YES IF YOU WANT TO CONTINUE will be received. Indicate with YES if the blocking is to be executed. Indicate with NO if the blocking is not to be executed, and the printout BLOCKING ORDER CANCELLED will be received. An observation alarm DISTRIBUTED GROUP SWITCH UNIT MANUALLY BLOCKED indicating that the unit is now blocked is added in the alarm list. If the alarm DISTRIBUTED GROUP SWITCH FAULT is present for the unit being manually blocked, then the fault alarm is ceased. This command cannot be given immediately after an initial start or if the switch type is not initiated. The order remains after system restart.

1.1 Command
GDBLE:UNIT=unit;

1.2 Parameters
UNIT=unit Distributed Group Switch unit identifier

Expressed as clm-n, mux-p-n or xm-p-r-c where: c clm mux n p A B r xm Individual column number Clock Module (CLM) name Multiplexer unit name Unit number Plane identifier Plane A Plane B Individual row number Switch Matrix (XM) unit name See Application Information for block GIOH and each unit specific AI (CLM, MUX3, MUX34, MUXSP , MUXTS, XM).

2 Function
This command ends the blocking of a unit in the Distributed Group Switch. Result printout DISTRIBUTED GROUP SWITCH UNIT DEBLOCKING RESULT is received. An observation alarm DISTRIBUTED GROUP SWITCH UNIT MANUALLY BLOCKED indicating that the unit was blocked is no longer in the alarm list. This command cannot be given immediately after an initial start or if the switch type is not initiated. The order remains after system restart.

3 Examples
3.1 Example 1
GDBLE:UNIT=CLM-1; This command ends the blocking of CLM unit 1.

3.2 Example 2
GDBLE:UNIT=MUX3-B-2;

This command ends the blocking of the Digital Link version 3 Multiplexer (MUX3) in plane B, unit 2.

3.3 Example 3
GDBLE:UNIT=MUX34-A-3; This command ends the blocking of the Digital Link adaptable from version 3 to 4 Multiplexer (MUX34) in plane A, unit 3.

3.4 Example 4
GDBLE:UNIT=MUXSP-B-1; This command ends the blocking of the Multiplexer based on Space Switch Module (MUXSP) in plane B, unit 1.

3.5 Example 5
GDBLE:UNIT=MUXTS-A-2; This command ends the blocking of the Multiplexer based on Time Switch Module (MUXTS) in plane A, unit 2.

3.6 Example 6
GDBLE:UNIT=XM-B-1-4; This command ends the blocking of XM in plane B, row 1, column 4.

50. Xem RP/EM:

1.1 Command
/ \ |DEV=dev... | | | | / \ | RADRP:+ |dety...| +; |DETY=+ +[,PPS]| | |ALL | | | \ / | \ /

1.2 Parameters
DETY=dety DEV=dev PPS Device type ALL All device types Device Pre-Post Service If this parameter is given, then data is printed only for devices in Pre-Post Service State. If the parameter is omitted, then data is printed only for devices not in Pre-Post Service State.

2 Function
The command orders a printout of device RP/EM data. The printout DEVICE RP/EM DATA IN BSC is received for specified devices, all devices of a device type, or all devices. If the parameter PPS is specified in the command, then only devices which are in Pre-Post Service State will be included on the printout. If the parameter PPS is omitted, when only devices which are not in Pre-Post Service State will be included on the printout. Up to sixteen (16) such commands may be given simultaneously. All DEVICE RP/EM DATA IN BSC printouts are interrupted and terminated on commencement of an EXCHANGE DATA command, to prevent the possibility of out-of-date printouts being obtained. The order does not remain after system restart.

50. Lnh pint v tng sae:

1.1 Command / \ / / \\ |sae| | |block|| SAAEP:SAE=+ + |,BLOCK= + |ALL| | |ALL || \ / \ \ //

+|;

1.2 Parameters
BLOCK=block Block name Identifier 1 - 7 characters ALL SAE=sae All loaded blocks Size Alteration Event Numeral 0 - 8192 The maximum value is defined in the Operating System Area as highest usable SAE number. ALL All defined SAEs

2 Function
This command is used to print file size information of Size Alteration Events (SAEs) defined in the system. The parameter SAE specifies the Size Alteration Event number. The SAE type can be local or global. The table indicates the number range for local and global SAEs:

Table 1

SAE Type GLOBAL LOCAL GLOBAL

SAE number range 0 - 499 500 - 899 900 - highest usable SAE number defined in the Operating System Area If the SAE number specified in parameter SAE is of type LOCAL, the parameter BLOCK must also be specified. If value ALL is specified for parameter BLOCK then file size information of the specified LOCAL SAE in all participating blocks are printed. If the SAE number specified in parameter SAE is of type GLOBAL, the parameter BLOCK must not be specified. If parameter value ALL is specified for parameter SAE then file size information of all SAEs defined in the system are printed. If a block name is specified together with ALL for parameter SAE, then all SAEs defined in the specified block are printed. The function uses the SAE database tables where all SAEs that are defined in the system are stored. If the SAE database tables are not complete, the function allows file size information of one SAE to be printed. The order does not remain after system restart.

3 Examples
3.1 Example 1
SAAEP:SAE=4; This command prints file size information of of Global SAE 4.

3.2 Example 2
SAAEP:BLOCK=RE,SAE=513; This command prints file size information of Local SAE 513 participated by block RE.

3.3 Example 3
SAAEP:BLOCK=RE,SAE=ALL; This command prints file size information of all SAEs participated by block RE.

3.4 Example 4
SAAEP:SAE=500,BLOCK=ALL; This command prints file size information of Local SAE 500 in all participating blocks.

3.5 Example 5
SAAEP:SAE=ALL;

3 Examples
3.1 Example 1
RADRP:DEV=RXTRA-1; Printout device RP/EM data for device RXTRA-1.

3.2 Example 2
RADRP:DEV=RXTRA-33&&-47; Printout device RP/EM data for devices RXTRA-33 to RXTRA-47 inclusive.

3.3 Example 3
RADRP:DETY=RXTRA,PPS; Printout device RP/EM data for all RXTRA-devices in Pre-Post Service State.

3.4 Example 4
RADRP:DETY=ALL; Printout device RP/EM data for all devices not in

Pre-Post Service State. Li:

FAULT CODE 6 INVALID DEVICE TYPE SPECIFIED details Command not permitted for this device type. FAULT CODE 7 DEVICE TYPE DOES NOT HAVE PPS FUNCTION details Device type does not have the Pre-Post Service state function associated with it. FAULT CODE 18 NO DEVICE DATA AVAILABLE FOR OUTPUT details No device data available for output. FAULT CODE 29 DATA CHANGE IN PROGRESS Command not allowed, data change command in progress.

51. Tng SAE t ng:

1.1 Command

SAALI;

1.2 Parameters
-

2 Function
Command SAALI orders the execution of the Size Alteration Events in the Size Alteration Action List. The command is terminated if the Automatic Size Alteration State is set Passive. The order remains after system restart.

3 Examples
3.1 Example 1
SAALI; The Size Alteration Events in the Size Alteration Action List are executed.

52. Khai BPCs:

1.1 Command
/ RLBDC:CELL=cell[,CHGR=chgr]+[,NUMREQBPC=numreqbpc] \ [,NUMREQEGPRSBPC=numreqegprsbpc] [,NUMREQCS3CS4BPC=numreqcs3cs4bpc] \ [,TN7BCCH=tn7bcch]+; /

1.2 Parameters
CELL=cell Cell designation This is a symbolic name of a defined cell. CHGR=chgr NUMREQBPC=numreqbpc Channel group number Numeral 0 - 15 Number of required BPCs This parameter indicates the number of required Basic Physical Channels (BPCs) in a channel group. The parameter value must be specified as a multiple of 8.

Numeral 8 - 128 SYSDEF System defined limit Number of BPCs is defined by the number of frequencies in the channel group. NUMREQCS3CS4BPC=numreqcs3cs4bpc Number of required GPRS CS-3 or CS-4 BPCs This parameter indicates the number of required BPCs in a channel group that can support General Packet Radio Service (GPRS) CS-3 or CS-4. Numeral 0 - 128 NUMREQEGPRSBPC=numreqegprsbpc Number of required EGPRS BPCs This parameter indicates the number of required BPCs in a channel group that can support Enhanced General Packet Radio Service (EGPRS). Numeral 0 - 128 TN7BCCH=tn7bcch TN7 on BCCH frequency This parameter indicates if Timeslot Number (TN) 7 on the Broadcast Control Channel (BCCH) frequency can be configured with Traffic Channels (TCHs) supporting EGPRS or GPRS only. EGPRS GPRS

TN7 on the BCCH frequency can be configured with TCHs supporting EGPRS. TN7 on the BCCH frequency can be configured with TCHs supporting GPRS only.

2 Function
This command defines the number of required BPCs, and how many of the required BPCs that can support EGPRS or GPRS CS-3 or CS-4. It also defines if TN7 on the BCCH frequency can be configured with TCHs supporting EGPRS or GPRS only. The number of TCHs for a channel group can be calculated by subtracting the BPCs used for control channels from the number of required BPCs. If the number of required BPCs is set to system defined, the number of required BPCs is equivalent to the number of defined frequencies times eight. An extended range cell only configures half of the BPCs. There must be at least one frequency defined per eight number of required BPCs.

It is not allowed to set the number of required BPCs so that the Stand-alone Dedicated Control Channels (SDCCH/8s) set in command RLCCC cannot be configured. The number of SDCCH/8s and the number of required BPCs that can support EGPRS or GPRS CS-3 or CS-4 cannot exceed the number of required BPCs in the channel group. The parameter TN7BCCH is only valid for channel group 0. If channel groups have been defined for the cell using command RLDGI, then the CHGR parameter is mandatory. The command is not valid for external cells, that is, cells belonging to another Base Station Controller (BSC). The order remains after system restart.

3 Examples
3.1 Example 1
RLBDC:CELL=HLM1,NUMREQBPC=8; The required number of BPCs for the cell HLM1 is set to 8.

3.2 Example 2
RLBDC:CELL=HLM1,CHGR=1,NUMREQBPC=16; The required number of BPCs in channel group 1 in cell HLM1 is set to 16.

3.3 Example 3
RLBDC:CELL=HLM1,CHGR=1,NUMREQBPC=SYSDEF; The required number of BPCs in channel group 1 in cell HLM1 is set to the number of BPCs defined by the number of frequencies in the channel group.

3.4 Example 4
RLBDC:CELL=HLM1,CHGR=1,NUMREQBPC=16,NUMREQCS3CS4BPC=4; The required number of BPCs in channel group 1 in cell HLM1 is set to 16. The required number of BPCs that support GPRS CS-3 or CS-4 in channel group 1 in cell HLM1 is set to 4.

3.5 Example 5
RLBDC:CELL=HLM1,CHGR=0,NUMREQBPC=16,NUMREQEGPRSBPC=4, TN7BCCH=EGPRS; The required number of BPCs in channel group 0 in cell HLM1 is set to 16. The required number of BPCs that support EGPRS in channel group 0 in cell HLM1 is set to 4. TN7 on the BCCH frequency can be configured with TCHs supporting EGPRS.

53. Lnh dng Tng BPCs:

RLBDC:CELL=cell[,CHGR=chgr]+[,NUMREQBPC=numreqbpc] \ [,NUMREQEGPRSBPC=numreqegprsbpc] [,NUMREQCS3CS4BPC=numreqcs3cs4bpc] \ [,TN7BCCH=tn7bcch]+; /

1.2 Parameters
CELL=cell Cell designation This is a symbolic name of a defined cell. CHGR=chgr NUMREQBPC=numreqbpc Channel group number Numeral 0 - 15 Number of required BPCs This parameter indicates the number of required Basic Physical Channels (BPCs) in a channel group. The parameter value must be specified as a multiple of 8. Numeral 8 - 128 SYSDEF System defined limit Number of BPCs is defined by the number of frequencies in the channel group. NUMREQCS3CS4BPC=numreqcs3cs4bpc Number of required GPRS CS-3 or CS-4 BPCs This parameter indicates the number of required BPCs in a channel group that can support General Packet Radio Service (GPRS) CS-3 or CS-4. Numeral 0 - 128 NUMREQEGPRSBPC=numreqegprsbpc Number of required EGPRS BPCs This parameter indicates the number of required BPCs in a channel group that can support Enhanced General Packet Radio Service (EGPRS). Numeral 0 - 128 TN7BCCH=tn7bcch TN7 on BCCH frequency This parameter indicates if Timeslot Number (TN) 7 on the Broadcast Control Channel (BCCH) frequency can be configured with Traffic Channels (TCHs) supporting EGPRS or

GPRS only. EGPRS TN7 on the BCCH frequency can be configured with TCHs supporting EGPRS. GPRS TN7 on the BCCH frequency can be configured with TCHs supporting GPRS only.

2 Function
This command defines the number of required BPCs, and how many of the required BPCs that can support EGPRS or GPRS CS-3 or CS-4. It also defines if TN7 on the BCCH frequency can be configured with TCHs supporting EGPRS or GPRS only. The number of TCHs for a channel group can be calculated by subtracting the BPCs used for control channels from the number of required BPCs. If the number of required BPCs is set to system defined, the number of required BPCs is equivalent to the number of defined frequencies times eight. An extended range cell only configures half of the BPCs.There must be at least one frequency defined per eight number of required BPCs.It is not allowed to set the number of required BPCs so that the Stand-alone Dedicated Control Channels (SDCCH/8s) set in command RLCCC cannot be configured.The number of SDCCH/8s and the number of required BPCs that can support EGPRS or GPRS CS-3 or CS-4 cannot exceed the number of required BPCs in the channel group. The parameter TN7BCCH is only valid for channel group 0. If channel groups have been defined for the cell using command RLDGI, then the CHGR parameter is mandatory. The command is not valid for external cells, that is, cells belonging to another Base Station Controller (BSC). The order remains after system restart.

3 Examples
3.1 Example 1
RLBDC:CELL=HLM1,NUMREQBPC=8; The required number of BPCs for the cell HLM1 is set to 8.

3.2 Example 2
RLBDC:CELL=HLM1,CHGR=1,NUMREQBPC=16; The required number of BPCs in channel group 1 in cell HLM1 is set to 16.

3.3 Example 3
RLBDC:CELL=HLM1,CHGR=1,NUMREQBPC=SYSDEF; The required number of BPCs in channel group 1 in cell HLM1 is set to the number of BPCs defined by the number of frequencies in the channel group.

3.4 Example 4
RLBDC:CELL=HLM1,CHGR=1,NUMREQBPC=16,NUMREQCS3CS4BPC=4; The required number of BPCs in channel group 1 in cell HLM1 is set to 16. The required number of BPCs that support GPRS CS-3 or CS-4 in channel group 1 in cell HLM1 is set to 4.

3.5 Example 5
RLBDC:CELL=HLM1,CHGR=0,NUMREQBPC=16,NUMREQEGPRSBPC=4, TN7BCCH=EGPRS; The required number of BPCs in channel group 0 in cell HLM1 is set to 16. The required number of BPCs that support EGPRS in channel group 0 in cell HLM1 is set to 4. TN7 on the BCCH frequency can be configured with TCHs supporting EGPRS.

54. Li ABIS PATH UNAVAIL:

117.
Note: In this result an ABIS PATH UNAVAIL(khong san co, khong co gia tri) fault may be received, this fault is also covered(che boi) by this OPI

Alarm ceasing printout: RADIO X-CEIVER ADMINISTRATION MANAGED OBJECTS IN TRANSCEIVER GROUP MANUALLY BLOCKED

1.1 Command
RXAPI:MO=mo,DEV=dev...,DCP=dcp...[,RES64K];

1.2 Parameters
DCP=dcp Digital connection point number used as termination point in the Base Transceiver Station (BTS) for the Abis path Numeral 0 - 511 DEV=dev Transmission device used for the Abis path See Application Information for block TRAN for the format and value range of this parameter. MO=mo Managed object instance See Application Information for block RXCTA for the format and value range of this parameter. The Managed Object (MO) must be of class Transceiver Group (TG). RES64K A 64 kbit/s Abis path will be reserved for use by a suitably configured Time Slot (TS) only.

2 Function
This command is used to define one or more Abis paths between the Base Station Controller (BSC) and the Base Transceiver Station (BTS). Up to 124 Abis paths may be defined per TG. All Abis paths within a TG must be connected to devices of the same transmission type. See Application Information for block RBLT for valid transmission types.

Warning!
The setup of the transmission type must be considered when defining Abis paths as they may already be used by the transmission system for control purposes.

The first specified DEV argument is connected to the first specified DCP argument and the second specified DEV argument is connected to the second specified DCP argument, etc. The answer printout RADIO X-CEIVER ADMINISTRATION ABIS PATH RESULT will show the results of the Abis path definition request. The order remains after system restart.

3 Examples
3.1 Example 1
RXAPI:MO=RXOTG-1,DEV=RBLT-1,DCP=1; An Abis path is defined in BTS logical model G12 between the transmission device RBLT 1 and DCP 1 within TG 1.

3.2 Example 2
RXAPI:MO=RXOTG-3,DEV=RBLT-2&&-4,DCP=4&&6; Abis paths are defined in BTS logical model G12 between the transmission device RBLT 2 and DCP 4, the transmission device RBLT 3 and DCP 5 and between the transmission device RBLT 4 and DCP 6 within TG 3.

3.3 Example 3
RXAPI:MO=RXOTG-1,DEV=RBLT-1&&-31,DCP=1&&31; Abis paths are defined in BTS logical model G12 between the transmission device RBLT 1 to RBLT 31 and DCP 1 to DCP 31 within TG 1. This means one 2 Mbit PCM system (or 1.5 Mbit PCM system in the USA) is connected.

3.4 Example 4
RXAPI:MO=RXOTG-1,DEV=RBLT-1&&-31&RBLT-33&&-63,DCP=1&&31&33&&63; Abis paths are defined in BTS logical model G12 between the transmission device RBLT 1 to RBLT 31 and DCP 1 to DCP 31, RBLT 33 to RBLT 63 and DCP 33 to DCP 63 within TG 1. This means two 2 Mbit PCM systems (or 1.5 Mbit systems in the USA) are connected.

3.5 Example 5
RXAPI:MO=RXOTG-1,DEV=RBLT24-0&&-23,DCP=1&&24; Abis paths are defined in BTS logical model G12 between the transmission device RBLT24 0 to RBLT24 23 and DCP 1 to DCP 24 within TG 1. This means one 2 Mbit PCM system (or 1.5 Mbit PCM system in the USA) is connected.

3.6 Example 6
RXAPI:MO=RXOTG-1,DEV=RBLT24-0&&-47,DCP=1&&24&33&&56; Abis paths are defined in BTS logical model G12 between the transmission device RBLT24 0 to RBLT24 23 and DCP 1 to DCP 24, RBLT24 24 to RBLT24 47 and DCP 33 to DCP 56 within TG 1. This means two 2 Mbit PCM systems (or 1.5 Mbit PCM systems in the USA) are connected.

3.7 Example 7
RXAPI:MO=RXOTG-1,DEV=RBLT15-1&&-31,DCP=1&&31; Abis paths are defined in BTS logical model G12 between the transmission device RBLT15 1 to RBLT15 31 and DCP 1 to DCP 31 within TG 1. This means one 2 Mbit PCM system (or 1.5 Mbit system in the USA) is connected.

3.8 Example 8
RXAPI:MO=RXOTG-1,DEV=RBLT-1&&-31,DCP=1&&31,RES64K; 64 kbit/s Abis paths are defined in BTS logical model G12 between the transmission device RBLT 1 to RBLT 31 and DCP 1 to DCP 31 within TG 1 and are reserved for use only by TSs configured to use such paths. This means one 2 Mbit PCM system (or 1.5 Mbit system in the USA) is connected.

55. LAPD:

4.1 LAPD Concentration

Figure 1

LAPD Concentration

A LAPD concentrator receives messages to several TRXs on one concentrated LAPD link connected to the BSC. The LAPD concentrator distributes the messages to the indicated TRXs via their respective dedicated non concentrated LAPD links. A LAPD concentrator also receives messages from several TRXs and transfers them to the BSC on the concentrated LAPD link.

4.2 Choise of TEI values

The TEI valus for TRXs must be unique within a LAPD Concentrator. Within one TG the TEIs are predefined to have unique values. When concentrating LAPD links belonging to TRXs in different TGs, it may be neccessary to change the TEI values of the TRXs to get unique TEI values in the LAPD concentrator. This change must be done at the site.

5 Glossary
CNC Equipment type connected to a concentrator board

CONCB CTSLOT EM LAPD NCTSLOT RILT TEI TG TRX

LAPD concentrator board Concentrated timeslot Extension Module Link Access Ptotocol for D-channel Non-concentrated timeslot Radio Interface Line Terminal Terminal Endpoint Identifier Transceiver Group Transceiver

56. Li:
A, Li 1a:17- lin quan n IDB, Ylink.(cn thay i post Ylink) B, Li 1b:4- Lin quan n anten, t s VSRW.(c th khc phc angten, i feeder ca cell ). - Hin tng TRX OML fault do mt lung hoc ngun cung cp khng .

57. Lnh lin quan n BPCs:

1.1 Command
/ RLBDC:CELL=cell[,CHGR=chgr]+[,NUMREQBPC=numreqbpc] \ [,NUMREQEGPRSBPC=numreqegprsbpc] [,NUMREQCS3CS4BPC=numreqcs3cs4bpc] \ [,TN7BCCH=tn7bcch]+; /

1.2 Parameters
CELL=cell Cell designation This is a symbolic name of a defined cell. CHGR=chgr NUMREQBPC=numreqbpc Channel group number Numeral 0 - 15 Number of required BPCs This parameter indicates the number of required Basic Physical Channels (BPCs) in a channel group. The parameter value must be specified as a multiple of 8. Numeral 8 - 128 SYSDEF

System defined limit Number of BPCs is defined by the number of frequencies in the channel group.

NUMREQCS3CS4BPC=numreqcs3cs4bpc Number of required GPRS CS-3 or CS-4 BPCs This parameter indicates the number of required BPCs in a channel group that can support General Packet Radio Service (GPRS) CS-3 or CS-4. Numeral 0 - 128 NUMREQEGPRSBPC=numreqegprsbpc Number of required EGPRS BPCs This parameter indicates the number of required BPCs in a channel group that can support Enhanced General Packet Radio Service (EGPRS). Numeral 0 - 128 TN7BCCH=tn7bcch TN7 on BCCH frequency This parameter indicates if Timeslot Number (TN) 7 on the Broadcast Control Channel (BCCH) frequency can be configured with Traffic Channels (TCHs) supporting EGPRS or GPRS only. EGPRS GPRS

TN7 on the BCCH frequency can be configured with TCHs supporting EGPRS. TN7 on the BCCH frequency can be configured with TCHs supporting GPRS only.

2 Function
This command defines the number of required BPCs, and how many of the required BPCs that can support EGPRS or GPRS CS-3 or CS-4. It also defines if TN7 on the BCCH frequency can be configured with TCHs supporting EGPRS or GPRS only. The number of TCHs for a channel group can be calculated by subtracting the BPCs used for control channels from the number of required BPCs. If the number of required BPCs is set to system defined, the number of required BPCs is equivalent to the number of defined frequencies times eight. An extended range cell only configures half of the BPCs. There must be at least one frequency defined per eight number of required BPCs. It is not allowed to set the number of required BPCs so that the Stand-alone Dedicated Control Channels (SDCCH/8s) set in command RLCCC cannot be configured. The number of SDCCH/8s and the number of required BPCs that can support EGPRS or GPRS CS-3 or CS-4 cannot exceed the number of required BPCs in the channel group.

The parameter TN7BCCH is only valid for channel group 0. If channel groups have been defined for the cell using command RLDGI, then the CHGR parameter is mandatory. The command is not valid for external cells, that is, cells belonging to another Base Station Controller (BSC). The order remains after system restart.

3 Examples
3.1 Example 1
RLBDC:CELL=HLM1,NUMREQBPC=8; The required number of BPCs for the cell HLM1 is set to 8.

3.2 Example 2
RLBDC:CELL=HLM1,CHGR=1,NUMREQBPC=16; The required number of BPCs in channel group 1 in cell HLM1 is set to 16.

3.3 Example 3
RLBDC:CELL=HLM1,CHGR=1,NUMREQBPC=SYSDEF; The required number of BPCs in channel group 1 in cell HLM1 is set to the number of BPCs defined by the number of frequencies in the channel group.

3.4 Example 4
RLBDC:CELL=HLM1,CHGR=1,NUMREQBPC=16,NUMREQCS3CS4BPC=4; The required number of BPCs in channel group 1 in cell HLM1 is set to 16. The required number of BPCs that support GPRS CS-3 or CS-4 in channel group 1 in cell HLM1 is set to 4.

3.5 Example 5
RLBDC:CELL=HLM1,CHGR=0,NUMREQBPC=16,NUMREQEGPRSBPC=4, TN7BCCH=EGPRS; The required number of BPCs in channel group 0 in cell HLM1 is set to 16. The required number of BPCs that support EGPRS in channel group 0 in cell HLM1 is set to 4. TN7 on the BCCH frequency can be configured with TCHs supporting EGPRS.

58. Cc t vit tt
1.2 Parameters
arfcn Absolute Radio Frequency Channel Number (ARFCN)

It represents the frequency to which a Receiver (RX) or Transmitter (TX) is tuned, or the frequency associated with a timeslot handler. HOP Frequency hopping For a TX, HOP is printed when synthesised frequency hopping. bpc Basic Physical Channel (BPC) individual bspwr Base Transceiver Station (BTS) nominal power, expressed in dBm c0f Carrier zero filling YES Carrier zero filling is turned on. NO Carrier zero filling is turned off. chcomb Channel combination BCCH BCCH + CCCH SDCCH8 SDCCH/8 * 8 SDCCH4 BCCH + CCCH + SDCCH/ 4 * 4 CBCH8 SDCCH/8 * 7 + CBCH CBCH4 BCCH + CCCH + SDCCH/ 4 * 3 + CBCH TCH TCH icm Idle channel measurement ON Idle channel measurement performed OFF Idle channel measurement not performed mismatch BTS capability mismatch specific reason for configuration selection failure BAND Frequency band/system type The frequency band/system type of the Managed Object (MO) does not match the required frequency band/system type. BTSPWR BTS power The value is within minimum and maximum power limits of the TX, but a value not allowed by the BTS. BTSXRANGE Extended range The function is not supported by the Timeslot (TS). CELL Cell dedication The dedicated cell individual of the MO does not match the required cell individual. CHGR Channel group dedication The dedicated channel group of the MO does not match the required channel group. MAXBTSPWR Maximum BTS power The nominal power of a TX exceeds the maximum power of the BTS.

mo

MINBTSPWR Minimum BTS power The nominal power of the TX is less than the minimum power of the BTS. NONE No mismatch NPWR Nominal power The nominal power of a TX cannot satisfy that required by the cell. RXDIV RX Diversity The diversity capability of the RX does not match the required capability. Managed Object Instance (MOI) See Application Information for block RXCTA for parameter format. modp morx mots motx MO of class Digital Path (DP) MO of class RX MO of class TS MO of class TX

n1 n3 n4 offs

Severely errored second estimator Errored second and severely errored second estimator Severely errored second estimator Frame number offset The time difference from the Timing Function (TF) acting as master in another Transceiver Group (TG), expressed as a number of Time Division Multiple Access (TDMA) frames. Configuration data printout result BLOCKED The MO is not in global state OPER and is therefore not available to the configuration function. BPCFAIL An attempt to create a BPC individual has failed. CONFIG The MO is configured with the indicated parameters. FAILED An attempt to configure this MO was not successful. N/A The MO is not of class RX, TG, TS, TX, or DP. Therefore configuration data is not appropriate. SELECT The MO is selected for use but not yet configured. For an MO of class TS a speech/data path may not yet be setup. UNDEF The MO is not defined. UNUSED The MO is not configured, no other parameters are printed for this MO. Spare bits It sets the transmitted spare bits (Sa4-Sa8) in Pulse Code Modulation

result

sbits

(PCM) time slot 0. The TS is a binary number according to the following format: Sa8 Sa7 Sa6 Sa5 Sa4. tn Time slot number txad TX logical address associated with a TX or a timeslot handler HOP Baseband frequency hopping xra Extended range YES The time slot handler is an extended range time slot handler. It can support traffic at a distance of greater than 35 km between the mobile station and the base station. NO The time slot handler is not an extended range time slot handler. EOT DURING PRINTOUT The operator has cancelled the printout. NONE No data existed to be printed. AHOP NOT SUPPORTED BY TG Antenna Hopping (AHOP) is switched on, but the feature is not supported by the BTS. CONFIGURATION DATA MAY BE INCONSISTENT A request to the TG for configuration status indicated that the configuration may have been changed. The data printed may be inconsistent. CONFIGURATION IS SUSPENDED A request to the TG for configuration status indicated that configuration is currently suspended. The data printed may be inconsistent. FLEXIBLE ABIS ALLOCATION NOT SUPPORTED BY TG Flexible Abis Allocation is switched on, but the feature is not supported by the BTS. INCONSISTENT TRANSCODER CONNECTION TYPE The transcoder connection type for the TG is not consistent with the cell requirements. INSUFFICIENT CS3CS4 CAPABLE EQUIPMENT Insufficient MOs of class Transceiver Controller (TRXC) or Interface Switch (IS), with suitable General Packet Radio Service (GPRS) Coding Scheme (CS) 3 or CS 4 capabilities are available within this TG to meet the cell requirements. INSUFFICIENT EGPRS CAPABLE EQUIPMENT Insufficient MOs of class TRXC or IS, with suitable Enhanced GPRS (EGPRS) capabilities are available within this TG to meet the cell requirements. INSUFFICIENT TRX EQUIPMENT Insufficient MOs of class RX or TS, with suitable capabilities are available within this TG to meet the cell requirement. INSUFFICIENT TX EQUIPMENT Insufficient MOs of class TX, with suitable capabilities were available within this TG to meet the cell requirement at the time of configuration. If more TX equipment has become available since configuration was started the cell must be halted and activated to include these TXs in the configuration. IRC NOT SUPPORTED BY TG Interference Rejection Combining (IRC) is switched on, but the feature is not supported by the BTS. MAIO AUTOMATIC ALLOCATION PERFORMED

The Mobile Allocation Index Offset (MAIO) list did not contain all valid MAIOs so the missing ones were added to the end of the list randomly. MAIO EXCEEDS FREQUENCY SET SIZE The TG has invalid MAIOs, that is, MAIOs that exceed the number of frequencies in the hopping frequency set. TF NOT SYNCHRONISED The MOs within this TG are not currently used to support the cell because the TF is not synchronised FAULT INTERRUPT fault type A fault interruption occurred during printing. Fault type: FORMAT ERROR The command was incorrectly specified. UNREASONABLE VALUE details The parameter was specified with an unreasonable value. FAULT CODE 2 CANNOT MIX DIFFERENT BTS LOGICAL MODELS details The MO parameter specified MOIs from more than one BTS logical model. FAULT CODE 6 MO NOT IN VALID STATE details The MOI is not in an appropriate state. The TG must not be in state UNDEF.

2 Function
This printout is received as an answer printout to command RXCDP. It lists configuration data for MOs specified in command RXCDP. The configuration data indicates how MOs are configured to provide a number of BPCs, as well as the digital path configuration. When the contents of this printout indicate that frequency hopping is being supported, more detailed information may be obtained from the printout RADIO X-CEIVER ADMINISTRATION MANAGED OBJECT HOPPING DATA obtained using command RXHDP.

3 Action
This printout requires no action.

4 Printout Type
Answer printout

5 Printout Block
RXECOCRXOCOC

6 Glossary
AHOP ARFCN BPC BTS CS DP EGPRS GPRS IRC IS MAIO MO MOI PCM RX TDMA TF TG TRX TRXC TS TX Antenna Hopping Absolute Radio Frequency Channel Number Basic Physical Channel Base Transceiver Station Coding Scheme Digital Path (Managed object) Enhanced GPRS General Packet Radio Service Interference Rejection Combining Interface Switch (Managed object) The Mobile Allocation Index Offset Managed Object Managed Object Instance Pulse Code Modulation Receiver (Managed object) Time Division Multiple Access Timing Function (Managed object) Transceiver Group (Managed object) Transceiver Transceiver Controller (Managed object) Time Slot handler (Managed object) Transmitter (Managed object)

7 References
7.1 Command Descriptions
RXCDP Radio X-ceiver Administration, Managed Object Configuration Data, Print RXHDP Radio X-ceiver Administration, Managed Object Hopping Data, Print

7.2 Printout Descriptions

RADIO X-CEIVER ADMINISTRATION MANAGED OBJECT HOPPING DATA

7.3 Application Information

RXCTA

59. Khai bo cng sut:

1.1 Command
/ / \\ | |sctype|| RLCPC:CELL=cell|,SCTYPE=+ +| | |ALL || \ \ // / \ +[,MSTXPWR=mstxpwr][,BSPWRT=bspwrt][,BSPWRB=bspwrb]+;

1.2 Parameters
BSPWRB=bspwrb Base Station (BS) output power in dBm, for Broadcast Control Channel (BCCH) Radio Frequency (RF) channel number Numeral 0 - 63 The current Base Transceiver Station (BTS) version may have specific parameter restrictions. See "BTS parameter limitations" in OPERATION AND MAINTENANCE MANUAL for current BTS version. This parameter is not valid for external cell. BSPWRT=bspwrt BS output power in dBm, for non-BCCH RF channel numbers Numeral 0 - 63 The current BTS version may have specific parameter restrictions. See "BTS parameter limitations" in OPERATION AND MAINTENANCE MANUAL for current BTS version. This parameter is not valid for external cell. CELL=cell Cell designation.

This is a symbolic name of a defined cell. MSTXPWR=mstxpwr Maximum transmit power in dBm, for Mobile Station (MS) on connection Numeral 13 - 43 in steps of 2 (GSM 800) Numeral 13 - 43 in steps of 2 (GSM 900) Numeral 4 - 30 in steps of 2 (GSM 1800) Numeral 4 - 30 in steps of 2 (GSM 1900) SCTYPE=sctype Subcell type This parameter is not valid for external cells. UL OL ALL The subcell type is underlaid. The subcell type is overlaid. Both UL and OL.

2 Function
This command defines or changes configuration power data in a GSM cell or subcell. The command is not valid for external Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN) cells. If a subcell structure exists, then SCTYPE must be specified for parameters MSTXPWR and BSPWRT. If a subcell structure exists and parameter SCTYPE is given with ALL, then BSPWRB can also be included with MSTXPWR, BSPWRT, or both, in the command.

Parameters MSTXPWR and BSPWRT are the only command parameters valid for underlaid (UL) and overlaid (OL) subcell. If the cell is external, only parameter MSTXPWR may be specified with parameter CELL. The order remains after system restart.

3 Examples
3.1 Example 1
RLCPC:CELL=HLM1,BSPWRB=33,BSPWRT=35; This is an example of when a subcell structure does not exists. The BS output power for the BCCH RF channel number is changed to 33 dBm and the BS output power for the non-BCCH RF channel numbers is changed to 35 dBm. The configuration data is assigned to cell HLM1.

3.2 Example 2
RLCPC:CELL=HLM1,SCTYPE=OL,BSPWRT=38; This is an example of when a subcell structure exists. The BS output power for the non-BCCH RF channel numbers to the OL subcell in cell HLM1 is changed to 38 dBm.

3.3 Example 3
RLCPC:CELL=HLM3,SCTYPE=ALL,BSPWRT=33,MSTXPWR=25,BSPWRB=35; This is an example of when a subcell structure exists. The BS output power for the non-BCCH RF channel numbers is changed to 33 dBm, the maximum transmit power for the MS on connection is changed to 25 dBm in a GSM 800 cell or a GSM 900 cell. The BS output power for the BCCH RF channel number is changed to 35 dBm. The configuration data is assigned to both UL and OL subcell in cell HLM3.

3.4 Example 4
RLCPC:CELL=LIN4,MSTXPWR=26; This is an example for an external cell. The maximum transmit power for the MS on connection is changed to 26 dBm in a GSM 1800 or a GSM 1900 cell. The configuration data is assigned to cell LIN4, a cell belonging to another Base Station Controller (BSC).

60. xem route:

1.1 Printout:

strsp:r=all;
RSTAT rstat . . . rstat

DEVICE STATE SURVEY R NDV NOCC NIDL NBLO r ndv nocc nidl nblo . . . . . . . . . . . . . . . r ndv nocc nidl nblo [NONE] [EOT DURING PRINTOUT] / \ |FAULT INTERRUPT| |fault type | \ / END

1.2 Parameters
nblo ndv nidl nocc r rstat Number of blocked devices Number of devices Number of idle devices Number of occupied devices Route designation Route status BLOC RES1 RES2 NORES Blocked Reserved for priority calls Reserved for non-overflow traffic No restrictions

61. Lnh xem ti nguyn tng i:

SIZE ALTERATION OF DATA FILES INFORMATION 1 Format
1.1 Printout: saaep:sae=298;
SIZE ALTERATION OF DATA FILES INFORMATION SAE sae BLOCK [block] CNTRTYP NI cntrtyp [ni] NIU [niu] NIE [nie NIR nir]

/ | | |

/ \ |fault type| \ / . . . . . . . . . . . . . . . . . . . . .

\ | | |

| sae [block] cntrtyp [ni] [niu] | |/ \ ||fault type| |\ / | |[DBS DETECTED TRANSACTION ERROR] | | |[EOT DURING PRINTOUT] \ END

[nie

nir]

| | | | | | | | | |

1.2 Parameters
block cntrtyp Block name SAE Control Type CONS1 CONS2 MANUAL PROGRAM THRESH1 THRESH2 ni Number of individuals The file size of Size Alteration Event. nie Number of individuals expansion size The file size expansion for the Size Alteration Event. nir Number of individuals reserved The file size of a Size Alteration Event that is reserved for automatic size increase. Number of individuals used The number of individuals in SAE that is being used by the participant block. A measure of the current utilization of a Size Alteration Event. Size Alteration Event (SAE) Software File Congestion Supervision Congestion Event Control Manual Control Program Control Threshold Control defined by the system Threshold Control defined by the application block

niu

sae

Lnh xem ti nguyn cell: SAAEP:SAE=

3.1 SAE Number and Block Information

SAE number and block information, for each type of data file, is shown in Table 1.
Table 1 SAE Block Information

Data File Processor load control Internal cells External GSM cells External UTRAN cells Neighbour Relation Counter, Internal cells Neighbour Relation Counter, External GSM cells MS individuals MS individuals for signalling connection setup UTRAN Cell Data relations CHGR individuals TRXC individuals

SAE 000 298 299 1133 522 523 913 500 502 1152 1153

Block LOAS ROTRAN ROTRAN ROTRAN RQCD RQCD RMCC RMSCS RQUCD RCCGD RXCMOO

62. Time zones:

1 Format
1.1 Command CACAR:DATE=date[,TIMEZONE=timezone]; 1.2 Parameters
DATE=date Date Expressed as yymmdd, where: yy mm dd

Year Numeral 00 - 99 Month Numeral 01 - 12 Day Numeral 01 - 31

TIMEZONE=timezone Time zone If the parameter is omitted, the system time (time zone 0) will be used. The maximum value is defined in the Operating System Area. Numeral 0 - 23

2 Function
This command is used to remove a date from the calendar table. The day category value and the subday category value for this date then take on their default values. The order remains after system restart.

3 Examples
3.1 Example 1
CACAR:DATE=991224; The 24th of December 1999 for the system clock (time zone 0) is removed from the calendar table. The day category value and the subday category value for this date then take on their default values.

3.2 Example 2
CACAR:DATE=991224,TIMEZONE=5; The 24th of December 1999 for time zone 5 is removed from the calendar table. The day category value and the subday category value for this date then take on their default values.

4 Printouts
4.1 Check Printout
Yes.

4.2 Procedure Printouts

EXECUTED NOT ACCEPTED fault type Fault type:

FUNCTION BUSY The function is busy. FORMAT ERROR The command or a parameter was incorrectly specified. UNREASONABLE VALUE details The parameter was specified with an unreasonable value.

4.3 Answer Printouts

This command has no answer printouts.

4.4 Result Printouts

This command has no result printouts.

5 Logging
Yes.

6 Command Category Group

Recommended value 8 (H'8)

7 Command Receiving Block

JOB

8 Glossary
Time zone The calendar function has a system clock and time zones. The system clock is defined as time zone 0. Time zones greater than 0 define the time difference between system time and different regions to that of the system clock.

9 References
This document has no references.

63. Lnh xa channel group ca cell:

1.1 Command RXTCE:MO=mo,CELL=cell,CHGR=chgr...; 1.2 Parameters
CELL=cell Cell designation. Symbolic name, maximum 7 characters. CHGR=chgr Channel Group. A channel group is a part of the cell using a subset of the frequencies

used in a cell. Numeral 0-15. MO=mo Managed Object Instance. See application information for block RXCTA for the format and the value range of this parameter. Only managed objects of managed object class TG are allowed in the command.

2 Function
This command allows the operator to disconnect one or more channel groups from a transceiver group (TG) which has previously been defined. Only managed objects of managed object class TG are allowed in the command. The channel groups must also previously have been defined and halted. The command is not allowed for external cells. A maximum of 16 channel groups can be connected to a TG. The order remains after system restart.

3 Examples
3.1 Example 1
RXTCE:MO=RXETG-7,CELL=LIN3,CHGR=6&7; The command disconnects the channel groups 6 and 7 in the cell LIN3 from TG 7 in BTS logical mode G01.

3.2 Example 2
RXTCE:MO=RXOTG-9,CELL=LIN4,CHGR=0&&15; The command disconnects the channel groups 0 to 15 in the cell LIN4 from TG 9 in BTS logical mode G12.

4 Printouts
4.1 Check Printout
Yes.

4.2 Procedure Printouts

EXECUTED

PARTLY EXECUTED fault type NOT ACCEPTED fault type Fault type:

FUNCTION BUSY Function busy FORMAT ERROR Format error UNREASONABLE VALUE details Unreasonable value FAULT CODE 1 COMMAND NOT SUPPORTED FOR THIS MO The command is not supported for the specified managed object type. FAULT CODE 4 WRONG MO CLASS The specified managed object type has an unsuitable MO class. Only managed objects of managed object class TG are allowed in this command. FAULT CODE 5 MO BUSY The managed object instance is currently in use by another function. FAULT CODE 18 THE SPECIFIED CELL DOES NOT EXIST The specified cell has not been defined. Command RLDEI may be used to define a cell. FAULT CODE 20 CELL CONNECTED TO A RADIO INTERFERENCE RECORDING INDIVIDUAL details The channel group cannot be disconnected due to radio interference recording for the associated cell. The cell must be removed from the recording identity using the command RARDC. FAULT CODE 28 CHGR NOT HALTED details The channel group is not halted. Command RLSTC may be used to halt a channel group. FAULT CODE 29 CHGR NOT DEFINED details

The channel group is not defined. Command RLDGI may be used to define a channel group. FAULT CODE 32 CHGR NOT CONNECTED details The channel group is not connected to the specified managed object. FAULT CODE 38 COMMAND NOT VALID FOR EXTERNAL CELLS The cell specified is external and not allowed in the command. FAULT CODE 20 CELL CONNECTED TO A RADIO INTERFERENCE RECORDING INDIVIDUAL details The channel group cannot be disconnected due to radio interference recording for the associated cell. The cell must be removed from the recording identity using the command RARDC.

Lnh thc hin:

Rarre:rid=, Rardc:rid=, Ramre:rid=, Ramdc:rid=,cell=,

1 Format
1.1 Command
1.1.1 Format 1
/ \ | | |CELL=cell... | | | |CELL=ALL,CSYSTYPE=csystype| | | RARDC:RID=rid,+ +; | / \ | | |arfcn... | | |ARFCN=+ + | | |ALLOCATED| | | \ / | \ /

1.1.2 Format 2
/ \ | / \| | |cell...|| |CELL=+ +| | |ALL ||

| \ /| RARDC:RID=rid,+ +,REM; | | |ARFCN=arfcn...| | | \ /

1.2 Parameters
ARFCN=arfcn Absolute Radio Frequency Channel Number (ARFCN) This parameter indicates the ARFCN for the carrier frequencies for which interference measurements will be made. Numeral 128 - 251 (GSM 800) Numeral 1 - 124 (GSM 900, P-band) Numeral 0, 975 - 1023 (GSM 900, G1-band) Numeral 512 - 810 (GSM 1900) Numeral 512 - 885 (GSM 1800) ALLOCATED Measurements on the frequencies that are allocated in each cell respectively will be made. CELL=cell Cell designation This is a symbolic name of a defined cell. ALL

All internal cells

CSYSTYPE=csystype Cell system type GSM800 System Type GSM 800 GSM900 System type GSM 900 GSM1800 System type GSM 1800 GSM1900 System type GSM 1900 REM Remove specified frequencies This parameter indicates that the specified cells or frequencies are removed from the configuration. RID=rid Recording Identity (RID) for Radio Interference Recording Identifier 7 It is possible to have up to 10 allocated RIDs, named RIRID00 RIRID09.

2 Function

2.1 Format 1
This command adds cells and frequencies to a Radio Interference Recording (RIR) definition. RARDC can be given several times for the same RID. No configuration on the Transceivers (TRXs) is performed before the command RARCI is given. At least one cell must be specified before the frequency option ARFCN , can be given. A cell cannot be defined for more than one RID . CELL=ALL is only accepted for RIDs in state ALLOCATED. If CELL=ALL is given, also CSYSTYPE must be specified. Then all cells with the specified system type are included in the RIR definition. Multi band cells are included as well, if their Broadcast Control Channel (BCCH) resides in the specified system type. Cell list can contain cells with different cell system type. The total number of frequencies for one definition (can be given by several RARDC commands) is limited to 150. The argument for the parameter ARFCN can be specified in two ways: either by a discrete numeral value (test frequency) or by the string ALLOCATED. When ARFCN is specified by test frequencies, all cells connected to the RID measure on those frequencies. The two ways of definition of ARFCN cannot be combined. If ARFCN is specified as ALLOCATED, then test frequencies cannot be added to the definition later on. However, if ARFCN is specified with test frequencies and later on an other RARDC redefines ARFCN as ALLOCATED, then the test frequencies are removed and replaced by the frequencies allocated in each one cell, connected to the RID. ARFCN has a default value which is stated in Application Information for block RORIR. The command is accepted for RIDs in state ALLOCATED, USED, CONFIGURATION COMPLETE or RECORDING COMPLETE. RID state can be checked with command RARRP. After successful execution of RARDC, RID state is changed to USED. For more information about the RID states see the Operational Instruction BSC, Radio Interference Recording, Administer . The order does not remain after system restart.

2.2 Format 2
This command removes cells or frequencies from a RIR definition. If all specified frequencies are removed from the definition, the frequency option ARFCN is set to the default value. The default value is stated in Application Information for block RORIR.

The command is accepted for RIDs in state ALLOCATED, USED, CONFIGURATION COMPLETE or RECORDING COMPLETE. RID state can be checked with command RARRP. After successful execution RID state is changed to ALLOCATED if all cells are removed from the definition and to USED if at least one cell remains in the definition. For more information about the RID states see the Operational Instruction BSC, Radio Interference Recording, Administer . The order does not remain after system restart.

3 Examples
3.1 Example 1
RARDC:RID=RIRID00,CELL=AIRPORT&CITY; This example connects cells AIRPORT and CITY to RID RIRID00.

3.2 Example 2
RARDC:RID=RIRID01,CELL=ALL,CSYSTYPE=GSM900; This example defines the RID RIRID01 to measure on all frequencies in all internal cells with the system type GSM 900. Also multi band cells, having BCCH in GSM 900 band, will be included in the definition.

3.3 Example 3
RARDC:RID=RIRID01,ARFCN=ALLOCATED; This example defines the RID RIRID01 to measure on the allocated frequencies in each cell, that are defined for RIRID01, respectively.

3.4 Example 4
RARDC:RID=RIRID03,CELL=ALL,REM; This example removes all cells defined for the RID RIRID03.

3.5 Example 5
RARDC:RID=RIRID06,ARFCN=20&30,REM; This example removes the ARFCNs 20 and 30 from the RID RIRID06. RARDC:RID=RIRID06,ARFCN=20&&30,REM; This example removes the ARFCNs 20 to 30 from the RID=RIRID06.

3.6 Example 6
RARDC:RID=RIRID07,CELL=ALL,CSYSTYPE=GSM1800;

This example connects all cells with system type GSM 1800 to RIRID07, both single band and multi band cells are included. RARDC:RID=RIRID07,CELL=MBC_B900_1800&SBC900; The second example adds to the definition of RIRID07 a multi band cell MBC_B900_1800 with BCCH in GSM 900 and second frequency band in GSM 1800. A single band cell SBC900 with system type GSM900 can also be added to the same definition.

4 Printouts
4.1 Check Printout
No.

4.2 Procedure Printouts

EXECUTED NOT ACCEPTED fault type Fault type:

FUNCTION BUSY The function is busy. FORMAT ERROR The command or a parameter was incorrectly specified. UNREASONABLE VALUE details The parameter was specified with an unreasonable value. FAULT CODE 3 CELL NOT DEFINED details The cell is not defined. FAULT CODE 38 COMMAND NOT VALID FOR EXTERNAL CELLS details The command must not be used for external cells. FAULT CODE 71 CELL NOT CONNECTED TO THIS RID details Attempt to remove a cell not connected to the RID. FAULT CODE 72 CELL ALREADY CONNECTED TO RID [details]

The cell is already connected to a RID. Note: If ALL was given in the command, no details will be given. FAULT CODE 73 RID IN WRONG STATE The RID is in the wrong state. See the Command Description RARRP and the Operational Instruction BSC, Radio Interference Recording, Administer. FAULT CODE 76 FREQUENCY NOT CONNECTED TO THIS RID details The frequency is not connected to this RID. FAULT CODE 78 ARGUMENT SPECIFIED TWICE IN COMMAND details The argument has already been given in the command. FAULT CODE 80 FREQUENCY ALREADY CONNECTED TO THIS RID details The frequency is already connected to this RID. FAULT CODE 87 TOO MANY FREQUENCIES SPECIFIED details Too many frequencies are specified for one RID. The total number of frequencies for one definition is limited to 150. FAULT CODE 95 NO CELLS WITH SPECIFIED SYSTEM TYPE DEFINED There are no cells of the specified system type defined for the Base Station Controller (BSC).

63. Tm hiu ACA:

5.2.17 Message Store
The function block Adjunct Processor Communication (ACA) is used for high speed reliable data transport from the CP to the AP through the Message Protocol to Adjunct Processor (MTAP) protocol. When the data arrives to the AP, the function Message Store Deamon (MSD) stores it safely. MSD does no interpretation of the data. To check the contents of the safe storage the command msdls can be used. The function block in the CP that sends data to MSD is called MTAP, as is the protocol. These are the alarms from MSD and MTAP: AP MESSAGE STORE WARNING, see section Section 5.3.12 .

The ACA parameters the user is allowed to change and the permitted values of these parameters are described in the function block ACA application information.

64. Lnh block device:

a, Actions
Disconnect Device from Route
1. Is the ETC to be used for other functions? Yes Go to Step 2. No Go to Step 5. 2. Block all devices in the digital path (DIP): Use command BLODI . Printout: BLOCKING RESULT 3. Block the DIP: Use command DTBLI . Alarm printout: BLOCKING SUPERVISION 4. Set the device to the pre-post service state: Use command EXDAE . 5. Disconnect the device from the route: Use command EXDRE .

Remove Signalling Route?

6. Is the signalling route to be removed? Yes Go to Step 7. No Go to Step 8.

Remove Route
7. Remove the route for signalling links: Use command EXROE .

Job Completed
8. Make a report. Note: See Operational Instruction Report of Finished Work . 9. The job is completed.

3 References
3.1 Operational Instructions
Report of Finished Work

3.2 Command Descriptions

BLODI DTBLI EXDAE EXDRE EXROE BLOCKING OF DEVICE, INITIATE DIGITAL PATH TRANSMISSION FUNCTIONS, BLOCKING, INITIATE EXCHANGE DATA, PRE-POST SERVICE, DEVICE ACTIVATION, END EXCHANGE DATA, CONNECTION OF DEVICES IN A ROUTE, END EXCHANGE DATA, SPECIFICATION OF ROUTE DATA, END

3.3 Printout Descriptions

BLOCKING RESULT BLOCKING SUPERVISION

4 Additional Information
No additional information is applicable to this document.

5 Glossary
DIP ETC PCD Digital Path Exchange Terminal Circuit Pulse Code Modulation Device

3.4

EXDUE:DEV=dev...;

This command disconnects devices from a Switching Network Terminal (SNT) unit. Note: For 155 Mbit/s Exchange Terminal (ET) it is possible to disconnect only a sequence of 32 devices, which is the default value defined for one SNT inlet.

The order remains after system restart.

3.5

exdri: dev=UPD1-34273&&-34303, r=VINA1CO&VINA1CI, misc1=3141;

MISC1=misc1 Miscellaneous information For value range see the Application Information for the relevant device block. This command connects devices to a route. For affiliated routes, indication is made to all the route names in the command

65. Lenh Reset giam sat kenh TCH, SDCCH:

RADIO CONTROL CELL SEIZURE SUPERVISION OF LOGICAL CHANNELS ALARM, RESET 1 Format
1.1 Command
RLVAR:CHTYPE=chtype;

1.2 Parameters
CHTYPE=chtype Channel type TCH SDCCH Traffic Channel Stand Alone Dedicated Control Channel.

2 Function
This command is used to order alarm reset of all unapproved TCHs and SDCCHs for internal cells with seizure supervision active. All information about alarmed logical channels per channel type (TCH,SDCCH) is cleared by this command, and can no longer be printed. The order does not remain after system restart.

3 Examples
3.1 Example 1
RLVAR:CHTYPE=TCH;

Reset seizure supervision alarm for channel type TCH.

3.2 Example 2
RLVAR:CHTYPE=SDCCH; Reset seizure supervision alarm for channel type SDCCH.

4 Printouts
4.1 Check Printout
Yes.

4.2 Procedure Printouts

EXECUTED NOT ACCEPTED fault type

Fault type: FUNCTION BUSY Function busy FORMAT ERROR Format error UNREASONABLE VALUE FAULT CODE 84 NO ALARM GIVEN Unreasonable value

Alarm resetting ordered but no alarm had been given.

LENH XEM PROFILE:

nsstp; gdstp; ioexp; c7spp:sp=all; ntcop:snt=all; dbtsp:tab=rps501boards; dphip;