tedebsc

GERAN

Technical Description

Base Station System

TED:eBSC

A50016-G5100-A020-01-7618

2 A50016-G5100-A020-01-7618

TED:eBSC

Id:0900d8058008a487

f Important Notice on Product Safety

DANGER - RISK OF ELECTRICAL SHOCK OR DEATH - FOLLOW ALL INSTALLATION INSTRUCTIONS.

The system complies with the standard EN 60950 / IEC 60950. All equipment connected to the system must comply with the applicable safety standards.Hazardous voltages are present at the AC power supply lines in this electrical equipment. Some components may also have high operating temperatures.Failure to observe and follow all installation and safety instructions can result in serious personal injury or property damage.Therefore, only trained and qualified personnel may install and maintain the system.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

LEBENSGEFAHR - BEACHTEN SIE ALLE INSTALLATIONSHINWEISE.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Alle an das System angeschlossenen Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.In diesen Anlagen stehen die Netzversorgungsleitungen unter gefährlicher Spannung. Einige Komponenten können auch eine hohe Betriebstemperatur aufweisen.Nichtbeachtung der Installations- und Sicherheitshinweise kann zu schweren Körperverletzungen oder Sachschäden führen.Deshalb darf nur geschultes und qualifiziertes Personal das System installieren und warten.

Caution:

This equipment has been tested and found to comply with EN 301489. Its class of conformity is defined in table A30808-X3247-X910-*-7618, which is shipped with each product. This class also corresponds to the limits for a Class A digital device, pursuant to part 15 of the FCC Rules.These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment.This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accor-dance with the relevant standards referenced in the manual “Guide to Documentation”, may cause harmful inter-ference to radio communications.For system installations it is strictly required to choose all installation sites according to national and local require-ments concerning construction rules and static load capacities of buildings and roofs.For all sites, in particular in residential areas it is mandatory to observe all respectively applicable electromagnetic field / force (EMF) limits. Otherwise harmful personal interference is possible.

Trademarks:

All designations used in this document can be trademarks, the use of which by third parties for their own purposes could violate the rights of their owners.

Copyright (C) Siemens AG 2006

Issued by the Communications GroupHofmannstraße 51D-81359 München

Technical modifications possible.Technical specifications and features are binding only insofar as they are specifically and expressly agreed upon in a written contract.

Copyright (C) Siemens AG 2006

Issued by the Communications GroupHofmannstraße 51D-81359 München

Technical modifications possible.Technical specifications and features are binding only insofar as they are specifically and expressly agreed upon in a written contract.

A50016-G5100-A020-01-7618

3

TED:eBSC

Id:0900d8058008a487

Table of ContentsThis document has 50 pages.

Reason for Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1 Structure of the Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.1 BSS Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.2 eBSC Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.3 eBSC Main Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.4 Traffic Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.4.1 Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2 eBSC HW Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.1 Introdution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.2 eBSC Hardware Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.2.1 Rack Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.2.1.1 Upper Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.2.1.2 Lower Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.2.1.3 DC Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.2.2 Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242.2.3 Basic Configurations and System Expansion . . . . . . . . . . . . . . . . . . . . . . . 242.2.4 Alarm Reporting Functional Split . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.2.5 eBSC Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272.2.6 eBSC Rack Power Consumption and Physical Characteristic . . . . . . . . . . 27

3 Module Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.1 E1/T1 Line Module (LIET and IOLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.2 Main Control Processor (MCP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.3 User Plane Module (UPM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.4 Application Processor (AP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.5 STM1 Line Module (LISO Blade) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.6 Switching Matrix (SMAC and eIOSM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.7 Shelf Manager Module (ShMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363.8 Shelf Alarm Panel (SAP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383.9 Alarm Collector and Fan Control (ACFC) . . . . . . . . . . . . . . . . . . . . . . . . . . 383.10 Power Entry Module (PEM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393.11 Power Supply (DC Panel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.12 Lamp Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

4 eBSC Software Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434.1 Flexible PCM Lines Configuration (Asub) . . . . . . . . . . . . . . . . . . . . . . . . . . 46

5 Environmental Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485.1 Storage and Transportation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485.2 Stationary Use Indoor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485.3 Electromagnetic Compatibility (EMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495.3.1 Emission Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495.3.2 Immunity Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

4 A50016-G5100-A020-01-7618

TED:eBSC

Id:0900d8058008a487

6 Product safety and EMF Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506.1 Product Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506.2 Power Supply Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

A50016-G5100-A020-01-7618

5

TED:eBSC

Id:0900d8058008a487

List of FiguresFigure 1 BSS Network Architecture and External Components. . . . . . . . . . . . . . 10Figure 2 LMT Evolution within the SBS System. . . . . . . . . . . . . . . . . . . . . . . . . . 12Figure 3 eBSC and BSS System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Figure 4 Supported Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Figure 5 eBSC aTCA Shelf Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Figure 6 eBSC Functional Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Figure 7 eBSC Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Figure 8 eBSC Upper Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Figure 9 eBSC Lower Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Figure 10 LIET / IOLI Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Figure 11 MPC Block Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Figure 12 UPM and Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Figure 13 LM-STM1/OC3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Figure 14 SMAC Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Figure 15 Shelf Manager Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Figure 16 SAP Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Figure 17 Power Distribution Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Figure 18 Lamp Panel Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Figure 19 eBSC Software Physical Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Figure 20 PCM Lines Configuration in Selection and Transparent Mode . . . . . . . 47

6 A50016-G5100-A020-01-7618

TED:eBSC

Id:0900d8058008a487

List of TablesTable 1 Summary of eBSC capacity figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Table 2 Cardinality and Redundancy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Table 3 Physical Characteristics of the eBSC . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Table 4 Storage and Trasportation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Table 5 Environmental Requirements for Stationary Use Indoor. . . . . . . . . . . . . 48Table 6 Product Safety Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Table 7 Power Supply Interface Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 50

A50016-G5100-A020-01-7618

7

TED:eBSC Reason for Update

Id:0900d805800ec1d9

Reason for UpdateIssue History

Issue 1 for Release BR9.0 (12/2006)

Issue Date Summary

01 12/2006 New release BR9.0

8 A50016-G5100-A020-01-7618

TED:eBSC

Id:0900d805800ec1d9

Reason for Update

A50016-G5100-A020-01-7618

9

TED:eBSC Structure of the Manual

Id:0900d805800e7119

1 Structure of the ManualThis manual describes the features provided in the HW/SW architecture at the eBSC and it is organized as follows:

Chapter 1: Introduction

This chapter explains the purpose of this manual, its organization and how the user can use it. Besides it introduces the Network Elements (BSC1 and eBSC, BTS, TRAU) of the BSS system together with the LMT Evolution, their main characteristics and func-tions.

Chapter 2: eBSC Architecture

Main purpose of this chapter is to give an overview of eBSC Architecture. Besides it describes the open hardware platform advanced Telecomunication Computing Archi-tecture (aTCA).

Chapter 3: Module Descripition

In this chapter each eBSC blade with its main functions is described; for each blade it is given a short introduction to its main characteristics. The Hardware Design Specification describes the hardware functionalities and the implementation of the WARP (tWin AMC caRrier Processor).

Chapter 4: eBSC Software Architecture

This chapter describes the software physical allocation on each related blade; the logical software architecture is subdivided into Functional Areas and Subsystems.

Chapter 5: Environmental Requirements

This chapter provides in table form Storage, Transportation, Stationary Use Indoor and Outdoor, Electromagnetic Compatibility, Emission and Immunity Requirements to which BSS system shall be aligned.

Chapter 6: Product Safety and EMF Protection

This chapter provides in table form Product Safety and EMF Protection and Power Supply Interface Requirements.

1.1 BSS OverviewThe BSS network architecture is represented in next Figure 1. The system includes the following main components: a) Base Transceiver Station Equipment (BTSE);b) Base Station Controller (BSC1);c) Transcoding and Rate Adaptation Unit (TRAU);d) Local Maintenance Terminal Evolution (LMT).

The following network elements always represented in Figure 1 are not part of the BSS system but interact with it to provide services in the GSM mobile network:a) MSC;b) Radio Commander;c) GGSN, SGSN nodes;d) SMLC and GMLC to support and manage the Location Services (for more details

see the manual: “TED:SMLC”).

The main characteristics and functions of each BSS component are described below:

10 A50016-G5100-A020-01-7618

TED:eBSC

Id:0900d805800e7119

Structure of the Manual

Base Transceiver Station Equipment (BTSE):

The BTSE comprises the entire radio network equipment installed in a site for a single cell or a group of cells, each of which (a BTS) is characterized by its own Base Station Identification Code (BSIC). In case of sector cells, each cell refers to its own BTS, although all BTSs are physically grouped together in the same site (BTSE). The BTSE provides functions such as speech and channel encoding/decoding, transmission and reception, etc.

Base Station Controller (BSC1 - eBSC):

The BSC1 is the main component of the BSS system and it provides the interfaces to the BTS and TRAU Network Elements and to the Radio Commander for O&M functions. All the main components of the BSC1 are duplicated in order to provide a fault-tolerant mechanism. The BSC1 administers the radio resources, it maps the radio channels to terrestrial channels and it supports handover procedures between the connected cells.

In current BR 9.0 Release both BSC1 and eBSC are inserted.

Transcoding and Rate Adaptation Unit (TRAU):

For each traffic channel the TRAU adapts the different transmission rates for speech and data calls on the radio side to the PCM 64 kbit/s transmission rate on the MSC side. It also performs transcoding functions between the different speech coding algorithms used on the radio interface (full rate, half rate, enhanced full rate) and the interface (PCMA or μ law G.711) used within the terrestrial network.

Local Maintenance Terminal Evolution (LMT Evolution):

The LMT Evolutional application is installed on a portable terminal, for example a laptop computer used for local or remote operation and maintenance functions of the con-nected Network Element. The same application is used for the maintenance of all BSS Network Elements.

Figure 1 BSS Network Architecture and External Components

A50016-G5100-A020-01-7618

11


Id:0900d805800e7119

The Local Maintenance Terminal Evolution (LMT Evolution) is the O&M system interfa-cing its users from one side and the connected network element (eBSC, BTSE, TRAU) from the other side for Operation & Maintenance tasks.

The purpose of the LMT Evolution is to support the Operation and Maintenance activities in a very efficient and user friendly way and to provide all the possible informations about the condition of a specific Network Element running in field with particular attention to eventual faults or anomalous situations.

The LMT Evolution can be connected to the Network Element BSC1 (BSC/72, BSC/120), eBSC ,TRAU and to all BTS types. The connection is realized by the T inter-face.

The T interface is based on X.21 + V.11 (physical layer) and on the HDLC + LAPB pro-tocols.

In the next Figure 2 it is represented the position of the LMT Evolution within the BSS system:

AC Authentication Center LMT Local Maintenance Terminal Evolution

eBSC Base Station Controller

BSS Base Station Subsystem LR Location Register

BTS Base Transceiver Station MS Mobile Station

CCU Channel Codec Unit RC Radio Commander

CBC Cell Broadcast Centre MSC Mobile service Switching Center

EIR Equipment Identity Register PCU Packet Control Unit

GGSN Gateway GPRS Support Node SGSN Serving GPRS Support Node

GMLC Gateway Mobile Location Center SMLC Serving Mobile Location Center

GR GPRS Register TRAU Transcoding and Rate Adaption Unit

HLR Home Location Register VRL Visitor Location Register

12 A50016-G5100-A020-01-7618

TED:eBSC

Id:0900d805800e7119


Figure 2 LMT Evolution within the SBS System

The LMT Evolution can be interconnected to a Network Element in three different ways:

– Local Mode: in this case the LMT Evolution is physically connected (through the T-interface) to the Network Element on which the user is working.

– Remote Mode: In this case the LMT Evolution is physically connected to a BTSE or a TRAU through the T-interface and a new connection to the related BSC1 is acti-vated by the user (for example the LMT Evolution is physically connected to a BTSE, and via the Abis interface the user is able to work in the remote modality with eBSC).

– Interworking Mode: In this case the LMT Evolution is physically connected to a eBSC through the T-interface and a new connection to a BTSE or to a TRAU con-nected to that eBSC is activated by the user.

1.2 eBSC OvervieweBSC is a new commercial SBS product aiming at providing the same features sup-ported by the current BSC1; on top of more performing HW and SW complexes, which enable the provision of enhanced capacity figures.

This new product provides as a stand-alone system which is functionally equivalent to BSC1, with higher capacity and SW commonality with BSC1. Both products (BSC1 and eBSC) support the same release.

After introducing eBSC, new releases will be available on both versions until BSC1 obsolescence. The eBSC is the last step of a High Capacity BSC1 strategy started with the provision of BSC/72 in BR6.0.

With BSC/120, the BSC1 product has met its architectural limits, which define the capacity figures it can fulfill. Several limiting factors, including power supply, thermal dis-sipation, switching matrix and centralized (non-scalable, single processor) call process-ing architecture, do not allow to increase capacity.

The eBSC system allows to overcome the above mentioned limitations. The availability of a scalable call processing architecture allows to tailor the configuration of the BSC1

A50016-G5100-A020-01-7618

13


Id:0900d805800e7119

to customers’ needs which vary with the addressed market. This will allow for a more rational network planning and for a smooth adaptation to variations in traffic demand over space and time.

Large connectivity, combined with a powerful Packet Handling subsystem capable of around 3 times the throughput that BSC1 provides, helps in accommodating the increas-ing demand of data services in the current GSM network.

The adoption of highly performing eBSC solution allows to significantly reduce the floor space/BSC1.The eBSC provides additional capacity and specific functionality (e.g. STM1/OC3 interface).

Hereafter the main Customer improvement are summarized:

• CAPital EXpenditure savings:

– Lower network nodes are necessary due to higher capacity BSC1;

– Processing scalability allows high capacity configuration even with heavy traffic models – PAY AS you GROW concept;

• OPeration Expenditure savings:

– High speed interfaces (STM1/OC3) allow a dramatic reduction of transport expenses with respect to E1/T1 leased lines;

– The adoption of a “wall mounting” equipment practise (cabling is completely acces-sible on the front of the rack), in combination with the high capacity per single cabinet, results in reduced expenses for site rental, Installation & Commissioning, Operation & Maintenance, power consumption.

1.3 eBSC Main FeaturesThe enhanced Base Station Controller (eBSC) is a Network Element of the BSS system and is supervised by the Local Maintenance Terminal Evolution (LMT Evolution) and by the Network Management System for operation and maintenance activities.

The position of the eBSC within the SBS system is represented in Figure 3.

Figure 3 eBSC and BSS System

The Base Station Controller (eBSC) is the central component in BSS system and acts as a concentrator for the links between Abis, Asub, and Gb interfaces; eBSC supports a variety of configurations on Abis interface. The Transcoder and Rate Adaptation Unit

14 A50016-G5100-A020-01-7618

TED:eBSC

Id:0900d805800e7119


(TRAU) interacts with the eBSC to handle and to route information. The Local Mainte-nance Terminal Evolution (LMT) is a portable terminal, e.g. a laptop computer used for local or remote operation and maintenance functions.

The Configuration and the eBSC features are based on Recommendations of the GSM Technical Committee of the European Telecommunication Standards Institute (ETSI) and the Technical Sub-Committee T1P1 of the American National Standards Institute (ANSI), especially, the "Phase 2" series of recommendations for GSM 850, GSM 900, GSM1800 and GSM1900 systems.

Abis interface supports various configuration types (star, multidrop, and loop) in relation also with various types of transmission media (for example: microwave, PCM30, PCM24, satellite links).

Following the 2n redundancy concept implemented for the central eBSC components as well as the n + 1 redundancy concept implemented for all line interfaces, an high level of fault tolerance is supported. A sophisticated redundancy concept is applied that ensures that hardware faults have no impact on active calls. An easy system upgrade is provided via software download procedures that are able to handle simultaneously dif-ferent software versions. In addition, for the reason that capacities are queued onto priority levels, either line interfaces or BTS (s) can be added without any traffic interrup-tion whatsoever.

Supported interfaces (Um, Abis, Asub, Gb, etc.) are represented in the Figure 4.

Figure 4 Supported Interfaces

eBSC is compatible to the Phase 2+ series of recommendations valid for GSM850, GSM900, GSM1800, and GSM1900 systems. eBSC does not require raised floors for installation. Consequently, an operator can choose to use eBSC either centrally, for example installed in a standard telecommunication office room, or remotely, in a shel-ter’s confined space. Installation times are also kept as short as possible. Embedded 16 or 64 kbps signaling channels are provided for LAPD protocols between eBSC and BTS elements and seeing that only one channel (a single LMT Evolution can be applied to all Network Elements) is required per BTS site. This platform with its Packet Control Unit (PCU) offers optimal flexibility to support and EGPRS /GPRS services.

Main eBSC features are the following:

A50016-G5100-A020-01-7618

15


Id:0900d805800e7119

• Support of Asub interface towards the remote TRAU, with 16 kbit/s submultiplexing; • Support of Abis interface towards the BTSE, with 16 and 8 kbit/s submultiplexing; • Support of different transmission media (optical fibre, coaxial cable, symmetrical

pairs) of both PCM30 and PCM24 type; • Support of STM1/OC3 interfaces for Gb traffic to/from the PS core network. Classi-

cal IP over ATM is adopted. In addition, STM1/OC3 can be also adopted on Abis and Asub interfaces (and also for X.25 64 Kbit/s time slots on E1/T1 lines and Lb interface over E1/T1);

• Support of 16 kbit/s and 64 kbit/s LAPD (depending on the required signalling throughput) physical signalling channels on Abis interface;

• Voice and data switch between MSC/SGSN and BTS(s); • Clock synchronization and distribution over radio access network; • Support of control, operation and maintenance functions (for example software

download) of entire BSS system; • Handling of CCS#7 on Asub interface and LAPD channels management on Abis

interface; • Availability of reserved port to LMT Evolution; • Availability of reserved port to Radio Commander; • Support of hierarchical cell structure; • Support of extended cells; • Support of dual band operation; • Management of cell broadcast service messages; • Data collection for important time-consuming file processes; • Event logging; • Redundancy of all the main blades.

1.4 Traffic CapacityThe Base Station Controller (BSC) offers a dynamic capacity of up to 10,000 Erlang with the number of controlled TRX of up to 2000. The dynamic capacity of 10,000 Erlang is achievable in single AP configuration with the Siemens Traffic Model.

The 10.000 Erlang target figure can be achieved also with different TMs. This means that different (also higher) BHCA values applies, but, depending on the traffic mix, a multi processor configuration may be required. Besides the achieved capacity also depends on network configuration.

Full eBSC capacity is achieved with complete connectivity and with the High Configura-tion (2 shelves).

BR 6.0 BSC/72

BR 7.0 BSC/120

BR 8.0 BSC/120

BR 9.0 eBSC

Controlled TRXs 500 900 900 2000

Controlled Cells 250 400 400 1000

Controlled BTSE 200 200 200 500

Controlled TRAUs 32 48 48 100

PCM (Abis+Asub+Gb) 72 120 120 540 equiv. E1 lines

Table 1 Summary of eBSC capacity figures

16 A50016-G5100-A020-01-7618

TED:eBSC

Id:0900d805800e7119


1.4.1 ConnectivityThe enhanced Base Station Controller (eBSC) supports up to 540 equivalent E1 lines (Abis + Asub +Gb) depending on the configuration: physical PCM only, mixed physical PCM/channelised optical (providing max equivalent E1 = 540 lines), all optical channe-lised STM1/OC3. In case channelised OC3 is configured, the connectivity increases up to 672 equivalent T1 lines. Besides up to 288 physical PCM ports can be equipped. In addition, the eBSC supports star configuration towards the Transcoding and Rate Adap-tation Unit (TRAU). The capacity of the TRAU is provided to modularly expand traffic channels up to 960 per rack. Only one channel is required per Base Transceiver Station (BTS) to connect it to the Base Station Controller (BSC) by the provided 16 or 64 Kbps signaling channels (LAPD protocol). Up to 100 TRAUs can be connected to the eBSC (125 in case of T1 connectivity).

LAPD (Abis+Asub) 240 240 240 1300

SS7L 8 16 16 8x16

GPRS Channels (16Kb/s chan. on Abis)

1536 2816+256 2816+256 7650+850

Processing Capacity (BHCA)

128000 192000 192000 400000

Processing Capacity (Erl)

3200 4800 4800 10000

Switching Capacity (Erl) 3500 5200 5200 11000

BR 6.0 BSC/72

BR 7.0 BSC/120

BR 8.0 BSC/120

BR 9.0 eBSC

Table 1 Summary of eBSC capacity figures

A50016-G5100-A020-01-7618

17

TED:eBSC eBSC HW Architecture

Id:0900d805800e24e2

2 eBSC HW Architecture

2.1 IntrodutioneBSC is based on the open hardware platform advanced Telecommunication Comput-ing Architecture (aTCA PICMG 3.0). It provides off-the-shelf components and it supports application specific functionality and enhancements on board level. The aTCA standard defines:

• the Mechanical form factors and constructions for blade (boards);

• the Regulatory guidelines for safety, grounding and EMC according to NEBS and ETSI for the central office equipment;

• an hardware management system for the temperature control and fault detection;

• the basic inter-connection scheme and transport mechanisms available to each board, including the electrical characteristics of the interfaces on board level.

The eBSC provides a wall mounting feature, i.e. all the boards must be accessible by the eBSC front side only. This means that the eBSC allows the use of standard aTCA front blades/boards, but the Rear Transition Modules (RTM) are moved on the eBSC front.

In the eBSC the front access option, that means board backplane connections toward the “Zone 3” of backplane, is only reserved to the SMAC and LIET boards by means of eIOSM (Input/Output Switching Matrix) and IOLI (Input/Output Line Interface) respec-tively.

18 A50016-G5100-A020-01-7618

TED:eBSC

Id:0900d805800e24e2

eBSC HW Architecture

Figure 5 eBSC aTCA Shelf Concept

The eBSC is aligned to the PICMG 3.0 requirements; as a consequence all the main boards are interfaced by means of Gigabits Ethernet links via the Switching Matrix. eBSC aTCA compliance includes the adoption of the IPMI management architecture, based on a central (redundant) Shelf Manager (ShMC).

The eBSC equipment is composed the following elements:

– Rack;– Upper Shelf;– Lower Shelf;– DC Panel.

Each shelf supports up to 16 main blades. In addition the shelves the equiment practise includes the following blade types:

– Power Entry (PEM) blade;– Shelf Manager Module (ShMC) blade;– Alarm collector and Fan Control (ACFC). It is supported only on Upper shelf;– Shelf Alarm Panel (SAP) blade.

A50016-G5100-A020-01-7618

19


Id:0900d805800e24e2

2.2 eBSC Hardware ArchitectureThe eBSC functional overview is represented in Figure 6.

Figure 6 eBSC Functional Overview

The eBSC provides the following main functions and interfaces:

LM-E1/T1

Up to 288 PCM ports

Line Module E1/T1 terminates PCM and L2 for Abis, Asub, Gb, Lb and X.25 / 64 Kbit/s Time Slots. This functionality is provided by LIET+IOLI blades.

LIET performs the processing portion of Line Module E1/T1, IOLI is the Input/Output interface that provides line terminations.

LM-STM1/OC3

Up to 16 STM1 ports

Gb, Abis, Asub, Lb (and X.25 / 64 Kbit/s Time Slots) interfaces can also be implemented on Line Module STM1/OC3 providing:

– Abis, Asub, Lb: VC-12 (VC-11) – channelised STM1 (OC3);– X.25: transport of O-link via PCMS;– For Abis and Asub, LM-STM1/OC3 must also terminate L2;– Gb: unstructured STM1/OC3 with classical IP over ATM (Gb is also supported via

Ethernet – High Speed Gb). This functionality is provided by LISO blade.

20 A50016-G5100-A020-01-7618

TED:eBSC

Id:0900d805800e24e2


MCP

The Main Control Processor is O&M master, providing:

– central function;– communication with dependent blades based on Ethernet (via ShMC or directly,

depending on task);– Ethernet for IP-based O-link and LMT;– X.25 for “legacy” O-link (also supported via PCMS).

This functionality is provided by MCP blade.

AP

Several Application Processors (Application Processor – Master and Application Pro-cessor – Dependent) support distributed Call Processing.

– AP-M: SS7 signalling BSC1, MSC + RRM for selected cells;– AP-D(s) (presence depending on traffic requirements): RRM for selected cells.

This functionality is provided by AP blade.

UPM

Several User Plane Modules support PS services. Moreover, one UPM may be option-ally configured as Central NSM (Network Service Module). This functionality is provided by UPM blade.

SM

Switching Matrix provides the Ethernet backbone for all blades in the same shelf; Inter-shelf connections; Main Clock Generator. This functionality is provided by SMAC blade. As the LIET, the SMAC has one Input/output module associated: IOSM module.

Ports X.25/V.11

Two ports are supposed to be used as one alternative for dedicated O-link ports.

Ethernet ports

Two ports are supposed to be used as another alternative for dedicaded O-link ports.

and two ports are supposed to be used as dedicated connection to the LMT.

Two External Synchronization Sources

The eBSC has also the capability to synchronise the internal Clock Generator either to an E1/T1 port or to an STM-1 ports signals.

RAS ( Remote Alarms Signalling)

Three alarm status indication; they are controlled by software and they are supposed to indicate the Critical, Major and Minor alarm status.

A50016-G5100-A020-01-7618

21


Id:0900d805800e24e2

2.2.1 Rack ConfigurationThe eBSC rack is composed by the upper shelf, the lower shelf and DC panel. The main-tenance concept is compliant to the PICMG 3.1 Recommendations and provides a dupli-cated Shelf Manager in each shelf supporting the power management, the fans control and the fault management. The main rack’s characteristics are the following:

• it has no rear access for maintenance activities;

• the front door supports an alarming mechanism to detect possible door open states;

• the rack is equipped with an alarm lamp panel (visible trough the door opeing) with different colors related to the alarm’s severity (for example: red = Critical);

• it provides an optimized system cabling interface.

The Figure 7 shows a view of the eBSC rack with upper, lower shelf and DC panel.

Figure 7 eBSC Rack

22 A50016-G5100-A020-01-7618

TED:eBSC

Id:0900d805800e24e2


2.2.1.1 Upper ShelfThe upper shelf is composed by a sub shelf at the bottom. It contains the main aTCA blades in vertical position (for example the LIET blades). Any blade defined for the eBSC can be plugged in this sub shelf. It is also the only shelf which can house the LIET/IOLI modules. The SMAC blades have their own dedicated slots. At the top a sub shelf is housed. It contains in vertical position the I/O modules of LIET and SMAC: IOLI and IOSM respectively. Only the Upper shelf houses the Alarm Connector and Fans Control blade (ACFC). According to the aTCA standard, the upper shelf implements the follow-ing additional features:

• 48V main voltage connection and filtering by means of the PEM unit; • Fan control and maintenance supervision via the Shelf Manager mainly supported

by the ShMC blade. The Upper Shelf includes a redundant ShMC blade.

Figure 8 eBSC Upper Shelf

A50016-G5100-A020-01-7618

23


Id:0900d805800e24e2

2.2.1.2 Lower ShelfThe Lower Shelf is composed by a sub shelf at the bottom. It can house any standard aTCA blades and it is equal to the bottom sub shelf implemented in the upper shelf. The only difference is that the lower shelf does not support the LIET. The SMAC blades have their own reserved slots. The top sub shelf is lower respect to the bottom sub shelf. It contains only the SMAC I/O modules – IOSM – hosted in horizontal position.The lower shelf implements the following additional features according to the aTCA standards:

• -48V main voltage connection and filtering by means of the PEM unit; • Fan control and maintenance supervision via the Shelf Manager mainly supported

by the ShMC blade. The Lower Shelf includes a redundant ShMC blade.

Figure 9 eBSC Lower Shelf

2.2.1.3 DC PanelThe DC Panel splits and distributes to the shelves the two -48V main feeds of the rack. Each power line provides up to 25A and it is protected against over current by means of a breaker. The DC panel contains also additional EMI filters on power supply cables that guarantee the compliance to limits on noise conducted emissions on -48V main feeds measured at the input of the rack. This is obtained in combination with filters distributed on each blade.

On the DC panel front is available the RAS connector, like in the BSC1, this is a SUB-D 37 type connector used to send the BSS alarms to a remote location.

24 A50016-G5100-A020-01-7618

TED:eBSC

Id:0900d805800e24e2


2.2.2 RedundancyThe redundancy concept is supported in the eBSC main components and different types of hardware redundancy have been implemented, as follow:

• The Switching Module and Clock (SMAC) blade hosts the Ethernet Switch that runs in active/active redundant configuration;

• The Main Control Processor runs in active/standby configuration. For the reason that the modules work in an hot standby configuration which is supported by the hardware, a special circuit is provided to perform the automatic alignment of the data between the two copies of the processor blades;

• The Application Processor (AP) runs in active/standby mode. For the reason that the modules work in an hot standby configuratio; therefore there are N pairs of APs in the system;

• The User Plane Module (UPM) runs in load sharing configuration;

• The LIET support n+1 redundancy and operate with one blade that is ready but in stand-by while the remaining N blades manage the user traffic. When a failure occurs to the active blade, the stand-by blade is set active to manage the external PCM signals. A specific circuit is provided to route all the E1/T1 signals towards the LIET spare blade. No hardware provision is required to route the internal connec-tions supported by a faulty line card to the LIET spare blade;

• The STM1 support the 1+1 redundancy.and operate in 1+1 APS configuration. A specific hardware inter-connection is provided between the line framers of the two STM-1 line blades to support the function.

Hereafter the blades cardinality and related redundancy:

2.2.3 Basic Configurations and System ExpansionThe system is composed by 1 rack hosting 1 or 2 shelves (16 slots each). Shelves host up to 14 blades providing processing (signalling, packet handling), line interface, O&M controller-MCP and always have 2 blades for internal switching functionality. Racks and shelves adopt the wall mounting equipment practise. The two shelves are distinguished into “upper shelf” and “lower shelf”. Two different configurations are supported: “Basic” eBSC and “High End” eBSC.

Blade Cardinality Redundancy

LIET 9+1 Hot standby

LISO 4+4 Hot standby

SM 1+1 Hot standby

UPM 11 Load sharing

AP-M 1+1 Hot standby

AP-D 5+5 Hot standby

MCP 1+1 Hot standby

Table 2 Cardinality and Redundancy

A50016-G5100-A020-01-7618

25


Id:0900d805800e24e2

Basic eBSC Configuration

The “Basic” Configuration includes 1 shelf only and its capacity is limited in terms of con-nectivity and GPRS data traffic to the BSC/120 figures. Rack contains:

– Upper shelf: • 1+1 MCP (hot stand-by); • 2 SMAC blades (active/active); • 1+1 AP; LIET/IOLI line cards, UPMs (depending on traffic requirements); • Redundant ShMC.

– Lower shelf is not equipped.

High eBSC Configuration

The “High” Configuration is prepared to grow to the maximum capacity and will therefore consist of 2 shelves. Rack contains:

– Lower shelf: • 1+1 MCP (hot stand-by); • 2 SMAC blades (active/active); • UPMs, Aps depending on traffic requirements; • Redundant ShMC.

– Upper shelf: • 2 SMAC blades (active/active); • LIET/IOLI line cards, UPMs depending on traffic requirements); • Redundant ShMC.

Upgrade from “Basic” (one shelf) to “High End” eBSC configuration (2 shelves), if required by the customer at a later time, can be carried out in field with service interrup-tion. When providing it, e.g. line cards will take the place of AP and MCP pairs in the upper shelf. AP/MCP blades will be moved to the lower shelf, requiring system restart and interrupting the service.

2.2.4 Alarm Reporting Functional SplitThis process comprises Alarm Generation, Alarm Collection, Alarm Filtering and indica-tion.

Remote Alarms Signalling

The eBSC sends the alarms to the Radio Commander and to the LMT Evolution.

The eBSC subsystem provides the local displaying of the alarms that will be sent to the R.C. The leds are associated to as many relay contacts to send outside the following alarm conditions:

Global alarm: Critical

Global alarm: Major

Global alarm: Minor

Environment alarm

SAI/PAI alarm: Minor

Equipment alarm: RC

Equipment alarm: MPCC

Equipment alarm: CLK

26 A50016-G5100-A020-01-7618

TED:eBSC

Id:0900d805800e24e2


LEDs are colored as follows:– green LEDs are used to localizing equipment status;– yellow LEDs are used to signal minor severity alarms;– red LEDs are used to signal major and critical severity alarms.

The rack is enclosed by front doors: therefore, the alarm panel is not visible during normal operation; however, three summary LEDs also extend (in parallel) to lamps located outside the rack. These external lamps illuminate when a critical, major or minor alarm is present.

LEDs are subdivided in the following groups:

GLOBAL ALARM:– illuminated red LED for CRITICAL alarm;– illuminated orange LED for MAJOR alarm;– illuminated yellow LED for MINOR alarm.

SYSTEM ALARM:– illuminated red LED and not flashing for MAJOR alarm;– red LED flashing for CRITICAL alarm;– illuminated yellow LED for MINOR alarm.

EQUIPMENT STATUS - COMMUNICATION:– green illuminated LED for no alarm;– green LED flashing for alarm.

S/W RUN (NEW and OLD):– S/W RUN LEDs are normally switched off. They illuminate only during the change

version procedure.– When a LED is illuminated, it indicates which software version is currently running.– These LEDs switch off when the operator enters the appropriate command (end of

change version).

MINOR ALARM:

SAI PAI– alarm related to PCMS lines;– alarm related to PCMB lines;– alarm related to PCMG lines.

ENV– illuminated and not flashing indicates a MINOR alarm;– slow flashing indicates a MAJOR alarm;– fast flashing indicates a CRITICAL alarm.

ENV LED switches on when there's an enviromental alarm such as smoke, intrusion, fire or temperature.

A50016-G5100-A020-01-7618

27


Id:0900d805800e24e2

2.2.5 eBSC CapacityThe enhanced Base Station Controller (eBSC) supports up to 540 equivalent E1 lines (Abis + Asub +Gb) depending on the configuration: physical PCM only, mixed physical PCM/channelised optical (providing max equivalent E1 = 540 lines), all optical channe-lised STM1/OC3. In case channelised OC3 is configured, the connectivity increases up to 672 equivalent T1 lines. Besides up to 288 physical PCM ports can be equipped, this is valid both in case of T1 or E1 lines.

In addition, the eBSC supports star configuration towards the Transcoding and Rate Adaptation Unit (TRAU). The capacity of the TRAU is provided to modularly expand traffic channels up to 960 per rack. Only one channel is required per Base Transceiver Station (BTS) to connect it to the Base Station Controller (eBSC) by the provided 16 or 64 Kbps signaling channels (LAPD protocol). Up to 100 TRAUs can be connected to the eBSC (125 in case of T1 connectivity).

2.2.6 eBSC Rack Power Consumption and Physical CharacteristicThe eBSC rack power consumption and physical characteristics are described in the table below:

Power consumption and physical characteristics of the eBSC

Power consumption (W) < 1500 W / Shelf

Input voltage DC - 48V

Operating temperature range - 5°C to + 40°C

Height 2000 mm

Width 600 mm

Depth 450 mm

Weight < 200 Kg

Upper Shelf 1023 mm

Lower Shelf 698 mm

Table 3 Physical Characteristics of the eBSC

28 A50016-G5100-A020-01-7618

TED:eBSC

Id:0900d805800e2281

Module Description

3 Module DescriptionIn this chapter each eBSC blade with its main functions is described.

eBSC is based on the open hardware platform advanced Telecommunication Comput-ing Architecture (aTCA PICMG 3.0).

The Hardware Design Specification describes the hardware functionalities and the implementation of the WARP (tWin AMC caRrier Processor) based blade to be used in the eBSC equipment.

The WARP and the WARP-L cards are general purpose processor boards that can accept up to two AMC (Advance Mezzanine Cards) in order to specialize their functions. The WARP is used in the eBSC equipment as a motherboard for the MCP and AP entities while the WARP-L is used as a motherboard for the UPM and STM-1. The dif-ferent eBSC blades can be obtained, depend on the type of the mezzanines equipped on the WARP and on the WARP-L. To achieve the AP functions no mezzanines are needed.

As an ATCA blade, the WARP structure is splitted in two main parts:

• Carrier IPMC: incorporates the circuitry responsible for the low level HW mainte-nance. Together with the shelf manager realizes the shelf management concepts as specified in the PICMG 3.0. Being the WARP an AMC Carrier this part is also in charge to control the mezzanines sites.

• PAYLOAD: it is the user defined part of the board in which the specific functions are implemented. Basically the WARP payload is a general purpose processor complex which tasks are different depending on the type of eBSC blade the WARP is used.

The WARP paylaod architecture can further be splitted in the following sub-blocks:

– Processor complex block;

– Peripherals block;

– Hot redundancy block;

– Clock generation block;

– Power supply block.

3.1 E1/T1 Line Module (LIET and IOLI)The LIET blade is a Line Module providing 32 physical interfaces E1/T1 to/from Abis/Asub/Gb.Moreover LIET module manages up to 256 LAPD links.

PCM lines can support Abis, Asub, Gb, Lb, and one or two 64 Kbit/s time slots, also X.25 traffic (O-link).

The LIET blade supports and manages the E1/T1 interfaces. The E1/T1 support is provided both from LIET blade (processing portion located in the front side slot of the shelf) and from the Input/Output Line Interface (IOLI) that provides the line terminations.

The LIET blade supports the N+1 redundancy concept with N = 9 ; a spare LIET is avail-able, but without the correspondent IOLI. When a fault occurs to a LIET, the spare takes over the relative lines, serving the traffic without service interruption until the problem is solved and a switch-back is consequently performed.

The main task of the LIET blade is the conversion of external data and speech traffic (in PCU/TRAU frame or FR formats) from TDM to the internal Gigabit Ethernet transport format, and vice-versa. In case of signalling channels on the TDM interface, the

A50016-G5100-A020-01-7618

29

TED:eBSC Module Description

Id:0900d805800e2281

hardware terminates the HDLC layer and it transfers the payload data to the on-blade processor for level2 protocol handling. The resulting payload is then forwarded to the AP blades for further level3 processing.

The IOLI module supports the electrical interface towards the external lines. The elec-trical interface consists of the redundancy relays, over voltage protections, transformers and plugs.The main LIET/IOLI performance data are the following:

• Support of 32 line interfaces configurable for either E1 (120 Ohm or 75 Ohm) or T1 (100 Ohm) via:

– 4 x D37 SUB-D connectors (8 lines per connector) housed on the IOLI module front, providing the 100 /120 Ohm connections;

– 32 x coaxial connectors housed on the IOLI module front, providing the 75 Ohm con-nections;

• Support of up to two 2.048 MHz reference clocks extracted from the line interfaces;

• Management of at least 256 HDLC channels;

• Support for conversion between 8 /16 / 64 Kbit/s time slots on the TDM interface and internal Ethernet-based PPP-Mux connections switched through the SMAC.

The Figure 10 shows the block diagram.

Figure 10 LIET / IOLI Block Diagram

30 A50016-G5100-A020-01-7618

TED:eBSC

Id:0900d805800e2281

Module Description

3.2 Main Control Processor (MCP)The MCP functionality is obtained mounting the T-REX mezzanine board and the Hard Disk drive mezzanine board on the WARP.

MCP (Main Control Processor) blade is the Central O&M controller (redundant, 1+1 hot stand-by based on HW support for redundancy), supporting O&M for the whole system. Internal O&M traffic is handled via Ethernet and via standard facilities supported by the adopted equipment practise. The O&M controller also provides connections for RC (X.25, Ethernet) and LMT (Ethernet only); RC serial (X.25) connectors, one per MCP, are physically available on DC panel. The central O&M controller interacts with the ShMC for the management of aTCA-based HW.Main Performances:

– HDD (Hard Disk Driver) for DBMS data persistency. Active copy keeps HDD on stand-by copy aligned.

– Connection to RC/CBC: • 1 port for 10/100 BASE-T Ethernet for Ethernet- IP based O&M; • 2 ports for X.25-based connection. Physical link according to V.11-X.21

HDLC providing HW support for LAPB protocol.– Connection to LMT:

• 1 port for 10/100 BASE-T Ethernet- IP based for connection to Local Manage-ment Terminal.

– HW configuration logic to indicate the active and stand-by copy even in presence of failures and during boot phase, when SW is not loaded yet.

– HW support for 1:1 redundancy scheme (same as AP blade, see above).

MCP blade front panel houses the RC and LMT IP connectors. RC serial (X.25) connec-tors, one per MCP, are physically available on Rack Top through the Crossing board; (the internal connections to MCPs are provided). Connectors available on the MCP front panel are:

– RC (O-Link) – two RJ45 for Ethernet connection;– LMT – one RJ45 for Ethernet connection.


A50016-G5100-A020-01-7618

31


Id:0900d805800e2281

Figure 11 MPC Block Diagram

3.3 User Plane Module (UPM)With two GEARs (Gigabit Ethernet Abis handleR) mezzanine cards on it, the WARP is configured as UPM and is responsible for the processing of packet data.

The GEAR board is a mezzanine board, it supports the processing of the layer2 packet data traffic over the Abis interface. Two Gigabit Ethernet links from the fabric interface are routed to the mezzanine card, each from one Ethernet switch plane.

UPM blade manages the protocol stack conversion between the Gb and Abis interfaces of EGPRS/GPRS radio channels. It is located in the eBSC and supports interfaces to several Channel Coding Units (CCU) located in BTS. UPM acts as a statistical multi-plexer and router, dealing with protocol stacks and interworking functions. In fact, it receives Radio Link Control packets (RLC) from Abis channel that refers to more than one mobile station (MS) and packs them into Logical Link Control frames (LLC). These LLC frames are routed, together with other LLC frames coming from any of the other Abis channels to SGSN and vice versa.

Main software and hardware components of BSS system supporting EGPRS/GPRS services are represented in the Figure 12.

32 A50016-G5100-A020-01-7618

TED:eBSC

Id:0900d805800e2281

Module Description

Figure 12 UPM and Interfaces

UPM blades (User Plane Module; 0 to n depending on traffic requirements) handle (E)GPRS traffic. UPMs implement PCU functionality and are used in load sharing con-figuration, accordingly with key license.

Performances:

– 850 Abis channels @16 kbit/s terminating (E)GPRS protocols;– Termination of internal PPPmux transport for TDM channels.

At most 11 blades of this type can be configured. The 11th blade is available if Central NS is enabled and will not process Abis channels. In this case, another UPM is desig-nated as stand by Central NS router and under normal conditions works as plain UPM. In case of failure of the central NSEI router, the UPM designated as stand-by Central NS router is taken out of the PCU load balancing pool, its (E)GPRS traffic is dropped and this blade takes over the role of active Central NS UPM.

3.4 Application Processor (AP)When the AMC bays are not populated, the WARP carries out the call processing appli-cation and is recognized as AP-M/D board.

The AP blade is responsible for the call processing application. In eBSC the traffic model requires both an improved call-processing performance over BR8.0 and the distribution of the application over a number of blades. The AP will run in 1+1 redundancy in active / stand-by mode. Therefore there may be N such pairs of APs in the system.

One redundant 1+1 (hot / stand-by) is based on HW support for redundancy-“hot link”. Application Processor-Master (AP-M) blade supports SS7 to/from the CS core network and also handles RRM for selected cells, while a number 0 to n, depending on traffic requirements. Application Processor-Dependent (AP-D) blades handle RRM for other groups of selected cells.

3.5 STM1 Line Module (LISO Blade)The blade module STM-1/OC3 provides 2 optical links to/from Abis/Asub/Gb interfaces, which can be configured in:

– Channelized mode (63 E1 equivalent lines);

A50016-G5100-A020-01-7618

33


Id:0900d805800e2281

– Unchannelized mode (broadband);– Mixed mode.

The overall connectivity per module is 126 (2x63) E1 equivalent lines (channelized mode) or 2 x 155 MB/s (unchannelized mode).Moreover LM-STM1/OC3 module manages up to 1024 LAPD links.

The LM-STM1/OC3 functionality is achieved mounting the two SLIM mezzanine on the WARP.

The SLIM board is an AMC mezzanine, it supports a optical interface channelized STM1/OC3 (VC-12) that provides the Abis/Asub interface for TDM traffic for the con-nection towards the BTS and TRAU nodes.

The USLIM board is an AMC mezzanine, it supports a optical interface unchannelized STM1/OC3 (VC-4) traffic for the Gb interface with classical IP over ATM.

In addition, STM1/OC3 is also adopted on Abis and Asub interfaces (and also for X.25 64 Kbit/s time slots on E1/T1 lines and Lb interface over E1/T1) in order to make the best use of STM1/OC3 backbones and to optimize footprint at the same time. In this case, channelized STM1 (which allows to aggregate up to 63 E1 lines or 84 T1 lines in a single STM1/OC3 container) is provided.

Support of line protection (APS, Active Protection Switching) is provided in addition to blade protection. Each STM1/OC3 line card supports 2 optical ports, which can be con-figured in structured (Abis/Asub; possibly Gb depending on customer’s requirements) or unstructured mode. The adopted line card uses a 1+1 redundancy scheme. At most 4+4 blades of this type can be configured on an eBSC basis.

The cross link between active and stand-by copy for APS data is currently assumed to go back to the baseboard and to go over ATCA’s Update Interface.


34 A50016-G5100-A020-01-7618

TED:eBSC

Id:0900d805800e2281

Module Description

Figure 13 LM-STM1/OC3

3.6 Switching Matrix (SMAC and eIOSM)The Switching Module and Clock (SMAC) blade provides a Gigabit Ethernet switch for both aTCA interfaces and supports central clock functions. In addition the SMAC blade has associated own I/O module: the eIOSM module housed in the upper part of the shelf.

The SMAC supports the transport of all types of traffic (user and control data) between the blades of the aTCA shelf and between the aTCA shelves inserted in the rack; besides it supports the generation of a centralized clock to run in a synchronous trans-port network.

For reliability reasons the transport and clock generation functions work in a redundant configuration within the system. For the transport function the redundancy configuration is active/active to enable the load sharing over both Ethernet planes.

The centralized clock functionality works in active/standby configuration. An on-blade processor configures, supervises and controls all the functional modules of the SMAC. It is connected to the own redundant transport function. The main components of the SMAC blade are:

– the Gigabit Ethernet Switching (GES) module that supports the transport functions of user, control and management data. Basic interface (as defined in PCMG 3.0)

A50016-G5100-A020-01-7618

35


Id:0900d805800e2281

and Fabric Interface (as defined in PCMG 3.0) are provided. Inter-shelf transport uses either n Gigabit Ethernet;

– the Main Clock Generator Module (MCG) provides the central clock functionality. It generates an high stable synchronization clock distributed within the shelf and used for synchronizing the line interfaces within the aTCA shelf. Besides Jitter and wander of clock generated and distributed are aligned to the requirements defined in ITU-T G.812 type I (2048 kHz interfaces and STM-N), ITU-T G.813 (SEC) and Telcordia GR-1244-CORE;

– the General Purpose peripheral Processor (GPP) manages and supervises the status of GES and MCG components by means of a standard bus. The RAM memory with ECC has a size of 1 Giga Byte.

SMAC manages up to 21 External Alarms, open door alarm included. The alarm signals are connected via backplane to the ACFC blade available in the upper shelf. The SMAC I/O module, IOSM blade, is a Field Replaceable Unit (FRU) equipped with a memory to identify its PID. IOSM supports eight Ethernet links for external connections by means of eight RJ45 connectors available on the blade front panel. Two RJ45 connectors of those are reserved to provide the High Speed Gb (HSGb) external connections toward the SGSN. A SUB-D 25 female type connector provides the 2.048 MHz signal for the external synchronization (T3).


36 A50016-G5100-A020-01-7618

TED:eBSC

Id:0900d805800e2281

Module Description

Figure 14 SMAC Block Diagram

3.7 Shelf Manager Module (ShMC)According to PICMG 3.1, aTCA Management functions are responsible to monitoring the health of HW components, resetting and powering up a blade. The IPM Controllers (IPMC) are present on every blade.

The Shelf Manager functionality is provided by the ShMC located in the aTCA shelf. It guarantees the control of the Shelf, acting as a starter and dispatcher of commands to the blades through the IPMC via a dedicated bus (IPMB) with IPMI commands. Each shelf of the eBSC includes a redundant (1+1) ShMC blade.

The Shelf Manager blade shall provide the following functions:

– Shelf Management capability for up to 16 slots ATCA shelf;– Dual IPMB bus architecture;– Dual 10/100Mbps Ethernet Controller;– Generation of Telco alarms. LEDs and isolated Telco alarms connection on the SAP

blade;

A50016-G5100-A020-01-7618

37


Id:0900d805800e2281

– Dedicated link to the redundant ShMC for active-standby operation;– Power supply, Monitoring and speed control of FANs inside the shelf;– Dedicated link to the two shelves data modules (FRU modules);– Serial port for debugging purposes (UART);– Single ambient temperature monitor on blade;– Remote power supply feeds monitoring ( sensor on PEM blade ).


Figure 15 Shelf Manager Block Diagram

The SHMM provides a flexible platform for shelf management functionality. Using the Small Outline Dual Inline Memory Module (SODIMM) mezzanine form factor the SHMM is especially targeted to provide the primary shelf management intelligence on the ShMC blade. The SHMM is for system architectures based on [ATCA] specification.

The SHMM supports redundant operation with automatic switchover between two SHMMs. In a configuration where two SHMMs are presents, one acts as the active shelf manager and the other as standby. Both SHMMs monitor each other, and either can trigger a switchover if necessary.

The master only I2C bus present on the SHMM module is also used to connect to micro-controller the following devices present on the ShMC blade:

• Temperature monitors: provide the ambient temperature measure surrounding the blade.

• System management controller: provides the fans control via the PWM command and it receives the tachometer feedback signal.

38 A50016-G5100-A020-01-7618

TED:eBSC

Id:0900d805800e2281

Module Description

3.8 Shelf Alarm Panel (SAP)The Shelf Alarm Panel (SAP) is the unit providing the Telco alarm interface of eBSC shelf. On its front plate are available:

– the Telco alarms connector for remote monitoring;– the Telco alarm LEDs;– the Telco alarm reset push button;– a connector to route Telco Minor, Major and Critical alarms signals to the rack Lamp

Panel.

The SAP blade is connected, with a master I2C bus, to both Shelf Managers blades but only the active Shelf manager has access to SAP.


Figure 16 SAP Block Diagram

3.9 Alarm Collector and Fan Control (ACFC)The Alarm Collector and Fan Control (ACFC) blade is the unit that provides the interface to connect up to 21 External Alarms (environment), open door alarm included, to the eBSC equipment and that realizes the interface to connect the two Shelf Managers with the Fans trays to provide the control of the cooling of the shelf.

A50016-G5100-A020-01-7618

39


Id:0900d805800e2281

Protection devices against over voltages on the External Alarms lines are provided on the blade.

The rear connector of the ACFC realizes the interface, via backplane, to the SMAC blades and the Fan trays. This interface provides:

– the External alarms lines to the SMAC blades;– the dedicated -48V power supply line used to supply the Fan trays modules;– the control and monitor the speed of the fans;– the protection against overvoltages on alarm signal lines.

On the front plate of the blade there are the interface connectors for the External Alarms, Door Alarm and Fan control. The External Alarms connector, like in the BSC1, is a SUB D 50 Type connector.

External Alarms Interface

The External Alarm Interface is a connector that collects up to 21 alarms each one con-stituted by two wires that report the status of a relay. The wire correspondent to the common of relay is put to electrical ground GND inside the ACFC blade.

Line Protection

This block realizes the protection on alarm signal lines against overvoltages due to surges.This protection is realized with semiconductor devices on each signal line that discharge the surge overcurrent to mechanical ground (GNDM).

Fan Control Interfaces

There are two fan control interfaces, one for each ShMC.

Each interface is a constituted by a connector that collects from its ShMC the PWM signal to control the speed of all six fans and the power supply for the fans.

The same interface returns to its ShMC three fans presence signals (one for each fan tray module) and six tachometer signals (one for each fan).

Signals lines to and from the two Shelf Managers are combined and split inside ACFC blade without any particular device and are connected to the three fan tray modules.

The power supply from the two Shelf Managers are combined inside the ACFC board with "OR" diodes on MUE lines.

3.10 Power Entry Module (PEM)The Power Entry Module (PEM) implements the interface to the main power supply input. It is used both in upper and lower shelf.

Each shelf contains two PEM to connect the two -48V main feeds provided, for redun-dancy.

Each main feed to the shelf comes from the rack DC Panel split on four cables pairs that are fixed on the front of each PEM.

Inside the PEM the split is maintained on four power lines that are fed separately to the shelf backplane via the rear connector. An EMI filter on each line contributes to meet the EMC requirements at shelf level, as represented in next Figure 17.

40 A50016-G5100-A020-01-7618

TED:eBSC

Id:0900d805800e2281

Module Description

Figure 17 Power Distribution Concept

The presence of power supply on each line is monitored and when, for any reason, a failure occurs on a power line, a specific alarm signal for that line is generated and sent to the Shelf Manager, on a dedicated I2C bus, via shelf backplane.

A50016-G5100-A020-01-7618

41


Id:0900d805800e2281

3.11 Power Supply (DC Panel)Each eBSC shelf is supplied by two independent lines at -48V for redundancy and combined together only at blade level. The top of the rack hosts the power supply cables connections and lighting protection devices. The DC panel provides the power distribu-tion; the two main supply lines are split on several power lines for a multiple power entries connection to the shelves. Each power line is protected by a breaker accessible at the DC Panel front plate and specific filters are available on each main line. Electro-magnetic Compatibility (EMC) requirements are fulfilled by combined operations of these filters with the EMI filters at shelf and blade level.

For the reason that the partially proprietary equipment practise of the eBSC implies devi-ation from aTCA requirements, also aTCA shelf power supply requirements have been partially fulfilled.

The eBSC shelf power supply has the following characteristics:

– it is aligned to the safety requirements of IEC 60950 Recommendation for power entry terminals or connectors;

– power entry method supported is both connector or power stud;– fusing at power entry point of the shelf is not supported;– the DC panel supports power switching.

All the main blades (SMAC, AP etc.) receive the dual DC feeds provided by the shelf. The secondary voltages are generated on each blade by specific DC-DC converters.

Any power required by an Input/Output module is provided by the corresponding blade (for example the SMAC) via backplane.

TERA Board

The TERA is the board that collects the Telco alarms of the Upper and Lower shelf (from the SAP board) and realizes the “OR” of each alarm type for Remote Alarm Signalling (RAS).

This board accommodate three connectors: two Molex Micro-D 15 plug for input alarm signals from SAPs boards and one Sub-D 37 pin female for the RAS output. The board consist of only direct connections among these three connectors and there aren’t other passive or active components.

The “OR” alarm signals shall be available, as in the previous BSC, on a SUB-D 37 pins connector.

The pinout of Critical, Major and Minor alarms is the same of the BSC1 for compliance.

All other remote alarms of the previous BSC system are not present in eBSC and for this reason the correspondent pins of the RAS connector are N.C. (Not Connected).

The Power Alarm and the Reset signals for Minor and Major alarm, present only on eBSC, are mapped on pins that are not assigned in the BSC1.

The TERA board is placed inside the DC Panel with the connectors available on the front panel.

42 A50016-G5100-A020-01-7618

TED:eBSC

Id:0900d805800e2281

Module Description

3.12 Lamp PanelThe Lamp Panel is the module of the rack that shall signalize in a visual manner the Minor, Major and Critical alarms generated by the maintenance system of eBSC.The lamps shall be visible from the front of the rack and the following colours in combination with the named alarms are applied:

– MinorYellow

– MajorOrange/amber

– CriticalRed

The lighting of each LED is controlled switching on/off a 48V voltage (range 40.5V to 57V) carried to Lamp panel from MSU.

This voltage is, for redundancy, the “OR” derived from FEED A and FEED B supply lines and is adequately protected against overcurrents or shortcircuits. The maximum current available is 0.5A max.

The 48V positive pole is carried directly and it is common to all three LEDs. The 48V negative pole is carried separately to each LED when the correspondent alarm is switched on by one of its two associated relay contact, one on SAP board of the Upper Shelf and the other on SAP board of the Lower Shelf. The relays are controlled by the eBSC system maintenance.

The “OR” functions between the corresponding alarms criteria from the SAP boards is realized on Lamp Panel board (see Figure 18).

Figure 18 Lamp Panel Concept

A50016-G5100-A020-01-7618

43

TED:eBSC eBSC Software Architecture

Id:0900d805800e22a6

4 eBSC Software ArchitectureThe eBSC software is subdivided into the following main categories:

– software components that do not depend from the adopted BSC1 or eBSC platform like, for example, the GPRS/EGPRS software;

– software components that have been restructured to run on eBSC platform, like for example the Q3 stack software;

– software components that depend from the eBSC platform, like for example the Operating system.

Besides the eBSC software architecture is structured in two different levels:

1) Software physical allocation: at this level the software is allocated on each related blade, as represented in next Figure 19;

2) Logical software architecture: the Software is subdivided into Functional Areas and Subsystems. A functional area is the set of logical functions that provide one or more services (an example of functional area is the "System Download", the "Q3 stack", the "Status Manager", etc.). A subsystem is a further subdivision of the Functional area, that means that a Functional Area can be composed by one or more subsystems.

Figure 19 eBSC Software Physical Allocation

This logical subdivision is independent from the physical allocation of the software: for example, a Functional Area may also include the software residing on the MPC, AP or both.

The eBSC software includes also the peripheral processors. Their functions (for example the functions provided by Abis and A protocol stacks) are detailed in the related GSM Recommendations.

The MPC software is the main eBSC sw component; it controls the configuration, oper-ational and maintenance status of all the subsystems, including the subordinate proces-sors. The MPC software manages the Operating System, the status administration and audit functions, the System Maintenance, the Database Administration, the control and supervision of the switching matrix and all the related administrative functions.

Besides it supervises also the Level2 Lapd, the Level3 Radio Service, the Packet Service, the Network Layer 7 and GPRS/EGPRS services.

The AP software is mainly responsibile of the application functions performing the Level 3 Radio layer as specified by the GSM Recommendations. Besides Its software includes functions supporting the Operating System, the general maintenance, the Database Administration.

MPC software AP software SMAC software UPM software Line Module

Software

eBSC Software

44 A50016-G5100-A020-01-7618

TED:eBSC

Id:0900d805800e22a6

eBSC Software Architecture

The SMAC software is the common communication part for all traffic within the eBSC and it provides the synchronization capability from an external source in order to generate and propagate all the clocking signals necessary to keep synchronous the system and the boards supporting synchronous transport network interfaces.

The UPM software is specialized to support the packet switching (PS) functions. that include the channel allocation functionality, the management of GPRS/EGPRS traffic, the CPU reset etc. Besides UPM software supports the legacy ‘Gb over FR’ , Gb over IP over Ethernet’ interfaces as well as the ‘Gb over IP over ATM’ protocol stack; and also the Network Service functionality allowing the configuration of the entire GPRS Network Servoce layer on one UPM physical blade.

The Line Module software supports the traffic exchanged between the Abis and Asub interfaces (voice and CS data services), between the Abis and UPM software to trans-port GPRS data at the Abis side of the PCU and also between the Gb interface and UPM to transport the same GPRS data at the Gb side of the eBSC. The Line Module software provides also the level 2 termination for the BTSE connected to eBSC as well as for the A and Lb interfaces (MTP-2 for SS7 layer 2), the support of PCMH (for extended SS7 links) and X25A (O&M link embedded in Asub interface).

The eBSC software architecture is composed by the following logical subsystem:

– Operating System;– EBSC basic services;– Data Base Administration;– Status Manager;– Level2 Radio;– Level3 Radio.

The main functions and characteristics of each subsystem are described in the next part of the chapter, as follows:

Operating System

The eBSC Operating System is Linux. It is structured in the following main applications:

Boot Loader

This sybsystem manages the SW load and OS startup.

Kernel

This subsystem is the core of the Operating System it manages the OS resources. Kernel provides the applications with the features needed for their usage, in most cases through a set of system calls. Its main functionalities are the following:

– CPU time management, for real time tasks activity scheduling;– memory management, for dynamic allocation of memory areas;– communication and synchronization between tasks, by means of messages data

structures, mailboxes, semaphores and so on;– system timings, for timers handling.

In the eBSC blades, CPU time management and task scheduling operations are managed by the Kernel of MontaVista Linux Operating System.

Virtual Operating System

The Virtual Operating System is a library that can be linked by applications in order to gain access to some useful services, and to facilitate old code porting on the new plat-form.

A50016-G5100-A020-01-7618

45


Id:0900d805800e22a6

eBSC Basic Services

The eBSC Basic Services provide a common base SW platform on which applications can be easily developed and integrated. The eBSC Base Services are scalable and easily extensible system functionalities; they implement a kind of high availability mid-dleware and service applications for usage by the proprietary SW applications. They allow SW based redundancy to avoid future HW dependency.

Besides these services provide a set of APIs to enable highly available applications; before they can use the capabilities of the available services, the SW applications need “to subscribe” themselves to those they expect to use. Each of the Base Services may also use the functionalities of other services by subscribing to them.

The main basic Services are the following:

– Board Accessibility Service;– Message Service;– Availability Management Service;– Memory Replication Service;– Event Service.

Data Base Administration

The Functional Area "Data Base Administration" resides on several eBSC components (as many as possible according to systems architecture) and it is common to the BSC1 platform. The Data Base Administration software provides the capability to load the database of the peripheral processors and to align the database of the connected NE when required. It also provides the capability to load the internal processor local DBs for the following processors:

– AP;– UPM;– SMAC;– LIET.à

A copy of the database is stored on the system disk in order to provide the capability to restore, in case of system crash, the last saved Configuration in the BSS system. The Database software resides mainly on MCP processor (Central Administration part). A local administration part providesconfiguration data management for the AP processor.

Status Manager

This software functional area is common for the eBSC and BSC1, but the subsystem are mainly working on BSC1 performing the functions for maintaining under control the states of all the HW devices present in the BSC1 system. In particular all the requests for status transition are validated and propagated according to the predefined hierarchy of HW devices. Status manager software supports audit functions mainly to verify that the status information about the operational availability of a given device is consistent among the different eBSC processors bearing a software representation of the specific device.

Level2 Radio

This software functional area covers the various Level 2 HDLC protocol applications which can be found in the eBSC. The protocol applications are spread over the various Line Module blades. So, LIET and LISO blades host the applications supporting follow-ing HDLC-based protocols:

– LAPD linksto control BTSM (Abis) and TRAU (Asub);

46 A50016-G5100-A020-01-7618

TED:eBSC

Id:0900d805800e22a6

eBSC Software Architecture

– MTP-2 protocolto provide level 2 links to SS7 stack (A interface);– LAPB links to provide support for X25A connections over Asub. LAPB protocol is

actually terminated on MCP blade, and a gateway is needed to convey LAPB payload from Line Modules to MCP and vice versa.

Level3 Radio

The level3 Radio software subsystem is spread all over the AP blades. In general it has to be distinguished between two kinds of functionalities:

1. Central functionality: it is a functionality running only on one AP (AP Master) blade.2. Distributed functionality: it is a functionality running all over the AP blades.

The main Central functionalities are the following:

1. A and Lb interfaces messages handling up to SCCP included;2. PCU, pdt, Sccp and A timeslot handling procedures;3. The allocation of pdt resources;4. The storing of relation between each connection and the blade that connection is

running on;5. Cell Broadcast procedure;6. Network Assisted Cell Change (NACC) procedure;7. Sysinfo Handling;8. Paging procedure;9. Load balancing procedure.

The main Distributed functionalities, in general are the cell oriented functionalities, as follow:

1. the handling of calls (establishing, keeping, and releasing) related to the BTSMs the involved blade has in charge of Abis interface messages handling;

2. the allocation of Abis and radio resources;3. Sysinfo handling;4. Cell Overload;5. IMSI/Tracing procedure;6. Frequency redefinition;7. Location Service procedure.

The eBSC software architecture has determined a general rework of the L3 internal subsystem and process functionalities distribution. In general, it must be distinguished between APM (Central) and APD (distributed) specific functionality. The APM function-ality is the Layer3 functionality related to the procedures in some way centralised from the Call Processing point of view so, for example, not related to a specific connection-related procedure management. The APD is the functionalities related to all the internal procedures directly related to the single connection.

4.1 Flexible PCM Lines Configuration (Asub)BSS system supports flexible PCM line configuration from eBSC towards TRAUs and BTSs. In this case, PCM instances (PCMs) represent the connections between eBSC Line Module (LM-E1/T1). The Line Module (i.e. the LM-E1/T1) holds PCM line interfaces that are used as Abis or Asub interfaces by a switching network.

A50016-G5100-A020-01-7618

47


Id:0900d805800e22a6

Each dual line interface circuit can handle two PCM lines, in order to provide a line redundancy capability. An active or standby mode is used, when operating in this redun-dant mode. The line interface circuits are able to manage the individual 64 Kbps timeslots of the transmission media, either by a number of four independent 16 Kbps traffic channels (TCH/F) or by eight independent 8 Kbps traffic channels (TCH/H), to be connected at Asub interface side.

Without increasing the number of Line Modules, it is possible to increase the number of PCM instances (PCMs) that are configured. In fact, Line Module enables each of the PCM couples to be configured, either in the selection mode to keep trunks busy (even if not duplicated), or in transparent mode to keep only one trunk busy (configured sim-plex).

The configuration of PCM lines in the selection mode is represented on the left side of Figure 20, where 16 TRAU modules are connected to the Line Interface blade via dupli-cated lines on redundant links. At the right side, the figure shows the configuration of PCM lines in the transparent mode to connect 32 TRAUs modules via simplex lines. This TRAU flexibility is applied also to BTSs. This includes also a mixed configuration of inter-faces towards TRAUs modules and BTSs supported by the same Line Module.

Figure 20 PCM Lines Configuration in Selection and Transparent Mode

48 A50016-G5100-A020-01-7618

TED:eBSC

Id:0900d805800e22c8

Environmental Requirements

5 Environmental RequirementsIn this chapter the main eBSC environmental requirements are described.

5.1 Storage and TransportationThe criteria in this section apply to the equipment in its normal shipping container. The packaged equipment shall not be affected in its functional performances after it has been exposed to the environment described in Table 4:

5.2 Stationary Use IndoorThe Indoor equipment shall not be affected by the environmental conditions specified in ETS 300019-1-3 Recommendation, class 3.1. The environmental requirements together with the relevant test specifications are defined in Table 5.

Environment Storage Transport

Climatic conditions ETS 300 019-1-1 class 1.2EN 300 019-2-1 Test T 1.2

ETS 300 019-1-2 class 2.3EN 300 019-2-2 Test T 2.3

Biological conditions ETS 300 019-1-1 class 1.2 ETS 300 019-1-2 class 2.3

Chemically active sub-stances

ETS 300 019-1-1 class 1.2 ETS 300 019-1-2 class 2.3

Mechanically active sub-stances

ETS 300 019-1-1 class 1.2 ETS 300 019-1-2 class 2.3

Mechanical conditions ETS 300 019-1-1 class 1.2EN 300 019-2-1 Test T 1.2

ETS 300 019-1-2 class 2.3EN 300 019-2-2 Test T 2.3

Table 4 Storage and Trasportation

Environmental requirements Test specification

Climatic conditions for Base Station equipment EN 300019-2-3Test specification T3.1E- 5°C... + 45°C

Climatic conditions for eBSC, BSC1, RNC, TRAU

EN 300019-2-3Test specification T3.1+5°C... + 40°C

Chemically and mechanically active sub-stances

No test required (The characteristic severities of class 3.1 should be con-sidered when designing the equip-ment and when choosing components and materials)

Mechanical conditions EN 300019-2-3Test specification T3.2

Acoustic noise emission ETS 300753 (6), class 3.1Measurement method: ISO 7779

Table 5 Environmental Requirements for Stationary Use Indoor

A50016-G5100-A020-01-7618

49

TED:eBSC Environmental Requirements

Id:0900d805800e22c8

5.3 Electromagnetic Compatibility (EMC)

5.3.1 Emission Requirements

g The eBSC, BSC1, TRAU and the Radio Commander comply with Low Voltage Directive 73/23/eec and EMC Ditective 89/336/EEC.

5.3.2 Immunity Requirements

g The EN 50121-4 Recommendation is applicable for GSM-R equipment only.

Earthquake EN 300 019-2-3 chapter 4.2 (IEC 60721-2-6: Zone 4)

Environmental requirements Test specification

Table 5 Environmental Requirements for Stationary Use Indoor

eBSC, BSC1, TRAU: EN 300 386

EN 55022 Class B

FCC Part 15.107 Class A

FCC Part 15.109 Class A

eBSC, BSC1, TRAU: EN 300 386

EN 55024

EN 61000-6-2

50 A50016-G5100-A020-01-7618

TED:eBSC

Id:0900d805800e22d6

Product safety and EMF Protection

6 Product safety and EMF ProtectionIn this chapter some product safety and EMF protection rules for the eBSC system are presented.

6.1 Product SafetyThe eBSC Network Elements comply with the safety requirements of the standards listed in the Table 6.

6.2 Power Supply Interface

Europe / World North America

Safety of information technology equipment

IEC 60950-1 UL 60950-1

Radio Transmitting Equipment IEC 60215 −

Safety of laser products IEC 60825-1IEC 60825-2

UL 60950

Fire resistance IEC 60950(4.4, Annex A)

UL 60950UL 94

Table 6 Product Safety Requirements

Test Criteria Steady state voltage tolerance requirements

-48 V DC 230 V / 50 HZ AC 120 V / 60 HZ AC

Normal operation:

Within this voltage range no damage or dete-rioration of functional performance shall occur during and after the test. Performance of Base Station equipment shall meet the fol-lowing requirements of the relevant Air Inter-face standards:

- TX Modulation accuracy

- TX output power (only GSM)

- RX Reference sensitivity.

ETS 300 132-2:

- 40,5 to - 57,0 V

Line to neutral:207 to 253 V

47-53 Hz

Line to neutral:90 to 132 V

Line to line:180 to 264 V57 - 63 Hz

Table 7 Power Supply Interface Requirements

Date post:	06-Dec-2015
Category:	Documents
Upload:	sinasabikona
View:	2 times
Download:	0 times

tedebsc

Documents