Tmo18074d0sgdeni4.0 Ce PDF

Do not delete this graphic elements in here:
Mobile Network
BSS B10 B11 O&M Evolution
TMO18074 D0 SG DEN Issue 04
STUDENT GUIDE
All Rights Reserved © Alcatel-Lucent 2010
BSS B10 B11 O&M Evolution Page 1

Blank Page
2 All Rights Reserved © Alcatel-Lucent 2010

Mobile Network
BSS B10 B11 O&M Evolution This page is left blank intentionally
Document History
Edition Date Author Remarks
01 YYYY-MM-DD Last name, first name First edition

Module Objectives
Upon completion of this module, you should be able to:
Describe the purpose of the "A-Flex" feature and its O&M impacts
Describe the purpose of the "A Signaling over IP" feature and its O&M impacts
Describe the purpose of the "STM-1 BSC" feature and its O&M impacts
Describe the purpose of the " Gb-Flex" feature and its O&M impacts
Describe the purpose of the "OMC-R Improvements" feature and its O&M
impacts
Describe the purpose of the "HMI Improvements" feature and its O&M impacts

Mobile Network

Module Objectives [cont.]

Mobile Network
This page is left blank intentionally

Table of Contents
Page
Switch to notes view!
1 A Signaling over IP 7
1.1 What Is the Purpose of this Feature? 8
1.2 How Does It Work? 12
1.3 What Are the O&M Impacts? 17
2 A-Flex 23
3 STM-1 BSC 44
4 Gb-Flex 71
5 OMC-R Improvements 93
5.1 Centralized License Server and Time Validity 94
5.2 OMC-R Compatible with the SAN Architecture 101
5.3 SEC Command Line Interface 106
5.4 New Sun Hardware Platform 109
6 HMI Improvements 111
6.1 Copy and Paste Data into OMC-R Forms 112
5 6.2 Edit n Adjacencies All Rights Reserved © Alcatel-Lucent 2010 113
6.3
Mobile Network Customization
of BTS External Alarms 115
6.4 Load Indicators of OMC 117
6.5 Fast Measurement Mode for BSC Investigation 120
6.6 Software Migration Improvements 125
6.7 New ALMAP FM Module 129
7 Exercises 132
7.1 A Signaling over IP 133
7.2 A Fex Signaling 137
7.3 STM-1 BSC 141
7.4 Gb Flex 147
7.5 OMC-R HMI and Supervision Improvements 152
Abbreviations and Acronyms 156

Table of Contents [cont.]
Page
Switch to notes view!

Mobile Network

1 A Signaling over IP

Mobile Network

1.1 What Is the Purpose of this Feature?
Principle in B10: In B10, the A9130 BSC Evolution communicates with

the MSC using the SS7 protocol based on the LSL or HSL mode.
SS7 Signaling
A9130
BSS in HSL
Mode Ater
A
Mux TC
BSC
MGW
SS7
BSS in LSL Signaling
Mode A9130
MSC
Ater
Mux TC A Server
BSC

Mobile Network
In LSL mode, one TS of the Atermux is used to carry the SS7 signaling between the BSC and the MSC server.
We can have up to 16 SS7 TSs per BSC.
In HSL mode, one dedicated PCM is used to carry the SS7 signaling between the BSC and the MSC server.
The signaling links are connected directly from the BSC to the MSC without going through the TransCoder
(TC).
For redundancy purposes, 2 HSL links are used. The load is shared between both links.

1.1 What Is the Purpose of this Feature? [cont.]
Principle in B11: In B11, the purpose of the A Signaling Over IP feature

is to transfer the SS7 signaling over the IP network.
IP
A9130
Ater
Mux TC A
BSC
MGW
A9130
Ater A MSC
Mux TC
BSC

Mobile Network
With the A Signaling over IP feature, the BSC and the MSC server are connected directly via an IP network.

Why A Signaling over IP?

A signaling over IP is the requirement to provide the BSS with more flexibility
to access the NGN network.
It is in line with the BSS evolution direction (IP Transport in the BSS).
Several Benefits
Improvement of the signaling transfer reliability and lower transfer delay.
Higher signaling transfer bandwidth.
Simple network configuration and flexible network constructure.
Support of multi remote SS7 end points to be connected to the BSC.
This facility which allows the connection of one BSC to several MSCs is called A-
Flex.

Mobile Network

Restrictions
This feature is an optional feature.
A Signaling over TDM is still supported.
The TDM mode and the IP mode are exclusive per BSS.

Mobile Network

1.2 How Does It Work?
BSSAP Protocol Stack over TDM

In case of A Signaling transfer in pure TDM mode, the BSC and MSC
communicate using the MTP protocol.
A9130 MSC
BSC Server
BSSAP The TC is transparent BSSAP

for the signaling
SCCP SCCP
MTP 3 MTP 3
MTP 2 MTP 2
N7 Links
TC
MTP 1 MTP 1

Mobile Network

1.2 How Does It Work? [cont.]
BSSAP Protocol Stack over IP

In B11, with A Signaling over IP, the MTP protocol is replaced by
M3UA/SCTP/IP.
A9130 MSC
BSC Server
BSSAP BSSAP
SCCP SCCP
M3UA M3UA
SCTP SCTP
IP
IP IP

Mobile Network
The MTP3 User Adaptation (M3UA) supplies all the MTP3 interfaces to the user protocol, like SCCP.
The Stream Control Transport Protocol (SCTP) guarantees the signaling transport timely. This protocol is
presently used to transfer the M3UA signaling over IP.
The SCTP is designed to establish robust communication associations between two endpoints.

BSSAP Protocol Stack in the BSC

Functions in the BSC
CCP
BSSAP
SCCP
OMCP
M3UA_LM
TP
M3UA SLH
SCTP MTP 2
IP MTP 1
: IP mode : TDM mode

Mobile Network
The MTP3 User Adaptation (M3UA) supplies all the MTP3 interfaces to the user protocol, like SCCP.
The Stream Control Transport Protocol (SCTP) guarantees the signaling transport timely. This protocol is
presently used to transfer the M3UA signaling over IP.
The SCTP is designed to establish robust communication associations between two endpoints.
The Signaling Link Handling (SLH) is an MTP3 Layer Function.

Application Server (AS)

One BSC is one AS. From the BSC
point of view, the MSC is a remote
AS.
IP Server Process (IPSP)

ASL In the BSC, for each MSC, there is
IPSP MSC one separate IPSP.
AS (BSC)
ASL
A Signaling Link (ASL)
IPSP MSC The ASL is established between 2
IPSPs belonging to different ASs.

Mobile Network
The IPSP is one process that handles the M3UA/SCTP.
ASL is an SBL that represents the SCTP association between BSC and MSC. For one MSC instance, there are at
max 4 ASLs.

Rules
The A Signaling Over IP feature is only implemented in the BSC Evolution.
A BSC can be connected to more than one MSC (with the A-Flex feature).
For each MSC, we can have up to 4 ASLs.

Mobile Network
The IPSP is one process that handles the M3UA/SCTP.
ASL is an SBL that represents the SCTP association between BSC and MSC. For one MSC instance, there are at
max 4 ASLs.

1 What Are the O&M Impacts?
1.3 What Are the O&M Impacts?
Feature Activation
A signaling over IP is activated per BSC by setting the parameter
EN_A_Signaling_Over_IP to enabled.

Mobile Network

1.3 What Are the O&M Impacts? [cont.]
Add MSC
A new parameter group is introduced at BSC level to declare an MSC:
TRAFFIC_MODE
MSC_SPC
MIN_NB_ACTIVE_IPSP
MSC_CN_ID
MSC_WEIGHT
NRI_LIST

Mobile Network

Add ASL
For each MSC, one or more ASLs must be declared with the following
information:
ASIG_SCTP_ENDPOINT_
IP_ADDRESS_1
ASIG_SCTP_ENDPOINT_
IP_ADDRESS_2
ASIG_SCTP_ENDPOINT_
PORT

Mobile Network
This SBL represents the SCTP association between BSC and MSC. For one MSC instance, there are at max 4
ASLs.
To create an ASL, the following information is required:

LOCAL_ASIG_SCTP_ENDPOINT_IP_ADDRESS_1
LOCAL_ASIG_SCTP_ENDPOINT_PORT
ASIG_SCTP_ENDPOINT_IP_ADDRESS_1
ASIG_SCTP_ENDPOINT_PORT
The LOCAL_ASIG_SCTP_ENDPOINT_IP_ADDRESS_1 and LOCAL_ASIG_SCTP_ENDPOINT_PORT are read only.

New Alarms (1/2)

ASL_REP: This alarm is reported whenever one SCTP association is broken
or established.
RMH-REP: This alarm is for the Multi-Homing feature and it is only

reported for the ASL that has the remote endpoint with 2 IP addresses. It is
reported whenever one of the IP addresses status is changed while the
SCTP association status keeps in traffic.
INC-REP: This alarm is used for the TDM N7 link. In A Signaling Over IP,
this alarm is used to indicate one MSU is received with unexpected DPC or
OPC.
MSC-REP: This alarm is reported when the AS is INACTIVE.

Mobile Network
MSC-REP
An Alarm Condition ‘BEGIN’ alarm = the SBL MSC is updated to state FLT.
An Alarm Condition ‘END’ alarm = the SBL MSC is updated to state IT.

New Alarms (2/2)

MSC-DEGRADE: This alarm is reported when there is less than n IT ASL for
load-sharing mode. This alarm is mostly caused by one IP network problem:
for one MSC there are not enough IT ASLs to take traffic.
MSC-TRAFFIC-REDUCTION: This alarm indicates that the MSC load balance

status changes for the A-Flex feature: the MSC is excluded or included in
the load balance from the BSC point of view.

Mobile Network
MSC-DEGRADE
An Alarm Condition ‘BEGIN’ alarm = the SBL MSC is updated to state FIT
An Alarm Condition ‘END’ alarm = the SBL MSC is updated to state IT.
MSC-TRAFFIC-REDUCTION
In case the MSC is excluded due to overload, send BEGIN with alarm number 1.
In case the MSC is excluded due to the operator requested offloading, send BEGIN with alarm number 2.
In case the MSC is excluded due to the external MSC reset, send BEGIN with alarm number 3.
Note: without the A-Flex feature, this alarm will not be used.

Summary
The A Signaling Over IP feature allows the BSC to communicate with

the MSC using the SS7 protocol based on the IP mode.
The Benefits of A Signaling Over IP are:

Improvement of the signaling transfer reliability and lower transfer delay.
Higher signaling transfer bandwidth.
Simple network configuration and flexible network constructure.
Support of multi remote SS7 end points to be connected to the BSC.
The A Signaling Over IP feature is an option and is required for the A-

Flex facility implementation.
A Signaling Over IP is only implemented in the BSC Evolution.
There are new alarms.

Mobile Network

2 A-Flex

Mobile Network

2 A-Flex
Without the A-Flex Feature

In B10, the BSC can be connected to only one MSC Server.
In case of MSC Server failure, the

resources for the whole BSC are lost.
No calls possible!
A9130 MSC
BSC server
Signaling
Traffic
Media
Gateway

Mobile Network

2 A-Flex
With the A-Flex Feature

In B11, thanks to the A-Flex feature, a BSC
can be connected to more than one MSC. MSC
server
Signaling
A9130
BSC
Traffic Media
Gateway
Signaling
In case of MSC Server failure, MSC
the new calls are managed server
by the other MSC Server.

Mobile Network

2 A-Flex
Without the A-Flex feature, there is no redundancy of the MSC Server.
In case of MSC Server failure, there is no

more call establishment possible in
the cells of the BSS.
A-signaling over IP IP A-signaling over IP
Atermux A
Traffic
TC MGW
A9130
BSC MSC
Server

Mobile Network

2 A-Flex
To enable the A-Flex feature, A Signaling over IP should be activated.
In case of MSC Server failure, only a part of

the circuit resources for the BSS are lost.
A-signaling over IP A-signaling over IP

IP
MGW
Atermux A
VMGW MSC
Server
TC
A9130
BSC MSC
VMGW Server

Mobile Network
The MGW is statically partitioned into n Virtual MGWs (VMGWs), n corresponding to the number of MSC Servers
connected to the MGW.

2 A-Flex
Virtual Media Gateway Concept

Each physical MGW is partitioned into n Virtual MGWs, where n is the number
of MSC Servers associated to the MGW.
If we have 1 MGW connected to 2 MSC Servers, we will have:
Virtual MGW circuit trunk Static A-Flex MSC

partition number index
For BSC1 Virtual MGW/1-1 1 1

connected
to MGW/1 Virtual MGW/1-2 2 2
So the A interface circuits used by the BSC are partitioned into 2 Virtual
MGW circuit trunks, i.e. 2 static A-Flex partitions.

Mobile Network

2 A-Flex
Configuration
Let's assume that we have 2 MGWs and 8 MSC Servers for a
configuration of 48 AterMux CS. How many static A-Flex partition, A-
trunks and A-trunks per A-Flex partition are needed?
Match the correct answers.
Number of static A-Flex partition 192
Number of A-trunks 12
Number of A-trunks per A-Flex partition 16

Mobile Network

2 A-Flex
CS Pool Area Concept

In B10, if the BSC has 40% of the capacity of an MSC, there is a wastage
on the MSC side.
MSC
Signaling
40% MSC
A9130 Signaling
40% MSC
BSC
Waste of resources 20% MSC
MSC
Signaling
40% MSC
A9130
BSC
60% MSC

Mobile Network

2 A-Flex
CS Pool Area Concept in B11

A CS pool area is an area within which an MS may roam without need to
change the serving MSC Server.
MSC MSC
Server Server
A9130 A9130 A9130 A9130 A9130 A9130

BSC BSC BSC BSC BSC BSC
CS pool area 1 CS pool area 2

Mobile Network
A CS pool area is served by one or more MSC Servers in parallel.

2 A-Flex
The NAS Node Selection Function is a new function impIemented in

the BSC. This new function is in charge of balancing the load between
the MSC Servers connected to the BSC.
MSC MSC MSC

Server Server Server
Weight=5
Weight=5 Weight=10
BSC
NAS
Node
Selection
Function

Mobile Network
The Non Access Stratum (NAS) is a functional layer that supports signaling and traffic between the Core
Network and the Mobile Station.
The NAS Node Selection Function is a BSC function that assigns a specific CN Node (MSC Server) to serve an
MS.
The MSC_weight parameter is defined for each MSC Server connected to the BSC. This parameter allows to
take into account several MSC capacities and to make the load balancing according to that weight.
If the MSC weight is increased, the number of A-trunks connected to that MSC Server might also need to be
increased.

2 A-Flex
The Network Resource Identifier (NRI) is a parameter used to identify

uniquely a CN Node (MSC Server) within a BSC.
Every MSC Server is configured with one or more NRIs.
The length of the NRI shall be the same in all the MSC Servers of one CS
pool area.
The NRI is part of every temporary identity (TMSI) which the MSC Server
assigns to an MS.
Example of NRI inside the TMSI
NRI
TMSI

Mobile Network
The NRI has a configurable length of 0 to 10 bits.

A configurable length of 0 bit indicates that the NRI is not used and this feature is not applied in the MSC/VLR
or SGSN.
The NRI shall be coded from bits 23 to 14.
An NRI shorter than 10 bits shall be encoded with the most significant bit of the NRI field in bit 23.

2 A-Flex
How many NRIs at most can be allocated to an MSC Server?

Some customers require that:
one BSC supports at least 16 MSC Servers, which means the NRI length shall
be at least 4 bits.
the BSC supports a 10-bit NRI.
Length of NRI Number of MSCs per pool (Note) Number of TMSIs per NRI value
for a given time periode
4 15 (2^21) * 3 = ~6.3 M
6 63 (2^19) * 3 = ~1.6 M
7 127 (2^18) * 3 = ~0.8 M
10 1023 (2^15) *3 = ~0.1 M
It is clear that, in certain cases, one NRI per MSC Server is not
sufficient in terms of available TMSI space. In B11, we assume that one
MSC Server can have up to 8 NRIs.
Mobile Network
The NRI has a configurable length of 0 to 10 bits.

A configurable length of 0 bit indicates that the NRI is not used and this feature is not applied in the MSC/VLR
or SGSN.
The NRI shall be coded from bits 23 to 14.
An NRI shorter than 10 bits shall be encoded with the most significant bit of the NRI field in bit 23.

2 A-Flex
MSC Selection with TMSI Included in the Initial Layer 3 Message
NRI 2
NRI2
NRI2
NRI2
NRI2
SCCP ti
Conn
ec MSC
on
l.
Server
Estab
e
e
servic s servic s
ue BSC
reque re q
t t )
(TMSI
) (TMSI NRI 4
NAS Node
Selection
Function
MSC
Server

Mobile Network
If the TMSI is included in the Initial Layer 3 message, the BSC derives the NRI (based on the NRI length
configured by O&M) then uses the NRI to find the MSC Server address (MSC SPC) and triggers the SCCP
Connection Establishment towards the corresponding MSC Server.

2 A-Flex
MSC Selection with IMSI Included in the Initial Layer 3 Message
NRI 2
Load balancing
computation
MSC
Server
e
e
servic st servic st
reque reque BSC
(IMSI) (IMSI)
NRI 4
SCCP n
ctio
NAS Node Conne bl.
Selection Esta
Function
SCCP n
ctio
Conne bl. MSC
Esta Server

Mobile Network
If the IMSI is included in an Initial Layer 3 message which is not a PAGING RESPONSE, then the BSC forwards
the received message to an MSC Server selected by using the load-balancing algorithm.
If the IMSI is included in a PAGING RESPONSE message, the BSC searches the saved [IMSI, MSC identity] entries.
If the IMSI is found and the corresponding MSC Server is "operational", then the BSC forwards the received
message to the MSC Server.
Otherwise the BSC forwards the received message to an MSC Server selected by using the load-balancing
algorithm.

2 A-Flex
Engineering Rules
The A-Flex feature is based on the A-Signaling over IP feature (it doesn‘t
work with the A-signaling over TDM).
A-Flex is only implemented in the A9130 BSC.
This feature is not supported with the legacy MSC (monolithic).
This feature works only with the Media Gateway supporting the Virtual MGW
feature.
We can connect up to 16 MSC Servers to one BSC.
There are up to 8 NRIs per MSC.

Mobile Network
The legacy MSC means the monolithic MSC that handles both signaling and data.
An MSC Server and a Media Gateway make up the full functionality of an MSC.
The MSC Server handles only signaling.
The Media Gateway handles user’s data.
There are up to 8 NRIs per MSC. These NRIs cannot be assigned to the other MSCs of the CS pool area.

2 A-Flex
The benefits of the A-Flex feature are:

Reducing the signaling traffic in the core network.
Increasing the service availability.
Achieving the load balancing amongst the MSC Servers.
Easier Core Network expansion.

Mobile Network
Reducing the signaling traffic in the core network

An external location update to the HLR and an inter-MSC handover procedure become only necessary if the MS
leaves the CS pool area.
Increasing the service availability

Without the A-Flex feature, the unavailability of an MSC Server leads to the service outage of the complete
area controlled by the MSC Server. With this feature, if an MSC fails the remaining MSC(s) in the CS pool area
can take over the new service requests.
Achieving the load balancing amongst the MSC Servers

The introduction of the CS pool area allows to balance the load in the MSC Servers of a CS pool area. Thus
situations where, within one CS pool area, certain MSCs are overloaded while others are almost idle can be
avoided. Indeed this means that in the CS pool area the available processing capacity can be used in a better
way. This leads to increasing the robustness and better response times of the core network.
Easier Core network expansion

If the core network capacity needs to be increased, there is no need anymore to reconfigure the radio
network. The existing LA/RA configuration can be kept. It is sufficient to add a new MSC Server to the CS pool
area with the same radio configuration data as the other MSC Servers of this CS pool area.

2 A-Flex
Feature
Activation
The EN_A_Flex
parameter
activates the A-
Flex feature, when
set to Enabled.

Mobile Network
To enable the A-Flex feature, at least one MSC Server and one ASL should be declared.

2 A-Flex
Add MSC
A new parameter group
is introduced at BSC
level for the
characteristics of each
MSC:
TRAFFIC_MODE
MSC_SPC
MIN_NB_ACTIVE_IPSP
MSC_CN_ID
MSC_WEIGHT
NRI_LIST
Depending on the
version used, the
parameter names
may change.

Mobile Network

2 A-Flex
Add ASL
For each MSC, one or more ASLs must be declared with the following
information:
Depending on the
version used, the
parameter names
may change.

Mobile Network
To create an ASL, the following information is required:

The LOCAL_ASIG_SCTP_ENDPOINT_IP_ADDRESS_1 and LOCAL_ASIG_SCTP_ENDPOINT_PORT are read only.

2 A-Flex
New Alarm
MSC-TRAFFIC-REDUCTION indicates that the MSC load balance status
changes. For the A-Flex feature, the MSC is excluded from or included in the
load balance from the BSC point of view:
In case the MSC is excluded due to overload, the BSC sends BEGIN with alarm
number 1.
In case the MSC is excluded due to the operator requested offloading, the BSC
sends BEGIN with alarm number 2.
In case the MSC is excluded due to the external MSC reset, the BSC sends BEGIN
with alarm number 3.
Without the A-Flex feature, this alarm is not used.

Mobile Network

Summary
A-Flex is based on the A-Signaling over IP feature.

A-Flex is an optional feature and is only implemented in the A9130
BSC.
This feature can be activated (or disactivated) by the EN_A_Flex
parameter.
This feature allows to connect more than one MSC Server to a BSS.
The maximum number of MSC Server per BSS is 16.
The NRI identifies uniquely a MSC Server, but up to 8 NRIs can be
assigned to one MSC Server.
This feature doesn’t work with the legacy MSC.
The Media Gateway needs to support the Virtual MGW feature.

Mobile Network

3 STM-1 BSC

Mobile Network

3 STM-1 BSC
SDH versus PDH

The Synchronous Digital Hierarchy (SDH) technology designates signal
interfaces for very high-speed digital transmission over optical fiber
links. The SDH technology tends to replace the PDH technology (which
is not designed for high-speed data transfer).
SDH standards have defined the capacities listed in the table below.
SDH SONET Rate

STM-1 OC-3 155Mb/s
STM-4 OC-12 622Mb/s
STM-16 OC-48 2.5Gb/s

STM-64 OC-192 10Gb/s
STM-128 OC-384 20Gb/s
STM-256 OC-768 40Gb/s

Mobile Network
SONET is the SDH version in the United States.
Plesiosynchronous Transmission Hierarchy (PDH)

In Europe:
E-1 = 2Mbps,
E-2 = 8Mbps,
E-3 = 34Mbps,
E-4 = 140Mbps,
E-5 = 565Mbps.
The PDH technology is not designed for high-rate transfers, to insert or extract a data from (E1/E3) all the
frame should be demultiplex/multiplex.

3 STM-1 BSC
SDH Network Topology

An SDH network can be designed according to three types of topology.
Whichever the topology, the access to the SDH network is done through
an Add-Drop Multiplexer (ADM).
ADM
ADM
ADM
ADM
ADM
ADM
ADM
ADM
ADM
ADM
ADM
Ring topology Star topology Bus topology

Mobile Network

3 STM-1 BSC
Add-Drop Multiplexer (ADM)

An ADM is a device that adds (inserts) or drops (removes) lower-data-
rate channel traffic from the higher-rate aggregated channel.
Tributary input
E.g.: E1/T1 E3/T3 termination
Coaxial or fiber can also be connected.
STM-1/4/16…
Optical
network

Mobile Network

3 STM-1 BSC
SDH Hierarchy: ETSI Multiplexing Structure
xn STM n
140Mbps
AUG POH AU-4 POH VC 4 C4
34Mbps
x3 x3 TUG 3 POH TU-3 POH VC 3 C3
POH AU-3 POH VC 3

x7
6Mbps
x7 TUG 2 POH TU-2 POH VC 2 C2

2Mbps
x3 C12
POH TU-12 POH VC 12
1.5Mbps
POH VC 11 C11

Mobile Network
Path OverHead (POH)

The POH is an additional transport capacity designed for the container. POH is used to manage the input tributary.
Section OverHead (SOH)

The SOH is used to manage the transmission line section. SOH is made up of:
a Regenerator SOH (RSOH) used for communication between regenerators.
a Multiplexer SOH (MSOH) used for communication between ADMs.
Virtual Container (VC)

A VC-n is made up of a Container (C-n) and a Path OverHead (POH).
VC-n = C-n + POH, where n = 11, 12, 2, 3, 4
Tributary Unit (TU-n)

A TU is made up of a VC-n and a pointer (PTR). The PTR identifies the VC-n location in the SDH frame.
Tributary Unit Group (TUG)

The TUG-2 / TUG-3 can consist of several types of capacity payloads with different sizes:
The TUG-2 is:
4 x TU-11, or
3 x TU-12, or
1 x TU-2.
The TUG-3 is:
either 7 x TUG-2,
or 1 x TU-3.
The TUG is obtained through byte interleaved multiplexing.

3 STM-1 BSC
According to the previous drawing, how many E1 links (VC12) can one
STM-1 link carry?
Select the correct answer.
21
63
155

Mobile Network

3 STM-1 BSC
According to the capacity of one STM-1 in terms of VC12, how many

STM-1 links should be connected to one 1000 TRXs MX BSC capacity to
carry the 252 PCM links?
1
2
3
4

Mobile Network

3 STM-1 BSC
SDH Basic Frame Architecture

Example: E1 KLM locationTu12
overTu12
an STM-1
Tu12 frame. TU 12#KLM
#1 #2 #3 K: n° TUG3
Tu12 Tu12 Tu12 L: n° TUG2
#1 #2 #3
M: n° TU12
TUG2#1
RSOH TUG2#2
Tu12 Tu12 Tu12
POH
PTR Tu12 Tu12 Tu12 TUG3#2 TUG3#3
VC4
Tu12 Tu12 Tu12
MSOH Tu12 Tu12 Tu12
Tu12 Tu12 Tu12
TUG3#1
Mobile Network

3 STM-1 BSC
According to the KLM numbering, what is the location of the TU12 in

green on the diagram below?
3, 5, 2
TUG2#1
1, 5, 2
1, 3, 2 RSOH TUG2#2
3, 2, 5 Tu12 Tu12 Tu12
PTR POH Tu12 Tu12 Tu12

VC4 TUG3#2 TUG3#3
Tu12 Tu12 Tu12 Tu12
MSOH Tu12 Tu12 Tu12
Tu12 Tu12 Tu12
TUG3#1
Mobile Network

3 STM-1 BSC
In B10, the “STM-1 TC” facility was the first step to introduce STM-1
connectivity in the BSS. This provided high-density E1 connection,
thanks to 155 Mbit/s STM-1 interfaces.
Example of Mixed Configuration with STM-1 TC Facility
BSC BSC
BTS BTS
ADM
ADM
SDH TC
ADM Network
BTS ADM ADM Optical fiber

MSC (STM-1)
The STM-1 TC feature E1 link

was optional.
MFS ADM

Mobile Network

3 STM-1 BSC
In B11, a next step of STM-1 connectivity in the BSS is provided with

the “STM-1 BSC” facility, thanks to 155 Mbit/s STM-1 interfaces. A 9130
BSC configured with STM-1 interface boards can be pure E1, pure STM-1
or mixed of E1 and STM-1.
Example of Mixed Configuration with STM-1 BSC Facility
BSC
BSC BTS
BTS ADM
ADM
SDH TC
Network
ADM
ADM ADM Optical fiber
MSC (STM-1)
BTS
The STM-1 BSC feature E1 link
is optional.
MFS ADM

Mobile Network

3 STM-1 BSC
The introduction of STM-1 in the 9130 BSC allows to:

reduce cost on interface equipment to SDH network.
reduce drastically time/error of installation/cabling.
reduce the space needed for cables and distribution frames.
simplify cabling & assignment changes.
increase the reliability and availability.

Mobile Network
Benefits
Reduce cost on interface equipment to SDH network: with removal of E1 to STM-1 boards to connect the BSC
to the SDH network (CAPEX saving).
Reduce drastically time/error of installation/cabling: only 4 STM-1 interfaces are needed in the BSC to
replace the 176 E1 links for Abis interface and 76 E1 links for Atermux interface (OPEX saving).
Reduce the space needed for cables and distribution frames: the 8 STM1 fibers use much less cable ways
and distribution frames than the 252 PCM links (OPEX saving).
Simplify cabling & assignment changes: modification of routing of a VC12 can be done remotely by computer
command, as there is no cabling change (OPEX saving).
Increase the reliability and availability: STM-1 connectivity provides excellent availability thanks to the
combination of APS & EPS, as well as it benefits from the reliability of SDH network architecture (OPEX
saving).

3 STM-1 BSC
The introduction of the

STM-1 BSC facility BSC Hardware Architecture
requires a new board
called JBXTP3, which JB
XT
replaces JBXTP. P3
w
STM-1
The JBXTP3 working in JB
XT optional
P3
1+1 redundancy. JB
XM JB
XS r
UX SW
It is able to handle 252 (
du
pli
ca
te
(du
pli
ca
te JB
d) d) XC
E1 or 4 protected STM- CP
1
1 links. Radio Network Links
JB JB
XL JB XC
IU XO
Each STM-1 link is a E1 1
(du
MC
P
CP
n
155 Mbit/s optical pli
ca
te d)
interface, multi or JB
XL
mono-mode/short IU
n
Haul type. r: Redundancy
W: Working LIU Shelf ATCA Shelf
External Ethernet Links

Mobile Network
Optical fibers can be classified into two categories according to the diameter of the heart and the wavelength
used: mono mode and multimode fiber.
The multimode fibers were first on the market. They carry several modes of transport (light paths). Because
of the modal dispersion, there is a temporal spread of the signal proportional to the length of the fiber.
Consequently, they are used only for low speeds and short distances.
For longer distances and / or higher rates, we prefer to use mono mode fiber which are more technologically
advanced because finer. Their thin heart admits only one mode of propagation: the most direct in the fiber
axis. The losses are so minimal.
Mono mode fibers are therefore suitable for intercontinental routes (submarine cables).
Mono-mode/short-haul type: Pluggable O/E converters, called Small Form Factor Pluggable (SFP), are used
and enable other STM-1
types.

3 STM-1 BSC
The JBXTP3 board is a functional variant of the JBXTP board.

The name of the functional module added on the mother board is E1
VC-12. It is able to support hot insertion of 4 STM-1 electro/optical
modules (multi or monomode fiber optic transceivers).
Global Architecture of JBXTP3
ųP The module E1 VC-12 with

selector functions allows the
with selector mapping of:
function
E1 on LIU-E1 input port
HDLC SS7
E1 VC-12 E1 on any STM1 VC12-E1 input
port without any numbering
restriction
any mix of LIU-E1 and VC12-E1
Q1 R/W GbE
bits 252 E1 switch
framers NE1oE
TDM switch Mapper
63 Ethernet
frame
STM-1 Optical rs NE1oE
TDM

Mobile Network
Characteristics of the JBXTP3:

Multiplexing/demultiplexing of up to 252 E1 links from/to the Gigabit Ethernet interface (NE1oE).
Handling of GSM protocols HDLC, SS7, Q1 and R/W bits.
(ML-)PPP handling and IP routing.
Gigabit Ethernet switching.
TDM switching.
IPMI V1.5.
E1 VC-12 module.
The E1 VC-12 module supports the Automatic Protection Switching (APS) function, required for optical line
interface. The APS decision is independent for each STM-1 link.
This module includes:

Four 63 E1 framers terminating up to 252 E1 with Data + Clock or four STM-1 links.
Eight ESD FPGAs to perform the adaptation between the Data + Clock line interfaces of the framers and the
two 16 serial links of the NE1oE module.
One SFP cage supporting hot insertion of 4 STM-1 electro/optic modules (multimode or monomode Fiber
optic transceivers).

3 STM-1 BSC
In the 9130 BSC, the connection of STM-1 links is performed in the

front plate of the JBXTP thanks to the SFP connectors.
The fiber optic transceivers provide a reliable
interface.
TX
RX 1
SFP connectors
2
One optical fiber

3
JBXTP3 Board

Mobile Network
STM-1 is a 155-Mbps interface from the SDH family (STM-4, STM-16, STM-64).
E1 is transported in VC-12 tributary. STM-1 contains 63 VC-12. 1 TC supports 4 STM-1 maximum.
E1 Mapping in the 4 STM-1 Frames

To give the flexibility to affect any E1 anywhere in any STM-1 frame, the STM-1 daughter board is designed
for a 252 x 252 E1 cross-connect.

3 STM-1 BSC
Engineering Rules
The introduction of the STM-1 facility in the 9130 BSC implies the
following engineering rules:
STM-1 interface being an optional feature in Alcatel-Lucent BSS, a

maximum number of STM-1 interfaces is set per OMC-R.
This “account” considers the total number of STM-1 interfaces
activated in BSCs and TCs supervised by the OMC-R.
Any VC12 container of the BSC STM-1 link can be allocated either to
Abis or Ater interface.

Mobile Network
STM-1 interface is an optional feature in Alcatel-Lucent BSS.

A maximum number of STM-1 interfaces is set per OMC-R. This “account” considers the total number of STM-1
interfaces activated in BSCs and TCs supervised by the OMC-R. When the total number of STM-1 interfaces is
close to the limit (a threshold is defined by the operator in the OMC-R), a warning is issued at declaration
time. When the limit is exceeded, operator basic actions at OMC are forbidden.

3 STM-1 BSC
STM-1 Configuration Operating Mode

The management of STM-1 in one BSC is based on 3 steps:
Declaration of STM-1 interface via the OMC-R Terminal.
The operator can declare or remove the STM-1 interface for the selected
Network Element (NE) from the OMC-R.
Configuration of STM-1 via the BSC terminal.
The configuration of the STM-1 links (logical E1 to VC12 mapping) is
performed from the BSC terminal.
The operator prepares the configuration in a first operation, downloads it in
the BSC in a second step and then applies this configuration later, in a third
step.
The configuration file can be imported or exported from the

BSC, allowing back office preparation for better efficiency.
Supervision of STM-1 via the OMC-R terminal.

The JBXTP3 boards and the STM-1 links in the BSC are supervised from the
OMC-R.
The supervised STM-1 configuration in the BSC can be displayed on demand.

Mobile Network

3 STM-1 BSC
2 new SBLs are created for STM-1 support on BSC side.
SBL Hierarchy on BSC Side
BSC
TP-HW(1) TP-HW(2)
STM1-TTP STM1-TTP
(i) (i+4)
OR
STM1-ITF
(i)
With i = 1 to 4

Mobile Network
2 new SBLs are created for STM-1 support on BSC side:

STM1-TTP: this represents the STM-1 termination. This SBL is mapped on the STM-1 termination supported
by the TP HW SBL
STM1-ITF: this represents a protected interface. This SBL is not mapped to an RIT. This SBL is logically
mapped on the corresponding active and standby STM-1 TTP.

3 STM-1 BSC
2 protections are performed:
Automatic Protection Switching (APS) performs the protection of the STM-

1 links in case of failure on one line.
The APS mechanism is used in 1+1 with unidirectional non-revertive switching

mode.
Equipment Protection Switching (EPS) performs the protection of the

transmission board in case of failure on one JBXTP3 board.
The combination of EPS and APS provides total availability and

reliability of the STM-1 links and termination points.

Mobile Network
The APS is used in 1+1 with unidirectional non-revertive switching mode. It is compliant to ITU-T G.841.
An APS is used to avoid the loss of an STM-1 link in case of physical link failure. The standards have designed
two modes:
Unidirectional protection.
Bi-directional protection.
Unidirectional Protection
Each end of the link transmits on both lines permanently and each end of the link selects only one line for
reception of the traffic and monitors the received signal on that line. If the received signal is faulty, then APS
in that end will switch the reception to the other line. At a given point in time, thus one end could use one
line and the other end the other line for reception.
Bi-directional Protection
Each end of the link transmits and receives always on one and the same selected line. Each end of the link
monitors the received signal on that line. If the received signal is faulty, then APS in that end will switch the
reception to the other line and will signal the switch to the other end (in-band signaling protocol if possible).
At a given point in time, thus both ends use one and the same working line (except during the short
transitions).
After failure recovery, there are two options:

The revertive mode. This mode ensures that after a repair only the link on the primary TCIF board is used.
The non-revertive mode. Over longer time, a link can be distributed over two TCIF boards.
The Alcatel-Lucent policy choice is unidirectional and non-revertive.

3 STM-1 BSC
APS: 1+1 Mode with

Unidirectional Non-revertive Normal line
Switching Mapper
Switch
Unidirectional switching means Optical fiber
that transmission is always Mapper
performed on the two (working and Data

Active section
redundant) links, while reception is Mapper
switched from working link to
redundant link in case of failure. Mapper
The two links are hold by separate
ActiveTPGSM
boards, thanks to EPS.
HW mirroring
The protection switching is also Mapper STM-1function
non-revertive, meaning that a Backup line
Switch
switch to the protected line is
maintained even after the working
line has recovered from the failure. Optical fiber
Mapper
Standby
section Mapper
Rx active in service
Mapper
Tx working/protection in service
Rx standby in service Standby TPGSM

Mobile Network
Each STM-1 interface has two sections. One is connected to the active TPGSM and the other one is connected
to the standby TPGSM.
Only the payload is exchanged between the two boards (active and standby TPGSM).
Inside the BSC, the selection of the section to be used for reception is performed by the active TPGSM. Each
TPGSM supervises the status of all sections connected to it. The standby TPGSM reports the status of its
sections to the active TPGSM.
At start-up, the active section is elected from the first section with a status IT. If both sections are IT, the
active section is elected on the active TPGSM.
In case of active section failure, the active TPGSM elects the other section as active if it has a status IT.
The STM-1 mode is unidirectional, i.e. the same frames are transmitted in parallel on two sections and each
equipment selects autonomously the section to be used for reception.
The STM-1 is non-revertive, i.e. once the TP has changed the active section, it does not come back to the
previous section when the failure ends.

3 STM-1 BSC
With EPS, the traffic on the Active section
active STM-1 interface board Normal line

is switched in case of board Mapper
failure to the spare standby Switch

Optical fiber
board (Active/Hot standby Mapper
mode). The two boards are Data
coupled in the ATCA® back Mapper
panel to provide the APS

Mapper
function. All established calls
ActiveTPGSM
are preserved after the EPS
HW mirroring
switch. Mapper STM-1function
Backup line
The combination of EPS and APS Switch
provides total availability and Relay
reliability of the STM-1 links and Mapper
termination points. Optical fiber
Mapper
Standby
section Mapper
Rx active in service
Tx working/protection in service Mapper
Rx standby in service Standby TPGSM

Mobile Network
On the TPGSM board, there is one mapper per STM-1 connector. Each mapper could be configured in two
modes: the mode master or the mode relay.
The active TPGSM configures thanks to the HW mirroring between the 2 TPGSM boards:
all its mappers in mode master.
all mappers of the standby TPGSM. The standby TPGSM configures all its mappers in mode relay.
Example of Scenario
In case of active TPGSM failure, there is a TPGSM takeover.
The board is powered-off.
The newly active TPGSM has to configure its mapper in mode master and to elect for each STM-1 interface the
section configured on the newly active TPGSM.
STM-1 interfaces are no longer protected.
If a section is out of service on the newly active TPGSM, there is a loss of a STM-1 interface.

3 STM-1 BSC
Declaration of STM-1 Interface from the DCN Window (OMC-R)

Mobile Network

3 STM-1 BSC
Appearance of STM-1 in BSSUSM after the STM-1 Interface 1

Activation (OMC-R)

Mobile Network

3 STM-1 BSC
Configuration of the STM-1 Interface and Activation from the BSC

Terminal

Mobile Network

3 STM-1 BSC
Ater View after Configuring and Activating STM-1 Interface at

OMC-R

Mobile Network

3 STM-1 BSC
A set of alarms is defined to report at OMC-R level possible

configuration errors or failure of the STM-1 hardware equipment or
logical interface (down to VC12 level). STM-1 BSC introduces the
alarms listed in the table below.
Alarm Label Alarm Type Definition
SFP-UNEQ 10 Small Form-Factor Pluggable not equipped

LOS 11 Section Loss Of Signal
LOF 12 Section Loss Of Frame
MS-AIS 13 Multiplex Section Alarm Indication Signal
MS-RDI 14 Multiplex Section Remote Defect Indication
MS-BER-10E-6 15 Multiplex Section Bit Error Rate 10-6
MS-BER-10E-3 16 Multiplex Section Bit Error Rate 10-3
AU-LOP 21 Administrative Unit 4 Loss of Pointer
AU-AIS 22 Administrative Unit 4 Alarm Indication Signal
HP-UNEQ 31 High Order Path Unequipped
HP-PLM 32 High Order Path Payload Label Mismatch
HP-RDI 33 High Order Path Remote Defect Indication
HP-LOM 34 High Order Path Loss of Multiframe

Mobile Network

Summary
The “STM-1 BSC” facility allows the BSC to provide high-density E1 connection
thanks to 155 Mbit/s STM-1 interfaces. This leads a saving of CAPEX and OPEX.
The “STM-1 BSC” requires a JBXTP3 board to connect the BSC to an SDH
network.
One JBXTP3 is able to manage from 1 up to 4 optical fibers multi or mono-

mode connected in the front panel via SFP.
The “STM-1 BSC” facility is an option and is limited to a maximum number of

STM-1 links per OMC.
The BSC configured with STM-1 interface boards can be pure E1, pure STM-1
or mixed of E1 and STM-1.
Any VC12 container of the BSC STM-1 link can be allocated either to the Abis
or Ater interface.

Mobile Network

4 Gb-Flex

Mobile Network

4 Gb-Flex
In B10, the current Alcatel-Lucent BSS implementation is based on the

legacy network architecture: the BSS can be connected to only one
SGSN.
In case of SGSN failure, the GPRS

calls are lost and the GPRS service is
not accessible for the MS anymore.
BSS SGSN

Mobile Network
In case an SGSN fails, all the established GPRS calls managed by this SGSN are lost.

4 Gb-Flex
In B11, the Gb Flex feature allows a BSS to be connected to more than

one SGSN.
IPIn case of SGSN failure,

the new calls are managed
by the other SGSN.
SGSN 2
BSS
SGSN 1

Mobile Network
In case an SGSN fails, all the established GPRS calls managed by this SGSN are lost. But the new calls are
managed by another SGSN.

4 Gb-Flex
The benefits of the Gb-Flex feature are:
Reducing the signaling traffic in the core network.
Increasing the service availability.
Achieving the load balancing amongst the SGSNs.
Easier Core Network expansion.

Mobile Network
Reducing the signaling traffic in the core network

An external location update to the HLR and an inter-SGSN handover procedure become only necessary if the MS
leaves the PS pool area.
Increasing the service availability

Without the Gb-Flex feature, the unavailability of an SGSN leads to the service outage of the complete area
controlled by the SGSN. With this feature, if an SGSN fails, the remaining SGSN(s) in the PS pool area can take
over the new service requests.
Achieving the load balancing amongst the SGSN

The introduction of the PS pool area allows to balance the load in the SGSN of a PS pool area. Thus situations
where, within one PS pool area, certain SGSNs are overloaded while others are almost idle can be avoided.
Indeed this means that in the PS pool area the available processing capacity can be used in a better way. This
leads to increasing the robustness and better response times of the core network.
Easier Core network expansion

If the core network capacity needs to be increased, there is no need anymore to reconfigure the radio network.
The existing LA/RA configuration can be kept. It is sufficient to add a new SGSN to the PS pool area with the
same radio configuration data as the other SGSN(s) of this PS pool area.

4 Gb-Flex
The implementation of Gb-Flex requires firstly the Gb over IP for the GPs
associated to one BSS :
An IP endpoint is is defined by its IP address and UDP port. An IP
endpoint can be data, signaling or pre-configured endpoint.
A Data IP endpoint is used for data traffic.
A Signaling IP endpoint is used for signaling traffic.
A Pre-configured IP endpoint is used to exchange the configuration
between the BSS and the SGSN.
MFS SGSN
NSE1 NSE1
) UDPb
UDPa NSVC1( UDPa/IP1, UDPb/IP2 IP2
IP1 IP Network
GP
NSVC2
( UDPa
/IP1, U
DPc/IP UDPc
3) IP3

Mobile Network
The Alcatel-Lucent solution supports only one IP endpoint per NSE on MFS side.
On the other hand, it is possible to configure several IP endpoints per NSE on SGSN side (up to 16).
The Network Service Virtual Circuit (NS-VC) is given by a pair of IP endpoints at MFS and SGSN levels.
The pre-configured IP endpoint is used in case of dynamic configuration of Gb over IP.

4 Gb-Flex
PS Pool Area
A PS Pool area is an area within which an MS can roam without need to
change the serving SGSN. A PS Pool area is served by one or more SGSNs
in parallel.
Network Resource Identification (NRI)

A number which allows one GP to identify one SGSN responsible for one
MS according to its TLLI.
NAS Node Selection Function (NSF)

A function which allows one GP to select one SGSN among several
candidate SGSNs for one MS according to its TLLI.
Gb Flex is an optional feature and is licensed at OMC level.
The activation of the Gb Flex Feature is performed per BSS.

Mobile Network

4 Gb-Flex
Engineering Rules
One PS pool area can
be served by one or SGSN Pool1 SGSN Pool2
several SGSNs.
SGSN1 SGSN2 SGSN3

8 SGSNs maximum
per BSS.
One BSS can belong

to several PS pool
areas.
BSS BSS BSS
1 2 3
PS Pool area1 PS Pool area2

Mobile Network
The PS pool area definition is extracted from the 3GPP 23.236.

As specified by 3GPP: “If LAs or RAs span over multiple RAN node service areas then all these RAN node
service areas have to belong to the same PS pool-area”.
For the BSS, it means that “LAC and RA defined on several BSSs must belong to the same PS pool area”.
This is only a rule that can be given to the operator. There is no control to be done at OMC-R level.
The granularity in a PS pool area is the BSS.
Note:
All the cells controlled by a BSC belong to the same (one or more) PS pool areas.

4 Gb-Flex
Reminder on P_TMSI and TLLI

Packet Temporary Mobile Subscriber Identifier (P_TMSI)
A P_TMSI is assigned by the GPRS core network (SGSN) to an MS. It is used in the GMM
sub-layer to identify it.
The P_TMSI is unique within a given Routing Area.
Temporary Logical Link Identifier (TLLI)

The Temporary Logical Link Identifier (TLLI) provides the signaling address used for
communication between the MS and the SGSN. A TLLI is built by the MS or by the SGSN
either on the basis of the P_TMSI (local or foreign), or directly (random).
There are 3 types of TLLI:
Local TLLI: derived from the P_TMSI allocated by the SGSN, and valid only in the
Routing Area associated to the P_TMSI.
Foreign TLLI: derived from a P_TMSI allocated in another RA.
Random TLLI: selected randomly by the MS when the MS has not a valid P_TMSI.
Within one RA, a one-to-one relationship exists between

the TLLI and the P_TMSI.

Mobile Network

4 Gb-Flex
On receipt of a TLLI from one MS, the GP selects the correct SGSN
according to an algorithm based on two mechanisms:
NRI
NAS NSF SGSN Pool1
Which SGSN
do I have to SGSN1
select?
NSE1
NSE1
SGSN2
NSE2 NSE2
TLLI
NSE3 SGSN3
GP NSE3
Gb Flex implies more than one NSE per GP board (maximum 8). SGSN Pool2
Mobile Network

4 Gb-Flex
NRI characteristics:
The NRI is a part of the P-TMSI, which is assigned by the serving SGSN
to the MS.
The NRI is coded in bits 23 to 14 of P_TMSI.
The NRI identifies uniquely an individual SGSN out of all SGSNs, which
serve in parallel a PS pool area.
It is the SGSN, which sets the NRI in the P_TMSI.
Valid P_TMSI 31 30 29-24 NRI 18-0
Local TLLI 31 30 29-24 NRI 18-0
2 bits set to 1
SGSN Pool2
Mobile Network
In areas where PS pool areas overlap the NRI identifies uniquely an SGSN out of all SGSNs, which serve all
these overlapping PS pool areas, i.e. an NRI identifies uniquely an SGSN within a BSS.
A local TLLI is built by an MS, which has a valid P_TMSI as follows:

Bits 31 down to 30 are set to 1.
Bits 29 down to 0 are set equal to bits 29 to 0 of the P_TMSI.
A foreign TLLI is built by an MS, which has a valid P_TMSI as follows:

Bit 31 is set to 1 and bit 30 is set to 0.
Bits 29 down to 0 are set equal to bits 29 to 0 of the P_TMSI.
A random TLLI is built by an MS, which has not a valid P_TMSI as follows:
Bit 31 is set to 0.
Bits 30 down to 27 are set to 1.
Bits 26 down to 0 are chosen randomly.
Regardless of the NRI length, the most significant bit of the NRI is always in bit 23 of P_TMSI.

4 Gb-Flex
NRI Engineering rules:

The length of the NRI shall be the same in all nodes of a domain in one
PS pool area.
More than one NRI may be assigned to an SGSN, but from the BSS point
of view, an NRI identifies uniquely an SGSN.
When there is a large NRI length, it could be interesting that an SGSN

has several NRIs to increase the number of mobiles it can manage.
The NRI length is defined per BSS.
The NRI is significant only when En_Gb_Flex is enabled in the BSS.
The maximum number of NRIs per SGSN is 8.

Mobile Network
In areas where PS pool areas overlap, the NRI identifies uniquely an SGSN out of all SGSNs, which serve all
these overlapping PS pool areas, i.e. an NRI identifies uniquely an SGSN within a BSS.

4 Gb-Flex
The NRI Is Known by the GP :

Let’s assume one MS performing a RA Update procedure with a valid
P_TMSI.
NRI 1 equal to SGSN1! NRI = 1

Now let me select the
SGSN IP endpoint.
SGSN 1
NSE1
NSE1
NRI=1 NRI = 2
Foreign TLLI
SGSN 2
GP

Mobile Network
If the MS has stored a valid P_TMSI in the SIM, the MS derives a foreign TLLI from that P_TMSI and uses it for
transmission of the following messages:
ATTACH REQUEST message of any GPRS attach procedure.
RA UPDATE REQUEST message procedure if the MS has entered a new RA.
Any other GMM message is transmitted using a local TLLI derived from the P_TMSI or directly using a random
TLLI, which means no valid P_TMSI is available. When the MS does not have a valid P_TMSI stored (that is, the
MS is not attached to GPRS), the MS may use a randomly selected random TLLI for transmission of the ATTACH
REQUEST message of any GPRS attach procedure.

4 Gb-Flex
The NRI Is not Known by the GP

P_TMSI.
NRI3? I don’t know

this relation. So let me NRI = 1
select the SGSN
according to the NAS
NSF.
SGSN 1
NRI = 2
NRI=3
Foreign TLLI SGSN 2
NSF
GP

Mobile Network
If the MS has stored a valid P_TMSI in the SIM, the MS derives a foreign TLLI from that P_TMSI and uses it for
transmission of the following messages:
ATTACH REQUEST message of any GPRS attach procedure
RA UPDATE REQUEST message procedure if the MS has entered a new RA
Any other GMM message is transmitted using a local TLLI derived from the P_TMSI or directly using a random
TLLI, which means no valid P_TMSI is available. When the MS does not have a valid P_TMSI stored (that is, the
MS is not attached to GPRS), the MS may use a randomly selected random TLLI for transmission of the ATTACH
REQUEST message of any GPRS attach procedure.

4 Gb-Flex
The NAS Node Selection Function selects, according to a given

algorithm, an SGSN among all the SGSN available for the BSS in several
PS pool areas where the BSS is defined.
To increase the algorithm capabilities:

A WEIGHT per SGSN is defined to allow load sharing between the
SGSNs.
a SLOW_MOVING_FACTOR is defined to select SLOW_MOVING_FACTOR
times an SGSN previously selected by the NSF
There is no way for the GP board

to know the load in the SGSN.
SGSN 2
SGSN 1
Weight5 Weight10

Mobile Network
The NSF selects an SGSN for a mobile in a cell. The algorithm is done by cell. Each cell is independent and has
no knowledge of the repartition done in the other cells of the same BSS. When the feature is not supported,
En_Gb_flex disabled in the BSS, then the NSF function can be called. But as there is only one SGSN, the NSF
function will always return the same SGSN.
To increase the algorithm capabilities, a weight per SGSN is defined to allow load sharing between the SGSNs.
There is no correlation between the SGSN weight and the number of NRIs per SGSN.
For instance, if SGSN1 has a weight=5 and SGSN2 has a weight=10, then SGSN2 will be selected twice more
often than SGSN1.
There is no way for the GP board to know the load in the SGSN. For instance, once an SGSN is detected in
failure, MSs making UL access are dispatched on the other SGSNs. If the SGSN recovers from a long failure,
then the GP has no way to reach a balanced traffic between the SGSN. (Only the new incoming traffic will be
dispatched on all the SGSNs, all other MS being attached to the other SGSNs).

4 Gb-Flex
The NRI Is not Known by the GP

P_TMSI.
After computation,
the result of the
NAS NSF
algorithm
is SGSN2! NRI = 1
SGSN 1
weight5
NRI=3 NRI = 2
weight10
Foreign TLLI
NSF
SGSN 2
GP

Mobile Network
The NSF selects an SGSN for a mobile in a cell. The algorithm is done by cell. Each cell is independent and has
no knowledge of the repartition done in the other cells of the same BSS. When the feature is not supported,
En_Gb_flex disabled in the BSS, then the NSF function can be called. But as there is only one SGSN, the NSF
function will always return the same SGSN.
To increase the algorithm capabilities, a weight per SGSN is defined to allow load sharing between the SGSNs.
There is no correlation between the SGSN weight and the number of NRIs per SGSN.
For instance, if SGSN1 has a weight=5 and SGSN2 has a weight=10, then SGSN2 will be selected twice more
often than SGSN1.

4 Gb-Flex
NSF Case Usage
The NRI retrieved in the TLLI (foreign or local) is not known.

TLLI is random.
The SGSN associated to the MS context is no more valid (bvc-sig of the
NSEI related to the NRI is no more operational, thze SGSN associated to
the cell where the MS is located is out of service (bvc-ptp of the NSEI
related to the NRI is not (operational, started)).
NRI retrieved in the TLLI with the Null-NRI (network maintenance on
SGSN considered by the GP as “Off –Loaded”).

Mobile Network
Null-NRI
A 'null-NRI' indicates to the GP that the NAS Node Selection Function shall be used to select an SGSN to receive
a message. There is one unique 'null-NRI' in a PLMN supporting the pool functionality.
There are situations where a network operator will wish to remove some load from one SGSN in an orderly
manner (e.g. to perform scheduled maintenance, or to perform load re-distribution to avoid overload) with minimal
impact to end users and/or additional load on other entities. The re-distribution procedure does not require any
new functionality in the terminal, that is, all terminals can be moved.
This is done in the BSS, by removing the SGSN from the NAS Node Selection Function. The SGSN is removed
from the NAS Node Selection Function by setting the attribute SGSN_OFFLOAD_STATE to “off loaded”.
Re-distribution of UEs is initiated via an O&M command in the SGSN, which needs to be off-loaded. In a first
phase (a couple of Periodic LU/RAU periods long), UEs doing LU/RAU or Attach are moved to other SGSNs in
the pool. When the SGSN receives the Location Update, Routing Area Update or Attach request, it returns a new
TMSI/P-TMSI with a null-NRI, and a non-broadcast LAI/RAI in the accept message.

4 Gb-Flex
SGSN Selection Summary

On receipt of the TLLI from an MS by the GP, the processing for selecting
an SGSN is as follows:
Local or foreign TLLI
NRI
NRI NRI
known unknown
OR
Select an SGSN IP Endpoint Select an SGSN

In the SGSN defined by the NRI (NSF function)
Select an SGSN IP Endpoint

in the selected SGSN according to
the IP Endpoint weight

Mobile Network

4 Gb-Flex
Parameters for Feature Activation
The EN_Gb_Flex parameter enables or disables the Gb-Flex feature: It can be set to
enabled only when the Gb transport mode is equal to IP.
NRI_LENGTH_PS must have a value not equal to 0.
NRI_LIST_PS must have at least one significant value.
SGSN_WEIGHT must have a value not equal to 0.
SGSN_OFFLOAD_STATE should be set to on-loaded.
SLOW_MOVING_FACTOR must have a value not equal to 0: It can be set to

disabled only when one SGSN is connected to the BSS.

Mobile Network
NULL_NRI_PS:
Defines the null value for the NRI used with Gb Flex. It is significant only when EN_Gb_Flex is enabled.
N.B.: This parameter must be defined at BSS level. The Null_NRI_PS is valid inside one PLMN. As the MFS can support several BSSs in
several PLMNs, it is not possible to define this parameter at MFS level. This parameter must also be changeable to allow the Gb Flex
introduction in B11 without being obliged to delete and recreate the BSS.
NRI_LENGTH_PS:
Defines the configurable length of an NRI, expressed as a number of bits. It is used by the MFS to derive the NRI value from the received
TLLI, and to identify the serving SGSN, connected to the MFS (Gb Flex feature). It is significant only when EN_Gb_Flex is enabled.
N.B.: This parameter must be defined at BSS level. The NRI length is valid inside one pool area. It is not possible to define this parameter
at MFS level. This parameter must also be changeable to allow the Gb Flex introduction in B11 without being obliged to delete and recreate
the BSS.
SLOW_MOVING_FACTOR:
The number of times one SGSN is used, once selected by the NSF.
EN_GB_FLEX:
Enables/disables the support of the "Gbflex" feature.
NRI_LIST_PS:
The list of the Network Resource Identifiers associated to a given SGSN, connected to the MFS. Up to 8 NRIs can be defined per SGSN
(and at least one).
SGSN_WEIGHT:
The weight assigned to an SGSN, connected to the MFS, for the load balancing function. A high value is to be associated to a high capacity
SGSN, because it will be chosen more often than an SGSN with a lower weight.
SGSN_OFFLOAD_STATE:
The state assigned to a given SGSN, connected to the MFS, for the load redistribution function. That function removes the « off loaded »
SGSN from the list of candidate SGSNs on BSS side.
MAX_NB_SGSN:
The maximum number of SGSNs connected to a BSS (maximum value: 8)

4 Gb-Flex
NRI_LIST_PS
SGSN_WEIGHT
SGSN_OFFLOAD_STATE
MAX_NB_SGSN

Mobile Network
NRI_LIST_PS:
The list of the Network Resource Identifiers associated to a given SGSN, connected to the MFS. Up to 8 NRIs
can be defined per SGSN (and at least one).
SGSN_WEIGHT:
The weight assigned to an SGSN, connected to the MFS, for the load balancing function. A high value is to be
associated to a high capacity SGSN, because it will be chosen more often than an SGSN with a lower weight.
SGSN_OFFLOAD_STATE:
The state assigned to a given SGSN, connected to the MFS, for the load redistribution function. That function
removes the « off loaded » SGSN from the list of candidate SGSNs on BSS side.
MAX_NB_SGSN:
The maximum number of SGSNs connected to a BSS (maximum value: 8)

4 Gb-Flex

NULL_NRI_PS
NRI_LENGTH_PS
SLOW_MOVING_FACTOR
EN_GB_FLEX

Mobile Network
NULL_NRI_PS:
Defines the null value for the NRI used with Gb Flex. It is significant only when EN_Gb_Flex is enabled.
N.B.: This parameter must be defined at BSS level. The Null_NRI_PS is valid inside one PLMN. As the MFS can
support several BSSs in several PLMNs, it is not possible to define this parameter at MFS level. This parameter
must also be changeable to allow the Gb Flex introduction in B11 without being obliged to delete and recreate the
BSS.
NRI_LENGTH_PS:
Defines the configurable length of an NRI, expressed as a number of bits. It is used by the MFS to derive the NRI
value from the received TLLI, and to identify the serving SGSN, connected to the MFS (Gb Flex feature). It is
significant only when EN_Gb_Flex is enabled.
N.B.: This parameter must be defined at BSS level. The NRI length is valid inside one pool area. It is not possible
to define this parameter at MFS level. This parameter must also be changeable to allow the Gb Flex introduction
in B11 without being obliged to delete and recreate the BSS.
SLOW_MOVING_FACTOR:
The number of times one SGSN is used, once selected by the NSF.
EN_GB_FLEX:
Enables/disables the support of the "Gbflex" feature.

Summary
Gb-Flex is a facility allowing a BSS to be connected to more than

one SGSN.
Gb-Flex is an optional feature and is only implemented with the Gb

over IP feature.
A PS Pool area is an area within which an MS can roam without need

to change the serving SGSN.
A PS pool area can be served by one or several SGSNs.
A BSS can belong to several PS pool areas.
The maximum number of SGSNs per BSS is 8.
Gb Flex implies more than one NSE per GP board (maximum 8).

Mobile Network

Summary
On receipt of a TLLI from one MS, the GP is able to:

Identify the SGSN responsible for this MS thanks to the Network Resource
Identifier value if this one is known.
Select an SGSN among several candidate SGSNs according to the NAS Node
Selection Function algorithhm (Weight + Slow_Moving_Factor).
The NRI identifies uniquely an SGSN.
The NRI length is defined per BSS.
8 NRIs maximum can be assigned to one SGSN.

Mobile Network

5 OMC-R Improvements

Mobile Network

5.1 Centralized License Server and Time Validity
Centralized license server for optional features (1/2)

In B10, the management of the optional features locked per quantity is
done on a per OMC basis, thanks to the oflcf file.
oflcf.in
RNIM Yes Request

request is executed.
No
Request cannot be accomplished.

Maximum number of allowed quantities exceeded.
OMC-R
HMI
RNIM RNIM
request request
User X

Mobile Network

5.1 Centralized License Server and Time Validity [cont.]
Centralized license server for optional features (2/2)

Multi-OMC customers may want to negotiate the configured quantities
globally, not on a per OMC basis. Thanks to a centralized server, these
customers can manage the quantities associated to optional features
for the whole network.
oflcf.in oflcf.in oflcf.in
1000 TRXs 1000 TRXs 1000 TRXs
OMC OMC OMC
Upper Limits file

2000 AMR-WB TRXs
Multi-OMC
operator

Mobile Network
The license server will use a limits file (similar to the current oflcf) in order to store the allowed upper limits
of the configured quantities.
For a multi-OMC operator, there will be one oflcf file per OMC and a single limits file containing the
negotiated limits for the whole network.

Time validity for optional features

(2/2)
Time validity allows customers to test
optional features during an evaluation
period. Time validity is a new field
that replaces the license status field oflcf.in
AMR_WB = 2009/08/13
within the oflcf file (which is
currently an On/Off flag). This field
contains the end date of the Yes
RNIM Request
evaluation period, for each optional request is executed.
feature. No
Request cannot be accomplished.

Time validity expired.
OMC-R
HMI
RNIM RNIM
request request
User X

Mobile Network
Validity-date: Its format is yyyy/mm/dd

Range / default value: 0000/00/00..9999/99/99

There is one limit file per

multi-OMC.

Mobile Network

There is one oflcf per OMC.

Mobile Network

Rules
The license manager can be installed either on an OMC, or on
another UNIX® machine.
The limits file MUST be located on one of the concerned OMCs,

irrespective of where the license manager is hosted.
In nominal cases, it is assumed that the license manager and the

limits file will be hosted by the same OMC machine.

Mobile Network

Benefits
The benefits of the Centralized Licence Server and Time Validity for
optional features are:
Managing the optional features locked per quantity in the context of a
multi-OMC configuration.
Offering the trial period facility for the optional features.
The feature is
NOT optional!

Mobile Network

5.2 OMC-R Compatible with the SAN Architecture
Principle in B10
In B10, each OMC has its own disk. Some disks may be under used
while some others are at or near capacity.
OMC 1 OMC 2 OMC 3 OMC 4
Disk 1 Disk 2 Disk 3 Disk 4
Decentralized storage

Mobile Network

5.2 OMC-R Compatible with the SAN Architecture [cont.]
Principle in B11
With the SAN technology, data is consolidated into a single storage
pool. All machines in the Storage Area Network can directly access
this storage pool.
OMC 1 OMC 2 OMC 3 OMC 4
SAN storage
Disk consolidation

Mobile Network

SAN Architecture
A SAN is made up of servers, storage devices (tapes, disk arrays) and
network devices (hubs, routers, switches, etc.). So a SAN constitutes
an entirely separate network from the LAN.
Client Server Disk
Client
LAN SAN
Client
Server Disk

Mobile Network
In a SAN, a variety of servers are connected to various storage devices.

The storage devices form a pool and are externalized from individual servers, allowing the storage pool to be
shared between multiple servers.

SAN Requirements
Storage hardware
Host Bus Adapter (HBA)
Fiber Channel/Gigabit Ethernet switch
Fiber Channel/Gigabit Ethernet cables
SAN file system

Mobile Network
SAN Components
Storage hardware:
Disk-based storage is the primary storage media in any SAN solution. Many SANs also use a tape-based system
for backup. Appropriate storage hardware should offer high-availability features to prevent data loss or
downtime in the event of a disk failure, power outage, or other issue.
Host Bus Adapter (HBA):
An HBA is an adapter (usually a PCI card, such as Qlogic’s 2GB Fibre Channel PCI card, or Qlogic QLA4052C for
the iSCSI solution) that is installed in each node computer in a storage network. An HBA is used to connect the
node to a Fiber Channel/Gigabit Ethernet switch.
Fiber Channel/Gigabit Ethernet switch:
This multiport device provides the interconnections required to connect multiple Fiber Channel storage
devices to computer nodes. Today’s SAN solutions use 1Gb or 2Gb (100MB/s or 200MB/s) Fiber Channel, an
open standard technology for reliable, high-speed storage interconnectivity.
Fiber Channel/Gigabit Ethernet cables:
Fiber Channel cables physically connect all the nodes in a storage network. Copper cables are most
economical and used for short distances. Optical cables can transmit stored data over many kilometers.
SAN file system:
The SAN file system software is the key software component required for building a SAN. A SAN file system
virtualizes multiple physical storage devices into a single volume and makes it visible to all computer nodes in
the SAN. A SAN file system uses a controller to manage metadata, or data about the data, to track the
physical location of files and provide file locking to prevent multiple users from accidentally writing into the
same file at the same time.

Benefits
The cost of management goes down as storage subsystems become
centrally located and easier to manage.
Redundancies are created: if Server 1 fails in a SAN architecture, the
storage on Subsystem 1 can still be accessed via Server 2.
Backup or restore (disk-to-tape or tape-to-disk or disk-to-disk) can
be done without involvement of servers and at higher speeds. Notice
that SAN can do this without increasing the LAN traffic.
File sharing can occur between servers due to any-to-any
connectivity.
Excess capacity can be allocated where needed in a SAN
architecture, instead of being unused in a traditional DAS
architecture.

Mobile Network

5.3 SEC Command Line Interface
In B11, the OMC-R Command Mode is extended so that the operator

is able to perform the same actions with the command mode like in
OMC-R SECUSM.

Mobile Network

5.3 SEC Command Line Interface [cont.]
From the Command Mode, the operator can access the SEC CLI using
the following syntax :
/alcatel/omc3/sec/script/run_accli.pl -login axadmin -password any -

noterminal -nossl -norole -port 6001
An alias will be defined, so this syntax will be transparent for users.
omcdo -SEC
The SEC CLI commands are described in the

ALMAP SEC 7.0, CLI’ User’s Guide.

Mobile Network

5.3 SEC Command Line Interface [cont.]
Benefits
The operator can create scripts that allow him to:
Manage user profiles (creation, deletion, modification, etc.).
Map a profile to user accounts.
Manage Objet Access Domains (OADs).

Mobile Network

5.4 New Sun Hardware Platform
OMC-R Configurations (1/2)

In B11, the OMC-R V490 is replaced by the M4000.
OMC-R SUN Model Processor(s) RAM Disks

configurations
2x1350 MHz
8GB
SunFire™ V490 (or higher) 2x146GB internal disks
Small (or more)
US IV
with or without
NPOE Sun Enterprise™ 2x2.4GHz
8GB 2x146GB internal disks
M4000 Sparc64 VII
2x1350 MHz
8GB
SunFire V490 (or higher) 2x146GB internal disks
(or more)
US IV
Standard
Sun Enterprise 2x2.4GHz
8GB 2x146GB internal disks
M4000 Sparc64 VII
4x1350MHz
16GB 2x146GB internal disks +
Large-1 SunFire V490 (or higher)
(or more) 6 x 73GB EDB SE3510
US IV
and
Large-2 Sun Enterprise 2x2.4GHz 2x146GB internal disks +
16GB
M4000 Sparc64 VII 6x146GB ST2540 2 Ctrl

Mobile Network

5.4 New Sun Hardware Platform [cont.]
OMC-R Configurations (2/2)

In B11, the OMC-R V490 is replaced by the M4000.
OMC-R
SUN Model Processor(s) RAM Disks
configurations
4x1350MHz 16GB 2x146GB internal disks +
X-Large SunFire V490
(or higher) US IV (or more) 12x73GB EDB SE3510
Master
Sun Enterprise 2x2.4GHz 2x146GB internal disks +
16GB
SunFire V490
X-Large (or higher)US IV (or more) 6x73GB EDB SE3510
Agent Sun Enterprise 2x2.4GHz 2x146GB internal disks +
16GB
SunFire V490
(or higher) US IV (or more) 12x73GB EDB SE3510
XX-Large Master
Sun Enterprise 2x2.4GHz 2x146GB internal disks +
16GB

SunFire V490 (or higher) US IV (or more) 6x73GB EDB SE3510
XX-Large Agent
Sun Enterprise 2x2.4GHz 16GB 2x146GB internal disks +

Mobile Network

6 HMI Improvements

Mobile Network

6 HMI Improvements
6.1 Copy and Paste Data into OMC-R Forms
In B11, all text boxes and objects become editable to allow the user to
copy and paste data.
1. Select
2. Paste

Mobile Network

6 HMI Improvements
6.2 Edit n Adjacencies
The purpose of this feature is to allow the user to modify one or more
adjacency parameters on several adjacencies in one shot.
1. Select one or more

parameters
2. Modify the value

Mobile Network

6 HMI Improvements
6.2 Edit n Adjacencies [cont.]
The Edit N Adjs button allows the user to modify the parameters for all
the selected adjacencies. This option is available only from the PRC
windows.

Mobile Network

6 HMI Improvements
6.3 Customization of BTS External Alarms
In B11, the OMC-R offers the possibility to create several profiles of BTS
External Alarms.

Mobile Network

6 HMI Improvements
6.3 Customization of BTS External Alarms [cont.]
In the BSSUSM view, the user can assign an External Alarm Profile to a
BTS.

Mobile Network

6 HMI Improvements
6.4 Load Indicators of OMC
Performance indicators are available for most of the Network Elements

of the BSS. But only few information are provided on the resources of
the OMC-R.
In addition to the CPU and the Memory load provided by the Multi
Router Traffic Grapher (MRTG), the set of Load indicators is extended
by integrating the ORCA solution.

Mobile Network

6 HMI Improvements
6.4 Load Indicators of OMC [cont.]
View all the data View one data

for a period for a period

Mobile Network

6 HMI Improvements
6.4 Load Indicators of OMC [cont.]
Example of indicators

Mobile Network

6 HMI Improvements
6.5 Fast Measurement Mode for BSC Investigation
In B10, the Permanent Measurement Campaign (PMC), that includes the

counters reported in measurement type 110, has an accumulation
period of at least 30 minutes. As a consequece, the first measurements
are available between 60 and 90 minutes after a network operation.
Network Measurements
Operation are available
T0 T0+30’ T0+60’ T0+90’
Meaningless Accumulation
Period Period Transfer to NPO

Mobile Network

6 HMI Improvements
6.5 Fast Measurement Mode for BSC Investigation [cont.]
The purpose of this feature is to reduce the accumulation period of

counters type 110 to 15 minutes for only one BSC at a time during a
limited period. With this feature the first measurements will be
available between 45 and 60 minutes after a network operation.
Reduced
accumulation Network Reduced accumulation
period activation Operation period deactivation
T0-30’ T0 T0+15’ T0+30’ T0+45’ T0+60’ T0+90’
Meaningless
Period Measurements
are available
Accumulation
Period
Transfer to NPO

Mobile Network

6 HMI Improvements
The activation of
the feature is
done in the
BSSUSM/Campaig
ns Supervision
view.
The OMC-R user
first enters a
minimum number
of reduced
accumulation
periods, then
activates them.

Mobile Network

6 HMI Improvements
Rules
It is possible to reduce the accumulation period only for counters
type 110 that is used in the Permanent Measurement Campaign.
Only one BSC can have a reduced accumulation period at a time.
It is possible to reduce the accumulation period for the counter type
110 to 15 minutes, from 2 up to 4 intervals.
It is not possible to define a reduced accumulation period out of a
recording interval (the first one or the second one).
To avoid disturbances in the normal reporting periods planned for all
BSCs, the reduced accumulation period can start at any 15' boundary,
but must end at the end of a normal accumulation period.

Mobile Network

6 HMI Improvements
6.6 Software Migration Improvements
In B11, a new view is created in order to pilot the migration of all

the BSSs from one single screen.
New

Mobile Network

6 HMI Improvements
6.6 Software Migration Improvements [cont.]
It is possible to pilot the software replacement of all the BSSs from

one single screen.
It is no longer needed to stop the Permanent Measurement
Campaigns before the migration (the counters are available during
the migration, but not during the activation).
QoS can be checked 30’ (or 1 hour, according to the reporting
period) after the activation of the software, without waiting for the
end of the audits.
Several actions are chained together, like the preparation of the SW
package and its download and preload.
The operator can still follow all the steps of the migration
in the BSSUSM/Software Management view.

Mobile Network

6 HMI Improvements
The operator has access to this new view from the DCN window or
from the RNUSM window.
RNUSM Window
DCN Window

Mobile Network

6 HMI Improvements
New Reports
2 new reports are available during and at the end of the migration:
the Resources report informs the user on the status of BSS resources
Total number of N7 or ASL support resources
Total number of OML support resources
Number of BTSs whose O&M capability is locked
Etc.
the Differencial report keeps an history of 2 snapshots after migration
allowing the operator to compare the initial status with the 1st status
snapshot after migration, and the 1st snapshot with a 2nd one taken later
on.
This report also lists all active alarms with their perceived severity.

Mobile Network

6 HMI Improvements
Lock Mechanism
To avoid some conflicts, all configuration actions are locked during a
SW migration.
This lock mechanism works from the moment the SW package is
generated until the end of the audit following the activation or the
abort.
If a user attempts to activate a PRC during a SW replacement, the
PRC activation request is rejected.

Mobile Network

6 HMI Improvements
6.7 New ALMAP FM Module
The evolution of ALMAP leads to the replacement of the existing AS

Module for Fault Management.

Mobile Network

6 HMI Improvements
6.7 New ALMAP FM Module [cont.]
Main counter
of alarms
Alarms of
one sublist
The alarms are

listed per page

Mobile Network

6 HMI Improvements
6.7 New ALMAP FM Module [cont.]
Modify a sublist
Create a sublist
Create some filters

Mobile Network

7 Exercises

Mobile Network
Section @@SECTION
BSS B10 B11 O&M
Module
Evolution
@@MODULE
Page 132
Page 132
7 Exercises
7.1 A Signaling over IP
Is the following statement true or false?

With A Signaling over IP, the signaling between the BSC and the MSC
goes through the TC.
True
False

Mobile Network
Section @@SECTION
BSS B10 B11 O&M
Module
Evolution
@@MODULE
Page 133
Page 133
7 Exercises
7.1 A Signaling over IP [cont.]

We can have one BSS using A Signaling Over IP and one BSS using A
Signaling Over TDM.
True
False

Mobile Network
Section @@SECTION
BSS B10 B11 O&M
Module
Evolution
@@MODULE
Page 134
Page 134
7 Exercises

The A Signaling Over IP feature is activated by a command on the BSC
Terminal.
True
False

Mobile Network
Section @@SECTION
BSS B10 B11 O&M
Module
Evolution
@@MODULE
Page 135
Page 135
7 Exercises
In A Signaling Over IP, which protocol is used to transfer the SCCP

signaling?
MTP
M3UA
M2UA

Mobile Network
Section @@SECTION
BSS B10 B11 O&M
Module
Evolution
@@MODULE
Page 136
Page 136
7 Exercises
7.2 A Flex Signaling

We can use A-signaling over IP whatever the generation of the BSC.
True
False

Mobile Network
Section @@SECTION
BSS B10 B11 O&M
Module
Evolution
@@MODULE
Page 137
Page 137
7 Exercises
7.2 A Flex Signaling [cont.]
With what can the A-Flex feature work?
A Signaling over TDM
A Signaling over IP
Both

Mobile Network
Section @@SECTION
BSS B10 B11 O&M
Module
Evolution
@@MODULE
Page 138
Page 138
7 Exercises

If the TMSI is included in the initial layer 3 message, the BSC can
recover the MSC address.
True
False

Mobile Network
Section @@SECTION
BSS B10 B11 O&M
Module
Evolution
@@MODULE
Page 139
Page 139
7 Exercises
Let's suppose that we have 2 MGWs and 6 MSC Servers for a

configuration of 48 Atermux CS.
How many static A-Flex partitions do we have?
2 6 8 10 12
How many A-trunks are there?

48 96 144 192
How many A-trunks will we have per A-Flex partition?
4 8 12 16 24

Mobile Network
Section @@SECTION
BSS B10 B11 O&M
Module
Evolution
@@MODULE
Page 140
Page 140
7 Exercises
7.3 STM-1 BSC
What does the STM-1 BSC feature allow?
To connect one 9130 BSC to one SDH network via STM-1 links
To connect one 9130 BSC to one SDH network via E1 links thanks to an ADM
To connect any BSC to one SDH network via STM-1 links
To connect the 9130 BSC to one SDH network via E1 links thanks to an ADM

Mobile Network
Section @@SECTION
BSS B10 B11 O&M
Module
Evolution
@@MODULE
Page 141
Page 141
7 Exercises
7.3 STM-1 BSC [cont.]
What does the STM-1 BSC feature require?
One 9130 BSC equipped with at least oneJBXTP3 board
One 9130 BSC equipped with two JBXTP3 boards
One 9130 BSC equipped with two JBXTP board whatever the version

Mobile Network
Section @@SECTION
BSS B10 B11 O&M
Module
Evolution
@@MODULE
Page 142
Page 142
7 Exercises
What is the maximum number of VC 12 per STM-1?
48
63
128
155

Mobile Network
Section @@SECTION
BSS B10 B11 O&M
Module
Evolution
@@MODULE
Page 143
Page 143
7 Exercises
Is it possible to mix STM-1 links with physical E1 links on the Atermux

interface?
Yes
No

Mobile Network
Section @@SECTION
BSS B10 B11 O&M
Module
Evolution
@@MODULE
Page 144
Page 144
7 Exercises

When the “STM-1 BSC” facility is activated, the Abis interface should be
declared as E1 links.
True
False

Mobile Network
Section @@SECTION
BSS B10 B11 O&M
Module
Evolution
@@MODULE
Page 145
Page 145
7 Exercises
Is the STM-1 configuration change possible from the OMC-R?
Yes
No

Mobile Network
Section @@SECTION
BSS B10 B11 O&M
Module
Evolution
@@MODULE
Page 146
Page 146
7 Exercises
7.4 Gb-Flex
What does the Gb-Flex allow ?
To connect a BSS to more than one SGSNs
To connect a BSS to one SGSN with more than one GP boards

Mobile Network
Section @@SECTION
BSS B10 B11 O&M
Module
Evolution
@@MODULE
Page 147
Page 147
7 Exercises
7.4 Gb-Flex [cont.]

The Gb-Flex is a facility which requires Gb over IP.
True
False

Mobile Network
Section @@SECTION
BSS B10 B11 O&M
Module
Evolution
@@MODULE
Page 148
Page 148
7 Exercises
7.4 Gb-Flex [cont.]

The maximum number of SGSN connected to one BSS in case of Gb-Flex
activation is 8.
True
False

Mobile Network
Section @@SECTION
BSS B10 B11 O&M
Module
Evolution
@@MODULE
Page 149
Page 149
7 Exercises
7.4 Gb-Flex [cont.]
Let’s assume one MS performing a GPRS attach procedure without

having a valid P_TMSI.
At reception of the random TLLI by the GP board, the selection of the
SGSN will be processed thanks to :
NRI
NAS NSF

Mobile Network
Section @@SECTION
BSS B10 B11 O&M
Module
Evolution
@@MODULE
Page 150
Page 150
7 Exercises
7.4 Gb-Flex [cont.]

The Gb-Flex implies more than one NSE per GP board.
True
False

Mobile Network
Section @@SECTION
BSS B10 B11 O&M
Module
Evolution
@@MODULE
Page 151
Page 151
7 Exercises
7.5 OMC-R HMI and Supervision Improvements

There will be a limits file and an oflcf file in each OMC.
True
False

Mobile Network
Section @@SECTION
BSS B10 B11 O&M
Module
Evolution
@@MODULE
Page 152
Page 152
7 Exercises
7.5 OMC-R HMI and Supervision Improvements [cont.]

It is now possible to create a user and to assign him/her rights by
command.
True
False

Mobile Network
Section @@SECTION
BSS B10 B11 O&M
Module
Evolution
@@MODULE
Page 153
Page 153
7 Exercises

It is possible to assign several profiles of BTS External Alarms to a BTS.
True
False

Mobile Network
Section @@SECTION
BSS B10 B11 O&M
Module
Evolution
@@MODULE
Page 154
Page 154
7 Exercises

For which type of counter does the Fast Measurement Mode for BSC
Investigation feature allow to reduce the accumulation period?
Counter type 110
Counter type 180
Both of them

Mobile Network
Section @@SECTION
BSS B10 B11 O&M
Module
Evolution
@@MODULE
Page 155
Page 155
Abbreviations and Acronyms
#
3GPP Third Generation Partnership Project IP Internet Protocol
Switch to notes view! IPMI Intelligent Platform Management
A Interface
A BSS-MSC interface IPoE1 IP over E1
Abis BTS-BSC interface IpoEth IP over Ethernet
ADM Add-Drop Multiplexer IpoRS232 IP over RS232
ALMAP Alcatel-Lucent Management Platform IPSec IP Security
AMR-WB Adaptive Multi-Rate – WideBand IPSP IP Server Process
APS Automatic Protection Switching
AS Alarm Surveillance L
AS Application Server LA Location Area
ASL A Signaling Link LAN Local Area Network
AterMUX Ater Interface sub-Multiplexed LDAP Lightweight Directory Access Protocol
LMT Local Maintenance Terminal
B LSL Low-speed Signaling Link
BSC Base Station Controller
BSS Base Station Subsystem M
BSSAP Base Station Subsystem Application M3UA MTP3 User Adaptation
Protocol MFS Multi-BSS Fast Packet Server
BSSUSM BSS User Services Manager MGW Media GateWay
BTS Base Transceiver Station MIB Management Information Base
MLPPP Multi-Link PPP
C MMI Man-Machine Interface
CAPEX Capital Expenditures MRTG Multi Router Traffic Grapher
CLI 156 Command Line Interface MS 2010
All Rights Reserved © Alcatel-Lucent Mobile Station
Mobile Network
C-n BSS B10 B11Container
O&M Evolution n MSC Mobile services Switching Center
CN Core Network MSOH Multiplexer SOH
CPU Central Processing Unit MTP Mobile Signaling Unit
CS Circuit Switching MTP n Message Transfer Part level n
MX Multistandard controller platform
D
DAS Distributed Authorization Server N
DCN Data Communication Network NAS Non Access Stratum
DHCP Dynamic Host Configuration Protocol NAS Network Access Server
DPC Destination Point Code NE Network Element
DTM Dual Transfer Mode NE1oE n E1 over Ethernet
NEM Network Element Manager
E NGN Next Generation Network
EPS Equipment Protection Switching NPO Network Performance Optimizer
NRI Network Resource Identifier
F NSS Network Subsystem
FM Fault Management
FTP File Transfer Protocol O
O&M Operation and Maintenance
G OAD Object Access Domain
GSM Global System for Mobile OC-x Optical Carrier x
communications OMC Operation and Maintenance Center
OMC-R Operation and Maintenance Center-
H Radio
HBA Host Bus Adapter OML Operation and Maintenance Link
HDLC High-level Data Link Control OPC Origin Point Code
HLR Home Location Register OPEX Operational EXpenditures
HMI Human-Machine Interface OS Operating System
HSL High-speed Signaling Link
HW HardWare P
PC Personal Computer
I PCI Peripheral Component Interconnect
IE Information Element PCM Pulse Code Modulation
IMSI International Mobile Subscriber Identity PDH Plesiochronous Digital Hierarchy

Abbreviations and Acronyms
Q
PLMN Switch to notes
Public Land view!
Mobile Network U
PMC Permanent Measurement Campaign UDP User Datagram Protocol
POH Path OverHead
PPP Point-to-Point Protocol V
PRC Provisioning Radio Configuration VC Virtual Circuit
PS Packet Switching VC Virtual Container
PSTN Public Switched Telephone Network VLAN Virtual Local Area Network
PTR Pointer VLR Visitor Location Register
VMGW Virtual Media GateWay
Q
QoS Quality of Service
R
RA Routing Area
RADIUS Remote Authentication Dial In User
Service
RNIM Radio Network Information Manager
RNUSM Radio Network User Services Manager
RSOH Regenerator SOH
S
SAN Storage Area Network
SBL Security Block
SCCP Signaling Connection Control Part All Rights Reserved © Alcatel-Lucent 2010
157
SCSI Mobile Network
Small Computer System Interface
SCTP Stream Control Transport Protocol
SDH Synchronous Digital Hierarchy
SE Supplementary Element
SEC Security
SECUSM Security User Services Manager
SFP Small Form Factor Pluggable
SFTP Secured File Transfer Protocol
SGSN Serving GPRS Support Node
SLH Signaling Link Handling
SNMPV3 Simple Network Management Protocol
version 3
SOH Section Overhead
SPC Signaling Point Code
SS7 Signaling System no.7
SSW Subrack Switch
STM-1 Synchronous Transport Module level 1
SW SoftWare
T
TC TransCoder
TCP Transmission Control Protocol
TDM Time-Division Multiplexing
TLS Transport Layer Security
TMSI Temporary Mobile Subscriber Identity
TP Transmission Path
TRA TRE with 8-PSK capacity
TRE Transceiver Equipment
TRX Transceiver
TS Time Slot
TS Technical Specification
TUG Tributary Unit Group
TU-n Tributary Unit n

Blank Page

Mobile Network
BSS B10 B11 O&M Evolution This page is left blank intentionally

End of Module

Mobile Network

Tmo18074d0sgdeni4.0 Ce PDF

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Tmo18074d0sgdeni4.0 Ce PDF

Загружено:

Авторское право:

Доступные форматы

Do not delete this graphic elements in here:

All Rights Reserved © Alcatel-Lucent 2010

BSS B10 B11 O&M Evolution Page 1

2 All Rights Reserved © Alcatel-Lucent 2010

Edition Date Author Remarks

01 YYYY-MM-DD Last name, first name First edition

BSS B10 B11 O&M Evolution Page 2

Upon completion of this module, you should be able to:

3 All Rights Reserved © Alcatel-Lucent 2010

BSS B10 B11 O&M Evolution Page 3

4 All Rights Reserved © Alcatel-Lucent 2010

BSS B10 B11 O&M Evolution Page 4

Abbreviations and Acronyms 156

BSS B10 B11 O&M Evolution Page 5

6 All Rights Reserved © Alcatel-Lucent 2010

BSS B10 B11 O&M Evolution Page 6

7 All Rights Reserved © Alcatel-Lucent 2010

BSS B10 B11 O&M Evolution Page 7

Principle in B10: In B10, the A9130 BSC Evolution communicates with

8 All Rights Reserved © Alcatel-Lucent 2010

BSS B10 B11 O&M Evolution Page 8

Principle in B11: In B11, the purpose of the A Signaling Over IP feature

9 All Rights Reserved © Alcatel-Lucent 2010

BSS B10 B11 O&M Evolution Page 9

Why A Signaling over IP?

10 All Rights Reserved © Alcatel-Lucent 2010

BSS B10 B11 O&M Evolution Page 10

A Signaling over TDM is still supported.

11 All Rights Reserved © Alcatel-Lucent 2010

BSS B10 B11 O&M Evolution Page 11

BSSAP Protocol Stack over TDM

BSSAP The TC is transparent BSSAP

12 All Rights Reserved © Alcatel-Lucent 2010

BSS B10 B11 O&M Evolution Page 12

BSSAP Protocol Stack over IP

13 All Rights Reserved © Alcatel-Lucent 2010

BSS B10 B11 O&M Evolution Page 13

BSSAP Protocol Stack in the BSC

: IP mode : TDM mode

The Signaling Link Handling (SLH) is an MTP3 Layer Function.

BSS B10 B11 O&M Evolution Page 14

Application Server (AS)

IP Server Process (IPSP)

15 All Rights Reserved © Alcatel-Lucent 2010

The IPSP is one process that handles the M3UA/SCTP.

BSS B10 B11 O&M Evolution Page 15

For each MSC, we can have up to 4 ASLs.

16 All Rights Reserved © Alcatel-Lucent 2010

The IPSP is one process that handles the M3UA/SCTP.

BSS B10 B11 O&M Evolution Page 16

17 All Rights Reserved © Alcatel-Lucent 2010

BSS B10 B11 O&M Evolution Page 17

18 All Rights Reserved © Alcatel-Lucent 2010

BSS B10 B11 O&M Evolution Page 18

19 All Rights Reserved © Alcatel-Lucent 2010

To create an ASL, the following information is required:

The LOCAL_ASIG_SCTP_ENDPOINT_IP_ADDRESS_1 and LOCAL_ASIG_SCTP_ENDPOINT_PORT are read only.

BSS B10 B11 O&M Evolution Page 19

New Alarms (1/2)

RMH-REP: This alarm is for the Multi-Homing feature and it is only

MSC-REP: This alarm is reported when the AS is INACTIVE.

20 All Rights Reserved © Alcatel-Lucent 2010

BSS B10 B11 O&M Evolution Page 20

New Alarms (2/2)