MFS Alcatel PDF

Alcatel 9130 MFS/BSC
Alcatel 9130 MFS Evolution

Description / B9
3FL12335ABAAWBZZA
Edition 3
TRAINING MANUAL
Alcatel 9130 MFS Evolution Description / B9

All rights reserved © 2006, Alcatel
Copyright © 2006 by Alcatel - All rights reserved

Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from Alcatel
Page 1
Safety Warning
Both lethal and dangerous voltages are present within the equipment. Do not wear conductive jewellery
while working on the equipment. Always observe all safety precautions and do not work on the
equipment alone.
Caution
The equipment used during this course is electrostatic sensitive. Please observe correct anti-static
precautions.
Trade Marks
Alcatel and Main Street are trademarks of Alcatel.
All other trademarks, service marks and logos (“Marks”) are the property of their respective holders
including Alcatel. Users are not permitted to use these Marks without the prior consent of Alcatel or such
third party owning the Mark. The absence of a Mark identifier is not a representation that a particular
product or service name is not a Mark.
Copyright
This document contains information that is proprietary to Alcatel and may be used for training purposes
only. No other use or transmission of all or any part of this document is permitted without Alcatel’s
written permission, and must include all copyright and other proprietary notices. No other use or
transmission of all or any part of its contents may be used, copied, disclosed or conveyed to any party in
any manner whatsoever without prior written permission from Alcatel.
Use or transmission of all or any part of this document in violation of any applicable Canadian or other
legislation is hereby expressly prohibited.
User obtains no rights in the information or in any product, process, technology or trademark which it
includes or describes, and is expressly prohibited from modifying the information or creating derivative
works without the express written consent of Alcatel.
Alcatel, The Alcatel logo, Main Street and New bridge are registered trademarks of Alcatel.
All other trademarks are the property of their respective owners. Alcatel assumes no responsibility for the
accuracy of the information presented, which is subject to change without notice.
© 2005 Alcatel. All rights reserved.
Disclaimer
In no event will Alcatel be liable for any direct, indirect, special, incidental or consequential damages,
including lost profits, lost business or lost data, resulting from the use of or reliance upon the
information, whether or not Alcatel has been advised of the possibility of such damages.
Mention of non-Alcatel products or services is for information purposes only and constitutes neither an
endorsement nor a recommendation.
Please refer to technical practices supplied by Alcatel for current information concerning Alcatel
equipment and its operation.
Page 2
Course title : B9 / Alcatel 9130 MFS Evolution Description
Reference : 3FL12335ABAAZZZZA Teaching languages :
Standard duration Training methods
Theoritical method
6
Total duration (hrs) 6 Sequence :
Maximum number of participants : 12 (Only applicable to c-learning and v-learning)
Audience :
Personnel in charge of operating the Alcatel 9130 MFS Evolution
Objectives :
By the end of the course, participants will be able to:
- locate and justify the equipment in the Alcatel GPRS network,
- describe the telecom functions of the equipment,
- describe the hardware organization,
- describe the software organization,
- describe the SW and HW cooperation for defense mechanisms
- discover the Man to Machine Interface possibilities useful for equipment maintenance and supervision
Prerequisites :
Training module “Introduction to GPRS – 3FL 10472 ACAA”.
Course contents: 5 Defense Mechanisms

· Software defense
1 The MFS Evolution within the Alcatel GPRS
· Hardware defense
Network
· Overview of the Alcatel GPRS solution
· Possible interconnections of the equipment
6 Man/Machine Interface
· Equipment access possibilities
. Common view from Maintenance Terminal or
2 MFS Telecom Function Description · Introduction
OMC
· The PCU functions
3 Hardware Description
· What is the MX concept ?
· General hardware architecture
· Description of the ATCA rack
· Main components of the MFS Evolution
· Configurations and performances
4 Software Description
· General organization
· The Tomix Middleware
· The MFS Evolution application software
Page 3
Page intentionally left blank
Page 4
Objectives Contract number :
Course title : Alcatel 9130 MFS Evolution Description /B9
Client (Company, centre) :
Language : dates from : to :
Number of trainees : Location :
Surname, First name :
Did you meet the following objectives ?

Tick the corresponding box
Please, return this sheet to the trainer at the end of the training
Yes (or No (or
Instructional objectives Globally globally Comments
yes) no)
1 - To be able to locate and justify the equipment in
the Alcatel GPRS network
2 - To be able to describe the telecom functions of

the equipment
3 - To be able to describe the hardware

organization
4 - To be able to describe the software organization
5 - To be able to describe the SW and HW

cooperation for defense mechanisms
6 - To be able to discover the Man to Machine
Interface possibilities useful for equipment
maintenance and supervision
Page 5
Objectives (continued)
Yes (or No (or
Instructional objectives Globally globally Comments
yes) no)
Other comments
Thank you for your answers to this questionnaire

Page 6
1 The MFS Evolution within the
Alcatel GPRS Network

Page 7
1 The MFS Evolution within the Alcatel GPRS Network
Section presentation
8
Objective : to be able to locate the MFS Evolution

in the Alcatel GPRS Network, to identify its external
interfaces and its main characteristics
Program :
1.1 Overview of the Alcatel GPRS Solution
1.2 Possible interconnections of the equipment
Alcatel 9130 MFS Evolution Description / B9 All rights reserved © 2006, Alcatel
Page 8
1.1 The MFS Evolution environment

Page 9
Subsystem view
10
MSC/
TC VLR PSTN
HLR
BSC Gs Gr
BTS GSM CoreNetwork
BTS MFS
Ater
Abis Mux GGSN
Gb Gn IP Gi Internet
SGSN Backbone Intranet
Radio Access Network
2 3
Charging Border
1 Gateway DNS/ Gateway
DHCP
GPRS & EGPRS Core Network
Page 10
MFS functions
11
The Multi BSS Fast packet Server (MFS) :

performs the GPRS Packet Control Unit (PCU) functions (3GPP 03.60
standard)
manages the Gb interface with the GPRS & EGPRS core network
MFS
GPRS & EGPRS

BSC AterMux Gb
Core Network
Page 11
SGSN function
12
The SGSN stores subscriber data : SGSN

Subscription information
• International Mobile Subscriber Identity (IMSI)
• one or more temporary identities (P-TMSI)
• zero or more PDP addresses
Location information
• the cell or the Routing Area (RA) where the MS is registered
• the VLR number of the associated VLR (if the Gs interface is implemented)
• the address of each GGSN for which an active PDP context exists
Page 12
GGSN function
13
The GGSN stores subscriber data received from the HLR and the SGSN :
Subscription information GGSN
• IMSI
• zero or more PDP addresses
Location information
• the address of the SGSN where the MS is registered
Page 13

Page 14
Standard interconnection
15
MSC
Ater TC
Mux
Ater A
Mux
BSC PCU
BTS
GP board GGSN
SGSN
MFS
Gb
OMC-R IMT
CS traffic
GPRS traffic
Ethernet link
See Annex 7.2 for other connecting possibilities
Page 15
Exercise 1/2
16
Objective : to be able to locate the Alcatel 9130

MFS within the GPRS Alcatel solution
- Is the MFS specified by the 3GPP standard ?
- Is the MFS part of the BSS?
- What are the functions managed by the MFS ?
- What types of traffic are managed by the MFS ?
- Does the MFS keep track of the individual MS location ?
Time allowed:
3 minutes
Page 16
Exercise 2/2
17
In the white rectangles, identify the equipments (straight lines) and the
interfaces (doted lines)
MSC
Ater TC
Mux
Ater
Mux
BSC PCU
BTS
GP board GGSN
SGSN
MFS
Gb
Time allowed:
3 minutes
OMC-R IMT
CS traffic
GPRS traffic
Ethernet link
Page 17
Evaluation
18
Objective : to be able to locate the MFS

Evolution in the Alcatel GPRS Network,
to identify its external interfaces and its
main characteristics
Thank you for answering

the objective sheet
Page 18
2 MFS Telecom Function
description

Page 19
2 MFS Telecom Function Description
20
Objective : to be able to describe the telecom functions

of the equipment
Program :
2.1 Introduction
2.2 The PCU functions
Page 20
description
2.1 Introduction

Page 21
2.1 Introduction
General description
22
The MFS Evolution includes

Telecom Functions (= PCU functions)
O&M Functions
The present chapter will focus on the Telecom Functions implemented by the
PCU Function defined in 3GPP 03.64
The O&M functions will be described in chapter 4 “ Software Description”
PCU functions are defined in 3GPP 03.64.

The functions inside the Channel Codec Unit (CCU) are:
the channel coding functions, including Forward Error Correction (FEC) and interleaving
radio channel measurement functions, including received quality level, received signal level and
information related to timing advance measurements.
The BSS is responsible for the allocation and de-allocation of radio resources. A PCU frame must be transferred
between the PCU and the BTS every 20 ms.
Page 22
description

Page 23
What do they consist in ?
24
The main PCU functions implement :

LLC PDU segmentation / re-assembly into RLC/MAC PDU
PDCH scheduling (resource multiplexing)
Channel access control (access requests and grants)
ARQ function (RLC block Ack / Nak, buffering and retransmission of RLC
blocks)
Radio channel management (power control, congestion control,
broadcast control information)
PCU functions are defined in 3GPP 03.64.

The functions inside the Channel Codec Unit (CCU) are:
the channel coding functions, including Forward Error Correction (FEC) and interleaving
radio channel measurement functions, including received quality level, received signal level and
information related to timing advance measurements.
The BSS is responsible for the allocation and de-allocation of radio resources. A PCU frame must be transferred
between the PCU and the BTS every 20 ms.
ARQ = Automatic Repeat Request
Page 24
LLC PDU segmentation /re-assembly
25
LLC PDU segmentation / re-assembly into RLC/MAC PDU

Radio blocks
Abis Um
SGSN Gb MFS A-ter mux
BSC BTS GPRS: 456 symbols
Channel EGPRS: 464 symbols
coding
Re-assembly
PDCH 1
LLC
Segmentation
PDCH 2
PDUs M-EGCH
On TRX 1
M-EGCH PDCH 3
PDCH 4
PDCH 5
On TRX 2
Transmission and reception data flows are the same for GPRS and EGPRS, except for EGPRS MCS-9, MCS-8 and MCS-7, where
4 normal bursts carry 2 RLC blocks (1 RLC block within 2 bursts for MCS-9 and MCS-8).
Radio blocks are transported on the air interface (Um) over 4 consecutive normal bursts of the TDMA frame.
The GPRS normal burst is composed of 156.25 symbols (1 bit for 1 symbol, GMSK only):
• 6 tail symbols,
• 26 training sequence symbols,
• 114 encrypted symbols,
• 2 stealing flags (2 symbols, used to specify the coding scheme),
• 8.25 guard period (symbols).
For GPRS, the radio blocks are transported by 114 x 4 = 456 symbols.
The E-GPRS burst is composed of 156.25 symbols (3 bits for 1 symbol in case of 8-PSK and 1 bit for 1 symbol in case of GMSK):
• 6 tail symbols,
• 26 training sequence symbols,
• 116 encrypted symbols (there is stealing flags),
• 8.25 guard period (symbols).
For E-GPRS, the radio blocks are transported by 116 x 4 = 464 symbols.
The interface between BTS and MFS is called M-EGCH and it consists in a set of GCHs which are statistically shared by
all the PDCHs of one TRX.
The Statistical Multiplexing feature shall allow to reduce the consumption of GCH resources (especially on Ater) by
multiplexing the blocks of all the PDCHs of a TRX on a single transmission link: the M-EGCH link, instead of using a
single EGCH link per PDCH. So the (M)CS variations of the TBFs mapped on a TRX can compensate each other
without requiring more transmission resources.
Page 25
PDCH scheduling 1/3
26
PDCH scheduling
A PDCH can be shared by several MSs
A TBF can be allocated on several PDCHs
A PDCH can be shared by a GPRS and an EGPRS MS. However, when a
PDCH is shared between a UL GPRS TBF and a DL EGPRS TBF, the DL EGPRS
TBF cannot use 8-PSK.
allocation of reso
n a mic urc
Dy es
Pool
of radio
resources
Subscribers
Page 26
PDCH scheduling 2/3
27
PDCH scheduling
For a DL or UL transfer, an MS is provided with a TBF
• a set of radio blocks is allocated on one or more PDCHs
• a TBF is temporary and is maintained only for the duration of the transfer
A TBF establishment is requested :
• by the MS for a UL transfer
• by the MFS for a DL transfer
Each TBF is :
• assigned a Temporary Flow Identity (TFI)
• unique in each direction, within a cell
Page 27
PDCH scheduling 3/3
28
PDCH scheduling (example)
There is one
M-EGCH for all the
PDCHs of a TRX
(TRE)
(GPU)
The interface between BTS and MFS is called M-EGCH and it consists in a set of GCHs which are statistically
shared by all the PDCHs of one TRX.
Page 28
PDCH allocation in a cell 1/2
29
PDCH allocation in a cell (1/2)
Periodically, based on the CS and PS load of the cell, the BSC

builds the SPDCHs_Allocation bitmap and sends a RR
Allocation Indication message to the MFS.
RR Allocation Indication
MFS BSC
RR Usage Indication
Periodically, MFS sends to the BSC a RR Usage Indication

message which contains a confirmation of the allocated SPDCHs
as well as the usage of the SPDCHs
A PDCH can be master (MPDCH) dedicated to GPRS signaling or slave (SPDCH) dedicated for traffic and signaling.
Page 29
PDCH allocation in a cell 2/2
30
RESERVED FOR PS
MIN_SPDC
PRIORITY FOR PS H
MAX_SPDCH_HIGH_LOAD
PRIORITY FOR CS MAX_SPDCH_LIMIT
MAX_SPDCH
RESERVED FOR CS
Every TCH_INFO_PERIOD * RR_ALLOC_PERIOD seconds, according to the load and the settings of the cell, the BSC
evaluates the number of SPDCH which must be allocated to the MFS (MAX_SPDCH_LIMIT) and builds the SPDCH
allocation bitmap which is sent to the MFS in the RR Allocation Indication message.
MIN_PDCH: Minimum number of master and slave PDCHs that are always allocated to the MFS.
MAX_PDCH_HIGH_LOAD: Maximum number of slave and master PDCHs that can be allocated to the MFS when the
CS traffic is high.
MAX_PDCH: Maximum number of slave and master PDCHs that can be allocated to the MFS in the cell.
MIN_SPDCH, MAX_SPDCH and MAX_SPDCH_HIGH_LOAD are computed by the BSC according to the value of
MIN_PDCH, MAX_PDCH, MAX_PDCH_HIGH_LOAD, NB_TS_MPDCH and a weighting factor which depends on the
availability of the TRXs of the cell.
NB_TS_MPDCH is the number of MPDCHs of the cell (these are statically allocated).
Page 30
Exercise 1/1
31
Describe 3 of the PCU functions (2 minutes)
Time allowed :
3 minutes
Page 31
Evaluation
32
Objective : to be able to describe the

telecom functions of the equipment

the objective sheet
Page 32

Page 33
34
Objective : to be able to describe the hardware

organization of the MFS Evolution equipment
Program :
3.1 What is the MX Concept ?
3.2 General hardware architecture
3.3 Description of the ATCA rack
3.4 Main components of the MFS Evolution
3.5 Configurations and performance
Page 34
3.1 What is the MX concept ?

Page 35
Presentation 1/2
36
The MFS Evolution is based on the MX concept = multi-standard -> A

reflexion that points out the common features between different
Alcatel equipments :
Mx is the new Platform for the Alcatel Mobile Equipments,

Based on AdvancedTCA standards (ATCA)
Open to RNC evolution (the UMTS BSC)
Addressing in priority the GSM products (BSC and MFS)
Covering both Control and User (transmission) planes
Supporting Voice and GPRS services.
The Mx platform has been chosen to :
Increase BSC and MFS capacities
Optimize BSC and MFS configuration
Reduce the equipment cost and simplify network maintenance
ATCA = Advanced Telecom Computing Architecture
Page 36
Presentation 2/2
37
MFS or MFS-BSC Evolution rack

TRU
Common dimensions: ATCA

Standard
Universal
Standard 19" rack (0.6 X 0.6 X 2m ) Subrack #2
Shelf
Height: 2m (Useful height 40U)
ATCA
Standard
... Same equipment platform for ... Universal
Suback #1
Shelf
BSC and MFS standard subrack (ATCA)
Termination shelf

Termination
… but independent machines ... Shelf
Termination
Termination
Shelf
Shelf
Stand (100mm)
Stand (100mm)
Standard Unit. 1U = 44.45 mm
Same equipment practice, same technology platform for:

BSC and MFS (PCU)
RNC and TC (planned)
… but independent machines
Reuse of existing software
Independent performance scalability and product flexibility
Clear split in user (transmission) and control plane
… supporting different network architectures
e.g. centralised and distributed location of BSC and MFS
Optimised for new transmission technology (e.g. SDH)
Combination in one rack (e.g. 500TRX BSC-MFS-TC) possible
MX BSC standalone:
possible connection to current MFS and MX MFS
MX MFS standalone:
possible connection to current BSC and MX BSC
Page 37

Page 38
Rack description
39
The A9130 MFS Evolution is housed in a

single 19” standard rack which provides:
Mechanical housing for up to two ATCA shelves

A power distribution shelf called PDU
External connection that can be 2Mb/s E1 or
Giga Ethernet on balanced pairs,
Safety protection to industry standards.
The A9130 MFS is housed in a single 19” standard rack:

A pre-equipped rack, with location to host 2 ATCA chassis,
A terminal server,
A Power Distribution Unit (PDU) named JSXPDUB.
Page 39
Functional Aspect
40
O&M Control stations
Radio Processing
IMT boards
OMCP1
OMCP2
…
SSW1
LSN 0
Mux
Radio
LIU LSN 1
Network LIU
E1 LIU
Links
SSW2 (redundant)
Ater or Gb
External Ethernet Links
Ethernet link Gb Ethernet Links
A platform is composed of applications stations and controls stations interconnected by a secured Local Secured
Network (LSN) network. The control stations run on an active/standby mode. The LSN network is based on
Ethernet technology.
Each station is connected to the two LSN networks.
An internal terminal server located in the backplane of the control stations interconnects all modules and ensures
a RS232 to IP gateway (especially during equipment restart when no IP is available)
All Radio Processing boards are in active mode except one spare board per ATCA subrack that is in standby
mode.
SSW are in active/standby mode
Always 2 MUX boards in a standard configuration. They work in active/standby mode.
Page 40
Board introduction
41
E1 connections
GP
L GP
Abis GP
I
M S GP
U S GP
MU
UX S GP
16 LIU X 16 S GP
E1 X W GP
W GP
L
Ater I MFS
U GP
9 PCU +
1SPARE
OMCP
OMCP
LIU shelf: Multiplexes/de-multiplexes and cross connects all E1 external links to/from NE multiplexed links (n E1 over
Ethernet) on the TP and the GP board. Equipped with two MUX boards and n LIU boards, depending on capacity.
The LIU shelf hosts Two MUX boards which collect the E1 links from the 16 LIU boards on 16 serial links at 36.864
Mbit/s and build packets sent towards up to 32 directions (125ms each) on a Gigabit Ethernet link.
SSW: it’s an Ethernet switch which allows exchanges between all platform elements and external IP/Ethernet
equipment.
OMCP: these control stations are used to process defense functions and platform Operation, Administration and
Maintenance (OAM) generic services..
GP: Manages the user plane packet data flow processing.
Ethernet links on the IP ports of the SSW switch: these links connect the platform to external IP equipment (i.e. OMC-
R, external alarm box).
Page 41

Page 42
ATCA subrack presentation
43
= Advanced Telecom Computing Architecture

The ATCA subrack:
- A standard development fully compliant with the
PICMG 3.0 R1.0 specifications
- Shelf is designed for "five nines" uptime
(99.999%)
- 14 node slots which can be equipped with
Advanced TCA node blades
- Two SHMC shelf manager boards. Each blade
and Field Replaceable Unit (FRU) provides links
to the shelf manager through an Intelligent
Platform Management Bus (IPMB)
Page 43
ATCA subrack internal elements
44
Advanced Telecom Computing Architecture
Blades & RTM

Chassis
This platform is a high availability distributed platform composed of blades compliant with the Advanced Telecom
Computing Architecture (ATCA) open standard
ATCA has been developed by the PCI Industrial Computers Manufacturers Group (PICMG).
ATCA (PICMG 3.x) is the third platform defined by the PICMG group and includes some significant enhancements
over the preceding Compact PCI (PICMG 2.x)
RTM : Rear Transition Module
Chassis designs are shifting from proprietary to standard backplanes. Here is an ATCA chassis made by Centellis.
Other manufacturers exist and can be found on the Web.
Page 44
ATCA subrack front and rear views
45
= Advanced Telecom Computing Architecture
Subrack Front View Subrack Rear View
Page 45
3 Hardware description

Page 46
ATCA subrack close view
47
The ATCA shelf and

boards
The MFS Evolution platform includes two 19”ATCA chassis named A13U. Each chassis provides 14 vertical
physical slots (from 1 to 14).
A chassis is divided in two sides:
slots 1 to 6 are part of the left front side (6 slots),
slots 9 to 14 are part of the right front side (6 slots).
Slots 7 and 8 are dedicated to switch cards (Ethernet switches).
Each slot has:

a front side for inserting cards,
a rear side for inserting Rear Transition Modules (RTMs), or a filler when no RTM is required.
An ATCA chassis includes:
a mechanical chassis with dual star backplane,
a distribution board,
an air filter,
4 Power Entry Modules (PEMs),
4 fan units,
2 Shelf Manager Controllers (ShMCs),
2 COnfiguration & ALarm (COAL) also cards called PC (personality cards),
From the front side of an ATCA chassis, the following types of cards can be inserted:
GP board, SSW board, OMCP board called “control stations”
Page 47
SSW board
48
ATCA : SSW or Ethernet switches
Front Rear
ATCA Ethernet switches are F-300 switch cards. Each Ethernet switch provides:
13 internal (through the backplane) GE interfaces towards other slots,
1 internal (through the backplane) GE interfaces towards one ShMC,
2 unused (through the backplane) GE interface.
The associated ARTM is a standard ARTM-F300.
All stations are connected through the backplane to both Ethernet switches. This connection makes up a Local
Secured Network (LSN).
Off-The-Shelf: Motorola ATCA-F300

GbE Base Interface Switch
16 Base channels
8 GbE uplinks via RTM: ARTM-F300
Layer 2 switching
GbE Fabric Interface Switch (Not used)
15 Fabric channels
1 GbE uplink via RTM
Update Channel
IPMI V1.5
SNMP Agent for switch management
TDM Clock option via CGM (Not used)
Front Ethernet and Serial ports (Debug)
Page 48
OMCP board
49
ATCA : OMCP or Control stations
No RTM
Front Rear
Control stations are used to process defence functions and platform Operation, Administration and Maintenance
(OAM) generic services.
A control station is a standard ATCA-715 card. It has no RTM, that is ATCA rear side module for OMCP.
Each control station includes:

a Pentium M 1.8 GHz processor,
a 4GB memory,
A 60 GB Integrated Device Electronics (IDE) hard disk,
Two 1 Gigabit Ethernet (GE) interfaces.
GE : Gigabit Ethernet
Page 49
GP board
50
ATCA : the GP board
Front
GP boards are used for radio processing

NE1oE Method consisting to transport n x E1 frames in an Ethernet payload, assigned to a dedicated MAC
address
Page 50
SMM and PC board
51
SMM and PC boards
ATCA ShMC is an M100 card. Each chassis embeds 2 ShMCs.

An M100 ShMC has a GE uplink interface for Hardware Platform Interface (HPI) access to the platform (console redirection,
remote upgrade of firmware, etc.).
The ShMC is the main component of the shelf management system:
There are 5 communication channels between the GPU board and the control station:
It monitors, controls and ensures proper operation of the shelf and other components (fan units, PEMs, RTMs, etc.),
it reports anomalies and errors and takes corrective actions if required (for example, increase the speed of the fan units,
etc.),
it has access to the detailed inventory information as well as sensor status information of the shelf and its components.
ATCA COAL card is an A100 card. Each chassis embeds 2 ATCA A100 COAL cards.
An ATCA A100 COAL card has a DB15 connector that provides access to dry contact for alarm inputs and outputs.
The ATCA A100 COAL card:
contains the chassis FRU information store,
contains rotary switches to set Shelf Geographical Address (SGAs),
provides High Availability (HA), SGA and configuration bit inputs,
provides interfaces for up to 2 filter switches and 4 temperature sensors, for example, air inlet,
provides Telco alarming, that is, relay outputs for major, minor, and critical errors and up to 4 opto-isolated inputs,
displays the states and alarms via LEDs on the front panel,
provides interface to Intelligent Platform Management Bus (IPMBs) A and B.
Two or four field maintainable intelligent Power Entry Modules (PEM) are installed beneath the rear slots of the backplane
Page 51
LIU shelf description
52
LIU SHELF
front view
(No connector
on rear view)
The LIU shelf ensures the concentration of 256 E1 (or T1 in a future step) on a 1 Gigabit Ethernet link.
oIt is not necessary to have all the 16 LIU boards inserted. If the MFS rack contains only one ATCA shelf, 8 LIU
boards are.
oAll the boards are used only when an MX MFS is configured with two shelves.
The LIU shelf hosts:

Two PEM boards supporting the connection from - 40 up to 72VDC secondary voltage, the EMI filtering, the down
conversion in a 12V voltage, and collects the alarms through a I2C link
Two MUX boards which collect the E1 links from the 16 LIU boards on 16 serial links at 36.864 Mbit/s and build
packets sent towards up to 32 directions (125ms each) on a Gigabit Ethernet link
16 LIU boards converting 16 plesiochronous E1 links into a synchronous link at 36.864 Mbits (4B/5B coded).
Page 52
The 3 LIU shelf boards
53
Boards of the LIU SHELF
JBMUX
JBXLIU JBXPEM
To recognize the different boards, 3 possibilities :

-the name on the front aluminium plate
-the connector type on the front plate
-the insertion position, see bottom diagram here above.
Page 53
PDU
54
PDU : Power Distribution Unit
The PDU can be seen as 2 independent sides, each shelf of the rack being powered by both sides for redundancy
purpose.
From left to right, we have switch A1 to A5 and then B1 to B5
A1 and B1 power the optional upper ATCA shelf

A3 and B3 power the lower ATCA shelf
A4 and B4 power the LIU shelf
Page 54
3.5 Configurations and performances

Page 55
MFS in stand alone mode (1/3)
56
MX-MFS B9
MFS Standalone
configurations
MFS stand alone

Equipment
9GP 21 GP
Upper SSW 2
ATCA
shelf GP 1 to 12
LIU Mux 2
shelf LIU board 8 16
SSW 2
Lower
OMCP 2
ATCA
shelf GP 1 to 9 9
Spare GP 1
Every configuration includes:

2 OMCP (still called “servers” or “control stations”) per MFS rack, either with Standard or Large configuration,
2 Ethernet switches per ATCA shelf,
In the 9 GP configuration, please note the 2 equal possibilities : MFS extension to 21 GP or rack sharing with BSC.
Shelf numbering is as follows:

-----------------
| ATCA Shelf 4 |
| |
| ATCA Shelf 3 |
| |
| LIU Shelf 2 |
| |
| LIU Shelf 1 |
-----------------
Page 56
57
MFS ATCA Shelf layout
sion
subrack exten
P in
N o OMC
MFS LIU Shelf layout

2 Ethernet switches per ATCA rack,
In the 9 GP configuration, please note the 2 equal possibilities : MFS extension to 21 GP or rack sharing with BSC.
LIU shelf 2 is used only in case of rack shared configuration: MFS – BSC Mx.
Page 57
58
2 possible configurations for an MFS in stand-alone mode:

Standard or Large
Standard Large
TRU TRU In details :
Standard: MFS Evolution with 1 ATCA

: maximum 9 GP*+ 1
1 ATCA, 1 LIU shelf, 8 LIU boards, 2 SSW and
MFS
MFS 2 OMCP boards.
10+1 to 21+1 Max number of BSS: 9
1+1 to 9+1 GP boards
Large: MFS Evolution with 2 ATCA :
GP boards maximum 21 GP*+ 1 for both subracks
Max number of BSS: 21
Termination Termination * GP = GPU evolution

Shelf Shelf capacity 1GP = 1GPU (inside MFS A9130) in B9
Stand Stand
2 GPU (inside MFS A9130) in the future
E1 Connexions - Standard configuration: 1 to 8 LIU x 16 E1 = 128 E1
Large configuration : 128 E1 up to 256 E1 in the unique LIU shelf

2 Ethernet switches per ATCA rack,
Large Configuration: upper and lower subrack must be seen as a unique configuration needing 2 OMCP only.
Therefore, the second telecom subrack supports up to 12 GP boards as maximum capacity due to the fact that no
extra OMCP boards are necessary in the upper subrack.
Main dimensioning rules:

- MFS Evolution is made of 1 to 21 GP.
- GP handles the packet traffic of one BSS and offers up to 12 interfaces (Ater-interface or Gb Interface) for MFS
configuration
- MFS Evolution can handle the packet traffic of 21 BSCs.
- One BSS can be connected to one or several GP boards (6 max) in relation with the GPRS traffic.
- All BSSs connected to a given MFS Evolution are managed by the OMC-R managing this
MFS.
- BSSs connected to a same MFS Evolution can be linked to one or several co-located MSCs;
- MFS Evolution can be connected to one or several SGSN, but a GP board can be connected
to only one SGSN.
- Each GP board supports a different number of Packet Data Channels (PDCHs) according to
the highest GPRS and EDGE coding schemes used by the operator.
Page 58
59
How many E1s (therefore LIU) can I handle with 1, 4, 9 and 21 GPs
Main figures: GP2

Ater Allocation on LIU boards for stand alone MFS
GP1
Standard case:
12 LIU ports per GP
to get maximum number of
21 GP in a MFS
(12 or 16 LIU ports per GP
According to MFS
SA or RS configuration)
1 LIU board for 16 E1 (Tx / Rx)

( => 1 E1 cable )
1 LIU Shelf manages
16 LIU boards GP9
=>1LIU shelf = 16 x 16 E1
= 256 E1 Table for 12 x E1 per GP
links max
SA: stand alone

RS: rack sharing
A GP board can be assigned 12 or 16 E1, value chosen during the

installation
For example, in the 21 GP configuration, we have just 16 LIU boards,

that means 256 E1.
In such case, we can have only 12 E1 per GP board.
A GP board can have its 12 E1 shared between 2 consecutive LIU
boards.
In the 8 GP configuration, we have 8 LIU boards, so we can configure

the GP with either 12 E1 or with 16 E1.
Page 59
MFS in rack sharing mode
60
MFS/BSC Evolution shared configurations

2 possibilities in case of BSC/MFS rack sharing
TRU TRU
BSC MFS
BSC Evolution configuration
BSC up to 400 TRX : 126 E1
BSC 600 TRX up to 1000 TRX : 256 E1
MFS BSC
MFS Evolution configuration :
9 GP*+ 1 maximum
Termination Termination
Shelf Shelf
Shelf Shelf
Stand Stand
This configuration is fully described in the “Alcatel 9130 BSC Evolution Description”
As far as the MFS is concerned, only an MFS in standard configuration is possible. It includes:
2 control stations,
2 Ethernet switches,
1 (lower) LIU shelf equipped with 7 LIU boards and 2 MUX boards
Page 60
Exercises 1/2
61
5 minutes Please fill-in the white rectangles

O&M Control stations
Radio Processing
boards
OMCP1
OMCP2
IMT
…
SSW1
LSN 0
Mux
Radio
LIU LSN 1
Network LIU
Links LIU
SSW2 (duplicated)
Ater or Gb
Page 61
Exercises 2/2
62
3 minutes
TRU TRU
For each configuration:

MFS
MFS MFS Evolution with 1 ATCA
MFS Evolution with 2 ATCA
How many GP boards, LIU shelf, LIU boards,
SSW boards, OMCP boards and possible
connected E1 ????
Shelf Shelf
Stand Stand
Page 62
Evaluation
63

hardware organization of the MFS
Evolution equipment

the objective sheet
Page 63
4 Software description

Page 64
4 Software Organization
Objectives
65
Objective : to be able to describe the software

organization of the MFS Evolution equipment
Program :
4.1 General organization
4.2 The Tomix Middleware
4.3 The MFS Evolution application software
Page 65
4.1 Software architecture

Page 66
4.1 General Organization
Vertical organization
67
MFS
MFSEvolution
Evolution The MFS Evolution application runs
Software Application
Application
Software over TOMIX middleware and is used
Software
Software for supervision and maintenance.
Telecom
Telecom TOMIX
TOMIXMiddleware
Middleware It provides a comprehensive set of
Middleware
Middleware platform services
Initialization
Operating HW Management
Operating Linux
LinuxMantavista
Mantavista
System SW Management
System
Availability Management
O&M Agents
Hardware
Hardware ATCA Protocol Stacks (e.g. SS7)
Platform ATCA
Platform
Linux CG Ed: Linux Carrier Grade Edition described herafter.
Page 67
4.1 General Organization
Not any Linux distribution …
68
Linux Mantavista Carrier Grade Edition

High availability (service continuity, defense,…)
Real-time performance,
Resource monitoring and event logging
Management framework,
Standards based open systems,
Diagnostics (online and offline),
Performance and scalability.
Tomix runs on Linux Carrier Grade (CG) OS. Linux CG is an advanced Linux-based development platform
designed specifically for the robustness and high availability requirements of carrier grade class applications.
Linux CG serves in telecom and datacom applications used in packet based and wireless infrastructure solutions.
Linux CG is specified by the ODSL forum, which includes major players from IT, Telecom and Linux distribution.
Page 68
4.2 The Tomix middleware

Page 69
4.2 The TOMIX middleware
A modular cooperation
70
MFS Evolution application software runs under the supervision of the platform middleware
The Tomix middleware is a software layer between the telecom applications and the Linux Operating System (OS).
The platform middleware provides a robust, generic Alcatel system, which forms the basis of current and planned
telecommunications developments.
The software components include options or plug-ins such as :

Generic management services
Web based GUIs, which provide the operators with full access to the system
Common Object Request Broker Architecture (CORBA) is a software interface for communicating between
distributed, self-contained software modules
ATCA-based platform offers secured Signaling System Nº 7 (SS7) service management as an option (not used
here for the MFS)
Page 70
4.2 The TOMIX middleware
Detailed description
71
A generic platform with services described and

presented in chapter 6 (Man Machine Interface )
Access Control
Log Management
Alarm Management
Observation Service
Hardware Management
Software Management
ATCA-based platform provides the following generic management services:
Access Control
The Access Control service manages and supervises access to the platform and NEs.
Log Management
The Log Management service enables the operator to display and extract log information.
Alarm Management
The platform includes Global Alarm Management (GAM).
Alcatel GAM provides a Web-based GUI for a local or remote operator to manage alarms originating in the
platform and the MFS system.
Observation Service
The Observation service enables performance management and handles the observation jobs submitted by
management systems or automatically started at system initialization.
Hardware Management
The Hardware Management service monitors platform hardware components.
If a hardware fault occurs the Hardware Management service sends an alarm, which indicates the faulty
component to be replaced.
Software Management
Software Management enables management of secure Installation, Maintenance and Update functions for MFS
application and platform software.
Page 71

Page 72
OMCP and GP software cooperation
73
OMC-R IMT
MFS - GPU sessions
Server
(real-time
agents) Q3 CMPS
interface
CFG
Admin MIB Admin Admin Admin
Real-time Real-time Real-time Real-time
GOM RSC GEM GAM GPM
MIB
Sessions 1 2 3 4 5
GPU
(PSOS
Telecom tasks) Session Board &
Performance
Resource Configuration Alarm
Manager
Manager Agent Manager
There are 5 communication channels between the GPU board and the control station:
Telecom channel (1): used for the requests, answers and state change notifications
• for Network Services configuration (Gb interface).
• for Bearer Channels configuration (AterMux interface).
• for BSS and cell configuration (Cell Management).
GPU Network channel (2): used for network configuration requests and answers as well as network
notifications.
GPU Physical channel (3): used for GPU hardware component configuration requests and answers as well
as hardware notifications.
Alarm channel (4): used for collecting all hardware, network and GPRS alarms.
Performance Manager channel (5): used for PM configuration requests and all reports from the GPU
board.
Each channel is a Communication Service session established between a Provable Secure Operating System
(PSOS) task on a GP board and a Real-Time MFS Agent on the control station.
Each process can be divided into 3 main parts:
Administrative layer: to manage configuration data given through CMPS request from a Q3 agent or the
IMT terminal.
Real time layer: to manage object states updated upon notifications received from the GPU.
Agents to support the process.
RMA agents support all data persistency:

The configuration data are stored in a specific table with a backup on disk.
Resource data are stored in another table with no backup on disk.
MIB – 2 Management Information Bases – CFG: Configuration and RSC: Resources
Page 73
OMCP real time agent description
74
O&M Functional Description

MFS Real-time Agents
• GAM - Global Alarm Manager
• GEM - GPRS Equipment Manager
• GOM - GPRS Operations and Maintenance
• GPM - GPRS Performance Manager
• Q3
The GAM is in charge of:

Collecting all the faults occurring in the MFS (XPU, O&M board, E1 MUX boards, ATCA shelves and
telecom alarms). .
recording alarm objects in a secured table.
allowing the IMT and the Q3 agent to access these alarm objects.
generating the end of alarms on pending ones, for instance in case of a board failure.
managing a communication session with the IMT terminal.
The GEM responsible for the GP hardware and low layer software management is in charge of:
GPU initialization, supervision and defence (switchover).
NE1oE configuration on GPU and E1 MUX board
handling requests received through CMPS concerning GPU, cross-connections and PCM-TP.
Time management for XPU boards.
The GOM is independent from physical equipments, which are managed by the GEM. It is in charge of:
telecom resource configuration and supervision, including the bearer channels, Gb interface.
AterMux interface and cell management domains.
synchronization of the logical GPU resource states after a server switchover.
The GPM or GPRS Performance Manager on the OMCP board is in charge of:
collecting counters from GPUs.
generating a file containing the counters and their values.
Q3 manages the Q3 interface to the Alcatel1353 RA OMCR. It has the following characteristics :
the information managed by the OMC and the internal information managed by the agents.
The MFS real-time agents are not seen from the OMC.
It is initialised only in “site mode”.
Page 74
GP PSOS tasks description
75
The GPU PSOS tasks are :

BAM - Board and Alarm Manager
TRM - Telecom Resource Manager
PM - Performance Manager
SCA - Session Configuration Agent
The BAM agent manages the GPU hardware. It is in charge of:

supervising physical resources, e.g., the PCM-TP, synchronization.
starting the telecom application tasks
reporting hardware and telecom alarms to the GAM.
The TRM agent manages the telecom functions. It is in charge of:

BSS logical configuration, activation and supervision for the Bearer, AterMux interface and
Cell management domains.
Network Service logical configuration and supervision for the Gb Interface domain.
The PM agent manages the scanner configuration and the collection of PM counters values.
The SCA manages the network configuration and supervision.
Page 75
O&M Functional Description
76
Backup / Restore
Each control station possesses a local disk (system configuration files)
Both control stations share a common partition as well
TOMIX offers a backup possibility :

to back up data from the shared disk exclusively (no data can be backed up
from the local disks)
to store the data on a particular partition of the shared disk
System configuration files

They contain for example the Ethernet addresses of the stations. System configuration files are configured during
the first installation of the MFS SW and are never changed.
Since these data are stored on the local disks, there is no possibility to back up these data using the TOMAS
backup facility.
Data Set Instances (DSIs)

They contain the TOMAS database managed by the Data Manager (DM) and called Management Information
Base (MIB). They are used by TOMAS and the MFS applications. DSIs are updated very often, upon interactions
with the GPU, the IMT and the OMC.
In order to have a consistent backup, all DSIs need to be backed up at the same time (Ater, Gb and radio
configuration).
Backup general processing (backup of DSIs)

Backup operations can be triggered quite often because they do not interfere with the MFS system and because
they are transparent (neither O&M nor telecom outage).
The MFS allows to store up to 5 backup files created on operator’s request (manual backup files) and up to 12
backup files created automatically by the MFS (automatic backup files). This allows to restore them quickly, without
having to download them from the OMC. The backup files are automatically compressed by the MFS.
Page 76
Evaluation
77

software organization of the MFS
Evolution

the objective sheet
Page 77
5 Defense Mechanisms

Page 78
79
Objective : to be able to understand the SW and HW

cooperation in case of hardware or software failure
Program :
5.1 SW supervision
5.2 HW redundancy
Page 79
5.1 SW supervision

Page 80
5.1 Software Supervision
General principle
81
General principle for board redundancy : the OMCP scheme

Switchover
Standby
Active Active
Standby
1 3
If one MFS Activation
Gxx Gxx
Real-time Gxx of all MFS
agent fails Real-time
Watchdog agents
CMA CMA
2
Detection by
the Configuration
Management Agent
Gxx Any active MFS Real-time agent

Shared Partition
Gxx Any standby MFS Real-time agent
Switchover
If any MFS Real-time agent crashes on the active control station, the Configuration Management Agent(CMA),
active on both sides, activates all standby MFS Real-time agents on the standby control station.
As a consequence, the standby control station becomes active.
The former active control station (with failed MFS Real-time agent) is re-started.
Redundant boards are aware of the crash of the active control station by receiving an indication of session abort.
Each agent will establish a new session with the new active control station.
Page 81
5.2 HW redundancy

Page 82
5.2 Hardware redundancy
Which defense for which type of board ?
83
MFS Evolution hardware redundancy depends on the shelf

type and on the type of board
Shelf Board (Mnemo) Redundancy

2 types of
ATCA (JBX) GPU N+1
(JBX) OMCP 1+1
redundancies:
(JBX) SSW 1+1
(1) (JAX) SSW or SSW-RTM 1+1 N+1 and 1+1
(1) (JBX) PS 1+1
(1) (JAX) SMM 1+1 N active / 1 standby
(1) (JAX)PC 1+1 and
1 active / 1 standby
LIU (JBX) PEM 1+1
(JBX) LIU termination None
(JBX) MUX 1+1
(1): rear subrack elements – LIU has only front elements
Above table from top to bottom, left to right and front to rear of each subrack of the equipment
Mnemo stands for “Mnemonic”, the full name to distinguish between JB elements with “B” standing for boards,
from JA elements with “A” standing for Applique=remote connector for boards here also named RTM.
We can have a board on the rear side of a shelf (ex JBXPEM on rear side of the ATCA shelf), however no “JA” or
Applique element can be found on a front shelf in this version of MFS.
Hardware monitoring
The hardware components of the MFS Evolution are permanently monitored by cyclic polling of the board status
registers.
When the system detects a defective board:

LEDs on the board signal the fault,
The active subsystem switches over to the standby subsystem according to the type of board.
Provided mechanisms:
duplication of hardware,
duplex configuration,
link protection switching,
hardware monitoring.
Page 83
1+1 redundancy
84
Switchover scenario for 1+1 (duplication) redundancy scheme:

OMCP or SSW
Page 84
N+1 redundancy
85
Switchover scenario for N+1 redundancy scheme
In the N+1 scheme, the redundant GP boards takes over the processing and capacity of the failed GP with a
minimum service interruption
Page 85
Evaluation
86
Objective : to be able to understand the

SW and HW cooperation in case of
hardware or software failure

the objective sheet
Page 86
6 Man/Machine interface

Page 87
88
Objective : discover the most important Man to Machine

Interface screens useful for equipment maintenance
and supervision
Program :
6.1 Equipment access possibilities
6.2 Common view from Maintenance Terminal or OMC
Page 88

Page 89
How can we dialog with the MFS ?
90
Access to the
MFS Evolution
TCP/IP
The Alcatel 9130 MFS Evolution can be managed via

2 distincts Ethernet connections:
OMC-R
In local using a standard PC with a Netscape Web

browser v4.7 minimum
In remote via the OMC-R
Installation and
A web-based interface displays Maintenance
the same supervision information Terminal A9130 MFS
locally at the IMT or remotely (IMT) Evolution
at the OMC-R
Web based interfaces possibilities:

Locally: the user at the IMT via a Web browser (Internet Explorer or Netscape) is able to manage the
Network Element.
Remotely: the user at the OMC-R can manage the same Network Element.
Machine to machine interfaces are based on:

FTP: Software upgrade and backup /restore.
Telnet: Ping, etc/host file, Unix Administration.
Page 90

Page 91
Main menu + Physical view
92
Maintenance application
screen shots 1/2
Physical view = ATCA shelf view
Alarm summary + Main Menu
The left screen shows the main screen offering an alarm summary (alarms are synthesized by severity) and the
main menu including the very useful “View” Menu (site View, Physical View, …) .
On the right we have the representation of the front view of the Physical view – a representation of the front view
of the ATCA rack with its 14 slots and the inserted board
We can see the inserted GP boards (slot 1, 2 and 5), A = OMCP server A , B = OMCP server B, LSN = SSW
board
The OMC offers extra possibilities such as Ater and Gb interfaces configurations menus
Page 92
Site view = MFS view
93
Maintenance
application screen
shots 2/2
Site view = MFS rack view
Site View: TOMAS submenu supervises:

The Local Secured Networks 0 and 1
The Shelf Managers of ATCA shelves 1 and 2
The A and B Control Stations of the MFS Rack
A router
Site View: Rack_0 supervises the whole ATCA shelf

SHELF_3 = bottom ATCA shelf
SR_0 = unique LIU shelf with its 2 MUX boards
OTHER BOARDS : PEM power Modules and PC cards (COAL or Personality cards for external alarms)
BOARDS = the different GP boards in their slot
Page 93
Evaluation
94
Objective : discover the most important

Man to Machine Interface screens
useful for equipment maintenance and
supervision

the objective sheet
Page 94
7 ANNEX

Page 95
7 ANNEX
7.1 The PCU function

Page 96
UL TBF establishment sequence diagram
97
One phase access UL TBF establishment initiated by the MS in packet

idle mode on a PCCCH
MS MFS (PCU)
(EGPRS) Packet Channel Request 1
Scenario 1: request is rejected 2
Access request Packet Access Reject

and access grants
Scenario 2: request is accepted 3
Packet Uplink Assignment 3a
USF scheduling 3b
PDCH RLC data block 3c

scheduling
Packet UL ack/nack 3d
(1a) Packet access procedure for GPRS

The Packet Channel Request message is received on a PRACH and indicates one of the following access types:
One phase access (in this case, the MS also provides the network with its multi-slot class) / Short access / Page Response / Cell
Update / Mobility Management procedure / Single Block Without TBF Establishment.
(1b) Packet access procedure for EGPRS
The 11-bit EGPRS Packet Channel Request message is received on a PRACH and indicates one of the following access
types:
One phase access / Short access / Signalling.
(2) Packet access reject procedure for (E)GPRS
The Packet Access Reject message is sent on the same PCCCH than the one on which the (EGPRS) Packet Channel Request
message was received in case the access request cannot be satisfied.
(3) Packet channel assignment procedure for (E)GPRS
(3a) In case a Packet Channel Request message is received from the mobile station, if the packet access request can be
satisfied immediately, a Packet Uplink Assignment message is sent to the MS assigning a TFI, the PDCH(s) carrying the TBF with its respective
USF(s), the TA channel, the channel coding scheme, the TAI and the initial TA value.
If the EGPRS is activated in the cell, upon receipt of an EGPRS Packet Channel Request message from the mobile station, if
it is NOT possible to allocate the TBF in EGPRS mode, a Packet Uplink Assignment message in GPRS mode is sent to the MS. Otherwise a
Packet Uplink Assignment message in EGPRS mode is sent to the MS assigning a TFI, the PDCH(s) carrying the TBF with their respective USF(s),
EGPRS window size, etc.
On receipt of the assignment message, the MS switches to assigned PDCHs.
(3b) USF(s) are scheduled
A USF is sent to the MS to start the Uplink transfer.
One phase access Contention resolution for (E)GPRS
(3c) The MS transmits uplink blocks when allowed by the scheduled USF. The MS provides its TLLI (and TFI) in the first RLC data blocks
sent to the BSS on the assigned PDCH(s) until the contention resolution is completed at the MS side. The contention resolution is done
at the BSS side as soon as one of these first blocks is received correctly. The MS using the assigned TBF is identified non-ambiguously.
(3d) The contention resolution is done at the MS side when the BSS sends on the PACCH a Packet UL Ack/Nack message with the TLLI
(and TFI) field after having received correctly the first RLC data block comprising the TLLI.
Page 97
DL TBF establishment sequence diagram
98
DL TBF establishment initiated by the BSS for an MS in packet idle mode

on a PCCCH
MS BSS
Packet DL Assignment, polling 1
Packet Control Acknowledgment 2
Packet power ctrl / Timing advance 3
Packet power ctrl / Timing advance
RLC/MAC block 4
Packet Downlink Assignment

A Packet Downlink Assignment message is sent on a PCCCH (on the first available PPCH occurrence or on the PPCH block of the MS paging
group(s), depending whether the MS is in non-DRX mode or not) assigning a TFI, EGPRS window size (for EGPRS TBF only), the PDCH(s)
carrying the TBF, the TA channel and the TAI. No initial timing advance is provided.
The Packet Downlink Assignment message is sent in EGPRS mode if:
the PDCH(s) allocated are on an EGPRS-capable TRX.
the MS is EGPRS-capable.
the EGPRS is activated in the cell.
Otherwise the Packet Downlink Assignment message is sent in GPRS mode.
(2) Packet Downlink Acknowledgement

The MS acknowledges the receipt of the Packet DL Assignment message on the same PCCCH slot. During each DL TBF establishment attempt,
the Alcatel BSS re-evaluates the MS radio state as well as the MS DRX mode and sends the Packet DL Assignment message:
on the PACCH if a UL TBF has been created in parallel to the previous DL TBF establishment attempt,
either or on the first available PPCH occurrence or the PPCH block of the MS paging group(s), depending whether the MS is in non-
DRX mode or not (See § and §).
(3) Packet Power Ctrl/Timing Advance

The BSS sends to the MS on a PACCH the initial timing advance (to be used by the MS when sending a Packet DL Ack/nack message). Indeed,
if the Packet Power Ctrl/Timing Advance message is lost, the MS cannot send an UL message (Packet DL Ack/Nack) until it receives a valid
timing advance through the continuous timing advance procedure.
(4) RLC MAC block

The MS stops the timer T3190 on receipt of the first valid RLC/MAC block. If T3190 expires, the MS aborts the procedure and returns to packet
idle mode.
Page 98
ARQ and UL Data transfer
99
ARQ function / Example of UL Data Transfer
Radio blocks are assigned on a PDCH

MS by USF scheduling MFS (PCU)
USF scheduling
Radio block n
PDTCH
USF scheduling
Radio block n+1

PDTCH
Packet downlink ack/nack (ack radio block n/nack radio block n+1)
PACCH
USF scheduling
Radio block n+1

PDTCH
USF scheduling
Page 99
BSC and MFS cooperation for PDCH allocation
100

4 5
3
Allocated 2
SPDCH
Max_PDCH - Nb_TS_MPDCH
Max_PDCH_High_Load - Nb_TS_MPDCH
Min_PDCH - Nb_TS_MPDCH
(1) The cell is activated for PS traffic and MAX_SPDCH_DYN is equal to (MAX_PDCH - Nb_TS_MPDCH).
Resources (Min_PDCH - Nb_TS_MPDCH) are requested to the BSC (pre-allocation phase).
(2) Additional PDCHs are requested to the BSC until the maximum number of SPDCHs is allocated.
(3) The BSC sends a Load Indication with a decreased MAX_SPDCH_DYN. A soft preemption is activated on the exceeding
PDCHs. T_PDCH_Preemption is activated.
(4) During the soft preemption process, T_PDCH_Preemption expires>. A fast preemption process is activated on the PDCHs
that are still marked as soft preempted.
(5) The BSC sends a load indication with an increased MAX_SPDCH_DYN.
The PS traffic increases until MAX_SPDCH_DYN is reached.
Max_PDCH_High_Load
Defines the lower value of the maximum number of PDCHs (SPDCHs + MPDCHs) per cell when the cell is in high load situation.
This parameter indicates the lower limit of the load adaptation mechanism.
Max_PDCH
Defines the maximum number of PDCHs (SPDCHs + MPDCHs) that can be allocated in a cell. Whatever the PS traffic is, there
will never be more than Max_PDCH PDCHs in a cell.
Min_PDCH
Defines the minimum number of radio time slots which are allocated for the PS traffic (i.e., no corresponding Ater transmission
resources are allocated) and for MPDCHs.
The aim of this parameter is to guarantee a minimum number of radio time slots for the PS traffic in one cell.
Nb_TS_MPDCH
Defines the number of MPDCHs in the cell (one primary MPDCH and (Nb_TS_MPDCH - 1) secondary MPDCHs).
Page 100
7 ANNEX
7.2 MFS Evolution connection modes

Page 101
Summary
102
Reminder: all MFS connection possibilities
Page 102
Standard connection with dedicated or mixed Ater link
103
Direct connection for Gb
Dedicated or mixed Ater link
Page 103
TC transparency (Gb interface through A interface)
104
Gb interface connection through the transcoder and MSC (TC

transparency)
Page 104
7 ANNEX
7.3 Exercise solutions

Page 105
7.3 Exercise solutions
MFS Configuration exercise
106
TRU TRU For each configuration:

MFS
How many GP boards, LIU shelf, LIU boards,
SSW boards, OMCP boards and possible
connected E1 ????
MFS
Shelf Shelf
Stand Stand
Solution of the exercise:
MFS Evolution with 1 ATCA :

9 GP+ 1 maximum, 1 LIU shelf, 8 LIU boards, 2 SSW and 2 OMCP boards
8 x 16 E1 = 128 E1
MFS Evolution with 2 ATCA :

21 GP+ 1 maximum, 2+2 SSW and 2 OMCP boards only (no OMCP board in the upper ATCA)
1 LIU shelf only for stand-alone MFS evolution : from 8 LIU boards (128 E1) to 16 LIU boards (256 E1)
Page 106
Glossary
107
A Switch to notes view! M

Abis Telecommunication Interface MAC Media Access Control
between BSC and BTS MFS Multi-BSS Fast packet Server
APS Automatic Protection Switching MRD Mobile Radio Division
ATCA Advanced Telecom Computing MSC Mobile services Switching Center
Architecture MX Multistandard
Ater Telecommunication Interface
between MSC and BSS N
NE1oE Method consisting to transport n x
B E1 frames in an Ethernet payload,
Blade General naming for an 8U ATCA assigned to a dedicated MAC
Front board address
BSC Base Station Controller
BSS Base Station Subsystem O
BTS Base Transceiver Station OMCP O&M Control Processing (board)
OMC-R Operation and Maintenance Center
C – Radio
CBC Cell Broadcast Center O&M Operation & Maintenance
CCP Call Control Processing
COAL Configuration and Alarm board P
CPR Common Processor PCI Peripheral Component Interconnect
CS Circuit Switched PDU Power Distribution Unit
PEM Power Entry Module
E PICMG PCI Industrial Computer
E1 Alcatel 9130 MFS Evolution
E1 refersDescription / B9
to primary rate or ManufacturerAll rights reserved © 2006, Alcatel
Group
aggregate bandwidth transmissions PMC PCI Mezzanine Card
conforming to ITU-T G.703 and PS Packet Switched
G.732 at 2.048 Mb/s. PSOS Provable Secure Operating System
EDGE Enhanced Data rate for GSM
Evolution R
EGPRS Enhanced General Packet Radio RLC Radio Link Control layer
Service RNC Radio Network Controller
EMI Electro Magnetic Interference RP Radio Processing
EPS Equipment Protection Switching RTM Rear Transition Module
R&D Research & Development
F
FR Full Rate S
FRU Field Replaceable Unit SM System Manager
SMM Shelf Management Module
G SSW Subrack SWitch
Gater Telecommunication Interface STM-1 Synchronous Transport Module -
between BSS and SGSN over Ater level 1 (Data Rate: 155.52 Mb/s)
Gb Telecommunication Interface
between BSS and SGSN T
GCH GPRS Channel T1 Transmission signal level 1
GEth Gigabit Ethernet conforming to AT&T Public 62411 at
GP General Processor – the 9130 MFS 1.544 Mb/s.
radio processing board TCH/RM Traffic Channel/Resource
GPRS General Packet Radio Service Management
GPS Global Positioning System
GPU GPRS Processing Unit U
GSL GPRS Signaling Link U Standard Unit. 1U = 44.45 mm
GSM Global System for Mobile UMTS Universal Mobile
communications Telecommunications System
UTRAN UMTS Terrestrial Radio Access
L Network
LIU Line Interface Unit
Page 107
108

This page is left blank intentionally All rights reserved © 2006, Alcatel
Page 108
109
Page 109

MFS Alcatel PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MFS Alcatel PDF

Uploaded by

Copyright:

Available Formats

Alcatel 9130 MFS/BSC

Alcatel 9130 MFS Evolution

Alcatel 9130 MFS Evolution Description / B9

Copyright © 2006 by Alcatel - All rights reserved

Reference : 3FL12335ABAAZZZZA Teaching languages :

Standard duration Training methods

Total duration (hrs) 6 Sequence :

Maximum number of participants : 12 (Only applicable to c-learning and v-learning)

Course contents: 5 Defense Mechanisms

Did you meet the following objectives ?

2 - To be able to describe the telecom functions of

3 - To be able to describe the hardware

4 - To be able to describe the software organization

5 - To be able to describe the SW and HW

Thank you for your answers to this questionnaire

Alcatel 9130 MFS Evolution Description / B9

Objective : to be able to locate the MFS Evolution

1.1 The MFS Evolution environment

Alcatel 9130 MFS Evolution Description / B9

Radio Access Network

GPRS & EGPRS Core Network

The Multi BSS Fast packet Server (MFS) :

GPRS & EGPRS

The SGSN stores subscriber data : SGSN

• one or more temporary identities (P-TMSI)

• zero or more PDP addresses

• zero or more PDP addresses

1.2 Possible interconnections of the equipment

Alcatel 9130 MFS Evolution Description / B9

See Annex 7.2 for other connecting possibilities

Objective : to be able to locate the Alcatel 9130

- Is the MFS part of the BSS?

- What are the functions managed by the MFS ?

- What types of traffic are managed by the MFS ?

- Does the MFS keep track of the individual MS location ?

Objective : to be able to locate the MFS

Thank you for answering

Alcatel 9130 MFS Evolution Description / B9

Objective : to be able to describe the telecom functions

Alcatel 9130 MFS Evolution Description / B9

The MFS Evolution includes

PCU functions are defined in 3GPP 03.64.

2.2 The PCU functions

Alcatel 9130 MFS Evolution Description / B9

The main PCU functions implement :

PCU functions are defined in 3GPP 03.64.

ARQ = Automatic Repeat Request

LLC PDU segmentation / re-assembly into RLC/MAC PDU

PDCH scheduling (example)

PDCH allocation in a cell (1/2)

Periodically, based on the CS and PS load of the cell, the BSC

Periodically, MFS sends to the BSC a RR Usage Indication

PDCH allocation in a cell (2/2)

PRIORITY FOR CS MAX_SPDCH_LIMIT

Describe 3 of the PCU functions (2 minutes)

Objective : to be able to describe the

Thank you for answering

Alcatel 9130 MFS Evolution Description / B9

Objective : to be able to describe the hardware

3.1 What is the MX concept ?

Alcatel 9130 MFS Evolution Description / B9

The MFS Evolution is based on the MX concept = multi-standard -> A

Mx is the new Platform for the Alcatel Mobile Equipments,