09 - 02 - OS8513AEN51GLA1 - Creating BTS Sites Exercise 2G

Radio Network Configuration Management
Creating BTS sites

Exercise
1 Nokia Siemens Networks
OS8513EN51GLA01
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.
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 Analyser
CM Editor
CM Operations Manager
MML
Network Editor
Alarm Monitor
OS8513EN51GLA01
Creating GSM BTS Sites

Contents
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
OS8513EN51GLA01
Creating GSM BTS Sites by creating a new plan

Uploading actual configurations
Creating a new plan with CM Editor
Create managed objects to new plan
Checking the plan
Approving the plan
Activating the plan in BSC
Checking the actual configuration
Unlocking objects in BSC
Activating the unlock plan in BSC
OS8513EN51GLA01
Uploading Actual Configurations

OSS
NetAct Database
System Server
Actuals
Actuals
Uploading Actuals
BSC
BSC
Database
OS8513EN51GLA01
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
Create a new Plan with CM Editor

OSS
Tier1 Client PC
NetAct Database
CM Editor
Create a new Plan
Update the plan
Create a
new Plan
New
New
Plan
Plan
C:\
BSC
BSC
Database
OS8513EN51GLA01
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.
Create managed objects to new Plan

Operator Seat PC
CM Editor
Create managed
objects:
LapD
BCF
BTS
TRX
OSS
Create managed
NetAct Database
Objects
New
New
Plan
Plan
C:\
BSC
BSC
Database
OS8513EN51GLA01
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
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Create LapDs
fixed CCITT frame data

TCH1
TCH2
TCH3
TCH4
TCH5
TCH1
TCH6
TCH7
TCH8
TCH2
TCH3
TCH4
TCH5
TCH6
TCH7
TCH8
MBCCH+TCH for TRX1

MBCCH+TCH for TRX2
BSC
BSC
Abis-interface
TRXSIG1
TRXSIG2
TRXS1
TRXS3
BCFS1
BCF
BCF
BCFSIG
Abis-If: PCM= _____
OS8513EN51GLA01
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.
Create BCF and attach BCFSIG

BCF
|_BTS
|_HOC
|_POC
|_TRX1
|_BTS
|_HOC
|_POC
|_TRX2
|_BCFSIG
BCFSIG
BCF-ID=_
BTS-ID=_
HOC
TRXSIG1
BTS-ID=_
POC
TRX1
POC
HOC
TRX2
TRXSIG2
|_TRXSIG1
|_TRXSIG2
OS8513EN51GLA01
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.
Create BTSs
BCF
|_BTS
|_HOC
|_POC
BCFSIG
|_TRX1
|_BTS
|_HOC
|_POC
|_TRX2
|_BCFSIG
|_TRXSIG1
|_TRXSIG2
BCF-ID=_
BTS-ID=_
HOC
TRXSIG1
BTS-ID=_
POC
TRX1
POC
HOC
TRX2
TRXSIG2
OS8513EN51GLA01
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).
Create TRXs and attach TRXSIGs

BCF
|_BTS
|_HOC
|_POC
BCFSIG
BCF-ID=_
|_TRX1
|_BTS
|_HOC
|_POC
BTS-ID=_
HOC
BTS-ID=_
POC
POC
HOC
|_TRX2
|_BCFSIG
TRXSIG1
TRX1
TRX2
TRXSIG2
|_TRXSIG1
|_TRXSIG2
OS8513EN51GLA01
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 LapD
link is only used for Prime Sites.
Checking the Plan

Operator Seat PC
OSS
NetAct Database
CM Analyser
Run rule set 2G_Site_Creation
Make corrections to your plan
Rerun the checks
Completed
Completed
Plan
Plan
Complete and check
Plan in RAC database
C:\
BSC
BSC
Database
OS8513EN51GLA01
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 PostCheck 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
Approving the Plans

OSS
Operator Seat PC
NetAct Database
CM Operations
Manager
Approve the plan(s)
(optional)
Approve the plan
Completed
Completed
and
and
approved
approved
Plan
Plan
In NetAct database
C:\
BSC
BSC
Database
OS8513EN51GLA01
Note! The general procedure of approving plans with CM Operations Manager is explained in
the training document CM Applications
Activating the Plan in BSC

OSS
Operator Seat PC
NetAct Database
CM Operations
Manager
Activate the plan or
Pre-Activate the plan
Completed
Completed
and
and
approved
approved
Plan
Plan
Activate
Plan In NE
C:\
BSC
BSC
Database
OS8513EN51GLA01
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.
Checking the Actual Configuration

OSS
Operator Seat PC
NetAct Database
CM Analyser
Run appropriate checks for
the actual configuration
Actuals
Actuals
Check the actuals
In NetAct database
C:\
BSC
BSC
Database
OS8513EN51GLA01
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.
Unlocking Objects in BSC

Tier1 Client PC
OSS
NetAct Database
CM Editor
Create unlock plan
OR Unlock the objects
directly
Create an unlock
Unlock
Unlock
Plan
Plan
plan
C:\
BSC
BSC
Database
OS8513EN51GLA01
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
Activating the Unlock Plan in BSC

OSS
Tier1 Client PC
NetAct Database
Activate the unlock plan
Unlock
Unlock
Plan
Plan
Activate
Plan In NE
C:\
BSC
BSC
Database
OS8513EN51GLA01
Activate/download the unlock plan with CM Operations Manager and monitor the
download log.
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.
Creating GSM BTS Sites by importing a plan

Uploading actual configurations
Importing the RNW plan to the NetAct database
Completing the RNW Plan in NetAct database
Checking the plan
Approving the plan
Activating the plan in BSC
Checking the actual configuration
Unlocking objects in BSC
Activating the unlock plan in BSC
OS8513EN51GLA01

OSS
NetAct Database
System Server (HP/UX)
Actuals
Actuals
Uploading Actuals
BSC
BSC
Database
OS8513EN51GLA01
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

Tier1 Client PC
OSS
NetAct Database
Import plan
Define a plan name
Assign System Template
...
Uncompleted
Uncompleted
Plan
Plan
Import a plan
Uncompleted
Uncompleted
Plan
Plan e.g.
e.g. from
from
Planning
Planning tool
tool
C:\
BSC
BSC
Database
OS8513EN51GLA01
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
Completing the RNW Plan in RAC with CM Editor

OSS
Tier1 Client PC
CM Editor
Add missing
parameters
Create missing objects
Complete the
NetAct Database
RNW Plan
Completed
Completed
Plan
Plan
C:\
NE
BSC
Database
OS8513EN51GLA01
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.
Checking the Plan

OSS
Tier1 Client PC
NetAct Database
CM Analyser
Run rule set 2G_Site_Creation
Make corrections to your plan
Rerun the checks
Completed
Completed
Plan
Plan
Complete and check
Plan In NetAct database
C:\
BSC
BSC
Database
OS8513EN51GLA01
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 PostCheck 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
Approving the Plans

OSS
Tier1 Client PC
NetAct Database
CM Operations
Manager
Approve the plan(s)
(optional)
Approve the plan
Completed
Completed
and
and
approved
approved
Plan
Plan
In NetAct database
C:\
BSC
BSC
Database
OS8513EN51GLA01
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
Activating the Plan in BSC

OSS
Tier1 Client PC
NetAct Database
CM Operations
Manager
Activate the plan
Completed
Completed
and
and
approved
approved
Plan
Plan
Activate
Plan In NE
C:\
BSC
BSC
Database
OS8513EN51GLA01
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.
Checking the Actual Configuration

OSS
Tier1 Client PC
NetAct Database
CM Analyser
Run appropriate checks
for the actual configuration
Actuals
Actuals
Check the actuals
In RAC database
C:\
BSC
BSC
Database
OS8513EN51GLA01
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.
Unlocking Objects in BSC

OSS
Tier1 Client PC
NetAct Database
CM Editor
Create unlock plan or
unlock objects directly
Unlock
Unlock
Plan
Plan
Create an unlock
plan
C:\
BSC
BSC
Database
OS8513EN51GLA01
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
Activating the Unlock Plan in BSC

OSS
Tier1 Client PC
NetAct Database
CM Operations
Manager
Activate the unlock plan
Unlock
Unlock
Plan
Plan
Activate
Plan In NE
C:\
BSC
BSC
Database
OS8513EN51GLA01
Activate/download the unlock plan with CM Operations Manager and monitor the
download log.
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.
Verifying and Cleanup
Assigning the BTS to its final Maintenance

region
Check alarms
OS8513EN51GLA01
Verifying and Clean-up
OS8513EN51GLA01
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.
Verifying and Clean-up
OS8513EN51GLA01
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.
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
OS8513EN51GLA01
Create a Deletion Plan with CM Editor

OSS
Tier1 Client PC
CM Editor
Create a deletion Plan
Update Plan
Create a
NetAct Database
deletion Plan
Deletion
Deletion
Plan
Plan
C:\
BSC
BSC
Database
OS8513EN51GLA01
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
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.
Activating the Deletion Plan in BSC

OSS
Tier1 Client PC
NetAct Database
Activate the deletion plan
Deletion
Deletion
Plan
Plan
Activate
Plan In NE
C:\
BSC
BSC
Database
OS8513EN51GLA01
Activate/download the deletion plan with CM Operations Manager and monitor the
download log.
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.
Delete plans from RAC database
OS8513EN51GLA01
Select a plan or multiple plans

Select Delete
Delete checks in CM Analyser
OS8513EN51GLA01
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?
Appendix: Parameters
LapD Parameter
BCF Parameter
BTS Parameter
TRX Parameter
OS8513EN51GLA01
Create LapD-links:
Object type
Parameter
LapD name
LAPD
Values
Values
Values
Values
Team1
Team2
Team3
Team4
BS001
BS002
BS003
BS004
(BCFSIG)
PCM
40
41
42
Please, check ET numbers with your trainer
TSL
31
31
31
43
Sub-TSL
Bit rate
64
64
64
64
SAPI
62
62
62
62
TEI
31
Administrative unlocked unlocked unlocked unlocked

state
Note! Do not enter any IDs for the LapD channels. The BSC will assign
the final ID itself during the activation of the plan.
Object
type
Parameter
LAPD
Values
Values
Values
Values
Values
Values
Values
Values
Team1
Team1
Team2
Team2
Team3
Team3
Team4
Team4
LapD name
T0101
T0102
T0201
T0202
T0301
T0302
T0401
T0402
PCM
40
40
43
43
TSL
25
26
25
26
25
26
25
26
Sub-TSL
Bit rate
16
16
16
16
16
16
16
16
SAPI
TEI
Administrative
State
unlocked
unlocked
unlocked
unlocked
unlocked
unlocked
unlocked
unlocked
(TRXSIG)
41
41
42
42
Create LapD-links:
Object type
Parameter
LapD name
LAPD
Values
Values
Values
Values
Team1
Team2
Team3
Team4
BS001
BS002
BS003
BS004
(BCFSIG)
PCM
40
41
42
TSL
31
31
31
43
Sub-TSL
Bit rate
64
64
64
64
SAPI
62
62
62
62
TEI
31
Administrative unlocked unlocked unlocked unlocked

state
Note! Do not enter any IDs for the LapD channels. The BSC will assign
the final ID itself during the activation of the plan.
Object
type
Parameter
LAPD
Values
Values
Values
Values
Values
Values
Values
Values
Team1
Team1
Team2
Team2
Team3
Team3
Team4
Team4
LapD name
T0101
T0102
T0201
T0202
T0301
T0302
T0401
T0402
PCM
40
40
43
43
TSL
25
26
25
26
25
26
25
26
Sub-TSL
Bit rate
16
16
16
16
16
16
16
16
SAPI
TEI
Administrative
State
unlocked
unlocked
unlocked
unlocked
unlocked
unlocked
unlocked
unlocked
(TRXSIG)
41
41
42
42
Parameter tables for site creation
Create BCF object:
Object type Parameter
BCF
Values
Values
Values
Values
Team 1
Team 2
Team 3
Team 4
BCF-Id
BCF Name
BCF1
BCF2
BCF3
BCF4
Administrative state locked
locked
locked
locked
BCF type
UltraSite UltraSite UltraSite UltraSite
Attached
BS001
LapD
BS002
BS003
BS004
Create BTS object
Object type Parameter
BTS
Values
Values
Values
Values
Team 1
Team 2
Team 3
Team 4
BSC-ID
Given by parent object
BCF-ID
BTS-ID
1&2
3&4
5&6
7&8
BTS Name
BTS1/
BTS3/
BTS5/
BTS7/
BTS2
BTS4
BTS6
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
BCC
Freq.-band in use GSM 1800 GSM 1800 GSM 1800 GSM 1800
Object type Parameter Values

Team 1
HOC-ID
1
HOC
POC
POC-ID
Values
Team 2
1
Values
Team 3
1
Values
Team 4
1
Create HOC and POC
Create 1st TRX object:
Object
type
Parameter Values
Values
Values
Values
Team 1
Team 2
Team 3
Team 4
TRX-ID
TRX
Name
Trx1
Trx1
Trx1
Trx1
Freq
700
720
655
681
TRX SIG
T0101
T0201
T0301
T0401
Channel
type
0:
MBCCHC
0:
MBCCHC
0:
MBCCHC
0:
MBCCHC
1-7: TCHF
1-7: TCHF
1-7: TCHF
1-7: TCHF
BTS
TRX
PCM
40
41
42
Same PCMs as for LapD creation
43
TSL
1-2
1-2
1-2
1-2
Sub-TSL
0-3
0-3
0-3
0-3
Assigned
T0101
T0201
T0301
T0401
LapD
TSC
Note! The Training Sequence Code (TSC) must have the same value as
the BTS parameter Base Station Colour Code (BCC)
Create 2nd TRX object:
Object Parameter Values

type
Team 1
Values
Values
Values
Team 2
Team 3
Team 4
TRX-ID
TRX
Name
Trx2
Trx2
Trx2
Trx2
Freq
710
730
665
691
TRX SIG
T0102
T0202
T0302
T0402
Channel
type
0:
MBCCHC
0:
MBCCHC
0:
MBCCHC
0:
1-7: TCHF
1-7: TCHF
1-7: TCHF
BTS
TRX
MBCCHC
1-7:TCHF
PCM
40
41
42
43
Same PCMs as for LapD creation
3-4
3-4
3-4
TSL
3-4
Sub-TSL
0-3
0-3
0-3
0-3
Assigned
T0102
T0202
T0302
T0402
TSL
TSC
Note! The Training Sequence Code (TSC) must have the same value as
the BTS parameter Base Station Colour Code (BCC)

09 - 02 - OS8513AEN51GLA1 - Creating BTS Sites Exercise 2G

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

09 - 02 - OS8513AEN51GLA1 - Creating BTS Sites Exercise 2G

Uploaded by

Copyright:

Available Formats

Radio Network Configuration Management

Creating BTS sites

1 Nokia Siemens Networks

4 Nokia Siemens Networks

Creating GSM BTS Sites

Creating GSM BTS Sites by creating a new plan

5 Nokia Siemens Networks

Creating GSM BTS Sites by creating a new plan

6 Nokia Siemens Networks

Uploading Actual Configurations

Create a new Plan with CM Editor

8 Nokia Siemens Networks

Create managed objects to new Plan

9 Nokia Siemens Networks

To make a create plan

fixed CCITT frame data

MBCCH+TCH for TRX1

Abis-If: PCM= _____

10 Nokia Siemens Networks

Create BCF and attach BCFSIG

11 Nokia Siemens Networks

Create TRXs and attach TRXSIGs

Checking the Plan

14 Nokia Siemens Networks

Approving the Plans

Approve the plan

15 Nokia Siemens Networks

Activating the Plan in BSC

16 Nokia Siemens Networks

Tips for trouble shooting, if the download fails:

Checking the Actual Configuration

18 Nokia Siemens Networks

Unlocking Objects in BSC

20 Nokia Siemens Networks

Activating the Unlock Plan in BSC

21 Nokia Siemens Networks

Creating GSM BTS Sites by importing a plan

22 Nokia Siemens Networks

Uploading Actual Configurations

System Server (HP/UX)

Uploading Actual Configurations

24 Nokia Siemens Networks

Completing the RNW Plan in RAC with CM Editor

26 Nokia Siemens Networks

Checking the Plan

27 Nokia Siemens Networks

Approving the Plans

Approve the plan

28 Nokia Siemens Networks

Activating the Plan in BSC

29 Nokia Siemens Networks

Checking the Actual Configuration

30 Nokia Siemens Networks

Unlocking Objects in BSC

31 Nokia Siemens Networks

Activating the Unlock Plan in BSC

32 Nokia Siemens Networks

Verifying and Cleanup

Assigning the BTS to its final Maintenance

33 Nokia Siemens Networks

Verifying and Clean-up

34 Nokia Siemens Networks

Open CM Editor and browse into Actual part.