ned

ED - Cellular Network ControllerHandling

DN985789Issue 14-1 en

# Nokia Siemens Networks 1 (104)

MSC/HLR, Rel. M14.2, Product Documentation,v.2

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended for theuse of Nokia Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted inany form or means without the prior written permission of Nokia Siemens Networks. Thedocumentation has been prepared to be used by professional and properly trained personnel,and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomescustomer comments as part of the process of continuous development and improvement of thedocumentation.

The information or statements given in this documentation concerning the suitability, capacity, orperformance of the mentioned hardware or software products are given “as is” and all liabilityarising in connection with such hardware or software products shall be defined conclusively andfinally in a separate agreement between Nokia Siemens Networks and the customer. However,Nokia Siemens Networks has made all reasonable efforts to ensure that the instructionscontained in the document are adequate and free of material errors and omissions. NokiaSiemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues whichmay not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NOEVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUTNOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESSOPPORTUNITY OR DATA, THAT MAYARISE FROM THE USE OF THIS DOCUMENT OR THEINFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights andother intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark ofNokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners,and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2008. All rights reserved.

2 (104) # Nokia Siemens Networks DN985789Issue 14-1 en

ED - Cellular Network Controller Handling

Contents

Contents 3

List of tables 4

List of figures 5

Summary of changes 7

ED - CELLULAR NETWORK CONTROLLER HANDLING 9

EDC CREATE CELLULAR NETWORK CONTROLLER 13

EDD DELETE CELLULAR NETWORK CONTROLLER 23

EDE RESTART CELLULAR NETWORK CONTROLLER 27

EDS CHANGE CELLULAR NETWORK CONTROLLERADMINISTRATIVE STATE 31

EDR DEFINE ROUTES 35

EDL DEFINE SIGNALLING SYSTEM INFORMATION 45

EDM CHANGE CELL IDENTIFICATION METHOD 49

EDP CHANGE PAGING METHOD 53

EDI CHANGE CHANNEL PRIORITY ASSIGNMENT FUNCTIONMODE 57

EDH CHANGE REVERSED CIRCUIT ALLOCATION FUNCTIONMODE 61

EDN MODIFY NAME OF BSSAP VERSION 65

EDT MODIFY INFORMATION ON BSSAP VERSION 67

EDV MODIFY VERSION OF BSSAP 81

EDG MODIFY CELLULAR NETWORK CONTROLLER PARAMETERS85

EDB OUTPUT INFORMATION ON BSSAP VERSION 89

EDO OUTPUT CELLULAR NETWORK CONTROLLER DATA 97



Contents

List of tables



List of figures



List of figures

Summary of changes

Changes between document issues are cumulative. Therefore, the latestdocument issue contains all changes made to previous issues.

Changes made between issues 14-1 and 14-0

The new optional 'A5/3 ciphering supported' value has been added to theBSSAP functional parameter of EDT and EDB commands.

The generic 'A_2 ciphering supported' value of the BSSAP functionalparameter has been changed to optional in the EDT command.


MGW R99 can only be handled with the EDS, EDD, and EDO commands.MGW R99 has been removed from other commands including it.

The EDF and EDK commands have been removed.


EDO OUTPUT CELLULAR NETWORK CONTROLLER DATA

The UPD and NUPD parameters have been added to the EDO command.



Summary of changes

ED - CELLULAR NETWORK CONTROLLERHANDLING

With the commands in this command group, you can create, delete, andrestart Base Station Controllers (BSC) and Unlicensed Mobile AccessNetwork Controller (UNC/UNCP) and handle the parameters of the BSCsand UNCs in the MSC or MSC Server (MSS).

There are two types of UNCs. The UNC with A+-interface (UNCP in thisdocument) is a modified A-interface with UMA extensions. However, alsoUNC with standard A-interface is supported by the Nokia MSC/MSS.

You can modify the following parameters:

. BSC/UNC administrative state

. routing

. signalling point code and BSSAP subsystem number <option>

. cell identification method

. paging method

. channel priority assignment function mode

. reversed circuit allocation function mode <option>

. BSSAP version of the BSC/UNC

. user plane destination (UPD) <option>

You can also output data from the BSCs/UNCs and BSSAP version, andmodify the following BSSAP version-specific information:

. A-interface timers and parameters

. BSS functional parameters.



ED - CELLULAR NETWORK CONTROLLER HANDLING

With optional commands, it is also possible to remove MGW Release 99from the MSS.

When you want to define or modify the location area-BTS-BSC/UNCrelation, use the EPB command from the BTS and SA handling, EPCommand Group.

More information can be found in the Cellular Radio Network Managementmanual.

Menu of the command group:

CELLULAR NETWORK CONTROLLER HANDLING COMMANDS

? ..... DISPLAY MENU

C: ..... CREATE CELLULAR NETWORK CONTROLLER

D: ..... DELETE CELLULAR NETWORK CONTROLLER

E: ..... RESTART CELLULAR NETWORK CONTROLLER

S: ..... CHANGE CELLULAR NETWORK CONTROLLER ADMINISTRATIVE STATE

R: ..... DEFINE ROUTES

L: ..... DEFINE SIGNALLING SYSTEM INFORMATION

M: ..... CHANGE CELL IDENTIFICATION METHOD

P: ..... CHANGE PAGING METHOD

I: ..... CHANGE CHANNEL PRIORITY ASSIGNMENT FUNCTION MODE

H: ..... CHANGE REVERSED CIRCUIT ALLOCATION FUNCTION MODE <OPTION>

N: ..... MODIFY NAME OF BSSAP VERSION

T: ..... MODIFY INFORMATION ON BSSAP VERSION

V: ..... MODIFY VERSION OF BSSAP

G: ..... MODIFY CELLULAR NETWORK CONTROLLER PARAMETERS <OPTION>

B: ..... OUTPUT INFORMATION ON BSSAP VERSION

O: ..... OUTPUT CELLULAR NETWORK CONTROLLER DATA

Z; ..... RETURN TO MAIN LEVEL

The commands in this command group are:

EDC CREATE CELLULAR NETWORK CONTROLLER

EDD DELETE CELLULAR NETWORK CONTROLLER

EDE RESTART CELLULAR NETWORK CONTROLLER

EDS CHANGE CELLULAR NETWORK CONTROLLERADMINISTRATIVE STATE

EDR DEFINE ROUTES

EDL DEFINE SIGNALLING SYSTEM INFORMATION

EDM CHANGE CELL IDENTIFICATION METHOD

EDP CHANGE PAGING METHOD

EDI CHANGE CHANNEL PRIORITY ASSIGNMENTFUNCTION MODE

EDH CHANGE REVERSED CIRCUIT ALLOCATIONFUNCTION MODE <OPTION>



EDN MODIFY NAME OF BSSAP VERSION

EDT MODIFY INFORMATION ON BSSAP VERSION

EDV MODIFY VERSION OF BSSAP

EDG MODIFY CELLULAR NETWORK CONTROLLERPARAMETERS <OPTION>

EDB OUTPUT INFORMATION ON BSSAP VERSION

EDO OUTPUT CELLULAR NETWORK CONTROLLERDATA



ED - CELLULAR NETWORK CONTROLLER HANDLING

EDC CREATE CELLULAR NETWORKCONTROLLERFunction With this command you can create a BSC or UNC (and UNCP) in an MSC

or MSS by giving the BSC/UNC name and number.

Note

The system automatically creates a BSC/UNC in administrative stateLOCKED. This means that the BSC/UNC is not in operational use. Tobring the BSC/UNC into operational use, change it to state UNLOCKEDwith the EDS command.

Parameters object identification: reference object identification: pool view mode;

Syntax EDC: [ TYPE=<object type | BSC def> ],

NAME=<object name>,

NO=<object number>:

[ RNAME=<reference object name> |

RNO=<reference object number> |

<default parameter values> def ]:

[ <pool view mode | ALL def> ];

Parameterexplanations

TYPE: object type

Parameter Value Description

TYPE BSC base station controller (default)

UNC unlicensed mobile access network controller with A -interface <option>

UNCP unlicensed mobile access network controller with A+ -interface <option>




If Feature 1705: Unlicensed Mobile Access (UMA) support in MSC/MSCServer is not activated, only the BSC can be chosen as type of object.

NAME: object name


NAME text string of 1 to 10 characters BSC/UNC name

Name must be unique.

NO: object number


NO decimal from 1 to 4095 BSC/UNC number

Number must be unique.

Give both the name and number.

RNAME and RNO: reference object name and number


RNAME text string of 1 to 10 characters reference BSC/UNC name

RNO decimal from 1 to 4095 reference BSC/UNC number

These parameters identify the BSC/UNC that already exists in yournetwork. Use either RNAME or RNO to copy the parameter values of thereference object to the parameters of the BSC/UNC you are creating.

Reference object parameter values are copied to the following parameters:

. BSSAP subsystem number <option>

. cell identification method

. paging method

. BSSAP version

. channel priority assignment function mode



. reversed circuit allocation function mode <option>

. user plane destination <option>

If you do not give a reference object, the default values are used in theparameters listed above.

pool view mode

This parameter defines whether the circuit pools are included in theexecution printout. The parameter can have the following values:

Value Description

ALL all available circuit pools are shown (default)

NONE circuit pools are not shown

Note

In the case of UNCP, the parameter is not relevant.

Examples 1. Create the BSC with the name BSC2 and number 693, using thereference BSC name BSC1. Default value ALL is used for pool viewmode, so all available circuit pools would be shown in the executionprintout.

ZEDC:TYPE=BSC,NAME=BSC2,NO=693:RNAME=BSC1:ALL;

2. Create the BSC with the name BSC2 and number 832, using thedefault BSC parameter values. Pool view mode is defined as NONE,so the circuit pools would not be shown in the execution printout.

ZEDC:NAME=BSC2,NO=832::NONE;

3. Create the UNCP with the name UNCAPLUS1 and number 200,using the default UNCP parameter values.

ZEDC:TYPE=UNCP,NAME=UNCAPLUS1,NO=200;

4. Create the UNC with the name UNCAINT10 and number 300, usingthe default UNC parameter values.

ZEDC:TYPE=UNC,NAME=UNCAINT10,NO=300;

Executionprintouts

The abbreviations used in the execution printouts:




CI= cell identity

LAC= location area code

UMA= unlicensed mobile access

The program outputs the object name, number, and data aftermodifications in CMU files have succeeded. For example, the ZEDC:TYPE=BSC,NAME=ROAD21,NO=313; command creates the BSC with thename ROAD21 and number 313. The default is used for pool view mode.The output is as follows:

DX 200 DX220-LAB 2001-07-19 10:28:56

CREATING BASE STATION CONTROLLER

BSC NAME .......................(NAME). :ROAD21

BSC NUMBER .....................(NO)... :313

BSC ADMINISTRATIVE STATE .............. :LOCKED

BSC OPERATIONAL STATE ................. : -

BSC TRAFFIC LIMITATION ................ : -

SIGNALLING NETWORK CODE ........(SNC).. : -

SIGNALLING POINT CODE ..........(SPC).. : - (hex)

BSSAP SUBSYSTEM NUMBER .........(SSN).. :FE (hex)

CELL IDENTIFICATION METHOD .....(CID).. :CLI

PAGING METHOD ......................... :LAC

BSSAP VERSION ..................(VER).. :15

PRIORITY ASSIGNMENT FUNCTION .......... :OFF

CIRCUIT ALLOCATION BY BSS ............. :OFF

CIRCUIT POOLS : ROUTE :

0: NOT APPLICABLE .................... : -

1: FR ................................ : -

2: HR ................................ : -

3: DR ................................ : -

4: FR DATA/EFR ....................... : -

5: FR/EFR ............................ : -

6: EFR/FR DATA/HR .................... : -

7: DR/EFR ............................ : -

8: HSCSD 2 FR ........................ : -

9: DR DATA/HSCSD 2 FR ................ : -

10: DR/EFR/HSCSD 2 FR ................. : -

11: HSCSD 4 FR ........................ : -

12: DR DATA/HSCSD 4 FR ................ : -

13: DR/EFR/HSCSD 4 FR ................. : -

15: FR DATA 14.5 ...................... : -

16: HSCSD 2 FR 14.5 ................... : -

17: HSCSD 4 FR 14.5 ................... : -

18: DR DATA/HSCSD 2 FR 14.5 ........... : -

19: DR DATA 14.5/HSCSD 4 FR 14.5 ...... : -

20: DR 14.5/EFR ....................... : -

21: DR 14.5/EFR/HSCSD 2 FR 14.5 ....... : -

22: DR 14.5/EFR/HSCSD 4 FR 14.5 ....... : -

23: AMR ............................... : -



24: AMR/FR DATA ....................... : -

25: FR/EFR/AMR/FR DATA ................ : -

26: FR/EFR/AMR/FR DATA 14.5 ........... : -

27: DR/EFR/AMR/DR DATA ................ : -

28: DR/EFR/AMR/DR DATA 14.5 ........... : -

29: DR/EFR/AMR/DR DATA/HSCSD 2 ........ : -

30: DR/EFR/AMR/DATA/HSCSD 2/14.5 ...... : -



42: CTM + FR .......................... : -

43: CTM + EFR ......................... : -

44: CTM + FR/EFR ...................... : -

45: CTM + DR/EFR ...................... : -

46: CTM + AMR ......................... : -

47: CTM + FR/EFR/AMR .................. : -

48: CTM + DR/EFR/AMR .................. : -

CIRCUIT POOLS WITH TFO : ROUTE :

1: FR ................................ : -

3: DR ................................ : -

4: FR DATA/EFR ....................... : -

5: FR/EFR ............................ : -

6: EFR/FR DATA/HR .................... : -

7: DR/EFR ............................ : -

10: DR/EFR/HSCSD 2 FR ................. : -

13: DR/EFR/HSCSD 4 FR ................. : -

20: DR 14.5/EFR ....................... : -

21: DR 14.5/EFR/HSCSD 2 FR 14.5 ....... : -

22: DR 14.5/EFR/HSCSD 4 FR 14.5 ....... : -

25: FR/EFR/AMR/FR DATA ................ : -

26: FR/EFR/AMR/FR DATA 14.5 ........... : -

27: DR/EFR/AMR/DR DATA ................ : -

28: DR/EFR/AMR/DR DATA 14.5 ........... : -





42: CTM + FR .......................... : -

43: CTM + EFR ......................... : -

44: CTM + FR/EFR ...................... : -

45: CTM + DR/EFR ...................... : -

47: CTM + FR/EFR/AMR .................. : -

48: CTM + DR/EFR/AMR .................. : -

BTSs UNDER BSC :

NO BTS LOCATED

COMMAND EXECUTED




Note

BSSAP subsystem number can be modified with the optionalparameter in the EDL command and circuit allocation by BSS with theoptional EDH command.

Visibility of the circuit pools 1–32, 42–48, and all TFO pools depend onthe options that are used. Pools are described in the explanation of thepool number parameter in the EDR command.

If the pool view mode had been defined as NONE in the previouscommand, the output would have been as follows:

DX 200 DX220-LAB 2001-07-19 10:28:56

CREATING BASE STATION CONTROLLER

BSC NAME .......................(NAME). :ROAD21

BSC NUMBER .....................(NO)... :313

BSC ADMINISTRATIVE STATE .............. :LOCKED

BSC OPERATIONAL STATE ................. : -

BSC TRAFFIC LIMITATION ................ : -









BTSs UNDER BSC :

NO BTS LOCATED

COMMAND EXECUTED

In this example, the ZEDC:TYPE=UNCP,NAME=UNCAPLUS1,NO=200;command creates the UNC with A+ -interface with name UNCAPLUS1and number 200. Circuit pools are not relevant in case of UNCP. Theoutput is as follows:

DX 200 DX220-LAB 2001-07-19 10:29:13

CREATING UMA NETWORK CONTROLLER

UNC NAME .......................(NAME). :UNCAPLUS1

UNC NUMBER .....................(NO)... :200

UNC ADMINISTRATIVE STATE .............. :LOCKED

UNC OPERATIONAL STATE ................. : -

UNC TRAFFIC LIMITATION ................ : -





BSSAP SUBSYSTEM NUMBER .........(SSN).. :71 (hex)





USER PLANE DESTINATION INDEX ...(UPD).. : -

USER PLANE DESTINATION NAME ....(NUPD). : -

BTSs UNDER UNC :

NO BTS LOCATED

COMMAND EXECUTED

Note

The User Plane Destination (UPD) can be modified with the EDGcommand.

If the object to be created is UNCP, pools are not displayed. Circuitallocation by BSS is omitted from the printout because that feature isirrelevant to the UNCP.

In this example, the ZEDC:TYPE=UNC,NAME=UNCAINT10,NO=300;command creates the UNC with A-interface with name UNCAINT10 andnumber 300. The default is used for pool view mode. The output is asfollows:

DX 200 DX220-LAB 2001-07-19 10:29:13

CREATING UMA NETWORK CONTROLLER

UNC NAME .......................(NAME). :UNCAINT10

UNC NUMBER .....................(NO)... :300













0: NOT APPLICABLE .................... : -

1: FR ................................ : -

2: HR ................................ : -

3: DR ................................ : -




4: FR DATA/EFR ....................... : -

5: FR/EFR ............................ : -

6: EFR/FR DATA/HR .................... : -

7: DR/EFR ............................ : -

8: HSCSD 2 FR ........................ : -

9: DR DATA/HSCSD 2 FR ................ : -

10: DR/EFR/HSCSD 2 FR ................. : -

11: HSCSD 4 FR ........................ : -

12: DR DATA/HSCSD 4 FR ................ : -

13: DR/EFR/HSCSD 4 FR ................. : -

15: FR DATA 14.5 ...................... : -

16: HSCSD 2 FR 14.5 ................... : -

17: HSCSD 4 FR 14.5 ................... : -

18: DR DATA/HSCSD 2 FR 14.5 ........... : -

19: DR DATA 14.5/HSCSD 4 FR 14.5 ...... : -

20: DR 14.5/EFR ....................... : -

21: DR 14.5/EFR/HSCSD 2 FR 14.5 ....... : -

22: DR 14.5/EFR/HSCSD 4 FR 14.5 ....... : -

23: AMR ............................... : -

24: AMR/FR DATA ....................... : -

25: FR/EFR/AMR/FR DATA ................ : -

26: FR/EFR/AMR/FR DATA 14.5 ........... : -

27: DR/EFR/AMR/DR DATA ................ : -

28: DR/EFR/AMR/DR DATA 14.5 ........... : -





42: CTM + FR .......................... : -

43: CTM + EFR ......................... : -

44: CTM + FR/EFR ...................... : -

45: CTM + DR/EFR ...................... : -

46: CTM + AMR ......................... : -

47: CTM + FR/EFR/AMR .................. : -

48: CTM + DR/EFR/AMR .................. : -


1: FR ................................ : -

3: DR ................................ : -

4: FR DATA/EFR ....................... : -

5: FR/EFR ............................ : -

6: EFR/FR DATA/HR .................... : -

7: DR/EFR ............................ : -

10: DR/EFR/HSCSD 2 FR ................. : -

13: DR/EFR/HSCSD 4 FR ................. : -

20: DR 14.5/EFR ....................... : -

21: DR 14.5/EFR/HSCSD 2 FR 14.5 ....... : -

22: DR 14.5/EFR/HSCSD 4 FR 14.5 ....... : -

25: FR/EFR/AMR/FR DATA ................ : -

26: FR/EFR/AMR/FR DATA 14.5 ........... : -

27: DR/EFR/AMR/DR DATA ................ : -

28: DR/EFR/AMR/DR DATA 14.5 ........... : -







42: CTM + FR .......................... : -

43: CTM + EFR ......................... : -

44: CTM + FR/EFR ...................... : -

45: CTM + DR/EFR ...................... : -

47: CTM + FR/EFR/AMR .................. : -

48: CTM + DR/EFR/AMR .................. : -

BTSs UNDER UNC :

NO BTS LOCATED

COMMAND EXECUTED

Note

BSSAP subsystem number can be modified with the optionalparameter in the EDL command and circuit allocation by BSS with theoptional EDH command.

Visibility of the circuit pools 1–32, 42–48, and all TFO pools depend onthe options that are used. Pools are described in the explanation of thepool number parameter in the EDR command.

Semantic errormessages

If an error occurs, the system displays a general MML semantic errormessage.

Execution errormessages

If an error occurs, the system displays a general MML execution errormessage.




EDD DELETE CELLULAR NETWORKCONTROLLERFunction With this command you can delete a BSC, UNC, or MGW R99 from an

MSC or MSS by giving the BSC/UNC/MGW name or number.

Before you delete a BSC/UNC/MGW, check with the EDO command thatthere are no BTSs or SACs connected to it (since BSC/UNC/MGW can notbe deleted if there is a BTS/SAC relation). BTS/SAC relation can beremoved by modifying the BTS-BSC/UNC relation with the EPB commandor SAC-MGW relation with the optional EPF command.

Also ensure that the BSC/UNC/MGW is in administrative state LOCKEDbefore you delete it. Use the EDS command to change the administrativestate.

Parameters object identification;

Syntax EDD: [ TYPE=<object type | BSC def> ],

( NAME=<object name> |

NO=<object number> );


TYPE: object type





MGW multimedia gateway R99 <option>




If Feature 1260: Inter System Handover and UMTS Changes in MSC andFeature 1705: Unlicensed Mobile Access (UMA) support in MSC/MSCServer are not activated, only BSC can be chosen as type of object.

NAME: object name


NAME text string of 1 to 10 characters BSC/UNC/MGW name

NO: object number


NO decimal from 1 to 4095 BSC/UNC/MGW number

Name or number has to be given.

Examples 1. Delete the BSC named BSC2.

ZEDD:TYPE=BSC,NAME=BSC2;

2. Delete the MGW number 3618.

ZEDD:TYPE=MGW,NO=3618;

3. Delete the UNCP named UNCPLUS1.

ZEDD:TYPE=UNCP,NAME=UNCPLUS1;

Executionprintouts

The program outputs the object name and number after the modificationsin the CMU files have succeeded.

Command ZEDD:TYPE=BSC,NAME=DISTR1; deletes the BSC namedDISTR1. The output is as follows:

DX 200 DX220-LAB 2001-07-19 10:29:33

DELETING BASE STATION CONTROLLER

BSC NAME .......................(NAME). :DISTR1

BSC NUMBER .....................(NO)... :2950

COMMAND EXECUTED

Command ZEDD:TYPE=MGW,NO=13; deletes the MGW number 13. Theoutput is as follows:



DX 200 DX220-LAB 2001-07-19 10:29:51

DELETING MULTIMEDIA GATEWAY R99

MGW R99 NAME ...................(NAME). :ABCD

MGW R99 NUMBER .................(NO)... :13

COMMAND EXECUTED

Command ZEDD:TYPE=UNCP,NAME=UNCPLUS1; deletes the UNC+named UNCPLUS1. The output is as follows:

DX 200 DX220-LAB 2001-07-19 10:29:33

DELETING UMA NETWORK CONTROLLER

UNC NAME .......................(NAME). :UNCPLUS1

UNC NUMBER .....................(NO)... :100

COMMAND EXECUTED








EDE RESTART CELLULAR NETWORKCONTROLLERFunction With this command you can restart a BSC or UNC by giving the BSC/UNC

name or number.

Note

The object must be in administrative state UNLOCKED before yourestart it. Use the EDS command to change the administrative state.

Parameters object identification;

Syntax EDE: [ TYPE=<object type | BSC def> ],


NO=<object number> );


TYPE: object type






NAME: object name






NO: object number




Examples 1. Restart the BSC named OXFORD.

ZEDE:TYPE=BSC,NAME=OXFORD;

2. Restart the UNC named UNCA100.

ZEDE:TYPE=UNC,NAME=UNCA100;

Executionprintouts

The program outputs the object name and number after the initiation of theBSC restart sequence in the MSC has succeeded.

Command ZEDE:TYPE=BSC,NAME=ABERDEEN; restarts the BSC namedABERDEEN. The output is as follows:

DX 200 DX220-LAB 2001-07-19 10:30:06

RESTARTING BASE STATION CONTROLLER

BSC NAME .......................(NAME). :ABERDEEN

BSC NUMBER .....................(NO)... :2950

COMMAND EXECUTED

Command ZEDE:TYPE=UNC,NAME=UNCA100; restarts the UNC namedUNCA100. The output is as follows:

DX 200 DX220-LAB 2001-07-19 10:30:06

RESTARTING UMA NETWORK CONTROLLER

UNC NAME .......................(NAME). :UNCA100

UNC NUMBER .....................(NO)... :100

COMMAND EXECUTED





EDS CHANGE CELLULAR NETWORKCONTROLLER ADMINISTRATIVE STATEFunction With this command you can change the administrative state of one or

more BSCs/UNCs or MGW R99s by giving the BSC/UNC/MGW names ornumbers and BSC/UNC/MGW administrative state.

You need to use this command, for example, when:

. you want to bring a BSC/UNC/MGW into operational use bychanging the administrative state to UNLOCKED (because thesystem always creates a BSC/UNC/MGW in administrative stateLOCKED)

. you want to delete a BSC/UNC/MGW and it is in state UNLOCKED

. you want to restart a BSC/UNC/MGW and it is in state LOCKED

Note

Before you change the BSC/UNC (A-interface)/MGW administrativestate to UNLOCKED, at least one route has to be defined with the EDRcommand or the circuit allocation by BSS has to be enabled with theoptional EDH command. Before changing the UNCP (A+ interface)administrative state to 'UNLOCKED', the user plane destination has tobe defined with the EDG command. Also, a signalling point code has tobe defined with the EDL command for the BSC/UNC/MGW.

Changing BSC/UNC/MGW administrative state to LOCKED when it isalready locked in file is allowed, because this way you can try to resolvea possible state conflict error situation between RNEUPD andCRMPRB.

Parameters object identification: object administrative state;




Syntax EDS: [ TYPE=<object type | BSC def> ],

( NAME=<object name>... |

NO=<object number>... ):

( U |

L );


TYPE: object type




UNCP unlicensed mobile access network controller with A+interface <option>


If Feature 1260: Inter-System Handover and UMTS Changes in MSC andFeature 1705: Unlicensed Mobile Access (UMA) support in MSC/MSCServer are not activated, only the BSC can be chosen as type of object.

NAME: object name



The character '&' can be used to give several object names.

NO: object number



The character '&' can be used to give several object numbers.


object administrative state

This parameter defines whether the object is in operational use, that is,whether it is recognised by the MSC call control functions. The parametercan have the following values:



Value Description

U unlocked (object is in operational use)

L locked (object is not in operational use)

Give either U or L.

Examples 1. Change the administrative state of the BSC named BSCO2 toUNLOCKED:

ZEDS:TYPE=BSC,NAME=BSCO2:U;

2. Change the administrative state of the BSCs numbered 2305 and2463 to LOCKED:

ZEDS:TYPE=BSC,NO=2305&2463:L;

3. Change the administrative state of the MGWs named HIGHW3 andHIGHW23 to UNLOCKED:

ZEDS:TYPE=MGW,NAME=HIGHW3&HIGHW23:U;

4. Change the administrative state of the UNCP named UNCP200 toUNLOCKED:

ZEDS:TYPE=UNCP,NAME=UNCP200:U;

Executionprintouts

The program outputs the object name, number, and administrative statevalue after the modifications in the CMU files have succeeded.

Command ZEDS:TYPE=BSC,NO=345:U; modifies the state of the BSCnumber 345 to UNLOCKED. The output is as follows:

DX 200 DX220-LAB 2001-07-19 10:30:31

CHANGING BASE STATION CONTROLLER ADMINISTRATIVE STATE

BSC ADMINISTRATIVE STATE .............. :UNLOCKED

BSC LIST :

MANCHESTER 345

COMMAND EXECUTED

Command ZEDS:TYPE=MGW,NAME=MGWA1&MGWA2:L; modifies theadministrative state of the MGWs named MGWA1 and MGWA2 toLOCKED. The output is as follows:




DX 200 DX220-LAB 2001-07-19 10:30:39

CHANGING MULTIMEDIA GATEWAY R99 ADMINISTRATIVE STATE

MGW R99 ADMINISTRATIVE STATE .......... :LOCKED

MGW R99 LIST :

MGWA1 185

MGWA2 186

COMMAND EXECUTED

Command ZEDS:TYPE=UNCP,NO=200:U; modifies the state of the UNCnumber 200 to UNLOCKED. The output is as follows:

DX 200 DX220-LAB 2001-07-19 10:30:31

CHANGING UMA NETWORK CONTROLLER ADMINISTRATIVE STATE

UNC ADMINISTRATIVE STATE .............. :UNLOCKED

UNC LIST :

UNCP200 200

COMMAND EXECUTED







EDR DEFINE ROUTESFunction With this command you can define the routes of the circuit pools between

a BSC/UNC (A-interface) and an MSC/MSS by giving the BSC/UNC (A-interface) name or number and pool and route numbers.

You need to define at least one route with this command, or enable circuitallocation by BSS with the optional EDH command, before you change theBSC/UNC (A-interface) administrative state from LOCKED toUNLOCKED.

The commands in the routing management function class are related tothis command.

Parameters object identification: pool number, route number, pool TFO capability<option>;

Syntax EDR: [ TYPE=<object type | BSC def> ],


NO=<object number> ):

<pool number>,

<route number>,

[ <pool TFO capability | N def> <option> ];


TYPE: object type







EDR DEFINE ROUTES

NAME: object name



NO: object number




pool number

A circuit pool is a group of circuits that all have the same transcodingcapabilities. Different pool numbers have been defined for different rateimplementations. The pool number parameter is obligatory. Available poolnumbers depend on which optional features are in use.

Pool number 0 is always available. Pool number 1 and the rest of the poolsare available when the optional reversed circuit allocation feature is not inuse. Pool numbers 2 and 3 are available when the optional half-rate codecfeature is in use. Pool numbers 4–7 are available when the optionalenhanced full-rate codec feature is in use. Pool numbers 8–13 areavailable when the optional high speed circuit switched data feature is inuse. Pool numbers 15–22 are available when the optional 14.4 kbit/s datatraffic channel feature is in use. Pool numbers 23–32 are available whenthe optional AMR speech codec feature is in use. Pool numbers 42–48 areavailable when the optional CTM (Cellular Text Telephone Modem)functionality feature is in use. TFO pool numbers 1, 3–7, 10, 13, 20–22,25–32, 42–45, and 47–48 are available when the optional TFO and theabove mentioned pool number specific features are in use.

Note

With the BSC/UNC, when the optional reversed circuit allocation is inuse, only pool number 0 is available. The route of all other pools canstill be removed. This is because the BSC/UNC is now taking care ofroute allocation, so route definition is no longer needed in the MSC/MSS.

Pool numbers:



. 0: Not applicable

The BSC is not using any pools.

. 1: FR

This is the BSC's pool that supports full-rate speech and data. TFOsupport is optional.

. 2: HR <OPTION>

This is the BSC's pool that supports half-rate speech and data.

. 3: DR <OPTION>

This is the BSC's pool that supports both full- and half-rate speechand data. TFO support is optional.

. 4: FR DATA/EFR <OPTION>

This is the BSC's pool that supports enhanced full-rate speech andfull-rate data. TFO support is optional.

. 5: FR/EFR <OPTION>

This is the BSC's pool that supports enhanced full-rate speech andfull-rate speech and data. TFO support is optional.

. 6: EFR/FR DATA/HR <OPTION>

This is the BSC's pool that supports enhanced full-rate speech, full-rate data, and half-rate speech and data. TFO support is optional.

. 7: DR/EFR <OPTION>

This is the BSC's pool that supports enhanced full-rate speech andboth full- and half-rate speech and data. TFO support is optional.

. 8: HSCSD 2 FR <OPTION>

This is the BSC's pool that supports the maximum of 2 full-ratechannels on a multislot configuration. The maximum radio interfacedata rate per channel is 12 kb/s.

. 9: DR DATA/HSCSD 2 FR <OPTION>

This is the BSC's pool that supports both full- and half-rate data, andthe maximum of 2 full-rate channels on a multislot configuration. Themaximum radio interface data rate per channel is 12 kb/s.

. 10: DR/EFR/HSCSD 2 FR <OPTION>



EDR DEFINE ROUTES

This is the BSC's pool that supports both full- and half-rate speechand data, enhanced full-rate speech, and the maximum of 2 full ratechannels on a multislot configuration. The maximum radio interfacedata rate per channel is 12 kb/s. TFO support is optional.

. 11: HSCSD 4 FR <OPTION>

This is the BSC's pool that supports the maximum of 4 full-ratechannels on a multislot configuration. The maximum radio interfacedata rate per channel is 12 kb/s.

. 12: DR DATA/HSCSD 4 FR <OPTION>

This is the BSC's pool that supports both full- and half-rate data andthe maximum of 4 full-rate channels on a multislot configuration. Themaximum radio interface data rate per channel is 12 kb/s.

. 13: DR/EFR/HSCSD 4 FR <OPTION>

This is the BSC's pool that supports both full- and half-rate speechand data, enhanced full-rate speech, and the maximum of 4 full-ratechannels on a multislot configuration. The maximum radio interfacedata rate per channel is 12 kb/s. TFO support is optional.

. 15: FR DATA 14.5 <OPTION>

This is the BSC's pool that supports full-rate data. The radio interfacedata rate used is 14.5 kb/s.

. 16: HSCSD 2 FR 14.5 <OPTION>

This is the BSC's pool that supports the maximum of 2 full-ratechannels on a multislot configuration. The radio interface data rateused is 14.5 kb/s.

. 17: HSCSD 4 FR 14.5 <OPTION>

This is the BSC's pool that supports the maximum of 4 full-ratechannels on a multislot configuration. The radio interface data rateused is 14.5 kb/s.

. 18: DR DATA/HSCSD 2 FR 14.5 <OPTION>

This is the BSC's pool that supports both full- and half-rate data andthe maximum of 2 full-rate channels on a multislot configuration. Themaximum radio interface data rate per channel is 14.5 kb/s.

. 19: DR DATA 14.5/HSCSD 4 FR 14.5 <OPTION>

This is the BSC's pool that supports both full- and half-rate data, andthe maximum of 4 full-rate channels on a multislot configuration. Themaximum radio interface data rate per channel is 14.5 kb/s.



. 20: DR 14.5/EFR <OPTION>

This is the BSC's pool that supports both full- and half-rate speechand data, and enhanced full-rate speech. With full- and half-ratechannels the maximum radio interface data rate per channel is 14.5kb/s. TFO support is optional.

. 21: DR 14.5/EFR/ HSCSD 2 FR 14.5 <OPTION>

This is the BSC's pool that supports both full- and half-rate speechand data, enhanced full-rate speech, and the maximum of 2 full-ratechannels on a multislot configuration. The maximum radio interfacedata rate per channel is 14.5 kb/s. TFO support is optional.

. 22: DR 14.5/EFR/ HSCSD 4 FR 14.5 <OPTION>

This is the BSC's pool that supports both full- and half-rate speechand data, enhanced full-rate speech, and the maximum of 4 full-ratechannels on a multislot configuration. The maximum radio interfacedata rate per channel is 14.5 kb/s. TFO support is optional.

. 23: AMR <OPTION>

This is the BSC's pool that supports both full- and half-rate AMRspeech.

. 24: AMR/FR DATA <OPTION>

This is the BSC's pool that supports both full- and half-rate AMRspeech and full-rate data.

. 25: FR/EFR/AMR/FR DATA <OPTION>

This is the BSC's pool that supports both full- and enhanced full-ratespeech, AMR full- and half-rate speech, and full-rate data. TFOsupport is optional.

. 26: FR/EFR/AMR/FR DATA 14.5 <OPTION>

This is the BSC's pool that supports both full- and enhanced full-ratespeech, AMR full- and half-rate speech, and full-rate data. Themaximum radio interface data rate is 14.5 kb/s. TFO support isoptional.

. 27: DR/EFR/AMR/DR DATA <OPTION>

This is the BSC's pool that supports both full- and half rate speech,enhanced full-rate speech, AMR full- and half-rate speech, and bothfull- and half-rate data. TFO support is optional.

. 28: DR/EFR/AMR/DR DATA 14.5 <OPTION>



EDR DEFINE ROUTES

This is the BSC's pool that supports both full- and half-rate speech,enhanced full-rate speech, AMR full- and half-rate speech, and bothfull- and half-rate data. The maximum radio interface data rate is14.5 kb/s. TFO support is optional.

. 29: DR/EFR/AMR/DR DATA/HSCSD 2 <OPTION>

This is the BSC's pool that supports both full- and half-rate speech,enhanced full-rate speech, AMR full- and half-rate speech, both full-and half-rate data and the maximum of 2 full-rate channels on amultislot configuration. TFO support is optional.

. 30: DR/EFR/AMR/DATA/HSCSD 2/14.5 <OPTION>

This is the BSC's pool that supports both full- and half-rate speech,enhanced full-rate speech, AMR full- and half-rate speech, both full-and half-rate data and the maximum of 2 full-rate channels on amultislot configuration. The maximum radio interface data rate perchannel is 14.5 kb/s. TFO support is optional.

. 31: DR/EFR/AMR/DR DATA/HSCSD 4 <OPTION>

This is the BSC's pool that supports both full- and half-rate speech,enhanced full-rate speech, AMR full- and half-rate speech, both full-and half-rate data and the maximum of 4 full-rate channels on amultislot configuration. TFO support is optional.

. 32: DR/EFR/AMR/DATA/HSCSD 4/14.5 <OPTION>

This is the BSC's pool that supports both full- and half-rate speech,enhanced full-rate speech, AMR full- and half-rate speech, both full-and half-rate data and the maximum of 4 full-rate channels on amultislot configuration. The maximum radio interface data rate perchannel is 14.5 kb/s. TFO support is optional.

. 42: CTM + FR <OPTION>

This is the BSC's pool that supports CTM functionality and full-ratespeech. TFO support is optional.

. 43: CTM + EFR <OPTION>

This is the BSC's pool that supports CTM functionality and enhancedfull-rate speech. TFO support is optional.

. 44: CTM + FR/EFR <OPTION>

This is the BSC's pool that supports CTM functionality, full-ratespeech and enhanced full-rate speech. TFO support is optional.

. 45: CTM + DR/EFR <OPTION>



This is the BSC's pool that supports CTM functionality, both full- andhalf-rate speech and enhanced full-rate speech . TFO support isoptional.

. 46: CTM + AMR <OPTION>

This is the BSC's pool that supports CTM functionality and both full-and half-rate AMR speech .

. 47: CTM + FR/EFR/AMR <OPTION>

This is the BSC's pool that supports CTM functionality, both full- andenhanced full-rate speech and AMR full- and half-rate speech. TFOsupport is optional.

. 48: CTM + DR/EFR/AMR <OPTION>

This is the BSC's pool that supports CTM functionality, both full- andhalf rate speech, enhanced full-rate speech and AMR full- and half-rate speech. TFO support is optional.

route number

The number given to a route. The route number is obligatory. It is a decimalvalue from 300 to a maximum value that depends on system configuration.

Note

You can give one route number only once under the same BSC/UNC.This route number must not be used by another unlocked BSC/UNC. Ifyou wish to delete a route, set the route number to 0. A maximum of 16routes, including TFO routes, can be defined for every BSC/UNC.

pool TFO capability <option>

This parameter identifies whether the route is defined for TFO pool ornormal pool. The parameter can have the following values:

Value Description

Y TFO pool is used

N TFO pool is not used (default)



EDR DEFINE ROUTES

Tandem Free Operation (TFO) means the configuration of a voice ormultimedia call for which transcoders are physically present in thecommunication path, but transcoding functions are disabled, or partiallydisabled, in order to avoid multiple transcoding. The objective is to improvethe speech quality in mobile-to-mobile calls.

Examples 1. Set the full-rate pool with TFO of the BSC named BSCA2 to 543.

ZEDR:TYPE=BSC,NAME=BSCA2:1,543,Y;

2. Set the half-rate pool of the BSC number 137 to 650.

ZEDR:TYPE=BSC,NO=137:2,650;

3. Remove the full-rate pool with TFO from the BSC named BSCA2.

ZEDR:TYPE=BSC,NAME=BSCA2:1,0,Y;

4. Set the half-rate pool of the UNC number 200 to 2150.

ZEDR:TYPE=UNC,NO=200:2,2150;

Executionprintouts

The program outputs the BSC name, number, and routing values aftermodifications in CMU files have succeeded.

Command ZEDR:TYPE=BSC,NO=1345:1,502,Y; modifies the routingof the BSC number 1345. The output is as follows:

DX 200 DX220-LAB 2001-07-19 10:33:45

DEFINING ROUTES

BSC NAME .......................(NAME). :BSC18

BSC NUMBER .....................(NO)... :1345


1: FR ................................ :502

COMMAND EXECUTED

Command ZEDR:NAME=BSCA1:2,0; deletes the half-rate pool of theBSC named BSCA1. The output is as follows:

DX 200 DX220-LAB 2001-07-19 10:34:13

DEFINING ROUTES

BSC NAME .......................(NAME). :BSCA1

BSC NUMBER .....................(NO)... :743




2: HR ................................ : -

COMMAND EXECUTED

Command ZEDR:TYPE=UNC,NO=200:2,2150; modifies the half-ratepool of the UNC number 200. The output is as follows:

DX 200 DX220-LAB 2001-07-19 10:34:13

DEFINING ROUTES

UNC NAME .......................(NAME). :UNCA200

UNC NUMBER .....................(NO)... :200


2: HR ................................ :2150

COMMAND EXECUTED







EDR DEFINE ROUTES

EDL DEFINE SIGNALLING SYSTEMINFORMATIONFunction With this command you can define the signalling system information of a

BSC/UNC by giving the BSC/UNC name or number, signalling network,and signalling point code. You can define the optional BSSAP subsystemnumber. Use this command when the signalling network uses 14/24 bitsignalling point codes.

The commands in the SS7 network administration class are related to thiscommand. Once you have defined the SPC of the BSC/UNC with SS7network administration MMLs, add the corresponding SPC to the cellularradio network file with this command.

You can also define the SPC and SNC of the cellular network files beforecreating the corresponding SPC with the SS7 network administrationMMLs.

Parameters object identification: signalling network code, signalling point code: BSSAPsubsystem number <option>;

Syntax EDL: [ TYPE=<object type | BSC def> ],


NO=<object number> ):

<signalling network code>,

<signalling point code>:

[ SSN=<BSSAP subsystem number> <option> ];


TYPE: object type










NAME: object name



NO: object number




signalling network code

The Signalling Network Code (SNC) identifies the signalling network. It isobligatory. As its value, it can have one of the networks that have beendefined in the Signalling Connection Control Part (SCCP) of the exchange.If all signalling networks exist, the alternatives are:

Value Description

IN0 international network 0

IN1 international network 1

NA0 national network 0

NA1 national network 1

signalling point code

The Signalling Point Code (SPC) is the binary code uniquely identifying asignalling point in a signalling network. It is obligatory. The value can beentered as hexadecimal, decimal or, if allowed in the network in question,with hyphens between digits (for example, 0-5-0). The value rangedepends on the given signalling network:



Value Description

hexadecimal 0 ... 3FFF SPC for 14 bit signalling network

hexadecimal 0 ... FFFFFF SPC for 24 bit signalling network

SSN: BSSAP subsystem number <option>


SSN hexadecimal 10 ... FE BSSAP subsystem number <option>

This parameter identifies the subsystem by using the SCCP. The valuecan also be given as decimal. The maximum number of different SSNsunder one MSC/MSS is 10.

Examples 1. Set the SPC of the BSC named LONDON1 to 345, SNC to NA1, andSSN to 14.

ZEDL:TYPE=BSC,NAME=LONDON1:NA1,345:SSN=14;

2. Modify the SPC of the BSC number 201 to 0-5-0 and SNC to IN1.

ZEDL:TYPE=BSC,NO=201:IN1,0-5-0;

3. Set the SPC of the UNCP named UNCPLUS1 to 100, SNC to IN1,and SSN to 10.

ZEDL:TYPE=UNCP,NAME=UNCPLUS1:IN1,100:SSN=10;

Executionprintouts

The program outputs the BSC name, number, and signalling systeminformation after modifications in CMU files have succeeded.

Command ZEDL:TYPE=BSC,NO=1345:IN1,0-4-0; modifies the SPCof the BSC number 1345 to 0-4-0 and the SNC to IN1. The output is asfollows:

DX 200 DX220-LAB 2001-07-19 10:34:36

DEFINING SIGNALLING SYSTEM INFORMATION

BSC NAME .......................(NAME). :LEEDS

BSC NUMBER .....................(NO)... :1345

SIGNALLING NETWORK CODE ........(SNC).. :IN1

SIGNALLING POINT CODE ..........(SPC).. :20/0-004-0 (hex/dec)

COMMAND EXECUTED

Command ZEDL:TYPE=UNCP,NAME=UNCPLUS1:IN1,100:SSN=10;sets the SPC of the UNCP named UNCPLUS1 to 100, SNC to IN1, andSSN to 10. The output is as follows:




DX 200 DX220-LAB 2001-07-19 10:34:36

DEFINING SIGNALLING SYSTEM INFORMATION


UNC NUMBER .....................(NO)... :100

SIGNALLING NETWORK CODE ........(SNC).. :IN1

SIGNALLING POINT CODE ..........(SPC).. :100/0-032-0 (hex/dec)


COMMAND EXECUTED







EDM CHANGE CELL IDENTIFICATION METHODFunction With this command you can change the cell identification method of one or

more BSCs/UNCs by giving the BSC/UNC names or numbers and the cellidentification method.

Parameters object identification: cell identification method;

Syntax EDM: [ TYPE=<object type | BSC def> ],



( CGI |

CLI |

CI );


TYPE: object type






NAME: object name







NO: object number





cell identification method

This parameter defines the method that the MSC/MSS uses to identify acell in a BSC/UNC during a handover.

With the BSC or UNC the value may be one of the following:

Value Description

CGI CI + LAC + MNC + MCC

CLI CI + LAC

CI CI

Give one of the cell identification methods.

The abbreviations used above:

CGI= cell global identity

CI= cell identity


MNC= mobile network code

MCC= mobile country code

Examples 1. Change the cell identification method of the BSC namedBIRMINGHAM to CLI.

ZEDM:TYPE=BSC,NAME=BIRMINGHAM:CLI;

2. Change the cell identification method of the BSCs namedBRISTOL1 and BRISTOL2 to CGI.

ZEDM:TYPE=BSC,NAME=BRISTOL1&BRISTOL2:CGI;

3. Change the cell identification method of the UNC named UNCAINT1to CLI.



ZEDM:TYPE=UNC,NAME=UNCAINT1:CLI;

Executionprintouts

The program outputs the object name, number, and cell identificationmethod value after modifications in CMU files have succeeded.

Command ZEDM:TYPE=BSC,NO=2510:CI; modifies the cellidentification method of the BSC number 2510 to CI. The output is asfollows:

DX 200 DX220-LAB 2001-07-19 10:35:02

CHANGING CELL IDENTIFICATION METHOD

CELL IDENTIFICATION METHOD .....(CID).. :CI

BSC LIST :

GLASGOW 2510

COMMAND EXECUTED

Command ZEDM:TYPE=UNC,NAME=UNCAINT1:CLI; modifies the cellidentification method of the UNC named UNCAINT1 to CLI. The output isas follows:

DX 200 DX220-LAB 2001-07-19 10:35:02

CHANGING CELL IDENTIFICATION METHOD


UNC LIST :

UNCAINT1 10

COMMAND EXECUTED








EDP CHANGE PAGING METHODFunction With this command you can change the paging method of one or more

BSCs/UNCs by giving the BSC/UNC names or numbers and pagingmethod.

Parameters object identification: paging method;

Syntax EDP: [ TYPE=BSC/UNC/UNCP | BSC def ],



( CGI |

CLI |

LAI |

LAC |

ALL );


TYPE: object type






NAME: object name







NO: object number





paging method

This parameter defines the method that the MSC/MSS uses to identify thescope of a paging request.

With the BSC or UNC the value can be one of the following:

Value Description

CGI CI + LAC + MNC + MCC

CLI CI + LAC

LAI LAC + MNC + MCC

LAC LAC

ALL ALL CELLS IN BSC/UNC

Give one of the paging methods.

The abbreviations used above:

CGI= cell global identity

CI= cell identity




Examples 1. Change the paging method of the BSC named BSC2 to CGI.

ZEDP:TYPE=BSC,NAME=BSC2:CGI;



2. Change the paging method of the BSC numbers 235 and 2463 toALL.

ZEDP:TYPE=BSC,NO=235&2463:ALL;

3. Change the paging method of the UNCP named UNCPLUS1 to CGI.

ZEDP:TYPE=UNCP,NAME=UNCPLUS1:CGI;

Executionprintouts

The program outputs the object name, number, and paging method valueafter modifications in CMU files have succeeded.

Command ZEDP:TYPE=BSC,NAME=BSCA1&BSCA2:ALL; changes thepaging method of the BSCs named BSCA1 and BSCA2 to ALL. Theoutput is as follows:

DX 200 DX220-LAB 2000-07-19 10:35:46

CHANGING PAGING METHOD

PAGING METHOD ......................... :ALL

BSC LIST :

BSCA1 4076

BSCA2 4077

COMMAND EXECUTED

Command ZEDP:TYPE=UNCP,NAME=UNCPLUS1:CGI; changes thepaging method of the UNC named UNCPLUS1 to CGI. The output is asfollows:

DX 200 DX220-LAB 2000-07-19 10:35:46

CHANGING PAGING METHOD

PAGING METHOD ......................... :CGI

UNC LIST :

UNCPLUS1 1010

COMMAND EXECUTED








EDI CHANGE CHANNEL PRIORITYASSIGNMENT FUNCTION MODEFunction With this command you can change the channel priority assignment

function mode of one or more BSCs or UNCs by giving the BSC/UNCnames or numbers, and the function mode ON/OFF.

The radio channel assignment function operates so that the calls in line fora free radio channel are arranged in the priority order according to a calltype.

Parameters object identification: channel priority assignment function mode;

Syntax EDI: [ TYPE=<object type | BSC def> ],



( ON |

OFF );


TYPE: object type






NAME: object name



EDI CHANGE CHANNEL PRIORITY ASSIGNMENT FUNCTIONMODE




NO: object number





channel priority assignment function mode

Value Description

ON priority assignment function is ON

OFF priority assignment function is OFF

Give one of the function modes.

Examples 1. Change the priority assignment function mode of the BSC namedBSCO2 to ON.

ZEDI:TYPE=BSC,NAME=BSCO2:ON;

2. Change the priority assignment function mode of the BSCs namedHIGHW3 and HIGHW23 to ON.

ZEDI:TYPE=BSC,NAME=HIGHW3&HIGHW23:ON;

3. Change the priority assignment function mode of the UNC namedUNC1000 to ON.

ZEDI:TYPE=UNC,NAME=UNC1000:ON;

Executionprintouts

The program outputs the object name, number, and priority assignmentfunction value after modifications in CMU files have succeeded.

Command ZEDI:TYPE=BSC,NO=745:ON; changes the priorityassignment function mode of the BSC number 745 to ON. The output is asfollows:



DX 200 DX220-LAB 2001-07-19 10:35:56

CHANGING CHANNEL PRIORITY ASSIGNMENT FUNCTION MODE

PRIORITY ASSIGNMENT FUNCTION .......... :ON

BSC LIST :

NORWICH 745

COMMAND EXECUTED

Command ZEDI:TYPE=UNC,NAME=UNC1000:ON; changes the priorityassignment function mode of the UNC named UNC1000 to ON. Theoutput is as follows:

DX 200 DX220-LAB 2001-07-19 10:35:56

CHANGING CHANNEL PRIORITY ASSIGNMENT FUNCTION MODE

PRIORITY ASSIGNMENT FUNCTION .......... :ON

UNC LIST :

UNC1000 1000

COMMAND EXECUTED







EDI CHANGE CHANNEL PRIORITY ASSIGNMENT FUNCTIONMODE

EDH CHANGE REVERSED CIRCUITALLOCATION FUNCTION MODE <OPTION>Function With this command you can change the reversed A -interface circuit

allocation function mode of one or more BSCs/UNCs (A-interface) bygiving the BSC/UNC names or numbers, and the function mode ON/OFF.

When the circuit allocation by BSS is in use (ON), only the route of the 'NotApplicable' pool can be defined. The routes of the other pools can bedeleted by using the EDR command. If the configuration is set correctly, theonly pool that should be seen with the EDO command is the N/A poolbecause circuit pools are not relevant in the case of reversed allocation.

When the circuit allocation by BSS is out of use (OFF), all circuit pools canbe modified and viewed, if corresponding options are in use.

The state of a BSC/UNC (A-interface) must be LOCKED, when thefunction mode of the circuit allocation by BSS is changed.

Note

It is not possible to execute this command if UNCP (A+ -interface) is inquestion.

Parameters object identification: circuit allocation by BSS;

Syntax EDH: [ TYPE=<object type | BSC def> ],



( ON |

OFF );


TYPE: object type



EDH CHANGE REVERSED CIRCUIT ALLOCATION FUNCTIONMODE





NAME: object name



The character '&' can be used to give several BSC/UNC names.

NO: object number



The character '&' can be used to give several BSC/UNC numbers.


circuit allocation by BSS

Value Description

ON circuit allocation by BSS is ON

OFF circuit allocation by BSS is OFF

Give one of the function modes.

Examples 1. Change the reversed circuit allocation function mode of the BSCnamed BSCO2 to ON.

ZEDH:NAME=BSCO2:ON;

2. Change the reversed circuit allocation function mode of the BSCnumbers 837 and 2463 to OFF.

ZEDH:NO=837&2463:OFF;



3. Change the reversed circuit allocation function mode of the BSCsnamed HIGHW3 and HIGHW23 to ON.

ZEDH:NAME=HIGHW3&HIGHW23:ON;

4. Change the reversed circuit allocation function mode of the UNCnamed UNC1000 to ON.

ZEDH:TYPE=UNC,NAME=UNC1000:ON;

Executionprintouts

The program outputs the BSC/UNC name, number, and reversed circuitallocation function mode value after modifications in CMU files havesucceeded.

Command ZEDH:NO=745:ON; changes the reversed circuit allocationfunction mode of the BSC number 745 to ON. The output is as follows:

DX 200 DX220-LAB 2001-07-19 10:36:18

CHANGING REVERSED CIRCUIT ALLOCATION FUNCTION MODE

CIRCUIT ALLOCATION BY BSS ............. :ON

BSC LIST :

BSCO2 745

COMMAND EXECUTED

Command ZEDH:NAME=BSCA1&BSCA2:OFF; modifies the reversedcircuit allocation function modes of the BSCs named BSCA1 and BSCA2to OFF. The output is as follows:

DX 200 DX220-LAB 2001-07-19 10:36:37



BSC LIST :

BSCA1 837

BSCA2 2463

COMMAND EXECUTED

Command ZEDH:TYPE=UNC,NAME=UNC1000:ON; changes the reversedcircuit allocation function mode of the UNC named UNC1000 to ON. Theoutput is as follows:



EDH CHANGE REVERSED CIRCUIT ALLOCATION FUNCTIONMODE

DX 200 DX220-LAB 2001-07-19 10:36:18


CIRCUIT ALLOCATION BY BSS ............. :ON

UNC LIST :

UNC1000 1000

COMMAND EXECUTED







EDN MODIFY NAME OF BSSAP VERSIONFunction With this command you can modify the name of a BSSAP version.

Parameters BSSAP version: name of BSSAP version;

Syntax EDN: <BSSAP version>:

<name of BSSAP version>;


BSSAP version

There are 50 prepacked BSSAP service profile descriptions in an MSC.These service profile descriptions define the data combinations of BSSfunctions and the values of A-interface timers and parameters. A BSSAPservice profile description is identified with the unique number calledBSSAP version. The BSSAP version is an obligatory parameter. It is adecimal between 1 and 49.

You can modify the parameters included in a prepacked BSSAP versionwith the EDT command.

name of BSSAP version

The name of the BSSAP version is also obligatory. The name is a textstring of 1 to 15 characters.

Examples 1. Modify the name of the BSSAP version 25 to TESTVERSION.

ZEDN:25:TESTVERSION;

Executionprintouts

The program outputs the BSSAP version identification and modified nameof the BSSAP version after the modification in the CMU files hassucceeded.

Command ZEDN:26:TESTVERSION2; modifies the name of BSSAPversion 26 to TESTVERSION2. The output is as follows:



EDN MODIFY NAME OF BSSAP VERSION

DX 200 DX220-LAB 2001-07-19 10:37:25

MODIFYING NAME OF BSSAP VERSION


BSSAP NAME .................(VERNAME).. :TESTVERSION2

COMMAND EXECUTED







EDT MODIFY INFORMATION ON BSSAPVERSIONFunction With this command you can modify the BSS functional parameters and A

interface timers and parameters included in a BSSAP version. Give theBSSAP versions or names of the BSSAP versions you want to modify.

Parameters BSSAP version, name of BSSAP version: parameter type, parameterindex, parameter value;

Syntax EDT: ( VER=<BSSAP version>... |

VERNAME=<name of BSSAP version>... ):

<parameter type>,

<parameter index>,

<parameter value>;


BSSAP version

There are 50 prepacked BSSAP service profile descriptions in an MSC.These service profile descriptions define the data combinations of BSSfunctions and values of A interface timers and parameters. A BSSAPservice profile description is identified with the unique number calledBSSAP version.

When you create a new BSC, the system automatically attaches it toBSSAP version 15. If you use reference BSC, the BSSAP versionparameter is copied to the new BSC.

The BSSAP version is a decimal between 1 and 49. You can give severalBSSAP versions by using characters '&' and '&&'.

name of BSSAP version

The name of the BSSAP version is a text string of 1 to 15 characters. Youcan give several names by using the character '&'.




Give either the BSSAP version or the version name, but not both.

parameter type

The parameters of the BSSAP version are divided into three types. Withthis parameter you can define which parameter type you want to modify.The parameter type is obligatory. It can have one of the following values:

Value Description

T A interface timer

P A interface parameter

F BSS functional parameter

parameter index

Every parameter in the 'type' category has been indexed, so that you referto the parameters by giving their indexes instead of their names. Theparameter index is obligatory. With BSS functional parameters the index isa decimal 1–n, and with A interface timers and parameters 0–n. Themaximum value n of the index depends on the type of the parameter youwant to modify.

parameter value

The value of the BSS functional parameter is obligatory. If you do not givea value to an A interface timer or parameter, the default value is used. Thevalue range depends on the parameter you want to modify.

The parameters, their corresponding indexes, and value ranges are listedbelow.

In the timers description, start descripes timer initiation situation, normalstop descripes timer stop or restart situation, expire descripes resultingaction when timer expires.

Type T, A interface timers:

. 0: Global reset guard period in the MSC

The range of values is from 30 to 150; the default value is 50 (=5 s).Start : Receiving of Reset -message.Normal Stop : -Expiry : Sending of Reset Ack -message.

. 1: Overload timer (short) in the MSC



The range of values is from 10 to 1200; the default value is 100 (=10s).Start : Receiving of Overload -message from the BSC. Overloadtimer T5.Normal Stop : -Expiry : During T5 all incoming Overload -messages are ignored.

. 2: Overload timer (long) in the MSC

The range of values is from 20 to 1200; the default value is 300 (=30s).Start : Receiving of Overload -message from the BSC. Overloadtimer T6.Normal Stop : Receiving of Overload -message from the BSC (timeris re-started).Expiry : Raise the traffic with one overload traffic step (10%).

. 3: Time of receipt of RESET CIRCUIT ACK

The range of values is from 50 to 200; the default value is 100 (=10s).Start : Sending of Reset Circuit -message.Normal Stop : Receiving of Reset Circuit Ack -message.Expiry : Reset Circuit is repeated. When the max number ofrepetitions has been made, Alarm 2773 is raised. Concerned circuitremains in BA-SY state.

. 4: Time of receipt of RESET ACK at MSC

The range of values is from 300 to 1200; the default value is 600(=60 s).Start : Sending of Reset -message.Normal Stop : Receiving of Reset Ack -message.Expiry : Alarm 1560 is set. Reset is repeated. When the max numberof repetitions has been made, Alarm 1560 is cancelled and Alarm2772 is raised.

. 5: Guard period after subsystem prohibited

The range of values is from 10 to 1500; the default value is 290 (=29s).Start : Receiving of SSP.Normal Stop : Receiving of SSA.Expiry : Internal resource releasing towards concerned subsystem(BSC) i.e. Call clearings (clear code A08H).

. 6: Guard period after subsystem available




The range of values is from 0 to 1500; the default value is 0 s.Start : Receiving of SSA.Normal Stop : Receiving of SSP.Expiry : Global Reset -procedure is started towards concernedsubsystem (BSC).

. 7: Overload timer for the MTP congestion

The range of values is from 20 to 300; the default value is 180 (=18s).Start : Receiving of N-PCSTATE SCCP primitive telling thecongestion of remote SP.Normal Stop : Receiving of N-PCSTATE SCCP primitive telling theremote SP is OK.Expiry : Reduce the traffic with one overload traffic step (10%).

. 8: Time of receipt of CIPHER MODE COMPLETE

The range of values is from 50 to 200; the default value is 150 (=15s).Start : Sending of Ciphering Mode Command.Normal Stop : Receiving of Ciphering Mode Complete.Expiry : Alarm 1653 is set. Call clearing (clear code B15H).

. 9: Time of receipt of ASSIGNMENT COMPLETE

The range of values is from 50 to 300; the default value is 150 (=15s).Start : Sending of Assignment Request.Normal Stop : Receiving of Assignment Complete.Expiry : Alarm 1653 is set. Call clearing (clear code B1AH).

. 10: The maximum queueing time after QUEUEING INDICATION inassignment (t_queueing_c)

The range of values is from 100 to 300; the default value is 200 (=20s).Start : Receiving of Queueing Indication.Normal Stop : Receiving of Assignment Complete.Expiry : Alarm 1653 is set. Call clearing (clear code B1AH).

. 11: Time of receipt of CLEAR COMPLETE

The range of values is from 50 to 300; the default value is 150 (=15s).Start : Sending of Clear Command.Normal Stop : Receiving of Clear Complete.Expiry : After 1st expiry Clear Command is repeated, after 2nd expirycontinue clearing (sending of RLSD).

. 12: Time of receipt of CLEAR COMPLETE in handover



The range of values is from 50 to 300; the default value is 150 (=15s).Start : Sending of Clear Command.Normal Stop : Receiving of Clear Complete.Expiry : After 1st expiry Clear Command is repeated, after 2nd expirycontinue clearing (sending of RLSD).

. 13: Time of receipt of HANDOVER REQUEST ACK

The range of values is from 20 to 200; the default value is 100 (=10s).Start : Sending of Handover Request.Normal Stop : Receiving of Handover Request Ack.Expiry : Sending of RLSD to target BSC, HND RQD REJ to sourceBSC (if requested).

. 14: Time of receipt of HANDOVER COMPLETE (T3103) in handover

The range of values is from 20 to 300; the default value is 150 (=15s).Start : Receiving of Handover Request Ack.Normal Stop : Receiving of Handover Complete.Expiry : Alarm 1653 is set. Call clearing (clear code B14H).

. 15: The maximum queueing time after QUEUEING INDICATION inhandover

The range of values is from 100 to 300; the default value is 200 (=20s).Start : Receiving of Queueing Indication.Normal Stop : Receiving of Handover Request Ack.Expiry : Sending of RLSD to target BSC, HND RQD REJ to sourceBSC (if requested).

. 16: Time after traffic reason handover during which the MS isrefused new handovers

The range of values is from 0 to 600; the default value is 150 (=15 s).Start : Set after Traffic Reason -handover. During this timer newhandover attempts are not allowed to avoid ping-pong handovers.Normal Stop : -Expiry : New handovers are allowed again.

. 17: The maximum waiting time of RE-ESTABLISHMENT REQUEST

The range of values is from 10 to 300; the default value is 100 (=10s).Start : Receiving of Clear Request.Normal Stop : Receiving of Re-Establishment Request.Expiry : Call clearing (clear code B13H or B1BH).




. 18: The maximum waiting time of CLASSMARK UPDATE

The range of values is from 10 to 300; the default value is 50 (=5 s).Timer is not used, because Classmark Request -procedure is notsupported (=is not needed).

. 19: The maximum waiting time of POSITION TRACKINGINDICATION <OPTION>

The range of values is from 10 to 30; the default value is 20 (=2 s).This is the maximum time that the original MSC waits for locationinformation from the second MSC after an inter-MSC handover. Thelocation information specifies the cell under the second MSC fromwhich the emergency call is made.

Type P, A interface parameters:

. 0: The maximum repeat count of BSS global reset message

The range of values is from 0 to 65535; the default value is 10.

. 1: The maximum number of BTSs, which can simultaneously havean HO candidate enquiry procedure in progress in one BSS


. 2: The maximum number of BTSs, which can simultaneously have aperiodic resource indication method in one BSS


. 3: The maximum repeat count of resource request messages afterthe resource indication method has been set


. 4: The maximum number of cells, which are taken into considerationin the cell list of the source BSC in a handover


. 5: The mode of action, if there is a conflict between the circuit poolinformation of the MSC and the circuit pool information of the BSC


. 6: The maximum repeat count of the circuit reset message


. 7: The maximum repeat count of the change circuit message




Type F, BSS functional parameters:

A BSS functional parameter can have one of the following values:

Value Description

0 BSS does not support functional parameter

1 BSS supports functional parameter

. 1: BSC reset is (/is not) supported

Defines the ability of the BSC to handle the global reset proceduredefined in GSM 08.08, section 3.1.4.1.

. 2: BSC circuit reset is (/is not) supported

Defines the ability of the BSC to handle the reset circuit proceduredefined in GSM 08.08, section 3.1.4.2.

. 3: Blocking information is (/is not) lost in the incoming BSC reset

Defines whether or not blocking information of circuits is reset whenthe RESET message is received from the BSC.

. 4: Blocking information is (/is not) lost in an outgoing BSC reset

Defines whether or not blocking information of circuits is reset whenthe RESET message is sent to the BSC.

. 5: Block in an unknown CIC is (/is not) responded to

Defines how an unknown Circuit Identity Code (CIC) in the receivedBLOCK message is handled.

. 6: Circuit reset message to the unknown CIC is (/is not) responded to

Defines how an unknown circuit identity code in the receivedCIRCUIT RESET message is handled.

. 7: SCCP subsystem prohibited during BSS reset is (/is not) handled

If the Signalling Connection Control Part (SCCP) BSSAP'subsystem prohibited' information is handled during a BSS reset,the reset procedure is interrupted and restarted when 'subsystemavailable' information is received.

. 8: Mobile-originated short message is (/is not) supported

Must be defined as 'not supported' if you want to prevent the mobile-originated SMS.<OPTION>




. 9: Mobile-terminated short message is (/is not) supported

Must be defined as 'not supported' if you want to prevent the mobile-terminated SMS.<OPTION>

. 10: Data services are (/are not) supported

Must be defined as 'not supported' if the BSS does not support dataservices.

. 11: SDCCH handover is (/is not) supported

Defines whether control channel handovers are supported or not.

. 12: Information in SCCP CC message is (/is not) supported

Defines whether transfer layer 3 messages are supported in the'SCCP Connection Confirmed' message or not.

. 13: Information in SCCP CREF message is (/is not) supported

Defines whether transfer layer 3 messages are supported in the'SCCP Connection Refused' message or not.

. 14: Information in SCCP RLSD message is (/is not) supported

Defines if transfer layer 3 messages are supported in the 'SCCPReleased' message or not.

. 15: Tracing is (/is not) supported

Defines if the BSC supports at least the ph1 trace invocation definedin phase 1 GSM 08.08, section 3.1.11 (see also parameter 34).

. 16: Handover candidate enquiry is (/is not) supported

Defines the ability of the BSC to handle the Handover CandidateEnquiry Procedure defined in GSM 08.08, section 3.1.8.

. 17: Resource indication is (/is not) supported

Defines the ability of the BSC to handle the Resource IndicationProcedure defined in GSM 08.08, section 3.1.3.

. 18: BSC overload is (/is not) supported

Defines the ability of the BSC to handle the OVERLOAD messagedefined in GSM 08.08, section 3.1.12.2.

. 19: Cause field is (/is not) used in a handover request message

Defines the ability of the BSC to handle the cause field in theHANDOVER REQUEST message defined in GSM 08.08, section3.2.1.17.



. 20: A5_2 ciphering is (/is not) supported.<OPTION>

Defines the BSS's support for ciphering algorithm A5/2.

. 21: Multiple ciphering is (/is not) supported.

Defines the BSS's support for multiple ciphering algorithms in theCIPHER MODE COMMAND message.

. 22: Cipher_resp_mode field is (/is not) mandatory in the ciph_cmd

Defines whether or not the cipher response mode field is mandatoryin the CIPHER MODE COMMAND message defined in GSM 08.08,section 3.2.1.30.

. 23: IMEI request in cipher_mode_command is (/is not) supported

Defines whether or not the IMEI request is supported in the CIPHERMODE COMMAND message defined in GSM 08.08, section3.2.1.30.

. 24: Unequipped_circuit message is (/is not) supported

Defines the ability of the BSC to handle the UNEQUIPPED CIRCUITmessage defined in GSM 08.08, section 3.1.19.6.

. 25: Radio channel information is included in the DLCI

Defines the ability of the BSC to handle radio channel informationincluded in the DLCI defined in GSM 08.06, sections 6.3.2 and3.1.4.1.

. 26: Two bytes length of Layer 3 header information field is (/is not)supported

Defines the ability of the BSC to handle the two bytes of the Layer 3header information field defined in GSM 08.08, section 3.2.2.9.

. 27: Channel_needed field is (/is not) supported in paging

Defines the ability of the BSC to handle the channel_needed field inpaging defined in GSM 08.08, section 3.1.10.

. 28: Classmark request operation is (/is not) supported

Note

This feature is not supported in an MSC.

. 29: Confusion message is (/is not) supported




Defines the ability of the BSC to handle the CONFUSION messagedefined in GSM 08.08, section 3.2.1.45.

. 30: Indicates whether or not the BSC is capable of handling 6 kbit/sintermediate-rate on the radio interface for full-rate TCH for non-transparent data services.

. 31: Indicates whether or not the BSC is capable of handlingHANDOVER and CIPHERING simultaneously.

. 32: Classmark_3 information element is (/is not) supported

Defines the ability of the BSC to handle the Classmark_3 field in theHANDOVER REQUEST message defined in GSM 08.08, section3.2.1.8.

. 33: Paging method 'all cells on BSS' is (/is not) supported in search

Defines if the 'all cells' paging method is used in case of a search.

. 34: Indicates whether MSC_INVOKE_TRACE is (/is not) supported

Defines the BSC's support for phase 2 MSC INVOKE TRACEmessage defined in GSM 08.08 section 3.2.1.27.

. 35: Half rate code points are (/are not) supported

Defines the BSC's support for the half-rate code points defined inGSM 08.08.

. 36: Re-establishment is (/is not) supported

Must be defined as 'supported' if the re-establishment procedure isin use in the BSC area.

. 37: Current channel information element in HANDOVER REQUESTis (/is not) supported

Defines the BSC's support for the current channel field in theHANDOVER REQUEST message defined in GSM 08.08, section3.2.1.17.

. 38: Cell identifier information element in HANDOVER COMMAND is(/is not) supported

Defines the BSC's support for the cell identifier information elementin the HANDOVER COMMAND message defined in GSM 08.08,section 3.2.1.11.

. 39: Multiple voice coder is (/is not) supported

. 40: Indicates whether or not the bytes of the CIC are sent in areversed order to the BSC.



. 41: Load indication message is (/is not) supported

. 42: Indicates if the maximum of 2 traffic channels can be used in theHSCSD service <OPTION>.

. 43: Indicates if the maximum of 4 traffic channels can be used in theHSCSD service <OPTION>.

. 44: Indicates if the 14.4 kbit/s radio interface data rate is (/is not)supported <OPTION>.

. 45: Indicates whether the position tracking of emergency calls afterinter-MSC handover is supported or not <OPTION>.

The original MSC requests location information that specifies the cellunder the second MSC from which the emergency call is made. Theresponse of the second MSC consists of position trackinginformation with which the call can be routed to a correct serviceelement.

. 46: Indicates whether the directed retry handover without directedretry cause is allowed or not.

The directed retry is the process of assigning a mobile station to atraffic channel in the cell other than the serving cell due to thecongestion. When the parameter is supported, the MSC accepts thedirected retry handover request made by the BSC also with othercauses than the directed retry cause. If the parameter is notsupported, the directed retry handover request is accepted by theMSC only with the directed retry cause.

. 47: Indicates whether or not the circuit group block and circuit groupunblock messages are supported between the BSS and the MSC<OPTION>.

The circuit group block message is used to indicate that a set ofterrestrial resources must be remotely blocked at the receivingnetwork element, and cannot therefore be used by the traffic. Thecircuit group unblock message is used to indicate that a set ofblocked terrestrial resources may be returned to the service. Whenthis parameter is set on, the circuit group block/unblock messagesare supported.

. 48: Indicates whether information passing transparently from oldBSS to new BSS via the MSC is supported or not.

. 49: Indicates whether Enhanced Circuit Switched Data rates (ECSD)are supported or not in the BSC <OPTION>.

. 50: Indicates whether AMR speech codec is supported or not in theBSC <OPTION>.




. 51: Indicates whether location positioning services are supported ornot in the BSC <OPTION>.

. 52: Indicates whether localised service areas (SOLSA) aresupported or not in the BSC <OPTION>.

. 53: Indicates whether RANAP extensions are supported or not<OPTION>.

Identifies if RANAP protocol-related extensions can be used. Forexample, RNC_id field in Handover_Request message.

. 54: Indicates whether COMMON_ID information is supported or not.

Identifies if Common Id message or Common Id message field canbe used. Common Id is used to identify mobile equipment and/ormobile subscriber. Common Id field is possible, for example, inHandover_Request message.

. 55: Indicates whether LAYER 3 HEADER INFORMATION NOTSUPPORTED is supported or not.

Identifies whether layer 3 header info is not allowed to be sent totarget.

. 56: Indicates whether SERVICE HANDOVER is supported or not.

Identifies whether service handover is allowed to be sent to target.

. 57: Indicates whether SERVING SAI is supported or not <OPTION>.

Identifies whether serving SAI can be used in handover requestmessage.

. 58: Indicates whether MSC RELEASE INFORMATION is supportedor not.

The purpose of this BSSAP bit is to indicate whether the BSS is ableto inform the mobile station about the release of the MSC.

. 59: Indicates whether MAP CODEC NEGOTIATION is supported ornot.

The purpose of this BSSAP bit is to indicate if it is possible to usecodec negotiation towards the target MSS through MAP.

. 60: Indicates whether Cellular Text Telephone Modem (CTM)functionality is supported or not. <OPTION>

The purpose of this BSSAP bit is to indicate if BSS supports texttelephony calls.



. 61: Indicates whether MODIFIED RE-ESTABLISHMENT RELEASESEQUENCE is supported or not.

The purpose of this BSSAP bit is to define the method of releasingthe source side resources in the call re-establishment functionality. Ifthis parameter is set, the SCCP level release (RLSD) is triggered bythe BSSMAP Clear Complete —message.Without setting thisparameter the SCCP level release (RLSD) is optimized by sending itimmediately after the BSSMAP Clear Command —message.

. 62: Indicates whether A5/3 ciphering is supported or not.<OPTION>

The purpose of this BSSAP bit is to indicate if BSS supports A5/3ciphering algorithm.

Examples 1. Modify the BSS functional parameter corresponding to index 3 of theBSSAP version 9 to YES.

ZEDT:VER=9:F,3,1;

2. Modify the A interface timer corresponding to index 12 of BSSAPversions 5 and 30 to 20 s.

ZEDT:VER=5&30:T,12,200;

3. Modify the A interface parameter of three consecutive BSSAPversions, the first of which has identification 11, to 23. Thecorresponding index for the modified parameter is 2.

ZEDT:VER=11&&13:P,2,23;

4. Modify information on BSSAP version 26, so that the default value isset to the A interface timer corresponding to index 7.

ZEDT:VER=26:T,7;

Executionprintouts

The program outputs the BSSAP version identification and the value of themodified parameter after modifications in the CMU files have succeeded.

Command ZEDT:VER=7:F,1,1; changes the BSS functional parametercorresponding to index 1 to YES. The output is as follows:

DX 200 DX220-LAB 2000-07-19 10:37:42

MODIFYING INFORMATION ON BSSAP VERSION

1: BSC RESET SUPPORTED ................................. :YES

BSSAP VERSION:

7 VERSION7

COMMAND EXECUTED




Command ZEDT:VER=1&&4:T,0,90; modifies the value of the Ainterface timer corresponding to index 0 to 90 (9 s). The modification ismade for four consecutive BSSAP versions, the first of which hasidentification 1. The output is as follows:

DX 200 DX220-LAB 2000-07-19 10:37:58


0: GLOBAL RST QUARD PERIOD AT MSC ...................... :90 x 100 msec

BSSAP VERSION:

1 VERSION1

2 VERSION2

3 VERSION3

4 VERSION4

COMMAND EXECUTED

Command ZEDT:VER=5:P,0,; sets a default value to the A interfaceparameter corresponding to index 0. The modification is made for BSSAPversion 5. The output is as follows:

DX 200 DX220-LAB 2000-07-19 10:38:13


0: MAX REPEAT CNT OF BSS GLOB RST ...................... :10

BSSAP VERSION:

5 VERSION5

COMMAND EXECUTED







EDV MODIFY VERSION OF BSSAPFunction With this command you can modify the BSSAP version of one or more

BSCs/UNCs.

When you create a new BSC/UNC, the system automatically attaches it toBSSAP version 15. If you use reference BSC/UNC, the values ofreference BSC/UNC parameters are copied. When you wish to change theBSSAP version of a BSC/UNC, give the BSC/UNC names or numbers andBSSAP version value.

Parameters Object identification: BSSAP version;

Syntax EDV: [ TYPE=<object type | BSC def> ],



<BSSAP version>;


TYPE: object type






NAME: object name






NO: object number




BSSAP version

There are 50 prepacked BSSAP service profile descriptions in an MSC.These service profile descriptions define the data combinations of BSSfunctions and the values of A interface timers and parameters. A BSSAPservice profile description is identified with the unique number calledBSSAP version. The BSSAP version is obligatory. It is a decimal between1 and 49.


Examples 1. Modify the BSSAP version of the BSC named BSCO2 to 3.

ZEDV:TYPE=BSC,NAME=BSCO2:3;

2. Modify the BSSAP version of the BSCs named HIGHW3 andHIGHW23 to 11.

ZEDV:NAME=HIGHW3&HIGHW23:11;

3. Modify the BSSAP version of the UNCP named UNC1000 to 22.

ZEDV:TYPE=UNCP,NAME=UNC1000:22;

Executionprintouts

The program outputs the object name, number, and new BSSAP versionvalue after modifications in CMU files have succeeded.

Command ZEDV:TYPE=BSC,NO=1280:4; modifies the BSSAP versionof the BSC 1280 to 4. The output is as follows:

DX 200 DX220-LAB 2001-07-19 10:38:26

MODIFYING VERSION OF BSSAP




BSC LIST :

BSC18 1280

COMMAND EXECUTED

Command ZEDV:TYPE=UNCP,NAME=UNC1000:22; modifies the BSSAPversion of the UNC named UNC1000 to 22. The output is as follows:

DX 200 DX220-LAB 2001-07-19 10:38:26

MODIFYING VERSION OF BSSAP


UNC LIST :

UNC1000 1000

COMMAND EXECUTED








EDG MODIFY CELLULAR NETWORKCONTROLLER PARAMETERS <OPTION>Function With this command you can modify the parameters of one or more UNCs

by giving the UNCP names or numbers, and the parameter information.This command includes parameters only for UNC with A+ -interface, socommand cannot be given for other type of objects.

Parameters object identification: object parameters;

Syntax EDG: ( NAME=<object name>... |


( UPD = <user plane destination index> |

NUPD = <user plane destination name> );


NAME : object name


NAME text string of 1 to 10 characters UNC name


NO: object number


NO decimal from 1 to 4095 UNC number





EDG MODIFY CELLULAR NETWORK CONTROLLERPARAMETERS

UPD: user plane destination index


UPD decimal number from 0 to 999 the index of a user plane destination

User plane destination must be created before attaching it to a UNC. Userplane destinations can be handled with the commands of User PlaneTopology Data Handling, JF Command Group. The UPD is only definablefor a UNC with A+ -interface.

The UPD and NUPD are alternative parameters.

NUPD: user plane destination name


NUPD text string of 1 to 15 characters the name of a user planedestination

User plane destination must be created before attaching it to a UNC. Userplane destinations can be handled with the commands of User PlaneTopology Data Handling, JF Command Group. The user plane destinationis only definable for a UNC with A+ -interface.


Examples 1. Change the user plane destination of the UNC with A+ -interfacenamed UNCPLUS1 to 2.

ZEDG:NAME=UNCPLUS1:UPD=2;

2. Change the user plane destination of the UNC with A+ -interfacenumbers 200&201 to UPD9.

ZEDG:NO=200&201:UPDNAME=UPD9;

Executionprintouts

The program outputs the object name, number, and user plane destinationvalue after the modifications in the CMU files have succeeded.

Command ZEDG:NO=200&201:UPDNAME=UPD9; modifies the userplane destination of the UNC numbers 200&201 to UPD9. The output is asfollows:

DX 200 DX220-LAB 2001-07-19 10:35:02

MODIFY CELLULAR NETWORK CONTROLLER PARAMETERS



USER PLANE DESTINATION INDEX ...(UPD).. :9

USER PLANE DESTINATION NAME ....(NUPD). :UPD9

UNC LIST :

UNCPLUS1 200

UNCPLUS2 201

COMMAND EXECUTED







EDG MODIFY CELLULAR NETWORK CONTROLLERPARAMETERS

EDB OUTPUT INFORMATION ON BSSAPVERSIONFunction With this command you can output BSSAP version-specific information.

Such information includes the BSS functional parameters, A interfacetimers and parameters, as well as a list of the logical BSCs, a list of thelogical UNCs and network LAs attached to the BSSAP version.

You can also output information on the BSSAP version of a specific BSC/UNC or BSC/UNC group by giving the BSC/UNC names or numbers. Youcan output the desired information group by identifying it in the command.

Parameters BSSAP version identification: information group;

Syntax EDB: [ VER=<BSSAP version>... |

VERNAME=<name of BSSAP version>... ] |

[ [ TYPE=<object type | BSC def> ],

NAME=<object name>... |

NO=<object number>... |

<all VER> def ]:

[ <information group | ALL> def ];


VER: BSSAPversion


VER decimal from 0 to 49 BSSAP version

There are 50 prepacked BSSAP service profile descriptions in an MSC.These service profile descriptions define the data combinations of BSSfunctions and values of A -interface timers and parameters. A BSSAPservice profile description is identified with the unique number calledBSSAP version.





VERNAME: name of BSSAP version


VERNAME text string of 1 to 15 characters name of BSSAP version

TYPE: object type






NAME: object name



NO: object number



Give either VER, VERNAME, TYPE and NAME or NO, or NAME or NO. Ifparameter TYPE is not given but NAME or NO is given, the default value isBSC. You can give several BSSAP versions and names by usingcharacters '&' and '&&' in the version, and '&' in the version name. You canalso give several BSC/UNC numbers and names by using characters '&'and '&&' in the number, and '&' in the name. If you do not give any of theparameters, information on all BSSAP versions is displayed as default.

information group



With this parameter you can choose the type of information you wish toview. The purpose of the parameter is to make it easier to find theinformation you want. The names of the information groups are:

Value Description

FUN BSS functional parameters

TIM A interface timers

PAR A interface parameters

BSC list of the logical BSCs attached to a BSSAP version

UNC list of the logical UNCs with A -interface attached to a BSSAP version <option>

UNCP list of the logical UNCs with A+ -interface attached to a BSSAP version <option>

NLA list of the network LAs attached to a BSSAP version

ALL all information on a BSSAP version (default)

Examples 1. Output all information on BSSAP version 3.

ZEDB:VER=3;

2. Output all information on the BSSAP version of the BSC namedOXFORD.

ZEDB:TYPE=BSC,NAME=OXFORD:ALL;

3. Output the BSS functional parameters of BSSAP version 1.

ZEDB:VER=1:FUN;

4. Output the A interface timers of five consecutive BSCs, the firstnumber being 201.

ZEDB:TYPE=BSC,NO=201&&205:TIM;

5. Output all information on all BSSAP versions.

ZEDB; or EDB::ALL;

6. Output list of the logical UNCs attached to a BSSAP version of theUNC named UNC1000.

ZEDB:TYPE=UNC,NAME=UNC1000:UNC;

Executionprintouts

The program displays desired information on the BSSAP version (BSSfunctional parameters, A interface timers or parameters, a list of the logicalBSCs or network LAs attached to the BSSAP version, or all theseinformation), and also the object name and number if you give thecommand with one of these parameters.




Command ZEDB:TYPE=BSC,NAME=ABERDEEN:FUN; outputs the BSSfunctional parameters of the BSC named ABERDEEN. The output is asfollows:

DX 200 DX220-LAB 2001-07-19 10:39:02

OUTPUTTING INFORMATION ON BSSAP VERSION

BSC NAME .......................(NAME). :ABERDEEN

BSC NUMBER .....................(NO)... :245


BSSAP NAME .................(VERNAME).. :VERSION23

1: BSC RESET SUPPORTED ................................. :NO

2: BSC CIRCUIT RESET SUPPORTED ......................... :NO

3: BSC's BLOCKING INFO LOST IN INCOMING RESET .......... :YES

4: BSC's BLOCKING INFO LOST IN OUTGOING RESET .......... :YES

5: UNKNOWN CIC BLOCK RESPONDED ......................... :NO

6: UNKNOWN CIRCUIT RESET RESPONDED ..................... :NO

7: SCCP SSP DURING BSC RESET SUPPORTED ................. :YES

8: MOBILE ORIGINATED SMS SUPPORTED ..................... :NO

9: MOBILE TERMINATED SMS SUPPORTED ..................... :NO

10: DATA SERVICES SUPPORTED ............................. :NO

11: SDCCH HANDOVER SUPPORTED ............................ :NO

12: INFO IN SCCP CC-MESSAGE SUPPORTED ................... :NO

13: INFO IN SCCP CREF-MESSAGE SUPPORTED ................. :NO

14: INFO IN SCCP RLSD-MESSAGE SUPPORTED ................. :NO

15: TRACING SUPPORTED ................................... :NO

16: HANDOVER CANDIDATE ENQUIRY SUPPORTED ................ :NO

17: RESOURCE INDICATION SUPPORTED ....................... :NO

18: BSC OVERLOAD SUPPORTED .............................. :NO

19: CAUSE FIELD IN HANDOVER REQUEST SUPPORTED ........... :NO

20: A5_2 CIPHERING SUPPORTED ............................ :NO

21: MULTIPLE CIPHERING SUPPORTED ........................ :NO

22: CIPH_RESP_MODE FIELD MANDATORY IN CIPH_CMD .......... :NO

23: IMEI REQUEST IN CIPH_CMD SUPPORTED .................. :NO

24: UNEQUIPPED CIRCUIT SUPPORTED ........................ :NO

25: RADIO CHANNEL INFORMATION INCLUDED TO THE DLCI ...... :NO

26: TWO BYTES LENGTH OF LAYER 3 HEADER INFO SUPPORTED ... :NO

27: CHANNEL_NEEDED FIELD SUPPORTED IN PAGING ............ :NO

28: CLASSMARK REQUEST OPERATION SUPPORTED ............... :NO

29: CONFUSION MESSAGE SUPPORTED ......................... :NO

30: BSC CAPABLE TO HANDLE 6 KBIT/S RATE FOR TCH/F ....... :NO

31: BSC CAPABLE TO HANDLE HO AND CIPHERING PARALLELLY ... :NO

32: CLASSMARK_3 INFORMATION ELEMENT SUPPORTED ........... :NO

33: PAGING METHOD ALL CELLS ON BSS SUPPORTED IN SEARCH .. :NO

34: MSC_INVOKE_TRACE SUPPORTED .......................... :NO

35: HALF RATE CODE POINTS SUPPORTED ..................... :NO

36: RE-ESTABLISHMENT SUPPORTED .......................... :NO

37: CURRENT CHANNEL IN HANDOVER REQUEST SUPPORTED ....... :NO

38: CELL IDENTIFIER IN HANDOVER COMMAND SUPPORTED ....... :NO

39: MULTIPLE VOICE CODER SUPPORTED ...................... :NO

40: REVERSED BYTE ORDER IN CIC .......................... :NO

41: LOAD INDICATION MESSAGE SUPPORTED ................... :NO

42: MAX 2 TRAFFIC CHANNELS CAN BE USED IN HSCSD SERVICE . :NO




44: 14.4 KB RADIO INTERFACE DATA RATE SUPPORTED ......... :NO

45: POSITION TRACKING REQUEST SUPPORTED ................. :NO

46: DIRECTED RETRY ALLOWED WITHOUT DIRECTED RETRY CAUSE . :NO

47: CIRCUIT GROUP BLOCK/UNBLOCK MESSAGE SUPPORTED ....... :NO

48: BSS TO BSS INFO SUPPORTED ........................... :NO

49: ENHANCED CIRCUIT SWITCHED DATA SUPPORTED ............ :NO

50: AMR SPEECH CODEC SUPPORTED .......................... :NO

51: LOCATION POSITIONING SUPPORTED ...................... :NO

52: LOCALISED SERVICE AREA SUPPORTED .................... :NO

53: RANAP EXTENSIONS SUPPORTED .......................... :NO

54: COMMON ID INFORMATION SUPPORTED ..................... :NO

55: LAYER 3 HEADER INFORMATION NOT SUPPORTED ............ :NO

56: SERVICE HANDOVER SUPPORTED .......................... :NO

57: SERVING SAI SUPPORTED ............................... :NO

58: MSC RELEASE INFO SUPPORTED .......................... :NO

59: MAP CODEC NEGOTIATION SUPPORTED ..................... :NO

60: CTM FUNCTIONALITY SUPPORTED ......................... :NO

61: MODIFIED RE-ESTABLISHMENT RELEASE SEQUENCE .......... :NO


COMMAND EXECUTED

Command ZEDB:VER=2; outputs all information on BSSAP version 2.The output is as follows:

DX 200 DX220-LAB 2001-07-19 10:39:42




1: BSC RESET SUPPORTED ................................. :YES

2: BSC CIRCUIT RESET SUPPORTED ......................... :YES

3: BSC's BLOCKING INFO LOST IN INCOMING RESET .......... :YES

4: BSC's BLOCKING INFO LOST IN OUTGOING RESET .......... :YES

5: UNKNOWN CIC BLOCK RESPONDED ......................... :NO

6: UNKNOWN CIRCUIT RESET RESPONDED ..................... :NO

7: SCCP SSP DURING BSC RESET SUPPORTED ................. :YES

8: MOBILE ORIGINATED SMS SUPPORTED ..................... :NO

9: MOBILE TERMINATED SMS SUPPORTED ..................... :NO

10: DATA SERVICES SUPPORTED ............................. :NO

11: SDCCH HANDOVER SUPPORTED ............................ :NO

12: INFO IN SCCP CC-MESSAGE SUPPORTED ................... :NO

13: INFO IN SCCP CREF-MESSAGE SUPPORTED ................. :NO

14: INFO IN SCCP RLSD-MESSAGE SUPPORTED ................. :NO

15: TRACING SUPPORTED ................................... :NO

16: HANDOVER CANDIDATE ENQUIRY SUPPORTED ................ :NO

17: RESOURCE INDICATION SUPPORTED ....................... :NO

18: BSC OVERLOAD SUPPORTED .............................. :NO

19: CAUSE FIELD IN HANDOVER REQUEST SUPPORTED ........... :NO


21: MULTIPLE CIPHERING SUPPORTED ........................ :NO

22: CIPH_RESP_MODE FIELD MANDATORY IN CIPH_CMD .......... :NO

23: IMEI REQUEST IN CIPH_CMD SUPPORTED .................. :NO




24: UNEQUIPPED CIRCUIT SUPPORTED ........................ :NO

25: RADIO CHANNEL INFORMATION INCLUDED TO THE DLCI ...... :NO

26: TWO BYTES LENGTH OF LAYER 3 HEADER INFO SUPPORTED ... :NO

27: CHANNEL_NEEDED FIELD SUPPORTED IN PAGING ............ :NO

28: CLASSMARK REQUEST OPERATION SUPPORTED ............... :NO

29: CONFUSION MESSAGE SUPPORTED ......................... :NO

30: BSC CAPABLE TO HANDLE 6 KBIT/S RATE FOR TCH/F ....... :NO

31: BSC CAPABLE TO HANDLE HO AND CIPHERING PARALLELLY ... :NO

32: CLASSMARK_3 INFORMATION ELEMENT SUPPORTED ........... :NO

33: PAGING METHOD ALL CELLS ON BSS SUPPORTED IN SEARCH .. :NO

34: MSC_INVOKE_TRACE SUPPORTED .......................... :NO

35: HALF RATE CODE POINTS SUPPORTED ..................... :NO

36: RE-ESTABLISHMENT SUPPORTED .......................... :NO

37: CURRENT CHANNEL IN HANDOVER REQUEST SUPPORTED ....... :NO

38: CELL IDENTIFIER IN HANDOVER COMMAND SUPPORTED ....... :NO

39: MULTIPLE VOICE CODER SUPPORTED ...................... :NO

40: REVERSED BYTE ORDER IN CIC .......................... :NO

41: LOAD INDICATION MESSAGE SUPPORTED ................... :NO



44: 14.4 KB RADIO INTERFACE DATA RATE SUPPORTED ......... :NO

45: POSITION TRACKING REQUEST SUPPORTED ................. :NO

46: DIRECTED RETRY ALLOWED WITHOUT DIRECTED RETRY CAUSE . :NO

47: CIRCUIT GROUP BLOCK/UNBLOCK MESSAGE SUPPORTED ....... :NO

48: BSS TO BSS INFO SUPPORTED ........................... :NO

49: ENHANCED CIRCUIT SWITCHED DATA SUPPORTED ............ :NO

50: AMR SPEECH CODEC SUPPORTED .......................... :NO

51: LOCATION POSITIONING SUPPORTED ...................... :NO

52: LOCALISED SERVICE AREA SUPPORTED .................... :NO

53: RANAP EXTENSIONS SUPPORTED .......................... :NO

54: COMMON ID INFORMATION SUPPORTED ..................... :NO

55: LAYER 3 HEADER INFORMATION NOT SUPPORTED ............ :NO

56: SERVICE HANDOVER SUPPORTED .......................... :NO

57: SERVING SAI SUPPORTED ............................... :NO

58: MSC RELEASE INFO SUPPORTED .......................... :NO

59: MAP CODEC NEGOTIATION SUPPORTED ..................... :NO

60: CTM FUNCTIONALITY SUPPORTED ......................... :NO

61: MODIFIED RE-ESTABLISHMENT RELEASE SEQUENCE .......... :NO


0: GLOBAL RST GUARD PERIOD AT MSC ...................... :50 x 100 msec

1: OVERLOAD TIMER (SHORT) IN MSC ....................... :100 x 100 msec

2: OVERLOAD TIMER (LONG) IN MSC ........................ :30 x 100 msec

3: TIME OF RECEIPT OF RST CRCT ACK ..................... :100 x 100 msec

4: TIME TO RETURN RST ACK TO BSS ....................... :600 x 100 msec

5: GUARD PERIOD AFTER SUBS PROHIB ...................... :1500 x 100 msec

6: GUARD PERIOD AFTER SUBS AVAIL ....................... :0 x 100 msec

7: OVERL TIMER FOR MPT CONGESTION ...................... :180 x 100 msec

8: CIPHER MODE COMPL RECEIPT TIME ...................... :150 x 100 msec

9: ASSIGNMENT COMPL RECEIPT TIME ....................... :100 x 100 msec

10: MAX QUEUEING TIME IN ASSIGNMEN ...................... :200 x 100 msec

11: CLEAR COMPLETE RECEIPT TIME ......................... :150 x 100 msec

12: CLEAR COMPL RECEIPT TIME IN HO ...................... :150 x 100 msec

13: HANDOVER REQ ACK RECEIPT TIME ....................... :100 x 100 msec

14: HO COMPLETE RECEIPT TIME IN HO ...................... :100 x 100 msec

15: MAX QUEUEING TIME IN HANDOVER ....................... :200 x 100 msec



16: TIME AFTER TRAFFIC REASON HO ........................ :150 x 100 msec

17: MAX WAIT TIME OF RE-ESTABL REQ ...................... :100 x 100 msec

18: MAX WAIT TIME OF CLASSMARK UPD ...................... :50 x 100 msec

19: MAX WAIT TIME OF POS TRACK IND ...................... :20 x 100 msec

0: MAX REPEAT CNT OF BSS GLOB RST ...................... :10

1: MAX NBR OF HO CANDID ENQ BTSs ....................... :10

2: MAX NBR OF PERIOD RES IND BTSs ...................... :30

3: MAX REPEAT CNT OF RESOURCE REQ ...................... :3

4: MAX CELL AMOUNT CONSIDER IN HO ...................... :3

5: POOL CONFLICT ACTION MODE ........................... :1

6: MAX REPEAT CNT OF CIRCUIT RST ....................... :20

7: MAX REPEAT CNT OF CHANGE CRCT ....................... :1

LIST OF BSCs ATTACHED TO BSSAP VERSION:

LONDON 235

GLASGOW 1417

BRISTOL 798

LIST OF UNCs WITH A-INTERFACE ATTACHED TO BSSAP VERSION:

UNC1000 1000

UNCAINT1 120

LIST OF UNCs WITH A+ -INTERFACE ATTACHED TO BSSAP VERSION:

UNCPLUS1 150

UNCPLUS2 151

LIST OF NETWORK LAs ATTACHED TO BSSAP VERSION:

LAC MCC MNC

----- --- ---

8 123 321

COMMAND EXECUTED

Command ZEDB:TYPE=UNC,NAME=UNC1000:UNC; outputs the list ofthe logical UNCs attached to a BSSAP version of the UNC namedUNC1000. The output is as follows:

DX 200 DX220-LAB 2001-07-19 10:39:19


UNC NAME .......................(NAME). :UNC1000

UNC NUMBER .....................(NO)... :1000



LIST OF UNCs WITH A-INTERFACE ATTACHED TO BSSAP VERSION:




UNC1000 1000

UNCAINT1 120

COMMAND EXECUTED







EDO OUTPUT CELLULAR NETWORKCONTROLLER DATAFunction With this command you can output data on one or more BSCs/UNCs/

MGW R99s by giving the BSC/UNC/MGW names or numbers. If you wantto interrogate all UNCs with A+ -interface that are attached to a specificuser plane destination, give the UPD or NUPD as search criteria in thecommand. BSC/UNC/MGW-specific data can be modified by using thecommands of this command group. BSSAP-specific data handled with thiscommand group can be viewed with the EDB command.

Parameters Object identification: pool view mode;

Syntax EDO: [ TYPE = <object type | BSC def> ],

[ NAME = <object name>... |

NO = <object number>... |

[ UPD = <user plane destination index> <option>|

NUPD = <user plane destination name> <option>] |

<all> def ]:

[ <pool view mode | ALL def> ];


TYPE: object type




UNCP unlicensed mobile access network controller with A+interface <option>





If Feature 1260: Inter-System Handover and UMTS Changes in MSC andFeature 1705: Unlicensed Mobile Access (UMA) support in MSC/MSCServer are not activated, only the BSC can be chosen as type of object.

Note

When you give only parameter TYPE, all BSCs, UNCs, or MGWs willbe output. By default, the data of all BSCs will be displayed.

NAME: object name



NO: object number



You can give several BSC/UNC/MGW identifications by using character '&'in the name, and '&' and '&&' in the number.

UPD: user plane destination index <option>


UPD decimal from 0 to999

the index of a user plane destination

This parameter is given for interrogating all UNCs with A+ -interface thatare attached to a specific user plane destination.


NUPD: user plane destination name <option>


NUPD text string of 1 to15 characters

the name of a user plane destination



This parameter is given for interrogating all UNCs with A+ -interface thatare attached to a specific user plane destination.


pool view mode

This parameter defines how the circuit pool list is displayed in theexecution printout. The parameter can have the following values:

Value Description

ALL all available circuit pools are shown (default)

USED only pools with route are shown

NONE circuit pools are not shown

More information about pools can be found in the EDR commanddescription.

Examples 1. Output data on the BSC named BSCA2. As default, all availablepools would be shown in the execution printout.

ZEDO:TYPE=BSC,NAME=BSCA2;

2. Output data on the MGWs named TOWN3 and ROAD7. Pools wouldnot be shown in the execution printout.

ZEDO:TYPE=MGW,NAME=TOWN3&ROAD7:NONE;

3. Output data on the BSC number 23, and on four consecutive BSCs,the first being number 2463. Only pools which have route, would beshown in the execution printout.

ZEDO:TYPE=BSC,NO=23&2463&&2466:USED;

4. Output data of all MGWs in MSC. All available pools would be shownin the execution printout.

ZEDO:TYPE=MGW:ALL;

5. Output data on all BSCs in the MSC without pool lists.

ZEDO::NONE;

6. Output data on the UNCP named UNCPLUS1. Circuit pools are notrelevant for UNCs with A+ interface.

ZEDO:TYPE=UNCP,NAME=UNCPLUS1;




7. Output data of all the UNCPs which are attached to the user planedestination index 123.

ZEDO:TYPE=UNCP,UPD=123;

Executionprintouts

The abbreviations used in the execution printouts:

CI= cell identity




RNCID= radio network controller identifier

SAC= service area code

UMA= unlicensed mobile access

CTM= cellular text telephone modem

The program outputs the object name, number, and data. CommandZEDO:TYPE=BSC,NAME=TOWN11; outputs data on the BSC namedTOWN11. The output is as follows:

DX 200 DX220-LAB 2001-07-19 10:40:23

OUTPUTTING BASE STATION CONTROLLER DATA

BSC NAME .......................(NAME). :TOWN11

BSC NUMBER .....................(NO)... :645


BSC OPERATIONAL STATE ................. :AVAILABLE

BSC TRAFFIC LIMITATION ................ :10%

SIGNALLING NETWORK CODE ........(SNC).. :NA0

SIGNALLING POINT CODE ..........(SPC).. :3A75 (hex)


CELL IDENTIFICATION METHOD .....(CID).. :CGI






0: NOT APPLICABLE .................... : -

1: FR ................................ : -

2: HR ................................ :344 STATE: AVAILABLE

3: DR ................................ : -

4: FR DATA/EFR ....................... : -

5: FR/EFR ............................ : -

6: EFR/FR DATA/HR .................... : -

7: DR/EFR ............................ : -

8: HSCSD 2 FR ........................ : -

9: DR DATA/HSCSD 2 FR ................ : -



10: DR/EFR/HSCSD 2 FR ................. : -

11: HSCSD 4 FR ........................ : -

12: DR DATA/HSCSD 4 FR ................ : -

13: DR/EFR/HSCSD 4 FR ................. : -

15: FR DATA 14.5 ...................... : -

16: HSCSD 2 FR 14.5 ................... : -

17: HSCSD 4 FR 14.5 ................... : -

18: DR DATA/HSCSD 2 FR 14.5 ........... : -

19: DR DATA 14.5/HSCSD 4 FR 14.5 ...... : -

20: DR 14.5/EFR ....................... : -

21: DR 14.5/EFR/HSCSD 2 FR 14.5 ....... : -

22: DR 14.5/EFR/HSCSD 4 FR 14.5 ....... : -

23: AMR ............................... : -

24: AMR/FR DATA ....................... : -

25: FR/EFR/AMR/FR DATA ................ : -

26: FR/EFR/AMR/FR DATA 14.5 ........... : -

27: DR/EFR/AMR/DR DATA ................ : -

28: DR/EFR/AMR/DR DATA 14.5 ........... : -





42: CTM + FR .......................... : -

43: CTM + EFR ......................... : -

44: CTM + FR/EFR ...................... : -

45: CTM + DR/EFR ...................... :415 STATE: AVAILABLE

46: CTM + AMR ......................... : -

47: CTM + FR/EFR/AMR .................. : -

48: CTM + DR/EFR/AMR .................. : -


1: FR ................................ :512 STATE: AVAILABLE

3: DR ................................ : -

4: FR DATA/EFR ....................... : -

5: FR/EFR ............................ : -

6: EFR/FR DATA/HR .................... : -

7: DR/EFR ............................ : -

10: DR/EFR/HSCSD 2 FR ................. : -

13: DR/EFR/HSCSD 4 FR ................. : -

20: DR 14.5/EFR ....................... : -

21: DR 14.5/EFR/HSCSD 2 FR 14.5 ....... : -

22: DR 14.5/EFR/HSCSD 4 FR 14.5 ....... : -

25: FR/EFR/AMR/FR DATA ................ : -

26: FR/EFR/AMR/FR DATA 14.5 ........... : -

27: DR/EFR/AMR/DR DATA ................ : -

28: DR/EFR/AMR/DR DATA 14.5 ........... : -





42: CTM + FR .......................... : -

43: CTM + EFR ......................... : -

44: CTM + FR/EFR ...................... : -

45: CTM + DR/EFR ...................... : -

47: CTM + FR/EFR/AMR .................. : -

48: CTM + DR/EFR/AMR .................. : -




BTSs UNDER BSC :

BTS NAME NO LAC CI BTS ADM. STATE

---------- ----- ----- ----- --------------

BTSAAA 54 5 54 LOCKED

BTSBBB 414 10 14 UNLOCKED

:

:

BTSNNN 3330 10 3330 LOCKED

COMMAND EXECUTED

Note

The visibility of BSSAP subsystem number is optional. List of availablepools is different if circuit allocation by BSS is on. Pools 2–32 and 42–48 and all TFO pools are optional. For more information about pools,see the EDR command.

The ZEDO:TYPE=BSC,NAME=CITY1:USED; command outputs data onthe BSC named TOWN11. Only pools with route are shown. The output isas follows:

DX 200 DX220-LAB 2001-07-19 10:40:40

OUTPUTTING BASE STATION CONTROLLER DATA

BSC NAME .......................(NAME). :CITY1

BSC NUMBER .....................(NO)... :259


BSC OPERATIONAL STATE ................. :AVAILABLE

BSC TRAFFIC LIMITATION ................ :10%










2: HR ................................ :324 STATE: AVAILABLE


1: FR ................................ :512 STATE: AVAILABLE

5: FR/EFR ............................ :312 STATE: AVAILABLE

10: DR/EFR/HSCSD 2 FR ................. :389 STATE: AVAILABLE

22: DR 14.5/EFR/HSCSD 4 FR 14.5 ....... :741 STATE: AVAILABLE



BTSs UNDER BSC :

BTS NAME NO LAC CI BTS ADM. STATE

---------- ----- ----- ----- --------------

BTSABC 45 3 52 UNLOCKED

BTSDEF 214 11 13 UNLOCKED

BTSGHI 4370 13 3331 LOCKED

COMMAND EXECUTED

The ZEDO:TYPE=MGW,NAME=MGWW; command outputs data on the MGWnamed MGWW. The output is as follows:

DX 200 DX220-LAB 2001-07-19 10:40:59

OUTPUTTING MULTIMEDIA GATEWAY R99 DATA

MGW NAME .......................(NAME). :MGWW

MGW NUMBER .....................(NO)... :5

MGW ADMINISTRATIVE STATE .............. :UNLOCKED

MGW OPERATIONAL STATE ................. :AVAILABLE

MGW TRAFFIC LIMITATION ............... : -




CELL IDENTIFICATION METHOD .....(CID).. :RGI

PAGING METHOD ......................... :LAI




0: NOT APPLICABLE..................... :304 STATE: AVAILABLE

RNCs UNDER MGW R99:

RNCID MCC MNC

----- --- ---

1 3 45

2 3 45

SACs UNDER MGW R99:

SA NAME NO LAC SAC SA ADM. STATE

---------- ----- ----- ----- -------------

SAC1 4 2 4 LOCKED

COMMAND EXECUTED

The ZEDO:TYPE=UNCP,NAME=UNCPLUS1; command outputs data on theUNCP named UNCPLUS1. The output is as follows:

DX 200 DX220-LAB 2001-07-19 10:40:23

OUTPUTTING UMA NETWORK CONTROLLER DATA





UNC NUMBER .....................(NO)... :100











USER PLANE DESTINATION INDEX ...(UPD).. :1

USER PLANE DESTINATION NAME ....(NUPD). :UPD1

BTSs UNDER UNC :

NO BTS LOCATED

COMMAND EXECUTED







ned

Documents

document issues

product documentation

latest document issue

bssap version

version of bssap

edo commands

edb output information

edb commands