differences between huawei atca-based and cpci-based softswitches issue2.0

HUAWEI TECHNOLOGIES CO., LTD.

www.huawei.com

HUAWEI Confidential

Security Level: 内部公开

Differences Between Huawei ATCA-Based and CPCI-Based SoftSwitches

ISSUE2.0

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential

This slides describe the differences between

ATCA-based and CPCI-based softswitches

from different aspects. Upon completion of this

course, you will be able to master the changes

made to the ATCA-based softswitch compared

with the CPCI-based softswitch.


Chapter 1Chapter 1 Overall DifferencesOverall Differences

Chapter 2 Hardware Differences

Chapter 3 Background Differences

Chapter 4 NMS Differences

Chapter 5 O&M Differences

Chapter 6 Function Differences

Chapter 7 Documentation Differences


Chapter 1 Overall DifferencesChapter 1 Overall Differences

1.1 Networking

1.2 Performance and Reliability

1.3 Software Architecture


Networking (No Difference Between ATCA and CPCI)

Huawei's mobile soft switch supports various networking modes, such as the multi-area network, N+1 dual homing, and MSC Pool. The network structure of ATCA-based softswitches is the same as the network structure of CPCI-based soft switches. You can use a mixture of ATCA-based softswitches and CPCI-based softswitches to form an MSC Pool.

The ATCA-based soft switch has a large capacity. Therefore, it uses multiple signaling points to interwork with other NEs. MPLS ---Multiprotocol label switching

BSC1 BSC2

MSC Server

PC 0

PC 2

BSC1 BSC2

PC 0

PC 1

N+1 Dual Homing + Mini-Flex MSC Pool + Mini-Flex

BSC3BSC3

Mini-Flex

Backup MSS1 MSS2

Mini-Flex

STP HLR/SCP/SMSC…

STP HLR/SCP/SMSC…

BSC4

Mini-Flex

BSC4

Backup Center

IP/MPLS IP/MPLS

Heart BeatMSC Server



1.1 Networking




Performance (ATCA is much better than CPCI) and Reliability (No Difference Between ATCA and CPCI) High performance

The ATCA(ADVANCE TELECOMMUNICATION COMPUTE ARCHITECTURE)-based softswitch

uses Intel four-core CPUs, with a main frequency of 2.13 GHz and data switching bandwidth of 2.5

Tbit/s.

The ATCA-based soft switch uses server blades, which facilitate distributed deployment.

The performance of a fully loaded ATCA-based VMSC with two cabinets and three subracks can

reach 26 MBHCA. Such a VMSC can support 10 million subscribers.

High integration and low power consumption

The following data is obtained based on the second traffic model of China Mobile in 2009:

The power consumption of an ATCA-based cabinet is 1.8 kW. The power consumption of two CPCI-

COMPACT PCI ----PCIMG PCI INDUSTRIAL COMPUTER ARCHITECTURE GROUP based

cabinets is 2.3 kW.

The occupied area of an ATCA-based cabinet is 0.48 square meters. The occupied area of an CPCI-

PCI --- PHERIFERIAL COMPONENET INTERCONNECT based cabinet is 0.96 square meters.

High reliability (99.999%)

All units of the ATCA-based Soft's witch are hot-swappable.

The ATCA-based soft's witch provides redundancy of all key components, such as the power

modules, fan modules, management modules, and processing modules. The ATCA platform enables the software to capitalize on the advanced hardware with multiple cores and multiple CPUs, thus improving the system performance without affecting the reliability.



1.1 Networking




Software Architecture (No Big Difference Between ATCA and CPCI)

The software architecture is consistent for the ATCA and CPCI platforms.

The differences between them are as follows:

The background software of the ATCA platform consists of the OMU, LMT, and

WebUI. The OMU is deployed on the UPBA1, and the LMT and WebUI on PCs to

implement man-machine interaction and device management.

The background software of the CPCI platform consists of the BAM and LMT.

The BAM is deployed on a server, and the LMT on PCs to implement man-

machine interaction and device management.

Operating system

Middleware

Communication

Protocol processing

Service processing

Operating system

Database software

PerformanceConfiguration

AlarmMaintenance

PerformanceConfiguration

AlarmMaintenance WebUI

LMT

Signaling interface and bearer

Database

Device mgmt Device mgmt

Host software Background software


The ATCA Softswitch Changes to Use the Linux OS

Component CPCI ATCA

Service boards VxWorks Compact Linux

iGWB Windows server Linux boards

XPTU Windows server Linux boards (The XPTU and

the OMU are integrated into

the same board)

BAM/OMU Windows server, SQL

database

Linux boards, Oracle

database

Note: When the SOSM networking is enabled, an XPTU server based on

the Windows OS is required.


Chapter 2 Hardware DifferencesChapter 2 Hardware Differences

2.1 Hardware Architecture

2.2 Hardware Specifications


Hardware Structure (ATCA Different from CPCI)

WEPI

WBFI WIFM

WCKI

WCPC

WBSG

WCDB

WMGC

WCCU

WSIU/WSMU

WBAI WAFM

iGWB

BAM

E1interface

BITS

FEinterface

ATMinterface

NMS

BC

Interface module Bottom-layersignaling

processingmodule

Serviceprocessing

module

System support module

LAN bus

OSTA bus

WEPIATM-2Minterface WEAM

WHSC

WS

WS

OAM module Hardware architecture (CPCI)

The differences are as follows:

The hardware architecture of the ATCA platform fully complies with the PICMG 3.x standards,

and therefore is an open standard platform.

The hardware architecture of the CPCI platform complies with the PICMG 2.x (PCI industrial

computer architecture group) standards, but is modified based on the requirements of vendors.

The inter-subrack cascading of the ATCA platform is implemented through the internal

SWU/SWI boards. Therefore, the LAN switches used in the CPCI platform are not necessary in

the ATCA platform.

Hardware architecture (ATCA)Hardware architecture (ATCA)


Buses in the ATCA Platform Have Better Extensibility and Are More Compliant to the Standards

CPCI ATCA

H.110 bus Base bus

CPCI bus Fabric bus

Ethernet bus IPMB bus

TDM bus

Buses in the CPCI platform have limited bandwidth:

Bandwidth of the CPCI bus: 2 x 2 Gbit/s

Bandwidth of the H.110 bus: 256 Mbit/s

Bandwidth of the Ethernet bus: 24 x 100 Mbit/s

Buses in the ATCA platform have better extensibility and are more compliant to the

standards:

IPMB bus: It is the device management bus of the OSTA2.0 subrack. It monitors and manages the hardware

in a subrack.

Base bus: It is the bus of the management control plane. It provides a channel for software loading, alarms,

and maintenance.

Fabric bus: It is the data channel of the service plane. It is used to carry service-related information in the

system.

TDM bus: It is used to transmit the data of synchronization clocks and inter-board narrowband timeslots.


Chapter 2 Hardware DifferencesChapter 2 Hardware Differences

2.1 Hardware Architecture

2.2 Hardware Specifications


MSOFTX3000 Hardware (ATCA vs CPCI)Item CPCI ATCA

CPU Power PC 750GL, with a main frequency of

1 G

X86 series, 4-core, with a main frequency of

2.13 G

Number of CPUs

on each board

1 2

Memory 1 GB 24 GB

Cabinet dimensions

(Height x Width x

Depth)

N68E (2.2m x 0.6m x 0.8m) N68E (2.2m x 0.6m x 0.8m)

Subrack

dimensions

9U (height) 19" (width) 14U (height) 19" (width) integrated subrack

Maximum

configuration

Five cabinets with eighteen subracks Two cabinets with three subracks

Weight Smaller than or equal to 450 kg Smaller than or equal to 356 kg

Working voltage -48 V DC -48 V DC/-60 V DC

Working

temperature

5-40 degrees centigrade (long-term) -5-50 degrees centigrade (short-term)

5-40 degrees centigrade (long-term) -5-50 degrees centigrade (short-term)

Working humidity 5%-85% (long-term) 5%-90% (short-term) 5%-85% (long-term) 5%-90% (short-term)


Chapter 3 Background DifferencesChapter 3 Background Differences

3.1 OMU and BAM

3.2 LMT

3.3 Performance Measurement

3.4 CDR Browse


The OMU Provides More Functions Than the BAM

SN CPCI BAM ATCA OMU

1 Supports single-NE management Supports multiple-NE management

2 Run on a server (PC) Run on a board

3 Windows OS Linux OS

4 Supported northbound interface:

MML

Supported northbound interfaces: SNMP,

SOAP, MML, WEB, and FTP

The differences between the OMU and the BAM are as follows:



3.1 OMU and BAM

3.2 LMT


3.4 CDR Browse


The ATCA LMT Supports Layered Management

SN CPCI LMT ATCA LMT

1 Supports single-NE

management.

Supports multiple-NE management.

2 Supports single-layer interface

(The initial interface displayed

after the LMT is launched is an

MML interface).

Supports multiple-layer interface. You can right-

click and choose the CGP node, service and

charging node, MML, tracing, and monitoring.

3 The device panel contains a

uniform interface.

The device panel contains hardware panel and

software panel, displaying the hardware and

software status of the boards in a layered form.

4 You cannot check the status of

BAM processes through the

LMT.

You can check the status of OMU processes

through the LMT.

The differences between the ATCA LMT and the CPCI LMT are as follows:

Note: The CGP is a carrier-class software platform established on the hardware platform. It features high usability, high

performance, easy O&M, and easy integration. The CGP provides the following:

Hardware management and multiple-NE maintenance and management

Bottom-layer function components that support service process development

Environment that supports service process development


Interfaces of the ATCA LMT and CPCI LMT

ATCA LMT CPCI LMT



3.1 OMU and BAM

3.2 LMT


3.4 CDR Browse


The ATCA Softswitch Provides User-Friendly Web-Mode PM Client

SN CPCI PM ATCA PM

1 MML and GUI Web

2 Register PM tasks using MML

commands and GUI

Register PM tasks through the Web client

3 Register objects and tasks

together

Register tasks and objects separately

4 You can enter the registration

through the function sets.

You can enter the registration through objects

and function sets.

The differences between the ATCA PM client and the CPCI PM client are as follows:



3.1 OMU and BAM

3.2 LMT


3.4 CDR Browse


The ATCA iGWB Provides Web-Mode CDR Browse Interface

iGWB »°µ¥ä¯ÀÀ


Chapter 4 NMS DifferencesChapter 4 NMS Differences

4.1 NMS Management

4.2 Patch Operations


NMS Management

The figure on the left shows the NMS (network management system

/OAM)management in the CPCI platform. The NMS directly connects to the

MSOFTX3000 through the MML protocol. In this example, an NMS (M2000)

connects to three MSOFTX3000s.

The figure on the right shows the NMS management in the ATCA platform. The NMS

directly connects to the CGP through the MML and SOAP protocols and indirectly

connects to the MSOFTX3000. The CGP and the MSOFTX3000 are managed by the

NSM as a single entity. The NMS communicates with the MSOFTX3000 through the

CGP.

CPCI

BAM BAM BAM

CGP

MML MML+SOAP

M2000

ATCA


Chapter 4 NMS DifferencesChapter 4 NMS Differences

4.1 NMS Management

4.2 Patch Operations


The ATCA NMS Provides the Hot Patch Management Function

Compared with the NMS of the CPCI platform, the NMS of the ATCA platform

provides the hot patch management function.

Choose Software > Browser, as shown in the figure above. The Software Browser

window is displayed.

Click the NM Server tab and then choose the CGPOMU node. The patches available

on the NMS are displayed. These patches are for the chosen NE.

Click the NE tab and then choose a CGPOMU node. The patches available on the NE

are displayed. You can load, activate, and confirm the patches.


Chapter 5 O&M DifferencesChapter 5 O&M Differences

5.1 Installation

5.2 Configuration

5.3 Upgrade

5.4 Patch


Installation Differences Between ATCA and CPCI Softswitches

OS

The ATCA OMU uses the Linux OS.

The CPCI BAM uses the Windows OS.

Installation mode

In the ATCA platform, sever boards for the OMU and iGWB are pre-installed before delivery

according to the contract. The software of the service boards is loaded from the OMU.

In the ATCA platform, the INU4 windows solution is provided for installing the OS and

database on the OMU boards through PCs.

In the CPCI platform, the servers such as the BAM and iGWB are installed from the CD-

ROM. The software of service boards is loaded from the BAM.



5.1 Installation

5.2 Configuration

5.3 Upgrade

5.4 Patch


Configuration Differences Between ATCA and CPCI Softswitches Configuration entry points

All configuration commands in the CPCI platform have the same entry point.

A new entry point for the basic platform data configuration, that is, the CGP, is added in the

ATCA platform. Service data of the NEs is configured through the NE nodes in a layered

form.

In the ATCA platform, the iGWB is provided by a board. The iGWB-related configuration is

completed through the charging node on the ATCA LMT, ensuring a uniform entry point.

Configuration commands

The configuration commands for the service data remain the same for the ATCA and CPCI

softswitches.

The basic platform data configuration in the ATCA platform is consistent with the

international convention. For example, ADD SHF is changed to ADD RACK. For details

about the changed commands, refer to the software guides delivered with the equipment.



5.1 Installation

5.2 Configuration

5.3 Upgrade

5.4 Patch


Upgrade Differences Between ATCA and CPCI Softswitches ATCA upgrade mode

The ATCA platform provides an upgrade interface based on the WEBUI.

The ATCA platform supports seamless upgrade that only interrupt services for 10 seconds.

The ATCA platform supports the uniform upgrade of the iGWB, OMU, and host.

The ATCA upgrade can be prepared in advance. The formal upgrade takes only 10 minutes.

This minimizes the risks.

CPCI upgrade mode

The CPCI platform is upgraded through the BAM.

The CPCI platform requires more upgrade steps. The iGWB, XPTU, and BAM must be

upgraded separately.

The formal upgrade takes about 90 minutes.



5.1 Installation

5.2 Configuration

5.3 Upgrade

5.4 Patch


Patch Differences Between ATCA and CPCI Softswitches Format of patch files

Patch files are compressed in the ATCA platform, which saves the space of hard disks.

Patch uploading

In the ATCA platform, patch packages are directly sent to specified path of the OMU by the

SFTP tool on the client.

In the CPCI platform, patch files are saved to specified path on the BAM.

Patch loading

Patch loading is the same for the ATCA and CPCI softswitches.


Chapter 6 Function DifferencesChapter 6 Function Differences

6.1 Module Group Configuration

6.2 iGWB


The ATCA Softswitch Provides Module Groups

In the CPCI platform, a board is a module.

The CPCI platform provides boards with different functions, such as the WCCU and WBSG.

When a board is added, a module is configured at the same time.

In the ATCA platform, the software is separated from the hardware to make full use of

multiple cores and multiple CPUs.

Boards are separated from modules. A module group, which is composed by several

modules, is configured on a board. For example, GCU100 and VCU100 are two module

groups.

The configuration of modules is determined by the configuration of module groups. When a

module group is configured, modules are automatically configured and module numbers are

automatically generated.

In the ATCA platform, modules work in active/standby mode. Service boards except the

iGWB, OMU, SMM, and SWU no longer work in active/standby mode. This is similar to

subrack and board in the CPCI platform: subracks do not work in active/standby mode, but

boards work in active/standby mode. Normally, an active module is carried by two boards

that assist each other.


Typical Module Groups

A module in the ATCA is equal to a board in the CPCI.

Module group type contains the number of modules, module type, and information about the

CPU core to which the module is bound.

The MSOFTX3000 provides various types of module groups suitable for different

applications.

Description

General Control Unit 100 (you are advised to configure a pair of this module groups for each subrack of the VMSC)

General Control Unit 101 (you are advised to configure two pairs of this module groups for each subrack of the GMSC/TMSC)

VMSC Control Unit 100 (a module group for expanding the VMSC)

Module group

GCU100 GCU101 VCU100

Core 0 CCU CCU CCU CCU CCU CCU




Core 4 VDB BSG BSG CCU CCU

Core 5 VDB BSG BSG VDB BSG

Core 6 CDB CDB VDB BSG

Core 7 IFM IFM VDB BSG


Chapter 6 Function DifferencesChapter 6 Function Differences

6.1 Module Group Configuration

6.2 iGWB


iGWB Differences Between ATCA and CPCI Softswitches Hardware of the iGWB

In the CPCI platform, the iGWB is installed on two PC servers.

In the ATCA platform, the iGWB is installed on two boards.

Charging networking

In the CPCI platform, all CDR(received clock and data recovery ) files are stored on

the same iGWB server. The billing center obtains CDR files from this iGWB server.

The ATCA platform supports distributed management. Thus, CDR files are stored on

one to three iGWB boards. The billing center obtains CDR files from different iGWB

boards.


Chapter 7 Documentation DifferencesChapter 7 Documentation Differences


Documentation Differences Between ATCA and CPCI

Deleted Manuals New Manuals Remarks

BAM User

Manual

The BAM no longer exists.

Performance

Metrics

Reference

The related information is

provided in the performance

measurement Help.

Performance

Management

This manual describes how to

log in to and use the

performance management

system.

Operator Guide This manual describes the

functions, operation procedure,

and precautions of the client.

Administrator Guide This manual describes how to

manage the OMU system.


The ATCA Softswitch Provides CPI-Format Documentation (1)

Note:

The documentation is classified into five categories: 1. Exemption 2. Description manuals 3. Procedure or service scenario manuals 4. Reference manuals 5. Optional part

Principles:

1. According to international conventions, Library Information and Safety are added at the beginning.

2. The arrangement of manuals agrees with the general habit of readers. Generally, readers first read the description manuals to understand the equipment, and then operate the equipment by referring to the procedure or service scenario manuals and reference manuals.

3. Different target readers can find the manuals they need at the first opportunity. For example, Installation and Commissioning and Operation and Maintenance.

4. The optional part is provided to meet the special requirements. For example, User Manual is used to describe important features of the MSOFTX3000.

Level-1 titlesLevel-1 titles


The ATCA Provides CPI-Format Documentation (2)

Principles for arranging description manuals:The arrangement of description manuals conforms to the cognitive habit. Manuals are classified from system to product to OM functions based on the fault, configuration management, accounting, performance, security (FCAPS) principle.

Principle for arranging network deployment manuals:The main thread is the operation task flow of the engineering scenarios.

Principle for arranging network operation and maintenance manuals:The main thread is the FCAPS principle. Common key tasks are described.

Level-2 titlesLevel-2 titles

谢谢www.huawei.com

differences between huawei atca-based and cpci-based softswitches issue2.0

Documents