-
1 Nokia Siemens Networks OS8513EN51GLA01
Radio Network Configuration ManagementCreating BTS sites
Exercise
During the exercise, refer to NED: NetAct documentation -> Optimise and Expand -> Creating BTS Site
Note! You find this document also as a paper copy in this training folder.
-
4 Nokia Siemens Networks OS8513EN51GLA01
Module Objectives
After completing this module, the student should be able to:Integrate GSM BTS sites as a plan based operation
By using the NetAct applications:
CM AnalyserCM EditorCM Operations ManagerMMLNetwork EditorAlarm Monitor
-
5 Nokia Siemens Networks OS8513EN51GLA01
Creating GSM BTS SitesContents
Creating GSM BTS Sites by creating a new plan Creating GSM BTS Sites by importing a plan (alternative) Verifying and Cleanup Restore the situation Appendix: Parameters
-
6 Nokia Siemens Networks OS8513EN51GLA01
Uploading actual configurationsCreating a new plan with CM EditorCreate managed objects to new planChecking the planApproving the planActivating the plan in BSCChecking the actual configurationUnlocking objects in BSCActivating the unlock plan in BSC
Creating GSM BTS Sites by creating a new plan
-
7 Nokia Siemens Networks OS8513EN51GLA01
OSS
BSC
BSCDatabase
NetAct Database
Uploading Actuals
System Server
CM Operations ManagerActualsActuals
Uploading Actual Configurations
Refer to the NED Creating BTS Sites, section: Uploading actual configurations and perform the steps described in To upload actual GSM configuration.
Note! For more information about the upload of managed objects, refer to the training document BSS CM Related Operational tasks, section: Verify status and consistency of managed objects in NetAct database
-
8 Nokia Siemens Networks OS8513EN51GLA01
OSSTier1 Client PC
BSC
BSCDatabase
NetAct Database
C:\
CM EditorCreate a new PlanUpdate the plan
Create a new Plan
NewPlanNewPlan
Create a new Plan with CM Editor
If no plan is available from planning tool, create a new empty plan with CM Editor.
Tip! Deselect View -> Show All Managed Objects in Plans in order to see only the objects to be updated, resp. created your plan,
Note! The general procedure of creating a new plan with CM Editor is explained in the training document CM Applications.
-
9 Nokia Siemens Networks OS8513EN51GLA01
OSSOperator Seat PC
BSC
BSCDatabase
NetAct Database
C:\
CM EditorCreate managed
objects:LapDBCFBTSTRX
Create managed
Objects
NewPlanNewPlan
Create managed objects to new Plan
To make a create plan
Create new LAPD links into the plan.
Create new BCF into plan.
Create new BTSs into the plan.
Create new TRXs into the plan.
Follow the detailed description on the following slides.
Note! Make sure that all the mandatory creation parameters are defined in the plan. For more information on these parameters, refer to Mandatory GSM parameters in the NED.
Tip! Select the view Site Creation 2G. This editor view contains parameters relevant when creating new BTS sites.
Note! The general procedure of creating new objects with CM Editor is explained in the training document CM Applications.
-
10 Nokia Siemens Networks OS8513EN51GLA01
Create LapDs012345678910111213141516171819202122232425262728293031
TCH1 TCH2 TCH3 TCH4TCH5 TCH6 TCH7 TCH8
fixed CCITT frame data
TCH1TCH5
TCH2TCH6
TCH3 TCH4TCH7 TCH8
TRXS1TRXS3
BCFS1
Abis-If: PCM= _____
MBCCH+TCH for TRX1
MBCCH+TCH for TRX2
TRXSIG1TRXSIG2
BCFSIG
BSCBSC
BCFBCF
Abis-interface
Create LapD-links according to the parameter tables in the Appendix of this exercise document (or from a handout of the instructor).
Make sure, that the following rules are fulfilled:
1) One BCFSIG (LapD-channel for OMU link) must be created per BCF-object in the plan.
2) One TRXSIG (LapD link for TRX) must be created for every TRX-object in the plan.
3) The SAPI (Service Access Point Identifier) must be 0 for TRXSIGs and 62 for BCFSIGs.
4) The TEI (Terminal Equipment Identifier) is always 1 for BCFSIG.
5) The TEI must be equal to the TRX-ID for every TRXSIG.
Note! You should leave the ID field for the LapD blank, because the ID is reserved automatically. This reserved temporary ID is used when the object is saved to the RAC database. The parent BSC gives the final ID when provisioning the plan to the network. In the name field, give a unique LAPD Link Name for the object. The name must be written in upper case.
Note! When creating new LAPD links for PrimeSites, the BCFSIG is also attached to the TRX-object, not to the BCF-object, i.e. the TRX-object has then two LapD-links attached.
-
11 Nokia Siemens Networks OS8513EN51GLA01
Create BCF and attach BCFSIG
BCF|_BTS|_HOC|_POC|_TRX1|_BTS|_HOC|_POC|_TRX2
|_BCFSIG|_TRXSIG1|_TRXSIG2
BCF-ID=_BCF-ID=_BCFSIGBCFSIG
BTS-ID=_
TRX1 TRX2TRXSIG1 TRXSIG2
HOC POC
BTS-ID=_
HOC POC
Create BCF-object according to the parameter tables in the Appendix of this exercise document (or from a handout) and attach the corresponding BCFSIG by its name.
-
12 Nokia Siemens Networks OS8513EN51GLA01
Create BTSs
BCF
|_BTS|_HOC|_POC|_TRX1
|_BTS|_HOC|_POC|_TRX2|_BCFSIG|_TRXSIG1|_TRXSIG2
BCF-ID=_BCFSIG
BTS-ID=_BTS-ID=_
TRX1 TRX2TRXSIG1 TRXSIG2
HOCHOC POCPOC
BTS-ID=_BTS-ID=_
HOCHOC POCPOC
Create BTS-objects according to the parameter tables in the Appendix of this exercise document (or from handout).
Create the HOCs and POCs (optional).
Note! This can also be automated by running the HocCreation and PocCreation correction rules with CM Analyser. (This is explained in the course of this exercise).
-
13 Nokia Siemens Networks OS8513EN51GLA01
Create TRXs and attach TRXSIGs
BCF|_BTS|_HOC|_POC
|_TRX1|_BTS|_HOC|_POC
|_TRX2|_BCFSIG
|_TRXSIG1|_TRXSIG2
BCF-ID=_BCFSIG
BTS-ID=_
TRX1TRX1 TRX2TRX2TRXSIG1TRXSIG1 TRXSIG2TRXSIG2
HOC POC
BTS-ID=_
HOC POC
Create TRX-objects according to the parameter tables in the Appendix of this exercise document (or from handout).
Tip! You only have to give the PCM and TSL values for the first channel. The rest of the channel data is automatically added to the plan by running the TRXParamsFill correction rule with CM Analyser. (This is explained in the course of this exercise).
Tip! Do not mix up the parameters LapD Link Name and and O&M LapD Link Name. The O&M LapDlink is only used for Prime Sites.
-
14 Nokia Siemens Networks OS8513EN51GLA01
OSSOperator Seat PC
BSC
BSCDatabase
NetAct Database
C:\
CM Analyser Run rule set 2G_Site_CreationMake corrections to your planRerun the checks
Complete and check
Plan in RAC database
CompletedPlan
CompletedPlan
Checking the Plan
Refer to the NED document Creating BTS Sites, section: Checking the plans.
Tip! You can find the 2G_Site_Creation rules under the Rule Set folder. This Rule Set contains also the rules for TRXParamsFill, HocCreation and PocCreation.
Note! If you want apply the corrections performed by CM Analyser to your plan, go to tab Post-Check Actions and select Generate Corrections.
Check the result of the rule check an whether the corrections have been applied correctly to your plan.
Rerun the 2G_Site_Creation rules. There should be no errors any more.
Note! The general procedure of checking plans with CM Analyser is explained in the training document CM Applications.
-
15 Nokia Siemens Networks OS8513EN51GLA01
OSS
CM Operations Manager
Approve the plan(s) (optional)
Operator Seat PC
BSC
BSCDatabase
NetAct Database
C:\
Completedand
approvedPlan
Completedand
approvedPlanApprove the plan
In NetAct database
Approving the Plans
Note! The general procedure of approving plans with CM Operations Manager is explained in the training document CM Applications
-
16 Nokia Siemens Networks OS8513EN51GLA01
OSS
CM Operations Manager
Activate the plan orPre-Activate the plan
Operator Seat PC
BSC
BSCDatabase
NetAct Database
C:\
ActivatePlan In NE
Completedand
approvedPlan
Completedand
approvedPlan
Activating the Plan in BSC
Refer to the NED document Creating BTS Sites, section: Activating the plan in BSC, RNC and MSC .
Note! The general procedure of activating plans with CM Operations Manager is explained in the training document CM Applications.
-
Tips for trouble shooting, if the download fails:
-read the error log carefully: which objects could not be created for which reason?
-Check with MML, which objects have been created in BSC
-ZEEI to check the RNW objects.
-ZDSB or ZDTI to check the LapDs.
-Check with CM Editor in the Actual Configuration node, which objects have been created in the NetAct database. If an object is listed in small letters, it is non-operational, i.e. it exists in the OSS database, but not in the network. Delete those non operational objects with Network Editor -> Delete from database.
-If you want use the same plan to make corrections, e.g. create those objects, which could not be created in the first try, delete the objects from the plan, which are already in the network and keep the objects which have not been created yet. Update, i.e. rename your corrected plan, before you activate it.
-If an object has been created in the network with wrong parameters, make a deletion plan. You can set the corresponding objects in your creation-plan to delete for this purpose. Remove the other object from the plan which are not affected and update, i.e. rename your plan before the download.
-Before you download the correction plan, upload the actual configuration in order to synchronise the NetAct database with the NE database.
-
18 Nokia Siemens Networks OS8513EN51GLA01
OSSOperator Seat PC
BSC
BSCDatabase
NetAct Database
C:\
CM Analyser Run appropriate checks forthe actual configuration
Check the actuals
In NetAct database
ActualsActuals
Checking the Actual Configuration
Refer to the NED document Creating BTS Sites, section: Checking the actuals.
Which might be appropriate rules to use for the check in this case?
Note! The general procedure of checking the actual configuration with CM Analyser is explained in the training document CM Applications.
-
20 Nokia Siemens Networks OS8513EN51GLA01
OSS
CM EditorCreate unlock plan OR Unlock the objects directly
Tier1 Client PC
BSC
BSCDatabase
NetAct Database
C:\
UnlockPlan
UnlockPlan
Create an unlock
plan
Unlocking Objects in BSC
Refer to the NED document Creating BTS Sites, section: Unlocking objects in the BSC, RNC and MSC and perform the steps described in To unlock objects related to GSM BTS sites.
Change the Administrative State to Unlocked for the BCFs, BTSs and TRXs in your plan.
You can also lock and unlock managed objects using Lock/Unlock functionality in CM Editor
Note! The general procedure of (mass) modifying parameters with CM Editor is explained in the training document CM Applications.
-
21 Nokia Siemens Networks OS8513EN51GLA01
OSS
CM Operations ManagerActivate the unlock plan
Tier1 Client PC
BSC
BSCDatabase
NetAct Database
C:\
ActivatePlan In NE
UnlockPlan
UnlockPlan
Activating the Unlock Plan in BSC
Activate/download the unlock plan with CM Operations Manager and monitor the download log.
Note! The general procedure of activating plans with CM Operations Manager is explained in the training document CM Applicationst.
Verify the result of the operation with CM Editor or MML (command ZEEI;)
If a managed object is still locked, try to unlock it manually with CM Editor or MML.
Unlock first the TRX(s), then the BTS(s) and last the BCF(s). When the BCF is unlocked, the GSM BTS site performs a restart.
-
22 Nokia Siemens Networks OS8513EN51GLA01
Uploading actual configurationsImporting the RNW plan to the NetAct databaseCompleting the RNW Plan in NetAct databaseChecking the planApproving the planActivating the plan in BSCChecking the actual configurationUnlocking objects in BSCActivating the unlock plan in BSC
Creating GSM BTS Sites by importing a plan
-
23 Nokia Siemens Networks OS8513EN51GLA01
OSS
BSC
BSCDatabase
NetAct Database
Uploading Actuals
System Server (HP/UX)
CM Operations ManagerActualsActuals
Uploading Actual Configurations
Refer to the NED document Creating BTS Sites, section: Uploading actual configurations and perform step1.
Note! For more information about the upload of managed objects, refer to the training document BSS CM Operational tasks, section: Verify status and consistency of managed objects in NetAct database
-
24 Nokia Siemens Networks OS8513EN51GLA01
OSSTier1 Client PC
BSC
BSCDatabase
NetAct Database
C:\
Import a plan
UncompletedPlan
UncompletedPlan
UncompletedPlan e.g. fromPlanning tool
UncompletedPlan e.g. fromPlanning tool
CM Operations ManagerImport planDefine a plan nameAssign System Template...
Uploading Actual Configurations
Refer to the NED document Creating BTS Sites, section: Importing the RNW plans in RAC database.
Note! The general procedure of importing plans with CM Operations Manager is explained in the training document CM Applications.
-
26 Nokia Siemens Networks OS8513EN51GLA01
OSSTier1 Client PC
NE
BSCDatabase
NetAct Database
C:\
CM EditorAdd missing parametersCreate missing objects
Complete the
RNW Plan
CompletedPlan
CompletedPlan
Completing the RNW Plan in RAC with CM Editor
Refer to the NED document Creating BTS Sites, section: To complete the GSM RNW plan with CM Editor and perform the steps, which are necessary.
The prerequisites in this case are:
SITE, ANTE or GCAL objects are not needed here.
EDGE and GPRS are not used.
Adjacencies are not created here (This is covered in Training Document Managing adjacencies)
Note! In case, you want to attach LapD-channels to the corresponding objects, there is a special parameter called Destination can be added to the Editor view for an LAPD. Its value indicates the BCF or TRX DN that uses the LAPD. If the Destination value is empty, the LAPD is free and can be attached to either the BCF or TRX.
Note! The general procedure of modifying parameters and creating managed objects with CM Editor is explained in the training document CM Applications.
-
27 Nokia Siemens Networks OS8513EN51GLA01
OSSTier1 Client PC
BSC
BSCDatabase
NetAct Database
C:\
CM Analyser Run rule set 2G_Site_CreationMake corrections to your planRerun the checks
Complete and check
Plan In NetAct database
CompletedPlan
CompletedPlan
Checking the Plan
Refer to the NED document Creating BTS Sites, section: Checking the plans and perform the steps 1-3.
Tip! You can find the 2G_Site_Creation rules under the Rule Set folder. This Rule Set contains also the rules for TRXParamsFill, HocCreation and PocCreation.
Note! If you want apply the corrections performed by CM Analyser to your plan, go to tab Post-Check Actions and select Generate Corrections.
Check the result of the rule check an whether the corrections have been applied correctly to your plan.
Rerun the 2G_Site_Creation rules. There should be no errors any more.
Note! The general procedure of checking plans with CM Analyser is explained in the training document CM Applications.
-
28 Nokia Siemens Networks OS8513EN51GLA01
Approve the plan
In NetAct database
OSS
CM Operations Manager
Approve the plan(s) (optional)
Tier1 Client PC
BSC
BSCDatabase
NetAct Database
C:\
Completedand
approvedPlan
Completedand
approvedPlan
Approving the Plans
Refer to the NED document Creating BTS Sites, section: Approving the plan(s).
Note! The general procedure of approving plans with CM Operations Manager is explained in the training document CM Applications
-
29 Nokia Siemens Networks OS8513EN51GLA01
OSS
CM Operations Manager
Activate the plan
Tier1 Client PC
BSC
BSCDatabase
NetAct Database
C:\
ActivatePlan In NE
Completedand
approvedPlan
Completedand
approvedPlan
Activating the Plan in BSC
Refer to the NED document Creating BTS Sites, section: Activating the plan in BSC, RNC and MSC .
Note! The LAPDs are automatically unlocked when you create LAPDs with CM Operations Manager.
Note! The general procedure of activating plans with CM Operations Manager is explained in the training document CM Applications.
-
30 Nokia Siemens Networks OS8513EN51GLA01
OSSTier1 Client PC
BSC
BSCDatabase
NetAct Database
C:\
CM Analyser Run appropriate checksfor the actual configuration
Check the actuals
In RAC database
ActualsActuals
Checking the Actual Configuration
Refer to the NED document Creating BTS Sites, section: Checking the actuals.
Which might be appropriate rules to use for the check in this case?
Note! The general procedure of checking the actual configuration with CM Analyser is explained in the training document CM Applications.
-
31 Nokia Siemens Networks OS8513EN51GLA01
OSS
CM EditorCreate unlock plan or unlock objects directly
Tier1 Client PC
BSC
BSCDatabase
NetAct Database
C:\
UnlockPlan
UnlockPlan
Create an unlock
plan
Unlocking Objects in BSC
Change the Administrative State to Unlocked for the BCFs, BTSs and TRXs in your plan or directly using CM Editor.
Note! The general procedure of (mass) modifying parameters with CM Editor is explained in the training document CM Applications.
-
32 Nokia Siemens Networks OS8513EN51GLA01
OSS
CM Operations Manager
Activate the unlock plan
Tier1 Client PC
BSC
BSCDatabase
NetAct Database
C:\
ActivatePlan In NE
UnlockPlan
UnlockPlan
Activating the Unlock Plan in BSC
Activate/download the unlock plan with CM Operations Manager and monitor the download log.
Note! The general procedure of activating plans with CM Operations Manager is explained in the NOCCM training document CM Applications.
Verify the result of the operation with CM Editor or MML (command ZEEI;)
If a managed object is still locked, try to unlock it manually with CM Editor or MML.
Unlock first the TRX(s), then the BTS(s) and last the BCF(s). When the BCF is unlocked, the GSM BTS site performs a restart.
-
33 Nokia Siemens Networks OS8513EN51GLA01
Verifying and Cleanup
Assigning the BTS to its final Maintenance region
Check alarms
-
34 Nokia Siemens Networks OS8513EN51GLA01
Verifying and Clean-up
Open CM Editor and browse into Actual part.
Select the managed object that you want to modify the MR for.
Right click at the object and choose Assign maintenance region from the pop-up menu.
The Maintenance region dialog opens.
Choose the MR that you want and then click Assign.
-
35 Nokia Siemens Networks OS8513EN51GLA01
Verifying and Clean-up
Open the Alarm Monitor from Top-Level User Interface -> Utils -> Fault Mgmt -> Alarm Monitor.Go to Configuration -> Monitoring Criteria.
Click on the Add-button in order to get a listing with managed objects in the RAC database. Select the object(s), you want to monitor, e.g. the new BTS.
Click on the magnifying glass.
On the main screen, you can see the alarms of the object(s) you selected beforehand.
-
36 Nokia Siemens Networks OS8513EN51GLA01
Restore the situation
Create a deletion plan with CM Editor Download the deletion plan to the BSC Delete plans from RAC database Delete checks from CM Analyser
-
37 Nokia Siemens Networks OS8513EN51GLA01
OSSTier1 Client PC
BSC
BSCDatabase
NetAct Database
C:\
CM EditorCreate a deletion PlanUpdate Plan
Create a
deletion Plan
DeletionPlan
DeletionPlan
Create a Deletion Plan with CM Editor
Update your plan by entering a new name.
Tip! Deselect View -> Show All Managed Objects in Plans in order to see only the objects to be updated, resp. created your plan,
Note! The general procedure of creating a new plan with CM Editor is explained in the training document CM Applications.
Highlight the objects in your plan to be deleted and go to Managed Object -> Change to Delete.
Note! The general procedure of modifying the object states within an plan with CM Editor is explained in the training document CM Applications.
-
38 Nokia Siemens Networks OS8513EN51GLA01
OSS
CM Operations ManagerActivate the deletion plan
Tier1 Client PC
BSC
BSCDatabase
NetAct Database
C:\
ActivatePlan In NE
DeletionPlan
DeletionPlan
Activating the Deletion Plan in BSC
Activate/download the deletion plan with CM Operations Manager and monitor the download log.
Note! The general procedure of activating plans with CM Operations Manager is explained in the training document CM Applications.
Check with MML, if the objects have been deleted in BSC
-ZEEI to check the RNW objects.
-ZDSB or ZDTI to check the LapDs.
Check with CM Editor in the Actual Configuration node, which objects have been created in the OSS database. If an object is listed in small letters, it is non operational, i.e. it exists in the OSS database, but not in the network. Delete those non operational objects with Network Editor -> Delete from database.
Perform an upload of the actual configuration.
-
39 Nokia Siemens Networks OS8513EN51GLA01
Delete plans from RAC database
Select a plan or multiple plans
Select Delete
-
40 Nokia Siemens Networks OS8513EN51GLA01
Delete checks in CM Analyser
If check results for the site creation plans are no longer needed, they can be deleted
Question: When would you want to keep the checks?
-
41 Nokia Siemens Networks OS8513EN51GLA01
Appendix: Parameters
LapD Parameter BCF Parameter BTS Parameter TRX Parameter
-
Object type Parameter Values
Team1
Values
Team2
Values
Team3
Values
Team4
LAPD
(BCFSIG)
LapD name BS001 BS002 BS003 BS004
PCM 40 41 42 43
TSL 31 31 31 31
Sub-TSL - - - -
Bit rate 64 64 64 64
SAPI 62 62 62 62
TEI 1 1 1 1
Administrative
state
unlocked unlocked unlocked unlocked
Object type
Parameter Values
Team1
Values
Team1
Values
Team2
Values
Team2
Values
Team3
Values
Team3
Values
Team4
Values
Team4
LAPD
(TRXSIG)
LapD name T0101 T0102 T0201 T0202 T0301 T0302 T0401 T0402
PCM 40 40 41 41 42 42 43 43
TSL 25 26 25 26 25 26 25 26
Sub-TSL 0 0 0 0 0 0 0 0
Bit rate 16 16 16 16 16 16 16 16
SAPI 0 0 0 0 0 0 0 0
TEI 1 2 1 2 1 2 1 2
Administrative State
unlocked unlocked unlocked unlocked unlocked unlocked unlocked unlocked
Create LapD-links:
Please, check ET numbers with your trainer
Please, check ET numbers with your trainer
Note! Do not enter any IDs for the LapD channels. The BSC will assignthe final ID itself during the activation of the plan.
-
Object type Parameter Values
Team1
Values
Team2
Values
Team3
Values
Team4
LAPD
(BCFSIG)
LapD name BS001 BS002 BS003 BS004
PCM 40 41 42 43
TSL 31 31 31 31
Sub-TSL - - - -
Bit rate 64 64 64 64
SAPI 62 62 62 62
TEI 1 1 1 1
Administrative
state
unlocked unlocked unlocked unlocked
Object type
Parameter Values
Team1
Values
Team1
Values
Team2
Values
Team2
Values
Team3
Values
Team3
Values
Team4
Values
Team4
LAPD
(TRXSIG)
LapD name T0101 T0102 T0201 T0202 T0301 T0302 T0401 T0402
PCM 40 40 41 41 42 42 43 43
TSL 25 26 25 26 25 26 25 26
Sub-TSL 0 0 0 0 0 0 0 0
Bit rate 16 16 16 16 16 16 16 16
SAPI 0 0 0 0 0 0 0 0
TEI 1 2 1 2 1 2 1 2
Administrative State
unlocked unlocked unlocked unlocked unlocked unlocked unlocked unlocked
Create LapD-links:
Please, check ET numbers with your trainer
Please, check ET numbers with your trainer
Note! Do not enter any IDs for the LapD channels. The BSC will assignthe final ID itself during the activation of the plan.
-
Parameter tables for site creation
Create BCF object:
Object type Parameter Values
Team 1
Values
Team 2
Values
Team 3
Values
Team 4
BCF BCF-Id 1 2 3 4
BCF Name BCF1 BCF2 BCF3 BCF4
Administrative state locked locked locked locked
BCF type UltraSite UltraSite UltraSite UltraSite
Attached
LapD
BS001 BS002 BS003 BS004
-
Create BTS object
Create HOC and POC
Object type Parameter Values
Team 1
Values
Team 2
Values
Team 3
Values
Team 4
BTS BSC-ID Given by parent object
BCF-ID 1 2 3 4
BTS-ID 1&2 3&4 5&6 7&8
BTS Name BTS1/
BTS2
BTS3/
BTS4
BTS5/
BTS6
BTS7/
BTS8
Cell Id 371&372 373&374 375&376 377&378
MCC 262 262 262 262
MNC 09 09 09 09
LAC 3371 3370 3371 3369
RAC 255 255 255 255
NCC 5 5 5 5
BCC 0 0 0 0
Freq.-band in use GSM 1800 GSM 1800 GSM 1800 GSM 1800
Object type Parameter ValuesTeam 1
ValuesTeam 2
ValuesTeam 3
Values Team 4
HOC HOC-ID 1 1 1 1
POC POC-ID 1 1 1 1
-
Create 1st TRX object:
Object type
Parameter Values
Team 1
Values
Team 2
Values
Team 3
Values
Team 4
BTS 1 3 5 7
TRX TRX-ID 1 1 1 1
TRX Name
Trx1 Trx1 Trx1 Trx1
Freq 700 720 655 681
TRX SIG T0101 T0201 T0301 T0401
Channel type
0: MBCCHC
1-7: TCHF
0: MBCCHC
1-7: TCHF
0: MBCCHC
1-7: TCHF
0: MBCCHC
1-7: TCHF
PCM 40 41 42 43
TSL 1-2 1-2 1-2 1-2
Sub-TSL 0-3 0-3 0-3 0-3
Assigned
LapD
T0101 T0201 T0301 T0401
TSC 0 0 0 0
Same PCMs as for LapD creation
Note! The Training Sequence Code (TSC) must have the same value asthe BTS parameter Base Station Colour Code (BCC)
-
Create 2nd TRX object:
Object type
Parameter Values
Team 1
Values
Team 2
Values
Team 3
Values
Team 4
BTS 2 4 6 8
TRX TRX-ID 2 2 2 2
TRX Name
Trx2 Trx2 Trx2 Trx2
Freq 710 730 665 691
TRX SIG T0102 T0202 T0302 T0402
Channel type
0: MBCCHC
1-7: TCHF
0: MBCCHC
1-7: TCHF
0: MBCCHC
1-7: TCHF
0:
MBCCHC
1-7:TCHF
PCM 40 41 42 43
TSL 3-4 3-4 3-4 3-4
Sub-TSL 0-3 0-3 0-3 0-3
Assigned
TSL
T0102 T0202 T0302 T0402
TSC 0 0 0 0
Same PCMs as for LapD creation
Note! The Training Sequence Code (TSC) must have the same value asthe BTS parameter Base Station Colour Code (BCC)