Configure GPRS ALU

Alcatel-Lucent GSM

Configure GPRS

MFS Document

Reconfiguration Method

Release B10

3BK 17430 0951 RJZZA Ed.10

Status RELEASED

Short title MPI95 / MDR1

All rights reserved. Passing on and copying of this document, useand communication of its contents not permitted without writtenauthorization from Alcatel-Lucent.

BLANK PAGE BREAK

2 / 52 3BK 17430 0951 RJZZA Ed.10

Contents

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.1.1 Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.1.2 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.1.3 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.1.4 Grouped Task Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

1.2 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.2.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.2.2 Site Specific Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171.2.3 External Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

1.3 Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191.4 Telecom/Supervision Outage and Operating Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221.5 Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

1.5.1 Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251.5.2 Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251.5.3 Applicable Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

2 Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2.1 Before Going Onsite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282.2 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

2.2.1 Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292.2.2 Required Knowledge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

2.3 Scenario Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302.3.1 Initial Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302.3.2 (Re)Configure Gb Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302.3.3 (Re)Configure Ater Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362.3.4 (Re)Configure Radio Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432.3.5 Test Call and GPRS Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472.3.6 Final Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

2.4 Reverse Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492.4.1 Recreate Deleted GPRS Radio Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502.4.2 Delete Created GPRS Radio Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502.4.3 Set Old Values on Modified GPRS Radio Resources . . . . . . . . . . . . . . . . . . . . . . . 51

3BK 17430 0951 RJZZA Ed.10 3 / 52

Contents

4 / 52 3BK 17430 0951 RJZZA Ed.10

Preface

Preface

Purpose This document describes how to reconfigure the Ater Mux and/or Gb interfaceand/or radio interface without physical modification of the Ater Mux.

It is applicable to BSS at technical release level B10.

What’s New In Edition 10Improvements made in Prerequisites (Section 1.2.1).

In Edition 09Improvement made in the following sections due to system evolution:

Site Specific Information (Section 1.2.2)

Scheduling (Section 1.3)

Telecom/Supervision Outage and Operating Impact (Section 1.4)

C5: Change Gb interface (Section 2.3.2.4)

Final Checks (Section 2.3.6)

In Edition 08GboIP dynamic was introduced in the following sections:

Cases (Section 1.1.1)




In Edition 07Update with the new equipment naming.

In Edition 06Updates were made in section C5: Change Gb interface (Section 2.3.2.4).

3BK 17430 0951 RJZZA Ed.10 5 / 52

Preface

In Edition 05Improvements were made in section C5: Change Gb interface (Section 2.3.2.4)

In Edition 04Delivered in release.The following sections were updated due to a system evolution:

Presentation (Section 1.1)

Cases (Section 1.1.1)

Grouped Task Sequence (Section 1.1.4)

Preparation (Section 1.2)

Prerequisites (Section 1.2.1)

Site Specific Information (Section 1.2.2)



C3.2: Create Gb Resources (Section 2.3.2.2)

C1.2, C1.4, C1.5, C3.3: Modify Gb Resources (Section 2.3.2.3)


Final Checks (Section 2.3.6)GBoIP was introdeced in the following sections:

Prerequisites (Section 1.2.1)



(Re)Configure Gb Interface (Section 2.3.2)


In Edition 03Update chapter Presentation (Section 1.1) by removing GSL condition.

In Edition 02Improvements were made due to a system evolution.

In Edition 01Improvements were made in sectionGrouped Task Sequence (Section 1.1.4)

Overall document quality was improved following an editorial review.

First official release of the document for B10.

6 / 52 3BK 17430 0951 RJZZA Ed.10

Preface

Audience This document is intended for:

Field service technicians

Site administrators

Project managers

System support engineers.

Assumed Knowledge You must have a basic understanding of the following:

Planning:

Network architecture and reshuffling principles

Scheduling.

Implementation:

Alcatel-Lucent operations and maintenance concepts for the BSS

GPRS concepts

9153 OMC-R operating in B10

Basic UNIX knowledge.

3BK 17430 0951 RJZZA Ed.10 7 / 52

Preface

8 / 52 3BK 17430 0951 RJZZA Ed.10

1 Overview

1 Overview

This Overview gives information needed by project managers and foremen, forpresentation to the customer and for site planning.

3BK 17430 0951 RJZZA Ed.10 9 / 52

1 Overview

1.1 PresentationThis scenario allows you to modify:

The Ater interface on an Ater Mux, or

The Gb interface from FR to IP and reverse, or

The Gb interface on a bearer channel, or

The radio interface on a cell.

Each interface re-configuration can be performed independently of the othersand several times, if several PCMs, bearer channels and cells are concerned.

The method applies to both the 9135 MFS and 9130 MFS Evolution. Pleasenote that in this document, the generic name MFS is used when a task appliesto both the 9135 MFS and 9130 MFS Evolution. When a task is intended foronly one type of MFS, the MFS type is clearly specified.

The different possible reconfigurations are:

Ater Mux reconfiguration:

Add GSL

Remove GSL

Increase GPRS granularity

Decrease GPRS granularity (ratio > 0%)

Delete GPRS granularity (ratio = 0%).

Gb interface reconfiguration:

Add NSE, NS-VC, SGSN_IP_ENDPOINT, PVC, bearer channel (FR-BC)

Remove NSE, NS-VC, SGSN_IP_ENDPOINT, PVC, bearer channel

Modify NS-VC, SGSN_IP_ENDPOINT, PVC, bearer channel (FR-BC).

Change the Gb interface transport mode:

From FR to IP

From IP to FR.

Radio interface reconfiguration:

GPRS parameters setting and PDCH activation on one cell to set GPRS

service on the cell

GPRS parameters modification, PDCH parameters modification on celland GPRS unlock on cell

PDCH deactivation on one cell to remove GPRS service on the cell.

According to the engineering rules:

The number of Ater Mux (BSC-MFS link) connected to the:

9135 MFS cannot be more than 8 links per GPU, and these links cannotbe connected to ports 8 to 15 of the GPU

9130 MFS Evolution cannot be more than 8 links per GPU.

10 / 52 3BK 17430 0951 RJZZA Ed.10

1 Overview

Maximum of 6 GPU boards per BSC

Ater Mux 1,2,7,8,13,14 can not be dedicated GPRS; they must go through

the TC because they carry the Q1,N7 and X25

Ater Mux that supports N7 cannot be dedicated GPRS.

3BK 17430 0951 RJZZA Ed.10 11 / 52

1 Overview

1.1.1 Cases

The following cases apply:

C1: Modification of GPRS ratio

C1.1: Increase GPRS ratio with GSL

C1.2: Decrease GPRS ratio with GSL

C1.3: Increase only GPRS ratio

C1.4: Decrease only GPRS ratio (ratio >0%)

C1.5: Delete GPRS (ratio=0%) on Ater Mux.

C2: No modification of GPRS ratio

C2.1: Delete a GSL

C2.2: Create a GSL.

C3: Gb reconfiguration

C3.1: Delete Gb resources

C3.2: Create Gb resources

C3.3: Modify Gb resources.

C4: Radio reconfiguration

C4.1: Declare GPRS on a new cell

C4.2: Delete GPRS on a cell

C4.3: Modify GPRS on a cell.

C5: Change Gb interface

C5.1: Change from Gb over FR to Gb over IP static

C5.2: Change from Gb over FR to Gb over IP dynamic

C5.3: Change from Gb over IP static to Gb over IP dynamic

C5.4: Change from Gb over IP dynamic to Gb over IP static

C5.5: Change from Gb over IP (static or dynamic) to Gb over FR.

1.1.2 Options

The following option applies in C1.1 and C1.3:

O1: Call traffic is shutdown (smoothly stopped) on all the Ater of the AterMux before increasing GPRS on it.

The following option applies in C5.1, C5.2 and C5.5:

O2: Create a new NSEI.

1.1.3 Restrictions

This method does not cover deleting the last GSL on the GPU/GP or onthe BSS.

12 / 52 3BK 17430 0951 RJZZA Ed.10

1 Overview

1.1.4 Grouped Task Sequence

The following figure shows the task sequence for the GPRS traffic configuration.

Figure 3 shows the task sequence for the Ater interface configuration orreconfiguration on an Ater Mux.

Figure 2 shows the task sequence for the Gb interface configuration orreconfiguration on a bearer channel.

Figure 4 shows the task sequence for the radio interface configuration orreconfiguration on a cell.

Inital Checks

Final Checks and Final Operations

(Re)Configure Gb Interface

(Re)Configure Ater Interface

(Re)Configure Radio Interface

OMC−R BTS

Test Call and GPRS Service

Figure 1: GPRS Traffic (Re)Configuration

3BK 17430 0951 RJZZA Ed.10 13 / 52

1 Overview

Delete Gb Resources ?

Create Gb Resources ?

Delete Gb Resources

Create Gb Resources

Modify Gb Resources

OMC−R

YesC3.1

YesC3.2

NoC3.3

NoC3.2 − C3.3

Change Gb interface ?

Change Gb interface

YesC5

NoC3

Figure 2: Gb Interface (Re)Configuration

OMC−R

ModifyGPRS

?

Increase GPRS

?

Create GSL ?

GPRSRatio = 0%

DeleteGSL ?

DeleteGSL ?

Only Delete GSL Only Create GSL

Increase GPRS with GSL

Modification

Only Increase GPRS

Increase GPRS with GSL

Modification

Delete GPRS on Ater Mux

Add GSL ?

Delete GSL ?Decrease GPRS with GSL

Modification

Decrease GPRS with GSL

Modification

Only Decrease GPRS

YesC1

NoC2

YesC2.1

NoC2.2

Yes No

YesC1.1

No

YesC1.1

NoC1.3

YesC1.2

NoC1.4

YesC1.2

No

NoYesC1.5

Figure 3: Ater Interface (Re)Configuration

14 / 52 3BK 17430 0951 RJZZA Ed.10

1 Overview

Add GPRS ?

DeleteGPRS ?

Create Radio Interface

Delete Radio Interface

Modify Radio Interface

OMC−R

YesC4.1

YesC4.2

NoC4.3

NoC4.2 − C4.3

Figure 4: Radio Interface (Re)Configuration

3BK 17430 0951 RJZZA Ed.10 15 / 52

1 Overview

1.2 Preparation

1.2.1 Prerequisites

The following prerequisites apply:

The BSS and the MFS are in service

The new PCM links (if needed) are installed

Links between the OMC-R and the MFS/BSC are available.

In case of Gb over IP the following prerequisites apply:

For 9135 MFS, replace existing hubs / switch with 1Gigabit / VLAN capable

switch (Alcatel Lucent Omniswitch 6224), use 9135 MFS MaintenanceHandbook.

For 9130 MFS Evolution, if necessary, move from 2 LANS O&M to 1 LAN

O&M, use 9130 MFS Evolution Maintenance Handbook.

Ensure that the MFS software is in validated state.

Install and configure a new router to be used for telecom. Connect the new

router with the MFS&IP network

Customer bul files with the corresponding parameters are downloaded tothe MFS.Make sure that the ’MFS start IP address’ parameter is defined in customerbul files.

The Create New VLAN task from 9130 MFS Evolution Maintenance

Handbook has been performed before changing the transport mode to IP.

Gb over IP is supported on:

9130 Evolution MFS

9135 MFS with DS10 control station equipped with Alcatel-LucentOmniStack LS 6224 switches

Before performing the change from GboFR to GboIP check the MFS

synchronization link.

If the MFS synchronization is made through the link with SGSN then thesynchronization should be changed as follows:

for MFS connected to the 9130 BSC Evolution: BSC has the capability toretrieve synchronization from the Ater packet TDM links, and synchronize

the MFS through the Ater packet TDM links

for MFS connected to the 9120 BSC: a TDM link between the TC and

the MFS .

16 / 52 3BK 17430 0951 RJZZA Ed.10

1 Overview

1.2.2 Site Specific Information

You must have the following specific information to complete the scenario:

Availability of a workstation at the OMC-R site

Server’s ’UserName’ and ’Password’

Cases and sub-cases to perform

Ater Mux number which concerns the operation

In the case of Ater interface reconfiguration, the new GPRS ratio value

and GSL creation (or not)

In the case of Gb interface reconfiguration, the parameter values to set onNS-VC/SGSN_IP_ENDPOINT, Gb_Transport_Mode or PVC objects or

bearer channel capacity. For NS-VC/SGSN_IP_ENDPOINT creation, NSEid, NS-VC id, SGSN_IP_ENDPOINT id, DLCI id parameters, and the EBS

parameter value are mandatory.

In the case of radio interface reconfiguration, the list of impacted cells andGPRS parameter values:

BSS/BSC parameters to modify

Trx_Pref_Mark

min_PDCH

max_PDCH

max_PDCH_High_Load

En_fast_initial_GPRS_access

NB_TS_MPDCH

Routing Area Code for GPRS on cell

Routing Area Color for GPRS on cell

Ps_Pref_Bcch_Trx

max_GPRS_Cs

max _EGPRS_Mcs

En_EGPRS

If the MFS is configured with GboIP, you must have the following specificinformation:

SGSN IP address

SGSN UDP port

Weight of the remote IP Endpoint for signalling traffic

Weight of the remote IP Endpoint for user traffic

Configuration of the gateway IP address.

Note: For O2 where the Gb transport mode is changed and a new NSEI is allocated,make sure you have the necessary information to create the new NSEI.

3BK 17430 0951 RJZZA Ed.10 17 / 52

1 Overview

1.2.3 External Tasks

During Gb resources creation, deletion, or modification, SGSN staff mustperform the same operation on the SGSN side.

18 / 52 3BK 17430 0951 RJZZA Ed.10

1 Overview

1.3 Scheduling

Time based on technical constraintsIn the following table, the number of resources shown does not take intoaccount individual customer or safety requirements.

Grouped TaskMSC /SGSN BTS BSC TC MFS OMC-R Time/Task

Initial Checks - - - - - 1 ope.

(25 min.)

25 min.

(Re)Configure GbInterface (C3):

- - - - - 1 ope.

Delete Gb Resources (3 min.) 3 min.

Create Gb Resources (2 min. + 3min./NS-VCor SGSN_IP_ ENDPOINT)

2 min. + 3min./NS-VCor SGSN _IP_ENDPOINT

Modify Gb Resources (2 min. + 2min. / NS-VCor 2 min.SGSN _IP_ENDPOINT)

2 min. + 2min. / NS-VCor 2 min./SGSN_IP_ENDPOINT

3BK 17430 0951 RJZZA Ed.10 19 / 52

1 Overview


Change Gb interface - - - - - 8 min.+ 4min./SGSN_IP_ENDPOINT(C5.1)

13 min.+ 4min./SGSN_IP_ENDPOINT(C5.2)



5 min.+ 4min./SGSN_IP_ENDPOINT+5 min./link(C5.5)

5 min (O2)





5 min.+ 4min./SGSN_IP_ENDPOINT+5 min./link(C5.5)

5 min (O2)

(Re)Configure AterInterface (C1, C2):

- - - - - 1 ope.

Create GSL (20 min.) 20 min.

Delete GSL (20 min.) 20 min.

Only Increase GPRS (15 min.) 15 min.

Only Decrease GPRS (15 min. + 1min./timeslot)

15 min. + 1min. / timeslot

Delete GPRS (25 min.) 25 min.

Increase GPRS with GSLModification

(25 min.) 25 min.

Decrease GPRS with GSLModification

(25 min. +1 min. /timeslot)

25 min. + 1min. / timeslot

(Re)Configure RadioInterface (C4):

- - - - - 1 ope.

20 / 52 3BK 17430 0951 RJZZA Ed.10

1 Overview


Create Radio Interface (25 min.) 25 min.

Modify Radio Interface (20 min.) 20 min.

Delete Radio Interface (15 min.) 15 min.

Test Call and GPRSService

- 1 com15 min.

(optional)

- - - 1 ope.

(26 min.)

26 min.

Final Checks - - - - - 1 ope.

(15 min.)

15 min.

TOTAL TIME - 15 min. - MIN: 1h 6min. + 15 min.(Ater) + 5 min. (Gb) + 15 min.(radio) = 1h37 min.

MAX:1h 11min. + 25min.(Ater) + 1 min./TS (Ater) +7 min. (Gb) + 25 min. (radio) =2h14 min. (with 10 timeslots).

ope. : OMC-R operator

com. : Commissioner

3BK 17430 0951 RJZZA Ed.10 21 / 52

1 Overview

1.4 Telecom/Supervision Outage and Operating ImpactThe following table describes the traffic outage and loss of supervision causedby each grouped task.

Out.Ref.

GroupedTask

Tel. / GPRSOut

Tel. / GPRSRed

Sup. Out Oper.Impact

Impacts ...

InitialChecks

- - - - None.

(Re)ConfigureGbInterface(C3)

Delete GbResources

- - - - None.

Create GbResources

None.

2 Modify GbResources

- / 5 min. or10 min. (lastNS-VC)

- - (2) GPRS reductionon Ater Mux or onGPU/GP if it is the lastNS-VC/SGSN_IP_ENDPOINTofthe GPU/GP. If it is theonly GPU/GP, there isGPRS outage.

2 Change Gbinterface

4 min. forC5.1, C5.2and C5.5

13 min. forC5.3 and C5.4

+ 5 min (forO2)

- - - (2) GPRS outage.

(Re)ConfigureAterInterface(C1,C2)

1,2

Create GSLon Ater Mux

- 35 min. - - (1) CS reduction onsecond Ater.

(2) GPRS reduction onsecond Ater.

1,2

Delete GSLon Ater Mux

- 35 min. (1) CS reduction onsecond Ater.

(2) GPRS reduction onsecond Ater.

22 / 52 3BK 17430 0951 RJZZA Ed.10

1 Overview

Out.Ref.

GroupedTask

Tel. / GPRSOut

Tel. / GPRSRed


Impacts ...

1,2

OnlyIncreaseGPRS

- 10 min. (O1)(1) / 10 min.(O1) (2)

- None.

or 10 min. if O1 isperformed.

OnlyDecreaseGPRS

- - - - None

1,2

DeleteGPRS onAter Mux

-/ - 20 min. (1) /20 min. (2)

- - None

or 20 min. if GSL existson Ater

1,2

IncreaseGPRSwith GSLModification

- 40 min. - CS and GPRSreduction on secondAter

or on Ater Mux if O1 isperformed.

1,2

DecreaseGPRSwith GSLModification

20 min.

(Re)ConfigureRadioInterface

- - - - None.

CreateRadioInterface

None.

ModifyRadioInterface

None.

DeleteRadioInterface

None.

Test Calland GPRSService

- - - - GPRS is started iflocked on the BSS orcells.

FinalChecks

- - - - None.

3BK 17430 0951 RJZZA Ed.10 23 / 52

1 Overview

Out.Ref.

GroupedTask

Tel. / GPRSOut

Tel. / GPRSRed


Impacts ...

For Ater interface:

Min: No reduction (ratio modification without GSL).

Max: 25 min. (ratio modification with GSL and O1).

For Gb interface:

Min: No reduction (ratio modification without GSL).

Max: 28 min. (Last Bearer Channel modification).

TOTAL

For Radio interface: None.

24 / 52 3BK 17430 0951 RJZZA Ed.10

1 Overview

1.5 Resources

1.5.1 Tools

The following tables describe the necessary hardware tools, software tools,and forms.

1.5.1.1 Hardware Tools

Item Part Number Use at...

GPRS mobiles equipped with SIM cards if calls have tobe performed from the BTS site.

- BTS

Laptop PC with CD-ROM reader for reading the currentdocumentation online.

OMC-R

1.5.1.2 Software Tools

Item Part Number Use at...

Customer Documentation CD with the version associatedwith the current document edition. Remember that thedocument you are reading cannot be used as a paperversion. It is online documentation using hypertext linkswhich take you to other parts of a document on the sameCD-ROM. All words in italics are hypertext links.

- OMC-R, BTS

1.5.1.3 Forms

1.5.2 Supplies

The following table describes the supplies for GPRS reconfiguration.

Item Part Number Contents Use at...

Topology regardingoperation.

- - OMC-R

1.5.3 Applicable Documents

You must have the following documents or have electronic access to thefollowing documents:

B10 BSS Methods Handbook

BSS Configuration Handbook

BSS Surveillance Handbook

Network Reconfiguration Recommendations

3BK 17430 0951 RJZZA Ed.10 25 / 52

1 Overview

26 / 52 3BK 17430 0951 RJZZA Ed.10

2 Scenario

2 Scenario

This Scenario presents all checks needed before beginning the scenario, andall detailed tasks to be performed on each site.

3BK 17430 0951 RJZZA Ed.10 27 / 52

2 Scenario

2.1 Before Going OnsiteBefore going onsite, you must check that the following information and suppliesare available:

All Prerequisites (Section 1.2.1) are met

The customer has been informed of the:

Date and time

Site name and address

Purpose of operation.

Personnel are available (refer to Scheduling (Section 1.3))

Site Specific Information (Section 1.2.2) is available

Tools (Section 1.5.1) are available and ready for operation

Supplies (Section 1.5.2) are available and ready for operation

Applicable Documents (Section 1.5.3) are available.

Ensure that the technical release level of the delivered board is in accordancewith the BSS hardware technical release document.

Ensure that the method used at the BSS site is at the same level as at theOMC-R.

28 / 52 3BK 17430 0951 RJZZA Ed.10

2 Scenario

2.2 Before You Start

2.2.1 Checks

Perform the following operations:

Check that all Prerequisites (Section 1.2.1) are met

Check the availability of all necessary Tools (Section 1.5.1) and Supplies(Section 1.5.2)

Inform the operator.

Among the cases described in Cases (Section 1.1.1) and the options describedin Options (Section 1.1.2), identify which cases and options apply to you.

2.2.2 Required Knowledge

You must be familiar with the following:

Safety Rules and Precautions


Reverse Procedure

Grouped Task Sequence (Section 1.1.4)

Operating Hints

How to document Faults and Anomalies.

3BK 17430 0951 RJZZA Ed.10 29 / 52

2 Scenario

2.3 Scenario DescriptionThis section describes how to perform GPRS logical configuration.

2.3.1 Initial Checks

Note Task Description Site To do Outage

- Perform an Audit Alarm State on the BSS. OMC-R 10 min. None.

- View Status of Managed Objects and Alarms(TC, BSC) and print them.

OMC-R 10 min. None.

- Display MFS Report and print it. OMC-R 5 min. None.

2.3.2 (Re)Configure Gb Interface

2.3.2.1 C3.1: Delete Gb ResourcesThis section describes how to delete the NSE andNS-VC/SGSN_IP_ENDPOINT.

When an NSE is deleted, all the associated NS-VC/SGSN_IP_ENDPOINTare deleted. When the NS-VC is deleted, the PVC and bearer channelare implicitly deleted. To delete a NS-VC/SGSN_IP_ENDPOINT, it mustbe previously locked. If it is the last NS-VC/SGSN_IP_ENDPOINT of theGPU/GP (multi-GPU/multi-GP), all the cells associated with the associatedNSE must be locked. If it is the last NS-VC/SGSN_IP_ENDPOINT of theBSS, the GPRS on the BSS must be previously locked. All these actionsmust be performed in synchronization with the SGSN because the NSEand NS-VC/SGSN_IP_ENDPOINT, PVC, FR-BC are deleted separately onthe MFS side and the SGSN side .


C3.1 If the last NS-VC/SGSN_IP_ENDPOINT of theBSS has to be locked ,Lock GPRS on BSS.

OMC-R 1 min. GPRS trafficstopped on BSS.

C3.1 If it is the last NS-VC/SGSN_IP_ENDPOINTon the GPU/GP, Lock GPRS on Cell fromNSEI to stop GPRS on all cells mapped onthe GPU/GP.

OMC-R 1 min. GPRS trafficstopped onGPU/GP.

C3.1 If the Gb is over FR Lock NS-VC .

If the Gb is over IP Lock SGSN_IP_ENDPOINT.

OMC-R 1 min. GPRS trafficreduction orstopped if lastNS-VC/SGSN_IP_ENDPOINT.

OMC-R 1 min. None.C3.1 If the Gb is over FR Delete NS-VC.

If the Gb is over IP DeleteSGSN_IP_ENDPOINT.

Note: Print windows before the deletion in casethe Reverse Procedure (Section 2.4) is used.

30 / 52 3BK 17430 0951 RJZZA Ed.10

2 Scenario


OMC-R 1 min. None.C3.1 Delete NSE.

Note: This action involves the reboot of theGPU/GP board, but CS traffic is not lost.

2.3.2.2 C3.2: Create Gb ResourcesIn the case of:

GboFRThis section describes how to create, on the MFS-SGSN and MFS-TClinks, NSE, NS-VC, PVC and bearer channels for one GPU/GP associatedwith the BSS.Repeat this grouped task for each GPU/GP associated with the BSS. Thiscreation must be performed in synchronization with the SGSN becausethe NSE and NS-VC, PVC, FR-BC are created separately on the MFS sideand the SGSN side and must have the same values, otherwise no GPRSpacket can be transferred between the MFS and the SGSN.

GboIPThis section describes how to create, on the MFS-SGSN and MFS-TC links,NSE, SGSN_IP_ENDPOINT for one GPU/GP associated with the BSS.Repeat this grouped task for each GPU/GP associated with the BSS. Thiscreation must be performed in synchronization with the SGSN becausethe NSE and SGSN_IP_ENDPOINT are created separately on the MFSside and the SGSN side and must have the same values, otherwise noGPRS packet can be transferred between the MFS and the SGSN.


C3.2

INPUT

If there are no Gb resources on the GPU/GP,Create NSE and Assign NSE to BSC (enter NSEIdentifier).

In the case of a multi-GPU/multi-GP, this taskmust be performed for each GPU/GP supportingGb resources.

OMC-R 2 min. None.

C3.2

INPUT

If the Gb is over FR Create NS-VC to create allrequired NS-VC.

If the Gb is over IP Create SGSN_IP_ENDPOINT.

OMC-R 2 min. perNS-VC/SGSN_IP_ENDPOINT

None.

C3.2 If the Gb is over FR Unlock NS-VC all createdNS-VC which are locked by default.

If the Gb is over IPUnlock SGSN_IP_ENDPOINTall created SGSN_IP_ENDPOINT which arelocked by default.

OMC-R 30 sec./NS-VCor 30sec./SGSN_IP_ENDPOINT

None.

C3.2 Check Gb. OMC-R 2 min. None.

3BK 17430 0951 RJZZA Ed.10 31 / 52

2 Scenario

2.3.2.3 C1.2, C1.4, C1.5, C3.3: Modify Gb ResourcesThis section describes how to modify the NS-VC/SGSN_IP_ENDPOINT, PVCparameters or bearer channel capacity.

To modify the capacity, the bearer channel must be deleted and created againby deleting the NS-VC and re-creating it. All these actions must be performedin synchronization with the SGSN .

If you want to decrease the GPRS capacity on Ater Mux (C1.2, C1.4 or C1.5)and if the Gb goes through the TC, you must decrease the Gb capacity beforereducing the Ater Mux granularity.

PVC, NS-VC, SGSN_IP_ENDPOINT Modification


OMC-R 2 min. perNS-VC.

None.C3.3 Apply this task only if the bearer channel isnot modified.

If the bearer channel is modified at the sametime as NS-VC and PVC, all the modificationsare performed during the recreation of theNS-VC.

Modify NS-VC or PVC to modify CIR, CBS,NIR, EBS, or Priority parameters.

Note: Print windows before the deletion in casethe Reverse Procedure (Section 2.4) is used.

OMC-R 2 min. perSGSN _IP_ENDPOINT

None.C3.3 Modify SGSN_IP_ENDPOINT to modify theSGSN_IP_ENDPOINT weight parameters.

Note:Print windows before the deletion in casethe Reverse Procedure (Section 2.4) is used.

C3.3 Check Gb. OMC-R 1 min. None.

Bearer Channel Modification

If you perform C1.2, C1.4 or C1.5, apply the following tasks only if the Gbgoes through the TC.


C3.3

C1.2

C1.4

C1.5

If this is the last NS-VC of the GPU/GP, LockGPRS on Cells from NSEI, if not already done.

OMC-R 1 min. START2

C3.3

C1.2

C1.4

C1.5

If this is the last NS-VC on the BSS, LockGPRS on BSS.

This task is performed from the SupervisedConfiguration (SC).

OMC-R 1 min. START2

32 / 52 3BK 17430 0951 RJZZA Ed.10

2 Scenario


C3.3

C1.2

C1.4

C1.5

Lock NS-VC. OMC-R 1 min. START2

or Reduction2.

OMC-R 1 min. Reduction2C3.3

C1.2

C1.4

C1.5

Delete NS-VC.

Note: Print windows before the deletion in casethe Reverse Procedure (Section 2.4) is used orto recreate the NS-VC in the next task.

OMC-R 2 min. Reduction2C3.3

C1.2

C1.4

C1.5

Input

Create NS-VC.

Note: Use the printed values before Gbresources modification.

C3.3

C1.2

C1.4

C1.5

Synchro

Ensure that the same NS-VC was created onthe SGSN side.

OMC-R 2 min. Reduction2

C3.3

C1.2

C1.4

C1.5

Unlock NS-VC. OMC-R 2 min. END2

or Reduction2.

C3.3

C1.2

C1.4

C1.5

Check Gb. OMC-R 1 min. Reduction2

or None.

C3.3

C1.2

C1.4

C1.5

If cells were locked, Unlock GPRS on Cellsfrom NSEI.

OMC-R 2 min. END2

or None.

C3.3

C1.2

C1.4

C1.5

If the GPRS was locked on the BSS, UnlockGPRS on BSS.

OMC-R 1 min. END2

or None.

3BK 17430 0951 RJZZA Ed.10 33 / 52

2 Scenario

2.3.2.4 C5: Change Gb interfaceThis section describes how to modify the Gb interface from FR to IP andreverse.

When performing the change from Gb over FR to Gb over IP thesynchronization link is lost and another mechanism is required. Two options arepossible, depending on the BSC type:

MFS connected to the 9130 BSC: BSC has the capability to retrieve

synchronization from the Ater packet TDM links, and synchronize the MFSthrough the Ater packet TDM links

MFS connected to the 9120 BSC: a TDM link between the TC and the

MFS is required.


OMC-R 2 min. None.C5.1

C5.2

Configure the IP gateway address for all theGPUs using Set Gateway from the MFS IMT:

for 9135 MFS, use 9135 MFS IMT User Guide

for 9130 MFS Evolution, use 9130 MFS

Evolution IMT User Guide.

Note : Perform this step for all the GPUsconnected to the impacted BSS.


C5.2

In order to configure the GPU IP address / UDPport number / mask for all the GPUs use SetGPUs IP Configuration from the MFS IMT:

for 9135 MFS, use 9135 MFS IMT User Guide

for 9130 MFS Evolution, use 9130 MFS

Evolution IMT User Guide.

Note : Perform this step for all the GPUsconnected to the impacted BSS.

C5.3

C5.4

O2

Lock GPRS on BSS OMC-R 1 min. START2

C5.3

C5.4

Lock SGSN_IP_ENDPOINT. OMC-R 1 min. Outage 2.

O2 Depending on the case Lock NS-VC or LockSGSN_IP_ENDPOINT.

OMC-R 1 min. Outage 2

OMC-R 1 min. Outage 2O2 Depending on the case Delete NS-VC or DeleteSGSN_IP_ENDPOINT.

Note : In case it is the last NS-VC /SGSN_IP_ENDPOINT, an automaticallyGP/GPU reset is triggered.

O2 Delete NSE. OMC-R 1 min. Outage 2

O2 Create new NSE OMC-R 2 min. Outage 2

34 / 52 3BK 17430 0951 RJZZA Ed.10

2 Scenario


OMC-R 1 min. Outage 2.C5.3

C5.4

Delete SGSN_IP_ENDPOINT

Note : In case it is the lastSGSN_IP_ENDPOINT, an automaticallyGP/GPU reset is triggered.

C5.2

C5.3

Modify NSE.

Set the parameter ’Gb_Configuration_Type’ to 1(dynamic configuration).

OMC-R 5 min. Outage 2.

Only for C5.3

C5.4 Modify NSE.

Set the parameter ’Gb_Configuration_Type’ to0 (static configuration).

OMC-R 5 min. Outage 2.

C5.1

C5.2

C5.3

C5.4

If neccesary, Create SGSN_IP_ENDPOINT, foreach NSE corresponding with the BSS.

OMC-R 2 min./SGSN_IP_ENDPOINT

Outage 2.

Only for C5.3and C5.4

C5.1

C5.2

C5.3

C5.4

Unlock SGSN_IP_ENDPOINT; all createdSGSN_IP_ENDPOINT which are locked bydefault.

OMC-R 2 min./SGSN_IP_ ENDPOINT

Outage 2.

Only for C5.3and C5.4

C5.5 If neccesary, Create NS-VC, for each NSEcorresponding with the BSS.

OMC-R 2min./NS-VC

Outage 2

C5.5 Unlock NS-VC; all created NS-VC which arelocked by default.

OMC-R 2min./NS-VC

Outage 2.

C5.3

C5.4

O2

If GPRS was locked on the BSS, Unlock GPRSon BSS.

OMC-R 1 min. END2

OMC-R 4 min. START2

END2

C5.1

C5.2

Change the Gb interface from FR to IP, using SetGb Transport Mode for BSS.

Note : The change of transport mode willreset all the GPUs attached to the impactedBSS.

WARNING : If the reset of GPUs, attachedto the impacted BSS, is not done, performthe reset manually, using the IMT.

C5.5 Install TDM cables between MFS and targetSGSN.

MFS 5 min./ link None.

3BK 17430 0951 RJZZA Ed.10 35 / 52

2 Scenario


C5.5

EXCH

Inform the MFS site that the SGSN is configuredto support frame relay.

MFS 1 min. None.

OMC-R 4 min. START2

END2

C5.5 Change the Gb interface from IP to FR, usingSet Gb Transport Mode for BSS.

Note : The change of transport mode willreset all the GPUs attached to the impactedBSS.

WARNING : If the reset of GPUs, attachedto the impacted BSS, is not done, performthe reset manually, using the IMT.

2.3.3 (Re)Configure Ater Interface

2.3.3.1 C2.2: Create GSL on Ater MuxThis task consists of adding a GSL channel. Note that it is not possible tocreate a GSL on a mixed or dedicated Ater Mux with 0% GPRS.


OMC-R 2 min. START1

START2

C2.2 Shutdown Traffic on One Ater of the second Aterof Ater Mux with WTC = 1 min.

Note: This task is suitable because duringthe GSL creation, the second DTC of theAter Mux is automatically reset.

If the ATR is carrying a GSL, a warningmessage appears. To continue with theoperation, confirm the message.


Reduction2

C2.2 Create GSL Channel.

When a question appears, click on [ OK ].

The configuration state in the BSC part of the"Ater Supervision" window becomes ’In progress’.

Wait until it becomes ’Available’.

During the audit, the following message appears:Abis/Ater view is not up to date! It

will be reloaded.

Click on [ OK ].

Note: After GSL creation, the BSCautomatically blocks Ach becoming GSL,and the OMC-R automatically performs BSChardware/alarm/state audits and updatesSM (and possibly TC) adapt transmission onBSC (and possibly TC) side.

The GSL is always created in a locked state.

C2.2 Align GPRS Configuration on One TP .

(The MFS part of the "Ater Supervision" Windowis then updated).


Reduction2

C2.2 Unlock Traffic on One Ater of the second Ater ofthe Ater Mux.

OMC-R 1 min. END1

END2

36 / 52 3BK 17430 0951 RJZZA Ed.10

2 Scenario


C2.2 Unlock GSL. OMC-R 1 min. None.

C2.2 Check Ater. OMC-R 1 min. None.

2.3.3.2 C2.1: Delete GSL on Ater Mux

Do not perform this grouped task if the GSL to remove is the last active GSLbecause this means deleting the GPRS.


OMC-R 1 min. GPRS traffic reducedon BSS.

C2.1 Lock GSL (not the last one).

If this is not successful, it means this is the lastactive GSL.

OMC-R 2 min. START1

START2

C2.1 Shutdown Traffic on One Ater of the secondAter of the Ater Mux with WTC = 1 min.

Note: This task is suitable because during theGSL deletion, the second DTC of the Ater Mux isautomatically reset.

If the ATR is carrying a GSL, a warning messageappears. Confirm the message to continue withthe operation.


Reduction2

C2.1 Delete GSL Channel.


The configuration state in the BSC part ofthe "Ater Supervision" window becomes ’Inprogress’.


During the audit, the following messageappears: Abis/Ater view is not up to

date! It will be reloaded.

Click on [ OK ].

Note: After GSL deletion, the BSC automaticallyblocks Ach becoming GSL, and the OMC-Rautomatically performs BSC hardware / alarm /state audits and updates SM (and possibly TC)adapt transmission on the BSC (and possibly TC)side.

C2.1 Align GPRS Configuration on One TP.

(The MFS part of the "Ater Supervision"window is then updated).


Reduction2

C2.1 Unlock Traffic on One Ater of the secondAter of the Ater Mux.

OMC-R 1 min. END1

END2


3BK 17430 0951 RJZZA Ed.10 37 / 52

2 Scenario

2.3.3.3 C1.3, O1: Only Increase GPRS on Ater MuxThis task consists of increasing the GPRS ratio on the Ater Mux withoutmodifying the GSL.

The MSC is automatically aware of timeslots becoming Gic. To avoid loss ofcalls on Cic timeslots becoming Gic, the operator can optionally stop thetraffic on the Ater Mux.


OMC-R 1 min. GPRS trafficreduced on BSS.

C1.3

O1

Lock GSL (not the last one).


OMC-R 5 min. START1

START2

C1.3

O1

Shutdown Traffic on Ater Mux of the Ater Muxwith WTC = 4 min., because Ach becomingGch will be blocked and ongoing calls willbe lost. Note: If the Ater Mux supports the last active

N7, the shutdown operation fails. Execute thenext tasks but ongoing calls will be lost.



Reduction2

or NONE

C1.3

INPUT

Configure GPRS Granularity, giving theGPRS ratio.




Note: If increasing the GPRS, the BSCautomatically blocks (towards MSC) Achbecoming Gic or GSL, which involves lossof ongoing calls on these Ach and theOMC-R possibly updates SM and TC adapttransmission on the TC side, if Gb goesthrough the TC.




Reduction2

or None.

C1.3

O1

Unlock GSL. OMC-R 1 min. Reduction1

Reduction2

C1.3

O1

Unlock Traffic on Ater Mux of all the Ater ofthe Ater Mux.

OMC-R 3 min. END1

END2


38 / 52 3BK 17430 0951 RJZZA Ed.10

2 Scenario

2.3.3.4 C1.4: Only Decrease GPRS on Ater MuxThis task consists of decreasing (still > 0%) the GPRS ratio on the Ater Muxwithout explicitly modifying the GSL if it is activated on the Ater Mux.

The MSC is automatically aware of Gic timeslots becoming Cic.



INPUT

Configure GPRS Granularity giving the GPRSratio.




During the audit, the following messageappears: Abis/Ater view is not up to

date! It will be reloaded.

Click on [ OK ].

Note: The OMC-R automatically locksGch becoming Cic, which involves lossof GPRS traffic on these Gch, and theOMC-R possibly updates SM and TC adapttransmission on the TC side if Gb goesthrough the TC.

C1.4 Align GPRS Configuration on One TP


OMC-R 1 min. None.

C1.4 Unlock Released CS Time Slot to unlock Gictimeslots that became Cic.

OMC-R 1 min./ timeslot.

None.


2.3.3.5 C1.5: Delete GPRS on Ater MuxThis task consists of setting the GPRS ratio to 0%.

The GSL is implicitly deleted and therefore must be previously locked. TheMSC is automatically aware of Gic timeslots becoming Cic.


C1.5 If GSL is activated on the Ater Mux, LockGSL (not the last one).

OMC-R 1 min. GPRS reduced onthe BSS.

OMC-R 2 min. START1C1.5 If GSL exists on the Ater Mux, ShutdownTraffic on One Ater of the second Ater ofAter Mux with WTC=1 min. Note: This task is suitable because, during the

GSL deletion, the second DTC of the Ater Mux isautomatically reset.


3BK 17430 0951 RJZZA Ed.10 39 / 52

2 Scenario



or None.

C1.5

INPUT

Unreserve Ater Time Slot for GPRS.

If and when a question appears, click on[ OK ].

The configuration state in the BSC part ofthe "Ater Supervision" window becomes’In progress’.


During the audit, the following messageappears: Abis/Ater view is not up

to date! It will be reloaded.

Click on [ OK ].

Note: The OMC-R automatically locks Gchbecoming Cic, which involves loss of GPRS trafficon these Gch.

Then, the BSC resets the DTC2 of the Ater Muxand the OMC-R automatically performs BSChardware/alarm/state audits and possibly updatesSM and TC adapt transmission on the TC side ifGb goes through the TC.

C1.5 Align GPRS Configuration on One TP

(The MFS part of the ’Ater Supervision’window is then updated).


or None.

C1.5 If the second Ater of the Ater Mux waslocked, then Unlock Traffic on One Ater.

OMC-R 1 min. END1

C1.5 If it is a mixed Ater Mux, then UnlockReleased CS Timeslot.

OMC-R 1 min./ timeslot.

None.


2.3.3.6 C1.1, O1: Increase GPRS with GSL ModificationThis task consists of increasing the GPRS ratio on the Ater Mux and modifyingthe GSL.

The MSC is automatically aware of Cic timeslots becoming Gic. To avoidloss of calls on Cic timeslots becoming Gic, the operator can optionally stopthe traffic on the Ater Mux.


OMC-R 1 min. GPRS trafficreduced on BSS.

C1.1 If GSL is activated on Ater Mux (notthe last one), Lock GSL (not the lastone).


OMC-R 5 min. START1

START2

C1.1

O1 / INPUT

Shut Down Traffic on Ater Mux of theAter Mux with WTC= 4 min., becauseAch becoming Gch will be blockedand ongoing calls will be lost. Note: This task fails if the Ater Mux supports

the last the last N7. Execute the next tasks butongoing calls will be lost.


40 / 52 3BK 17430 0951 RJZZA Ed.10

2 Scenario


OMC-R 1 min. START1

START2

C1.1 If the option is not performed,Shutdown Traffic on One Ater of thesecond Ater of the Ater Mux withWTC = 1 min. Note: This task is suitable because during the GSL

creation or deletion, the second DTC of the AterMux is automatically reset.


If the ATR supports the last active GSL, ongoingcalls will be lost.


Reduction2

C1.1

INPUT

Configure GPRS Granularity, givingthe GPRS ratio, modifying the GSL,and setting TC transparency if Gbgoes through the TC.

When a question appears, click on[ OK ].

The configuration state in the BSCpart of the "Ater Supervision" windowbecomes ’In progress’.


During the audit, the followingmessage appears: Abis/Ater view

is not up to date! It will be

reloaded. Click on [ OK ].

Note: A GSL is needed if there are none. It isstrongly recommended if there is only one. A GSLis always created in the locked state.

After Ater timeslot reservation, the BSCautomatically blocks Ach becoming Gch and, afterGSL creation, the BSC resets the DTC2 of the AterMux. Then, the OMC-R automatically performsBSC hardware/alarm/state audits and updates TCand SM adapt transmission on BSC and TC sides.

C1.1

O1

Unlock Traffic on Ater Mux. OMC-R 2 min. END1

END2

OR

Reduction1

Reduction2

C1.1 If the option was not been performed,then Unlock Traffic on One Ater of thesecond Ater of the Ater Mux.

OMC-R 1 min. END1

END2

C1.1 Align GPRS Configuration on OneTP.

(The MFS part of the "AterSupervision" window is thenupdated).

OMC-R 1 min. None.

C1.1 Unlock GSL to unlock the GSL if ithas been activated.

OMC-R 1 min. None.

3BK 17430 0951 RJZZA Ed.10 41 / 52

2 Scenario

2.3.3.7 C1.2, O1: Decrease GPRS with GSL ModificationThis task consists of decreasing the GPRS ratio on the Ater Mux and modifyingthe GSL.

The MSC is automatically aware of Gic timeslots becoming Cic.


C1.2 If GSL is activated (not the last one) onthe Ater Mux, Lock GSL

OMC-R 1 min. GPRS reducedon the BSS

OMC-R 3 min. START1

START2

C1.2

O1

Shutdown Traffic on One Ater of thesecond Ater of the Ater Mux withWTC=2 min.

Note: This task is suitable because during theGSL modification, the second DTC of the AterMux is automatically reset.

If the Ater Mux supports the last active GSL,ongoing calls on the second Ater will be lost.



Reduction2

C1.2

INPUT

Configure GPRS Granularity; givingthe GPRS ratio, activating GSLor deactivating GSL, setting TCtransparency if Gb goes through the TC.

When a question appears, click on[ OK ].

The configuration state in the BSCpart of the "Ater Supervision" windowbecomes ’In progress’.


During the audit, the following messageappears: Abis/Ater view is not up

to date! It will be reloaded.

Click on [ OK ].

Note: The OMC-R automatically locks Gchbecoming Cic, which involves loss of GPRStraffic on these Gch and the OMC-R possiblyupdates SM and TC adapt transmission on theTC side if Gb goes through the TC.

C1.2

O1

Unlock Traffic on One Ater of the secondAter of the Ater Mux.

OMC-R 1 min. END1

END2



OMC-R 1 min. None.

C1.2 Unlock Released CS Time Slot to unlockGic timeslots that became Cic.

OMC-R 1 min. /timeslot.

None.

C1.2 Unlock GSL if GSL is activated. OMC-R 1 min. None.

42 / 52 3BK 17430 0951 RJZZA Ed.10

2 Scenario

2.3.4 (Re)Configure Radio Interface

2.3.4.1 C4.1: Create Radio InterfaceThis task consists of setting GPRS radio parameters on cells.


C4.1 Create PRC (PRC1). OMC-R 1 min. None.

C4.1

INPUT

Copy OMC Cells to PRC (impacted cells fromSupervised Configuration into PRC1).

OMC-R 1 min. None.

C4.1 Create PRC (backup PRC) in restricted mode, tosave the current configuration for the ReverseProcedure (Section 2.4).

OMC-R 1 min. None.

C4.1 Copy OMC Cells to PRC (all cells from PRC1into backup PRC).

OMC-R 1 min. None.

C4.1 Synchronize PRC with SC (here backup PRC) OMC-R 1 min. Outage 2

C4.1 Check PRC (backup PRC) without forcing thecell administrative state.

OMC-R 1 min. None.

C4.1 Close PRC (backup PRC). OMC-R 30 sec. None.


INPUT

Set BSS/BSC Telecom Parameters in PRC1 toupdate parameters if needed. This task includesthe modification of CAE data specific to the MFS. Note: The duration depends on the number

of parameters to modify. The currentexample uses 10 parameters in differentwindows.

3BK 17430 0951 RJZZA Ed.10 43 / 52

2 Scenario



INPUT

To add GPRS on the cell or to modify GPRSparameters on one cell because the values toset are different between cells, Set Cell TelecomParameters in working PRC1.

Modify at least the following parameters that arenot filled when GPRS is created on the cell:

Routing Area Code

Routing Area Color

Max_PDCH (must be different from 0 to have

GPRS on the cell).

You can also modify:

Min_PDCH

NB_TS_MPDCH

Max_PDCH_High_Load


Ps_Pref_Bcch_Trx

max_GPRS_Cs

max _EGPRS_Mcs

En_EGPRS

To have GPRS on an extended cell:

MAX_PDCH, MAX_PDCH_HIGH_LOADand MIN_PDCH must have even values

NB_TS_MPDCH must be set to 0 when the

cell type is extended inner/outer

MAX_EGPRS_MCS is MCS4

EN_NACC, EN_PSI_STATUS and

EN_STREAMING are disabled

Note: To have GPRS on the cell,Trx_Pref_Mark must be 0. To modifyit for a block of TRX, use the JavaScript Set/Update Circuit/Packet MarkConfiguration Using Script.

Note: To modify only one cell, use the edit

cell command (see Set Cell TelecomParameters).

Note: If En_fast_initial_GPRS_access isset to ’Enable’, respect the following rule:

Min_PDCH >=En_fast_initial_GPRS_access +NB_TS_MPDCH.

C4.1 Synchronize PRC with SC (PRC1) OMC-R 1 min. Outage 2

C4.1 Check PRC (check all without forcing the celladministrative state).

OMC-R 3 min. None.

OMC-R 5 min. None.C4.1 Activate PRC with cell clean-up (in queuedmode, without forcing the cell administrativestate). Note: The duration depends on the number

of cells in the PRC.

C4.1 Close PRC (PRC1). OMC-R 1 min. None.

44 / 52 3BK 17430 0951 RJZZA Ed.10

2 Scenario

2.3.4.2 C4.3: Modify Radio InterfaceThis task consists of modifying GPRS radio parameters on cells or on the BSC.It also includes modification of TRX Pref.Mark on TRXs. This task is alsoperformed to unlock GPRS on cells.


C4.3 Create PRC (PRC2). OMC-R 30 sec. None.

C4.3

INPUT


OMC-R 1 min. None.

C4.3 Create PRC, in restricted mode, and backupPRC2 to save the current configuration for theReverse Procedure (Section 2.4).

OMC-R 30 sec. None.

C4.3 Copy OMC Cells to PRC (all cells from PRC2into backup PRC2).

OMC-R 1 min. None.

C4.3 Synchronize PRC with SC (backup PRC2) OMC-R 1 min. None

C4.3 Check PRC (backup PRC2) without forcingcell administrative state.

OMC-R 1 min. None.

C4.3 Close PRC (backup PRC2). OMC-R 30 sec. None.


INPUT

Set BSS/BSC Telecom Parameters in PRC2to update GPRS parameters, if needed. Thistask includes the modification of CAE dataspecific to the MFS.

Note: The duration depends on the number ofparameters to modify. The current exampleuses 10 parameters in different windows.


INPUT

If GPRS parameters have to be modified oncell(s) then, Edit n Cells in PRC2.

Modify parameters such as :

Min_PDCH

Max_PDCH_High_Load

Max_PDCH


NB_TS_MPDCH

Routing Area Code

Routing Area Color

Ps_Pref_Bcch_Trx

max_GPRS_Cs

max _EGPRS_Mcs

En_EGPRS

Note: If the TRX Pref.mark must be modifiedon a block of TRX, do not modify it herebecause it is done with the Java ScriptSet/Update Circuit/Packet Mark ConfigurationUsing Script.



Note: If En_fast_initial_GPRS_access is setto ’Enable’, respect the following rule:

Min_PDCH >= En_fast_initial_GPRS_access+ NB_TS_MPDCH.

C4.3 Synchronize PRC with SC(here PRC2) OMC-R 1 min. None

3BK 17430 0951 RJZZA Ed.10 45 / 52

2 Scenario


C4.3 Check PRC (PRC2 Check all without forcingthe cell administrative state).

OMC-R 3 min. None.

OMC-R 5 min. None.C4.3 Activate PRC in queued mode and withcell clean-up (PRC2 without forcing the celladministrative state). Note: The duration depends on the number

of impacted cells.


2.3.4.3 C4.2: Delete Radio InterfaceThis task consists of removing GPRS on cells by setting MAX_PDCH = 0.


C4.2 Create PRC (PRC3). OMC-R 30 sec. None.

C4.2

INPUT


OMC-R 1 min. None.

C4.2 Create PRC, in restricted mode, backupPRC3 to save the current configuration for theReverse Procedure (Section 2.4).

OMC-R 30 sec. None.

C4.2 Copy OMC Cells to PRC (all cells from PRC3into backup PRC3).

OMC-R 1 min. None.

C4.3 Synchronize PRC with SC (backup PRC3 OMC-R 1 min. None

C4.2 Check PRC (backup PRC3) without forcing thecell administrative state.

OMC-R 1 min. None.

C4.2 Close PRC (backup PRC3). OMC-R 30 sec. None.


INPUT

Select all impacted cells, using Edit n Cells .

SetMAX_PDCH=0,MAX_PDCH_HIGH_LOAD=0and MIN_PDCH =0, and if there are cellsdefined with MPDCH, set NB_TS_MPDCHto ’disable’ for each cell of the GPU/GP.If GPRS fast acces was used, setEN_fast_initial_GPRS_acces to ’disable’.

Note: The duration depends on the numberof impacted cells.



C4.3 Synchronize PRC with SC (here PRC3) OMC-R 1 min. None

C4.2 Check PRC (PRC3 Check all without forcingcell administrative state).

OMC-R 3 min. None.

OMC-R 5 min. None.C4.2 Activate PRC in queued mode and withcell clean-up (PRC3 without forcing the celladministrative state). Note: The duration depends on the number

of impacted cells.


46 / 52 3BK 17430 0951 RJZZA Ed.10

2 Scenario

2.3.5 Test Call and GPRS Service

If tests are unsuccessful, apply the Reverse Procedure (Section 2.4).

In the first step, GPRS on the BSS must be unlocked (if it is locked) to allowGPRS traffic on the BSS. Then, calls are performed on modified Ater Muxsupporting Circuit traffic. If calls succeed, GPRS tests are performed onmodified Ater Mux supporting GPRS traffic.

2.3.5.1 Unlock GPRS on Cells


- If GPRS is locked on cells because of first Gbresource creation, Unlock GPRS on Cells fromNSEI.

OMC-R 2 min.

2.3.5.2 Unlock GPRS on BSSThis step only needs to be performed when the GPRS is locked on the BSS.


- If GPRS locked on the BSS because of firstGb resource creation, Unlock GPRS on BSS.

OMC-R 2 min.

2.3.5.3 Test Calls


BTS 15 min. None.- If there is very little traffic on the modified AterMux supporting circuit, then perform calls using amobile to test these Ater Mux. This task is optional .

- Display USD Detailed DTC Information byselecting DTCs on which Busy Ach > 0.

OMC-R 2 min. None.

Check If explicit calls are performed from the BTSsite , check in the DTC report that each call issuccessful.

When no explicit call is launched from the BTSsite , observe different DTC reports and refreshthe view regularly.

OMC-R 5 min. None.

3BK 17430 0951 RJZZA Ed.10 47 / 52

2 Scenario

2.3.5.4 Test GPRS


BTS 15 min. None.- If there is very little traffic on modified Ater Muxsupporting GPRS, then perform GPRS callsusing a mobile to test these Ater Mux. This task is optional .

- Display USD Detailed DTC Information byselecting DTCs on which Busy Ach > 0.

OMC-R 2 min. None.

Check Check in the DTC report that each GPRS call issuccessful and print the DTC-report.

Observe different DTC reports and refresh theview regularly.

OMC-R 15 min. None.

2.3.6 Final Checks


Check Perform an Audit Alarm State on the BSC and TC. OMC-R 10 min. None.

- View Status of Managed Objects and Alarms(BSC, TC) and compare with the report printedduring the Initial Checks (Section 2.3.1).

OMC-R 10 min.

Display MFS Report and compare with the reportprinted during the Initial Checks (Section 2.3.1).

OMC-R 5 min. None.

C4.1

C4.2

Reshuffle Cell/GPU Mapping. OMC-R 1 min. 4 min. foreach cellremappedon anotherGPU/GP.

Data trafficoutage only.

- Delete PRC (PRC 1,2,3) if there are no problems. OMC-R 1 min. None.

C5.5 Delete SGSN_IP_ENDPOINT OMC-R 1 min. None.

C5.1

C5.2

Delete NS-VC OMC-R 1 min. None.

C5.1

C5.2

Unlink MFS TP from SGSN and after disconnectthe cable between the MFS TP and SGSN.

OMC-R 1 min. None.

C5.5 In case there is no BSS left using the Gb over IPlink disconnect the cable between the MFS andthe router leading to the IP network.

OMC-R 1 min. None.

48 / 52 3BK 17430 0951 RJZZA Ed.10

2 Scenario

2.4 Reverse ProcedureUse this procedure to reverse the network modifications described in thisscenario.

The reverse procedure to apply depends on the modifications that wereperformed:

For Ater Mux reconfiguration:

If the GSL was deleted, create it again using C2.2: Create GSL on

Ater Mux (Section 2.3.3.1)

If the GSL was created, delete it usingC2.1: Delete GSL on Ater Mux

(Section 2.3.3.2)

If the GPRS granularity was increased, use C1.4: Only Decrease GPRSon Ater Mux (Section 2.3.3.4) or C1.2, O1: Decrease GPRS with GSL

Modification (Section 2.3.3.7), or delete GPRS granularity using C1.5:

Delete GPRS on Ater Mux (Section 2.3.3.5)

If the GPRS granularity was decreased, increase it using C1.1, O1:Increase GPRS with GSL Modification (Section 2.3.3.6).

For Gb interface reconfiguration:

If Gb resources were deleted, create them using C3.2: Create GbResources (Section 2.3.2.2)

If Gb resources were created, delete them using C3.1: Delete Gb

Resources (Section 2.3.2.1)

If Gb resources were modified, modify them using C1.2, C1.4, C1.5,

C3.3: Modify Gb Resources (Section 2.3.2.3).

For radio interface reconfiguration:

If GPRS radio resources were deleted, recreate them using RecreateDeleted GPRS Radio Resources (Section 2.4.1)

If GPRS radio resources were created, delete them using Delete CreatedGPRS Radio Resources (Section 2.4.2)

If GPRS radio resources were modified, modify them using Set Old

Values on Modified GPRS Radio Resources (Section 2.4.3).

For changing the Gb interface:

From IP (static or dynamic)to FR use case C5.5 from section C5:

Change Gb interface (Section 2.3.2.4)

From IP dynamic to IP static use case C5.4 from section C5: Change Gb

interface (Section 2.3.2.4)

From IP static to IP dynamic use case C5.3 from section C5: Change Gbinterface (Section 2.3.2.4)

From FR to IP dynamic use case C5.2 from section C5: Change Gbinterface (Section 2.3.2.4)

From FR to IP static use case C5.1 from section C5: Change Gb

interface (Section 2.3.2.4)

3BK 17430 0951 RJZZA Ed.10 49 / 52

2 Scenario

2.4.1 Recreate Deleted GPRS Radio Resources

If radio parameters were modified and GPRS was deleted, reset old valuesand recreate the GPRS using the backup PRC3.


- Open PRC (backup PRC3). OMC-R 1 min.

- Activate PRC (backup PRC3 in queued mode,without forcing the cell administrative state andwithout cell clean-up).

OMC-R 4 min.

- Close PRC (backup PRC3). OMC-R 1 min.

- Reshuffle Cell/GPU Mapping. OMC-R 1 min. 4 min. for eachcell remappedon anotherGPU/GP.


2.4.2 Delete Created GPRS Radio Resources

If radio parameters were modified and GPRS was created, reset the old valuesand delete the GPRS using the backup PRC1.


- Open PRC (backup PRC1). OMC-R 1 min.

- Activate PRC (in queued mode, without forcingthe cell administrative state and without cellclean-up).

OMC-R 4 min.

- Close PRC (backup PRC1). OMC-R 1 min.

- Reshuffle Cell/GPU Mapping. OMC-R 1 min. 4 min. foreach cellremappedon anotherGPU/GP.


50 / 52 3BK 17430 0951 RJZZA Ed.10

2 Scenario

2.4.3 Set Old Values on Modified GPRS Radio Resources

If radio parameters were modified or the PDCH group was modified, reset theold values using the backup PRC2.


- Open PRC (backup PRC2) OMC-R 1 min.

- Activate PRC (in queued mode, without forcingthe cell administrative state and without cellclean-up).

OMC-R 4 min.

- Close PRC (backup PRC 2). OMC-R 1 min.

3BK 17430 0951 RJZZA Ed.10 51 / 52

2 Scenario

BLANK PAGE BREAK

52 / 52 3BK 17430 0951 RJZZA Ed.10

Date post:	26-Oct-2014
Category:	Documents
Upload:	dayanidhi-panda
View:	157 times
Download:	6 times