9135

Alcatel-Lucent GSM

9135 MFS Description

MFS Document

Sub-System Description

Release B10

3BK 21232 AAAA TQZZA Ed.05

Status RELEASED

Short title 9135 MFS

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

BLANK PAGE BREAK

2 / 84 3BK 21232 AAAA TQZZA Ed.05

Contents

Contents

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

1 MFS Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1 Introduction to MFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.1.1 MFS Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.1.2 (E)GPRS Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.2 MFS Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.2.1 Telecommunications Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.2.2 Server Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.2.3 Hub/Switch Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.2.4 OMC-R Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

1.3 External Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.4 Traffic and Signaling Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

1.4.1 Physical Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171.4.2 Packet Data Logical Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.4.3 Temporary Block Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191.4.4 NC2 in Packet Transfer Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191.4.5 Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

1.5 GPRS Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201.5.1 GPU Telecommunications Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201.5.2 Abis Resource Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261.5.3 MFS O&M Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271.5.4 SMLC Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

2 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292.1 Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

2.1.1 Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302.1.2 Dimensions and Weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322.1.3 Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332.1.4 Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

2.2 Power System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362.2.1 MFS Rack Power Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362.2.2 MFSDS10 Power Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372.2.3 Top Rack Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382.2.4 Bus Bars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382.2.5 Telecommunications Subracks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382.2.6 Server Subrack in MFSRACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382.2.7 Server Subrack in MFSDS10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392.2.8 Hub/Switch Subrack in MFSRACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392.2.9 O&M System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

2.3 Subracks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392.3.1 Telecommunications Subrack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392.3.2 Server Subrack for MFSRACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492.3.3 Server Subrack for MFSDS10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532.3.4 Hub/Switch Subrack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

2.4 Rack Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632.4.1 Rack Configurations with AS800 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642.4.2 Rack Configurations with DS10 Server (DS10/RC23 and DS10/RC40) . . . . . . 66

3 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703.2 O&M Software Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713.3 Communication Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723.4 Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

4 Managed Objects and RITs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

3BK 21232 AAAA TQZZA Ed.05 3 / 84

Contents

4.1 MFS Managed Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784.1.1 MFS Managed Object Class, Naming Attribute and Description . . . . . . . . . . . . . 784.1.2 MFS Managed Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814.1.3 MFS Managed Object Allowed States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 824.1.4 MFS Managed Object Supported Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

4.2 MFS RITs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

4 / 84 3BK 21232 AAAA TQZZA Ed.05

Preface

Preface

Purpose The 9135 Multi-BSS Fast Packet Server Description describes the functions,hardware and software of the MFS.

What’s New In Edition 05Improve Clock Synchronization (Section 2.3.1.4) with the new condition forautonomous synchronization of the MFS.

In Edition 04Update with the new equipment naming.

In Edition 03Improvements made in Hub/Switch Subsystem (Section 1.2.3), Cables (Section2.1.4),Modules (Section 2.3.3.1), Hub/Switch Subrack (Section 2.3.4),Modules/PBAs (Section 2.3.4.1), MFS Managed Object Hierarchy (Section4.1.2), MFS Managed Object Allowed States (Section 4.1.3), MFS ManagedObject Supported Operations (Section 4.1.4)

Improvements made in Clock Synchronization (Section 2.3.1.4).

Add GB over IP, new transport mode for the GB interface

In Edition 02Improvements made in Clock Synchronization (Section 2.3.1.4).

In Edition 01First official delivery in B10.

Audience This manual is intended for:

Commissioning personnel

Support and service engineers

OMC-R operators.

3BK 21232 AAAA TQZZA Ed.05 5 / 84

Preface

Assumed Knowledge The reader must have a general knowledge of telecommunications systems,terminology and Alcatel-Lucent BSS functions.

6 / 84 3BK 21232 AAAA TQZZA Ed.05

1 MFS Functional Description


This section provides an overview of the MFS.

It describes the MFS architecture, including related external interfaces,presents the functions and features of the MFS, and introduces the traffic andsignalling links used by the MFS.

3BK 21232 AAAA TQZZA Ed.05 7 / 84


1.1 Introduction to MFSGeneral Packet Radio Service (GPRS) extends the circuit-switched voice anddata capabilities of a GSM network to include high speed packet-switched data.A mobile station that is fitted with the (E)GPRS facility can transmit and receivedata up to an approximate theoretical maximum of 150 kbit/s.

The Alcatel-Lucent solution provides the Multi-BSS Fast Packet Server (MFS)to perform both circuit and high speed packet switching. The MFS is internal tothe BSS and provides the following basic functions:

PCU (Packet Control Unit) functions,

including:

PAD (Packet Assembly/Disassembly) function

Scheduling of packet data channels

Automatic Retransmission Request functions

Channel access control functions

Radio channel management functions.

The Gb Interface protocol stack, with 2 transport mode:

over Frame Relay

over IP (not for AS800).

1.1.1 MFS Overview

The position of the MFS in the Alcatel-Lucent BSS is shown in the figure below.

BSS

MS

MSC To PSTN

OMC−R

BSS

GGSN

TCBTSAter Mux

Gb

PS Traffic

Abis

SGSN

To Public DataNetworks

Ater Mux

PS Packet−Switched Traffic

CS Circuit−Switched Traffic

Gb MFS/SGSN Interface

PSTN Public Switched Telephone NetworkGGSN Gateway GPRS Support Node

SGSN Serving GPRS Support Node

CS Traffic

Gb

Gb

BSC

MFSA−GPSServer

Gb

BTS

The MFS communicates primarily with the following GPRS network elements:

The Serving GPRS Support Node (SGSN), which provides the BSS withmobile packet switching functions, including security and an interface to the

Home Location Register (HLR).

The Serving Mobile Location Center (SMLC), which is integrated into theMFS and is configured by the OMC-R. In the same way that the MFS

provides the GPRS services to several BSCs, the SMLC performs locationsservices for the same set of BSCs.

8 / 84 3BK 21232 AAAA TQZZA Ed.05


The Gateway GPRS Support Node (GGSN), which provides interworkingwith external packet-switched networks.

For more information about these GPRS Elements , refer to the BSS SystemDescription.

The MFS supports multiple BSSs and MSCs. An MFS can be connected toseveral SGSNs. Several MFSs can be connected to the same OMC-R.

Circuit-switched traffic is handled in the usual way by the MSC and the BSC.The link between the BSC and TC can only carry circuit-switched traffic. Alink going through the MFS can contain circuit-switched, circuit-switched andpacket-switched, or packet-switched traffic.

In the uplink direction, packet-switched data from the mobile station are sent tothe MFS as blocks which are assembled into packets. Depending on the codingscheme in use (see GPU Telecommunications Functions (Section 1.5.1) ), ablock can consist of 20 or 30 bytes. When all the bytes have been received,they are placed into packets of up to 1500 bytes for transmission to the SGSNvia the Gb Interface. In the downlink direction, packets are disassembled in theMFS and sent to the mobile station as blocks of 20 or 30 bytes.

For more information about the Multi-BSS Fast Packet Server , refer to theBSS System Description.

1.1.2 (E)GPRS Functions

The table below lists the standard (E)GPRS functions and shows where theyare implemented (software only, or both software and hardware).

Function BTS MFS SGSN GGSN

CCU software - - -

PCU - software andhardware

- -

SGSN - - software andhardware

-

GGSN - - - software andhardware

Gb Stack - software andhardware

software andhardware

-

For more information about (E)GPRS-Specific Implementation , refer to theBSS System Introduction.

3BK 21232 AAAA TQZZA Ed.05 9 / 84


1.2 MFS ArchitectureThis section provides an overview of the MFS architecture and describes thethree major subsystems of the MFS:

Telecommunications

Server

Hub/Switch.

The MFS’s basic architecture is shown in the figure below.

Duplicated Ethernet LANsPCM Links

PCM Links

Server A

GPU

GPU

Spare GPU

Telecommunications Subsystem

Server Subsystem

Hub/SwitchSubsystem

GPU GPRS Processing UnitLAN Local Area Network

Ethernet

SGSN

IP Network

10 / 84 3BK 21232 AAAA TQZZA Ed.05


The MFS architecture is shown in more detail in the figure below.

GPU

JAE1/JAE1CPCM Links

To IMT To SGSN

PCM Links

Ethernet Links

ICL/ISL Links

RS−232 Links

Redundant GPUBAREDC2 (for

Redundant GPU)

Subrack Midplane

Telecommunications Subrack

JBETI

JAETI JAETI

JBETI

BATTU BATTU

Ethernet Hub/Switch A1

Ethernet Hub/Switch B1

Server A Server B

Terminal Server

Ethernet Hub/Switch A2

Ethernet Hub/Switch B2

Hub/Switch Subrack

Server Subrack

Power AlarmsPower AlarmsExternal AlarmsExternal Alarms

External SettingsExternal Settings

ICL/ISL Busses

To SGSNEthernet

To OMC−R

3BK 21232 AAAA TQZZA Ed.05 11 / 84


1.2.1 Telecommunications Subsystem

The telecommunications subsystem containes two subracks. Each subrackcontains two power supply units. The subracks have a midplane with PBAsinserted from both the front and the rear. The subsystem uses the GPRSProcessing Unit (GPU) PBA to implement the PCU function. These are insertedfrom the front. Up to 16 GPUs can be fitted in one subrack.

Each GPU has an associated ’applique’ (JAE1 (120Ohm) or JAE1C (75Ohm)).These rear inserted ’appliques’ are used for physical line termination andas elements of an n+1 redundancy scheme. They are not protected by theredundancy mechanism. Communication between the servers and eachGPU is via duplicated Ethernet connections which include the BATTUs andEthernet hubs/switches.

The RIT type of the GPU PBA is JBGPU2.

The associated ’applique’ PBA for the redundant GPU is the BAREDC2.

The associated ’applique’ PBAs for the duplicated JBETIs are the JAETIs.

The JBETI provides alarm and status information for the servers. It detects theremoval/insertion of its associated JAETI and, when required, resets or rollsback the GPU specified by the server with a minimum loss of time or GPRStelecom outage. The detection and reset functions are performed using theICL/ISL buses. Each JAETI interconnects its associated JBETI with:

The servers

Three incoming cabinet power alarms

Eight incoming alarms (external to the cabinet)

Outgoing server-controlled settings for six external devices.

Note: Most of the telecommunications PBAs have a JA (applique) or JB (board) prefixin their names. Refer to Telecommunications Subrack (Section 2.3.1) forspecific layout information.

12 / 84 3BK 21232 AAAA TQZZA Ed.05


1.2.2 Server Subsystem

The server subsystem consists of two UNIX(TM) servers, one of which operatesin redundant mode. In the event of the master server failing, the standby serverbecomes the master server. The servers have their own local disk storageand they also share at least two common disks.

The server supervises the whole MFS cabinet and equipment and, in particular,the GPU PBAs. It gathers status and alarm information and communicates withthe OMC-R to transfer O&M information.

A IOLAN(TM) terminal server and an Installation and Maintenance Terminal(IMT) are used for the software installation, maintenance and hardwaremanagement of the servers.

There are two types of servers:

AS800In this configuration, the servers and hubs are contained in separatesubracks (refer to Subracks (Section 2.3) )

DS10 (RC23 or RC40)In these configurations, the servers and hubs/switches are contained inone subrack (refer to Subracks (Section 2.3) ).

Both servers are interconnected via the Ethernet Hubs/Switches. The serversuse RS-232 links via the terminal server and a Hub/Switch to connect to the IMT.

1.2.3 Hub/Switch Subsystem

The Hub/Switch subsystem consists of duplicated 100 Mbit/s Ethernetnetworks, one of which operates in redundant mode.

The Ethernet networks interconnect the GPUs and servers and provide theconnection points for the OMC-R and the IMT.

Two Ethernet hubs/switches provide duplicated connections between thetelecommunications subrack and the servers. If a second telecommunicationssubrack is fitted, two additional Ethernet hubs/switches are required.

Note: There are the following limitations:

The switch is not allowed for MFS with AS800

In order to support GB over IP, the old hubs/switches are replaced with

Alcatel-Lucent OmniStack LS 6224 switches

1.2.4 OMC-R Connection

The interface with the OMC-R is IP over Ethernet. This can be extendedusing any available means.

3BK 21232 AAAA TQZZA Ed.05 13 / 84


1.3 External InterfacesThe external MFS interfaces are shown in the figure below.

MFS

PCM Links

Ater Mux Interface

Gb Interface

BSC

SGSN

FRDN

IMT (Installation and Maintenance Terminal)

TCAter Mux Interface

PCM Links

IMT

OMC−R

Ater Mux InterfaceBSC

Ethernet Link

Ethernet Link

Gb Interface

Ater Mux + Gb Interface

A−GPS Server

Ethernet Link

Gb Interface

MSC

IP Network

IP Gb

The external MFS interfaces are described in the following table.

Interface Description

MFS-BSC Interface The interface between the MFS and the BSC (AterMux interface) is a 2 Mbit/s PCM link. The time slotswithin one link can carry both circuit-switched andpacket-switched traffic and SS7 signaling.

When the Ater Mux is mixedcircuit-switched/packet-switched, theMFS transparently connects the circuit-switchedtime slots to the TC and converts thepacket-switched time slots into the Gb interfaceprotocol, which is forwarded to the SGSN throughthe TC and MSC or through the MSC.

When the Ater Mux is fully packet-switched, the Gbtraffic is forwarded directly to the SGSN when thereis a dedicated MFS-SGSN link, or through the MSC.

The BSCLP interface is an Lb based protocol thatallows communication between the BSC and SMLCin a circuit-switched domain.

MFS-TC Interface The interface between the MFS and the TC (AterMux interface) is a 2 Mbit/s PCM link.

This link can be:

Fully devoted to carry circuit-switched time slots

Fully devoted to carry the Gb interface and SS7

on packet-switched time slots

A mixed circuit-switched/packet-switchedinterface on the same Ater Mux.

MFS-MSC Interface The interface between the MFS and the MSC isused to carry the Gb interface when there is nodedicated MFS-SGSN link.

14 / 84 3BK 21232 AAAA TQZZA Ed.05


MFS-SGSN Interface The interface between the MFS and the SGSN isused to carry the Gb interface.

This interface can go through a:

frame relay data network

IP network.

MFS-OMC-R Interface The OMC-R is connected to the MFS via anEthernet link. The OMC-R can be collocated withthe MFS or remote.

MFS-IMT Interface An Ethernet link is used to connect the IMT to theMFS. MFS commissioning and local managementare performed using the maintenance terminal.

MFS-A-GPS ServerInterface (SAGI)

The SAGI interface is an Lb interface on TCP/IP thatexchanges messages between the SMLC and theexternal A-GPS server following an Assisted GPSpositioning request in the circuit-switched domain.

3BK 21232 AAAA TQZZA Ed.05 15 / 84


1.4 Traffic and Signaling LinksThe figure below shows the traffic and signaling links for both circuit-switchedand packet-switched connections.

1211211211211211212112112112112112

PCU

MFS

TCBTS TCH

RSL

M−EGCH

BSCSS7

GCH

GSL

TCH

SS7

TCH

Gb1121121121

The table below briefly describes the circuit-switched and packet-switchedtraffic and the signaling links.

Link Description

TCH Carries circuit-switched voice or data. On the Abis Interface, circuit-switched voice can becarried on an 8 kbit/s or 16 kbit/s channel. On the Ater Mux Interface, it is carried on a 16kbit/s channel. Circuit-switched data is always carried on 16 kbit/s channels.

RSL Carries circuit-switched traffic management information for mobile station-to-networkcommunication. It is carried on a 16 kbit/s or 64 kbit/s channel. There is one RSL per TRE.The RSL also carries signaling to control the BTS TRX.

SS7 Carries call control and mobility management information between the MSC and BSC ona 64 kbit/s channel.

GCH Carries blocks of packet-switched data on a 16 kbit/s channel between the BTS and MFS.The blocks are transparently routed through the BSC to the BTS. There is one Ater resourceallocated per GCH for GPRS mobile stations.

M-EGCH Carries packet-switched data traffic on 16 kb/s channels between the BTS and MFS. Theblocks of all the PDCHs of a TRX are multiplexed on this link.

GSL Carries packet-switched traffic management information between the MFS and BSC on a 64kbit/s channel. If a second GSL is connected to the BSC for redundancy purposes, it mustbe on a different PCM link. GSL also carries location services messages, when enabled.

Gb Carries packets of data to and from the SGSN on transparent n x 64 kbit/s channels. This isa single link created by concatenating a number of 64 kbit/s time slots. The HDLC protocolis used, allowing remote SGSN connections to be made over a Frame Relay networkor through a IP network..

For more information about these traffic and signalling links, refer to the BSSSystem Description .

16 / 84 3BK 21232 AAAA TQZZA Ed.05


1.4.1 Physical Channel

The physical channel which supports the different packet data logical channelsis the Packet Data Channel (PDCH).

It consists of:

One TDMA time slot on the Air Interface, and

One M-EGCH (composed of one to 36 16 kb/s GCH) per TRX.

There are eight time slots in one TDMA frame, which means that each TRX canhave up to eight PDCHs. The figure below shows the Air Interface structurefor one PDCH.

Time Slots 876543287 1 1 2 3 4 5 6 7 8 2 31

310 42 5150 051

TDMA Frame (4.615 ms)

Multiframe = 52 TDMA Frames (240 ms)

Frames

In the example shown in the figure above, TS2 of each TDMA frame forms partof the same PDCH. The TDMA frames are organized as a 52-frame multiframe.

TS2 uses the frames in the multiframe as follows:

Frames 25 and 51 are unused

Frames 12 and 38 are used by the Packet Timing Advance Control Channel

(PTCCH). The PTCCH is the packet data logical channel for mobile station

timing advance control.

The remaining 46 frames are organized into blocks of four consecutive

frames (for example, Block 3 consists of TDMA frames 13-16) and areshared by the other packet data logical channels.

The figure below shows the Air Interface block structure.

3

Multiframe = 52 TDMA Frames (240 ms)

Frame

0 1 2 4 5 6 7 8 9 10 11

0 4 8 13 17 21 26 30 34 39 43 47

Block

0

Note: In the case of the Master Packet Data Channel (MPDCH), Block 0 is reservedfor the Packet Broadcast Control Channel (PBCCH) in the downlink direction.Refer to Packet Data Logical Channels (Section 1.4.2) for more information.

3BK 21232 AAAA TQZZA Ed.05 17 / 84


1.4.2 Packet Data Logical Channels

The table below provides a brief description of the packet data logical channels.

Channel Description

PCCCH The Packet Common Control Channel (PCCCH) providescommon control information to the mobile station. This includespaging, access grant and random access.

When the PCCCH is not allocated, the circuit-switched CCCHis used to initiate the packet data transfer. When the PCCCHis allocated, the PCCCH, Packet Broadcast Control Channel(PBCCH) and Packet Data Traffic Channel (PDTCH) share thesame PDCH.

The PCCCH supports the following sub-channels:

Packet Random Access Channel (PRACH) (uplink)

Packet Paging Channel (PPCH) (downlink)

Packet Access Grant Channel (PAGCH) (downlink).

PBCCH The PBCCH broadcasts general information on the downlinkwhich is used by the mobile station to access the network forpacket transmission. The existence of PCCCH (and consequentlythe existence of the PBCCH) is indicated by the circuit-switchedBroadcast Control Channel (BCCH).

PTCH The Packet Traffic Channel (PTCH) carries user data andassociated signaling:

PDTCH. Mapped to one PDCH. Up to five PDTCHs can beallocated to one mobile station.

Packet Associated Control Channel (PACCH). If multiple

PDTCHs are assigned to one mobile station, the identity ofthe PDCH carrying the PACCH is provided in the resource

assignment message. PACCH is bi-directional.

PTCCH Provides a bi-directional continuous timing advance mechanism.The mobile station is allocated a sub-channel of the uplinkPTCCH according to the timing advance index.

The PDCH which carries the PCCCH and PBCCH logical channels is referredto as the MPDCH. The location of the MPDCH is defined by the BCCHsystem information.

When an MPDCH is not defined, both the circuit-switched and packet-switchedsignaling use the BCCH and CCCH. The BSC forwards uplink CCCH flowto the MSC or MFS, as required.

Declaring an MPDCH is an operator choice which is based on the overall trafficdensity and relative loads of circuit-switched and packet-switched traffic. Ifpacket-switched traffic is low, an MPDCH is not declared.

18 / 84 3BK 21232 AAAA TQZZA Ed.05


1.4.3 Temporary Block Flow

A Temporary Block Flow (TBF) is the physical connection used by the mobilestation (uplink) or MFS (downlink) to support the unidirectional transfer ofpacket data on packet-switched physical channels.

The TBF is allocated to:

One or more PDCHs

One or more consecutive blocks to be used on the PDCHs for data transfer.

A TBF is temporary and is only maintained for the duration of the data transfer.

The blocks of a TBF contain a Temporary Flow Indicator (TFI) which identifiesthe blocks belonging to one message. Each block in the downlink direction alsocontains an Uplink Status Flag (USF). The USF tells the mobile station when itcan transmit data. For example, if the mobile station receives the required USFon Block n (downlink), it transmits its data on the following Block n+1 (uplink).

For more information, refer to GPRS Network Functions in the BSS SystemDescription.

1.4.4 NC2 in Packet Transfer Mode

During enhanced cell reselection, NC2 activates when the mobile station is inpacket transfer mode, reducing the number of cell reselections triggered duringGPRS sessions. When activated, the network controls the cell reselection ofeach mobile station involved in the packet transfer. Each of these mobilestations reports measurements on the serving cell and the six strongestsurrounding cells, enabling the network to dynamically reselect a specific cell.


1.4.5 Signaling

A GPRS Signalling Link (GSL) consists of a 64 kbit/s LAPD link between theMFS and the BSC.

It is used to:

Notify the BSC whether there is an MPDCH

Carry paging, channel request and access grant messages if there is noMPDCH

Receive cell state change information and BSC status

Allocate SPDCHs to the MFS (BSC to MFS)

Report SPDCH usage and radio usage to the BSC (MFS to BSC)

Allocate Abis nibbles (MFS to BSC)

Ask the BSC for cross-connection between Abis and Ater nibbles (MFS

to BSC).


3BK 21232 AAAA TQZZA Ed.05 19 / 84


1.5 GPRS FunctionsThe MFS performs two main types of functions:

GPU telecommunications

MFS O&M.

1.5.1 GPU Telecommunications Functions

A PCU controls the GPRS activity of one cell and is implemented in the GPUPBA.

The GPU performs the following telecommunications functions:

High Speed Data Services (HSDS)

Packet radio resource allocation

Autonomous Packet Resource Allocation

T4 reallocation

Uplink power control

Uplink medium access mode

Timing advance

Paging management

Channel coding

Link adaptation

Gb stack management

Alignment of PMU capacity to PTU capacity.

Refer to the following sections for more information about these functions.

20 / 84 3BK 21232 AAAA TQZZA Ed.05


1.5.1.1 High Speed Data ServiceHSDS provides CS1 to CS4 for GPRS, and MCS1 to MCS9 for E-GPRS. Italso provides functions to adapt radio resource allocation with E-GPRS mobilestations to avoid Ater blocking, by allocating more transmission resources onAbis and Ater to a radio time slot managing HSDS capability on a TRE basis.

HSDS is supported in each BSS and provides:

A second Abis linkWhen there are insufficient Abis time slots on one Abis link, a second Abiscan be attached to the BTS. This second link supports an extra set of 16knibbles for packet traffic but does not carry circuit-switched traffic.

MPDCH handlingMPDCH handling allows the MFS to manage the MPDCHs based on thepositioning information received from the BSC. This avoids inter-operablilityissues with mobile stations and wasting Ater resources.

CS1/CS4 and E-GPRS protocol modulation and coding schemesNine different modulation and coding schemes MCS1 to MCS9 are definedfor the E-GPRS radio data blocks.

Enhanced radio resource allocationE-GPRS traffic has priority over GPRS traffic. E-GPRS capable TRX areused for E-GPRS traffic and GPRS throughput is optimized as long as itdoes not conflict with E-GPRS traffic.

T4 reallocationT4 reallocation solves conflicts between uplink GPRS TBFs and downlinkE-GPRS TBFs.

Dynamic transmission handlingPDCHs are established with the maximum number of GCHs, whatever thesupported traffic. GCHs are released if the number of established GCHsbecomes greater than the target number of GCHs. For GPRS and E-GPRSTBF allocation, new PDCHs are established with a reduced number ofGCHs during the Ater congestion state.

3BK 21232 AAAA TQZZA Ed.05 21 / 84


1.5.1.2 Packet Radio Resource AllocationPacket radio resource allocation defines the number of PDCHs that areassigned to the mobile station.

The number of PDCHs that can be assigned to the mobile station depends onthe mobile station multislot class capability:

Type 1 mobile stations operate in simplex mode (that is, transmission and

reception are not simultaneous). The maximum number of PDCHs allowedare two for the uplink direction and four for the downlink.

Class 2 mobile stations operate in duplex mode (that is, transmission and

reception are simultaneous). The maximum number of PDCHs allowed arefive for the uplink and downlink.

An O&M parameter that can limit the number of PDCHs allocated to a TBF.

The MFS dynamically controls all radio time slots that can be used forpacket-switched traffic, thereby simplifying time slot allocation and decreasingPMU CPU loads.

1.5.1.3 Autonomous Packet Resource AllocationAutonomous Packet Resource Allocation introduces a new way of sharing radioresources between the MFS and the BSC. With this feature the MFS no longerneeds to request radio time slots from the BSC. Instead, the MFS is alwaysaware of all the available time slots. This speeds up PDCH establishment in theBSC and MFS and decreases CPU loads.

The feature introduces a CS/PS resource-sharing concept using time slotsdefined as follows:

Reserved for PS

Priority for PS

Priority for CS

Reserved for CS

Because the MFS is aware of all available time slots, the choice of the bestallocation to serve the TBFs in the MFS is simplified. With this feature, theSPDCHs are ordered by the BSC to ensure consistent CS and PS allocation.The BSC ranks the PS TRXs and sends this ranking to the MFS on theBSCGP interface at cell creation and when the cell is modified during anO&M operation. The BSC defines the number of SPDCHs allocated to theMFS by computing the MAX_SPDCH_LIMIT parameter periodically. Theresulting SPDCH allocation is based on the whole BSS load (CS + PS load),with the PS load being provided periodically by the MFS. The allocatedSPDCHs are always those with the highest priority for PS allocations. Theirpositions are provided to the MFS in a new message, the Radio Resource

(RR) Allocation Indication message. Consequently, the MFS no longerneeds to request additional SPDCHs from the BSC.

1.5.1.4 T4 Re-allocationT4 reallocation resolves conflicts between uplink GPRS TBFs and downlinkE-GPRS TBFs when they share the same PDCH. An uplink GPRS TBF isreallocated on resources that do not support any downlink GPRS TBFs.

22 / 84 3BK 21232 AAAA TQZZA Ed.05


1.5.1.5 Uplink Power ControlWhen the mobile station first accesses the cell on the PRACH, it uses theoutput power level specified on the PBCCH. After this, the mobile station outputpower level is based on the received signal strength. It is assumed that thepower loss is the same for uplink and downlink.

1.5.1.6 Uplink Medium Access ModeContention control is not required in the downlink direction even if the PDCH isshared by several mobile stations.

In the uplink direction, contention control is required when multiple mobilestations share the same PDCH. The MFS avoids contention by authorizingparticular mobile stations to transmit at particular times.

Medium access mode is the method by which the logical channels are allocatedon the uplink PDCH.

The channels are:

PDTCH/PACCHEach mobile station is allocated a particular USF value by the MFS. When amobile station receives the required USF value in a downlink block, ittransmits its data on the next uplink block.

PRACHWhen the mobile station wants to initiate a packet access procedure, it hasto send a packet channel request on the PRACH. The mobile stationexamines the downlink blocks and looks for a specific (free) USF valuewhich marks the position of the PRACH on the uplink. A free USF value indownlink Block n means that the PRACH is on uplink Block n+1.

PACCHWhen a mobile station is involved in a downlink packet transfer, it sends anacknowledgment, when required, on the uplink PACCH. The mobile stationexamines its downlink blocks and looks for a particular value (not theUSF) which authorizes the mobile station to transmit its acknowledgment.The acknowledgment is required by the mechanism which schedules theuplink block.

1.5.1.7 Timing AdvanceThe correct value for the timing advance used by the mobile station whentransmitting uplink blocks is derived by:

Initial estimationThe BTS performs measurements on the single access burst carrying thepacket channel request and sends a value to the mobile station. Thisvalue is used for uplink transmissions until the continuous timing advancemechanism provides a new value.

Continuous advanceThe BTS analyzes received access bursts over successive 52-framemultiframes and determines values which it sends to the mobile station.

For the downlink direction, the initial timing advance value is computed onreception of the Packet Control Acknowledgment from the mobile station. Thevalue is then returned to the mobile station in a timing advance or powercontrol message.

3BK 21232 AAAA TQZZA Ed.05 23 / 84


1.5.1.8 Paging ManagementThe network can coordinate circuit-switched and packet-switched paging. Thismeans that circuit-switched paging messages can be sent on the channelsused for packet-switched paging messages.

There are three modes:

Network Operation Mode 1Circuit-switched paging messages are sent via the SGSN and MFS.The circuit-switched paging message for the GPRS-attached mobile stationis sent on the PPCH or CCCH paging channel, or on the PACCH. Thismeans that the mobile station only needs to monitor one paging channel. Itreceives circuit-switched paging messages on the PACCH when the mobilestation is in packet transfer mode.

Network Operation Mode 2Circuit-switched paging messages are sent via the MSC and BSC, butnot the MFS.The circuit-switched paging message for the GPRS-attached mobilestation is sent on the CCCH paging channel. The channel is also used forpacket-switched paging messages. This means that the mobile station onlyneeds to monitor PCH. Circuit-switched paging continues on the PCH evenif the mobile station is assigned a PDCH.

Network Operation Mode 3Circuit-switched paging messages are sent via the MSC and BSC, butnot the MFS.The circuit-switched paging message for the GPRS-attached mobile stationis sent on the CCCH paging channel. The packet-switched paging messageis sent on either the PPCH (if allocated) or on the CCCH paging channel.

1.5.1.9 Channel CodingDifferent Coding Schemes (CS) can be used for the data on the Air Interface.For GPRS, the CS1 to CS4 coding schemes are used. For E-GPRS, the MSC1to MSC9 schemes are used. For more information on coding schemes, refer toGPRS CS3/CS4 and E-GPRS Protocol in the BSS System Description.

1.5.1.10 Link AdaptationFor GPRS, link adaptation changes Coding Schemes (CS) according to radioconditions and CS1 to CS4 requirements. For E-GPRS, link adaptationchanges Modulation and Coding Schemes (MCS) according to radio conditionsand MCS requirements.

When radio conditions worsen, a protected MCS with more redundancy ischosen, leading to a lower throughput. Inversely, when radio conditions improve,a less protected MCS is chosen for higher throughput. Nine modulation andcoding schemes enhance packet data communications (E-GPRS), providingraw RLC data rates ranging from 8.8 kbit/s to 59.2 kbit/s. Data rates above 17.6kbit/s require 8-PSK modulation on the Air Interface, instead of GMSK.

24 / 84 3BK 21232 AAAA TQZZA Ed.05


1.5.1.11 Gb StackCommunication between the MFS and SGSN is via the Gb Interface.

The Gb Stack function provides the following required supporting protocollayers:

Depending on GB transport mode:

Frame relay

IP

Network service

BSS GPRS Protocol (BSSGP).

1.5.1.12 Alignment of PMU Capacity to PTU CapacityFor non-streaming PS traffic, the PPC in the GPU can become a bottleneck,reducing throughput. This bottleneck can be overcome by aligning the capacityof the PMU to that of the PTU. PMU throughput is increased by:

Lowering the signaling overhead. This increases the amount of CPUavailable for PDU transfer

Lowering the CPU cost of PDU transmission so that more PDUs are

transmitted for a given signaling overhead.

To lower both the signaling overhead and the CPU cost of PDU transmission,the following improvements are implemented in the GPU software:

Extended UL allocation, whereby the radio resource allocation algorithm is

no longer used for each UL TBE establishment

Optimized Gb PDU handling

Saved memory copies, which reduces the number of memory copies

required per PDU.

3BK 21232 AAAA TQZZA Ed.05 25 / 84


1.5.2 Abis Resource Manager

The Abis Resource Manager was implemented in the MFS to manage the Abisnibbles (and their pools) required for Dynamic Abis Allocation and M-EGCHStatistical Multiplexing.

For more information on these features, refer to Dynamic Abis Allocation andM-EGCH Statistical Multiplexing in the BSS System Description.

There is one Abis resource manager per BTS. This resource manager iscreated in a GPU when the first cell (or the first BTS sector in cells sharedover two BTS) of a given BTS is created. The cell-to-GPU mapping algorithmthen ensures that all the other cells of the BTS are also mapped to the sameGPU. As a result, cells created after the first cell are able to use the same Abisresource manager.

When a cell shared over two BTS is created, two Abis resource managersare created (one for each BTS). In this case, one Abis resource manager isused to manage the Abis resources for the PS-capable TRXs of the cell. Theother resource manager is used to:

Establish an M-EGCH link for the MPDCHs of the cell (if MPDCHs areestablished by the BSC in the non-PS-capable sector of the cell)

Make the bonus basic Abis nibbles available to the other cells (if any) of the

BTS containing the non-PS-capable BTS sector.

When the last cell of a BTS (or the last BTS sector of a shared cell) is deleted,the Abis resource manager of that BTS is also deleted.

The Abis resource manager uses the following input messages to managethe Abis nibble pools:

Cell State Response or Cell State Change

The contents of the two messages are the same.These two messages contain information from the BSC indicating theposition of the bonus Abis nibbles to the MFS.

Extra Abis Pool Configuration

This message indicates the extra Abis time slots available for PS trafficin a BTS.

RR Allocation Indication

This message indicates which radio time slots are available for PS traffic(i.e., which radio time slots have basic Abis nibbles which can or cannot beused for PS traffic).

Cell deletion message.

26 / 84 3BK 21232 AAAA TQZZA Ed.05


1.5.3 MFS O&M Functions

The O&M functions of the MFS manage the:

Equipment

GPU telecommunications application

Alarms

Performance.

1.5.3.1 Equipment ManagementThis function manages the telecommunications equipment and, in particular,the JBETI and GPU hardware and low-level software. It handles all requests inthe first part of the initialization process.

This includes:

GPU software booting

GPU software reset and rollback functions

Session layer configuration

Framer configuration for Gb Interface messages

GPU switch configuration for circuit-switched connections.

The function also manages the switch over from a defective GPU to the spareGPU, and outage time during major software changes.

1.5.3.2 GPU Telecommunications Application ManagementThis function manages the telecommunications application of each logical GPU.It is responsible for telecommunications resource configuration and supervision.

This includes the:

Bearer channels

Gb Interface

Ater Mux Interface towards the BSC

Cell management domains.

1.5.3.3 Alarm ManagementAlarm Management is responsible for the processing of hardware andtelecommunications alarms within the MFS.

This function:

Collects all fault information for telecommunications and external alarms, thetelecommunications hardware and the active server

Records the fault information in a table

Allows the local IMT and the OMC-R to access the fault information

Generates the end alarm for pending alarms

Manages communication with the IMT.

3BK 21232 AAAA TQZZA Ed.05 27 / 84


1.5.3.4 Performance ManagementPerformance Management is responsible for:

Collecting the performance management counters associated with each

logical GPU

Creating a file to contain the counter values.

The MFS uses the following types of standard counters:

Counters monitoring activity between the BSC and the MFS

Counters monitoring activity between the MSC and the MFS.

1.5.4 SMLC Functions

The Serving Mobile Location Center (SMLC) provides the following functions:

Handles LCS protocols towards the BSC, the mobile station, and theexternal A-GPS server

Manages call-related location context per mobile station and positioning

methods

Triggers the position calculation process for the TA positioning method, and

presents the mobile station location estimate in standard format

Requests GPS Assistance Data from the external A-GPS server andprovides it to the mobile station

Provides mobile station-performed GPS measurements to and from the

A-GPS server to provide mobile station-assisted or mobile station-basedA-GPS positioning in a standard format

Improves location accuracy by providing assistance data via a GPS link

to the GPS-mobile station (A-GPS), navigation data from satellites andDifferential GPS (DGPS), and provides corrections to measurement errors

Uses O&M information present in the MFS or SMLC, provided by the OMC-R

Performs error handling.

28 / 84 3BK 21232 AAAA TQZZA Ed.05

2 Hardware

2 Hardware

This section describes the MFS hardware.

3BK 21232 AAAA TQZZA Ed.05 29 / 84

2 Hardware

2.1 CabinetThe 9135 MFS hardware consists of an indoor cabinet which is housed in atelecommunications building.

The MFS cabinet exists in several versions:

MFSRACK with an AS800 server

MFSDS10

with:

DS10/RC23 server, or.

DS10/RC40 server.

The following sections describe the cabinets in terms of:

Layout (Section 2.1.1)

Dimensions and Weight (Section 2.1.2)

Environment (Section 2.1.3).

2.1.1 Layout

The cabinets (BRVPS2) contain the following components.

MFSRACK:

Top rack unit (BDTRU2)The top rack unit provides DC power. Refer to Power System (Section 2.2)

Telecommunications Subrack (Section 2.3.1) (BSXTU)

Server Subrack for MFSRACK (Section 2.3.2) (PVSERV44)

Hub/Switch Subrack (Section 2.3.4) (JSHUB).

MFSDS10:

Top rack unit (BDTRU2)The top rack unit provides DC power. Refer to Power System (Section 2.2)

Telecommunications Subrack (Section 2.3.1) (BSXTU)

Server Subrack for MFSDS10 (Section 2.3.3) (JS19P)

30 / 84 3BK 21232 AAAA TQZZA Ed.05

2 Hardware

Both cabinets are shown in the figure below.

BDTRU2

TelecommunicationsSubrack

BSXTU

Server Subrack

PVSERV44

Hub/ Switch Subrack

JSHUB

MFSRACK

BRVPS2


BSXTU

Server Subrack

JS19P

MFSDS10


BSXTU


BSXTU

BRVPS2

Cable entry to the cabinet can be from either the:

TopIf the cabinet is mounted on a solid floor, cable ducting in the ceiling carriesthe cables to the top of the cabinet.

BottomIf the cabinet is mounted on a raised floor, cable ducting in the floor carriesthe cables to the bottom of the cabinet.

3BK 21232 AAAA TQZZA Ed.05 31 / 84

2 Hardware

2.1.2 Dimensions and Weight

The cabinet is designed for buildings with a minimum ceiling height of2.7 meters.

The table below shows the cabinet’s external physical dimensions.

Dimension Overall Size (mm)

Height 2208

Width (including side panels) 1000

Depth 600 (MFSRACK)

700 (MFSDS10)

The approximate weight of the fully equipped cabinet is 400 kg.

The cabinet consists of a rack fitted with side panels and front and rear doors.When the doors are closed, the equipment is EMI protected. The doors andside panel are easily removed for maintenance purposes.

The MFSRACK is a standard ETSI rack, 600 mm deep, that houses foursubracks.

The MFSDS10 rack is 700 mm deep and houses three subracks.

32 / 84 3BK 21232 AAAA TQZZA Ed.05

2 Hardware

2.1.3 Environment

Equipment must not be exposed to extremes of temperature or relativehumidity. To meet the required environmental conditions, air conditioningequipment may be required.

The following environmental conditions must be respected.

2.1.3.1 Temperature and HumidityFor altitudes between sea level and 500 meters, the temperature must bebetween + 5C and + 40C, within a relative humidity band of between 20 % and80 %. The temperature gradient must be less than 0.5C per minute.

Precautions must be taken to avoid electrostatics as this may result in minorshocks and/or damage to the equipment.

The relative humidity must be at least 20 % at manned sites or duringmaintenance periods.

2.1.3.2 Atmospheric PressureFor normal equipment operation, the atmospheric pressure must be between65 kilopascals (kPa) and 120 kPa. Low pressure extremes must not be allowedto coincide with upper temperature limits.

Note: An altitude of 3500 meters corresponds to a pressure of approximately65.7 kPa.

2.1.3.3 Solar RadiationDirect solar radiation must be avoided as this can result in damage to equipmentdue to overheating. Ensure that equipment is not subjected to direct sunlight.

2.1.3.4 Dust and ParticlesThe equipment operates normally in the presence of solid (non-conductive,non-ferromagnetic, non-corrosive) particles. The table below lists the maximumsizes and concentrations of particles.

Size of Particles(micrometers)

Concentration(millions of particles per cubic meter)

0.5 14

1 0.7

3 0.24

5 0.13

2.1.3.5 LightingAll optical signals, displays and labels are visible with an ambient light intensityof 800 lux.

3BK 21232 AAAA TQZZA Ed.05 33 / 84

2 Hardware

2.1.3.6 CoolingThe 9135 MFS equipment uses forced air cooling.

2.1.3.7 Safety StandardsThe 9135 MFS conforms to the EN60950 (Europe) safety standards.

2.1.4 Cables

The external and inter-subrack cabling is shown in the figure below.

16 x JLHE1

16 x JLHE1

Server Server

16 x JAE1/JAE1C

BATTU

JAETI

BATTU

JAETI

BLAAA

To DDF

To DDF

External AlarmsExternal Settings

16 x JLERH 16 x JLERH

BLAAA

BLAAA

BLAAA BLAAA

JLHALA

JLERHJLERH

ALETHD

ALETHD ALETHD

ALETHD

JLRJDB

BLTLM BLTLM

To IMT

TRU

16 x JAE1/JAE1C

BATTU

BATTU

JAETI

JAETI

Terminal Server

Hub Hub

JAHPS

JAHPSGb Gb

O&MDDF : Digital Distribution Frame

34 / 84 3BK 21232 AAAA TQZZA Ed.05

2 Hardware

The table below lists the external cables.

Identity From To Comment

ALETHD Hub/Switch IMT Ethernet

ALETHD Server OMC-R Ethernet

BLAAA JAETI Devices Alarms and settings

JLHE1 JAE1 DDF 32 PCM cables per subrack

ALETHD Switch ExternalRouter

Ethernet

ALETHD Hub/Switch ExternalA-GPSServer

Ethernet

To beupdated

OS-LS-6224 Externalrouter

1Gb Ethernet cable

The table below lists the inter-subrack cables.

Identity From To Comment

ALETHD Hub/Switch Server Ethernet

ALETHD Hub/Switch Terminal server Ethernet

BLAAA JAETI JAETI Different subracks

BLTLM TRU JAETI TRU alarms and referencevoltage

JLRJDB AS800 Terminal server RS-232

JLERH JAET1 Hub/Switch Ethernet

JLERH BATTU Hub/Switch Ethernet

JLHALA JAETI JAHPS Power Alarms

3BK 21232 AAAA TQZZA Ed.05 35 / 84

2 Hardware

2.2 Power SystemThe cabinet is powered by two independent -48V or -60V (nominal) DC externalpower sources. Each external power source must be capable of supplyingthe full power requirements of the cabinet in the event of the other externalpower source failing.

The maximum power consumption for a fully equipped cabinet is 3325 W.

The power distribution system is a duplicated system which minimizes systemdown time in the event of power faults. The figures below show the componentparts of the MFSRACK and the MFSDS10.

2.2.1 MFS Rack Power Distribution

10

10

LOADC ALM A1 A2 A3 A4

Bus Bar B

LOADC ALM B1 B2 B3 B4

Bus Bar A

To Server Subrack

To Server Subrack



Server Subrack

Hub Subrack

−48V(A) −48V(B)

0VPower UnitPower Unit

Power UnitPower Unit

Power Unit

−48V(A) −48V(B)

0V

−48V(A) −48V(B)

0V

−48V(A) −48V(B)

0V

−48V(A) −48V(B)

0V

−48V(A), 0V −48V(B), 0V

Circuit Breaker Set Button LOAD Indicator

(Circuit Breakers A3,B3)




Circuit Breaker Reset Button LOAD Button

36 / 84 3BK 21232 AAAA TQZZA Ed.05

2 Hardware

2.2.2 MFSDS10 Power Distribution

ALM A1 B1 B2 B3 B4A2 A3 A4 CC ALM10

10

LOAD LOAD

−48V(A), 0V −48V(B), 0V

−48V(A)−48V(B)

0V

−48V(A)−48V(B)

0V

−48V(A)−48V(B)

0V

−48V(A)−48V(B)

0V

Bus Bar A Bus Bar B

Power Unit Power Unit

Telecomunications

Subrack


Power Unit Power Unit


StorageWorks* A

StorageWorks* B

Server A (DS10/RC23 or D10/RC40)

Terminal Server

Hub

/ S

witc

h 1

Sockets

mainsFilter A

Sockets

mainsFilter A

Server Subrack

230 VAC 230 VAC

Telecomunications

Subrack

Hub

/ S

witc

h 2

Hub

/ S

witc

h 3

Hub

/ S

witc

h 4

(*) StorageWorks are present only for MFS with DS10/RC23, not for MFS with DS10/RC40

Server B (DS10/RC23 or D10/RC40)

3BK 21232 AAAA TQZZA Ed.05 37 / 84

2 Hardware

2.2.3 Top Rack Unit

The previous figures show the switches, reset buttons, and indicator lampsmounted on the front of the top rack unit.

The top rack unit consists of two identical sections. Each section performspower isolation, distribution and protection for one of the input power suppliesand external alarms:

Input power isolationThe input supply can be separately isolated by a manually-operated switch.

Input power filteringCapacitors are used to filter the input supply. The capacitors must becharged up (loaded) while the protected output supply circuit breakers areswitched off.A preload device monitors the charge level and illuminates the LOADindicator when the charge voltage is sufficiently high. The charge-upprocess can be speeded up by pressing the LOAD button.

Charge circuit protectionThe C circuit breaker opens if there is excessive current in the capacitorloading circuits.

External alarm protectionThe ALM circuit breaker trips if there are excessive voltage or currentlevels in the external alarm links.

Protected output supplies.Four circuit breakers (A1 to A4 or B1 to B4) protect the output suppliesagainst excessive currents. Each circuit breaker has two outputs, one ofwhich connects to Bus Bar A, while the other connects to Bus Bar B.In the MFSRACK, the A3/B3 outputs go directly to the server subrack.In the MFSDS10, the B4 output goes directly to the terminal server.

2.2.4 Bus Bars

A bus bar is fitted down each side of the rack. Each bus bar carries theprotected output supplies from the A and B sections of the top rack unit. TheHub/Switch subrack in the MFSRACK receives protected output suppliesonly from Bus Bar B.

2.2.5 Telecommunications Subracks

The telecommunications subrack input supplies are protected by the A1/B1and A2/B2 circuit breakers. The power units are located at each side of thesubracks.

2.2.6 Server Subrack in MFSRACK

The AS800 server subrack input supplies are protected by the A3/B3 circuitbreakers. The subrack contains its own power units.

38 / 84 3BK 21232 AAAA TQZZA Ed.05

2 Hardware

2.2.7 Server Subrack in MFSDS10

The DS10/RC23 servers and StorageWorks have a duplicated 230VACpower supply.

The DS10/RC40 servers have a duplicated 230VAC power supply.

The terminal server input supplies are protected by the B4 circuit breaker.

2.2.8 Hub/Switch Subrack in MFSRACK

The Hub/Switch subrack input supplies are protected by the A4/B4 circuitbreakers. The subrack contains two power units fitted on the right-hand sideof the subrack.

2.2.9 O&M System

A top rack unit alarm is generated if the C circuit breaker is open. The circuitbreaker protects the capacitor charging circuits.

2.3 SubracksThis section describes the subracks for the MFSRACK and the MFSDS10cabinets.

2.3.1 Telecommunications Subrack

This section describes the telecommunications subrack used in the MFSRACKand the MFSDS10. The figure below shows the subrack layout.

Fan Unit − BDAFU3+BAFAN2

PowerUnit PBAs

Telecommunications PBAsPower

Unit PBAs

The subrack contains the following components:

Fan Unit

Power Unit PBAs

Telecommunications PBAs.

3BK 21232 AAAA TQZZA Ed.05 39 / 84

2 Hardware

2.3.1.1 Fan UnitThe fan unit consists of two modules:

The main module (BDAFU3)

The fan unit alarm board (BAFAN2), which is a sub-assembly of BDAFU3.

The fan unit provides ventilation for the subrack. It draws air from below thesubrack and expels it through the top. The front panel contains a maintenanceswitch and a fault indicator. The fan unit receives its 12V input supply fromthe subrack power units. It consists of a controller, a tray with 14 fans, and 10temperature sensors.

The controller:

Controls the current supplied to each fan and monitors the fan’s speed

A non-urgent fan alarm is generated if:

The speed drops below the low speed threshold

There is no fan current (fan missing).

Monitors the temperature sensors.If a sensor detects an air temperature greater than 65C, an urgent alarmis generated.

Switches off the subrack power units if the air temperature exceeds 70C.

40 / 84 3BK 21232 AAAA TQZZA Ed.05

2 Hardware

2.3.1.2 PBA PositionsThe physical locations of the telecommunications and power unit PBAs areshown in the figure below.

SUBRACK TOP VIEWRear

Midplane

Front

BA35B2

BE35B2

BE35B2

BE35B2

BE35B2

BE35B2

BE35B2

JB

E−TI

JB

E−TI

JBGPU2

JBGPU2

JBGPU2

JBGPU2

JBGPU2

JBGPU2

JBGPU2

JBGPU2

JBGPU2

JBGPU2

JBGPU2

Spare

JBGPU2

BA

T−TU

JA

E−TI

JA

E−TI

JAE1

JAE1

JAE1

JAE1

JAE1

JAE1

JAE1

JAE1

JAE1

JAE1

JAE1

BA35B2

BA35B2

BA35B2

BA35B2

BA35B2

B A−REDC2

BA

T−TU

Note: The JAE1s are 120 Ohm PBAs. For 75 Ohm networks, JAE1Cs are used.

The subrack contains a midplane, which means that PBAs are plugged into thefront and rear of the subrack. PBAs that occupy the front and rear positionsof one slot operate as a pair. For example, the GPU and JAE1/JAE1C worktogether. The rear PBAs provide the cabling interface.

There are two types of PBAs:

TelecommunicationsThe figure above shows the positions of all the PBAs when the maximumnumber of JBGPU2s and their associated JAE1s are fitted. The redundantJBGPU2 and its associated BAREDC2 must occupy the positions shown.

There are two firmware packages:

JFGPU2 for the JBGPU2 board

JFETI for the JBETI board.

Power unit.There is a pool of six 200 W DC/DC converters. Each converter consistsof one BE35B2 PBA and its associated BA35B2 PBA. Five convertersprovide the subrack’s internal power requirements and the sixth converteroperates in redundant mode.Each converter receives both the -48V(A) and -48V(B) input supplies. In theevent of one input supply failing, the other input supply is used.The internally produced voltages are 5V, 3.3V, and 12V.

3BK 21232 AAAA TQZZA Ed.05 41 / 84

2 Hardware

2.3.1.3 Telecommunications Subrack O&MThe telecommunications subrack equipment provides alarms, visual faultindicators and reset buttons.

These are described below for the Fan Unit, JBETI, GPU, and BE35B2.

Fan Unit 1. Two alarm types are provided depending on the urgency:

Non-urgent

This alarm type is caused by:

At least one fan not operating at sufficient speed

The front panel maintenance key is set

The fan unit is unplugged.

Urgent.This alarm type is caused when a sensor detects a temperature greaterthan 65C.

The front panel of the fan unit provides:

A maintenance switchWhen the maintenance switch is in the ’on’ position, the fan unit canbe disconnected and withdrawn without shutting down the subrackpower units.

LED.For a description of the LED states, refer to the following table.

State Description

Green Maintenance switch on or no fault

Yellow Non-urgent alarm.

Red Urgent alarm.

42 / 84 3BK 21232 AAAA TQZZA Ed.05

2 Hardware

JBETI 2. The JBETI PBA reports alarms to the server.It collects alarms from the:

Top rack unit

Telecommunications subrack power unit PBAs

Fan unit.

The front panel of the JBETI PBA provides:

Two reset buttons

with the following functions:

S1 - hard resetAll hardware is reset.

S2 - soft resetOnly the on-board PowerPC is reset.

Two LEDs.The LEDs are controlled by the firmware during booting and by thesoftware when the software is downloaded.

For a description of the LED states during software booting, refer to thefollowing table.

Operation L1 State L2 State Time

Reset Red Yellow 5s

Booting Off Red 10s

Initialization Yellow Red 10s

Self Test Red Off 5s

Self Test/Initialization Failed Off Red (Blinking) -

Ready to Download Off Yellow (Blinking) -

Downloading Off Yellow -

End of Download Off Red -

Initialization Complete Off Off -

3BK 21232 AAAA TQZZA Ed.05 43 / 84

2 Hardware

For a description of the LED states when the software is loaded, refer tothe following table.

JBETI L1 State L2 State

Active Off Green

Reserve Off Green (Blinking)

Note: Only one of the two JBETIs is active. If the active JBETI fails, the reserveJBETI becomes active.

GPU 3. The GPU PBA front panel provides:

For a description of the LED states during software booting, refer to thefollowing table.

Operation L1 State L2 State Time

Reset Red Yellow 5s

Booting Off Red 10s

Initialization Yellow Red 10s

Self Test Red Off 5s

Self Test/InitializationFailed

Off Red (Blinking) -

Ready to Download Off Yellow (Blinking) -

Downloading Off Yellow -

End of Download Off Red -

Initialization Complete Off Off -

44 / 84 3BK 21232 AAAA TQZZA Ed.05

2 Hardware

For a description of the LED states after the software is downloaded,refer to the following table.

GPU PCM Link State L1 State L2 State

Active No PCM links installed Off Green

At least one PCM link not installed Current colorunchanged

Green

All equipped PCM links available Green Green

At least one equipped PCM link failed Red Green

Spare No PCM links installed Off Green(Blinking)

Note: Both GPU LEDs are off when in test mode. If the test fails or the GPU is locked,the LEDs are controlled by the firmware.

BE35B2 4. The BE35B2 DC/DC converters generate the following alarms:

-48V Alarm.

This alarm is triggered when the -48V(A) or -48V(B) input supply is inone of the following states:

Missing

Fuse needs replacingThe fuse protects against overload of the -48V supply by internalshort circuits. Two internally mounted fuses are provided, one for-48V (A) and one for -48V (B).

Voltage too high (over-voltage).

Converter Alarm.This is caused when any of the output voltages exceed the alarmthreshold. If the voltage reaches the over-voltage threshold, theconverter automatically shuts down.

The table below shows the Converter Alarm thresholds.

Output Voltage Alarm Threshold Shutdown Threshold

3.3V 3.60V to 3.85V 3.85V to 4.0V

5V 5.25V to 5.50V 5.5V to 6.0V

12V 12.60V to 13.2V 13.2V to 15.0V

3BK 21232 AAAA TQZZA Ed.05 45 / 84

2 Hardware

The front panel of the BE35B2 PBA provides:

On/off switch

LED.Refer to the table below for a description of the LED states.

LED State Description

L1 Green Normal operation

Off Power off or fault

2.3.1.4 Clock SynchronizationThe GPU architecture is based on synchronous interfaces, which means thatall elements connected to a GPU need to operate synchronously.

There are three modes of operation:

Autonomous ModeThis is the default mode.

The GPU is synchronized on the source with:

The links from the transcoder

The Gb interfaces to the SGSN, directly or via a frame relay networkIf the GB is over IP, this Gb interface can not be used for synchronization.

The AterMux links coming from 9130 BSC Evolution

The recommended priority order for the synchronization source is TC withthe highest priority, followed by SGSN and A1930 BSC Evolution withthe lowest priority.The selection of the synchronization sources can be modified using thelocal maintenance terminal.

Central Clock ModeTwo GPUs per subrack are assigned as masters. These masters deliver areference system clock signal on the back panels. All GPUs of the subrackare synchronized on this system clock signal.The master GPUs have one pool of synchronization sources. By default,this contains the transcoder inputs. This can be modified using the IMT.

Fixed Synchronization Sources ModeWhen all GPRS links are dedicated, it is possible to synchronize oneGPU to the output of another GPU. This GPU cascading reduces thesynchronization sources required from two-per-GPU to two-per-MFS rack.In this mode, the synchronization source algorithm is disabled and eachGPU synchronizes to port 14 or port 15 with equal priority.

Note: This mode of operation is not used for new installations as it has been replacedby the central clock mode which is more secure.

46 / 84 3BK 21232 AAAA TQZZA Ed.05

2 Hardware

The connections are made at the DDF (i.e. port 8 of GPU 1 is connected toport 14 of GPU 3). GPU cascading for one telecom subrack is shown inthe following figure.

8 9 10 11 12 13

14 15

GPU 10

8 9 10 11 12 13

14 15

GPU 11

8 9 10 11 12 13

14 15

GPU 6

8 9 10 11 12 13

14 15

GPU 7

8 9 10 11 12 13

14 15

GPU 8

8 9 10 11 12 13

14 15

GPU 9

8 9 10 11 12 13

14 15

GPU 3

8 9 10 11 12 13

14 15

GPU 4

8 9 10 11 12 13

14 15

GPU 5

8 9 10 11 12 13

14 15

GPU 1

8 9 10 11 12 13

14 15

GPU 2

From sync source

GPU cascading for two telecom subracks is shown in the following figure.

8 9 10 11 12 13

14 15

GPU 10

8 9 10 11 12 13

14 15

GPU 11

8 9 10 11 12 13

14 15

GPU 6

8 9 10 11 12 13

14 15

GPU 7

8 9 10 11 12 13

14 15

GPU 8

8 9 10 11 12 13

14 15

GPU 9

8 9 10 11 12 13

14 15

GPU 3

8 9 10 11 12 13

14 15

GPU 4

8 9 10 11 12 13

14 15

GPU 5

8 9 10 11 12 13

14 15

GPU 1

8 9 10 11 12 13

14 15

GPU 2

From sync source

8 9 10 11 12 13

14 15

GPU 21

8 9 10 11 12 13

14 15

GPU 22

8 9 10 11 12 13

14 15

GPU 17

8 9 10 11 12 13

14 15

GPU 18

8 9 10 11 12 13

14 15

GPU 19

8 9 10 11 12 13

14 15

GPU 20

8 9 10 11 12 13

14 15

GPU 14

8 9 10 11 12 13

14 15

GPU 15

8 9 10 11 12 13

14 15

GPU 16

8 9 10 11 12 13

14 15

GPU 12

8 9 10 11 12 13

14 15

GPU 13

Second Telecom sub−rack

In case of using GB over IP for one BSS, the GPUs attached to this BSS cannot use the Gb link as synchronizing.

There are the following alternatives for the MFS synchronization:

autonomous mode, using:

TC links if there are mixed AterMux

9130 BSC Evolution links

3BK 21232 AAAA TQZZA Ed.05 47 / 84

2 Hardware

centralized mode, when the BSS GPUs receive the synchronization from theGPU corresponding to other BSSs.

In case the MFS “single secured Gb” feature is used, the GPU synchronisationin autonomous mode can be used through the BSC links or through the TC linksif the Gb and the synchronisation from the TC do not share the same Atermux.

48 / 84 3BK 21232 AAAA TQZZA Ed.05

2 Hardware

2.3.2 Server Subrack for MFSRACK

The physical locations of the server modules are shown in the figure below.

300PS

300WPower Unit

Local

Disks

Local

Disks

CD

ROMs

FTRAY

Server A

CPUB+

PCIBF

CPUB+

PCIBF

SDBOX

ControlPanel

FTRAY

90WPower Unit

90PS LEDs

SharedDisks9GBD

Server B

SharedDisks9GBD

300PS

The subrack contains two AS800 systems and two disk systems connectedin a redundant configuration. Both servers are interconnected by the UltraSCSI busses. The online server is responsible for the overall management ofthe 9135 MFS.

The figure below shows the server device busses.

Server A Server BMain

Shared Disks

Mirrored Shared Disks

SE SCSI Local Bus

SE SCSI Local Bus

Optional Disk or Tape

Optional Disk or Tape

CD ROM CD ROM

Ultra SCSI

OS Disk OS Disk

Each server has a local device bus for the OS disk, the CD-ROM and anoptional disk or tape unit.

Two busses are provided for the shared disks. The shared disk module locatednext to Server A contains the main shared disks. The mirrored disks are locatedin the shared disk module located next to Server B.

3BK 21232 AAAA TQZZA Ed.05 49 / 84

2 Hardware

2.3.2.1 ModulesThe following modules are present:

AS800 Server

The AS800 server module consists of:

CPUBThis is a UNIX(TM) processor which runs the Digital(TM) UNIX(TM) OSand the telecommunications application software. For more information,refer to Software (Section 3) .

300PSThis is an internal 300 W power unit which provides +3.3V, +5V, +12V,-5V and -12V.

PCIBF.This is an internal fan unit.

Local Disk ModuleThe local disk module contains a LED panel and two slots for the OS diskand an optional disk or tape unit. The local disk module receives its DCsupplies from the 300 W server module power unit.

Shared Disk ModuleThe shared disk module (SDBOX) contains a LED panel and three slots forthe two shared disks (9GBD) and a 90 W power unit (90PS). The shareddisk module, the fan unit below and the CD-ROM above, receive their DCsupplies from the 90 W power unit.

CD-ROM ModuleCD-ROM module. This is a two-slot module which contains two CD-ROMdrives. Each CD-ROM drive is dedicated to one server.

Main Fan TrayEach fan unit (FTRAY) contains two fans and provides ventilation for themodules above it. Air is drawn in from below the subrack and expelledfrom the top of the subrack.

50 / 84 3BK 21232 AAAA TQZZA Ed.05

2 Hardware

2.3.2.2 AS800 Server Subrack O&MThe server subrack equipment provides alarms, visual fault indicators andreset buttons.

Server 1. The server gathers and reports all 9135 MFS alarms to the OMC-R and theIMT.The alarms are the standard types:

Quality of Service

Communications

Processing error

Equipment

Environment.

The front control panel of the server module has three push-buttons:

Right buttonPower on/off

Middle buttonEnter console mode and stop server

Left button.Reset server

The server front panel has two LEDs which are mounted horizontally. TheseLEDs are described in the table below.

Left LED(Yellow)

Right LED(Green) Description

Off Off Powered off at control panel or no DC input power.

On Off Powered on at control panel, but switched off by either:

Console command

Software

Fan failure

Over-temperature

Power supply failure.

Off On Powered on at control panel and normal operation.

On On Halt button pressed on front panel or halt command received from console.

3BK 21232 AAAA TQZZA Ed.05 51 / 84

2 Hardware

Local Disk LEDs 2. The local disk module has four green LEDs which are mounted vertically.

The LEDs are described in the table below, where the upper LED isidentified as ’1’ and the lower LED as ’4’ .

LED Description

1 Disk 0 (left disk) active

2 Disk 1 (right disk) active

3 +5V present

4 +12V present

Shared Disk LEDs 3. The shared disk has eight LEDs which are mounted vertically.

The LEDs are described in the table below, where the upper LED isidentified as ’1’ and the lower LED as ’8’ .

LED Description

1 (Green) Disk 0 (left disk) active.

2 (Green) Disk 1 (right disk) active.

3 (Green) User 0 - user-defined LED controlled by software.

4 (Green) User 1 - user-defined LED controlled by software.

5 (Green) +5V and +12V present.

6 (Yellow) Fan Fail 0 - rear fan in fan tray failed.

7 (Yellow) Fan Fail 1 - front fan in fan tray failed.

8 (Yellow) Temperature above +50;C.

CD-ROM Drive 4. The CD-ROM drive contains an ejector button and a green LED whichilluminates when the unit is active.

90 W Power Unit 5. The 90 W power unit contains a green LED which illuminates when thereare no power faults.

52 / 84 3BK 21232 AAAA TQZZA Ed.05

2 Hardware

2.3.3 Server Subrack for MFSDS10

This section describes the DS10 server subrack.

There are two types of MFS equipped with DS10:

9135 MFS with DS10/RC23 (one disk DS10 stations)

9135 MFS with DS10/RC40 (two disks DS10 stations)

The subrack is composed of two 19" mechanics, one vertical and onehorizontal, as shown in the figure below.

For MFS with DS10/RC23, one frame contains two DS10 processor boxes,two StorageWorks boxes and a terminal server (IOLAN). The second one hasup to four hubs/switches.

1 2 3 4

StorageWorks A −PVUSM088

DS10A − PSERV59

Terminal Server − TSERV

StorageWorks B −PVUSM088

DS10B − PSERV59

19" 19"

3.5U

3.5U

3U

3U

1U

HUB/SWITC H

HUB/SWITC H

HUB/SWITC H

HUB/SWITC H

3BK 21232 AAAA TQZZA Ed.05 53 / 84

2 Hardware

For MFS with DS10/RC40, one frame contains two DS10 processor boxes anda terminal server (IOLAN). The second one has up to four switches.

1 2 3 4


19" 19"

3U

3U

1U

SWITC H

SWITC H

SWITC H

SWITC H

Server A (DS10/RC40)

Server B(DS10/RC40)

54 / 84 3BK 21232 AAAA TQZZA Ed.05

2 Hardware

2.3.3.1 ModulesThe server subrack contains the following modules:

DS10/RC23 Server ModuleThe DS10/RC23 server module runs the Digital(TM) UNIX(TM) 4.0F OS andthe telecommunications application software. For more information, referto Software (Section 3) .

DS10/RC40 Server ModuleThe DS10/RC40 server module runs the Digital(TM) UNIX(TM) 5.1A OS andthe telecommunications application software. For more information, referto Software (Section 3) .

StorageWorks Module

Note: The StorageWorks module is present only in DS10/RC23, not in DS10/RC40.

The StorageWorks module (PVUSM088) is shown in the figure below.It consists of:

PVDD42, which is the shared disk

PVDAT01, which is a DAT tape drive

PSU, which provides an 180 W power supply.

Position of Shared DiskThe shared disk must always be in the right slot of each of the StorageWorksmodules.

Hub/Switch ModuleDepending on the configuration, two or four Ethernet hubs (HUB500) orswitches (SuperStack(TM) 10/100, Alcatel-Lucent OmniStack LS 6224) areequipped. For more information, refer to Hub/Switch Subrack (Section2.3.4) .

Terminal Server ModuleThe terminal server module (TSERV) is described in Hub/Switch Subrack(Section 2.3.4) .

3BK 21232 AAAA TQZZA Ed.05 55 / 84

2 Hardware

2.3.3.2 DS10 Server Subrack O&MThe server subrack equipment provides alarms, visual fault indicators andreset buttons.

These are described for:

DS10 server (both DS10/RC23 and DS10/RC40) front panel

The front panel is located in the lower right corner of the server andcontains from left to right:

HALT button, to put the DS10 in halt mode

Five LEDs, described in the table below. The left LED is identified as ’1’, the right LED as ’5’ .

LED Description

1 (Amber) Environment:

On indicates temperature or fan LED is on.

Flashes when operating system generates an alert.

2 (Amber) Temperature:

On indicates that the internal temperature exceedsoperating conditions. The system shuts down after 30seconds.

3 (Amber) Fan:

On indicates that at least one of the three fans in thesystem has failed. The system shuts down after 30seconds.

4 (Green) Disk activity:

Flashes when internal system disks are accessed.

5 (Green) Power

On when power is present in the system.

Power button, to start/stop the system.

56 / 84 3BK 21232 AAAA TQZZA Ed.05

2 Hardware

DS10 server (both DS10/RC23 and DS10/RC40) LEDs

Three Ethernet ports are required:

Two for the connection to the Ethernet hubs/switchesThere are two sets of two Ethernet LEDs, located in the lower right corneron the back of the system. These LEDs are described in the table below.

LED Description

Upper LED(Green)

Link:

On indicates Ethernet connection.

Lower LED(Green oramber)

Speed:

Green for Ethernet speed of 100 Mbit/s

Amber for Ethernet speed of 10 Mbit/s.

Activity:

Flashes with Ethernet activity.

One for the OMC-R connection.There are two LEDs on the connector of the DE504 quad Ethernetboard located at the back of the DS10. These LEDs are described inthe table below.

LED Description

Left LED Speed:

100 Mbit/s

Center LED Activity:

Flashes with Ethernet activity.

Right LED Link:

On indicates Ethernet connection.

3BK 21232 AAAA TQZZA Ed.05 57 / 84

2 Hardware

StorageWorks Power Supply LEDs

Note: StorageWorks is only present in DS10/RC23, not in DS10/RC40.Each power supply unit has two LEDs that display the status of the powersupply and the blower. These LEDs are described in the table below.

Upper LED(Green)

Lower LED(Green) Description

On On Normal operation

Off On Description:

Power supply is OK

One or more blowers failed.

Off Off One of the following conditions exists:

There is no AC power

Power supply failure.

58 / 84 3BK 21232 AAAA TQZZA Ed.05

2 Hardware

StorageWorks Shared Disk LEDsEach shared disk unit has two LEDs. The upper one is the device activityLED, and the lower one the fault indication LED. These LEDs are describedin the table below.

Upper LED(Green)

Lower LED(Amber) Description

On Off Normal operation

Off Off Normal operation

Flashing Off Normal operation

On On The shared disk is not responding to controlsignals.

On Flashing One of the following conditions exists:

The disk is active and spinning down due toa fault

The controller has issued the locate

command. This is not a fault condition.

Off Flashing One of the following conditions exists:

Due to a fault condition, the controller isspinning down the disk

The controller has issued the locate

command. This is not a fault condition.

Off On The disk is inactive and spun down.

Data CorruptionDo not remove the shared disk when the upper LED is on or flashing. Thiscan cause corruption or loss of data.

3BK 21232 AAAA TQZZA Ed.05 59 / 84

2 Hardware

2.3.4 Hub/Switch Subrack

This section describes the hub/switch subrack used in the MFSRACK.

The physical locations of the Ethernet modules and power unit PBAs (forAS800) are shown in the figure below.

Air Intake

Em

pty

JAHPS+BE35B2

JAHPS+BE35B2

Ethernet Hub B2 − HUB500/Switch

Ethernet Hub A2 − HUB500/Switch

Ethernet Hub B1 − HUB500/Switch

Ethernet Hub A1 − HUB500/Switch


For AS800, the subrack contains power unit PBAs located on the right-handside, and Ethernet modules on the left-hand side. Above the modules is anempty space which acts as the air intake for the server subrack.

For AS800, the BE35B2 PBAs are at the front of the subrack and the JAHPSPBAs are at the rear.

2.3.4.1 Modules/PBAsThe hub subrack contains the:

Ethernet HubsEach Ethernet hub is a 3Com(TM) SuperStack(TM) II Dual Speed Hub 500module. The modules have 24 ports which operate at 100 Mbit/s.If the 9135 MFS is a Standard configuration (up to 11 GPUs and aredundant GPU), only the A1 and B1 hub modules are fitted. Whenextending the Standard configuration, two additional hub modules must befitted. Additional cabling is required to link Hub A1 to A2 and Hub B1 to B2.

Ethernet Switches

Note: Ethernet switches are not allowed for MFS with AS800 configurations.Each Ethernet switch is a 3Com(TM) SuperStack(TM) 3 Baseline 10/100switch module or Alcatel-Lucent OmniStack LS 6224 switch. The moduleshave 24 ports which operate at 100 Mbit/s.If the 9135 MFS is a Standard configuration (up to 11 GPUs and a redundantGPU), only the A1 and B1 switch modules are fitted. When extending theStandard configuration, two additional switch modules must be fitted.Additional cabling is required to link Switch A1 to A2 and Switch B1 to B2.

Terminal serverThe terminal server is a Chase(TM) IOLAN+(TM) module which has eightports. Each port provides Ethernet to RS-232 conversion, and vice versa.The RS-232 connections operate at up to 115.2 Kbit/s.The terminal server uses -48V which is supplied by a cable connected to theJAHPS PBA front panel.

60 / 84 3BK 21232 AAAA TQZZA Ed.05

2 Hardware

Power Unit PBAs 9for AS800)

Note: Power unit PBAs are not present for MFS with DS10 configurations.There are two 200 W DC/DC converters. Each converter consists of oneBE35B2 PBA and its associated JAHPS PBA.Each converter receives both the -48V(A) and -48V(B) input supplies. In theevent of one input supply failing, the other input supply is used.Both converter outputs are coupled together to supply the Ethernet hubs,via the JAHPS PBAs connectors. In the event of one converter failing, theother converter provides sufficient power for the hubs.

The internally produced voltages (used by the Ethernet hubs) are:

5V

3.3V

12V.

The -48V(A) and -48V(B) input supplies also provide power for the terminalserver, via JAHPS PBAs connectors.

2.3.4.2 Hub/switch Subrack O&MThe hub/switch subrack equipment provides alarms and visual fault indicatorsfor the following components:

Ethernet hub/switchThe Ethernet hub/switch front panel LEDs are described in the table below.

LED Description

Power/SelfTest

A two-color LED shows the power-on/self test states:

Green - powered on and normal operation

Green flashing - self test mode

Yellow - self test failed

Yellow flashing - fault on second (cascaded) hub/switch.

Mgnt/Attn Not used.

3BK 21232 AAAA TQZZA Ed.05 61 / 84

2 Hardware

LED Description

Status n Two-color LEDs are provided for each of the 24 connections,where the connection speeds are represented by Green(100 Mbit/s) and Yellow (10 Mbit/s).

The LED states are:

On - link available

Flashing - link disabled or partitioned

Off - no link.

Segment Two-color LEDs are provided for the 10 Mbit/s and 100Mbit/s indicators.

The LED states are:

Green - traffic

Yellow - collision

Off - no traffic.

62 / 84 3BK 21232 AAAA TQZZA Ed.05

2 Hardware

Terminal serverThe terminal server front panel LEDs are described in the table below.

LED Description

POWER Module is switched on.

AUI Not used.

10BASE2 Not used.

10BASE-T The LED states are:

Green - no faults

Yellow - fault.

TXn On or flashing when transmitting traffic on link n.

RXn On or flashing when receiving traffic on link n.

BE35B2.For the BE35B2 alarm, switches and indicator descriptions, refer toTelecommunications Subrack (Section 2.3.1) .

2.4 Rack ConfigurationsThis section describes the MFS rack configurations.

There are two possible rack configurations for each MFS version:

Standard configuration

depending on subrack number:

One telecom subrack with a minimum of two GPU boards (1 active

+ 1 redundant) and a maximum of twelve GPU boards (11 active +1 redundant)

The second telecom subrack is internally pre-cabled but not equipped.

This means that the cables are physically present but not plugged inwhen the board is not equipped.

Standard pre-equipped configuration:Both telecom subracks are equipped and pre-cabled. The maximumcapacity is 32 GPU boards (30 active + 2 redundant).

3BK 21232 AAAA TQZZA Ed.05 63 / 84

2 Hardware

2.4.1 Rack Configurations with AS800 Server

The figures below show the possible configurations for MFSs equipped withAS800 servers:


Standard pre-equipped configuration.

2.4.1.1 Standard Configuration with AS800 Servers

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26

002 009 016 023 029 035 041 047 053 059 065 071 077 083 089 095 101 107 113 119 125 131 137 143 150 157

JBE

TI+

jaet

i

battu

GP

U+j

ae1

GP

U+

bare

dc2

JBE

TI+

jaet

i

battu

BE

35B

2+ba

35b2

BE

35B

2+ba

35b2

BE

35B

2+ba

35b2

BE

35B

2+ba

35b2

BE

35B

2+ba

35b2

BE

35B

2+ba

35b2

SBA−BPSPU

Fan unit

SBA−BPSPUSBA−BPMVP

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26

002 009 016 023 029 035 041 047 053 059 065 071 077 083 089 095 101 107 113 119 125 131 137 143 150 157

SBA−BPSPU SBA−BPSPUSBA−BPMVP

TRU

SERVERS

AS 800

empty space

IOLAN + 8 PORTS

BE

35B

2+ja

hps

SBA−BPSPU

BE

35B

2+ja

hps

SUPERSTACK II HUB 500


64 / 84 3BK 21232 AAAA TQZZA Ed.05

2 Hardware

2.4.1.2 Standard Pre-equipped Configuration with AS800 Servers

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26

002 009 016 023 029 035 041 047 053 059 065 071 077 083 089 095 101 107 113 119 125 131 137 143 150 157

JBE

TI+

jaet

i

battu

GP

U+j

ae1

GP

U+

bare

dc2

GP

U+j

ae1

GP

U+j

ae1

GP

U+j

ae1

GP

U+j

ae1

GP

U+j

ae1

GP

U+j

ae1

GP

U+j

ae1

GP

U+j

ae1

GP

U+j

ae1

GP

U+j

ae1

JBE

TI+

jaet

i

battu

BE

35B

2+ba

35b2

BE

35B

2+ba

35b2

BE

35B

2+ba

35b2

BE

35B

2+ba

35b2

BE

35B

2+ba

35b2

BE

35B

2+ba

35b2

SBA−BPSPU

Fan unit


1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26

002 009 016 023 029 035 041 047 053 059 065 071 077 083 089 095 101 107 113 119 125 131 137 143 150 157

JBE

TI+

jaet

i

battu

GP

U+

bare

dc2

JBE

TI+

jaet

i

battu

SBA−BPSPU

Fan unit


TRU

SERVERS

AS 800

empty space


IOLAN + 8 PORTS

BE

35B

2+ja

hps

SBA−BPSPU

BE

35B

2+ja

hps




BE

35B

2+ba

35b2

BE

35B

2+ba

35b2

BE

35B

2+ba

35b2

BE

35B

2+ba

35b2

BE

35B

2+ba

35b2

BE

35B

2+ba

35b2

3BK 21232 AAAA TQZZA Ed.05 65 / 84

2 Hardware

2.4.2 Rack Configurations with DS10 Server (DS10/RC23 and DS10/RC40)

The figures below show the possible configurations for MFSs equipped withDS10 servers:


Standard pre-equipped configuration.

2.4.2.1 Standard Configuration with DS10 Servers

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26

002 009 016 023 029 035 041 047 053 059 065 071 077 083 089 095 101 107 113 119 125 131 137 143 150 157

JBE

TI+

jaet

i

battu

GP

U+j

ae1

GP

U+

bare

dc2

JBE

TI+

jaet

i

battu

BE

35B

2+ba

35b2

BE

35B

2+ba

35b2

BE

35B

2+ba

35b2

BE

35B

2+ba

35b2

BE

35B

2+ba

35b2

BE

35B

2+ba

35b2

SBA−BPSPU

Fan unit


1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26

002 009 016 023 029 035 041 047 053 059 065 071 077 083 089 095 101 107 113 119 125 131 137 143 150 157

SBA−BPSPU SBA−BPSPUSBA−BPMVP

TRU

StorageWorks*

IOLAN + 8 PORTS

DS10 server

DS10 server

StorageWorks*

HU

B /

SW

ITC

H

HU

B /

SW

ITC

H

(*) StorageWorks is present only for MFS with DS10/RC23, not for MFS with DS10/RC40

66 / 84 3BK 21232 AAAA TQZZA Ed.05

2 Hardware

2.4.2.2 Standard Pre-equipped Configuration with DS10 Servers

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26

002 009 016 023 029 035 041 047 053 059 065 071 077 083 089 095 101 107 113 119 125 131 137 143 150 157

JBE

TI+

jaet

i

battu

GP

U+j

ae1

GP

U+

bare

dc2

GP

U+j

ae1

GP

U+j

ae1

GP

U+j

ae1

GP

U+j

ae1

GP

U+j

ae1

GP

U+j

ae1

GP

U+j

ae1

GP

U+j

ae1

GP

U+j

ae1

GP

U+j

ae1

JBE

TI+

jaet

i

battu

BE

35B

2+ba

35b2

BE

35B

2+ba

35b2

BE

35B

2+ba

35b2

BE

35B

2+ba

35b2

BE

35B

2+ba

35b2

BE

35B

2+ba

35b2

SBA−BPSPU

Fan unit


1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26

002 009 016 023 029 035 041 047 053 059 065 071 077 083 089 095 101 107 113 119 125 131 137 143 150 157

JBE

TI+

jaet

i

battu

GP

U+

bare

dc2

JBE

TI+

jaet

i

battu

SBA−BPSPU

Fan unit


TRU

StorageWorks*

IOLAN + 8 PORTS

DS10 server

DS10 server

StorageWorks*

BE

35B

2+ba

35b2

BE

35B

2+ba

35b2

BE

35B

2+ba

35b2

BE

35B

2+ba

35b2

BE

35B

2+ba

35b2

BE

35B

2+ba

35b2

HU

B /

SW

ITC

H

HU

B /

SW

ITC

H

HU

B /

SW

ITC

H

HU

B /

SW

ITC

H

(*) StorageWorks is present only for MFS with DS10/RC23, not for MFS with DS10/RC40

3BK 21232 AAAA TQZZA Ed.05 67 / 84

2 Hardware

68 / 84 3BK 21232 AAAA TQZZA Ed.05

3 Software

3 Software

This section describes the MFS software.

3BK 21232 AAAA TQZZA Ed.05 69 / 84

3 Software

3.1 OverviewThe software manages MFS telecommunications and O&M. It runs in theservers and on the GPU boards. The figure below shows the main softwarecomponents.

Hardware

Hardware

UNIX OS

PSOS

General Software

NECTAR

MFS Application

Telecom Application

OS Operating SystemPSOS Provable Secure Operating System

Active Server GPU

The active server contains the following software components:

UNIX(TM) operating system

General softwareThis includes tools, utilities and WAN support.

New Control Architecture (NECTAR)This is a middleware platform for IT hardware that enables the hardware tosupport telecommunications applications.

MFS application.This application supervises the MFS and downloads the telecommunicationsapplication to the GPU where the telecom functions are performed.

Each GPU contains the following software components:

Provable Secure Operating System (PSOS)

Telecommunications application

SMLC software.

70 / 84 3BK 21232 AAAA TQZZA Ed.05

3 Software

3.2 O&M Software ArchitectureThe O&M software architecture is shown in the figure below.

Active Server

UNIX

Standby Server

GPU

UNIX PSOS

NECTAR Platform

GPRS NE PlatformGPRS NE Platform

GPRS NE Platform

O&M Application

Telecom Application

NECTAR Drivers

NECTAR Drivers

GPU Drivers

Equipment Manager

Telecom Manager

NECTAR Platform

When a server operates in the standby mode, it does not run the O&Mapplication.

The active server contains the following components:

Digita(TM) UNIX(TM) operating system and NECTAR drivers that managethe Ethernet links

NECTAR platform which provides communications services, data

management, server supervision and process initialization

GPRS network element platform

Functions:

Controls the communications with the GPUs. This function is activeon both servers

Supervises the telecommunications equipment (GPUs, JBETI and

PCM links) and collects all alarms. These functions are not activeon the standby server.

O&M application which manages the telecom objects (Ater Mux Interface,

Cell, Gb Interface). These functions are not active on the standby server.

3BK 21232 AAAA TQZZA Ed.05 71 / 84

3 Software

3.3 Communication ChannelsCommunication between the GPUs and the server takes place as sessionsover five types of channel:

Telecom channels, used for requests, replies and state change notifications

when configuring.

There are the following channels:

Network services (Gb Interface)

Bearer channels (Ater Mux Interface)

BSS and cells (cell management).

GPU network channels, used for network configuration requests and replies

and for network notifications

GPU physical channels, used for GPU hardware component configuration

requests and replies and for hardware notifications

Alarm channels, used for collecting all hardware, network and GPRS alarms

Performance manager channels, used for GPU PM configuration requestsand reports from the GPUs.

Each channel is a Communications Service session established between aPSOS task (in the GPU) and a real-time MFS process, as shown in the figurebelow.

Real−time

Admin

Real−time

Admin

Real−time

Admin

Real−time

Admin

Real−time

Admin

CFG MIB

CFG MIB

Common Management Protocol Syntax (CMPS) Interface

Q3

GOM GEM GHW GAM GPM

Telecom BAM PMSCA

Server

GPU

Agent MFS Process NECTAR Process Communications Service Session

72 / 84 3BK 21232 AAAA TQZZA Ed.05

3 Software

Each real-time process has three main parts:

The administrative layer manages configuration data received over the Q3

Interface or from the IMT

The real-time layer updates object states when a notification is receivedfrom the GPU

Agents to support the process (see Agents (Section 3.4) ).

The real-time processes support data persistency. Configuration data is storedin a table and a backup copy is retained on disk. Resource data is also storedin a table but there is no backup. The resource data table is shared byboth servers.

3BK 21232 AAAA TQZZA Ed.05 73 / 84

3 Software

3.4 AgentsAgents provide support for the real-time MFS processes and the PSOS tasks.Refer to the following table for a description of each agent.

Agent Description

GPRS Operations andMaintenance (GOM)

GOM manages telecom resource configuration and supervision.

It works with the telecom agent on each GPU and is responsible for:

BSS static and online configuration and activation. This includes bearerchannel, Gb Interface, Ater Mux Interface and cell management domains.

Validity checks are performed and persistent data is updated andconfigured on the logical GPUs.

Supervision of the domains for operational states and status. Changes are

notified to the administrative part of the process.

Synchronization of the logical GPU resource states after a server

changeover.

Configuration of a logical GPU when requested by the GPU (after a start,reset or changeover).

Notification to GEM of logical GPU creation and deletion and PCM port

creation.

Global Alarm Manager(GAM)

GAM manages the MFS alarms.

It processes all hardware and telecom alarms and is responsible for:

Collecting all fault information relating to GPUs, the active server andtelecom and external alarms.

Recording alarms in a table.

Allowing the IMT and the Q3 agent to access the alarms.

Generating ending alarms when a fault is cleared (for example, when

a GPU is replaced).

Managing a communication session with the IMT.

74 / 84 3BK 21232 AAAA TQZZA Ed.05

3 Software

Agent Description

GPRS EquipmentManager (GEM)

GEM manages the GPU hardware and low-level software.

It handles all requests in the first steps of GPU initialization and isresponsible for:

GPU software booting.

Session layer configuration.

GPU framer hardware configuration (including data for clock

synchronization) for Gb Interface messages.

GPU switch configuration for Circuit Switched connections.

Logical GPU switch over and recovery.

The administrative part of GEM also handles requests concerning:

GPU, JBETI, cross connection and PCM objects arriving via the Common

Management Protocol Syntax (CMPS) interface.

Static objects created during commissioning.

GPRS PerformanceManager (GPM)

GPM manages the PM domain.

It works with the PM agent and is responsible for:

Configuring the scanners on the logical GPUs.

Collecting the PM counter values.

Generating a file to hold the values.

Processing CPMS requests.

Q3 Q3 manages the Q3 interface to the OMC-R. It is responsible for processingOMC-R requests, detecting faults and supervising the O&M states and status.

Board and Alarm Manager(BAM)

BAM manages the GPU hardware and is responsible for:

Physical configuration. This includes framer and switch configuration and

the change over to the spare GPU.

Supervision of the physical resources (for example, PCM interfaces and

synchronization).

Starting telecom tasks.

Reporting hardware and telecom alarms to GAM.

Providing log, trace and software error services for the logical GPUs.

Telecom Telecom manages telecom functions.

It is also responsible for the following O&M functions:

BSS logical configuration and activation and the supervision of bearer, Ater

Mux Interface and cell management domains.

Network service configuration and the supervision of the Gb Interfacedomain.

3BK 21232 AAAA TQZZA Ed.05 75 / 84

3 Software

Agent Description

PerformanceManagement (PM)

PM manages the scanner configuration and the collection of PM countervalues.

Session ConfigurationAgent (SCA)

SCA manages network configuration and supervision.

76 / 84 3BK 21232 AAAA TQZZA Ed.05

4 Managed Objects and RITs


This section describes the MFS Managed Objects and Replaceable items(RITs).

3BK 21232 AAAA TQZZA Ed.05 77 / 84


4.1 MFS Managed ObjectsThis section provides the following information about MFS Managed Objects:

Class, naming attribute and description

Hierarchy

Allowed States

Supported Operations

4.1.1 MFS Managed Object Class, Naming Attribute and Description

The Managed Object classes for the MFS are listed in the following table, withtheir corresponding naming attributes.

The naming attribute is used to construct the Relative Distinguished Name(RDN) of subordinate objects of this class. An RDN is constructed from:

The object identifier assigned to that attribute type, and

The value of the instance of the attribute.

The table also provides a description of each Managed Object.

Managed Object Class and NamingAttribute Description

aGprs2MbTTP

tTPId

This Managed Object class is a 2 Mb port managingobjects that terminates the transport entities, such as trailsand connections. All attributes are assigned values atcreate time.

aGprsAdjacent CellReselection

adjacentCellId

This Managed Object class focuses on the cell reselectionadjacencies related to GPRS functionality. This object iscreated for each adjacent cell to the containing cell. It isused to broadcast on the Air interface (via master PDCH)the adjacent cells that may support the GPRS functionality(if the adjacent cell (i.e. target cell) does not supportGPRS, the reselection procedure will fail).

aGprsBearerChannel

aGprsBearerChannelId

The Bearer Channel is the Frame Relay Bearer Channel(described in rec. Q.922 annex A and Q.933 annex A). Itrepresents a transport capacity on the Gb interface. It canbe a set of 64 kb time slots (case framed 2Mb-TTP). Thebearer channel supports the PVCs.

aGprsBssFunction

bssFunctionId

Represents a BSS network element. Only the BSS withGPRS capability are seen at the OMC/MFS interface andcan be configured by the operator.

aGprsBts

btsId

Represents the O&M functionality related to a specific cellwithin a BTS equipment.

aGprsFabric

fabricId

Represents the function of managing the establishment andthe release of the cross-connections of 2Mb-TTPs ports.

78 / 84 3BK 21232 AAAA TQZZA Ed.05



aGprsGicGroup

aGprsGicGroupId

A Managed Object from this class represents the set of allGICs pertaining all to the same Ater interface at the BSCside. The GICs have been grouped per Ater because allGICs of the same Ater have the same operational state(depending on the state of the DTC board at the BSC).

aGprsLapdLink

lapdLinkId

This Managed Object is the 64k channel on the MFS-BSCinterface supporting the GSL on a given BSC-MFSinterface. The GSL uses the GPRS LapD links in loadsharing. The GSL is not managed as an object class.

aGprsManaged ElementExtension

aGprsManagedElementExtensionId

This Managed Object class is a class of ManagedObjects that provide additional services related to themanagedElement object class for different domains(Radio, Ater-Gb, etc.). This is necessary becausemanagedElement is a standard Managed Object class andcannot be overloaded.

aGprsMasterChannelData

aGprsMasterChannelDataId

This Managed Object class defines the characteristics(attributes) of the cell that are not required when there is nomaster channel.

aGprsNse

aGprsNseId

The network service element (NSE) is an entity of the NSCtelecom layer of the Gb interface. The NSE ensures theload sharing of the outgoing BSSGP messages over its setof NS-VCs (to the SGSN), and routes the incoming SNSmessages to the required BVCs. The NSE contains a setof NS-VCs and a set of BVCs. The NSE is characterizedby its NSEI, also known by the SGSN.

aGprsNsvc

aGprsNsvcId

The network service virtual connection (NS-VC) is anentity of the network service control (NSC telecom layer onthe Gb interface). It is an end-to-end virtual connectionbetween MFS and SGSN. The NS-VC is identified by itsNS-VCI, also known by the SGSN.

aGprsPdchGroup

aGprsPdchGroupId

This Managed Object class defines the configurationparameters of a group of consecutive channels.

aGprsPowerControl

powerControlId

This Managed Object class supports the cell power controlparameter related to GPRS functionality (one objectinstance per cell).

aGprsPvc

aGprsDIcId

This class represents the frame relay implementation ofpermanent virtual connections.

btsSiteManager

btsSiteManagerId

This Managed Object class represents the O&Mfunctionality for a specific BTS equipment. Its purpose iscontainment (BTS sector or cell instances).

3BK 21232 AAAA TQZZA Ed.05 79 / 84



circuitPack

equipmentId

This Managed Object class is derived from M.3100circuitPack class. It represents boards that are present inTelecom subracks; these are GPU boards. The JBETIboards are not instantiated. This object is created when theGPU board is first plugged in. An objectCreation notificationis the emitted. The board is deleted when it is unplugged.An objectDeletion notification is then emitted.

crossConnection

crossConnectionId

Represents the cross-connection function between two2Mb-TTPs (the ’from termination’ and the ’to termination’ )with a granularity of one time slot (64 kb).

equipmentHolder

equipmentId

It represents the physical resource of a network elementthat is capable of holding other physical resources. It iscreated by NECTAR at initialization using the NECTAR’profile’ configuration file. In particular, this file is used toconfigure the userLabel.

eventForwarding Discriminator

discriminatorId

Represents an Managed Object class that contains adiscriminator construct that specifies the characteristics apotential event report must satisfy in order to be forwarded.

extendedCurrentAlarm SummaryControl

currentAlarmSummaryControlId

Represents an Managed Object class of support objectsthat provide the criteria for generation of current alarmsummary reports.

log (not installed)

logId

This Managed Object class represents a repository thatmay be used for alarm logging.

managedElement

managedElementId

This Managed Object class represents the MFSnetworkelement. Its purpose is containment, allowing theassociations of various functions that make up an instanceof this network element. It is created by NECTAR atinitialization using the NECTAR ’profile’ configuration file.In particular, this file is used to configure the userLabel.

nectarCircuitPack

equipmentId

This class is derived from M.3100 circuitPack class. It iscreated by NECTAR at initialization using the NECTAR’profile’ configuration file. In particular, this file is used toconfigure the userLabel.

nectarFRU

equipmentId

This Managed Object class represents the FRUsof the platform such as CPUBox, localDiskDrive,sharedDiskDrive, CDROMDrive, TapeDrive,localPowerSupply, sharedPowerSupply, sharedFanTray,localDiscBox, sharedDiskBox, LSNHub/Switch,LANIOHub/Switch, concentrator, X.25router, etc.

aGprsSgsnIpEndPoint An endpoint defined by its IP address and UDP port. AnIP endpoint can be a data endpoint and/or a signallingendpoint.

80 / 84 3BK 21232 AAAA TQZZA Ed.05


4.1.2 MFS Managed Object Hierarchy

The hierarchy of MFS Managed Objects is shown in the following figure.

This tree contains a graphical representation of the naming hierarchy of theindicated Managed Objects.

managed Element*(M3100)

event Forwarding Discriminator extendedCurrentAlarmSummaryControl

aGprsManagedElementExtension

aGprs2MbTTP aGprsNse aGprsBssFunctionequipmentHolder(rack)

aGprsBearerChannel aGprsNsvc btsSiteManagercrossConnection *

(M3100) aGprsLapdLink

aGprsPvc aGprsBtsaGprsGicGroup

aGprsMasterChannelData aGprsPowerControl aGprsPdchGroup

Circuit Pack

aGprsAdjacentCellReselection

aGprsFabric

aGprsSgsnIpEndPoint

equipmentHolder(shelf)

NectarCircuit Pack

NectarCircuitPack

NectarCircuitPack

equipmentHolder(ASPack)

Nectar FRU

Nectar FRU

equipmentHolder(ITPack)

3BK 21232 AAAA TQZZA Ed.05 81 / 84


4.1.3 MFS Managed Object Allowed States

The allowed states of MFS Managed Objects are indicated in the following table.

Managed ObjectClass

AdministrativeState

OperationalState

AvailabilityStatus

aGprs2MbTTP Locked/unlocked Enabled/disabled Not installed/failed/(empty)

aGprsAdjacentCellReselection - - -

aGprsBearerChannel - Enabled/disabled Not installed/failed/(empty)

aGprsBssFunction Locked/unlocked Enabled/disabled Not installed/failed/(empty)

aGprsBts Locked/unlocked Enabled/disabled Not installed/failed/(empty)

aGprsFabric - - -

aGprsGicGroup Locked/unlocked Enabled/disabled -

aGprsLapdLink Locked/unlocked Enabled/disabled Not installed/failed/(empty)


- - -

aGprsMasterChannelData - - -

aGprsNse - - -

aGprsNsvc Locked/unlocked Enabled/disabled Not installed/failed/off duty/intest/ dependency/(empty)

aGprsPdchGroup - - -

aGprsPowerControl - - -

aGprsPvc - Enabled/disabled Not installed/failed/(empty)

btsSiteManager - - -

circuitPack Locked/unlocked Enabled/disabled Failed/in test/(empty)

crossConnection Unlocked Enabled -

equipmentHolder - - -

eventForwardingDiscriminator Locked/unlocked Enabled/disabled -

extendedCurrentAlarmSummaryControl

- - -

log Locked/unlocked Enabled/disabled Not installed/failed/(empty)

managedElement Unlocked Enabled -

nectarCircuitPack Locked/unlocked Enabled/disabled Not installed/failed/(empty)

nectarFRU Locked/unlocked Enabled/disabled -

aGprsSgsnIpEndPoint Locked/unlocked Enabled/disabled Not installed/failed/off duty/intest/ dependency/(empty)

82 / 84 3BK 21232 AAAA TQZZA Ed.05


4.1.4 MFS Managed Object Supported Operations

The supported operations of MFS Managed Objects are indicated by acheckmark (X) in the following table.

Managed Object Class Supported Operations

Set Get Create Delete Lock Unlock Connect Disconnect

aGprs2MbTTP X X X X X X - -

aGprsAdjacentCellReselection

X X X X - - - -

aGprsBearerChannel X X X X - - - -

aGprsBssFunction X X X X - - - -

aGprsBts X X X X - - - -

aGprsFabric - X - - - - X X

aGprsGicGroup - X X X - - - -

aGprsLapdLink X X X X X X - -


- X X(*) X(*) - - - -

aGprsMasterChannelData

X X X X - - - -

aGprsNse X X X X - - - -

aGprsNsvc X X X X X X - -

aGprsPdchGroup X X X X(**) - - - -

aGprsPowerControl X X X X(**) - - - -

aGprsPvc X X X X - - - -

btsSiteManager X X X X - - - -

circuitPack X X - - - - - -

crossConnection - X - - - - - -

equipmentHolder - X X(*) X(*) - - - -

eventForwardingDiscriminator

X X X X - - - -

extendedCurrentAlarmSummaryControl

X X - - - - - -

log X X X X - - - -

managedElement X X X(*) X(*) - - - -

nectarCircuitPack X X X(*) X(*) - - - -

3BK 21232 AAAA TQZZA Ed.05 83 / 84


Managed Object Class Supported Operations

Set Get Create Delete Lock Unlock Connect Disconnect

nectarFRU - X X X - - - -

aGprsSgsnIpEndPoint X X X X X X - -

(*) Created at initialization time; after initialization. Create and Delete are not explicitly supported.

(**) Deleted only through cell deletion.

4.2 MFS RITsThe RITs in the MFS are listed in the following table.

RIT Remarks

GPU GPRS Processing Unit: hot insertion/extraction, plugand play (without declaration at the local terminal)

JBETI Ethernet to ISL gateway board: hotinsertion/extraction, plug and play (withoutdeclaration at the local terminal)

Fan Unit -

Pilot Station -

LSN Ethernet Hub / Switch (*) Local Sub-network Ethernet Hub / Switch

Router (X.25) (*) -

Terminal concentrator (*) -

Shared disk -

Rack/Subrack including CONV boards and FAN (*) -

BAREDC Redundancy applique

BATTU Applique giving access to Ethernet ports of theJBGPU boards

JAE1 E1 access applique with redundancy facilities

JAETI Access ports applique to the JBETI board

BA35B2 Power supply applique

(*) No action available for these units; only events and alarms are reported.

84 / 84 3BK 21232 AAAA TQZZA Ed.05

9135

Documents