product description of axc

8/14/2019 Product Description of AXC

http://slidepdf.com/reader/full/product-description-of-axc 1/171

Product Description of AXC

DN02166696Issue 22-0 en15/06/2007

# Nokia Siemens Networks 1 (171)

00039222.30

Nokia AXC - ATM Cross-connect C3.0



The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended for theuse of Nokia Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted inany form or means without the prior written permission of Nokia Siemens Networks. Thedocumentation has been prepared to be used by professional and properly trained personnel,and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomescustomer comments as part of the process of continuous development and improvement of thedocumentation.

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given “as is” and all liabilityarising in connection with such hardware or software products shall be defined conclusively andfinally in a separate agreement between Nokia Siemens Networks and the customer. However,Nokia Siemens Networks has made all reasonable efforts to ensure that the instructionscontained in the document are adequate and free of material errors and omissions. NokiaSiemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which

may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NOEVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUTNOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESSOPPORTUNITY OR DATA, THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THEINFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights andother intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners,and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2007. All rights reserved.

Hereby, Nokia Siemens Networks declares that this Nokia AXC ATM Cross-connect is incompliance with the essential requirements and other relevant provisions of Directive: 1999/5/ EC.

Nokia AXC will comply with the European Union RoHS Directive 2002/95/ EC on the restrictionof the use of certain hazardous substances in electrical and electronic equipment 1 July 2006 atthe latest. The directive applies to the use of lead, mercury, cadmium, hexavalent chromium,polybrominated biphenyls (PBB), and polybrominated diphenyl ethers (PBDE) in electrical andelectronic equipment put on the market after 1 July 2006.

FCC ID:PM5T55800 –01 This device complies with Part 15 of the FCC Rules. Operation issubject to the following two conditions: (1) This device may not cause harmful interference, and(2) this device must accept any interference received, including interference that may causeundesired operation.

2 (171) # Nokia Siemens Networks DN02166696Issue 22-0 en

15/06/2007




Contents

Contents 3

Summary of changes 7

1 Software licence terms for Nokia AXC 9

2 Nokia AXC 13

3 Transmission interface options 1 7

4 Licensing in AXC 23

5 Features 255.1 ATM capabilities 255.1.1 ATM cross-connecting 255.1.2 ATM service categories 275.1.3 BTS AAL2 multiplexing [application software] 285.1.4 Inverse Multiplexing for ATM (IMA) 305.1.4.1 Overdimensioning of IMA groups for PDH link protection 325.1.4.2 IMA configurations 325.1.4.3 IMA group timing 335.1.5 ATM over fractional E1/JT1/T1 [application software] 335.1.6 Circuit Emulation Service [application software] 34

5.1.7 Support for High Speed Downlink and Uplink Packet Access (HSDPA andHSUPA) 36

5.1.8 Path Selection 365.1.9 ATM over Ethernet [application software] 375.1.10 Traffic management functions 385.1.11 ATM interface oversubscription [application software] 415.1.12 ATM OAM functions 415.2 Integrated IP router 425.3 AXC protection options 435.4 E1/JT1/T1 interface operating mode 465.5 Performance monitoring 475.6 Synchronisation of AXC 49

6 AXC applications 516.1 Network applications of AXC 516.2 Site applications of AXC 526.3 Combining 2G and 3G traffic 556.4 Support for structured SDH networks 586.5 IP routing function of AXC 616.6 Nokia AXC Compact (AXCC and AXCD) 636.7 AXC node configuration 65

7 Management 697.1 Nokia AXC management 697.1.1 Nokia AXC management model 72

DN02166696Issue 22-0 en15/06/2007


Contents



7.2 Nokia AXC Manager 807.3 Nokia AXC-FB Hopper Manager 817.4 Nokia AXC automated commissioning concept 827.5 ATM layer configuration management for BTS 837.6 Q1 management 837.7 Neighbour Node Discovery (NND) 85

8 Mechanical structure 878.1 Nokia AXC mechanics 878.2 Stand-alone AXC mechanics 898.3 AXC power supply 918.4 DC-PIU 928.5 AXC unit LEDs 958.6 AXU 97

8.6.1 ATM cross-connect unit (AXU) 978.6.2 AXU functional blocks 988.7 AXCC/AXCD 1018.7.1 AXC Compact (AXCC/AXCD) 1018.7.2 AXCC/AXCD functional blocks 1038.8 IFUA/IFUD 1068.8.1 Interface units IFUA/IFUD 1068.8.2 IFUA/IFUD functional blocks 1088.9 IFUC 1128.9.1 Interface unit IFUC 1128.9.2 IFUC functional blocks 1138.10 IFUE 116

8.10.1 Interface unit IFUE 1168.10.2 IFUE functional blocks 1178.11 IFUF 1218.11.1 Interface unit IFUF 1218.11.2 IFUF functional blocks 1228.12 IFUG 1258.12.1 Interface unit IFUG 1258.12.2 IFUG functional blocks 1268.13 IFUH 1278.13.1 Interface unit IFUH 1278.13.2 IFUH functional blocks 128

9 Product structure 131

9.1 Delivery content of AXC 131

10 Technical specifications 13310.1 AXC performance 13310.1.1 Traffic capacity 13310.1.2 Operation 13710.2 AXC environmental requirements 14010.3 AXU 14210.3.1 AXU interfaces 14210.3.2 AXU power requirements 14210.3.3 AXU dimensions and weight 14310.4 AXCC 144

10.4.1 AXCC interfaces 144


15/06/2007




10.4.2 AXCC power requirements 14410.4.3 AXCC dimensions and weight 14510.5 AXCD 14510.5.1 AXCD interfaces 14510.5.2 AXCD power requirements 14610.5.3 AXCD dimensions and weight 14610.6 IFUA 14710.6.1 IFUA interfaces 14710.6.2 IFUA power requirements 14710.6.3 IFUA dimensions and weight 14810.7 IFUC 14810.7.1 IFUC interfaces 14810.7.2 IFUC power requirements 15010.7.3 IFUC dimensions and weight 150

10.8 IFUD 15110.8.1 IFUD interfaces 15110.8.2 IFUD power requirements 15110.8.3 IFUD dimensions and weight 15210.9 IFUE 15210.9.1 IFUE interfaces 15210.9.2 IFUE power requirements 15310.9.3 IFUE dimensions and weight 15410.10 IFUF 15410.10.1 IFUF interfaces 15410.10.2 IFUF power requirements 15610.10.3 IFUF dimensions and weight 156

10.11 IFUG 15710.11.1 IFUG interfaces 15710.11.2 IFUG power requirements 15710.11.3 IFUG dimensions and weight 15710.12 IFUH 15810.12.1 IFUH interfaces 15810.12.2 IFUH power requirements 15810.12.3 IFUH dimensions and weight 15910.13 Stand-alone mechanics 15910.13.1 S-AXC power requirements 15910.13.2 S-AXC dimensions and weight 16010.14 Nokia AXC Manager and Nokia AXC-FB Hopper Manager system

requirements 162

10.15 AXC standards 16310.15.1 Interface standards and recommendations 16310.15.2 ATM capabilities recommendations 16810.15.3 EMC standards 16910.15.4 Environmental standards 17010.15.5 Safety recommendations 171

DN02166696Issue 22-0 en15/06/2007


Contents




15/06/2007




Summary of changes

Changes between document issues are cumulative. Therefore, the latest

document issue contains all changes made to previous issues.

Changes between issues 22-0 and 21-0

The following sections have been added:

. Licensing in AXC

. Path Selection

. ATM over Ethernet

.

Interface unit IFUH and IFUH functional blocks . IFUH interfaces , IFUH power requirements , and IFUH dimensions

and weight

Information on IFUH interface unit has been added to sections

Transmission interface options and AXC node configuration .

Information on UBR+ has been added to section ATM service categories .

Information on HSUPA has been added to section Support for High Speed

Downlink and Uplink Packet Access (HSDPA and HSUPA) .

Information on Restricted Mode filtering has been added to sections

Integrated IP router and Nokia AXC management .

ATM over Ethernet counters have been added to section Performance

monitoring .

DN02166696Issue 22-0 en15/06/2007


Summary of changes




15/06/2007




1 Software licence terms for Nokia AXC

NTP licence statement

NTP (Network Time Protocol) is copyrighted © David L. Mills 1992-2001and comes under the following licence: "Permission to use, copy, modify,

and distribute this software and its documentation for any purpose and

without fee is hereby granted, provided that the above copyright notice

appears in all copies and that both the copyright notice and this permission

notice appear in supporting documentation, and that the name University

of Delaware not be used in advertising or publicity pertaining to distribution

of the software without specific, written prior permission. The University of

Delaware makes no representations about the suitability this software for

any purpose. It is provided "as is" without express or implied warranty."

STL licence statement

Standard Template Library (STL) Copyright © 1994 Hewlett-Packard

Company. Permission to use, copy, modify, distribute and sell this software

and its documentation for any purpose is hereby granted without fee,

provided that the above copyright notice appears in all copies and that

both that copyright notice and this permission notice appear in supporting

documentation. Hewlett-Packard Company makes no representations

about the suitability of this software for any purpose. It is provided "as is"

without express or implied warranty.

ChorusOS licence statement

ChorusOS r4.0.0 for PowerPC - Nokia uCM860 AXC Copyright (c) 1999

Sun Microsystems, Inc. All rights reserved. Copyright (c) 1992-1998

FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of

the University of California. All rights reserved.

SunSoft Internet Inter-ORB Protocol IIOP licence statement

This software product (LICENSED PRODUCT), implementing the Object

Management Group's "Internet Inter-ORB Protocol", is protected by

copyright and is distributed under the following license restricting its use.

Portions of LICENSED PRODUCT may be protected by one or more U.S.

DN02166696Issue 22-0 en15/06/2007


Software licence terms for Nokia AXC



or foreign patents, or pending applications. LICENSED PRODUCT is

made available for your use provided that you include this license andcopyright notice on all media and documentation and the software

program in which this product is incorporated in whole or part. You may

copy, modify, distribute, or sublicense the LICENSED PRODUCT without

charge as part of a product or software program developed by you, so long

as you preserve the functionality of inter-operating with the Object

Management Group's "Internet Inter-ORB Protocol" version one. However,

any uses other than the foregoing uses shall require the express written

consent of Sun Microsystems, Inc. The names of Sun Microsystems, Inc.

and any of its subsidiaries or affiliates may not be used in advertising or

publicity pertaining to distribution of the LICENSED PRODUCT as

permitted herein. This license is effective until terminated by Sun for failure

to comply with this license. Upon termination, you shall destroy or return allcode and documentation for the LICENSED PRODUCT. LICENSED

PRODUCT IS PROVIDED AS IS WITH NO WARRANTIES OF ANY KIND

INCLUDING THE WARRANTIES OF DESIGN, MERCHANTIBILITY AND

FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT, OR

ARISING FROM A COURSE OF DEALING, USAGE OR TRADE

PRACTICE. LICENSED PRODUCT IS PROVIDED WITH NO SUPPORT

AND WITHOUT ANY OBLIGATION ON THE PART OF SUN OR ANY OF

ITS SUBSIDIARIES OR AFFILIATES TO ASSIST IN ITS USE,

CORRECTION, MODIFICATION OR ENHANCEMENT. SUN OR ANY OF

ITS SUBSIDIARIES OR AFFILIATES SHALL HAVE NO LIABILITY WITH

RESPECT TO THE INFRINGEMENT OF COPYRIGHTS, TRADESECRETS OR ANY PATENTS BY LICENSED PRODUCT OR ANY PART

THEREOF. IN NO EVENT WILL SUN OR ANY OF ITS SUBSIDIARIES

OR AFFILIATES BE LIABLE FOR ANY LOST REVENUE OR PROFITS

OR OTHER SPECIAL, INDIRECT AND CONSEQUENTIAL DAMAGES,

EVEN IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH

DAMAGES.

Dataconnection licence statement

© COPYRIGHT DATA CONNECTION LIMITED 2002

GNU General Public License statement

The AXC embedded software contains a modified GNU tar-1.12 package

which is licensed under GNU General Public License, Version 2 and

software copyrighted by The Regents of the University of California,

Copyright (c) 1988, 1989, 1993. The source code is available at Nokia’s

Online Services at http://www.online.nokia.com/.

The AXC embedded software contains a modified OSPF routing daemon,

copyright (c) 1998 by John T.Moy. The OSPF routing daemon is licensed

under GNU General Public License, Version 2. The source code is

available at Nokia’s Online Services at http://www.online.nokia.com/.


15/06/2007




Rocksoft CRC licence statement

CRC Error Detection copyrighted (c) by Ross Williams, 1993

DHCP licence statement

The AXC embedded software contains a modified DHCP daemon,

Copyright (c) 1995, 1996, 1997, 1998, 1999 The Internet Software

Consortium - DHCP. All rights reserved.

Redistribution and use in source and binary forms, with or without

modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyrightnotice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright

notice, this list of conditions and the following disclaimer in the

documentation and/or other materials provided with the distribution.

3. Neither the name of The Internet Software Consortium - DHCP nor

the names of its contributors may be used to endorse or promote

products derived from this software without specific prior written

permission.

THIS SOFTWARE IS PROVIDED BY THE INTERNET SOFTWARECONSORTIUM AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR

IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THEIMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A

PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE

INTERNET SOFTWARE CONSORTIUM OR CONTRIBUTORS BE

LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,

EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT

NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR

SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS

INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF

LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY

OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE

POSSIBILITY OF SUCH DAMAGE.

gSOAP licence statement

Part of the software embedded in this product is gSOAP software.

Portions created by gSOAP are Copyright © 2001 –2004 Robert A. van

Engelen, Genivia, Inc. All Rights Reserved.

DN02166696Issue 22-0 en15/06/2007


Software licence terms for Nokia AXC



THE SOFTWARE IN THIS PRODUCT WAS IN PART PROVIDED BY

GENIVIA INC AND ANY EXPRESS OR IMPLIED WARRANTIES,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF

MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE

ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE

FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,

OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,

PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF

USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER

CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN

CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE

OR OTHERWISE) ARISING IN ANYWAY OUT OF THE USE OF THIS

SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH

DAMAGE.

OpenLDAP licence statement

THIS SOFTWARE IS PROVIDED BY THE OPENLDAP FOUNDATION

AND ITS CONTRIBUTORS ``AS IS'' AND ANY EXPRESSED ORIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A

PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE

OPENLDAP FOUNDATION, ITS CONTRIBUTORS, OR THE AUTHOR(S)

OR OWNER(S) OF THE SOFTWARE BE LIABLE FOR ANY DIRECT,

INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, ORCONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,

PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF

USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVERCAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN

CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE

OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS

SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH

DAMAGE.


15/06/2007




2 Nokia AXC

Nokia AXC is a transport node for third generation (3G) networks. It

functions as an ATM cross-connect device for Radio Access Network(RAN) that complies with 3GPP standards. Nokia AXC supports all

relevant international standards.

Nokia AXC provides a wide range of interfaces for transporting the 3G

ATM-based traffic over the existing transmission networks. Nokia AXC

interfaces support all different transmission media: wireline, optical fibre,

and microwave radio.

Because it is possible to use the existing plesiochronous digital hierarchy

(PDH) and synchronous digital hierarchy (SDH) transmission

infrastructure, investments in a separate ATM network are not required.

Consequently, the co-siting of GSM/EDGE/PDC and WCDMA basestations is a viable option and provides a possibility to save significantly in

site acquisition costs. Physical transmission links can be shared betweenthe 2nd and 3rd generation, or traffic in fixed networks. This ensures a

smooth evolution path towards the 3G environment.

There are three node alternatives for Nokia AXC:

. modular embedded Nokia AXC (AXUA/B + one or more IFUs)

. Nokia AXC Compact (AXCC and AXCD)

. Stand-alone AXC (S-AXC)

The modular embedded Nokia AXC and Nokia AXC Compact function as

integrated transport nodes for Nokia WCDMA base stations and Triple-

Mode Nokia UltraSite EDGE base stations (with WCDMA upgrade kit).

The S-AXC is a stand-alone network element.

Each modular embedded AXC or S-AXC node consists of an ATM Cross-

Connect Unit (AXU) and a number of transmission interface units (IFUs).

Because of the modular design of Nokia AXC, different types of interfaces

can flexibly be configured to meet the current transmission requirements

up to the maximum ATM switching capacity of 1.2 Gbit/s. Whenever traffic

DN02166696Issue 22-0 en15/06/2007


Nokia AXC



volumes increase and additional transmission interfaces are required, new

AXC transmission interface units can simply be added. They can beinserted either into a WCDMA BTS cabinet or into a subrack located, for

example, in a Nokia UltraSite Supreme/Optima site support cabinet. For

more information, refer to AXC node configuration.

The non-expandable Nokia AXC Compact contains AXU and IFU

functionality in a single unit.

Figure 1. AXC hardware image in Nokia AXC Manager

Modular embedded Nokia AXC

The modular embedded AXC is fully integrated into Nokia WCDMA base

stations and Triple-Mode Nokia UltraSite EDGE base stations (with

WCDMA upgrade kit). It interconnects and multiplexes the traffic from

different sectors of the BTS. It connects the BTS to the Radio Network

Controller (RNC) through the Iub interface. Moreover, it is capable of cross-

connecting traffic between other BTSs and the RNC.


15/06/2007




The modular embedded AXC also provides the clock to the BTS reference

clock circuitry. The clock can be either recovered from the transmissionnetwork or received from an external clock input or from the internal clock

of the AXU.

Nokia AXC Compact (AXCC and AXCD)

Nokia AXC Compact is an optimized AXC node solution for tail sites and

small hubs. Like the modular embedded Nokia AXC, it is fully integrated

into Nokia WCDMA base stations and Triple-Mode Nokia UltraSite EDGE

base stations (with WCDMA upgrade kit) and used for interconnecting and

multiplexing the traffic from different sectors of the BTS.

Stand-alone AXC (S-AXC)

The Stand-alone AXC (S-AXC) can be installed in a standard ETSI or 19-

inch rack, and co-located with a BTS or RNC site. The S-AXC can also be

installed in Nokia UltraSite Supreme/Optima site support cabinet. It is used

for multiplexing and cross-connecting traffic between different base

stations and the RNC.

Typically, the Stand-alone AXC:

. acts as an ATM traffic concentrator also in locations other than BTSs

sites. functions as transmission interface converter towards the RNC

. provides extra interfaces at base stations locations

. provides circuit emulation services

. acts as an SDH mapping converter from VC-4 to VC-12

DN02166696Issue 22-0 en15/06/2007


Nokia AXC




15/06/2007




3 Transmission interface options

Nokia AXC transmission interface units (IFUs) provide the physical

connection from Nokia WCDMA base stations to Radio Access Network.The units handle the mapping of ATM cells into transmission frames, cell

delineation, and monitoring of transmission signals. They feature options

for wireline, fibre optic, and radio transmission.

Whenever transmission capacity needs to be upgraded, new transmission

interface units can easily be added to Nokia AXC node. Because Nokia

AXC supports hot insertion, interface units can be added or replaced

without disturbing the operation of the node.

The interface units can be installed in Nokia UltraSite WCDMA base

stations, Nokia MetroSite WCDMA base station, Triple-mode Nokia

UltraSite EDGE base station and in an S-AXC. The actual number of unitsthat can be installed depends on the type of the base station. The S-AXC

can house five interface units.

Nokia AXC supports any combination of IFUs as long as the following

rules are respected:

. the maximum switching capacity is not exceeded

. the maximum number of powered FlexiHoppers is nine

. only IFUG and IFUH interface units can be installed with Nokia AXC

Compact (AXCC and AXCD)

. the number of logical interfaces is less than or equal to 32

Each physical interface E1, JT1, T1, STM-1, or OC-3 counts as one

logical interface. However, several physical interfaces can be

grouped together so they count as one logical interface. An IMAgroup containing E1, JT1 or T1 physical interfaces, E1s within

Flexbus interfaces or VC-12 each count as one logical interface.

DN02166696Issue 22-0 en15/06/2007


Transmission interface options



IFUA

. eight symmetrical PDH interfaces that are software configurable as

either E1 (8 x 2.048 Mbit/s), JT1 (8 x 1.544 Mbit/s) or T1 (8 x 1.544

Mbit/s)

. each of the interfaces can be deployed as plain ATM E1/JT1/T1 links

or assigned to the Inverse Multiplexing for ATM (IMA) function

. ATM over fractional E1/JT1/T1 [application software]

. CES for structured or unstructured E1/JT1/T1 [application software]

IFUC

. three optical STM interfaces, each of which can be configured

independently as either STM-1 mapping VC-4 (155.52 Mbit/s) or

OC-3 (155.52 Mbit/s)

. interface protection MSP 1:1 [application software]

IFUD

. eight coaxial PDH interfaces for E1 (8 x 2.048 Mbit/s)

. each of the interfaces can be deployed as plain ATM E1 links or

assigned to the Inverse Multiplexing for ATM (IMA) function. ATM over fractional E1 [application software]

. CES for structured or unstructured E1 [application software]

IFUE

. three Flexbus interfaces, each with up to 16 x E1 (2.048 Mbit/s)

. provides Flexbus connection to Nokia MetroHopper and Nokia

FlexiHopper radios, and to Nokia GSM/EDGE base stations

.

can be connected directly to another Flexbus interface (IFUE, FIU19(E), RRIC, FXC RRI)

. each of the E1 links within Flexbus interface can be deployed as

plain ATM E1 links or assigned to the Inverse Multiplexing for ATM

(IMA) function

. CES for unstructured E1 [application software]

. 2 Mbit/s cross-connections between Flexbus interfaces

. up to three radio outdoor unit power feeds


15/06/2007




. Q1 branching function via Flexbus interfaces for connecting other

Q1 network elements. 16 x E1 add-drop capacity to AXU

. Hot Standby for Flexbus 1 and Flexbus 2 for protecting connected

Nokia FlexiHopper microwave radio outdoor units

IFUF

. one optical interface for structured STM-1 (155.52 Mbit/s)

connections

. up to 63 VC-12 with IMA

. interface protection MSP 1:1 [application software]

IFUG

. eight 10 BaseT Ethernet ports

. connects external equipment on the AXC site to the common DCN

IFUH

. ATM over Ethernet for BTS [application software] using MPLS/IP

encapsulation with PWE3. two Fast Ethernet interfaces and one Gigabit Ethernet interface

(optical, SFP module is optional)

. one of the interfaces can be used to offload Iub traffic to Ethernet,

inside a Pseudowire tunnel towards the RNC

. provides ATM cell throughput of at least 60 Mbit/s for each direction

(uplink and downlink), fulfilling the throughput requirements imposed

by HSDPA and HSUPA features

. cannot be used with stand-alone AXC

AXCC

. combines AXUB and IFUA functionality in a single unit

. eight symmetrical PDH interfaces that are software configurable as

either E1 (8 x 2.048 Mbit/s), JT1 (8 x 1.544 Mbit/s) or T1 (8 x 1.544

Mbit/s)

. each of the interfaces can be deployed as plain ATM E1/JT1/T1 links

or assigned to the Inverse Multiplexing for ATM (IMA) function

DN02166696Issue 22-0 en15/06/2007





. CES for structured or unstructured E1/JT1/T1 [application software]

. non-expandable; only IFUG and IFUH interface units can be added

AXCD

. combines AXUB and IFUD functionality in a single unit

. eight coaxial PDH interfaces for E1 (8 x 2.048 Mbit/s)

. each of the interfaces can be deployed as plain ATM E1 links or

assigned to the Inverse Multiplexing for ATM (IMA) function

. CES for structured or unstructured E1 [application software]

. non-expandable; only IFUG and IFUH interface units can be added

Figure 2. Interface options for AXC

For more information on the AXC units and possible configurations, refer

to the following sections:

. AXC node configuration

. ATM cross-connect unit (AXU)

. Nokia AXC Compact (AXCC and AXCD)

. Interface unit IFUA/IFUD

AXC

IFUE

IFUCIFUF

IFUA, IFUDAXCC/D

FlexiHopper or MetroHopper radio

Nokia GSM/EDGE BTS

2G BTS via CES(Nokia and other)

ATM leased lines or SDH equipment

Leased lines or PDH/SDH equipment

AXU

IFUG

IP-managedequipment on site

IFUH

Ethernet network(e.g. xDSL, MetroEthernet)


15/06/2007




. Interface unit IFUC

. Interface unit IFUE

. Interface unit IFUF

. Interface unit IFUG

. Interface unit IFUH

DN02166696Issue 22-0 en15/06/2007






15/06/2007




4 Licensing in AXC

The use of certain software in Nokia AXC is controlled by licences. Such

software is called application software and it can be used only after obtaining and installing a valid licence.

The application software in the AXC consists of the following:

. ATM interface oversubscription

. ATM over Ethernet

. ATM over fractional E1/JT1/T1

. BTS AAL2 multiplexing

.

Circuit emulation service. Interface protection for IFUC and IFUF

. UBR+

The licences are AXC-specific and tied to the AXC backplane serial

number. Generation and distribution of the licences is only possible via

NetAct. See NetAct documentation for more details.

Nokia AXC contains a temporary licence that can be used for configuring

application software even though a valid licence is not yet available. The

temporary licence expires after 90 days. The temporary license periodstarts when a licensed functionality is configured into use.

DN02166696Issue 22-0 en15/06/2007


Licensing in AXC




15/06/2007




5 Features

5.1 ATM capabilities

5.1.1 ATM cross-connecting

The evolving end user services - be it voice, data or multimedia - require

flexible transmission in terms of variable bit rates, real-time transmission,

and efficient usage of transmission capacity. ATM has been chosen by the

international standardisation bodies as the transmission technology for the

3G networks because it can fulfil these demands as well as the related

requirements on quality of service.

ATM cross-connect unit (AXU)

Nokia AXC serves as a Virtual Path (VP) and Virtual Channel (VC) cross-

connect device for semi-permanent ATM connections.

The ATM Cross-connect unit (AXU) is the master unit which controls the

Nokia AXC node. AXU performs the main ATM functionality for

communication within the base station, as well as for the connections to

other network elements. The ATM switch fabric of the AXU enables flexible

cross-connections simultaneously on both VP and VC level.

Switching and interface capacity

Because of the modular design of Nokia AXC, different types of interfaces

can be flexibly configured to meet the transmission requirements. The

maximum bidirectional ATM switching capacity of the AXU is 1.2 Gbit/s.

The switching capacity of Nokia AXC Compact is 165 Mbit/s.

AXU supports 1000 simultaneous connections and AXC Compact 250simultaneous connections.

DN02166696Issue 22-0 en15/06/2007


Features



Supported VPI/VCI bits

The Virtual Path Identifier (VPI) indicates the virtual path, and the Virtual

Channel Identifier (VCI) the virtual channel over which an ATM cell will be

routed. The table below shows the default number of bits supported for VPI

and VCI on physical/logical interfaces.

Table 1. Supported VPI/VCI bits

Bits (AXC and S-AXC) Bits (AXC Compact)

VPI 1 –8 (default 4) 1 –5 (default 2)

VCI 1 –12 (default 7) 7

In AXC and S-AXC, the sum of bits used for VPI/VCI per interface cannot

exceed 13. The VPI/VCI bit range can be increased to a maximum of 13

bits in up to 14 interfaces. Alternatively, the range can be increased to 12

bits in up to 32 interfaces.

In AXC Compact, the number of VCI bits for each logical interface is

always 7. The default number of VPI bits is 2. It can be changed as long as

the number of logical interfaces is smaller than 8. The number of VCI

blocks required by an interface is 2 to the power of VPI bits (2VPI bits) and

the sum of VCI blocks cannot exceed 32. For example, it is possible to

have one interface with 3 VPI bits and 6 interfaces with 2 VPI bits (2 3 * 1 +

22 * 6 = 32).

Note

VCIs from 0 to 7 are not configurable. VCIs from 8 to 31 are

configurable but should not be used. They are reserved by

standardisation bodies for other purposes.

VC 21 in VP 0 is configurable but should not be used. It is reserved for Neighbour Node Discovery which is an ATM end-to-end management

feature.

Virtual Channel connections between BTS and RNC

Nokia AXC connects at least five Virtual Channels (VC) in the Iub interface

between the base station and radio network controller. Four VCs arerequired for user plane and control plane connections between the BTS

(WAM) and the RNC. The fifth VC connection is required for Operation and

Maintenance traffic (DCN).


15/06/2007




5.1.2 ATM service categories

Nokia AXC supports ATM service categories CBR and UBR, as defined by

the ATM Forum. These are applicable to both semi-permanent Virtual Path

Connections (VPC) and semi-permanent Virtual Channel Connections

(VCC).

Constant Bit Rate (CBR)

Constant Bit Rate (CBR) service category has been defined for

connections that continuously require a constant bit rate. The bandwidth is

further determined by the Peak Cell Rate (PCR). For CBR services, there

is a defined Quality of Service guaranteed, if the peak cell rate is not

exceeded. CBR connections can transport data at peak cell rate withouthaving an impact on the Quality of Service of other connections.

CBR supports real time applications that have strong requirements for Cell

Transfer Delay (CTD) and Cell Delay Variation (CDV). ATM cells for which

the maximum cell delay variation is exceeded are discarded. Typical

applications are voice traffic, video-conference, and circuit emulation. In

Nokia AXC, CBR is used for user plane and control plane traffic.

Unspecified Bit Rate (UBR)

Unspecified Bit Rate (UBR) has been specified for services that have noreal time requirements. Because Quality of Service is not guaranteed, the

connection has to be secured on higher layers. UBR services are also

called "best-effort" services. A typical application is data transfer such as

file transfer or management data. In Nokia AXC, UBR is used for O&M

traffic.

UBR+ [application software]

UBR+ is an extension of the UBR service category and implemented by

the parameter Minimum Desired Cell Rate (MDCR). Even when the traffic

load is high, an UBR+ connection guarantees a throughput of at least the

rate specified by the MDCR, but at the same time allows the UBR+

connection to take up the interface cell rate entirely.

Furthermore, Nokia implementation provides the user with an additional

parameter called UBRshare that makes it possible to favour individual

UBR+ connections. The amount of bandwidth that an UBR+ connection

obtains above its MDCR depends on the current traffic conditions and the

proportion of its UBRshare value to the sum of UBRshare values of all

UBR+ connections on the same ATM interface.

DN02166696Issue 22-0 en15/06/2007


Features



5.1.3 BTS AAL2 multiplexing [application software]

ATM technology for transport in 3G Radio Access Networks provides

statistical multiplexing gain and consequently the available network

capacity is utilised very efficiently. An even higher statistical multiplexing

gain is achieved by using AAL2 connections that allow multiple WCDMA

voice and data cells to be conveyed on one ATM connection (CBR VCC,

for example).

The purpose of BTS AAL2 multiplexing is to further reduce the number of

VCCs for AAL2 user plane traffic and AAL2 signalling traffic in the I ub

interface compared to the number of termination points in the BTS. This

means that otherwise fragmented resources are bundled up and the user

plane data uses less bandwidth than the sum of the peak bandwidths that

the multiplexed streams require. The number of VCCs that are required in

the Iub interface depends on the traffic mix for which the transport capacity

has been dimensioned.

Without BTS AAL2 multiplexing there is one or two AAL2 user plane VCCs

and one AAL2 signalling link between the AXC and RNC for each AAL2

termination point of the BTS. The figure below shows an example of a

situation in which only one AAL2 user plane VCC is in use.

Figure 3. Without BTS AAL2 multiplexing

BTS

AXC

RNC

WAM

WAM

WAM

VPC

Sector 1

Sector 3

Sector 2

User traffic

AAL2SIG

User traffic

User traffic

AAL2SIG

AAL2SIG


15/06/2007




Figure BTS AAL2 multiplexing shows how AAL2 connections from several

BTS AAL2 termination points are multiplexed into one or more (dependingon the traffic load) user plane AAL2 VCC connections between the BTS

and RNC. In a similar way, the AAL2 connections reaching the BTS from

RNC are switched into the AAL2 terminating points (1 or 2) of the WAMs.

Figure 4. BTS AAL2 multiplexing

AAL2 signalling messages are exchanged between the AAL2 signalling

entities via point-to-point VCC connections. With BTS AAL2 multiplexing,

only one AAL2 signalling VCC between the RNC and each BTS is needed.

Each WAM has its own unique A2EA address. Nokia AXC does not need

any A2EA but only uses this address to route the signalling messages tothe right destination. AAL2 signalling entities are located in the RNC, AXC

and BTS (WAM).

Capacity

In theory, one AAL2 user plane VCC can contain up to 255 AAL2 channels

(255 CIDs). However, only 248 channels are available, as CID range from

0 to 7 is reserved for Layer Management purposes. As long as there is

sufficient bandwidth available and less than 248 channels are occupied,

one VCC will be sufficient. Another VCC is needed if either the bandwidth

or the number of channels per VCC is too small or more than 248 AAL2

channels are required per each WAM. Nokia AXC is able to multiplex/

demultiplex AAL2 connections of up to 6 WAMs via Iub.

BTS AXC RNC

AAL2

WAM

WAM

WAM

VPC

Sector 1

Sector 3

Sector 2

1

2

3

User traffic

AAL2SIG

DN02166696Issue 22-0 en15/06/2007


Features



Capacity savings can be notable when the need to configure VCCs on I ub

is minimised. However, the VCCs need to be calculated according to theplanned traffic capacity during network dimensioning. The more traffic

there is to and from the base stations the more VCCs are still needed.

System requirements

Transmission plans and network element configurations must be updated.

The configurations in the AXCs, BTSs and RNCs need to be changed so

that the new (reduced) number of VCCs is applicable.

In order to use BTS AAL2 multiplexing, an AXUB unit or Nokia AXC

Compact (AXCC/D) is needed. A valid licence file is also required.

BTS AAL2 multiplexing is not available for stand-alone AXC.

Benefits

BTS AAL2 multiplexing provides the following benefits:

. depending on the traffic mix and the parameters, the Iub transmission

capacity savings can be notable

. the number of VCCs between the RNC and BTS is minimised

. better trunking gain is achieved

. only one AAL2 signalling Virtual Channel Connection (VCC) per BTS

is needed instead of one for each Wideband Application Manager

(WAM)

. transmission network planning is simplified because transmission

capacity can be calculated for the entire BTS instead of each sector

. Iub fragmentation is significantly decreased

. HSDPA is more efficiently supported if two or more active WAMs are

installed

5.1.4 Inverse Multiplexing for ATM (IMA)

Inverse Multiplexing for ATM (IMA) enables efficient transport of

broadband ATM traffic in the existing PDH/VC-12 transmission network.

This technique allows to combine several physical links into one logical

link and saves capacity by enabling the division of a high bandwidth ATM

data stream into several lower bit rate PDH/VC-12 transmission links. The

data stream can then be recombined at the far end without affecting the

original ATM cell order.


15/06/2007




The main benefits of IMA are:

. the transmission network becomes transparent for ATM

. capacity is saved because of better utilisation of E1/JT1/T1/VC-12

connections

. VP/VCs bigger than one single link can be transported by creating n

x E1/JT1/T1/VC-12 bit pipes

. IMA via FlexiHopper or n x E1 provides an “intermediate hierarchy”

before SDH/SONET

Figure 5. Principle of Inverse Multiplexing for ATM (IMA)

The transmitting end of an IMA link aligns the transmission of IMA frames

on all physical links. This allows the receiving end to adjust to differential

link delays from which the physical links belonging to the IMA group suffer.This is done by measuring the arrival times of the IMA frames on each

physical link. This ensures that the receiving end of the IMA link can

recreate the original ATM cell stream and pass it back to the ATM layer.

The maximum Differential Link Delay (DLD) that the IMA engine can

tolerate is 25 ms.

Single ATMcell stream fromATM layer

Original ATMcell stream toATM layer

IMA GroupLink 0

Link 1

Link 2

TX direction cellsdistributed acrosslinks in round robinsequence

RX direction cellsrecombined intosingle ATM stream

PHY

PHY

PHY

IMA Group

PHY

PHY

PHY

DN02166696Issue 22-0 en15/06/2007


Features



5.1.4.1 Overdimensioning of IMA groups for PDH link protection

Resilience of IMA groups against IMA link failures can provide a means for

PDH link protection. If a link in an IMA group fails, the IMA engine is able to

recover and reassign the distribution of ATM cells to the other PDH links in

the same IMA group. As a result, the IMA group remains operational even

though its capacity is reduced. The recovery time of the IMA engine upon

PDH link failure is approximately 2 seconds.

The minimum number of active IMA links that allows a group to stay active

is specified in Nokia AXC Manager by the parameter Minimum Number of

Links. An IMA group becomes unavailable if the number of operative links

in the group is less than the value of the parameter.

The ATM bandwidth specified for an IMA group is not dependent on the

Minimum Number of Links. It can be higher, lower or equal to the

bandwidth implied by the parameter value. Note that the ATM Connection

Admission Control (CAC) does not receive direct information on the IMA

layer status. Therefore, if the amount of traffic is greater than the available

links can carry and buffers are full, ATM cells will be discarded.

A link becomes operationally unavailable when transmission failures (such

as LOS or LOF) are detected.

5.1.4.2 IMA configurations

IMA functionality is supported by the PDH/VC-12 transmission interface

units, and it can easily be configured with Nokia AXC Manager. One IMA

link can be assigned to each PDH transmission interface. All links within

one IMA group must be from the same transmission interface unit. In IFUE,

the IMA groups can cross Flexbus interfaces.

The IMA functionality of the IFUs can be configured as follows:

. IFUA: 1 to 4 IMA groups, with 1 to 8 E1/JT1/T1 links per IMA group

. IFUD: 1 to 4 IMA groups, with 1 to 8 E1 links per IMA group

. IFUE: 1 to 8 IMA groups, with 1 to 8 E1 links per IMA group

. IFUF: 1 to 16 IMA groups, with 1 to 32 VC-12 links per IMA group

. AXCC: 1 to 4 IMA groups, with 1 to 8 E1/JT1/T1 links per IMA group

. AXCD: 1 to 4 IMA groups, with 1 to 8 E1 links per IMA group


15/06/2007




5.1.4.3 IMA group timing

Common transmit clock mode (CTC) is supported. The Tx timing link is

configurable in AXC per IMA group. The received clock signal of the

selected Tx timing link is used as the clock signal for all links of the IMA

group in Tx direction.

5.1.5 ATM over fractional E1/JT1/T1 [application software]

The use of fractional E1, JT1 or T1 enables the adding of full or partial E1/

JT1/T1 channels filled with 3G traffic into existing 2G traffic, without

disturbance. The timeslots within a standard PCM frame can be freely

shared between ATM and TDM traffic with a granularity of 64 kbit/s. Figure ATM over fractional E1/JT1/T1 gives an example of multiplexing of ATM

traffic into TDM traffic with the help of ATM over fractional E1/JT1/T1.

Figure 6. ATM over fractional E1/JT1/T1

For example, each of the eight interfaces in IFUA can be configured to

operate as either ATM over E1/JT1/T1 or ATM over fractional E1/JT1/T1.

In the fractional E1/JT1/T1 links, the timeslots that are unused by ATM

traffic can be filled with TDM traffic by external 64 kbit/s cross-connects

(Nokia Talk Family BTS, Nokia MetroHub and Nokia UltraSite GSM/EDGEBTS).

In a fractional interface, a number of PDH timeslots are reserved for ATM

traffic. The following characteristics apply to the PDH structures and the

usage of fractional interfaces in Nokia AXC:

. E1 frame contains 32 timeslots

. JT1 frame contains 24 timeslots

. T1 frame contains 24 timeslots

ATM/FractE1/JT1/T1

TDM/E1/JT1/T1 64k XC 64k XC

E1/JT1/T1

TDM/E1/JT1/T1

ATM/FractE1/JT1/T1

AXC

IFUA/D

2G BTS 2G BTS

AXC

IFUA/D

DN02166696Issue 22-0 en15/06/2007


Features



The timeslots in an E1 frame are numbered from 0 to 31. Timeslot 0 is

reserved for functions of the physical layer such as framing, alarmindications, performance monitoring and so on. Therefore, timeslot 0 of E1

frames cannot be used for fractional interfaces. Timeslot 16 is typically

used for the transport of signalling information. Therefore, it is normally not

possible to use timeslot 16 for fractional interfaces. However, Nokia AXC

Manager provides the option to use the timeslot 16. The usage of fractional

interfaces for E1 is characterized by a number of timeslots (N, N=1, 2, ...,

31).

The timeslots in a JT1 or a T1 frame are numbered from 1 to 24. The

physical layer functions which are performed by timeslot 0 in E1 are done

by specific F bits of the JT1 frame structure which are not included in any

of the 24 timeslots. The usage of fractional interfaces for JT1 ischaracterized by a number of timeslots (N, N=1, 2, ..., 24).

The actual timeslots, which are configured for fractional interfaces, are

always from 1 to N. Timeslots that are configured for fractional interfaces

have to start from timeslot 1 and they have to be contiguous.

Note

Fractional E1/JT1/T1s are not supported by Nokia AXC Compact.

5.1.6 Circuit Emulation Service [application software]

Circuit Emulation Service (CES) is a technique that allows mapping TDM

traffic into ATM cells. It is supported by interface units IFUA, IFUD and

IFUE and Nokia AXC Compact (AXCC/D).

It is not recommended to use CES with the interface unit IFUH (ATM over

Ethernet).

CES for unstructured E1/JT1/T1 emulates a point-to-point E1/JT1/T1

circuit, which means that the complete E1/JT1/T1 frame is transported

within ATM cells (granularity of E1/JT1/T1).

CES for structured E1/JT1/T1 emulates a point-to-point fractional E1/JT1/

T1 circuit, where only the timeslots filled by the TDM signal are transported

within ATM cells (granularity of 64 kbit/s). One contiguous block of

timeslots starting with any timeslot can be configured.


15/06/2007




The CES pass-through function of Nokia AXC is an internal CES function

that allows to perform a TDM cross-connection by setting up a circuitemulation service simultaneously on two AXC interfaces with an

associated ATM connection (see 1 in the figures below). Pass-through is

available for AXCC/D, IFUA, IFUD and IFUE (unstructured).

The CES can be terminated either in the same AXC (1 in the figures

below) or another AXC (2 in the figures below).

Note

Nokia AXC supports up to 32 CES connections. Each CES connection

equals one logical ATM interface.

Figure 7. CES for unstructured E1 in AXC

AXC

IFUA/D

e.g. IFUC

AXC

ATM

NetworkATM

CES(unstructured)

CES(unstructured)

ATM

E1/TDM

E1/TDM

E1/TDM

(1)

(2)

(2)

IFUA/D

IFUA/D

e.g. IFUC

(1)

(2)

A T M

c r o s s - c o n n e c t i o n

A T M

c r o

s s - c o n n e c t i o n

A T M


CES

CES

CES

DN02166696Issue 22-0 en15/06/2007


Features



Figure 8. CES for structured E1 in AXC

5.1.7 Support for High Speed Downlink and Uplink Packet Access (HSDPAand HSUPA)

Nokia AXC hardware supports both High Speed Downlink and Uplink

Packet Access (HSDPA and HSUPA) that provide high data rate

transmission in a WCDMA downlink and uplink, ensuring that usersrequiring effective multimedia capabilities benefit from data rates

previously unavailable because of limitations in the radio access network.

Nokia AXC supports HSDPA also for configurations where BTS AAL2

multiplexing application software is utilised and two user plane VCCs are

configured per WAM. These VCCs require a CBR Traffic Descriptor with aPeak Cell Rate of up to 40000 cells/s.

5.1.8 Path Selection

Path Selection enables separating AAL2 traffic to up to three different path

types:

AXC

IFUA/D

e.g. IFUC

AXC

ATM

NetworkATM

CES(structured)

CES(structured)

ATM

(1)

(2)

(2)

IFUA/D

IFUA/D

e.g. IFUC

(1)

(2)

A T M

c r o s

s - c o n n e c t i o n

A T M


A T M


CES

CES

CES

FractionalE1/TDM

FractionalE1/TDM

FractionalE1/TDM


15/06/2007




. stringent

. stringent bi-level

. tolerant

Nokia recommends that the stringent path is used for RT-DCH, stringent

bi-level for NRT-DCH, and tolerant for HSDPA/HSUPA.

The AXC allows for configuring any AAL2 path type to any ATM service

category. The characteristics of an AAL2 path type are determined by the

AAL2 Connection Admission Control.

Other application software, such as UBR+ and ATM over Ethernet, can becombined with Path Selection to provide further benefits for AAL2 traffic.

5.1.9 ATM over Ethernet [application software]

ATM over Ethernet, enabled by the IFUH interface unit, is one of the

building blocks of Hybrid BTS Backhaul. It is targeted to help the operators

to cope with the growing HSDPA peak rates by backhauling the BTS traffic

over a packet-switched Ethernet connection. It is possible to use either a

Fast Ethernet or an optical Gigabit Ethernet interface (SFP is optional) of

the IFUH for the connection. The ATM cell throughput of IFUH is at least 60

Mbit/s for each direction (uplink and downlink), fulfilling the throughputrequirements imposed by HSDPA and HSUPA. The IFUH can be used

with both modular embedded Nokia AXC or AXC Compact, but not with

stand-alone AXC.

In a typical configuration, the TDM connection is still used for DCH traffic

and synchronisation. Path Selection is used to separate the traffic.

It is also possible to use the packet-switched Ethernet connection for all

the traffic between the RNC and the BTS, as shown in the following figure.

In such a case, synchronisation signal must be provided by other means,

for example, a neighbouring BTS.

DN02166696Issue 22-0 en15/06/2007


Features



Figure 9. ATM over Ethernet

The Ethernet interface is used to establish a Pseudowire tunnel towards

the RNC. The tunnel contains up to six separate Pseudowires. Each

Pseudowire can be used to convey a certain traffic class. The ATM cells

are encapsulated in IP packets and transported inside the Pseudowires.

The encapsulation stack is MPLS over IP.

Bi-Directional Forwarding Detection (BFD) provides a mechanism to

monitor the operation of each Pseudowire. If a broken Pseudowireconnection is detected, an alarm is raised.

5.1.10 Traffic management functions

Nokia AXC features a set of traffic and congestion control functions which

help to ensure network efficiency and fulfil the defined Quality of Service

objectives.

VCC

VCC

VCC

VCC

VCC

VCC

AXC RNCIFUH

PWE3Gateway

PSN Tunnel

VCC

VCC

VCC

VCC

VCC

VCC

RT

NRT

ControlPlane

HSDPA

HSUPA

O&M

Pseudowire

Pseudowire

RT

NRT

ControlPlane

HSDPA

HSUPA

O&M

VPC

VPCs to/fromother Node Bs


15/06/2007




Connection Admission Control (CAC)

Nokia AXC checks the consistency of VPI/VCI values to determine

whether a VP/VC connection request may be accepted. Nokia AXC also

checks if new VPCs or VCCs can be accepted considering the total

capacity requirements of all connections and the available capacity of the

physical/logical interface.

As far as IMA groups are concerned, CAC accepts the requests based on

the number of available links in the IMA group.

User –Network Interface (UNI)

User-Network Interface (UNI) and Network Node Interface (NNI) signallingis transparent to Nokia AXC. However, Nokia AXC supports UNI cell

header format. Nokia AXC is uncontrolled ATM equipment, and therefore

the Generic Flow Control (GFC) bits are fixed to zero.

Usage Parameter Control (UPC)

The network monitors and controls that the traffic contract is respected in

terms of the traffic offered and the validity of the ATM connections. UPC is

performed at the UNI, and the UPC function can be enabled or disabled for all connections at an interface.

Nokia AXC provides a means to detect malicious connections. Non-

conformant traffic is either tagged (CLP=0 toggles to CLP=1) or discarded.

The Cell Delay Variation Tolerance (CDVT) value is used by the usage

parameter control algorithm that checks the conformance to the declared

cell rates of an observed cell stream.

The table below illustrates the actions for non-conforming cells of a cell

stream that consists of cells with CLP=0 and CLP=1 depending on the

conformance tests. UBR.2 is typically used together with Partial Packet

Discard (PPD).

Table 2. Conformance test definitions for UPC

Conformance test Parameters Action for non-

conforming cells

CBR.1 PCR; CDVT Discard cell

UBR.1 PCR; CDVT Discard cell

UBR.2 PCR; CDVT Toggle CLP=0 to CLP=1

(tagged)

DN02166696Issue 22-0 en15/06/2007


Features



Traffic shaping for CBR connections

Traffic shaping alters the traffic characteristics of a VPC/VCC cell stream in

order to achieve better network efficiency. In Nokia 3G Radio Access

Network the traffic sources (RNC and BTS) already provide sufficient

shaping features. In addition, Nokia AXC features a traffic shaping

functionality for CBR cross-connections on both VP and VC level. Traffic

shaping is performed with respect to the Peak Cell Rate (PCR) specified in

the traffic descriptor of the CBR connection.

CBR VPs that contain UBR cross-connections. To achieve VP shaping in

this case, the access profile bandwidth can be reduced on the interface.

CBR connections below 5000 cells/s that do not originate in the AXC arenot re-shaped.

It is possible to define up to 32 different traffic descriptors. Each of the CBR

connections must be associated with one traffic descriptor. However, traffic

descriptors can have identical peak cell rates. The definition of the PCRvalues has a granularity which is always less than 1.5% of the desired

value of the PCR. For PCR values less than 10 Mbit/s, the granularity in

the definition of the PCR is better than 0.2%.

Traffic shaping for UBR connections

Unspecified bit rate (UBR) traffic is normally used for DCN connections

that are terminated in the integrated IP router of Nokia AXC. The traffic that

is generated by this router is shaped according to the PCR that is specified

in the traffic descriptor of each DCN connection.

Queuing

Weighted fair queuing (WFQ) is used for unspecified bit rate (UBR) and

shaped virtual clock scheduling for CBR connections.

Early Packet Discard and Partial Packet Discard (EPD/PPD)

Nokia AXC features both Early Packet Discard (EPD) and Partial Packet

Discard (PPD) for VC connections carrying AAL5 traffic. EPD occurs in

case the ATM buffer is congested and exceeds the defined EPD limit. PPD

applies for cells that are to be discarded due to policing violation, Cell Loss

Priority (CLP) threshold violation, or because no free buffer space is

available.


15/06/2007




5.1.11 ATM interface oversubscription [application software]

ATM interface oversubscription allows for configuring the ATM bandwidth

of an interface independent of the physical bandwidth available.

Oversubscription can be used, for example, between two Stand-alone

AXCs (or a Standalone AXC and an embedded AXC in a Node B), of

which one concentrates the traffic from several Node Bs and the other

provides the connection to the RNC. In such a situation, oversubscription

provides the means to dimension the capacity of the physical trunk

transport to be smaller than the combined transport capacity allocated to

the Node Bs whose traffic it is concentrating. This is feasible because

typically all of the Node Bs do not generate their maximum traffic volume

simultaneously.

The physical bandwidth and the ATM interface bandwidth are controlled by

two different functional layers:

. the physical layer function adapts the ATM traffic rate to the physical

line rate. The physical layer inserts idle ATM cells if it does not

receive any user ATM cells from the ATM layer.

. the ATM layer function provides traffic management, such as

Connection Admission Control (CAC), and performs the traffic

scheduling among the ATM service categories and ATMconnections.

As long as the actual traffic volume does not exceed the physical

bandwidth, all ATM traffic management functions work in the usual

manner. However, if the ATM interface oversubscription is in use and the

traffic exceeds the physical bandwidth, the AXC starts to buffer and

eventually discard ATM cells. Therefore, the AXC provides counters that

can be used for monitoring the actual traffic load on the physical interface

in both egress and ingress directions.

5.1.12 ATM OAM functions

Virtual Path (F4) and Virtual Channel (F5) AIS & RDI (end-to-end)

The OAM cell flows can be used for monitoring end-to-end connections on

Virtual Path and Virtual Channel level. There are two types of alarms that

are generated in error situations. Alarm Indication Signal (AIS) sends an

error message to the direction of the signal and Remote Defect Indication

(RDI) sends an error message to the transmitting terminal.

DN02166696Issue 22-0 en15/06/2007


Features



5.2 Integrated IP router

Up to 96 VCCs can be terminated in the integrated IP router of Nokia AXC.

Some of these VCCs are used for the DCN connections between the AXC

and BTS, Neighbour Node Discovery and AAL2 signalling, but the

remaining VCCs can be used to access the DCN. Each Operation and

Maintenance VCC can be used for several IP routes.

AXC is also capable of directly connecting IP over ATM streams on the

ATM level. The connections are handled as normal ATM connections.

These features enable the integrated IP router to support a variety of DCN

topologies. For more information, see IP routing function of AXC . Nokia

AXC supports unnumbered links.

In addition, an Ethernet-based Local Management Port (LMP) is available

at the front panel of Nokia AXC. It is needed for local management of bothNokia AXC and WCDMA base station. Nokia AXC provides two different

modes concerning the LMP: restricted and unrestricted mode. In the

restricted mode, it is not by default possible to access network elements

other than the local AXC/BTS via the LMP. However, the user can define a

set of exception rules to the restricted mode so that any IP packet that

matches any of these rules is not discarded.

In the unrestricted mode, network elements other than the local AXC/BTScan be freely accessed using the Local Management Tool (LMT).

The functions of the integrated IP router can be further extended with IFUG

application. For more information, see AXC with Ethernet hub extension.

Open Shortest Path First (OSPF)

Open Shortest Path First (OSPF) routing protocol is used for updating the

IP routing tables automatically in the RAN DCN. The routes are calculated

on the basis of the number of routers, transmission speed, delays and

route cost. Each AXC node is configured to belong to a certain OSPF area

and all the nodes in the same area share the same routing information.Between the OSPF areas, the routing information is exchanged through

area border routers. Area border routers are typically RNCs.

Dynamic Host Control Protocol (DHCP)

Dynamic Host Control Protocol (DHCP) enables dynamic IP host

configuration. Nokia AXC acts as a DHCP server for the clients connected

to the LMP or IFUG unit. The clients can be either static equipment (such

as a site support cabinet) or dynamic equipment (such as a laptop for local

management). Each client receives its IP address only for a certain pre-


15/06/2007




defined period of time (lease time that can vary between one week and

one month). After this period of time, the client has to renew its lease. If thelease is not renewed, the address becomes free and the DHCP server can

allocate it to another client.

proxyARP

ProxyARP is an address resolution protocol which enables an

intermediate device to send an ARP response to the requesting host on

behalf of the end node. Using proxyARP means that all IP traffic directed

to the base station is handled and routed by the AXC. In this way, the BTS

and AXC can use the same subnet and IP addresses are used more

efficiently.

inATMARP

Inverse ATM Address Resolution Protocol (inATMARP) is a protocol that

enables the automatic detection of IP addresses on ATM interfaces. This

makes the configuration of the DCN connections much faster since only

the public IP address of the AXC node has to be set during configuration.

5.3 AXC protection options

Nokia AXC features interface protection mechanisms that enable the

network operator to maintain the transmission service in the event of

failure. A protection mechanism is activated whenever failures are

detected either in the physical connections between network elements or

within network elements on particularly critical functional modules.

IFUC and IFUF interface protection [application software]

Redundant physical SDH/SONET links may be established for protection.

When an external failure is detected in a physical link or IFU, protection

switching is executed automatically from one physical interface to another.

Nokia AXC supports MSP 1:1 interface protection for STM and STS

interfaces. In MSP 1:1, the protecting interface starts to carry user traffic

once the main link breaks down. The maximum switching time is 50 ms.

The switchover is triggered by the following events:

. alarms

. SDH: LOS, LOF, MS-AIS, MS-EBER, EBER-Path

. SONET: LOS, LOF, AIS-Line, EBER-Line, EBER-Path

DN02166696Issue 22-0 en15/06/2007


Features



. MSP/linear APS protocol (K1-K2 messages received from far-end

line end point). IFUC/IFUF removed

. operator request

Nokia AXC supports MSP1:1. MSP1:1 with MSP1+1 compatibility is

interoperable with MSP 1+1 implemented in Nokia RNC. Nokia AXC also

operates with third-party equipment that supports MSP1:1 or MSP1+1

compatible with MSP1:n as described in G.783, Annex A.

IFUF can be protected with another IFUF unit. With IFUC, protecting

interfaces can be on the same or another IFUC. The following rules applywhen configuring IFUC interface protection (interface 1 is the topmostinterface, interface 2 is in the middle and interface 3 is at the bottom of the

frontpanel:

. interface 1 of a unit can be protected by interface 1 of another unit or

any interface 3

. interface 2 of a unit can be protected by interface 2 of another unit or

any interface 3

. interface 3 of a unit can be protected by interface 3 of another unit

It is recommended to reserve interface 3 as the protecting interface as it

can be used to protect any other interface.

Unit protection can be implemented easily by using a configuration shown

in the figure below.


15/06/2007




Figure 10. Unit protection for IFUC units

Note

Nokia AXC supports 8 SDH/SONET interfaces and can use up to 7

additional SDH/SONET interfaces for protection. Interfaces used for

protection cannot carry additional ATM user traffic.

IFUE interface protection

Redundant PDH link air interface protection for Nokia FlexiHopper (Plus)

and MetroHopper radios is also possible. Flexbus interfaces 1 and 2 can

protect each other (Hot Standby).

Working IFUC

AXU

IF 1

IF 2

IF 3

Protecting IFUC

IF 3

IF 2

IF 1

DN02166696Issue 22-0 en15/06/2007


Features



Figure 11. Hot Standby for IFUE units

IFUE also supports the following propagation protection modes:

. space diversity

. frequency diversity

. polarisation diversity

In each propagation protection mode, the configuration includes one

indoor unit and two outdoor units.

5.4 E1/JT1/T1 interface operating mode

E1/JT1/T1 interfaces can automatically detect if they need to operate in

short or long haul mode. This means that depending on the used cable

and its length (and thus the attenuation the cable adds), the IFUA and

IFUD interface units of Nokia AXC adopt the required mode. The followingtable shows the supported attenuation ranges for E1/JT1/T1 interfaces in

short and long haul modes.

Table 3. Attenuation ranges for E1/JT1/T1 interfaces

Operating mode Attenuation range

Short haul max. 10 dB

Long haul max. 30 dB

IFUE

IF1

AXU

IF2

Outdoor unit A

Outdoor unit B

Outdoor unit A

Outdoor unit B


15/06/2007




JT1 and T1 require a line build-out setting that adjusts the TX power

output.

5.5 Performance monitoring

Performance information is collected, for example, during commissioning

to detect possible wrong configurations, during normal operation to detect

possible future failures, or during network optimisation to predict

bottlenecks in the network and the most critical links. Nokia AXC Manager

provides the following Performance Monitoring (PM) features:

Physical performance monitoring for E1, JT1, T1, STM-1, and OC-3

interfaces:

. unavailable seconds

. errored seconds

. severely errored seconds

. background block errors

. interface protection switches for STM-1 and OC-3 interfaces

Physical performance monitoring for ATM over Ethernet interfaces:

. number of received Ethernet frames on the link, both errored and

non-errored

. number of transmitted Ethernet frames on the link

. number of received Ethernet frames with FCS errors

. number of frames received on the link that were discarded because

of an unknown or unsupported protocol

.

number of Ethernet TX frames that were discarded due to rateshaping

. number of received Ethernet frames with an unknown VLAN ID

. number of received Ethernet frame bytes, both errored and non-

errored

. number of transmitted Ethernet frame bytes

. number of received Ethernet frames with a PSN header that is

incorrect or has a reserved value

DN02166696Issue 22-0 en15/06/2007


Features



PSN tunnel performance monitoring for ATM over Ethernet interfaces:

. number of received Ethernet frames with the Pseudowire header not

configured or with a reserved value

. number of packets received on the PSN tunnel

. number of packets transmitted on the PSN tunnel

IMA performance monitoring for E1, JT1, T1 and VC-12 interfaces:

. IMA control protocol cell violations

. severely errored seconds

. unavailable seconds

. Tx and Rx unusable seconds for the network element (Near and Far

End)

. number of one second intervals where the GTSM is down

. number of NE group failure condition entrances (Near and Far End)

. Tx and Rx link failure counts (Near and Far End)

. Ouf of IMA Frame anomalies per link

. Tx and Rx stuffing events per link

ATM performance monitoring for E1, JT1, T1, STM-1, OC-3, VC-12, and

ATM over Ethernet interfaces:

. number of HEC errors cells per TCTT (Transmission Convergence

Trail Termination Point)

. discarded cells due to HEC violation

. discarded cells due to protocol errors

. number of Tx and Rx cells per VC, SDH interface, IMA group and AXC

. number of Tx and Rx cells per QoS traffic class (CBR, UBR)

. number of discarded cells due to buffer overflow per AXC

. number of Tx and Rx cells discarded due to EPD and PPD per AXC

. number of Rx cells tagged due to Policing per AXC


15/06/2007




. number of Rx cells dropped by UPC per AXC

. number of seconds for which the used bandwidth of an ATMinterface is less than a certain ratio of its maximum bandwidth (0-

25%, 25-50%, 50-75%, 75-87.5% or 87.5-100%)

ATM performance monitoring for AAL5 connections:

. sum of invalid Convergence Sublayer (CS) field errors

. CRC violations

ATM performance monitoring for BTS AAL2 multiplexing:

. number of AAL2 CPS packets discarded due to CPS HEC errors

. number of succeeded and rejected connection establishments per

VC TP

. number of Tx and Rx messages in AAL2 signalling layer per VC TP

. SSCOP connection monitoring counter and errored PDUs counter

Further performance data can be collected on the Flexbus interfaces of

IFUE. For more information, refer to Maintaining Nokia FlexiHopper (Plus) and MetroHopper with IFUE .

Information on AXC counters is also available via Nokia Online Services.

For more information on AXC performance monitoring support in NetAct,

please refer to Nokia NetAct documentation.

5.6 Synchronisation of AXC

The clock distribution circuitry of Nokia AXC is located in the AXU. It

provides a reference clock for all the transmission interface units, and for

the BTS Wideband Synchronisation and Clock Unit (WSC).

The reference clock can be either recovered from any physical interface,

received from an external timing source, or from an internal reference. The

user can define a primary and a secondary reference clock source for

Nokia AXC. For example, an STM-1 interface can be selected as the

primary and a PDH interface as the secondary reference clock source. It is

also possible to select an external timing source as the primary reference

clock. If the primary reference clock source is lost, Nokia AXC switchesfirst to the secondary reference clock source, then into hold-over mode for

up to 24 hours, and after this to free-run mode.

DN02166696Issue 22-0 en15/06/2007


Features



The radio network controller (RNC) provides the primary reference clock

source for all other RAN network elements and as Nokia AXC connectsthe BTS to the RNC it also acts as a synchronisation interface between the

two elements. This is the preferred option for synchronisation.

Synchronisation Status Messages (SSM) are used to trace the source of

the synchronisation signals distributed via physical transmission lines.

Nokia AXC supports SSMs in transparent mode only, passing all

messages through without using the information.

The synchronisation signal can also be received from an external timing

source. The AXU features an interface for external reference clock (ERC)

input using different clock source options: 1.544 MHz, 2.048 MHz and 2

Mbit/s. Nokia AXC Compact does not support a 2 Mbit/s clock source, but

a spare PDH interface can be used for that purpose.

The internal clock source is only used if no other reference clock is

available. The internal clock source of the Nokia AXC is compliant withStratum 4E in free running mode and with G.813 in locked mode.

The synchronisation functions can be controlled with Nokia AXC Manager.


15/06/2007




6 AXC applications

6.1 Network applications of AXC

Nokia AXC transfers ATM traffic to the I ub interface between the base

station and the radio network controller. It can also interconnect different

base stations in the network topology.

Nokia AXC enables the WCDMA networks to fully utilise PDH and SDH

technologies in access networks, and thus there is no need to implement

an ATM-based core network. ATM cells from WCDMA base stations are

carried in PDH/SDH frames or virtual containers as the PDH/SDH network

delivers the bandwidth the ATM layer needs.

Figure Example of Radio Access Network transmission topologies

illustrates different network topologies that can be implemented using the

transmission capability of Nokia AXC.

DN02166696Issue 22-0 en15/06/2007


AXC applications



Figure 12. Example of Radio Access Network transmission topologies

For more information on various transmision network topologies refer to

Nokia UltraSite WCDMA Product Overview , Nokia UltraSite System Overview , and Nokia MetroSite System Overview .

6.2 Site applications of AXC

Nokia AXC interconnects and multiplexes traffic from different sectors of

the base station. Nokia AXC connects the base station to the radionetwork controller (RNC) and it can also cross-connect traffic between

other base stations and the RNC.

Iub

Iur Iur

Iu

n X E1 leased linesPDH radioSDH radioSDH optical fibre

RNC

SGSN

RNC

RNC

BTS

BTSBTS

BTSBTS

BTS

BTS

BTS

BTS

BTS

BTS

BTS

BTS

BTS

BTS

BTS

BTS

BTSBTS

BTS

MSC

STM-1 LOOP63 x 2M

PDH LOOP16 x 2M


15/06/2007




Furthermore, the Stand-alone AXC can act as an ATM traffic concentrator

also in locations other than base station sites, function as a transmissioninterface converter towards the RNC and provide extra interfaces at base

station locations.

Figure 13. Example of BTS-integrated Nokia AXC in a simple tree network

topology

Virtual Path switching for chained base stations

A Virtual Path (VP) can be terminated in Nokia AXC when the Virtual

Channels (VC) from the VP are cross-connected to different sectors of the

base station. Alternatively, a VP can be cross-connected to other base

stations further down in the network. In this way, several base stations can

be chained via the same STM-1 interface leaving from the RNC.

BTS Cabinet

Sector

Sector

Sector

Sector

Sector

Sector AXC

RNCIntegrated

ATM

functionality

RNC

BS Cabinet

Sector

Sector

BTS Cabinet

AXC

Sector

Sector

Sector Sector

BS Cabinet

Sector

BTS Cabinet

AXC

Sector

Sector

DN02166696Issue 22-0 en15/06/2007


AXC applications



Figure 14. VP switching for chained base stations

Virtual Channel switching for chained base stations

A VP is terminated in Nokia AXC and VCs from this VP can either be

cross-connected to different sectors of the base station or, via other

transmission interfaces, to other base stations further down in the network.

BTS

BTS

IntegratedATM

functionality

RNC

AXC

VP

VC

AXC


15/06/2007




Figure 15. VC switching for chained base stations

6.3 Combining 2G and 3G traffic

Nokia AXC provides different solutions for combining 2G (TDM) and 3G

(ATM) transmission. Nokia AXC can be connected to external PDH or

SDH/SONET equipment which can be used to add and drop traffic at E1/

JT1/T1 or STM-1 level. The required cross-connections can be performed

by, for example, Nokia MetroHub or 2G BTS-integrated transmission units.

Nokia AXC offers traffic grooming functions for combining 2G and 3G

traffic. There are various options for traffic grooming:

. ATM over fractional E1/JT1/T1

. Circuit Emulation Service (CES)

. Grooming at E1 granularity

BTS

BTS

AXC

VP

VC

IntegratedATM

functionality

RNC

AXC

DN02166696Issue 22-0 en15/06/2007


AXC applications



Nokia AXC enables the use of existing transmission infrastructure for the

3G solution. The existing spare capacity can also be taken into use. Thetransmission of co-sited base stations can be combined, for example, by

using fractional E1, JT1 or T1. In Nokia AXC, fractional E1, JT1 or T1 is

implemented by the IFUA and IFUD interface units.

In addition, the possibility to connect external cross-connect or

transmission equipment to Nokia AXC further increases the configuration

options. Nokia AXC provides inter-connection to Nokia MetroHopper and

Nokia FlexiHopper (Plus) radios as well as to Nokia GSM/EDGE base

stations. This is implemented by the Flexbus interfaces of the IFUE

interface unit that can be installed to Nokia AXC. IFUE can be directly

connected to Nokia MetroHopper and Nokia FlexiHopper (Plus) but also to

other Nokia PDH microwave radio indoor units, like RRIC, FXC RRI, FIU19(E) or another IFUE.

Figure Combining 2G and 3G transmission at shared sites illustrates how

2G and 3G traffic can be combined at shared sites. In this example, radio

links are used for connecting shared base station sites and the BSC/RNC.

When introducing WCDMA into the existing networks, the ATM traffic from

3G base station (Iub interface) can be transported via Nokia AXC (for

example, over an E1 link) to the co-sited 2G base station. The BSC and

RNC are connected to the underlaying base stations via a hub (for

example, Nokia MetroHub). The Stand-alone AXC co-sited with BSC/RNC

may be used as an ATM hub.


15/06/2007




Figure 16. Combining 2G and 3G transmission at shared sites

Figure 2G and 3G traffic sharing illustrates the combining of 2G and 3G

traffic with existing Nokia products in more detail. When using the TDM

layer for sharing transport links, ATM-based WCDMA Iub traffic is

transported over STM-1, E1/JT1/T1 or fractional E1 connections. The

WCDMA base station is connected to the GSM/EDGE base station or to

an external transmission node.

Introducing WCDMA:- 2G BTS allocates capacity to 3G BTS- PDH/SDH transmission supported- physical link devices supported

Growth of WCDMA:- optionally ATM based transportfor 2G traffic(3G BTS allocatescapacity to 2G BTS)

- Stand-alone AXC available as ATM hub

GSM/EDGE BTSwith PDHcross-connect

2G

AXC

3G

WCDMA BTSwith AXC

HUB PDH hub

HUBATM hub(S-AXC)

IUB AXC

3G2G

IUB AXC

3G2G

Combined Abis

+IUB

(IUB

mapped into E1sor fractional E1s)

Combined Abis

+IUB

(IUB

mapped into E1sor fractional E1s)

HUBBSC

RNC

Abis AXC

3G2G

A bis AXC

3G2G

HUBBSC

RNC

CombinedIUB

+Abis

(Abis

over ATM)

CombinedI

UB +A

bis

(A bis over ATM)

DN02166696Issue 22-0 en15/06/2007


AXC applications



Figure 17. 2G and 3G traffic sharing

Grooming at E1 granularity

2G and 3G traffic can also be combined with a granularity of E1. In the

IFUE interface unit, the 16 E1 links of a Flexbus interface can be freely

shared between ATM and TDM based traffic. Thus, for each Flexbus

interface, it is possible to mix a number n of independent E1 signals with a

broadband ATM signal with a bandwidth of m x E1, when n + m ≤ 16 .

6.4 Support for structured SDH networks

In addition to STM-1 with VC-4 mapping, Nokia AXC provides support for

structured STM-1 with IFUF interface unit. This offers the opportunity to

terminate VC-12 Virtual Containers at Nokia WCDMA BTS or S-AXC

locations.

NOKIAMETRO

HUB

Site 1

AXU

I

F

U

A

Site 2

RRIC

RRIC

NOKIATALKBTS

NOKIAFlexiHopper Microwave

radio

NOKIA UltraSiteWCDMA BTS

OptimaAXC

Site 3

NOKIA

UltraSite BTSGSM/EDGE

FXC RRI

FXC RRI

FXC E1/T1

FXCRRI

FXCRRI

FXCRRI

Flexbus16x2M

TO BSC/RNC

16X2Mbit/s

PDHLOOP 1.) FIU 19

2.) MetroHub3.) AXC

AXU

IFUA

AXC

NOKIAUltraSiteWCDMABTS Optima


15/06/2007




Figure Structured SDH network shows how Nokia S-AXC or modular

embedded Nokia AXC equipped with IFUF interface units can be deployedin an exemplary network. The S-AXC can be used for VC-12/VC-4

interface conversion between the SDH network and RNC, and as a hub for

VC-12/Flexbus interface conversion.

Figure 18. Structured SDH network

If a legacy structured SDH network exists or the offered structured SDH

leased lines are more attractive to an operator as ATM-based leased lines,

some advantages can be achieved. These are the reduction of

transmission cabling cost, the improvement of reliability and the improved

manageability of changes. Furthermore, the necessity of external

equipment that would consume valuable site space is further reduced.

As Figure IFUF application shows, Nokia AXC offers even the possibility of

adding and dropping, for example, E1 traffic from another WCDMA base

station or third-party microwave radio equipment. The IMA function of IFUF

can be used to combine several E1s (mapped into VC-12s) to an IMA

group.

BTS WCDMA BTS

S-AXCSTM-1VC-12

RNC

STM-1

VC-4

3xE1

3xE1

9xE1

9xE1

3xE1

3xE1

3xE1

3xE16xE1

3xE1

STM-1

VC-12

STM-1

VC-12

BTS

BTS

BTS BTSBTS

BTS

BTS

BTS BTS

BTSBTS

BTS

BTS

S-AXC3xE1

3xE1

SDH transport(e.g. STM-1or STM -16)

SDHmux

SDHmux

SDHmux

DN02166696Issue 22-0 en15/06/2007


AXC applications



Figure 19. IFUF application

Up to 16 interfaces are supported between each IFUF and the ATM switch

fabric. These 16 interfaces can be any mixture of single E1s and n x E1

IMA groups. The figure below illustrates how it is possible to connect up to

62 Node Bs (each with one or two E1s) to the RNC with one S-AXC.

E.g. 4 xE1 IMA

E.g. 24 xVC-12 IMA

A X U A / B

I F U E

I F U F

I F U A

STM-1 (VC-12)

based network

Towards other

BTSs

E1-basednetwork


15/06/2007




Figure 20. S-AXC connectivity

6.5 IP routing function of AXC

The embedded IP router of Nokia AXC enables not only star but also tree

Data Communication (DCN) topologies in Nokia RAN.

A X U A / B

I F U F

I F U C

I F U F

A X U A / B

I F U F

I F U C

I F U F

Node B 1

Node B 62

...

1-2 E1

1-2 E1

AXC1 AXC2

SDHnetwork

One STM-1 carries thetraffic from 15 and theother from 16 NODE Bs

STM-1 (VC-12)

STM-1 (VC-12)

RNC

STM-1 (VC-4)

STM-1 (VC-4)

STM-1

(VC-12)STM-1

(VC-12)

DN02166696Issue 22-0 en15/06/2007


AXC applications



In the star alternative, there are point-to-point ATM connections

established between the RNC and each Nokia WCDMA base station. Inthis case only the O&M data of the base station itself is routed (and

terminated) on the IP level in AXC, whereas the O&M data for other base

stations is cross-connected on the ATM level. This results in a more simple

IP network topology but on the other hand in a more complex ATM

topology.

In a tree topology, there is only one O&M channel between adjacent AXCs.

The user traffic related connections are cross-connected and the ATM

connection for O&M is terminated in each base station. Thus, the O&M

data of the base station itself and also that of the other base station in the

subtree is routed in AXC. This leads to a more complex IP but a simple

ATM topology.

Figure 21. DCN tree and star topologies

Nokia AXC with Ethernet hub extension

The IP routing function of Nokia can be extended with the IFUG interface

unit that acts as an Ethernet hub collecting IP traffic (typically Operation

and Maintenance traffic) from other co-located Nokia or third-party

equipment, such as Nokia RealTilt control unit and various IP-managed

Tree Topology

Star Topology

BTS

AXC

BTS

AXC

BTS

AXC

BTS

AXC

AXC

BTS

RNC

VC Termination

VC Connection

Physical Connection

AXC

BTS

AXC

BTS

Router


15/06/2007




Nokia AXC Compact supports CES and BTS AAL2 multiplexing

application software.

AXCC provides eight symmetrical E1/JT1/T1 connections with IMA and

AXCD eight coaxial E1 connections with IMA. Both units support ATM VP

and VC cross-connections and their maximum switching capacity is 165

Mbit/s.

Nokia AXC Compact has limited possibilities for expansion, but it is

possible to add IFUG and IFUH interface units.

Figure 23. Nokia AXC Compact applications

S-AXC RNC

BTS

BTS

BTS

BTS

2xE12xE1

2xE1

2xE1

Star topology

BTS RNC

BTS

BTS

5xE1

2xE1

1xE1

Tree topology

2xE1 5xE13xE1RNCBTSBTS BTS

Tail sites

BTSWCDMA BTSwith AXCC/D


15/06/2007




6.7 AXC node configuration

Nokia AXC provides a maximum ATM switching capacity of 1.2 Gbit/s,

which can be shared by the transmission interfaces of up to five IFUs. The

actual number of IFUs that can be installed depends on the type of the

base station. The stand-alone AXC can house five IFUs. Any mixture of

interface units is supported (for more information, see Transmission

interface options).

Nokia AXC Compact (AXCC and AXCD) provides a maximum ATM

switching capacity of 165 Mbit/s and has limited possibilities for expansion.

No additional IFUs apart from one or more IFUGs and one IFUH can be

installed.

Note that only one IFUH is supported for each AXC or AXC Compact.

IFUH cannot be installed in stand-alone AXC.

Table 4. Minimum and maximum configuration for AXC plug-in units

AXU IFUs AXC Compact

Nokia UltraSite WCDMA

BTS Supreme

1 1 –5 1 with 1 –4 IFUG/

IFUHs


BTS Optima Indoor / Optima

Compact Outdoor

1 1 –3 1 with 1 –2 IFUs

(IFUGs/IFUH)

Nokia MetroSite WCDMA

BTS

1 1 1 with no IFUs

Nokia MetroSite 50 BTS 1 1 1 with no IFUs

Nokia Triple-Mode UltraSite

EDGE BTS

1 1 1 with no IFUs

Nokia Stand-alone AXC 1 1 –5 -

The AXU unit and AXC Compact are always installed in slot 1. With certainrestrictions any combination of IFUs can be installed to the remaining

slots.

The following table shows the maximum number of AXC interfaces in

Nokia WCDMA base stations and in the Stand-alone AXC. Note that all

maximum numbers of interfaces cannot be used simultaneously.

DN02166696Issue 22-0 en15/06/2007


AXC applications



Table 5. Maximum number of physical/logical interfaces in Nokia WCDMA

BTSs and S-AXC

AXC installation

environment

Transmission

interface type

Max. number of physical

interfaces


BTS Supreme

E1/JT1/T1

STM-1/OC-3

STM-1 (structured)

Flexbus

ATM over Ethernet

40 with IMA, 32 without IMA

8

5

9*

1


BTS Optima and Optima

Compact

E1/JT1/T1

STM-1/OC-3

STM-1 (structured)

Flexbus

ATM over Ethernet

24 with/without IMA

8

3

9

1

Nokia MetroSite WCDMA

BTS

E1/JT1/T1

STM-1/OC-3

STM-1 (structured)

Flexbus

ATM over Ethernet

8 with/without IMA

3

1

3

1

Nokia MetroSite 50 BTS E1/JT1/T1

STM-1/OC-3

STM-1 (structured)

Flexbus

ATM over Ethernet

8 with/without IMA

3

1

3**

1

Nokia UltraSite Edge Triple

Mode BTS (WCDMA part)

E1/JT1/T1

STM-1/OC-3

STM-1 (structured)

Flexbus

ATM over Ethernet

8 with/without IMA

3

1

3

1

Nokia Stand-alone AXC E1/JT1/T1

STM-1/OC-3

STM-1 (structured)

Flexbus

40 with IMA, 32 without IMA

8

5

9*


15/06/2007




* Nine remote power feeds from IFUE to Nokia Microwave Radio Outdoor

Unit are supported. The total number of Flexbus interfaces can be 15 inNokia UltraSite WCDMA BTS Supreme and Nokia S-AXC.

** Two remote power feeds to outdoor units are supported by MetroSite 50

BTS.

Note

Each IFUE can add/drop a maximum of 16 times E1 to the switch fabric

of AXC. Each IFUF can add/drop either a maximum of 16 plain VC-12s

or up to 63 VC-12s distributed over a maximum of 16 IMA groups (withup to 32 IMA links) to the AXC switch fabric.

Each of these E1 or VC-12 connections counts as one logical interface,

and AXC supports a maximum of 32 logical interfaces. It is therefore

recommended to group them using IMA.

DN02166696Issue 22-0 en15/06/2007


AXC applications




15/06/2007




7 Management

7.1 Nokia AXC management

Nokia AXC features a CORBA based management protocol that complies

with the NWI3 interface specification.

Nokia AXC can be managed with Nokia NetAct network management

system or Nokia AXC Manager. Both of them use the same network

management interface to Nokia AXC.

The remote management communication takes place via an inband Data

Communications Network (DCN) channel using IP over ATM. Each Nokia

AXC node features an integrated IP router for routing management traffic.

For example, if the DCN traffic for several base stations is cross-

connected in the AXC, the DCN traffic for the base stations that are below

the AXC in the network topology does not have to be terminated in the

AXC. Each AXC in such a topology can perform IP routing and therefore a

great variety of DCN topologies can be realised with the integrated IP

router. For more information, see IP routing function of AXC .

There are two types of AXC user accounts, local and remote. Information

on remote user accounts is stored and managed in a centralized LDAP

directory. The account information can only be changed in Nokia NetAct.Each user account has a profile that defines which operations the user is

able to perform in the AXC. All possible operations are grouped into six

areas, such as transmission configuration and software management.

The IP over ATM connections for WAMs are fixed. Each WAM uses the

same VPI/VCI value for the VCC, which is terminated in Nokia AXC. Nokia

AXC will by default configure all connections between all installed WAMs.

WAMs are also connected to all other WAMs in the same base station for

internal communication. These connections also use fixed VPI/VCI values.

DN02166696Issue 22-0 en15/06/2007


Management



IP over ATM connections can use both UBR and CBR service category.

However, using CBR leads to unnecessary reservation of bandwidth.Therefore, UBR is the recommended service category for IP over ATM

connections.

A crossed Ethernet based Local Management Port (LMP) on the front

panel of the AXU provides further management access. A laptop can be

used to access the node via the LMP located in the AXU unit. Nokia AXC

provides two different modes concerning the LMP: restricted and

unrestricted mode. In the restricted mode, it is not by default possible to

access network elements other than the local AXC/BTS via the LMP.

However, the user can define a set of exception rules to the restricted

mode so that any IP packet that matches any of these rules is not

discarded. In the unrestricted mode, network elements other than the local AXC/BTS can be freely accessed.

Some functions of Nokia AXC can also be accessed using a web browser.

For example, it is possible to reboot or recover Nokia AXC in this way.

These actions are protected with a username and password. Furthermore,

some IP analysis tools, such as ping, are also available via a web browser.

Nokia NetAct

Nokia NetAct provides a full range of functions securing efficient

performance, configuration, transmission, security, fault management andhardware and software management capabilities, such as the scheduled

software upgrade of several AXCs at the same time.

Nokia NetAct network management system can be used in a centralised

manner to collect alarm and measurement data on Nokia AXC nodes

within a network. Nokia AXC Manager integrated into Nokia NetAct can be

used to remotely configure a Nokia AXC node. Nokia AXC-FB Hopper

Manager integrated into Nokia NetAct can be used to remotely configure a

Nokia FlexiHopper (Plus) or MetroHopper microwave radio link.

The table below lists the ports that are used in AXC. The information can

be used when configuring the firewall on the NetAct side.

Table 6. IP ports in Nokia AXC

Source Destinatio

n

Service Protocol/port Action

NetAct

AXC

AXC

NetAct

BTS

FTP (data)

FTP (control)

tcp/20

tcp/21

Accept


15/06/2007




Table 6. IP ports in Nokia AXC (cont.)

Source Destinatio

n

Service Protocol/port Action

NetAct AXC, BTS HTTP (AXC Manager

login, AXC web

interface)

tcp/80 Accept

AXC

NetAct

NetAct

AXC

NTP udp/123 Accept

AXC

Manager

AXC Local Management

Port

tcp/9000 N/A

AXC

NetAct

NetAct

AXC

Public IP (connectionfrom AXC to DCN)

Remote AXC

Manager session

tcp/49152-49652

tcp/49201

Accept

NetAct AXC Q1 Support Function tcp/27500 Accept

Whenever the hardware configuration of Nokia AXC changes, a

notification is automatically sent to Nokia NetAct. The notifications is sent

in the following cases:

. a unit is removed or replaced

. expected unit type is set via Nokia NetAct

. changes are made to the hardware settings (system name, user

label, location)

For more information on configuring the HW notification on the NetAct,

refer to Nokia NetAct documentation.

Furthermore, all operations performed by all users on the AXC are logged

and information on them is collected to a buffer. This information can be

uploaded to Nokia NetAct as a single XML file.

ATM end-to-end management

Nokia NetAct features an optional ATM end-to-end management solution

(ATM Manager, comprised of Tellabs 8100® network manager) that

supports the key Nokia 3G Radio Access Network elements at the ATM

layer. One of its key features is the discovery and documentation of the

ATM network topology, including the ATM layer virtual path and virtual

channel termination points and connections. The up-to-date network

documentation is a foundation for the actual ATM layer end-to-end

DN02166696Issue 22-0 en15/06/2007


Management



configuration management features such as manual or automatic routing

of ATM connections and their provisioning. ATM layer fault managementenables the user to monitor faults mapped on network connections rather

than just on the nodes involved.

Nokia NetAct ATM Manager provides tools for managing the ATM layer

connectivity in Nokia 3G RAN, offering centralised ATM layer end-to-end

configuration management and fault monitoring. ATM layer management

includes management for Nokia AXC, Nokia RNC and Nokia BTS network

elements including end-to-end connection management which makes

ATM connection management significantly easier, faster and less error

prone.

For further information, refer to NMS for 3G Mobile Systems (NetAct) User

Manual .

7.1.1 Nokia AXC management model

The management model of Nokia AXC can be divided into three layers:

the PDH/SDH/SONET/Ethernet Transmission Layer, the ATM Transport

Layer and the Application Layer.

Figure 24. AXC management model

Application Layer (IP DCN, AAL2, CES)

ATM Transport Layer

PDH/SDH/SONET/Ethernet Transmission Layer


15/06/2007




PDH/SDH/SONET/Ethernet Transmission Layer

The PDH/SDH/SONET/Ethernet Transmission Layer models the

functionality that is necessary for Nokia AXC to be connected to the PDH/

SDH/SONET/Ethernet network. This layer provides an abstract view of the

PDH/SDH/SONET/Ethernet Transmission Layer to the ATM Transport

Layer above.

The PDH Physical Section Trail represents the physical E1/T1/JT1

interfaces, the SDH/SONET Physical Section Trail the physical STM-1/

STS-3c interfaces, and the Ethernet Link the physical Ethernet interfaces.

E1/JT1/T1 links as well as E1 links within Flexbus interfaces can be

configured as IMA links that can be combined to form an IMA group. AnIMA group is considered a single transmission interface from the ATM

Transport Layer point of view. E1/JT1/T1 links can also be used as plain

PDH links.

The other SDH/SONET related entities represent the various SDH/SONETlayers. In most cases, they only provide some layer specific information

and need not be configured.

Transmission Convergence provides the ATM Transport Layer an abstract

view of the physical interfaces, and thus the ATM Transport Layer is

independent of the underlying transmission infrastructure. TheTransmission Convergence is automatically created when an IFU is

configured in Nokia AXC.

DN02166696Issue 22-0 en15/06/2007


Management



Figure 25. PDH/SDH/SONET/Ethernet transmission layer

ATM Transport Layer

The ATM Transport Layer models the VP and VC ATM cross-connect

functionality that is the main functionality of Nokia AXC.

A Connection Termination Point (CT) represents the anchor point of a VP/

VC connection that can either be terminated or cross-connected. A Trail

Termination Point (TT) indicates explicitly that a connection is terminated.

The Virtual Path Connection Termination Point (VPCT) is the lowest entityof the ATM Transport Layer. The Traffic Descriptor provides the traffic

parameters (e.g. PCR and Service Category) for the VPCT and the VCCT.

A Virtual Path Cross-connection is a cross-connection of two VPCTs. A

Virtual Path cross-connection can be modelled as shown in the following

figure.

IMA

PDH(E1/JT1/T1)

ATM Transport Layer (VPCT)

Transmission convergence

Fractional PDH(E1/JT1/T1)

SDH/SONET(STM-1/STS-3c)

Ethernet


15/06/2007




Figure 26. VP cross-connection

A Virtual Path Trail Termination Point (VPTT) is the termination point

through which the Virtual Channels included in the VP can be accessed so

that Virtual Channel Connection Termination Points (VCCT), Virtual

Channel Cross-connections and Virtual Channel Trail Termination Points

(VCTT) can be created. A Virtual Channel cross-connection can be

modelled as shown in the following figure.

TrafficDescriptor

VPCT

Transmission Convergence

Layer

VPCT

Transmission Convergence

Layer

VP

cross-connection

DN02166696Issue 22-0 en15/06/2007


Management



Figure 27. VC cross-connection

Application Layer

A terminated VC can be used by an application in the Application Layer.The ATM Adaptation Layer (AAL) is responsible for this functionality. The

following VCs can be terminated in the Nokia AXC:

. DCN VC (AAL5)

. AAL2 signalling VC (AAL5, with AXUB and AXC Compact)

. AAL2 User Plane VC (AAL2, with AXUB and AXC Compact)

.

CES (AAL1)

The following figure shows the generic view of the Application Layer.

TrafficDescriptor

VCCTVC

cross-connection

VPCT

Transmission ConvergenceLayer

VPTT

VCCT

VPCT


VPTT

TrafficDescriptor

TrafficDescriptor


15/06/2007




Figure 28. Generic view of the Application Layer

AAL5 is used for the DCN connections based on IP over ATM provided byNokia AXC. Terminated DCN connections are modelled in Figure DCN

connection terminated in AXC .

VC-CTP

VP-CTP


VP-TTP

TrafficDescriptor

VC-TTP

TrafficDescriptor

AALProfile

Application Layer (IP Link, AAL2, CES)

DN02166696Issue 22-0 en15/06/2007


Management



Figure 29. DCN connection terminated in AXC

Figure 30. Signalling link (AAL2 Control Plane)

VC-CTP

VP-CTP


VP-TTP

TrafficDescriptor

VC-TTP

TrafficDescriptor

AAL5Profile

Application Layer (IP Link)

VC-CTP

VP-CTP


VP-TTP

Traffic

Descriptor

VC-TTP

Traffic

Descriptor

AAL5Profile

Application Layer (AAL2 Signalling)


15/06/2007




Figure 31. AAL2 User Path (AAL2 User Plane)

Figure 32. CES

VC-CTP

VP-CTP


VP-TTP

Traffic

Descriptor

VC-TTP

Traffic

Descriptor

AAL2Profile

Application Layer (AAL2 User Path)

VC-CTP

VP-CTP


VP-TTP

TrafficDescriptor

VC-TTP

TrafficDescriptor

AAL1

Profile

Application Layer (CES)

PDH TransmissionConvergence Layer

DN02166696Issue 22-0 en15/06/2007


Management



7.2 Nokia AXC Manager

Nokia AXC is managed with Nokia AXC Manager software application. A

laptop as local management tool (LMT) can be used to access the node

via the local management port (LMP) of the AXU. Through the LMP, it is

possible to manage either the local AXC, or any other Nokia AXC node

within the same network.

Nokia AXC Manager provides an easy-to-use graphical user interface with

which you can, for example, configure and commission Nokia AXC nodes,

and make cross-connections. You can perform the following functions with

Nokia AXC Manager:

. commission a new Nokia AXC node manually through the graphical

user interface

. commission a new Nokia AXC node automatically by downloading

an XML file

. view and configure the settings and controls of Nokia AXC

. monitor the alarms generated by a node

. monitor the performance management data

.

download and activate new Nokia AXC node software releases. manage licences for application software

. export data for use with other tools, such as Nokia planning tools

. make configuration backups and restore AXC node configuration

. record, store and run a sequence of operations with the macrorecorder

. change the AXC account information

. reset the AXC

. recover the AXC

It is also possible to access the AXC via a web browser in order to perform

various operations (for example reset the AXC, retrieve log files and view

alarm information). Nokia AXC Manager can also be used as a Command

Line Tool. This enables you, for example, to create batch files for

configuring several AXC nodes with one command.


15/06/2007




You can find more information on the user interface of Nokia AXC Manager

in its online help system. It is available from the application as context-sensitive help and through the Help menu. To access the online help from

views, dialogue boxes and menus, press F1.

Note

Nokia AXC Manager checks the interdependency of the attributes of

the managed objects in order to make sure that a new action through

Nokia AXC Manager is not incoherent with the previously set

configurations.

Nokia AXC Manager can be downloaded from Nokia Online Services

(NOLS).

7.3 Nokia AXC-FB Hopper Manager

Nokia AXC-FB Hopper Manager is used for managing Nokia FlexiHopper

(Plus) and Nokia MetroHopper radios connected to the Flexbus interfaces

of the IFUE interface unit. It also manages the Flexbus part of the IFUE

itself. Nokia AXC-FB Hopper Manager can be connected to the Flexbuspart of the IFUE either directly via the LMP of the IFUE or remotely via the

DCN. It is possible to manage either the local radio or some aspects of a

radio at the far end of the radio hop.

The commissioning of Nokia FlexiHopper (Plus) and MetroHopper radios

is carried out with Nokia AXC-FB Hopper Manager. The application

provides an easy-to-use graphical interface with a commissioning wizardused in the commissioning tasks.

The following functions can be performed with Nokia AXC-FB Hopper

Manager:

. commission new nodes

. change the configuration of a new or previously configured node

. create 2 Mbit/s cross-connections between Flexbus interfaces

. troubleshoot a node

. monitor the fault status of a node

. monitor signal quality

DN02166696Issue 22-0 en15/06/2007


Management



. re-initiate channel selection procedure (Nokia MetroHopper)

. download new software

In addition, there is a separate application called Transmission Loader that

can be used for transmission element software upgrades.

You can find detailed information on the user interface of Nokia AXC-FB

Hopper Manager in its online help. For more information on the use of Nokia AXC-FB Hopper Manager and commissioning and maintenance of

the interface unit IFUE and connected Nokia FlexiHopper microwave

radios or Nokia MetroHopper radios, refer to Commissioning Nokia

FlexiHopper (Plus) and Nokia MetroHopper with IFUE and Maintaining

Nokia FlexiHopper (Plus) and Nokia MetroHopper with IFUE .

Nokia AXC-FB Hopper Manager can be downloaded from Nokia Online

Services (NOLS).

7.4 Nokia AXC automated commissioning concept

Nokia AXC automated commissioning concept is used for commissioning

Nokia AXC by importing an XML configuration file to Nokia AXC. This can

be performed either locally via Nokia AXC Manager or remotely via NokiaNetAct. The application of remote configuration is useful, for example,

when making major changes to existing networks (such as reparenting of

RNCs or implementation of new features).

The XML configuration file is created with Nokia NetAct planning tools. The

result of this planning phase is an AXC-specific XML file that contains all

Nokia AXC configuration parameters, such as VCI/VPI values of ATM

connections, the corresponding traffic descriptors and information about

the transmission interfaces to which these ATM connections belong. After

the XML configuration file has been imported and activated, Nokia AXC is

fully operational.

Automated commissioning reduces the commissioning time of Nokia AXC

remarkably. It reduces the manual commissioning effort and minimizes

configuration errors during the commissioning phase. This leads to

significant savings in time and costs of 3G roll-out.

It is also possible to generate an XML file that contains the current

configuration of the AXC node. The XML file is then imported to Nokia

NetAct PlanEditor where the settings can be changed or added. Finally, a

new XML file is created and imported to the AXC node.


15/06/2007




An XML file of the current AXC configuration can also be created for

backup purposes.

Note

The configuration of the Flexbus part of the IFUE including Q1 bus

settings cannot be configured via XML files.

7.5 ATM layer configuration management for BTS

RNS split is an operation where a number of already existing BTS sites are

moved from under the control of one RNC to under the control of another

RNC. This happens, for example, when there is a need for more capacity

in the network and therefore a new RNC is integrated to the network.

The RNS split operation requires reconfiguration of the radio network

parameters, and the ATM layer and IP network configuration in several

network elements in such a way that the network element downtime is

minimised, and the DCN connection for the O&M traffic is not lost.

With ATM layer configuration management for BTS, the AXC hides theWAM unit ATM layer configuration from the user. This means that BTS

WAMs do not need a separate ATM level configuration anymore. The AXC

takes care of all ATM layer related O&M tasks in the BTS including the

ATM OAM cell handling for the connections terminated in node B.

If the AXC does not have all the configuration parameters required by the

BTS, the BTS will use the existing parameter values from the site

configuration file for all parameters.

7.6 Q1 management

Nokia Q1 is a Nokia proprietary management protocol for PDH networkelements, such as Nokia MetroHopper and Nokia FlexiHopper (Plus)

radios and associated indoor units. Nokia AXC provides a path to reach

Q1 managed network elements that are below the AXC from the network

topology point of view.

DN02166696Issue 22-0 en15/06/2007


Management



Nokia AXC contains a Q1 support function (Q1SF), which implements a

Q1 polling functionality, and forwards Q1 messages over IP. The Q1SFacts as a Q1 bus master. Its Q1 bus is connected to a Q1 interface (V.11)

located on the front panel of the AXU or AXC Compact for direct

connection to any Q1 managed network element, such as a Nokia

UltraSite Support Supreme/Optima cabinet.

Optionally, the Q1 bus can also be connected to the Q1 embedded

operation channels (Q1 EOC) in the PDH frames of the IFUA, the IFUD or

the IFUE in order to manage remote Nokia Q1 equipment (e.g. located in a

GSM/EDGE BTS). Furthermore, the Q1 bus can be transported over the

overhead bytes of the Flexbus frame on the IFUE. For managing the

Flexbus part of the IFUE, its operation and maintenance microprocessor

can be directly accessed via the local management port (LMP) of theIFUE.

A Nokia Q1 agent acts as a mediation device between Nokia NetAct and

the AXC Q1 support function and it is typically used to configure the AXC

Q1 support function. However, if there is no connection to this mediation

device available during Nokia AXC commissioning, the Q1 support

function within the AXC can also be configured using a GCS command line

tool that is embedded in Nokia AXC Manager.


15/06/2007




Figure 33. AXC Q1 management

7.7 Neighbour Node Discovery (NND)

Nokia AXC provides means for managing ATM connections between

different AXCs. AXC supports an automated mechanism for updating

network topology information. The Neighbour Node Discovery (NND)

feature of Nokia AXC provides ATM level topology information to Nokia

NetAct ATM Manager. ATM Manager provides tools for managing the ATM

layer connectivity in Nokia 3G RAN, centralised ATM layer end-to-end

configuration management and fault monitoring.

Nokia NetAct / Nokia Q1 Agent

Q1 over TCP/IP

AXU IFUC IFUA IFUE

Q1SF

LMP

Internal Q1 bus

IProuter

Q1networkelement

ExternalQ1 bus

V.11

Q1networkelement

Q1networkelement

Q1 EOC

Q1/FlexbusEOC

DCN

DN02166696Issue 22-0 en15/06/2007


Management



Figure 34. Nokia NetAct ATM Manager

NND can send information packets through each AXC interface. Each

information packet contains a node identifier of the sending AXC and an

interface identifier. By reception of such a packet the AXC can determinethe neighbouring AXC node and the interface through which the AXC

nodes are connected. The NND feature is configurable for each interface

and as default it is activated. A pre-defined channel VP/VC (0,21) is

reserved for packet exchange. In order to keep required bandwidth at

minimum, information packets are sent once per minute. This means that

the peak cell rate is 5 cells/s and the sustained bandwidth less than 1kb/s.

The used traffic class is UBR.


15/06/2007




8 Mechanical structure

8.1 Nokia AXC mechanics

The modular embedded Nokia AXC is integrated in the Nokia WCDMA

base stations. Both modular embedded and stand-alone AXC consist of

the same hardware and software, and therefore provide the same

features. The only difference is in the environment the AXC units are

installed into.

The modular embedded Nokia AXC is designed to be scalable. Thus the

configuration is easy to change according to your needs. However, the

optimised Nokia AXC Compact for tail sites and small hubs is non-

expandable.

All the AXC units are connected together through a common backplane.

DN02166696Issue 22-0 en15/06/2007


Mechanical structure



Figure 35. Modular embedded Nokia AXC in Nokia UltraSite WCDMA BTS

Supreme Indoor

Wideband ApplicationManager (WAM)

WSC = SystemClock Unit

AXU = ATM

Cross-connection Unit

IFU = TransmissionInterface Unit


15/06/2007




8.2 Stand-alone AXC mechanics

The Stand-alone AXC subrack consists of two 6-slot S-AXC cartridges

with a fan unit, two DC-PIUs and plug-in units (AXU and IFUs). The stand-

alone subrack can be installed in a 600 mm wide ETSI rack or a 19-inch

rack (9 height units). One stand-alone subrack houses up to two S-AXC

nodes. The S-AXC can also be installed in Nokia UltraSite Supreme/

Optima site support cabinets to provide additional transmission capacity

and transmission interfaces to a BTS site. With the Circuit Emulation

Service feature, the S-AXC allows to extract TDM traffic out of the ATM

data stream, for example, at an RNC location.

Figure Nokia S-AXC subrack illustrates the S-AXC subrack as delivered tothe customer. Figure S-AXC subracks in an ETSI rack shows several S-

AXC subracks installed in an ETSI rack. The S-AXC subracks can be

installed directly on top of each other.

Figure 36. Nokia S-AXC subrack

Frame

Upper plate

ID sticker

6-slotcartridge

Cable tray

Fan unit

Blankingplate

DC-PIU cartridgewith 2 DC-PIUs

DN02166696Issue 22-0 en15/06/2007





Figure 37. S-AXC subracks in an ETSI rack


15/06/2007




8.3 AXC power supply

Base station integrated AXC

The BTS integrated AXC, the backplane and all attached units are

powered through the BTS. A BTS site can be powered with either DC or

AC.

When the BTS is powered with DC, there is an AC/DC converter and

batteries situated in the site support cabinet or in an indoor case located in

the site. The converter supplies –48VDC to the BTS and simultaneously to

the Nokia AXC.

When the BTS is powered with AC, the AC/DC converter located in the

BTS supplies the BTS and the Nokia AXC with –48VDC.

Stand-alone AXC

The Stand-alone AXC subrack is always supplied with –48 VDC battery

voltage by a separate DC-PIU power interface unit located in the samesubrack. The voltages required at the unit level are generated locally by

DC/DC converters.

The power supply for the S-AXC can be protected as there are two DC-

PIU units installed in the S-AXC subrack. Each Nokia S-AXC nodefeatures two battery power input interfaces. When the power cables are

connected to different DC-PIUs, either one of these units can function as a

redundant power supply. The two DC-PIUs provide redundancy protection

for the Nokia S-AXC nodes in the subrack. For more information, see DC-

PIU .

Cold start feature

The minimum operating temperature of Nokia AXC is -10°C. When that

temperature is reached after a warm-up, Nokia AXC starts up

automatically.

In temperatures lower than +20°C, the fans in the fan unit of a Stand-alone

AXC rotate at 1000 rpm. The rotation speed increases linearly so that in

temperatures of +50°C and above, the speed is 2800 rpm.

DN02166696Issue 22-0 en15/06/2007





8.4 DC-PIU

DC-PIU is a plug-in power interface unit that provides the DC power supply

(nominal voltage –48 VDC) for the Stand-alone AXC network element (see

AXC power supply ). DC-PIU supplies power for the S-AXC units and the

fan unit. There are two DC-PIUs already installed in the S-AXC subrack.

DC-PIU has the following interfaces on the front panel:

. battery voltage input interface

. two power output interfaces

. auxiliary power output interface (reserved)

. station alarm output interface

. station alarm input interface

. tricolour status LED

There are also two circuit breaker switches for the battery voltage output

lines. The circuit breakers function as overcurrent protectors.


15/06/2007




Figure 38. DC-PIU interfaces

Low frequency filtering is not included in the DC-PIU as the subrack or

cartridge handles the EMC line filtering for low frequency common-modedisturbances up to about 1 MHz. However, all connections are protected

with high frequency filtering to suppress EMC emissions possibly induced

to traces when connecting to the outside of the power subrack/cartridge.

Battery input

Station alarm

output

Station alarm

input

Aux power

output

Power output 1

Power output 2

LED

Circuit breakers

DN02166696Issue 22-0 en15/06/2007





Figure 39. DC-PIU block diagram

The alarm inputs coming through the DC-PIU's station alarm input

connector on the front panel are transferred to the station alarm block

circuit. The incoming alarm is indicated by the LED and it can be

transferred to a centralised alarm monitoring system as relay output via the

station alarm output connector. The meaning of the incoming alarms (A, B

and D) is explained in Reading alarms.

P2

Stationalarms

out

J2

J3+J4

Alarm

LED

PE

+Batt1

+Batt2

-Batt1

-Batt2

P1

J5+J6

Batt. in

Cap_ctrl

S1

S2

FH2/F1

P4

P3

P7

P5

Stationalarms in

Pow aux.out

Batt. out 1

Batt. out 2

VAP5 Station

alarms

Capalarm


15/06/2007




Figure 40. Operating principle of the station alarm block

8.5 AXC unit LEDs

Front panel LEDs

Each unit in Nokia AXC has a 3-colour status LED located on the front

panel. These indicators display the current state of the equipment.

Table 7. LED indications (O/A/F1)

Colour Explanation

Stable red Major or critical alarm

Blinking red Minor alarm

Stable yellow Unit starting up

Stable green Normal operation, power on

Blinking green Software download from LMT or network

during operation

VPBJumper: VPBcontact

no jumper: current loop jumper: GND contact

VAP5

GNDcontact

P2

P3 Front

A2in

B2in

D2in

VAP5

GND

CAP_REL

Alarm input connector

CAP_ALAlarm output connector

A1outA2outB1out

B2outD2outD1out

(E1)(E2)(F1)(F2)GND

A4D5B5

C6A6

C2C4D1D3

A2

B2

B3

1

23

4567891011

DN02166696Issue 22-0 en15/06/2007





IFUE LEDs

Interface unit IFUE has two 3-colour status LEDs on the front panel

indicating the operational status of the unit: O/A/F1 and O/A/F2 (O/A/F

signifies Operation/Alarm/Fail). The O/A/F1 LED indicates the operational

status of the ATM part and the O/A/F2 LED indicates the operational status

of the Flexbus part of the IFUE. In addition, each of the three Flexbus

interfaces has a status LED of its own (DC on).

. O/A/F1 (ATM part)

.

O/A/F2 (Flexbus part). DC on (Flexbus 1)

. DC on (Flexbus 2)

. DC on (Flexbus 3)

The following table shows the indications of the O/A/F2 multi-colour LED

for the Flexbus part.

Table 8. IFUE O/A/F2 LED indications

Colour Status

Green The unit functions well, no alarms.

Yellow Alarms with low priority occur, e.g. “the

node clock is not set”

Red Some errors occur, e.g. “LOS of FB1” or

“2M interface 3: Buffer overflow”

The following table shows shows the indications of the DC on Flexbus

LEDs.

Table 9. IFUE Status of “DC on” LED indications

Indication Status

Off Normal status, no remote power feeding.

Blinking Try to find an Outdoor Unit (OU), remote

power feeding is temporarily on.

On OU found and remote power feeding is

on.


15/06/2007




DC-PIU LEDs

The classification of the station alarms of the DC-PIU is described in the

table below. When there are no incoming station alarms the DC-PIU is not

lit.

Table 10. Classification of station alarms

Severity Class Colour

Critical, major A Red

Minor B Yellow

Reminder (disabled A or B alarm) D Green

8.6 AXU

8.6.1 ATM cross-connect unit (AXU)

The ATM cross-connect unit (AXU) is the master unit of the AXC node and

it controls the node within the Nokia WCDMA BTS. It cross-connects ATM

traffic within the BTS, and connects the BTS to other BTSs or to the Nokia

Radio Network Controller (RNC). The AXU unit is always installed in the

first slot of the AXC.

There are two AXU units available: AXUA and AXUB. AXUB provides the

BTS AAL2 multiplexing feature. It is enabled by the ATM Adaptation

Module (AAM) of the AXUB unit.

DN02166696Issue 22-0 en15/06/2007





Figure 41. AXU unit

For more information, refer AXU functional blocks to and AXC unit LEDs.

8.6.2 AXU functional blocks

The AXU unit includes the following functional blocks:

. Control Unit

. Clock Distribution Circuit

. ATM Switch Fabric

. AAM (in AXUB)

Power

module

Microcontroller module

AAM module(AXUB)

LMP

Q1

ERC

Ejector

Ejector

LED


15/06/2007




. Backplane Bus Adaptation

. DC/DC Converter

The figure below shows the block diagram of the AXU unit.

Figure 42. The functional blocks of the AXU unit

Control Unit

The Control Unit consists of the Microcontroller and other necessary

circuitry. It is compiled on a module that is the same in each AXC unit. The

module type is so generic that it meets all the requirements of each AXC

unit.

The Microcontroller runs all unit control software on the AXC.

LED LMP Q1 ERC

ControlUnit

Q1supportfunction

ClockDistr.

Circuit

ATMSwitchFabric

AAM(AXUB)

DC/DCConverter

Backplane Bus Adapt.

t o / f r o m

I F U X

t o / f r o m

W A M

D C i n p u t

I n t e r - u n i t

c o m m u n i c a t i o n

a n d

Q 1 b u s

C l o c k d i s t r i b u t i o n

DN02166696Issue 22-0 en15/06/2007





The Control Unit also features an IP router. Thus it provides a routing path

for remote BTS management and enables the local management of theBTS via the LMP of the AXC. Management of other BTSs via the IP router

is also possible. In addition the Control Unit features a Q1 management

support function which can be used to manage Q1 network elements

remotely. The Q1 network elements can be connected to the Q1

management support function by means of a cable connected to the Q1

interface at the front panel of the AXU or by means of operation channels

(EOC) embedded in some transmission signals. The Q1 management

support function can be connected via the backplane to AXC embedded

Q1 network elements (IFUE).

Clock Distribution Circuit

The Clock Distribution Circuit provides a reference clock for all IFUs and

the WSC.

The reference clock can either be recovered from a physical interface or

received from an external timing source, or from an internal reference

source. The internal clock is used if no external reference is available. In

this case the AXC does not provide a reference clock for the BTS, but the

BTS's WSC provides the clock for the BTS. The AXU features a dedicated

interface for external timing source input.

ATM Switch Fabric

The ATM Switch Fabric performs all ATM layer functionalities of the AXC:

. Virtual Path and Virtual Channel cross-connection functionality for

ATM cells between a certain number of IFUs and WAMs

. header translation functionality for ATM connections

. traffic management functions like policing or traffic shaping

. O&M functionality (operations, administration and maintenance)

The total switching capacity of the block is 1.2 Gbit/s.

AAM (in AXUB)

If the AAL type 2 module (AAM) on AXUB unit is taken into operation, it

multiplexes or demultiplexes AAL type 2 connections between the WAMs

and RNC into one or several VCCs.


15/06/2007




Backplane Bus Adaptation

The Backplane Bus Adaptation provides serial payload backplane

connections between the IFUs and the AXU by means of a bus, as well as

the AXU and the WAMs.

DC/DC Converter

The DC/DC Converter transforms the input voltage of –48 V fed through

the backplane to the voltages required at unit level.

8.7 AXCC/AXCD

8.7.1 AXC Compact (AXCC/AXCD)

AXC Compact is a combined unit that provides both AXUB and IFUA/D

functionality including BTS AAL2 multiplexing application software. It

houses the ATM switch fabric, Local Management Port, clock distribution

circuitry and eight PDH interfaces. In AXCC these interfaces are

symmetrical E1/JT1/T1 interfaces and in AXCD coaxial E1 interfaces.

AXC Compact occupies two slots in the cabinet/subrack.

DN02166696Issue 22-0 en15/06/2007





Figure 43. AXCC unit

Q1

ERC

Ejector

Ejector

LED

LMP

8 xE1/JT1/T1


15/06/2007




Figure 44. AXCD unit

8.7.2 AXCC/AXCD functional blocks

The AXCC/AXCD units include the following functional blocks:

. Overvoltage Protection

. Line Interface/Framer

. Interworking Unit

. IMA

. ATM Processing Unit

Q1

ERC

Ejector

Ejector

LED

LMP

8 x E1

DN02166696Issue 22-0 en15/06/2007






. Control Unit

. Clock Distribution Circuit

. DC/DC Converter

Figure 45. The functional blocks of the AXCC/D

Overvoltage Protection

The block provides appropriate overvoltage protection for the line

interface.

D C i n p u t

DC/DCConverter

Control Unit

LED LMP Q1 ERC

Q1

supportfunction

ClockDistr.

Circuit

8 x E1/JT1/T1


ATM Processing Unit

t o W S C

B a s e b o a r d

S a t e l l i t e b o a r d

t o / f r o m

W A M

IMA

Interworking Unit

Line Interface/Framer



15/06/2007




Line Interface/Framer

The Line Interface consists of 8 physical interfaces that can be either

symmetrical TQ connectors (8 x 100/110/120 Ω) or coaxial BT –43

connectors (16 x 75 Ω). The Framer adds the frames to the serial data

stream from the Interworking Unit.

Interworking Unit

The E1/JT1/T1-ATM Interworking Unit supports the mapping of ATM cells

from/into PDH frames. Thus it forms the interface between ATM and TDM.

CES Interworking supports the mapping of TDM traffic ATM cells. AXCC/D

supports both unstructured and structured CES.

IMA

The IMA implements Inverse Multiplexing for ATM that uses a cell based

multiplexing technique for mapping a single high-capacity ATM stream into

multiple lower-capacity PDH streams for transmission over independent

links.

ATM Processing Unit

The ATM Processing Unit perfoms the following functions:

. ATM switch fabric (capacity 165 Mbit/s)

. BTS AAL2 multiplexing

Control Unit


circuitry.

The Microcontroller runs all unit control software on the AXCC/D.

The Control Unit also features an IP router. Thus it provides a routing path

for remote BTS management and enables the local management of the

BTS via the LMP of the AXCC/D. Management of other BTSs via the IP

router is also possible. In addition the Control Unit features a Q1management support function which can be used to manage Q1 network

elements remotely. The Q1 network elements can be connected to the Q1

management support function by means of a cable connected to the Q1

interface at the front panel of the AXCC/D.

DN02166696Issue 22-0 en15/06/2007





Clock Distribution Circuit

The Clock Distribution Circuit provides a reference clock for the WSC.

The reference clock can either be recovered from a physical interface or

received from an external timing source, or from an internal reference

source. The internal clock is used if no external reference is available. In

this case the AXCC/D does not provide a reference clock for the BTS, but

the BTS's WSC provides the clock for the BTS. The AXCC/D features one

interface for external timing source input.


The Backplane Bus Adaptation provides serial payload backplaneconnections between the AXCC/D and the WAMs by means of a bus.

DC/DC Converter

The DC/DC Converter transforms the input voltage of -48 V fed through

the baclplane to the voltages required at unit level.

8.8 IFUA/IFUD

8.8.1 Interface units IFUA/IFUD

The IFUA is an interface unit for the standard ETSI E1 (2.048 Mbit/s), the

Japanese JT1 (1.544 Mbit/s) or the ANSI T1 (1.544 Mbit/s) symmetrical

connections. The IFUD is the interface unit for eight E1 (2.048 Mbit/s)coaxial connections.

IFUA and IFUD interface units support Inverse Multiplexing for ATM (IMA).

The units enable distribution of ATM connections across up to 8 E1/JT1/T1

links in an IMA group.

Each of the eight interfaces of the IFUs can be configured to operate either

as ATM over E1/JT1/T1 (IFUA) or E1 (IFUD), or as ATM over fractional E1/

JT1/T1 (IFUA) or E1 (IFUD). In the fractional E1/JT1/T1 links, the timeslots

that are unused by ATM traffic can be filled with TDM traffic by external 64

kbit/s cross-connects (Nokia Talk Family BTS, Nokia MetroHub and Nokia

UltraSite GSM/EDGE BTS).


15/06/2007




Figure 46. IFUA unit

8 x

E1/JT1/T1

Power module


LED

Ejector

Ejector

DN02166696Issue 22-0 en15/06/2007





Figure 47. IFUD unit

For more information, refer to IFUA/IFUD functional blocks and AXC unit LEDs.

8.8.2 IFUA/IFUD functional blocks

The IFUA/D units include the following functional blocks:

. Line Interface Overvoltage Protection

. Clock Recovery

.

E1/JT1/T1 –

ATM Interworking, CES Interworking

Power module

Ejector

8 x E1

LED

Ejector



15/06/2007




. IMA


. Control Unit

. DC/DC Converter

Figures The functional blocks of the IFUA unit and The functional blocks of

the IFUD unit show the block diagrams of the IFUA and IFUD units.

Figure 48. The functional blocks of the IFUA unit

I n t e r - u n i t


a n d Q 1 b

u s

C l o c k

d i s t r i b u t i o

n

ClockRecovery

Line InterfaceOvervoltage Protection

PLL

IMA


D C i n p u t

T o / f r o m

A X U

DC/DCConverter

ControlUnit

LED 8 x E1, JT1, T1(100/110/120 Ohm)

E1/JT1/T1-ATM Interworking

CES Interworking

E1:8X

1.920Mbit/s

JT1,T1:8X

1.536Mbit/s

DN02166696Issue 22-0 en15/06/2007





Figure 49. The functional blocks of the IFUD unit

Line Interface, Overvoltage Protection

The Line Interface, Overvoltage Protection consists of 8 physicalinterfaces that can be either symmetrical TQ connectors (8 x 100/110/120

Ω) or coaxial BT –43 connectors (16 x 75 Ω).

The block provides appropriate overvoltage protection. It contains framing

for the different line interface rates and provides electrical parameters.

I n t e r - u n i t


a n d Q 1 b u s

C l o c k

d i s t r i b u t i o n

ClockRecovery

Line Interface


PLL

IMA


D C i n p u t

T o / f r o m

A X U

DC/DCConverter

ControlUnit

LED 8 x E1(75 Ohm)

E1-ATM Interworking

CES Interworking

E1:8X

1.920Mbit/s


15/06/2007




Clock Recovery

The Clock Recovery recovers the clock signal from the incoming data

stream and passes it to the E1/JT1/T1 – ATM Interworking together with the

sampled data signal. Via the backplane the recovered clock signal is

transferred to the Clock Distribution Circuit of the AXU.

The block consists of a clock and a data recovery circuit working at either

1.544 Mbit/s or 2.048 Mbit/s.

The PLL recovers the clock signal from the common reference clock

provided by the Clock Distribution Circuit of the AXU.

E1/JT1/T1 –

ATM Interworking, CES Interworking

The E1/JT1/T1 – ATM Interworking supports the mapping of ATM cells

from/into PDH frames. Thus it forms the interface between ATM and TDM.

Each of the interfaces can be configured to operate as ATM over E1, JT1

or T1 or as ATM over fractional E1, JT1 or T1.

CES Interworking supports the mapping of TDM traffic into ATM cells.

IFUA/D supports both unstructured and structured CES.

IMA

The IMA implements Inverse Multiplexing for ATM (IMA) that uses a cell

based multiplexing technique for mapping a single high-capacity ATM

stream into multiple lower-capacity PDH streams for transmission over

independent links.

The IFUA/D supports 1 to 4 IMA groups with 1 to 8 E1/JT1/T1 links per IMA group.



connections between the IFUs and the AXU by means of a bus.

Control Unit




unit.


DN02166696Issue 22-0 en15/06/2007





DC/DC Converter

The DC/DC Converter converts the input voltage of –48V fed through the

backplane of the unit to the voltages required at unit level.

8.9 IFUC

8.9.1 Interface unit IFUC

The IFUC is the interface unit for SDH/SONET connections using optical

fibre. It provides three interfaces, each of which is software configurable aseither STM-1 (VC-4) or OC-3.

Figure 50. IFUC unit

3 x STM-1/OC-3

Power module


LED

Ejector

Ejector


15/06/2007




For more information, refer to IFUC functional blocks and AXC unit LEDs.

8.9.2 IFUC functional blocks

The IFUC unit includes the following functional blocks:

. Transceiver

. Clock Recovery

. SDH Framer


. Control Unit

. DC/DC Converter

The figure The functional blocks of the IFUC unit shows the block diagram

of the IFUC unit.

DN02166696Issue 22-0 en15/06/2007





Figure 51. The functional blocks of the IFUC unit

Transceiver

The Transceiver handles the electro-optical conversion and vice versa.

The Transceiver block consists of three transceivers each including a 1300

nm InGaAsP laser and an InGaAs PIN photodiode with a signal detection

circuit. The three optical fibre connectors on the front panel are an integral

part of the single mode transceivers.

I n t e r - u n i t


b u s

C l o c k



D C i n p u t

T o / f r o m

A X U

DC/DCConverter

ControlUnit

LED

SDH framer

PLLClock Recovery

3X149.76Mbit/s

Transceiver

STM-1/OC-3

STM-1/OC-3

STM-1/OC-3


15/06/2007




Clock Recovery

The Clock Recovery block recovers the clock signal from the incoming

data stream and passes it to the SDH Framer together with the sampled

data signal. Via the backplane the recovered clock signal can be

transferred to the Clock Distribution Circuit of the AXU.

The block consists of a clock and a data recovery circuit working at 155.52

Mbit/s.

The PLL recovers the clock signal from the common reference clock

provided by the Clock Distribution Circuit of the AXU.

SDH Framer

The SDH Framer provides the interface between the ATM layer and the

SDH physical layer.

The SDH Framer performs the mapping of ATM cells into/from SDH frame

structures STM-1 and OC-3.

It features a Line Interface at 155.52 Mbit/s and 51.84 Mbit/s data rate, and

transport and path overhead insertion and extraction via serial interfaces.




Control Unit




unit.


DC/DC Converter

The DC/DC Converter converts the input voltage of –48V fed through thebackplane of the unit to the voltages required at the unit level.

DN02166696Issue 22-0 en15/06/2007





8.10 IFUE

8.10.1 Interface unit IFUE

The IFUE provides an interconnection to Nokia FlexiHopper (Plus) and

MetroHopper radios, and to Nokia GSM/EDGE base stations. This is

implemented with three Flexbus interfaces, each of which has a maximum

capacity of 16 x E1 (2.048 Mbit/s). They also provide power to the outdoor

microwave radio units.

IFUE includes a PDH cross-connect facility between the 3 Flexbus

interfaces as well as the Flexbus interfaces and the E1-ATM interworking.

IFUE supports also IMA by enabling distribution of ATM connections

across up to 8 E1 channels in an IMA group. Note that due to differential

delay in an IMA group, it is recommended that all E1 channels of an IMA

group share the same Flexbus link.

Nokia FlexiHopper (Plus) microwave radio outdoor units connected to

Flexbus interfaces 1 and 2 can be configured to protect each other (Hot

Stand-by). Flexbus interface 3 is an unprotected interface that can only be

operated with one single Nokia MetroHopper or Nokia FlexiHopper (Plus).

Propagation protection (space diversity, frequency diversity and

polarisation diversity) is also supported.


15/06/2007




Figure 52. IFUE unit

For more information, refer to IFUE functional blocks and AXC unit LEDs.

8.10.2 IFUE functional blocks

The IFUE unit has two main blocks: Flexbus part and ATM part. The

Flexbus part can map a maximum of 16 x E1 channels into 3 Flexbus

interfaces, that is it provides an add-drop capacity of 16 E1 channels. The

other E1 channels of a Flexbus link can be cross-connected to another

Flexbus link. The ATM part implements the interface between the 16 E1

channels and ATM cell-based interface to the AXUs.

The IFUE unit includes the following functional blocks:

LED (ATM)

LED (FB)

3 x Flexbusconnector

LED (DC on)

Ejector

Power module


Ejector

MP

LMP

DN02166696Issue 22-0 en15/06/2007





. Flexbus Framer

. FB-E1 Deframing, 2 M Cross-Connect

. E1 – ATM Interworking, CES Interworking

. IMA


. Control Unit FB/ATM

. DC/DC Converter

Figure The functional blocks of the IFUE unit shows the functional blocks

of the IFUE unit.


15/06/2007




Figure 53. The functional blocks of the IFUE unit

Flexbus Framer

The Flexbus Framer provides the mapping between the FlexBus frame

structure and the 2Mbit/s data stream. It synchronises the data to the

transmit clock provided by the clock distribution of the AXU.

LED FB 1 FB 2 FB 3 LMP

D C I n p u t

C l o c k d i s t r i b u t i o n

Flexbus Framer

T o / F r o m

A X U

Q 1 b u s

16 xE1

FB - E1 Deframing

E1-ATM InterworkingCES Interworking

Backplane Bus Adapt. DC/DCConverter

ATM

CUIMA

Flexbus

ATM

I n t e r - u n i t

c o m m u n i c a t i o n b u s

2 M Cross-Connect

PLL

RemotePower

CU

FB

16 x 1.92Mbit/s

DN02166696Issue 22-0 en15/06/2007





FB-E1 Deframing, 2 M Cross-Connect

The FB-E1 Deframing block demultiplexes the frame structure of the data

coming from the Flexbus (FB) interfaces, and transmits the data to the 2 M

Cross-Connect block and other communication interfaces. The 2 M Cross-

Connect provides up to 32 non-blocking cross-connections. Up to 16 E1

channels from the ATM side can be cross-connected to the 3 x 16 E1

channels provided by the Flexbus interfaces. The 2Mbit/s cross-connect

can also be used to connect E1 lines coming from one FB interface to

another FB interface.

The PLL generates the clock signal and locks it to the common reference

clock provided by the Clock Distribution Circuit of the AXU. IFUE chooses

a clock signal based on the status of the AXU. IFUE can also recover theclock from one of the E1 signals in the FB interfaces and provide it to the

AXC as the common clock for all transmit interfaces.

E1 –ATM Interworking, CES Interworking

The E1 – ATM Interworking unit serves as a gateway between

Asynchronous Transfer Mode (ATM) networks and timeslot based PDH

networks. The E1-ATM Interworking unit supports the mapping of ATM

cells from/into PDH frames.

CES Interworking supports the mapping of TDM traffic into ATM cells.IFUE supports only unstructured CES.

IMA

The IMA unit implements Inverse Multiplexing for ATM (IMA) that uses a

cell-based multiplexing technique for mapping a single high-capacity ATM


independent links.

The IMA functionality can be configured in the IFUE to support 1 –8 IMA

groups with 1 –8 E1 links per IMA group.

Each of the E1 links within a Flexbus interface can be linked to the IMA, or

they can be deployed as plain ATM E1 links.



connection between the IFUs and the AXU by means of a bus.


15/06/2007




Control Unit FB/ATM

Provided by application software the Control Units (CU) are controlling all

relevant functions. The Control Unit of the ATM part consists of the

Microcontroller and other necessary circuitry. It is compiled on a module

that is the same in each AXC unit. The module type is so generic that it

meets all the requirements of each AXC unit.

IFUE has also an additional Control Unit in the Flexbus part. The Control

Unit is integrated in the main PCB of the unit. The LMP is connected to the

Control Unit of the Flexbus part for local management. The Flexbus part is

managed by the AXC-FB Hopper Manager via the LMP of the IFUE unit.

Both Control Units can be configured remotely via network managementsystem.

DC/DC Converter

The DC/DC Converter converts the input voltage of -48V fed through the

backplane of the unit to the voltages required at unit level. The unit can

feed power to up to 3 microwave radios. When connected to another Nokia

PDH microwave radio indoor unit, the remote power feeding is

automatically disabled.

8.11 IFUF

8.11.1 Interface unit IFUF

IFUF is the interface unit for structured SDH connections using opticalfibre. It provides one STM-1 (VC-12) interface.

Up to 63 x VC-12 can be terminated in IFUF. These VC-12s can be

distributed over a maximum of 16 IMA groups (with up to 32 IMA links) or

alternatively up to 16 plain VC-12s can be add/dropped to the AXC switch

fabric.

DN02166696Issue 22-0 en15/06/2007





Figure 54. IFUF unit

For more information, refer to IFUF functional blocks and AXC unit LEDs.

8.11.2 IFUF functional blocks

The IFUF unit includes the following functional blocks:

. Transceiver

. SDH Payload Extractor/Aligner

. E1 Framer, VT/TU Mapper

. IMA

Ejector

LED


Power module

STM-1

Ejector


15/06/2007





. Control Unit

. DC/DC Converter

Figure 55. The functional blocks of the IFUF unit

LED STM-1

E1 Framer VT/TU

Mapper

SDH PayloadExtractor/

Aligner


DC/DCConverter

I n t e r - u n i t


C l o c k


D C i n p u t

To/fromAXU

Transceiver

IMA

ControlUnit

ClockRecovery

DN02166696Issue 22-0 en15/06/2007





Transceiver

The Transceiver handles the electro-optical conversion and vice versa. It

consists of a 1300 nm InGaAsP laser and an InGaAs PIN photodiode with

a signal detection circuit. The optical fibre connector on the front panel is

an integral part of the single mode transceiver.

SDH Payload Extractor/Aligner

Together with the E1 Framer and VT/TU Mapper, the SDH Payload

Extractor/Aligner provides the interface between the ATM layer and the

SDH physical layer. The SDH Payload Extractor/Aligner multiplexes and

de-multiplexes the VC-4s to/from STM-1.

E1 Framer and VT/TU Mapper

The E1 Framer and VT/TU Mapper performs the mapping of up to 63 E1s

to/from VC-12/TU-12s and multiplexing and de-multiplexing VC-12s to/ from VC-4s.

IMA

The IMA unit implements Inverse Multiplexing for ATM (IMA) that uses a

cell-based multiplexing technique for mapping a single high-capacity ATM


independent links.

The IMA functionality can be configured in the IFUF to support 1 to 16 IMA

groups with 1 to 32 VC-12 links per IMA group.




Control Unit




unit.


15/06/2007




Clock Recovery

The Clock Recovery selects the node clock signal from the AXU and

provides all necessary clock signals to the unit. It also recovers the clock

signal from the incoming STM-1 data stream and forwards the signal to the

AXU. In case the clock signal cannnot be recovered, a LOS signal is

generated and forwarded to the AXU.

DC/DC Converter

The DC/DC Converter converts the input voltage of –48V fed through the

backplane of the unit to the voltages required at the unit level.

8.12 IFUG

8.12.1 Interface unit IFUG

The IFUG provides multiple simultaneous connections (8 x 10 BaseT

Ethernet ports), i.e. it connects external equipment on the site to the

common DCN. One connection is required to the local management port

(LMP) of the AXU and another to connect the AXC Manager to an interface

of the hub for local AXC/BTS Management. The remaining six Ethernetinterfaces can be used, for example, for Nokia Remote Downtilt Unit or any

other equipment that is managed via IP.

DN02166696Issue 22-0 en15/06/2007





Figure 56. IFUG unit

For more information, refer to IFUG functional blocks and AXC unit LEDs.

8.12.2 IFUG functional blocks

The IFUG unit includes the following functional blocks:

. Overvoltage Protection

. Transformer

. 10 BaseT Hub

. DC/DC Converter

Ejector

LED

8 xEthernet

Ejector


15/06/2007




Figure 57. The functional blocks of the IFUG unit

8.13 IFUH

8.13.1 Interface unit IFUH

The IFUH provides an ATM over Ethernet connection to the RNC for

Hybrid Backhaul. The unit contains two Fast Ethernet interfaces and an

optical Gigabit Ethernet interface (SFP is optional). However, only one of

these interfaces can be used at a time.

Line Interface


D C i n p u t

DC/DCConverter

LED 8 x RJ 45

Transformer

10 Base-THub

DN02166696Issue 22-0 en15/06/2007





The IFUH can be used with modular Nokia AXC and AXC Compact

configurations, but not with stand-alone AXC.

Figure 58. IFUH unit

For more information, refer to IFUH functional blocks and AXC unit LEDs.

8.13.2 IFUH functional blocks

The IFUH unit includes the following functional blocks:

. Ethernet Line Interface

. Ethernet Framer


Ejector

LED


Power module

Ejector

2 x Fast Ethernet

Gigabit Ethernet(optical, SFP isoptional)


15/06/2007




. Control Unit

. Clock Unit

. DC/DC Converter

Figure 59. The functional blocks of the IFUH unit

LED

Ethernet Framer


DC/DCConverter

I n t e r - u n i t


C l o c k


D C i n p u t

To/fromAXU

Ethernet Line Interface

ControlUnit

ClockUnit

2 x Fast Ethernet,1 x Gigabit Ethernet (optical, SFP is optional)

DN02166696Issue 22-0 en15/06/2007





Ethernet Line Interface

There are separate Ethernet line interfaces (or Ethernet PHYs) for Fast

Ethernet and Gigabit Ethernet. They manage the internal and external 10/

100 BaseT connections and the external Gigabit Ethernet connection. The

line interfaces use the SMII and GMII interface to communicate with the

Ethernet Framer.

Ethernet Framer

Ethernet Framer provides the main data path of the IFUH unit. It receives

the ATM cells from the backplane bus, places them into Ethernet frames

and transfers them to the line interface via the SMII (for Fast Ethernet) or

GMII (Gigabit Ethernet) bus, and vice versa.

The Ethernet Media Access Controller (MAC) is integrated into the

Ethernet Framer.




Control Unit


circuitry.

Clock Unit

The Clock Unit provides all necessary clock signals to the unit. In case the

clock signal cannnot be recovered, a LOS signal is generated and

forwarded to the AXU.

DC/DC Converter

The DC/DC Converter converts the input voltage of –48V fed through thebackplane of the unit to the voltages required at the unit level.


15/06/2007




9 Product structure

9.1 Delivery content of AXC

Table 11. Contents of AXC Stand-alone 19"-rack/ETSI rack T30454.01

Part Quantity

19” subrack 1

ETSI rack adaptor brackets 2

AXC 6-slot cartridge with fan unit 2

DC-PIU cartridge 1

DC-PIU (incl. alarm and internal power cables) 2

Blanking plates installed in the AXC 6-slot cartridge 10

Cable tray 1

Table 12. AXC plug-in units

Part Code

AXUA (AXU) T32107.01

AXUB (AXU) T32107.09

AXCC (symmetrical E1/JT1/T1) T32107.10

AXCD (coaxial E1) T32107.11

IFUA (symmetrical E1/JT1/T1) T32107.02

IFUC (SDH/SONET) T32107.05

IFUD (coaxial E1) T32107.03

IFUE (Flexbus) T32107.06

IFUF (structured SDH) T32107.07

DN02166696Issue 22-0 en15/06/2007


Product structure



Table 12. AXC plug-in units (cont.)

Part Code

IFUG (Ethernet hub) T32107.08

IFUH (ATM over Ethernet) T32107.12

Table 13. Product documentation

Product Code

AXC C3.0 Product Doc NED NOLS C33857.80

AXC C3.0 Product Doc NED CD ROM (1 pcs) C33857.90

AXC C3.0 Product Doc NED CD ROM (10 pcs) C33857.09

Table 14. Product Overview

Product Code

Nokia AXC ATM cross-connect Product OverviewNED NOLS

C33857.81


15/06/2007




10 Technical specifications

10.1 AXC performance

10.1.1 Traffic capacity

Table 15. Capacity of AXUA

Property Value

Switching capacity 1.2 Gbit/s

Simultaneous connections 1000 (with any mix of VPs and VCs)

Supported ATM service categories Constant Bit Rate (CBR)


ATM Forum af-tm-0056.000 (Traffic

Management)

Supported cross-connections semi-permanent Virtual Path Connections

(VPC)

semi-permanent Virtual Channel

Connections (VCC)

Table 16. Capacity of AXUB

Property Value

Switching capacity 1.2 Gbit/s


DN02166696Issue 22-0 en15/06/2007


Technical specifications



Table 16. Capacity of AXUB (cont.)

Property Value




Management)


(VPC)


connections (VCC)

Table 17. Capacity of integrated IP router

Property Value

Maximum throughput 1.5 Mbit/s

Maximum number of static routes 100

Maximum Transfer Unit (MTU) size 1500 bytes

Maximum number of IP DCN interfaces 96IPoA encapsulation LLC/SNAP

Note

The maximum MTU size in OMU (RNC) and third-party IP routers must

be configured to 1500 bytes, since larger MTUs are discarded by the

AXC.

Table 18. Capacity of AXCC and AXCD

Property Value

Switching capacity 165 Mbit/s



15/06/2007




Table 18. Capacity of AXCC and AXCD (cont.)

Property Value




Management)


(VPC)


connections (VCC)

Interface capacity 8 x 2.048 Mbit/s (E1)

8 x 1.544 Mbit/s (JT1, AXCC only)

8 x 1.544 Mbit/s (T1, AXCC only)

ATM capacity 8 x 1.920 Mbit/s; 8 x 4 528 cells/s (E1)

8 x 1.536 Mbit/s; 8 x 3 622 cells/s (JT1,

AXCC only)

8 x 1.536 Mbit/s; 8 x 3 622 cells/s (T1,

AXCC only)

Tolerance range ± 50 ppm (E1)

± 32 ppm (JT1, AXCC only)± 32 ppm (T1, AXCC only)

Table 19. Capacity of IFUA

Property Value

Capacity 8 x 2.048 Mbit/s (E1)

8 x 1.544 Mbit/s (JT1)

8 x 1.544 Mbit/s (T1)


8 x 1.536 Mbit/s; 8 x 3 622 cells/s (JT1)

8 x 1.536 Mbit/s; 8 x 3 622 cells/s (T1)


± 32 ppm (JT1)

± 32 ppm (T1)

DN02166696Issue 22-0 en15/06/2007





Table 20. Capacity of IFUC

Property Value

Capacity 3 x 155.52 Mbit/s (STM-1/VC-4; OC-3)

ATM capacity 3 x 149.760 Mbit/s; 3 x 353 207 cells/s

(STM-1/VC-4; OC-3)

Tolerance range ± 20 ppm (STM-1/VC-4; OC-3)

Any mix of SDH or SONET interfaces is possible on optical interfaces 1 - 3.

Table 21. Capacity of IFUD

Property Value

Capacity 8 x 2.048 Mbit/s (E1)



Table 22. Capacity of IFUE

Property Value

Capacity Up to 16 x 2.048 Mbit/s signals;

microwave radio outdoor unit power

supply


Table 23. Capacity of IFUF

Property Value

Capacity 1 x 155.52 Mbit/s (STM-1)

Mapping 63 x VC-12 (63 x E1 with 2.048 Mbit/s)


Tolerance range ± 20 ppm


15/06/2007




Table 24. Capacity of IFUH

Property Value

Ethernet capacity 100 Mbit/s (for both Fast Ethernet and

Gigabit Ethernet)

ATM capacity 60 Mbit/s

Note

The tolerance ranges given in this section correspond to the equipmentrequirements. The RAN system requirement for Nokia base stations is

± 0.015 ppm which is needed in order to fulfil the 3GPP requirements

for the air interface. The extracted clock signal from the I ub interface or an external clock source is used as the BTS clock reference source in a

WCDMA network.

10.1.2 Operation

Delays

Table 25. Estimated intrinsic delays

Interface type Estimated intrinsic delay/interface

STM-1/OC-3 16 μs

STM-1/VC-12 380 μs

E1 260 μs

JT1 316 μs

IMA (n x E1) 800 μs

IMA (n x JT1) 1000 μs

IMA (n x VC-12) 1850 μs

Flexbus 30 μs

CBR Cross-connection 350 μs

UBR Cross-connection 0 μs

AAL2 switching 200 μs

DN02166696Issue 22-0 en15/06/2007





When estimating Cell Transfer Delay (CDT), the AAL2 switching delay has

to be taken into account only in BTS AAL2 multiplexing, not in caseswhere AAL2 traffic is chained through the AXC. The delay caused by CIF

is insignificant and has no effect on CDT.

Table 26. Estimated generated Cell Delay Variation (CDV)

Interface CDV for CBR CDV for UBR

STM-1/OC-3 12 μs 12 μs

STM-1/VC-12 25 μs 25 μs

E1 660 μs 220 μs

JT1 828 μs 276 μs

IMA (2 x E1) 120 μs 120 μs

IMA (4 x E1) 70 μs 70 μs

IMA (8 x E1) 40 μs 40 μs

IMA (2 x JT1) 160 μs 160 μs

IMA (4 x JT1) 85 μs 85 μs

IMA (n x VC-12) 15 μs 15 μs

The following example illustrates how the estimated delay can becalculated for the STM-1 - IMA (2 x E1) connection shown in the figure

below.

Figure 60. Estimated delay

If the connection is of type UBR, the mean Cell Transfer Delay can be

calculated with the following formula: intrinsic STM-1 + intrinsic E1 +

intrinsic IMA (n x E1) or 16 + 260 + 800 = 1076 μs.

If the connection is of type CBR, the mean Cell Transfer Delay can be

calculated with the following formula: intrinsic STM-1 + CBR CC STM-1 +

intrinsic E1 + intrinsic IMA (n x E1) or 16 + 350 + 260 + 800 = 1426 μs.

AXCSTM-1 IMA (2xE1)

Delay


15/06/2007




The maximum Cell Transfer Delay can be calculated with the following

formula: CTD Max = CTD Mean + CDV/2. Thus for this connection themaximum CTD is CTD Mean + CDV IMA (2 x E1)/2, or for the UBR

connection 1076 + 120/2 = 1136 μs and for the CBR connection 1426 +

120/2 = 1486 μs.

The following table shows the Cell Transfer Delay (CTD) mean and

maximum values for these UBR and CBR connections. The propagation

delay of any transport medium is not included.

Table 27. CTD for example connection

STM-1 - IMA (2 x E1) CTD mean CTD max

UBR 1076 μs 1136 μs

CBR 1426 μs 1486 μs

Mean time between failures

Table 28. Mean time between failures (years)

Unit MTBF (in years)

AXUA 22

AXUB 20

AXCC 30

AXCD 30

IFUA 29

IFUC 25

IFUD 28

IFUE 19

IFUF 34

IFUG 47

IFUH 32

S-AXC DC-PIU 114

S-AXC fan unit 112

DN02166696Issue 22-0 en15/06/2007





10.2 AXC environmental requirements

Conditions of storage and transport

Nokia AXC complies with the following climatic conditions of storage and

transport:

Table 29. Climatic specifications, storage and transport

All units, storage and transport Ambient temperature of AXC

Temperature -45 to +45°C (storage)

-40 to +70°C (transport)

Nokia AXC complies with the following international standards for storage

and transport:

Table 30. Standards for storage and transport

Standard Standard name

ETS 300 019-1-1

Class 1.3E

Equipment Engineering (EE);

Environmental conditions and

environmental tests for

telecommunications equipment Part 1-1:

Classification of environmental conditions

Storage

ETS 300 019-1-2

Class 2.3






Transportation.

Conditions of operation

Nokia AXC complies with the following climatic conditions of operation:

Table 31. Climatic specifications, operation

All units, operation Ambient temperature of AXC

Temperature -33 °C to -10 °C (warm-up)

-10 to +55 °C (operational)


15/06/2007




Nokia AXC complies with the following international standards for

operation:

Table 32. Standards for operation


ETS 300 019-1-3

Class 3.2

ETS 300 019-1-3A1






Stationary use at weatherprotectedlocations.

ETS 300 019-1-4

Class 4.1

ETS 300 019-1-4A1






Stationary use at non-weatherprotected

locations.

Earthquake requirements

Nokia AXC complies with the following earthquake requirements:

Table 33. Earthquake requirements


Bellcore GR-63-Core, Zone 4 Network Equipment-Building System

(NEBS) Requirements: Physical

Protection

DN02166696Issue 22-0 en15/06/2007





10.3 AXU

10.3.1 AXU interfaces

Table 34. AXUA and AXUB interfaces

Interface Connector

Local Management Port (LMP) 10 BaseT crossed Ethernet interface,

RJ-45 connector

Ethernet standards IEEE 802.3 and

ANSI 8802.3, RFC 1483 (routed)

Q1 management port V.11 interface, D-sub 9 connector

External reference clock interface (ERC) Coaxial BT-43 connector, 75 Ω

1.544 MHz, 2.048 MHz, 2 Mbit/s

Note

In order to fulfil the 3GPP requirements for the air interface, the external

clock references must meet the long-term accuracy of ± 0.015 ppm.

10.3.2 AXU power requirements

Table 35. AXUA power supply and consumption

Property Value

DC power supply -37.5 to -60 VDC

Power consumption (typical) 35 W

Power consumption (max.) 40 W


15/06/2007




Table 36. AXUB power supply and consumption

Property Value




10.3.3 AXU dimensions and weight

Table 37. AXUA dimensions

Property Value (metric)

Height 264 mm

Width 25 mm

Depth 285 mm (incl. front panel)

Weight 800 g

Table 38. AXUB dimensions


Height 264 mm

Width 25 mm


Weight 900 g

DN02166696Issue 22-0 en15/06/2007





10.4 AXCC

10.4.1 AXCC interfaces

Table 39. AXCC interfaces

Interface Connector

E1/JT1/T1 interfaces TQ connector (symmetrical), 120/110/100 Ω

ITU-T G.703/ G.704

TTC JT-G.703/ TTC JT-G.704

ANSI T1.403/T1.102

ATM Forum af-phy-0064.000 (E1 Physical

Interface Specification)

ATM Forum af-phy-0086.000 (Inverse

Multiplexing for ATM (IMA))



ATM Forum af-vtoa-0078.000 (Circuit

Emulation Service)Local Management Port (LMP) 10 BaseT crossed Ethernet interface, RJ-45

connector

Ethernet standards IEEE 802.3 and ANSI

8802.3, RFC 1483 (routed)


External reference clock interface

(ERC)

Coaxial BT-43 connector, 75 Ω

1.544 MHz, 2.048 MHz

10.4.2 AXCC power requirements

Table 40. AXCC power supply and consumption

Property Value





15/06/2007




10.4.3 AXCC dimensions and weight

Table 41. AXCC dimensions and weight


Height 264 mm

Width 50 mm


Weight 950 g

10.5 AXCD

10.5.1 AXCD interfaces

Table 42. AXCD interfaces

Interface Connector

E1 interfaces Coaxial BT-43 connectors, 75 Ω

ITU-T G.703

ITU-T G.704








Emulation Service)

Local Management Port (LMP) 10 BaseT crossed Ethernet interface, RJ-

45 connector


8802.3, RFC 1483 (routed)


DN02166696Issue 22-0 en15/06/2007





Table 42. AXCD interfaces (cont.)

Interface Connector

External reference clock interface (ERC) Coaxial BT-43 connector, 75 Ω

1.544 MHz, 2.048 MHz

10.5.2 AXCD power requirements

Table 43. AXCD power supply and consumption

Property Value




10.5.3 AXCD dimensions and weight

Table 44. AXCD dimensions and weight


Height 264 mm

Width 50 mm


Weight 950 g


15/06/2007




10.6 IFUA

10.6.1 IFUA interfaces

Table 45. IFUA interfaces

Interface Connector

E1/JT1/T1 interfaces TQ connector (symmetrical), 120/110/

100 Ω

ITU-T G.703/ G.704

TTC JT-G.703/ TTC JT-G.704

ANSI T1.403/T1.102

ATM Forum af-phy-0130.000 (ATM on

Fractional E1/T1)





ATM Forum af-phy-0086.001 (InverseMultiplexing for ATM (IMA))


Emulation Service)

10.6.2 IFUA power requirements

Table 46. IFUA power supply and consumption

Property Value




DN02166696Issue 22-0 en15/06/2007





10.6.3 IFUA dimensions and weight

Table 47. IFUA dimensions


Height 264 mm

Width 25 mm


Weight 850 g

10.7 IFUC

10.7.1 IFUC interfaces

Table 48. IFUC interfaces

Interface Connector

Optical interfaces 1 – 3 LC connector, 0°

ITU-T G.707

TTC JT-G.707

ANSI T1.105.06

Table 49. STM-1/OC-3 optical interface characteristics

Property Value for STM-1 Value for

OC-3

Nominal bit

rate (kbit/s)

155 520 155 520

Application

code

I-1

ITU-T G.957

I-1

ATM megalink

service UNI

S-1.1

TTC JT-G.957

SR-1

ANSI

T1.105.06

Type of fibre SM

(G.652)

SM

(G.652)

SM

(G.652)

SM

(G.652)


15/06/2007




Table 49. STM-1/OC-3 optical interface characteristics (cont.)


OC-3

Operating

wavelength

range (nm)

1260 - 1360 1260 - 1360 1261 - 1360 1260 - 1360

Transmitter at reference point S

Transmitter

laser type

MLM MLM MLM MLM

Spectral

characteristics:-max. RMS

width (nm)

40 40 7.7 40

Max. mean

launched

power (dBm)

-8 -8 -8 -8

Min. mean

launched

power (dBm)

-15 -15 -15 -15

Min. extinction

ratio (dB)

8.2 8.2 8.2 8.2

Optical path between S and R

Attenuation

range (dB)

0 - 7 0 - 7 0 - 12 0 - 7

Max.

dispersion (ps/

nm)

18 18 96 18

Min. optical

return loss of

cable plant at

S, incl. any

connectors

(dB)

NA NA NA NA

Max. discrete

reflectance

between S and

R (dB)

NA NA NA NA

Receiver at reference point R

Min. sensitivity

(dBm)

-23 -23 -28 -23

Max. input

power (dBm)

-8 -8 -8 -8

DN02166696Issue 22-0 en15/06/2007





Table 49. STM-1/OC-3 optical interface characteristics (cont.)


OC-3

Max. optical

path penalty

(dB)

1 1 1 1

Max.

reflectance of

receiver,

measured at R

(dB)

NA NA NA NA

10.7.2 IFUC power requirements

Table 50. IFUC power supply and consumption

Property Value




10.7.3 IFUC dimensions and weight

Table 51. IFUC dimensions


Height 264 mm

Width 25 mm


Weight 750 g


15/06/2007




10.8 IFUD

10.8.1 IFUD interfaces

Table 52. IFUD interfaces

Interface Connector

E1 interfaces Coaxial BT –43 connector, 75 Ω

ITU-T G.703

ITU-T G.704

ATM Forum af-phy-0130.000 (ATM on

Fractional E1)







ATM Forum af-vtoa-0078.000 (CircuitEmulation Service)

10.8.2 IFUD power requirements

Table 53. IFUD power supply and consumption

Property Value




DN02166696Issue 22-0 en15/06/2007





10.8.3 IFUD dimensions and weight

Table 54. IFUD dimensions


Height 264 mm

Width 25 mm


Weight 800 g

10.9 IFUE

10.9.1 IFUE interfaces

Table 55. IFUE interfaces

Interface Connector

Flexbus interfaces 1-3

FB1, FB2, FB3

TNC connector 50 Ω (female)







ATM Forum at-vtoa-0078.000 (Circuit

Emulation Service)

Local Management Port (LMP) BQ connector

Measurement Point (MP) SMB connector

Table 56. Flexbus cable requirements

Property Value

Cable type Coaxial cable, double shielded or semi-

rigid


15/06/2007




Table 56. Flexbus cable requirements (cont.)

Property Value

Characteristic impedance 50 ± 2 Ω

DC resistance < 4.6 Ω (sum of inner and outer

conductor)

Data attenuation < 9.0 dB at 19 MHz

Flexbus signals - DC power supply

- Bidirectional data (37 Mbit/s, NRZ code,

1.4 V pulse amplitude)

Note

Over-voltage protection and cable equalizer are integral parts of the Flexbus

interface. Primary over-voltage protection is a 90 V gas-arrester. External gas-

arresters can be used as well.

To provide a sufficient long-term over-current protection to Flexbus cables, these

have to be routed through metallic tubes.

Table 57. Recommended cable types

RG-223 Maximum length 140 m

RG-214 Maximum length 300 m

10.9.2 IFUE power requirements

Table 58. IFUE power supply and consumption

Property Value

DC power supply -40.5 to - 60 VDC



Remote power feeding per Flexbus

interface (typical)

30 W

Power consumption for remote power

feeding per Flexbus interface (max.)

35 W

DN02166696Issue 22-0 en15/06/2007





10.9.3 IFUE dimensions and weight

Table 59. IFUE dimensions


Height 264 mm

Width 25 mm


Weight 1000 g

10.10 IFUF

10.10.1 IFUF interfaces

Table 60. IFUF interfaces

Interface Connector

Optical interface LC connector, 0°

ITU-T G.707

ITU-T G.783





Table 61. STM-1 optical interface characteristics

Property Value for STM-1

Nominal bit

rate (kbit/s)

155 520

Application

code

I-1

ITU-T G.957

I-1

ATM megalink service

UNI

S-1.1

TTC JT-G.957


15/06/2007




Table 61. STM-1 optical interface characteristics (cont.)

Property Value for STM-1

Type of f ibre SM

(G.652)

SM

(G.652)

SM

(G.652)

Operating

wavelength

range (nm)

1260 - 1360 1260 - 1360 1261 - 1360

Transmitter at reference point S

Transmitter

laser type

MLM MLM MLM

Spectral

characteristics:

-max. RMS

width (nm)

40 40 7.7

Max. mean

launched

power (dBm)

-8 -8 -8

Min. mean

launched

power (dBm)

-15 -15 -15

Min. extinction

ratio (dB)

8.2 8.2 8.2

Optical path between S and R

Attenuation

range (dB)

0 - 7 0 - 7 0 - 12

Max.

dispersion (ps/

nm)

18 18 96

Min. optical

return loss of

cable plant at

S, incl. any

connectors(dB)

NA NA NA

Max. discrete

reflectance

between S and

R (dB)

NA NA NA

Receiver at reference point R

Min. sensitivity

(dBm)

-23 -23 -28

Max. input

power (dBm)

-8 -8 -8

DN02166696Issue 22-0 en15/06/2007





10.11 IFUG

10.11.1 IFUG interfaces

Table 64. IFUG interfaces

Interface Connector

Ethernet port 10 BaseT, RJ-45 connector


8802.3

10.11.2 IFUG power requirements

Table 65. IFUG power supply and consumption

Property Value



10.11.3 IFUG dimensions and weight

Table 66. IFUG dimensions


Height 264 mm

Width 25 mm


Weight 500 g

DN02166696Issue 22-0 en15/06/2007





10.12 IFUH

10.12.1 IFUH interfaces

Table 67. IFUH interfaces

Interface Connector

Ethernet ports 1-2 (Fast Ethernet) 10 BaseT, RJ-45 connector

Ethernet standards IEEE 802.3 and IEEE

802.1Q

Ethernet port 3 (Gigabit Ethernet, optical) SFP module compliant with Multi-Sourcing

Agreement

Class 1 Laser Product

1000 Base-LX or 1000-Base-SX

Industrial temperature range -40°C...+85°

C

SFF-8472 compliant diagnostic monitoring

with internal calibration

Extraction Bail Acutator Latch

SFF Committee INF-8074iEthernet standards IEEE 802.3 and IEEE

802.1Q

10.12.2 IFUH power requirements

Table 68. IFUH power supply and consumption

Property Value





15/06/2007




10.12.3 IFUH dimensions and weight

Table 69. IFUH dimensions


Height 264 mm

Width 25 mm


Weight 1000 g

10.13 Stand-alone mechanics

10.13.1 S-AXC power requirements

Table 70. S-AXC power supply and power consumption

Property Value


Power consumption (max.) < 500 W

Recommended ext. fuse rating 16 A, 20 A, 25 A

Ext. power cable recommendation 2.5 - 4 mm2

Power loss (output diodes not connected) < 1.5 V * Iload

Fan unit power consumption 6 W

DC-PIU power consumption at 500 W

load

10 W (single mode, output diode not

used)

15 W (protected mode, output diode

used)

The maximum power consumption of 500 W of the Nokia S-AXC cartridge

is reached with a combination of 3 IFUE interface units, 9 connected and

powered Nokia FlexiHoppers, 2 AXU units and 1 IFUC interface unit. The

maximum number of powered FlexiHoppers is nine, but up to 5 IFUE

interface units can be installed in Nokia S-AXC.

DN02166696Issue 22-0 en15/06/2007





Table 71. DC-PIU energy storage

Property Value

Capacitance > 6 mF

Holdup capacity:

. Uout drops from 54 V to 40.5 V > 4.5 ms at maximum load (800 W)

Table 72. DC-PIU alarm interface

Property Value

Alarm configurations GND or VPB referenced or closed loop

Expected voltage level with reference to

GND at alarm inputs A2in, B2in and D2in,

no alarm

2.8 ... 7.0 V

Expected voltage level with reference to

GND at alarm inputs A2in, B2in and D2in,

alarm

0.0 ... 1.5 V

Input impedance 10 kOhms (pull-up resistors to + 5 V)

Maximum ratings of the relay outputs at –

48 Vdc, Resistive load IDC

0.5 A

Maximum ratings of the relay outputs at –

48 Vdc, Inductive load IDC

0.15 A

Max. resistance (DC) with closed relay

contacts

0.5 Ohm

Min. resistance (DC) with open relay

contacts

1 MOhm

10.13.2 S-AXC dimensions and weight

Table 73. Dimensions of S-AXC


Height 400 mm (9HU)

Width 485 mm

Depth < 350 mm


15/06/2007




Table 73. Dimensions of S-AXC (cont.)


Weight 14.6 kg (empty)

33 kg (fully equipped)

Table 74. Dimensions of 6-slot cartridge


Height 330 mm

Width 170 mm

Depth 320 mm

Weight 4600 g

Table 75. Dimensions of Fan unit


Height 33 mm

Width 165 mm

Depth 310 mm

Weight 1100 g

Table 76. Dimensions of DC-PIU


Height 265 mm

Width 36 mm

Depth 210 mm

Weight 1500 g

DN02166696Issue 22-0 en15/06/2007





10.14 Nokia AXC Manager and Nokia AXC-FB Hopper

Manager system requirements

Table 77. Hardware requirements for Nokia AXC Manager and Nokia AXC-FB

Hopper Manager

Requirement Value

Processor Intel Pentium II 600 MHz or higher

RAM Min. 64 MB

Hard disk space Min. 50 MB exclusively for AXC Manager, 100 MB

recommended

Display Colour display, minimum resolution 800 x 600.

1024 x 768 with 16 bit or more colour depth

recommended.

Accessories CD-ROM or DVD drive (optional)

Microsoft Windows -compatible mouse or pointing

device with required software

Microsoft Windows -compatible printer (optional)

Communication cable between PC and AXC (10

BaseT crossed Ethernet with RJ-45 connector)

Interface ports Ethernet port

Serial port or parallel port for printer

Mouse port (in case mouse is used as the

pointing device)

Table 78. Software requirements for Nokia AXC Manager and Nokia AXC-FB

Hopper Manager

Operating System Microsoft Windows 2000, Windows XPRegional settings English (United States, United Kingdom,

Ireland), Finnish, German (Standard)


15/06/2007




10.15 AXC standards

10.15.1 Interface standards and recommendations

E1 interface

Table 79. Recommendations relating to line interface E1

Standard Description

ITU-T G.703 Physical/electrical characteristics of

hierarchical digital interfaces

ITU-T G.704 Synchronous frame structures used at

primary and secondary hierarchical levels

ITU-T G.706 Frame alignment and cyclic redundancy

check procedures (CRC) relating to basic

frame structures defined in

Recommendation G.704

ITU-T G.775 Loss of Signal (LOS), Alarm Indication

Signal (AIS) and Remote Defect

Indication (RDI). Defect detection and

clearance criteria of PDH signals

ITU-T G.804 ATM cell mapping into PlesiochronousDigital Hierarchy (PDH)

ITU-T G.823 The control of jitter and wander within

digital networks which are based on the

2048 kbit/s hierarchy

ITU-T G.826 Error performance parameters and

objectives for international, constant bit

rate digital paths at or above primary rate

ETS 300 011 Integrated Services Digital Network

(ISDN) Primary rate User - Network

Interface (UNI), Part 1: Layer 1

specification

ETS 300 166 Transmission and Multiplexing; Physical

and electrical characteristics of

hierarchical digital interfaces for

equipment using 2048 kbit/s - based

plesiochronous or synchronous digital

interfaces

ATM Forum af-phy-0064.000 E1 Physical Interface Specification

ATM Forum af-phy-0086.000 Inverse Multiplexing for ATM (IMA)


ATM Forum af-phy-0130.000 ATM on Fractional E1/T1

DN02166696Issue 22-0 en15/06/2007





Table 79. Recommendations relating to line interface E1 (cont.)


ATM Forum af-vtoa-0078.000 Circuit Emulation Service Interoperability

JT1 interface

Table 80. Recommendations relating to line interface JT1

Standard DescriptionITU-T G.703 Physical/electrical characteristics of

hierarchical digital interfaces

TTC JT-G.703 Physical characteristics of hierarchical

digital interfaces

TTC JT-G.704 Frame structures used at primary and

secondary hierarchical interfaces

TTC JT-G.706 Frame synchronisation and CRC-

procedure

ITU-T G.775 Loss of Signal (LOS), Alarm Indication

Signal (AIS) and Remote Defect

Indication (RDI). Defect detection andclearance criteria of PDH signals

ITU-T G.804 ATM cell mapping into Plesiochronous

Digital Hierarchy (PDH)







TTC JT-I.431 ISDN Primary Rate User-Network

Interface Layer 1 - Specification

ETS 300 011 Integrated Services Digital Network

(ISDN) Primary rate User - Network

Interface (UNI), Part 1: Layer 1

specification

ETS 300 166 Transmission and Multiplexing; Physical

and electrical characteristics of

hierarchical digital interfaces for

equipment using 2048 kbit/s - based

plesiochronous or synchronous digital

interfaces



15/06/2007




Table 80. Recommendations relating to line interface JT1 (cont.)





T1 interface

Table 81. Recommendations relating to line interface T1

Recommendation Recommendation name

ANSI T1.403 Telecommunications - Network-to-

Customer Installation - DS1 Metallic

Interface

ANSI T1.102 Telecommunications - Digital Hierarchy

Electrical Interfaces

ANSI T1.408 Telecommunications - Integrated Services

Digital Networks (ISDN) Primary Rate -

Customer Installation Metallic Interfaces

Layer 1 Specification





STM-1/OC-3 interface

Table 82. Recommendations relating to STM-1/OC-3 interface


ITU-T G.707 Network - Node Interface for the

Synchronous Digital Hierarchy (SDH)

TTC JT-G.707 Network - Node Interface for the


ITU-T G.783 Characteristics of Synchronous Digital

Hierarchy (SDH) equipment functional

blocks

DN02166696Issue 22-0 en15/06/2007





Table 82. Recommendations relating to STM-1/OC-3 interface (cont.)





TTC JT-G.825 The control of jitter and wander within






ITU-T G.957 Optical interfaces for equipment and

systems relating to the synchronous

hierarchy

TTC JT-G.957 Optical interfaces for equipment and

systems relating to the synchronous

hierarchy

ITU-T G.958 Digital line systems based on the

Synchronous Digital Hierarchy for use on

optical fibre cables

TTC JT-G.958 Digital line systems based on the

Synchronous Digital Hierarchy for use on

optical fibre cables

ITU-T I.356 B-ISDN ATM layer cell transfer

performance

TTC JT-I.356 B-ISDN ATM layer cell transfer

performance

ITU-T I.432.2 B-ISDN User - Network Interface;

Physical layer specification: 155 520 kbit/

s and 622 080 kbit/s operation

TTC JT-I.432.2 B-ISDN User - Network Interface;

Physical layer specification: 155 520 kbit/

s and 622 080 kbit/s operation

TTC JT-I.432.4 B-ISDN User - Network Interface;Physical layer specification: 51 849 kbit/s

operation

ANSI T1.105.06 Telecommunications - Synchronous

Optical Network (SONET) - Physical

Layer Specifications




15/06/2007




Flexbus interface

Table 83. Recommendations relating to Flexbus interface


ITU-T G.704 Synchronous frame structures used at

primary and secondary hierarchical levels

ITU-T G.706 Frame alignment and cyclic redundancy

check procedures (CGC) relating to basic

frame structures defined in

Recommendation G.704

ITU-T G.775 Loss of Signal (LOS), Alarm IndicationSignal (AIS) and Remote Defect

Indication (RDI). Defect detection and

clearance criteria of PDH signals

ITU-T G.804 ATM cell mapping into Plesiochronous

Digital Hierarchy (PDH)







ITU-T G.921 Digital sections based on the 2048 kbit/s

hierarchy




IP DCN Extension interface

Table 84. Recommendations relating to IP DCN Extension interface


IEEE802.3/ANSI8802.3 Carrier Sense Mult iple Access with

Collision Detection (CSMA/CD) Access

Method and Physical Layer Specifications

RFC 1027 Using ARP to Implement Transparent

Subnet Gateways

RFC 1483 Multiprotocol Encapsulation over ATM

Adaptation Layer 5

DN02166696Issue 22-0 en15/06/2007





Table 84. Recommendations relating to IP DCN Extension interface (cont.)


RFC 2131 Dynamic Host Configuration Protocol

RFC 2132 DHCP Options and BOOTP Vendor

Extensions

RFC 2225 Classical IP and ARP over ATM

RFC 2328 OSPF Version 2

RFC 3004 User Class Option for DHCP

10.15.2 ATM capabilities recommendations

Table 85. Recommendations relating to ATM capabilities of AXC

Recommendation Recommendation name

ITU-T Q.2630.1 AAL type 2 signalling protocol (Capability

SET 1)

ITU-T Q.2630.2 AAL type 2 signalling protocol (Capability

SET 2)

ITU-T Q.2150.2 AAL type 2 signalling converter on

SSCOP

ITU-T Q.2130 B-ISDN signalling ATM adaptation layer -

Service specifc coordination function for

support of signalling at the user-network

interface (SSCF at UNI)

ITU-T Q.2210 Service Specific Connection Oriented

Protocol (SSCOP)

ITU-T I.363.2 Type 2 AAL

ITU-T I.363.5 Type 5 AAL

ITU-T I.732 B-ISDN equipment aspects - Functional

characteristics of ATM equipment

3GPP TS 25.426 UTRAN Iur and Iub Interface Data

Transport & Transport Signalling for DCH

Data Streams v.3.4.0


15/06/2007




10.15.3 EMC standards

Table 86. EMC recommendations


EN 50081-1 Electromagnetic compatibility - Generic

emission standard. Part 1: Residential,

commercial and light industry.

EN 50082-1 Electromagnetic compatibility - Generic

immunity standard. Part 1: Residential,

commercial and light industry.

EN 55022 Limits and methods of measurement of

radio disturbance characteristics of

information technology equipment.

EN 61000-4-2 Electromagnetic compatibility (EMC) -

Part 4: Testing and measurement

techniques; Section 2: Electrostatic

discharge immunity test, Basic EMC

Publication.



techniques; Section 3: Radiated, Radio-

frequency electromagnetic field immunity

test.



techniques; Section 4: Electrical fast

transient/burst immunity test, Basic EMC

Publication.



techniques; Section 5: Surge immunity

tests.



techniques; Section 6: Immunity toconducted disturbances induced by radio-

frequency fields.

IEC 1000-4-8 Electromagnetic compatibility (EMC) -


techniques; Section 8: Power frequency

magnetic field immunity test, Basic EMC

Publication.

IEC 1000-4-9 Pulse magnetic field immunity test.

DN02166696Issue 22-0 en15/06/2007





Table 86. EMC recommendations (cont.)


ITU-T K.20 Resistibility of telecommunication

switching equipment installed in a

telecommunications centre to

overvoltages and overcurrents

ITU-T K.41 Resistibility of internal interfaces of

telecommunication centres to surge

overvoltages

CISPR Publication No. 16-1 Specification for radio disturbance and

immunity measuring apparatus and

methods.

ETS 300 132-2 Equipment Engineering (EE); Power

supply interface at the input to

telecommunications equipment; Part 2:

Operated by direct current

10.15.4 Environmental standards

Table 87. Environmental recommendations


ETS 300 019-1-1

Class 1.3E




telecommunications equipment; Storage.

ETS 300 019-1-2

Class 2.3




telecommunications equipment;

Transportation.

ETS 300 019-1-3

Class 3.2

ETS 300 019-1-3A1




telecommunications equipment; Stationary

use at weatherprotected locations.

ETS 300 019-1-4

Class 4.1

ETS 300 019-1-4A1




telecommunications equipment; Stationary

use at non-weatherprotected locations.


15/06/2007




Table 87. Environmental recommendations (cont.)


Bellcore GR-63-Core, Zone 4 Network Equipment-Building System

(NEBS) Requirements: Physical

Protection

10.15.5 Safety recommendations

Table 88. Safety recommendations


EN 60825-1 Safety of laser products - Part 1:

Equipment classification, requirements

and user ’s guide

EN 60825-2 Safety of laser products - Part 2: Safety of


product description of axc

Documents