Vous êtes sur la page 1sur 48

Alcatel-Lucent GSM

Extend Ater Mux Interface


BSC & TC Document
Reconfiguration Method
Release B10
3BK 17430 1021 RJZZA Ed.09
Status RELEASED
Short title MPI102 / MDR1
All rights reserved. Passing on and copying of this document, use
and communication of its contents not permitted without written
authorization from Alcatel-Lucent.
BLANK PAGE BREAK
2 / 48 3BK 17430 1021 RJZZA Ed.09
Contents
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.1.1 Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.1.2 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.1.3 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.1.4 Grouped Task Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.2 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.2.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.2.2 Site Specific Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.2.3 External Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.3 Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.4 Telecom / Supervision Outage and Operating Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.5 Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1.5.1 Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1.5.2 Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1.5.3 Applicable Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2 Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.1 Before Going Onsite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.2 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.2.1 Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.2.2 Required Knowledge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.3 Scenario Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.3.1 Initial Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.3.2 C1.2, C2.2: Prepare Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.3.3 C1.1, C2.1: Modify BSC Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.3.4 Final Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2.3.5 Final Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.4 Reverse Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.4.1 Remove Added Ater Mux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.4.2 Reduce Configuration Logically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
2.4.3 Remove Hardware and Final Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
2.5 Scenario Specific Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.5.1 Ater Mux Extension in Existing and in New Added 9125 Compact TC Rack . . 44
2.5.2 Ater Mux Extension in 9125 TC with TC Rack Reconfiguration . . . . . . . . . . . . . . 45
2.5.3 Cable A Interface for MT120 Board Insertion in G2 TC . . . . . . . . . . . . . . . . . . . . . 47
2.5.4 Cable JBFAN for MT120 Board Insertion in G2 TC . . . . . . . . . . . . . . . . . . . . . . . . . 47
3BK 17430 1021 RJZZA Ed.09 3 / 48
Contents
4 / 48 3BK 17430 1021 RJZZA Ed.09
Preface
Preface
Purpose This document describes how to extend the Ater Mux Interface.
It is applicable to BSS at technical release level B10.
Whats New In Edition 09
Sections Activate HSL (only for 9130 BSC Evolution, if needed) (Section
2.3.2.5), De-activate HSL (only for 9130 BSC Evolution, if needed) (Section
2.4.2.1) were updated.
In Edition 08
Update with the new equipment naming.
In Edition 07
Section Presentation (Section 1.1) was updated.
In Edition 06
Update of system title.
In Edition 05
Delivered in release.
The following sections were improved due to system evolution changes:
Site Specific Information (Section 1.2.2)
Connect PCMs (Section 2.3.2.4)
Disconnect PCMs (Section 2.4.3.2)
Activate HSL (only for 9130 BSC Evolution, if needed) (Section 2.3.2.5)
De-activate HSL (only for 9130 BSC Evolution, if needed) (Section 2.4.2.1)
Scheduling (Section 1.3)
First official release of the document for B10 MR2.
In Edition 04
3BK 17430 1021 RJZZA Ed.09 5 / 48
Preface
Improvements were made in sections:
Activate HSL (only for 9130 BSC Evolution, if needed) (Section 2.3.2.5)
De-activate HSL (only for 9130 BSC Evolution, if needed) (Section 2.4.2.1)
The following sections were updated due to system evolution changes:
Site Specific Information (Section 1.2.2)
Connect PCMs (Section 2.3.2.4)
Disconnect PCMs (Section 2.4.3.2)
6 / 48 3BK 17430 1021 RJZZA Ed.09
Preface
In Edition 03
Restrictions 3BKA20FBR213361 and 3BKA20FBR209551 were removed from
section Activate HSL (only for 9130 BSC Evolution, if needed) (Section 2.3.2.5)
In Edition 02
Restriction 3BKA20FBR213361 was introduced in section Activate HSL (only
for 9130 BSC Evolution, if needed) (Section 2.3.2.5).
Restriction 3BKA20FBR209551 was introduced in section Activate HSL (only
for 9130 BSC Evolution, if needed) (Section 2.3.2.5).
In Edition 01
Improvements were made in sections Activate HSL (only for 9130 BSC
Evolution, if needed) (Section 2.3.2.5) and De-activate HSL (only for 9130 BSC
Evolution, if needed) (Section 2.4.2.1)
The following sections were updated as a result of system evolution changes:
Scheduling (Section 1.3)
Telecom / Supervision Outage and Operating Impact (Section 1.4)
Activate HSL (only for 9130 BSC Evolution, if needed) (Section 2.3.2.5)
De-activate HSL (only for 9130 BSC Evolution, if needed) (Section 2.4.2.1)
Presentation (Section 1.1)
Cases (Section 1.1.1)
Sections Activate HSL (only for 9130 BSC Evolution, if needed) (Section
2.3.2.5) and De-activate HSL (only for 9130 BSC Evolution, if needed) (Section
2.4.2.1) were improved following system evolution changes.
Section Grouped Task Sequence (Section 1.1.4) has been modified according
to the system behavior.
Section De-activate HSL (only for 9130 BSC Evolution, if needed) (Section
2.4.2.1) was updated.
Improvements were made in sections and due to system evolution:
Presentation (Section 1.1)
Applicable Documents (Section 1.5.3)
Improvements are made in section: Presentation (Section 1.1)
3BKA80CBR197035
- HSL restriction was removed from sections Cases (Section 1.1.1), Activate HSL (only for 9130
BSC Evolution, if needed) (Section 2.3.2.5), and De-activate HSL (only for 9130 BSC Evolution, if
needed) (Section 2.4.2.1).
Overall document quality was improved following an editorial review.
First official release of the document for B10.
3BK 17430 1021 RJZZA Ed.09 7 / 48
Preface
Audience This document is intended for:
Field service technicians
Specialists
Project managers
Foremen.
Assumed Knowledge You must have a basic understanding of the following:
Alcatel-Lucent operations and maintenance concepts for the BSS
BSC Terminal operation
Transmission Terminal operation
TC Terminal operation for 9125 TC
9153 OMC-R operation.
8 / 48 3BK 17430 1021 RJZZA Ed.09
1 Overview
1 Overview
This Overview gives information needed by project managers and foremen, for
presentation to the customer and for site planning.
3BK 17430 1021 RJZZA Ed.09 9 / 48
1 Overview
1.1 Presentation
This scenario explains how to extend the TC configuration by adding Ater
Mux connections.
The TC extension is allowed only if the number of the Ater Mux connections
defined at the TC site is less than MAX_ATERMUX_TPV1 value.
The scenario is applicable when:
Adding new Ater Mux on an existing or added G2 TC rack
Adding new Ater Mux on an existing or added 9125 TC rack
The extension operation may concern several BSCs as the 9125 Compact
TC is multi-BSC. In this case, the scenario must be repeated for each
concerned BSC.
The method applies to both the 9120 BSC and 9130 BSC Evolution.
For 9130 BSC Evolution, if you want to add ML-PPP links, perform all the tasks
related to the case C2.1: Add ML-PPP links from the Change IP Extraction
Mode for 9130 BSC Evolution document, after completing this method.
The G2 TC supports two generations of boards:
G2 TC, where one Ater Mux is managed by a set of one ASMC board and,
for each attached Ater, one ATBX and two DT16 boards
9125 TC, where one Ater Mux and the attached four Aters are managed
by a single MT120 board.
For G2 TCs, you must take into account the following:
A G2 TC configuration supports a maximum of three racks.
A new rack is only introduced when the existing one is full. If the existing
G2 TC rack has MT120 boards (all or only some boards), then the new
rack must be an 9125 rack. Otherwise, the operator must decide between a
G2 TC rack and an 9125 TC rack.
The first rack (when a G2 TC rack) can be extended with one or two G2 /
9125 TC racks, as shown in the cases a) to f) in Figure 1.
TC rack numbering must adhere to the following rules:
For a G2 TC rack added to an existing G2 TC rack, the rack number is
incremented by one
For 9125 TC, the rack numbers range from 5 to 15
For an 9125 TC rack added to an existing G2 TC rack, the 9125 TC rack
number is 5. If a second 9125 TC rack is added, then its number is
incremented by one (5 + 1 = 6).
10 / 48 3BK 17430 1021 RJZZA Ed.09
1 Overview
Figure 1: Possible Cases for G2 TC Rack Extension
The following rules apply for GPRS:
In the G2 TC rack, the ASMC+TRCU/MT120 boards remain unused for a
dedicated Ater Mux
The following Ater Mux cannot be dedicated:
Ater Mux 1, 2, 7, 8, 13, 14 because they carry Q1 and X25/IP
Any Ater Mux carrying the N7.
Maximum number of links on one GPU:
Is eight BSC-MFS links
In cascading synchronization mode of the MFS, the sum of BSC-MFS
links + MFS-TC links + MFS-SGSN cannot be greater than eight. These
links cannot be connected from ports 8 to 15 of the GPU.
The method is intended for both the 9130 BSC Evolution and 9120 BSC. Note
that the generic name BSC is used when a task applies to both the 9130 BSC
3BK 17430 1021 RJZZA Ed.09 11 / 48
1 Overview
Evolution and 9120 BSC. When a task is intended for only one type of BSC,
the BSC type is clearly specified.
In the case of an 9130 BSC Evolution, the platform is developed on Advanced
Telecom Computing Architecture (ATCA) standards. The following table
describes the standalone MXBSC configuration.
Configuration
Type
1 2 3 4 5
Capacity Nb TRX 200 400 600 800 1000
ATCA Shelf 1
Nb
active
CCP
1 2 3 4 5
Nb
OMCP
2 2 2 2 2
Nb
spare
CCP
1 1 1 1 1
Nb TP
GSM
2 2 2 2 2
Nb ATCA boards
Nb SSW 2 2 2 2 2
LIU Shelf 1
Nb boards LIU Nb MUX 2 2 2 2 2
Nb LIU 8 8 14 15 16
In the case of an 9130 BSC Evolution, there is one TSC VCE per TC cluster.
One TC cluster is composed of 6 Atermux, as for the 9120 BSC.
If there is not enough room on the TC rack to insert all the boards related to
the new Ater Mux, the existing Ater Mux connections of the impacted BSC
rack have to be moved to another 9125 TC rack.
The B9 9130 BSC Evolution supports 48 Ater Muxes (30 CS and 18 PS).
For a B10 9130 BSC Evolution, the number of ATER-HWAY-TP CS/PS is
increased. Consequently, the ATER-HWAY-TP CS are numbered from 1 to 30
and from 61 to 76. The ATER-HWAY-TP PS are numbered from 31 to 58. The
ATER-HWAY-TP 59 and 60 can be used for HSL or PS.
In case it is necessary to replace E1 links with STM1 or vice versa, see E1 to
STM1 Configuration or STM1 to E1 Configuration, as needed.
12 / 48 3BK 17430 1021 RJZZA Ed.09
1 Overview
1.1.1 Cases
The following cases apply:
C1: Ater Mux extension in a G2 TC
C1.1: Logical extension only (complementary to C1.2)
C1.2: TC hardware preparation only (complementary to C1.1)
C1.3: Add ASMC, ATBX, DT16 boards
C1.4: Add MT120 boards.
C2: Ater Mux extension in an 9125 Compact TC/ 9125 TC equipped with TC
STM1IP subrack
C2.1: Logical extension only (complementary to C2.2)
C2.2: TC hardware preparation only (complementary to C2.1) and add
MT120 boards
C3: Prepare for Ater Mux Extension going through the TC and carrying
GPRS traffic.
For a complete extension of the services, you must apply C1.1, C2.1 and C1.2,
C2.2. Once both the logical extension and hardware preparation are performed,
it is recommended to open the service as soon as possible.
For additional racks, the following cases apply:
C4: Extension of one or more BSCs in an existing 9125 TC rack (see
Ater Mux Extension in Existing and in New Added 9125 Compact TC
Rack (Section 2.5.1))
C5: Extension in a newly added 9125 TC rack (see Ater Mux Extension in
Existing and in New Added 9125 Compact TC Rack (Section 2.5.1))
C6: Reconfiguring the existing 9125 TC rack (see Ater Mux Extension in
9125 TC with TC Rack Reconfiguration (Section 2.5.2)).
C7: Activate HSL (only for 9130 BSC Evolution, if needed).
When an 9125 TC rack reconfiguration is needed, first apply Move BSS from a
9125 TC to Another.
If the Ater Mux will be via satellite, then apply Activate Ater via Satellite after
completing the tasks in this document.
When a mixed CS / GPRS link is needed, apply Move Direct CS Link into Mixed
CS / GPRS Link after completing the tasks in this document.
3BK 17430 1021 RJZZA Ed.09 13 / 48
1 Overview
1.1.2 Options
The following options apply:
O1: Put in service only some of the Aters (at least one) belonging to a
new Ater Mux
O2: Add Ater Mux supporting an N7 link
O3: TC extension concerns a new BSC.
1.1.3 Restrictions
The following restrictions apply:
Ater Mux belonging to the same 9120 BSC rack cannot be shared, for any
reason, between two different TC racks (even if the concerned TC racks
are 9125 TC racks)
Only an 9125 TC rack can be shared by several BSSs (even if this last
is connected to G2 TC rack(s)).
14 / 48 3BK 17430 1021 RJZZA Ed.09
1 Overview
1.1.4 Grouped Task Sequence
The following figure shows the grouped task sequence for this scenario.
Initial Checks
Insert TC Boards
Connect PCM Inform MSC
OMCR Site BSC Site TC Site
Prepare
Hardware
Modify BSC Configuration
Program Transmission
Unlock New Ater Mux
Test Ater Interface
Final Checks
Final Operations
Configure TC
Set Parameters (C1.3)
Identify and Note the
New TC Config (C2)
Figure 2: Extend Ater Mux Interface
3BK 17430 1021 RJZZA Ed.09 15 / 48
1 Overview
1.2 Preparation
1.2.1 Prerequisites
The following prerequisites apply:
Sufficient resources are available at the MSC to handle the additional load
required by the extension
The current BSC configuration is able to support the TC extension.
Otherwise, first apply the Extend BSC method
If Ater Mux via satellite is planned, then apply Activate Ater via Satellite
after this procedure.
For C1.3:
All ATBX boards for existing Ater Mux must be present in the TC rack, even
if some Aters are locked.
For C1.2 or C2.2:
Each TC rack is supplied complete with internal cables. This means that the
extensions do not involve changing or adding internal cables.
For TC boards to be inserted, check the TC Labelling Reference
PCM links between the MSC-TC and the BSC-TC are available, qualified
but not connected
For C1.2, C1.4 or C5:
If a new rack is necessary, then commissioning and cabling with the previous
rack must already be performed
When a new 9125 TC rack is needed, it must be installed and commissioned
(with the required MT120 boards). At factory level, the MT120 boards will be
filled from lower to higher subrack and from left to right. However, if during
site installation phase the PCM cables enter the rack from the top, the MT120
boards filling order begins from higher to lower subrack and from left to right.
16 / 48 3BK 17430 1021 RJZZA Ed.09
1 Overview
For C2:
For Ater Mux extension in an 9125 TC, you must know the concerned BSC
racks and the number of concerned MT120 boards
Check if there are free spaces within the existing 9125 Compact TC racks
for the concerned BSC. Note that only one given 9125 TC rack can handle
all Ater Mux belonging to a specific 9120 BSC rack
Depending on the BSCs that must be extended in terms of Ater Mux, and
depending on the remaining free spaces for the new MT120 boards, you can
reassign MT120 boards when combining C5 and C6, using Move BSS from
a 9125 TC to Another. TC rack-reconfiguration must be optimized in order to
reduce the outage of each extension operation.
For C3:
When a mixed CS / GPRS link is needed, you have to apply Move Direct CS
Link into Mixed CS / GPRS Link after this procedure.
1.2.2 Site Specific Information
You must have the following information to complete the scenario:
The impedance of the TC rack
The existing TC configuration (the number of existing Ater Mux and
supported boards). Note the TC rack / shelf / slot versus the BSC identifier /
Ater Mux identifier
The X.25/IP extraction point
The identity of the generic settings that must be locally downloaded (via
the TC terminal) on the added MT120 boards
The software version that must be locally downloaded (via the TC terminal)
on the added MT120 boards
The number of Ater Mux per BSC to be extended
The new TC configuration:
How many new Ater Muxes, which new boards, and where they go
Which will be the non-used Ater on which Ater Mux
Which new Aters will support the N7 link
How many racks in the new configuration, and the hardware generation
of the added rack, if any
How many new Ater Muxes, and the hardware generation of the added
boards
If an 9125 TC rack is added, will it be controlled by the same BSC as the
previous G2 TC rack(s) or by a new 9120 BSC.
MTP_Sequence_Number_Format (normal/extended)
3BK 17430 1021 RJZZA Ed.09 17 / 48
1 Overview
1.2.3 External Tasks
Inform MSC staff about:
New, added Ater Mux
Reduced Ater Mux
Modified Ater Mux.
1.3 Scheduling
Note: Time based on technical constraints
In the following table, the number of resources shown does not take into
account individual customer or safety requirements.
Grouped Task MSC BSC TC BTS OMC-R Time / Task
Initial Checks - - - - 1 ope. 15 min.
Prepare Hardware 1 ope. 1 Com 1 Team - 1 ope. 1 h 46 min./ 9120 BSC
+ 1 h/ Ater Mux
2 h 48 min./ 9130 BSC
Evolution + 1 h 2 min./
Ater Mux + 3 min. 30
sec./ TC board + 5
min./PCM
Modify BSC
Configuration
- 1 Com - - 1 ope. 24 min. in case of 9120
BSC
up to 36 min. in case of
9130 BSC Evolution
Final Operations - 1 Com - - 1 ope. 40 min. + 40 min./ Ater
Mux in the case of an
9120 BSC
1h 5 min. + 23 min./
Ater Mux in the case of
an 9130 BSC Evolution
Final Checks - 1 Com - - 1 ope. 15 min
TOTAL TIME max: 3 h 17 min. + 1
h 40 min./ Ater Mux in
case of 9120 BSC
max: 3 h 56 min. + 1 h
25 min./ Ater Mux + 3
min. 30 sec./ TC board
+ 5 min./PCM in case
of 9130 BSC Evolution
ope. : OMC-R Operator
Com : BSC Commissioner
Team : 2 commissioners, in order to gain time onsite for operational tasks
18 / 48 3BK 17430 1021 RJZZA Ed.09
1 Overview
1.4 Telecom / Supervision Outage and Operating Impact
The following table describes the traffic outage and loss of supervision caused
by each grouped task.
Out. Ref. Grouped Task Tel. Out Tel. Red
Sup.
Out
Oper.
Impact Impacts...
- Initial Checks - - - - None.
1 Prepare Hardware 47 min.
+ 3
min. 30
sec./TC
board
- - None.
- Modify BSC
Configuration
- - - None.
- Final Operations - - - - None.
- Final Checks - - - - None.
TOTAL TIME 47 min.
+ 3
min. 30
sec./TC
board
- - - None.
3BK 17430 1021 RJZZA Ed.09 19 / 48
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 ...
Installation tools - TC
PC terminal with associated cables and Eicon card (for an
9120 BSC)
- BSC
PC terminal with associated cable - TC
Laptop PC with CD-ROM for reading current documentation
online
- BSC, TC
1.5.1.2 Software Tools
Item Part Number Use at ...
BSC Terminal for logical extension / reduction - BSC
Transmission terminal for local download of TC
transmission settings
- TC
9125 TC Terminal for declaring and downloading the
MT120 boards
- TC
Customer Documentation CD with the version associated
with the current document edition. Remember that the
document you are reading cannot be used as a paper
version. It is online documentation using hypertext links
which take you to other parts of a document on the same
CD-ROM. All words in italics are hypertext links.
- BSC, TC, OMC-R
1.5.1.3 Forms
None.
20 / 48 3BK 17430 1021 RJZZA Ed.09
1 Overview
1.5.2 Supplies
The table below describes the necessary supplies.
Item Part Number Contents Use at ...
Site Documentation - - TC, BSC, OMC-R
C1.3: One ASMC, four ATBX boards per Ater
Mux
Two DT16 boards per used Ater (eight DT16
boards for a complete Ater Mux)
- - TC
C1.4/C2.2: One set of MT120 + JBFAN boards
and associated cable 3BK07741AFAA (per Ater
Mux)
- - TC
1.5.3 Applicable Documents
You must have the following documents or have electronic access to the
following documents:
B10 BSS Methods Handbook
BSS Configuration Handbook
BSS Surveillance Handbook
Network Reconfiguration Recommendations
Transcoder Hardware Description
Transmission Terminal User Guide
9125 Compact TC Terminal User Guide
BSC Functional Units Configurations.
BSC Terminal User Guide
Change IP Extraction Mode for 9130 BSC Evolution
3BK 17430 1021 RJZZA Ed.09 21 / 48
1 Overview
22 / 48 3BK 17430 1021 RJZZA Ed.09
2 Scenario
2 Scenario
This Scenario presents all checks needed before beginning the scenario, and
all detailed tasks to be performed on each site.
3BK 17430 1021 RJZZA Ed.09 23 / 48
2 Scenario
2.1 Before Going Onsite
Before going onsite, you must check that the following information and supplies
are 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 accordance
with the BSS hardware technical release document.
Ensure that the method used at the BSS site is at the same level as at the
OMC-R.
24 / 48 3BK 17430 1021 RJZZA Ed.09
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 and materials
Inform the operator.
Among the cases described in Cases (Section 1.1.1) and the options described
in 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
Telecom / Supervision Outage and Operating Impact (Section 1.4)
Reverse Procedure
Grouped Task Sequence (Section 1.1.4)
Operating Hints
How to document Faults and Anomalies.
3BK 17430 1021 RJZZA Ed.09 25 / 48
2 Scenario
2.3 Scenario Description
This section describes how to extend an Ater Mux interface.
There are two main subcases for this method:
Either you perform only a logical extension (C1.1 / C2.1) OR you perform
only a hardware extension (C1.2 / C2.2), OR
You perform the entire method for a logical and a hardware extension.
2.3.1 Initial Checks
Note Task Description Site To do Outage
- Perform a BSS Audit Alarm State . OMC-R 10 min. None.
OMC-R 5 min. None. - View Status of Managed Objects and Alarms for
TC and print the results.
Note: New Ater Mux are already represented,
but only in the BSC view. There are no
new TC related boards and no new Ater_TP
represented.
2.3.2 C1.2, C2.2: Prepare Hardware
2.3.2.1 Identify and Note New 9125 TC Configuration
This task helps you to identify your cases. If the conclusion is:
Either C4 and / or C5, then there is no outage
C6 or even C5+C6, then there is some outage for the operations
For all cases (C4, C5, C6), note all that must be done in terms of MT120
board assignment or reassignment (mapping TC rack / shelf / slot versus
BSC identifier / Ater Mux identifier)
For C6, inform the MSC as soon as possible about the planned modifications
For C5 and C6, you must use Move BSS from One 9125 TC to Another.
Note Task Description Site To do Outage
- Identify the TC rack to be extended and the number
of free spaces.
TC 5 min. None.
- For the 9120 BSC, use BSC Configuration Cabinet
Layouts to find out the number of the newly added
Ater Mux in each BSC rack.
BSC 5 min. None.
26 / 48 3BK 17430 1021 RJZZA Ed.09
2 Scenario
Note Task Description Site To do Outage
C4
CHECK
1
If there are enough free spaces in the existing TC
rack for all the Ater Mux to be added, then the
extension is performed in this rack.
TC 5 min. None.
C4
C5
O3
CHECK
2
If there are free spaces for only a part of the
BSC racks concerned by the extension, then the
extension is performed in the existing racks and in
a new, added TC rack.
TC 5 min. None.
C5
C6
CHECK
3
If it is acceptable to fill the free spaces in the
existing TC rack with the Ater Mux from the
concerned BSC, reconfiguration can be done in
this TC rack. For this, it is necessary to identify the
BSC rack (other than the concerned BSC) with the
fewest connections and to move them to the new,
added TC rack, applying Move BSS from One 9125
TC to Another.
TC 10 min. None.
3BK 17430 1021 RJZZA Ed.09 27 / 48
2 Scenario
2.3.2.2 Insert TC Boards
When an MT120 board is inserted in an empty TC shelf, the shelf must first be
powered ON.
Do not handle boards without using an anti-static wrist strap.
All new processors are installed after the power is switched on. All added
processors then enter their bootstrap, run their self-test, and wait until they
are ordered to be loaded.
For C5 and C6, you must use Move BSS from One 9125 TC to Another.
Note Task Description To do Outage
C2.2 Log on to the 9125 TC Compact Terminal,
using Log On, Check Parameters Settings
and then connect to the 9125 TC, as
described in Connect and Disconnect.
TC 3 min. None.
C1.2
C2.2
Look at the Physical Description of the boards
to be inserted.
TC 10 min. None.
TC 5 min./ Ater
Mux
None. C1.3 For each new Ater Mux, insert one ASMC
board and for each used Ater, one ATBX
board + two DT16 boards.
Note: Even if you do not foresee using all Aters
on an added Ater Mux, it is mandatory to insert
the ATBX board of each unused Ater (but not the
DT16 boards).
TC 5 min./ Ater
Mux
None. C1.4
C2.2
For each new Ater Mux, insert the MT120
boards one-by-one and, if it is a G2 TC rack
(C1.4), also insert the associated JBFAN
boards.
Also, cable the JBFAN board so it will be
monitored by the MT120 board (refer to Cable
JBFAN for MT120 Board Insertion in G2 TC
(Section 2.5.4)).
In C1.4, connect the 9125 TC Terminal to the
MT120 board as described in Connect and
Disconnect.
Note: In an 9125 TC rack, insert the MT120 in
a free space.
In a G2 TC rack, insert the MT120 board in place
of an ASMC board (refer to Cable A Interface for
MT120 Board Insertion in G2 TC (Section 2.5.3))
and insert the JBFAN board nearby in a place
usually used for an ATBX board.
C2.2 If, in the TC window, the BSC Comparison
Check panel automatically opens, follow the
on-screen indications and pay attention to the
warnings displayed in the panel.
TC 1 min./ Ater
Mux
None.
C1.3 Check the TC LED meanings ASMC O&M,
ATBX O&M, TP16 O&M (DT16) for LED
indications after the power ON.
TC 2 min. None.
28 / 48 3BK 17430 1021 RJZZA Ed.09
2 Scenario
2.3.2.3 Configure TC
The following section describes how to declare / configure new board(s) in the
TC and how to download them with the correct software.
Note: In case it is necessary to replace E1 links with STM1 see E1 to STM1
Configuration.
Note Task Description Site To do Outage
TC 25 min./ Ater
Mux
None. C1.3 Write Data to ASMB and ASMC
Boards (the ASMC boards) and
Write Data to ATBX Boards.
Note: You must also download the generic settings of the
ATBX boards associated with the Aters that will not be
used.
TC 5 min. None. C1.4
C2.2
C5
Check that the inserted MT120
boards are visible at the 9125 TC
Compact Terminal, in the right
place, using
Locate a Board in TCC for
G2/9125 TC
or
Locate a Board in TCC for 9125
TC equipped with TC STM1IP
subrack.
In the case of a new, added TC
rack, move the TC terminal to the
new TC rack.
Do not handle boards without using an anti-static wrist
strap.
TC 15 min. +
2 min./ Ater
Mux
None. C1.4
C2.2
Check if the software version is
the required one, using
View the Software Inventory for
G2/9125 TC
or
View the Software Inventory
for 9125 TC equipped with TC
STM1IP subrack.
If the required software version is
not present on the boards,
Download Software via TCC for
G2/9125 TC from the PC
or
Download TCIF Software for 9125
TC equipped with TC STM1IP
subrack.
Note: When inserting MT120 board(s) in a G2 TC rack
(C4.2), connect to each board separately and download
the software.
3BK 17430 1021 RJZZA Ed.09 29 / 48
2 Scenario
Note Task Description Site To do Outage
TC 3 min./ board None. C1.4
C2.2
For the MT120 boards where
the new software was previously
downloaded, Activate Software
from TCC if G2/9125 TC
or
Activate TCIF Software if 9125
TC equipped with TC STM1IP
subrack.
Note: When inserting MT120 board(s) in a G2 TC rack
(C4.2), connect to each board separately and activate the
software.
TC 2 min. None. O3
C1.4
C2.2
When the extension concerns a
new BSC, it must be declared at
the TC side. Declare a New BSC
when G2/9125 TC to append the
BSC managing the new boards
on the list of BSCs connected to
this 9125 TC rack.
In case the used TC is equipped
with STM1IP subrack use the
link Declare a New BSC when TC
with STM1IP subrack.
Note: When inserting MT120 board(s) in a G2 TC rack
(C1.4), the BSC name is not relevant.
TC 2 min./ Ater
Mux
None. C1.4
C2.2
Configure the Qmux and
Hardware for G2/9125 TC
or
Configure the Qmux and
Hardware for 9125 TC equipped
with TC STM1IP subrack to
declare new boards as managed
by the involved BSC; to set
the Ater Mux number for each
one; and to set the Qmux time
slot and nibble for the Ater Mux
connections with the Qmux link.
Note 1: Only for the new boards inserted in free spaces.
Note 2: When inserting MT120 board(s) in a G2 TC rack
(C1.4), the BSC name is not relevant.
30 / 48 3BK 17430 1021 RJZZA Ed.09
2 Scenario
Note Task Description Site To do Outage
C1.4
C2.2
Before generating an inventory
for the boards introduced in the
TC, update the information in the
TC Terminal by
Modifying Site Information for
G2/9125 TC
or
Manage Site Information for /9125
TC with TC STM1IP subrack
and then
Generate a Board Inventory for
G2/9125 TC
or
Generate a Board Inventory
for 9125 TC with TC STM1IP
subrack to modify the hardware
inventory of each concerned TC
rack.
TC 3 min. /TC
rack
-
TC 2 min./ board - C1.4
C2.2
Load the generic transmission
data settings for the TC, using
Online Configuration for G2/9125
TC
or
Online Configuration for 9125 TC
with TC STM1IP subrack.
Generic transmission settings
can be found on the PC in:
Program File\Alcatel\TC
terminal\generic_settings
Note: Load the generic settings file on every board
according to the Site Specific Information (Section 1.2.2).
In the case of X.25/IP routed over the A interface, load the
files with the X.25/IP connection only for the first two Ater
Mux of the BSC and the files without X.25/IP for the others!
- Disconnect the TC Terminal from
the 9125 TC, using Connect and
Disconnect.
TC 1 min. None.
3BK 17430 1021 RJZZA Ed.09 31 / 48
2 Scenario
2.3.2.4 Connect PCMs
The following section tells you how to connect PCMs.
Note: These PCM connections only concern the new boards previously inserted in a
free TC rack / shelf / slot.
Note Task Description Site To do Outage
BSC, TC 5 min./ Ater
Mux
None. C1.2
C2.2
Connect the PCM links between the BSC
and the TC. For MT120 boards, check the
connections in the
Overview Panel for G2/9125 TC
or
Overview Panel for 9125 TC equipped with TC
STM1IP subrack.
Note: Ater Mux and connected Aters must be
red, with a C on them.
TC, MSC 15 min./ Ater
Mux
None. C1.2
C2.2
Connect the PCM links between the MSC and
the TC.
Note: In order to save time, both connections
can be done in parallel and, also in parallel
with the TC board insertion.
C3 If the extended Ater Mux goes through the TC
and carries GPRS Traffic, connect the Ater Mux
link between the BSC and the MFS - DDF input.
BSC, MFS-
DDF
5 min. None.
C3 If the extended Ater Mux goes through the TC
and carries GPRS Traffic, connect the Ater Mux
link between the MFS - DDF output and the TC.
MFS-DDF,
TC
5 min. None.
C3 Connect the input of the MFS and the output of
the MFS in DDF with a strap (jumper).
MFS-DDF 5 min. None.
C7 Connect the PCM(s) between the BSC and the
MSC.
BSC-MSC 5 min./PCM None.
32 / 48 3BK 17430 1021 RJZZA Ed.09
2 Scenario
2.3.2.5 Activate HSL (only for 9130 BSC Evolution, if needed)
The following section describes how to activate the High Speed Signaling
Link (HSL).
When the command to activate the HSL is received by the BSC, the traffic
stops and the DLS is updated.
Note: In order to activate HSL, the following have to be applied:
Before HSL activation, ensure that the PCMs between the MSC and the
BSC LIU are directly cabled
The change of MTP_Sequence_Number_Format parameter has to be done
synchronized on both sides, MSC and BSC, to decrease the outage and to
prevent the following combinations:
BSC in extended and MSC in normal
MSC in extended and BSC in normal
Ensure that at the end of the procedure the same
MTP_Sequence_Number_Format is used on both sides (9130 BSC
Evolution and MSC).
Note Task Description Site To do Outage
C7 Allow Alarm Reporting on Ater Mux
(BSC side) corresponding to the
two PCMs on which the HSL will be
activated. Ensure that there are no
alarms.
OMC-R 2 min./ Ater
Mux
None
C7 Shut Down BSS Traffic: BSS-Tel
(WTC=4 min.)
OMC-R 5 min. START 1
BSC 25 min. OUTAGE 1 C7 Activate HSL.
Note 1: If needed, set the
MTP_Sequence_Number_Format to
extended.
Note 2: During the BSC reset, at the MSC site,
change the N7 configuration from LSL to HSL.
Note 3: The TC related boards are also updated
during the BSC reset.
C7 For each board carrying N7 (each
MT120 or ASMC and related ATBX),
Lock Board.
OMC-R 30 sec./ board OUTAGE 1
C7 For each board carrying N7 (each
MT120 or ASMC and related
ATBX),Unlock Board.
OMC-R 3 min. /board OUTAGE 1
OMC-R 15 min. OUTAGE 1 C7 Unlock BSS traffic (unlock BSS-TEL).
Audits are automatically triggered.
3BK 17430 1021 RJZZA Ed.09 33 / 48
2 Scenario
Note Task Description Site To do Outage
C7 If N7 links are locked, Unlock N7 links
(each link separately) from the OMC-R
OMC-R 2 min. END 1
OMC-R 10 min. None C7 Launch the BSC Hardware Audit for the
BSC SBLs.
The MFS GPRS configuration is misaligned
after this operation in the case of mixed Atermux
configured with the following GPRS ratios: 50%,
75%, 100%.
C7 If the MFS GPRS configuration is
misaligned, Resynchronize GPRS on
the MFS.
OMC-R 5 min. None
34 / 48 3BK 17430 1021 RJZZA Ed.09
2 Scenario
2.3.2.6 Inform MSC
The following section describes how to inform the MSC.
Note Task Description Site To do Outage
EXCH Inform MSC staff about the newly added Ater
Mux and also the modified Ater Mux, if there is
reconfiguration.
OMC-R/ MSC 5 min. None.
- Check the PCM numbering and if there are
differences between the BSC and the MSC, then
modify on the BSC side. Configure A-Interface
(Modify CICs).
OMC-R 5 min. None.
- Check the SLC numbering and if there are
differences between the BSC and the MSC, then
modify on the BSC side. Configure A-Interface
(Modify SLCs).
OMC-R 5 min. None.
2.3.3 C1.1, C2.1: Modify BSC Configuration
This command, from the BSC terminal, triggers the extension process on the TC
side. The BSC DLS integrates the new TC configuration but the new TC-related
boards do not appear on the OMC-R (refer to Final Operations (Section 2.3.4)).
Note Task Description Site To do Outage
BSC 6 min. max None. C1.1
C2.1
Modify BSC/TC Configuration but only for
TC-related parameters. The New Config BSC
field must be filled with "*****". The New Config
TC must be filled in according to the number of
new added Ater Mux.
Note: After the command activation, a
BSC-HW-RESYNCH message appears on the BSC
terminal.
OMC-R max 18 min.
in case of
9120 BSC
up to 30 min
in case of
9130 BSC
Evolution
None. C1.1
C2.1
The OMC-R automatically triggers a hardware
and alarm audit.
At the end of the audit, the new Ater Mux
appears on the TC side.
The new TC-related boards are not yet
visible on the OMC-R in this BSSUSM Main
View.
Note: Wait for the end of the audit before trying
any other action. A message appears after the
hardware Audit: Abis/Ater view is not up
to date ! It will be reloaded! Click on
[ OK ].
3BK 17430 1021 RJZZA Ed.09 35 / 48
2 Scenario
2.3.4 Final Operations
2.3.4.1 Program Transmission
After C1.1, C2.1: Modify BSC Configuration (Section 2.3.3), the BSC waits
for the following command from the BSC terminal to start programming the
network elements at the TC side (new boards). To do that, the BSC first polls
the new TC-related boards and, when the polling is finished, the new boards
are loaded and finally appear on the OMC-R.
Note Task Description Site To do Outage
BSC For 9120 BSC 10 min.
-20 min./ added Ater
Mux.
For 9130 BSC Evolution,
up to 3 min./ added
Ater-Mux + 15 min.
None. - Program Transmission. When this command is
activated, a report is received. It contains the
number of NE successfully configured, NE with
access failure and NE with download failure. Wait
(the duration depends on the number of added
Ater Mux) to see a BSC-HW-RESYNCH message (on
the BSC terminal) sent by the BSC to the OMC-R.
Note: If the program transmission report
shows that some of the NEs (adaptors) are
not successfully programmed, check if the
expected boards are all present in the right
place and initialize them manually, using the
BSC terminal.
OMC-R 20 min. in the case of
an 9120 BSC, up to 30
min. in the case of an
9130 BSC Evolution
Evolution.
None. - The BSC-HW-RESYNCH message triggers an
automatic audit at the OMC-R. At the end of the
audit, new shelves with the added boards appear
in the BSS Main View. IF DURING THE AUDIT,
new boards have not finished loading, then they
appear at the OMC-R with a clock symbol. In this
case, perform another alarm state audit manually
at the end of the automatic one.
Note 1: At the end of the audit, if there
are missing boards, then you will have one
warning per missing board.
Note 2: A message appears after the
hardware Audit: Abis/Ater view is not
up to date ! It will be reloaded!
Click on [ OK ].
2.3.4.2 C1.3: Set Parameters
The following section describes how to set the parameters.
Note Task Description Site To do Outage
C1.3 Create Transcoder Configuration Files. Adjust the
Trau Loudness parameter for the DT16 boards.
TC 2 min./ Ater
Mux
None.
C1.3 Enable / Disable ATBX CRC4 Process. Modify the
CRC4, if necessary. For this, check the CRC4 at
the MSC.
TC 2 min./ Ater
Mux
None.
36 / 48 3BK 17430 1021 RJZZA Ed.09
2 Scenario
2.3.4.3 Unlock New Ater Mux
To open the service on the new added Ater Mux, you must unlock them and,
in addition, for:
O1: Lock some Aters on an added Ater Mux
O2: Unlock the N7 link if the Ater Mux supports N7.
Note Task Description Site To do Outage
- If the Ater Mux are not already unlocked, Unlock
Traffic on Ater Mux.
OMC-R 2 min./
Ater Mux
None.
C1.2
C2.2
Enable alarms on the Ater Mux, using Allow
Alarm Reporting on Ater Mux (BSC and TC
sides).
OMC-R 2 min./
Ater Mux
None.
O2 Unlock RSL, N7 Support Resource (N7). OMC-R 2 min./
Ater Mux
None.
- Enable alarm reporting on each A TP, using
Allow Alarm Reporting on One A TP.
OMC-R 5 min./
Ater Mux
None.
O1 Lock the unused Aters. First, inhibit alarms
associated with each Ater, using Inhibit Alarm
Reporting on One A TP. Then, lock each
concerned Ater, using Lock Traffic on One Ater.
OMC-R 5 min./
Ater Mux
None.
2.3.4.4 Test Ater Interface
The following section describes how to test the Ater interface.
Note Task Description Site To do Outage
OMC-R 15 min. None. - Perform calls using the new Ater resources.
Display USD Detailed DTC Information.
Note: If calls on the new resources are
unsuccessful, then apply the Reverse Procedure
(Section 2.4).
C3 Disconnect the strap (jumper) between the
input of the MFS and the output of the MFS
in the DDF and prepare for the introduction
of the MFS.
MFS-DDF 5 min. None.
3BK 17430 1021 RJZZA Ed.09 37 / 48
2 Scenario
2.3.5 Final Checks
Note Task Description Site To do Outage
- Perform a BSS Audit Alarm State. OMC-R 10 min. None.
- View Status of Managed Objects and Alarms for the
TC and print the results. Compare with the results
from the Site Specific Information (Section 1.2.2).
OMC-R 5 min. None.
38 / 48 3BK 17430 1021 RJZZA Ed.09
2 Scenario
2.4 Reverse Procedure
2.4.1 Remove Added Ater Mux
2.4.1.1 Lock Ater Mux
Note Task Description Site To do Outage
O2 Lock RSL, N7 Support Resource (N7). OMC-R 2 min./ Ater
Mux
-
- First, inhibit alarms for the whole Ater Mux with Inhibit
Alarm Reporting on Ater Mux (BSC and TC side).
Then, lock the associated Aters with Lock Traffic on
Ater Mux.
OMC-R 5 min./ Ater
Mux
-
2.4.1.2 Free Ater Mux at TC Terminal
Note: In case it is necessary to replace STM1 links with E1 see STM1 to E1
Configuration.
Note Task Description Site To do Outage
C2 Log on to the TC terminal (if not yet done). Then,
for each TC rack concerned by any Ater Mux to be
removed, Connect and Disconnect (connect to the
TC terminal).
TC 3 min./
concerned
TC rack
-
TC 10 min./
Ater Mux
- C2 For each Ater Mux to be removed:
Locate a Board in TCC for G2/9125 TC or
Locate a Board in TCC for 9125 TC equipped
with TC STM1IP subrack(the MT120 module
concerned by any of the Ater Mux to be removed)
Use Configure the Qmux and Hardware for
G2/9125 TC or Configure the Qmux and
Hardware for 9125 TC equipped with TC
STM1IP subrack so that the MT120 board
is no longer assigned to the concerned BSC
(temporarily assign it to a previously created
dummy BSC).
Note: The MT120 board is now free to be
reassigned to another BSC / Ater Mux or
to be physically removed from the TC rack
(but wait before doing this last action).
C2 If the removed Ater Mux was the last one (in the
rack) belonging to a given BSC, then remove the
BSC from the list of BSCs that are handled by the
concerned TC rack (or change it to a dummy BSC
name and number), using Declare a New BSC
when G2/9125 TC. In case the used TC is equipped
with STM1IP subrack use the link Declare a New
BSC when TC with STM1IP subrack.
TC 5 min. -
3BK 17430 1021 RJZZA Ed.09 39 / 48
2 Scenario
2.4.2 Reduce Configuration Logically
2.4.2.1 De-activate HSL (only for 9130 BSC Evolution, if needed)
The following tasks deactivate the HSL. When this command is received by
the BSC, the traffic stops and the DLS is updated.
Note: In order to de-activate HSL, the following have to be applied:
After the HSL de-activation, disconnect the PCMs between the MSC and
the BSC LIU
The change of MTP_Sequence_Number_Format parameter has to be done
synchronized on both sides, MSC and BSC, to decrease the outage and to
prevent the following combinations:
BSC in extended and MSC in normal
MSC in extended and BSC in normal
Ensure that at the end of the procedure the same
MTP_Sequence_Number_Format is used on both sides (9130 BSC
Evolution and MSC).
Note Task Description Site To do Outage
C7 Shut Down BSS Traffic: BSS-Tel
(WTC=4 min.)
OMC-R 5 min. -
BSC 25 min. - C7 De-activate HSL.
Note 1: If MTP_Sequence_Number_Format is
extended, set it back to normal.
Note 2: An automatic BSC reset takes place.
Note 3: During the BSC reset, at the MSC site,
change the N7 configuration from HSL to LSL.
Note 4: Ignore the alarms from the follow-up
window.
Note 5: The TC related boards are also updated
during the BSC reset.
C7 For each board carrying N7 (each
MT120 or ASMC and related ATBX),
Lock Board.
OMC-R 30 sec./ board -
C7 For each board carrying N7 (each
MT120 or ASMC and related ATBX),
Unlock Board.
OMC-R 3 min./ board -
OMC-R 15 min. - C7 Unlock BSS traffic (unlock BSS-TEL).
Audits are automatically triggered.
C7 If N7 links are locked, Unlock N7 links
(each link separately) from the OMC-R
OMC-R 2 min. -
40 / 48 3BK 17430 1021 RJZZA Ed.09
2 Scenario
Note Task Description Site To do Outage
OMC-R 10 min. - C7 Launch BSC Hardware Audit for the
BSC SBLs.
The MFS GPRS configuration is misaligned
after this operation.
C7 If the MFS GPRS configuration is
misaligned, Resynchronize GPRS on
the MFS.
OMC-R 5 min. -
2.4.2.2 Modify BSC Configuration
This command, sent from the local BSC terminal, triggers the reduction process
in the BSC database. This reduction is a pure software process, and uses
the TC-CPF file as input.
Note Task Description Site To do Outage
BSC 6 min. - - Modify BSC / TC Configuration (in this case,
reduce the TC) returning to the previous
configuration. Note: All screen fields have to be filled except
New Config BSC, which must be filled with "*****".
- Less than one minute after command
activation, a BSC-HW-RESYNCH message
appears on the BSC terminal.
BSC 1 min. -
OMC-R 30 min. in the
case of an 9120
BSC, up to 30
min. in the case
of an 9130 BSC
Evolution.
- - The OMC-R then automatically triggers a
hardware and alarm audit. At the end of the
audit, the removed boards must disappear
from the BSS Main View.
Note: Wait for the end of the audit before
performing any other action. A message appears
after the hardware audit: Abis/Ater view is
not up to date ! Do you want to reload
it ? Click on [ OK ].
2.4.2.3 Inform MSC
Note Task Description Site To do Outage
EXCH Inform the MSC staff about removed Ater Mux. OMC-R 5 min. -
3BK 17430 1021 RJZZA Ed.09 41 / 48
2 Scenario
2.4.3 Remove Hardware and Final Checks
2.4.3.1 Remove TC Boards
Note Task Description Site To do Outage
TC 10 min. - C1
C2
The TC Physical Description configuration is the
reference for removing all Ater Mux-associated
boards. Note: The Ater Mux to be removed is either
supported by a set of ASMC, ATBX and
DT16 boards (in this case, remove all these
boards) or it is supported by a single MT120
board which must be removed.
C2 With the TC terminal connected one more time to
each concerned TC rack, use
Locate a Board in TCC for G2/9125 TC
or
Locate a Board in TCC for 9125 TC equipped with
TC STM1IP subrack as the reference for removing
the free MT120 boards (all boards assigned to a
dummy BSC).
TC 5 min./ Ater
Mux
-
C2 Disconnect the TC terminal from the 9125 TC, using
Connect and Disconnect.
TC 1 min. -
2.4.3.2 Disconnect PCMs
Note Task Description Site To do Outage
Except
C3
Disconnect the PCMs between the TC and the
MSC.
TC / MSC 15 min./ Ater Mux -
TC/ BSC 5 min./ Ater Mux - Except
C3
Disconnect the PCM between the TC and the
BSC.
Note: Both disconnections can be done in
parallel. The whole task can be performed in
parallel with the board removal.
C3 Disconnect the PCMs between the TC and the
MFS output from the DDF.
TC/ MFS 15 min./ Ater Mux -
C3 Disconnect the PCMs between the MFS input
from the DDF and the BSC.
MFS/ BSC 15 min./ Ater Mux -
C7 Disconnect the PCM(s) between the BSC and
the MSC.
BSC/MSC 5 min./PCM -
42 / 48 3BK 17430 1021 RJZZA Ed.09
2 Scenario
2.4.3.3 Final Checks
Note Task Description Site To do Outage
- Perform a BSS Audit Alarm State. OMC-R 15 min. -
- View Status of Managed Objects and Alarms for the TC and
print the results. Compare with the results from the Initial
Checks (Section 2.3.1).
OMC-R 15 min. -
3BK 17430 1021 RJZZA Ed.09 43 / 48
2 Scenario
2.5 Scenario Specific Tasks
2.5.1 Ater Mux Extension in Existing and in New Added 9125 Compact
TC Rack
An 9125 TC rack can handle up to 48 Ater Mux connections split into four
subracks. Each subrack can contain Ater Mux corresponding to two 9120 BSC
racks. The 9125 TC configuration requires mapping an MT120 board on a
specific Ater Mux belonging to a specific 9120 BSC rack. The extension in
a new rack is performed when the existing TC rack is almost full and there
is not enough place to put all the new Ater Mux in the same TC rack. It is
necessary to take in account that only one 9125 TC rack can handle the Ater
Mux belonging to a specific 9120 BSC rack.
AterMux
BSC1
rack1
AterMux
BSC1
rack2
AterMux
BSC3
rack3
AterMux
BSC4
rack1
AterMux
BSC1
rack3
AterMux
BSC2
rack1
AterMux
BSC4
rack2
AterMux
BSC5
rack1
AterMux
BSC2
rack2
AterMux
BSC2
rack3
AterMux
BSC5
rack2
AterMux
BSC6
rack1
AterMux
BSC3
rack1
AterMux
BSC3
rack2
AterMux
BSC6
rack2
AterMux
BSC7
rack1
AterMux
BSC7
rack2
TC RACK 1
TC RACK 2
TC RACK 3
used first to extend BSC 7
Figure 3: Ater Mux Extension in Existing and in New Added 9125 TC Rack
Extension of BSC 5 and BSC 6 in TC rack 2 belongs to C4. Extension of BSC 7
in TC rack 2 and in added TC rack 3 belongs to C4 and C5.
44 / 48 3BK 17430 1021 RJZZA Ed.09
2 Scenario
2.5.2 Ater Mux Extension in 9125 TC with TC Rack Reconfiguration
The extension in TC rack 1 needs reconfiguration, which means MT120 board
reassignment (an MT120 is referenced by TC rack / shelf / slot versus BSC.id /
Ater Mux.id). This is shown in Figure 4. BSC 3 currently has eight Ater Mux
(two Ater Mux belonging to BSC 3 rack 2). The rest of the rack is used for BSC
4 which currently has only four Ater Mux. Now the need is to add six Ater Mux
for BSC 4. In order to limit the outage (or telecom reduction) it is decided to
move the BSC 3 rack 2 Ater Mux into TC rack 2 and to have all BSC 4 rack 1
Ater Mux (with the two added ones) in TC rack 1. The alternative solution is
to keep all BSC 3 Ater Mux on TC rack 1 and move all existing BSC 4 Ater
Mux on TC rack 2, but this means moving four Ater Mux which represents a
bigger outage (telecom reduction).
The most inconvenient case is when you have to move Ater Mux 1,2 of a BSC
(with a total outage result). Therefore, if you have a BSC supporting only Ater
Mux 1 and 2 in the first step, and in the concerned TC rack there are less than
six free spaces, then it is recommended to choose another TC rack with more
free spaces. This recommendation avoids critical outage, when it is decided to
extend this BSC (try never to have to move Ater Mux 1, 2 of a given BSC).
3BK 17430 1021 RJZZA Ed.09 45 / 48
2 Scenario
1 6 3 2 4 5 7 4 1 8 2 3
x x
x x x x
TC RACK 1 TC RACK 2
Two new MT120 boards are plugged in
and assigned to BSC 3 rack 2 (Ater Mux 7, 8)
Four new MT120 boards are plugged in and assigned to
BSC4 rack 2 (Ater Mux 7, 8, 9, 10)
6 Ater Mux
BSC 1
rack 1
6 Ater Mux
BSC 1
rack 2
6 Ater Mux
BSC 1
rack 3
6 Ater Mux
BSC 2
rack 1
6 Ater Mux
BSC 2
rack 2
6 Ater Mux
BSC 2
rack 3
8 Ater Mux
BSC 3
4 Ater Mux
BSC 4
To be reassigned to
BSC 4 (Ater Mux 5, 6)
Figure 4: Ater Mux Extension in 9125 TC with TC Rack Reconfiguration
The above example combines C4 and C5.
Note: For C5 and C6, you must use Move BSS from One 9125 TC to Another.
46 / 48 3BK 17430 1021 RJZZA Ed.09
2 Scenario
2.5.3 Cable A Interface for MT120 Board Insertion in G2 TC
The following figure shows how to cable the A interface on the rear of a G2 TC
rack when replacing G2 TC boards (ATBX) by an MT120 board. It must be
performed on each ATBX connector.
to DDF TX
to DDF RX
Cabling TRCU with ATBX boards
Cabling TRCU with MT120 module
Figure 5: Connecting Cables to Rear of Rack for MT120 Board
2.5.4 Cable JBFAN for MT120 Board Insertion in G2 TC
The cabling enables the JBFAN board to be monitored by the MT120 board.
This cabling is done on the TRC16 back panel for any couple of MT120 with
JBFAN boards. Connect the cable extremity on the first top position of the 03B
and the 07A backpanel connectors.
The cable reference must be 3BK07741AFAA.
3BK 17430 1021 RJZZA Ed.09 47 / 48
2 Scenario
BLANK PAGE BREAK
48 / 48 3BK 17430 1021 RJZZA Ed.09