Alcatel 5020 MGC

System Description
215 86877 EACK TR

Edition/date Ed. 02, June 2005

Purpose Initial issue

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description Contents Page 2

Contents
About This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Objective. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Readership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Validity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Conventions and Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Network View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Alcatel 5020 MGC Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Alcatel 5020 MGC Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Media Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Access Gateways (AGW, cAGW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Trunk Gateways (TGW). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Residential Gateways / IP Access Devices (RGW/IAD, names used synonymously). 27 SIP-phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Transport Mechanism for bearer and signalling information . . . . . . . . . . . . . . . . . . . . . 27 Bearer Transport by IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 UNI Signalling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Access Signalling Transport by IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AGW, cAGW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H.248 or MGCP RGW / IAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SIP RGW/IAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SIP Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SIGTRAN for Support of Common Channel Signalling Types . . . . . . . . . . . . . . . . . . . Inter MGC Signalling SIP-I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 29 30 30 30 30 30

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description Contents Page 3

Other SIP interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Session Barder Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Support of DHCP/DNS service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Introduction and Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Introduction of Site-Configuration and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction of ALCATEL 5020 MGC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Concept-Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Basic Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Load monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Functional Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inter-Domain Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multi Domain Loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . External interface to TDM network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . External interfaces to packet network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Firewall Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 43 44 49 51 61 61 61 72 73 73 73 86 88

Hardware Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Equipment practice - 3rd party product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 call engine CEs on 3rd party hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 N7-solution on 3rd party hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 call engine Disk Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Related Chassis Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Rack Frame Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Frame Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Grounding and Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Hardware-Numbering-Scheme. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description Contents Page 4

hardware-components used in the Flex21 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Backplane / Midplane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power entry modules (FlexAlarm Modules) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power-supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flex managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cTCA-CEs - (single pentium CPCA) - General Description (CPCA) . . . . . . . . . . . . . . Dual-Processor Board (CPCB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ITCE-types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resource Manager (RM-CE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connection Control Manager (COCO). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SIP Control (SIPCE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SIP IAD Registry (SIPRG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SIGTRAN Control (STRAN). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Internet Protocol Signalling Access (IPACC). . . . . . . . . . . . . . . . . . . . . . . . . . . . . OAM Agent (OAM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Signalling Link N7 Control (SLN7S). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server-types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extended Assistant Billing System (EABS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extended Assistant Routing System (EARS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extended Assistant User Profile System (EAUS) . . . . . . . . . . . . . . . . . . . . . . . . . call engine CE-types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Peripheral and Load (PLCE or PLDA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trunk Gateway Control Element (TGWCS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Access Gateway Control Element (AGWCS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trunk Resource Allocator Control Element (TRAMC) . . . . . . . . . . . . . . . . . . . . . . Traffic Destination Code Control Element (TDC). . . . . . . . . . . . . . . . . . . . . . . . . . RCDS Control Element (RCDS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Traffic Management Control Element (INTM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . cTCA-processors LED-usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . call engine-CEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Filler Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3U Filler Panels (FP3U). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 105 106 106 106 107 112 112 113 113 113 113 114 114 114 115 115 115 116 116 116 116 117 117 117 118 118 118 118 120 120

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description Contents Page 5

6U Air-blocker Filler Panels (FP6UR / FP&U) . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transition Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fabric switch RTM "SwitchUp 6M+2G XB" (SFRTM). . . . . . . . . . . . . . . . . . . . . . Backbone switch RTM "SwitchUp 24G XB" (S24RTM) . . . . . . . . . . . . . . . . . . . . OAMCE/EABS RTM "PM 1116 SFF transition board 1x73GB" (SDRTM) . . . . . ITCE RTM "PM 1116 SFF transition board / no disks" (OGRTM) . . . . . . . . . . . . PLDA RTM "PM 1116 SFF transition board 2x36GB (DDRTM) . . . . . . . . . . . . . SLN7S RTM "SLN7S Feature RTM" (OFRTM) . . . . . . . . . . . . . . . . . . . . . . . . . . Fan-Module (FANB). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Air-filter (AIFA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LED Panel (LEDP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Serial interface access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMC Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . N7 termination PMC "ADAX HDC II SS7 PMC" (N7PMC) . . . . . . . . . . . . . . . . . . PIM Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . N7 termination PIM "ADAX HDCII SS7 PIM" (N7PIM) . . . . . . . . . . . . . . . . . . . . .

120 121 121 121 121 121 122 122 122 122 123 123 125 126 126 126

Topology of internal Packet-Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Connectivity of the CEs in Alcatel 5020 MGC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Plane- and Stage-Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fabric Switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backbone Node Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . On-board Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Virtual Ethernet Switches in JALUNAs call engine-virtualisation . . . . . . . . . . . . . . . . ELMs Virtual Switch Concept. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ethernet Link Maintenance (ELM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connectivity Aspects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Switch Port Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 127 133 134 135 135 139 141 142 142

EMC - System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Environmental. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 ETSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description Contents Page 6

NEBS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Platform Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Software-Platform of ITCE-Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 POSIX compliant operating systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration of OAMCE from SOLARIS7 to MVL CGE 3.1 . . . . . . . . . . . . . . . . . . . . . . . 3rd party SW Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The middle-ware layer called "SERVER PLATFORM" . . . . . . . . . . . . . . . . . . . . . . . . 145 145 145 146

General Addressing/Communication and Location Identification Issues . . . . . . . . . . . . . 151 Physical Transmission Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Load / Traffic Distribution across Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ethernet MAC Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ethernet transmission flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resilient Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Spanning tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Addressing Capabilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Computing MAC-Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Physical CE Address and Physical Blade Reference . . . . . . . . . . . . . . . . . . . . . . Addressing aspects in the call engine-JALUNA context . . . . . . . . . . . . . . . . . . . . Addressing aspects for the Dual Processor blade approach. . . . . . . . . . . . . . . . . LCE_Id and IP address composition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 152 152 153 153 154 154 155 159 160 160 160

Intra-call engine-Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Transport Protocol Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Ethernet transmission flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Inter-Domain Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Middleware (call engine CE ITCE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Functional addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Qualified functional addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Instance addressing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The logical instance addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EPG (call engine CE ITCE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 166 166 166 167 167

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description Contents Page 7

EPI (call engine CE EABS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EDOTCP (call engine CE EAxS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ROMA (call engine CE CMC). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RegLib (ITCE FlexMgr) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IPPoE (call engine CE ITCE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

167 168 168 169 169

Hardware Management Software (ChassisCoordinator, ChassisManager, clients). . . . . 170 System Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 call engine-domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ITCE-domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server-domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . hardware-management-domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Master Alarm Panel indication for x-domain alarms . . . . . . . . . . . . . . . . . . . . . . . . . . Rack Alarm handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ethernet Link Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . hardware Reset API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 174 174 175 176 177 178 178

New TOD synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Backup and Data Restore Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Server domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ITCE domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . complete BACKUP / RESTORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Partial BACKUP / RESTORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call engine domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 182 182 182 183

Loading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Principles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disk-Boot and Network-Boot for ITCE- and call engine-Domain . . . . . . . . . . . . . . . . Initial disk preparation for OAMCEs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disk preparation for PLDAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Error correction loading for call engine-domain . . . . . . . . . . . . . . . . . . . . . . . . . . . Server-Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . hardware-management-Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specific Loading-Features and Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 185 193 193 194 194 194 195

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description Contents Page 8

ITCE-domain:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call engine-domain:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server-domain (EABS only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Package Replacement / Context Dependent Loading. . . . . . . . . . . . . . . . . . . . . .

195 195 195 196

OA&M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 OAM-features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mixed mode TPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Consistency of data provisioned via ORJs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Customer Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Feature continuity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 199 199 200 200

Platform-aspects of N7-solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Measurement data retrieval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description About This Document Page 9

About This Document

Objective
This document defines the Alcatel 5020 MGC architecture. The Alcatel 5020 MGC offers a carrier grade Softswitch solution with superior using cTCA hardware only.

Readership
It addresses to all who are looking for introductory infomation about the electronic documentation set.

Validity
The Electronic Documentation forms the major part of the Customer Documentation for the Alcatel 5020 MGC. Note: Customer Documentation means the complete documentation set that customers get from Alcatel. The typical documentation set comprises the Electronic Documentation and some supplementary documentation, e.g., OEM documentation, see corresponding Overview. Alcatel 5020 MGC is typically used in combination with Alcatel 1000 call engine which is applied with a separate, specific Customer Documentation set, see corresponding Overview (remarks regarding call engine-specific documentation).

Definitions
The following list defines the terms that apply to Alcatel 5020 MGC.

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description About This Document Page 10

Term ACTIVE/ACTIVE (A/A)

Glossary Definition Pair of identical CEs, both are operational and have the view to the data of the mate. In normal operation mode, the first CE of the pair is responsible for the "first" half of the data and its function; the complementary part is handled in the other CE. In case of a failure, which results in an outage, a X-Over (=Crossover) is triggered which forces the available mate to take over the function and the related data of the failed CE. If the failed CE is available to become operational again, a X-Back (Crossback) is triggered. During the X-Over/X-Back there is a small outage time. After a X-Over until the X-Back is completed a performance degradation can occur (depending on dimensioning and current load situation). Official Branding for the call engine-MGC product Analogue or ISDN BA/PRA subscriber connected via AGW Access Gateway Control Element. This is the call engine processor, which hosts the call engine application software to control subscribers connected via AGW

ALCATEL 5020 MGC AGW Subscriber AGWCS

AGWDH / TGWDH Access / Trunk Gateway Device Handler. These are the call engine functions in the AGWCS/TGWCS which provide the interface between signalling/call control and the UNIX part ("virtual device handler") Application Server Server used for IP Centrex CENTREX IP Centrex IP involves the deployment of traditional Centrex services to IP endpoints and PSTN endpoints, providing most of the business telephony functionalities as known from existing Business Communication Group (BCG).

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description About This Document Page 11

Term

Glossary Definition

Centralised Access An Access Gateway which provides E1 connectivity for ISDN Gatewy (cAGW) PRA, RSU and/or V5.2 access networks. Physically this is a normal TGW however, it is carrying subscriber traffic rather than trunk traffic. cPCI / cTCA (Part) Hardware-Part of the system which is based on cPCI/cTCA equipment practice Chassis /Shelf There are several chassis- and shelf Crelated terms used in this document which could easily be misunderstood; see definitions below for clarification --CHASSIS refers to the hardware chassis that is delivered by CCPU --SHELF refers to maintenance view only and refers to a part of the chassis --Chassis-ID is an administrative item used inside the system to identify uniquely a chassis inside an iron-rack (sequential numbering) Vendor's chassis-ID is composed of rack-ID and chassis-ID stored in an EEPROM on chassis backplane; used inside the system to identify uniquely a chassis inside a complete system Shelf-ID refers to items in system maintenance view only Chassis n used inside this document as a pure sequential chassis numbering to identify uniquely a chassis inside the overall system; this avoids to use the cryptic "Vendor's chassis-ID"

Customer Premise CPEs are IADs or RGWs which are located at other parties equipment (CPE) than customer managed network and which can have static or dynamic IP-addresses assigned. GWDH GW-Trunk Internet Access Device IP Centrex AGWDH or TGWDH Gateway Trunk. Inter-exchange trunks with bearer over TGW Internet Access Device (IAD) is in the NGN context the same as Residential Gateway. IP Centrex is an end-to-end IP-based service utilizing a next-generation call control and call routing equipment at the carriers central office including a Softswitch or an application server

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description About This Document Page 12

Term ITCE Domain Media Server Residential Gateway

Glossary Definition Other term for LINUX Part Sever providing the Media Resource Function needed for tones, announcements, conferences, etc. VoIP Gateways, typically located at user premises, to connect analogue phones to the NGN; abbreviation: RGW, synonymously also IAD. The RGW perform the analogue voice to digital RTP-VoIP streams. The signalling for the analogue terminals connected to a RGW/IAD is performed in-band between the analogue TE and the RGW. Between the RGW and the MGC, H.248, MGCP or SIP is used, depending on the RGW type. Appropriate SIP or H.248 / MGCP information is exchanged between the MGC and the RGW/IAD for the analogue signalling events, and the required control information. Other than analogue TEs are not supported at RGWs/IADs. RGWs / IADs are non trusted devices, as a consequence, they are connected to the managed IP via ABGs. Part of the system where Software is based on call engine OS (incl. the OS itself) IP to IP Gateway at the border of the managed IP network, acting as a traversal and relay function for the CPEs. This can be a SIP terminal (directly connected to an IP network) or e.g. an IAD controlled via SIP. From Softswitch point of view the SIP UNI interface is provided with some restrictions: no multimedia, services are mapped to those of an ISDN subscriber. SIP with encapsulated ISUP, with mapping between BICC/ISUP and SIP header fields and SDP, according to ITU-T Recommendation Q.1912.5 Trunk Gateway Control Element. This is the call engine processor which host the call engine application software to control E1 trunks connected via TGW and ISDN PRA connected via AGW. Part of the system where Software is based on LINUX/Solaris OS (incl. the OS itself)

call engine Domain Other term for call engine Part call engine Part Session Border Controller SIP User

SIP-I

TGWCS

UNIX Part

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description About This Document Page 13

Term

Glossary Definition

Virtual Trunk Group Trunk Group with SIP-I signalling (i.e. bearer transport over IP without PCM channel structure). Like for PSTN Trunk Groups a VTKG also specifies the ISUP capabilities and bearer characteristics for PSTN services Access Border Gateway ALCATEL 5020 MGC AGW Subscriber AGWCS IP to IP Gateway at the border of the managed IP network, acting e.g. as firewall and NAT function. Official Branding for the call engine-MGC product Analogue or ISDN BA/PRA subscriber connected via AGW Access Gateway Control Element. This is the call engine processor, which hosts the call engine application software to control subscribers connected via AGW

AGWDH / TGWDH Access / Trunk Gateway Device Handler. These are the call engine functions in the AGWCS/TGWCS which provide the interface between signalling/call control and the UNIX part ("virtual device handler") Application Server Server used for IP Centrex cPCI / cTCA (Part) hardware-Part of the system which is based on cPCI/cTCA equipment practice GWDH GW-Trunk Internet Access Device IP Centrex AGWDH or TGWDH Gateway Trunk. Inter-exchange trunks with bearer over TGW Internet Access Device (IAD) is in the NGN context the same as Residential Gateway. IP Centrex is an end-to-end IP-based service utilizing a next-generation call control and call routing equipment at the carriers central office including a Softswitch or an application server Other term for Unix Part Sever providing the Media Resource Function needed for tones, announcements, conferences, etc.

ITCE Domain Media Server

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description About This Document Page 14

Term Residential Gateway

Glossary Definition VoIP Gateways, typically located at user premises, to connect analogue phones to the NGN; abbreviation: RGW, synonymously also IAD. The RGW perform the analogue voice to digital RTP-VoIP streams. The signalling for the analogue terminals connected to a RGW/IAD is performed in-band between the analogue TE and the RGW. Between the RGW and the MGC, H.248, MGCP or SIP is used, depending on the RGW type. Appropriate SIP or H.248 / MGCP information is exchanged between the MGC and the RGW/IAD for the analogue signalling events, and the required control information. Other than analogue TEs are not supported at RGWs/IADs. RGWs / IADs are non trusted devices, as a consequence, they are connected to the managed IP via ABGs. Part of the system where Software is based on call engine OS (incl. the OS itself) A user connected to the IP network via a native SIP User Agent (SIP terminal) and not via Gateway (e.g. like AGW subscribers) SIP with encapsulated ISUP, with mapping between BICC/ISUP and SIP header fields and SDP, according to ITU-T Recommendation Q.1912.5 Trunk Gateway Control Element. This is the call engine processor which host the call engine application software to control E1 trunks connected via TGW and ISDN PRA connected via AGW. Part of the system where Software is based on LINUX/Solaris OS (incl. the OS itself)

call engine Domain Other term for call engine Part call engine Part SIP User

SIP-I

TGWCS

UNIX Part

Virtual Trunk Group Trunk Group with SIP-I signalling (i.e. bearer transport over IP without PCM channel structure). Like for PSTN Trunk Groups a VTKG also specifies the ISUP capabilities and bearer characteristics for PSTN services

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description About This Document Page 15

Conventions and Terminology

Abbreviations
This part is provided to present basic or frequently abbreviations and their meanings.

Abbreviation ACE ACL ACM AGW AGWDH ANM APCE APM ASE ARP / RARP AS ASIC ASIG ASP ASSS ATM BA BDH-VFs BICC BootP BUD cAGW

Definition Auxiliary Control Element Access Control List Address Complete Message Access Gateway AGW Device Handler Answer Message Administration and Peripherals Control Element Application Transport Mechanism Application Service Element Address Resolution Protocol / Reverse ARP Application Server (for IP Centrex) Application Specific Integrated Circuit ACE Signalling Application Server Process Analogue Subscriber Signalling Subsystem Asynchronous Transfer Mode Basic Access Bulk Data Handling Virtual File Store Bearer Independent Call Control Boot Protocol BackUp Disk Centralized Access Gateway

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description About This Document Page 16

Abbreviation CAS CC CCGF CCSI CDE CdPN CDR CE CFCS CIC CIC CIDCW CLCE CLIP CLS CMC CNIP COCO CON CPE cPCI cTCA CPG CRC CSC CSF CSMA/CD CSTG CTSF

Definition Channel Associated Signalling Call Control Content of Communication Generation Function Common CE/SW Interface Customer Dependent Engineering Called Party Number Call Data Record Control Element: processor in the control plane Call and Facility Control System Call Instance Code (BICC) Circuit Identification Code (ISUP) Call Identification with Call Waiting Clock (& Tone) CE Calling Line Identification Presentation Call Server Common Management Centre Calling Name Identification Presentation Connection Control Connect Message Customer Premise Equipment Compact Peripheral Component Interface compact Telecom Computing Architecture Call Progress Message Call Recording Collector Call Session Controller Common Signalling Function Carrier Sensing Multiple Access with Collision Detection Compact System Timing Generator Common TCE Signalling Function

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description About This Document Page 17

Abbreviation CTX DFCE DH DHCP DIAM DLS DNS DSN DSS1 DTM EABS EALS EARS EAUS EDOTCP EGW ELM EMC EPH EPM EPR ESMA ESP ESWT EthH ETSI Ext eXXX

Definition Centrex Defence Control Element Device Handler Dynamic Host Configuration Protocol Dynamic Integrated Announcement Module Data Load Segment Domain Name Server Digital Switching Network Digital Subscriber Signalling System No.1 Digital Trunk Module Extended Assistant Billing System Extended Assistant Lawful interception System Extended Assistant Routing System Extended Assistant Userprofile System Exchange Dialogue Over TCP Ethernet Gateway (or Proxy) Ethernet Link Maintenance Electro Magnetic Compatibility External Protocol Handler Ethernet Peripheral Module Event Pending Register Ethernet Switch Module A (call engine PBA) Extended Server Platform Ethernet Switch Ethernet Handler European Telecommunications Standards Institute External indicates the object XXX used in conjunction with the Extend scenario

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description About This Document Page 18

Abbreviation FL FMM FSK FTP GDT GLS GSTM-RSU GUI GW GWCH HCCM HDS HD IAD IAM ICMP ICOCO ID IDMS IDT IETF IN IP SIG IP IPMB IPMI IRSU ISDN

Definition Fast Link Finite Message Machine Frequency Shift Keying File Transfer Protocol Gelobal Descriptor Table Generic Load Segment Generic Signalling Termination Module C Remote Subscriber Unit Graphical User Interface Gateway Gateway Communication Handler High Performance Common Channel Signalling Module Hardware Dependent Software Hardware Internet Access Device Initial Address Message Internet Control Message Protocol Interworking Connection Control Identity Integrated Data Manufacturing System Interrupt Descriptor Table Internet Engineering Task Force Intelligent Network IP Signalling Internet Protocol Intelligent Platform Management Bus Intelligent Platform Management Interface ISDN RSU (RSU for analogue and ISDN subscribers) Integrated Services Digital Network

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description About This Document Page 19

Abbreviation ISIG ISIM ISUP ISVCE ITCE ITF IUA KFR KUR LAN LCE_Id LEX LLC LLCE LTCE LSHR LSIF MAC MCCM MCL MCUD MCUH MG MGC MGCP MGW MH MM MPSR

Definition Interworking Signalling Interface Signalling Module ISDN User Part Improved Service Circuit Control Element Information Technology Control Element Interface ISDN Q.921 User Adaptation Layer Kernel Function Request Kernel User Request Local Area Network Logical CE Identity (address of a control element) Local Exchange Logical Link Control Logical Line Control Element Logical Trunk Control Element Load SHaRing Local Subscriber Identification Function Media Access Control Mega Common Channel Module Multi Channel Launch Module Control Unit D Module Control Unit H Media Gateway Media Gateway Controller Media Gateway Control Protocol Media GateWay Message Handler MultiMedia Multipath Self-Routing

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description About This Document Page 20

Abbreviation MRF MS MTP MW MV M2PA M2UA M3UA NA NAT NAPT NB NCCM NEBS NED NGN NH NIC NTP NUR OAC OAM OD ORJ OS OSN OWP PAN PATED

Definition Media Resource Function (=Media Server) Media Server Message Transfer Part Middle-ware MontaVista MTP Level 2 User Peer-to-Peer Adaptation Layer MTP Level 2 User Adaptation Layer MTP Level 3 User Adaptation Layer Network Address Network Address Translation Netword Address and Part Translation Narrow Band Next Generation Common Channel Module Network Equipment Building System Network Element Data Next Generation Network Network Handler Network Interface Controller Network Time Protocol Network Handler User Request Outgoing Access Code Operation, Administration and Maintenance Optical Disc Operator Requested Job Operating System Operating System Nucleus Operator Work Place Public Addressed Node Prefix Analysis and Task Element Definition

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description About This Document Page 21

Abbreviation PBA PCE PCI PCI PCM PDH PIM PLDA PLMN PMC POTS PR PRA PSTN PSU RAPTOR RAU REL RGSM RGW RIT RLC RM ROM RSU RT RTCP RTM

Definition Printed Board Assembly Physical Control Element Path Cell Index Peripheral Component Interconnect Pulse Code Modulation Pseudo Device Handler Peripheral Interface Module Peripheral and Control, Defence and Administration Control Element Public Land Mobile Network PCI Mezzanine Card Plain Old Telephone Subscriber Package Replacement Primary Rate Access Public Switched Telephone Network Power Supply Unit Remote Assistant for Package Transfer and On-Line Replacement Rack Assembly Unit Release Message Removable Generic Software Module Residential Gateway Replaceable ITem Release Complete Message Resource Manager Read Only Memory Remote Subscriber Unit Real-Time Real-Time Control Protocol Rear Transition Module
Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description About This Document Page 22

Abbreviation RTP R1hardware R2hardware SACE SADH SAM SAU SBC SBL SCALSVT SCCP SCN SCTP SDP SG SIGTRAN SIP SIP-A SIP-I SIP-M SIP-U SKR SLS SMC SMTP SNMP SPC SPS

Definition Real-Time Transport Protocol Release 1 Hardware Release 2 Hardware System Auxiliary Control Element System ACE Device Handler Subsequent Address Message Sub-rack Assembly Unit Session Border Controller (Gateway) Security Block SACE for Call Services for Trunks Signalling Connection Control Part Switched Circuit Network Stream Control Transmission Protocol Session Description Protocol Signalling Gateway Signalling Transport (IETF Working Group) Session Initiation Protocol SIP Interface to non-MGC SIP Servers / SIP Proxies (e.g. IP CTX AS, 5020 CSC, ) SIP Interface to other MGC (with encapsulated ISUP) SIP Interface to Media Server (MRF) SIP Interface to user equipment (e.g. SIP IAD) System Kernel Release Signalling Link Selection Software Management Centre Simple Mail Transfer Protocol Simple Network Management Protocol Signalling Point Code Service Provisioning System

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description About This Document Page 23

Abbreviation SSM STM SUA SVCE SW SWEL SYD TCAP TCE TCP TDH TDM TE TELCO TGW TGWDH TI TIS TMM TSIG TSM TSV TSS TTRCB TUA UCP UDI UDOTCP UDP

Definition System Support Machine Synchronous Transport Module SCCP User Adaptation Layer Service Circuit Control Element Software Switching Element System Disk Transaction Capabilities Application Part Terminal Control Element Transfer Control Protocol Trunk Device Handler Time Division Multiplex Terminal Equipment TELeCOmmunication Trunking Gateway TGW Device Handler Terminal Interface Terminal Interface Subsystem Traffic Metering and Measurement TCE Signalling Terminal Interface and Switch Maintenance TCE Supervisor Task Switch Segment Trunk Transaction Control Block TCAP User Adaptation Layer User Controlled Path Unrestricted Digital Information Unix Dialogue Over TCP User Datagram Protocol

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description About This Document Page 24

Abbreviation UER VDH VM VMS VMWI VOD VP VTKG WR XCM XMgr

Definition Unsolicited Event Report Virtual Device Handler Virtual Machine Voice Mail Server Visual Message Wait Indication Virtual Optical Disc Virtual Path Virtual TrunK Group World Release Xover Control Manager Extend Manager

Alcatel 5020 MGC

215 86877 EACE TR Ed. 01, April 2005

System Description Network View Page 25

Network View
Alcatel 5020 MGC Overview
As a key component of Alcatel's OPEN (Open Path to Enhanced Networking) portfolio, the Alcatel 5020 MGC addresses the evolution of existing TDM networks towards next generation networks (NGNs) by guaranteeing full-featured voice support. It delivers the scalability and interoperability required by voice service providers, guarantees full feature continuity, and provides a low-risk entry solution for NGN deployments that enriches the traditional TDM network. By using the evolutionary solution, with a minimum size of one rack on standard off-the-shelve Compact Telecom Computing Architecture (cTCA) hardware, operators can leverage their current network investments while following a secure flexible migration path toward NGNs. The Alcatel 5020 MGC can be applied as a standalone node to control NGN gateways and offer all Class 4 and Class 5 services immediately on any terminal and protocol, via pure IP communication, and consequently no need of a Digital Switching Network(DSN); this configuration is the focus of the present architecture description. The Alcatel 5020 MGC helps to safeguard Alcatel's installed base marker solutions and its embedded feature richness, including local market adaptations. Supported by collocated or rack-integrated servers, the Alcatel 5020 MGC provides connectivity to Multi Media users, e.g. using SIP phones, and IP CENTREX services. Via a Media Server, tones & announcements and features requiring bearer signal processing, like conferences, are provided. Figure 1 below gives an overview of the relevant network nodes, to which the ALCATEL 5020 MGC has relations. Within the Managed IP NGN of the Figure 1, only signalling or control links are depicted, the bearer transport is embedded in the IP network. The only used TDM connections are E1 spans containing SS7 links from and to the PSTN and IN-SCPs. The CMC for Operation and Management is described in a separate document. The IN AP (SCP) is a standard network function.

Alcatel 5020 MGC

215 86877 EACE TR Ed. 01, April 2005

System Description Network View Page 26

Figure 1. Network view of the Alcatel 5020 MGC

Alcatel 5020 MGC Interfaces

The Alcatel 5020 MGC allows a smooth evolution to NGN, by supporting several gateway nodes, transport mechanisms and control interfaces. Full feature continuity is realized for PSTN users, i.e. users, which are connected to the NGN with analogue or ISDN terminals, and ISDN PABXs, and users, which use the NGN for calls from their legacy PSTN environment.

Media Gateways
The following gateway types and external interfaces are provided in Alcatel 5020 MGC

Alcatel 5020 MGC

215 86877 EACE TR Ed. 01, April 2005

System Description Network View Page 27

Access Gateways (AGW, cAGW)

Analogue Access ISDN BA ISDN PRA

Trunk Gateways (TGW)

TDM E1 interfaces towards PSTN

Residential Gateways / IP Access Devices (RGW/IAD, names used synonymously)

RGW/IAD using H.248 or MGCP signalling towards the MGC RGW/IAD using SIP signalling towards the MGC SIP-phones SIP-phones for MM: SIP access is provided to users SIP-phones,
controlled by the A5020 CSC softswitch for Multi-Media services.

SIP-Phones for VoIP calls: SIP access is provided to users SIP-phones,

controlled by the A5020 MGC softswitch, for supporting a set of widely used supplementary services comparable to those used for ISDN

Transport Mechanism for bearer and signalling information

Bearer transport for voice and other media is fully based on IP, no direct circuit switched connections are used in Alcatel 5020 MGC. Access signalling transport (UNI) is fully based on IP.

Network Signalling (NNI)

For signaling links to the PSTN, including IN SCPs, classical SS7 signalling on E1 systems or SS7 via SIGTRAN is used. For backhauled SS7 links M3UA (SIGTRAN) is provided. For signaling links within the NGN, i.e. to other MGCs, SIP-I is used.

Alcatel 5020 MGC

215 86877 EACE TR Ed. 01, April 2005

System Description Network View Page 28

Bearer Transport by IP

Figure 2. Bearer Transport by IP The scenario above (Figure 2) shows the Bearer transported between the gateways via RTP/UDP/IP.

The following examples are illustrated

1. The bearer of subscriber on the same gateway is switched inside gateway, if there are no special Bearer features needed (e.g. basic call). This inside switching is not pplicable to RGWs/IADs, see(4). 2. If two subscribers are not connected on the same gateway, but controlled by the Alcatel 5020 MGC, then the bearer is switched over to the IP network. 3. If the terminating subscriber is located in PSTN/ISDN, an outgoing ISUP call is made; the bearer is switch over to the IP network to a TGW, and further from the TGW to the PSTN. 4. Deployed in a private IP-network, calls between users connected to the same RGW/IAD are routed via the related SBC allowing the network to control the bearers of such calls. This is a function of the SBC and deployed in a public IP- net or in the managed IP-net itself, the bearer is routed directly.

Alcatel 5020 MGC

215 86877 EACE TR Ed. 01, April 2005

System Description Network View Page 29

Note: The access types at the gateways are examples: A certain Gateway may support all of the shown accesses (analogue terminal, ISDN BA or PRA), or only some of them. Note: The Media Server is used, if special tones or announcements are needed or services like conferences are requested. In such cases, the bearer path is connected via IP to the MRF.

UNI Signalling
Access Signalling Transport by IP
AGW, cAGW

Analogue Access
The signalling for analogue TEs connected to AGW is performed in-band between the analogue TE and the AGW. The protocol H.248 and MGCP is used between the AGW and the Alcatel 5020 MGC. Signalling information is sent tieh H.248/MGCP commands, beside the normail bearner control information. H.248 (ITU-T) / MEGACO (IETF) (i.e. media gateway control protocol) is a protocol between the elements of a physically decomposed media gateway (MGW) and its controller (MGC). It is needed in the MGC (controller) and the associated AGWs or TGWs in order to: Control the call state pertaining to the connection control for media channels in the AGW/TGW. Transport analogue signalling information between AGW/TGW and MGC.

MGCP is a predecessor of H.248/Megaco. It is optionally used for control of RGWs/IADs.

ISDN Basic Access / Primary Rate Access

The SIGTRAN ISDN User Adaptation layer (IUA) is used in order to support the ISDN Basic and Primary Rate access, connected via AGGWS. The SIGTRAN protocol IUA/ transports the DSS1 information over IP between the MGC and AGW. Note: Primary Rate Accesses are generally connected to Centralised Access Gateways (cAGW); cAGW support E1 TDM links.
Alcatel 5020 MGC

215 86877 EACE TR Ed. 01, April 2005

System Description Network View Page 30

The lower layer SCTP functions, providing a reliable message transport between GWs and the MGC, is implemented.

H.248 or MGCP RGW / IAD

The signalling for analogue TEs connected to a RGW/IAD is performed in-band between the analogue TE and the RGW/IAD. Between the RGW and Alcatel 5020 MGC, H.248 or MGCP. Signalling information is sent with H.248 / MGCP commands, beside the normail bearer control information.

SIP RGW/IAD
RGWs/IADs, witch are controlled by an MGC via SIP, are supported directly Alcatel 5020 MGC.

SIP Terminals
See chapter SIP-phones for interfaces to the SIP-phones. Multi-Media SIP-phones are served by the Alcatel 5020 CSC and interworked to Alcatel 5020 MGC for routing to and from PSTN.NNI Signalling

SIGTRAN for Support of Common Channel Signalling Types

The SIGTRAN protocol family defines User Adaptation layers for SS7 based Common Channel Signalling types. For backhauling SS7 links the SIGTRAN protocol M3UA is as well implemented. ISUP is used unchanged.

Inter MGC Signalling SIP-I

For signalling between MGCs, which are connected by IP, SIP-I is used.

Alcatel 5020 MGC

215 86877 EACE TR Ed. 01, April 2005

System Description Network View Page 31

Figure 3. Inter MGC Signalling use of SIP-I The SIP-I protocol is transported over UDP/IP. The right hand side AGW and TGW are controlled by Softswitch 1, the RGWs/IADS on the left hand side are controlled by Softswitch 2. In case 1, a call takes place between access devices of the 2 softswitches. For the required signalling between the softswitches, SIP-I is used. From a signalling layer point of view, the functions are the same as with ISUP: SIP-I basically transports the ISUP messages. The Bearer is switched directly in the IP network between the related gateways, in case of the RGW user, via the SBC. In case 2, a call takes place between a PSTN user of Softswitch 1, connected via its Local Exchange and a TGW to the NGN, and an NGN user, at a RGW/IAD controlled by softswitch 2. For the signalling between the softswitches, again SIP-I is used The Bearer is, as above, switched directly in the IP network between the related gateways, in case of the RGW user, as above via the SBC.

Alcatel 5020 MGC

215 86877 EACE TR Ed. 01, April 2005

System Description Network View Page 32

Other SIP interfaces

SIP signalling is used for support of several signalling relations (see also Figure 1): As SIP-I is shown in the chapter before for inter MGC signalling, other SIP-types are used on the NNI interface as they are:

SIP-M: Defined to control the Media Resource Function for connecting

announcements and establishing conference bridges.

SIP-A:Signalling to Applications Servers (relevant for IP CENTREX server)

Note: The SIP-I terminology is overtaken from the Q.1912.5 specification, while the terms SIP-A, SIP-U(UNI) and SIP-M are introduced by ALCATEL in order to differentiate the signalling relations described above. They are based upon the SIP standard with different specific SIP-extensions and scenarios.

Session Barder Controller

SBC (Session Board Controller) is located at service providers managed IP-network. Customer intranet user GWs will only address SBCs IP address instead of MGCs IP address directly. Any H248/MGCP or SIP traffic from and to the GWs in the private IP-network must be relayed over SBC. In this sense SBC is like a bridge between the Internet and the managed IP-network.

Alcatel 5020 MGC

215 86877 EACE TR Ed. 01, April 2005

System Description Network View Page 33

Figure 4. SBC function in network In the Private Intranet the CPE (Customer Premise Equipment) get its dynamic IP address from customer owned DHCP server and can be registered on customer owned DNS server, but this is not visible for the MGC. All IP-addresses assigned in the private network (whether static or dynamic) are hidden behind the SBC. The single GWs (H248, MGCP) in the private IP-network are only identified via the

Alcatel 5020 MGC

215 86877 EACE TR Ed. 01, April 2005

System Description Network View Page 34

domain name in the H248/MGCP message and the source IP-address of the SBC. For SIP-IADs the SBC acts as a back-to-back user agent, maintain complete call state and participates in all call request. The speech paths to and from the RGW/IAD, independent they are SIP/H.248/MGCP controlled, will be relayed over the SBC as well. In the SBC all message between private CPE and MGC will be changed by an NAT/NAPT function and filtered by a firewall function for security reasons.

Support of DHCP/DNS service

Public CPEs (IADs/ RGWs) can have a static IP-address (as described above) or can get its dynamic address from a public DHCP server as shown in the figure below. If the public CPE uses a dynamic IP-address the domain name in the H248/MGCP header is mandatory for the CPE. Otherwise it could not be identified by the MGC. All messages and registration from the public CPEs will be relayed and filtered over the Firewall on the border of the managed IP-network. Only these IP-addresses and port are open which belong to the range of dynamic assigned IP-addresses and the H248/MGCP default ports.

Alcatel 5020 MGC

215 86877 EACE TR Ed. 01, April 2005

System Description Network View Page 35

Figure 5. DHCP/DNS service in network

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description System Architecture Page 36

System Architecture
Introduction and Overview
Introduction of Site-Configuration and Components
A basic component of the site configuration in the context of this product is the ALCATEL 5020 MGC which is placed in the MGC-rack as defined later in this document (depth = 600mm). The site configuration in the context covers more than the MGC and will be shown below for clarification. We have as well a Convedia CMS 1000 media server, a 5020 CSC multi-media softswitch and a Sylantro IP Centrex server. All of them will be assembled in one so-called multi-media rack which is placed next to the MGC rack(s). An OSP that might be needed/used in future in addition is to be placed in a third type of rack (called AS-rack) which is currently not (yet) foreseen and is not described in more detail. Following qualities are associated with the MM-rack:

common look and feel with telco rack size 600 x 900 x 2200 mm (increased depth) Earthquake compliance (not tested) inner height 47U, 1U at top and bottom reserved for rack enforcement (not
really usable due to shape of rack - rounded corners) Further assumptions related to configuration planned in MM-rack:

Assumed power dissipation for all used components about 5.5 kW Environmental temp. max. 30 C air blocking plate btw. front and rear has to be introduced to prevent any
airflow from back to front

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description System Architecture Page 37

only 5020 CSC small and medium configuration (means DS15 or DS25 only) extensions of Centrex- or Media-Server possible only in a second rack
See in figure below the composition of functional blocks into rack-types:

Figure 1. Site-Configuration Overview The figure below gives some more details w.r.t. components inside the MM-rack related to functional building blocks (note that the exact rack layout of the Alcatel

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description System Architecture Page 38

5020 CSC part is under responsibility of HP and is not necessarily exactly 100% as described in this document here; it is mentioned here to show principles):

Figure 2. MM-rack layout and configuration overview The various components that are available in the MM-rack are explained in more detail in the table below: ITEM DS15 DS25 SW4354R Description 1 CPU Alpha server 2 CPU Alpha server Manufacturer HP HP

2x7 disk enclosure, dual SCSI bus, HP dual power supply HP

HP ProCurve xxxx 24 port Gbit Ethernet switch

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description System Architecture Page 39

ITEM Digi PortServer TS16 Rack Convedia CMS 1000 SF V240 Pulsar STS16 PDU

Description 16 port terminal server 300 port IP media server 2 CPU Sparc server

Manufacturer Digi International Convedia SUN

240V power source transfer switch MGE UPS Systems

A more detailed view on Connectivity of serial-, SCSI-, Ethernet- and power-interfaces in the MM-rack is given in the following figures below. Please note as well that the switches are now mandatory because we use them as well to connect MGC-rack to external network:

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description System Architecture Page 40

Figure 3. MM-rack serial- and SCSI-connectivity

Figure 4. MM-rack power-connectivity

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description System Architecture Page 41

Figure 5. MM-rack ethernet-connectivity

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description System Architecture Page 42

From CSC OAM CSC OAM CSC Sip. CSC Sip. CSC Sip. CTRX CTRX

To

Path

Description

OAM Network VLAN2<->edge routers CSC management MGC (EABS) Ctrl. Network VLAN2 internal CDR calletion CSC->EABS

VLAN3<->edge routers SIP signaling MGC/CSC interworking CSC/IP Centrex interworking

MGC (IPACC) VLAN3 CTRX Ctrl. Network VLAN3

VLAN3<->edge routers IP Centrex signaling

OAM Network VLAN3<->VLAN2<->ed IP Centrex management ge routers MGC (IPACC) VLAN3 MGC (EABS) MS VLAN3<->VLAN2 VLAN3 CSC/IP Centrex interworking internal CDR calletion CSC->EABS IP Centrex media server control media streaming

CTRX CTRX CTRX MS MS MS

Bearer Network direct Ctrl. Network

VLAN3<->edge routers SIP signaling

OAM Network VLAN3<->VLAN2<->ed Media server management ge routers MGC (IPACC) VLAN3 MGC media server control

MS

MGC(IPACC) Network

VLAN3<->edge routers MGC signaling (Megaco, MGCP, SIGTRAN, SIP, SIP-I)

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description System Architecture Page 43

From

To

Path

Description

MGC(OAMCE)OAM Network VLAN2<->edge routers MGC OAM OWP OAM Network VLAN2<->edge routers MGC OAM

Figure 6. Potential VLAN setup in MM-rack configurations more detail see External interface to TDM network

Introduction of ALCATEL 5020 MGC

The ALCATEL 5020 MGC configuration for in the MGC-rack is the one defined in this document. There is only cTCA hardware where we will find as well the call engine-CEs. The mapping is no longer done 1:1 only but n:1 due to introduction of the call engine virtualisation concept.

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description System Architecture Page 44

The functional merge done for old version is kept. In addition CEs like PABX, LSIF are gone. The former call handling function of these CEs is replaced by an new interface module located in all *CS and PLDA, and the EAUS. For more details see CE-descriptions later on. Resulting impact on call engine-OSN limits and solutions have been identified as well in call engine-OSN description later on. MRF related parts will be available as an external function. Some other functions like local line or trunk terminations are not supported in this configuration (trunk termination for signalling links is available - see description of N7 solution later on). OAM-agent's OS is now LINUX MV CGE 3.1 which means that we do the migration from SOLARIS7 to LINUX. Two new server-types are introduced and fully integrated from platform point of view (handled like ITCEs): the EARS and the EAUS. All ITCEs and servers (except EABS) are now migrated to LINUX distribution MV CGE 3.1. All ITCEs and call engine-CEs are connected to the ESWTs, which are the only internal communication medium for inter- and intra-domain communication. All internal Ethernet Switches are incorporated into a maintenance concept for fault detection and isolation provided by Ethernet Link Maintenance (ELM). Each CE must participate in this concept independent to which domain it belongs (except EABS). Magnetic discs are now provided on new RTMs which means that no longer node-slots are wasted for these peripherals. Concept-Overview Handling multiple CE instances is managed by JALUNAs SW: We use a VM-monitor (nano-kernel) from JALUNA called OSware appended by a specific adaptation layer called NK2OSN. OSware is Jalunas technology to enable several OSs to run in parallel on one processor (in our case: multiple call engine-instances [optionally plus one secondary LINUX] ). OSware is supported by a so called primary OS which is a LINUX enhanced by specific RT patches: This primary OS has specific tasks and several secondary

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description System Architecture Page 45

OSs which are the guest OSs e.g. call engine-OSN (but also one secondary LINUX instance is possible) will run on top of the infrastructure described above. No TELCO applications will be placed on top of the primary LINUX. It is available to support Jalunas Virtualisation approach only. NK2OSN is a software layer, which adapts call engine software to the nanokernel environment i.o.w. NK2OSN simulates to call engine HdS (which its ITF-counterpart) that it is running directly on a well-known hardware. Only a limited number of changes/adaptations had to be made in call engine HdS. But using this adaptation layer enables call engine software to run on top of OSwares interfaces that are more or less generic and do not look like the hardware interfaces known by call engine-HdS. Jaluna does not emulate critical ASM instructions online by catching their execution via exceptions and executing some emulation-code instead. So e.g. all CLI / STI / PUSHF / POPF instructions can remain and our SW INT will be used as before (secondary call engine OS still executing on privilege level 0). Jaluna provides instead a concept where all secondary guest OSs (in our case mainly the adaptation-layer HdS) that execute on the processor-hardware have to be prepared/adapted in a way that they respect 1. OSwares need to be informed/involved whenever specific resources (e.g. hardware or central tables like GDT etc.) are changed because OSware administrates the OSs contexts and sets up the processors configuration and central tables accordingly when scheduling any of the secondaries. Therefore specific updates have to be done via OSware and some actions cannot be kept as they are (this affects specific peripherals and instructions that will be used by an OS if running alone on the hardware e.g. LGDT, LIDT, LLDT, INVD, WRMSR SYSENTER, SYSEXIT, IN, OUT, INS, INSB, INSW, etc., dynamic TSS entries in GDT, touching specific entries in IDT, control register modifications, etc. 2. All necessary adaptations and extensions for the call engine side will be concentrated in the HdS-layer. All upper-layer call engine software (OSN, other kernel, applications) have always to go via HdS when a relevant action is to be executed (for a complete list of relevant actions see document mentioned above). The major porting-effort on call engine side was therefore in call engine HdS which has been adapted to replace all hardware and some privileged machine-instructions by equivalents (invocations of NK2OSN component which is provided to shield specific call engine OS related handling from the generic OSware implementation) that are compatible with

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description System Architecture Page 46

the Jaluna-approach. The NK2OSN interface is a set of system calls, which are accessed from HdS via macros. NK2OSN is part of the OSN VM and its address space. 3. call engine software called HdS (Hardware dependent software) mainly covers the hardware related functions and provides defined interfaces to use the hardware. The upper layers of call engine OSN/kernel and applications need adaptations to access hardware only via HdS interfaces and not anymore directly (bypassing e.g. CCSI, manipulating directly ethernet controller, interrupt controller, timestamp counter, etc.). In addition they have to be adapted for all actions according to document mentioned above. The alternative of dynamic patching in call engine software is not to be applied. 4. All secondary guest OSs have as well to consider the assignment of specific physical hardware-devices to one specific VM-instance which could be the primary or any of the secondaries (in our case the primary LINUX for the ethernet controller and a specific secondary for the serial ITF). All other instances on the blade that want to make use of that hardware-device may access it via a virtual device driver that has to be provided in that case (e.g. ethernet ITF: controller owned by primary LINUX, access of secondaries via virtual ethernet switch implemented by a specific driver in NK2OSN). The building blocks (overview and individual view) that are used for the Virtualisation approach and their layering is shown in the figures below:

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description System Architecture Page 47

Figure 7. call engine CE Virtualisation using JALUNA approach overview of building blocks

Figure 8. call engine CE Virtualisation using JALUNA approach building block OSware

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description System Architecture Page 48

Figure 9. call engine CE Virtualisation using JALUNA approach building block NK2OSN

Figure 10. call engine CE Virtualisation using JALUNA approach building block ported call engineHdS Mapping of used building blocks to the well-known call engine legacy approach is shown in the figure below:

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description System Architecture Page 49

Figure 11. call engine CE Virtualisation using JALUNA approach mapping to legacy approach Features The Virtualisation approach in Alcatel 5020 MGC has the following qualities / features / restrictions:

Jalunas maximum of VMs that can run on one processor is 32. Currently we
are planning to have 4 VMs in Alcatel 5020 MGC but we are aiming to increase this number up to 16 VMs in call engine context.

The number of VMs on a blade is as well limited by the available

memory-size; we need approx. <64Mbyte for the JALUNA infrastructure (for 4VMs) plus the physical memory size that is allocated to each of the secondaries (for an call engine secondary we need max. 200Mbyte incl. space for uncompressed GLS/DLS pre-loading; I/O area size to be adapted accordingly). Note: that call engine HdS itself will still be mapped to linear 256Mbyte but there are holes inside; HdS will no longer have hard-coded memory-size assumption but will get the real physical memory size for the VM and restricts its actions on physical memory to given size.

The required memory-size (in Mbyte) for each VM to be actually

loaded/started is passed to OSware/primary LINUX in a command-line parameter osn-mem-size= <value> and will be taken from the MGC config-file for that blade (requested by boot-loader after location identification).

The number/IDs of VMs to be actually loaded/started is passed to

OSware/primary LINUX in a command-line parameter nk-running=<bit-field> (implicitly assuming that all the other ones will be set to stop-state) and will be taken from the MGC config-file for that blade (requested by boot-loader after location identification). This allows to use one unique Jaluna-software variant for running 1,2,3 or 4 VMs. Example for usage of this parameter.
Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description System Architecture Page 50

nk-running=000011xx (binary) secondary 1 and 2 are started, 3 and 4 stopped nk-running=001111xx (binary) secondaries 1,2,3 and 4 are all started (bit-positions in the <bit-field> are related to OSwares internal OS-Ids where nanokernel has Id=0, primary has Id=1, 1st secondary has Id=2, etc.)

The ID of a VM (VM-ID) is part of the physical address of that call engine

instance and therefore fixed offline (not possible to allocate it online dynamically). This VM-id is the reference used for the external addressing of a VM and subject of MAC addressing. It defines a configuration and build item. Jaluna internally needs to have independent OS instance references (OS-id) which are required to address the corresponding OS message queues. There exists a mapping table in this approach between VM-IDs and OS-IDs to decouple both reference schemes.

The serial interface is assigned to one specific VM (and cannot be changed

afterwards without reloading the related VMs); the indication for serial interface usage is passed to OSware/primary LINUX in a command-line parameter for that VM (parameter: osn-serial=xxxx )

Processor LEDs will no more reflect any load condition; instead they will be
used to indicate the number of running VMs on that blade.

Watchdog handling will be somehow virtualised: using the APIC will provide
the possibility to use the watchdog interrupt as NMI, which will then be delivered to the related VM (instead of simply doing a reset). In case of a watchdog expiration of a VM there is no reset of the whole blade. The NMI virtualized exception will be passed to related NK2OSN/OSN instance to enable reuse of existing native code and keep native behaviour and recovery policies. The actual value of the virtualised watchdog timer can be read by the call engine VM.

Jaluna will provide a virtualized HRC to each call engine VM, which can be
accessed via (modified) HdS using an NK2OSN trap. Downscaling of the frequency is still done by HdS code as before.

Debugging: call engine VMs will still have the 3 levels of debugging that were
available without Virtualisation: RODEM, Debug MONITOR, standard MPTMON-slave; debug registers will be virtualised, breakpoint handling will be possible in parallel for all call engine VMs. RODEM will be ported as part of HdS and RODETH will be emulated. call engine OSN/kernel/applications actions will never bypass HdS/CCSI/NK2OSN layers.

Alcatel 5020 MGC

215 86877 EACK TR Ed. 02, June 2005

System Description System Architecture Page 51

In case of individual call engine VM-reloads the Save/Restore mechanisms

will still work. In case of a boot/reset of the blade (of the primary LINUX) this will not be possible.

The quantum for scheduling-purposes per VM will be passed to Jalunas

OSware/primary LINUX in a command-line parameter and will be taken from the MGC config-file for that blade (requested by boot-loader after location identification).

Loading will be done ad described in chapter Loading A virtual ethernet switch is implemented for communication purposes as
described in chapter Virtual Ethernet Switches in JALUNAs call engine-virtualisation. There we find as well an explanation of related primary LINUX command line parameters buseth-net=(<net#>,<mask>) and buseth-mac=(<net#>,<addr>[/br][,<rxsize])

Configuration of VM instance will be done as description in chapterDisk-Boot

and Network-Boot for ITCE- and call engine-Domain

Summary of command-line options to be passed to primary LINUX (according

to configuration-file contents): buseth-net=(<net#>,<mask>) buseth-mac=(<net#>,<addr>[/br][,<rxsize]) fs-sched=(<period>:[<quantum>[/<prio>]],{[<quantum>[/<prio>]]}*) nk-running=<bit-field> osn-mem-size=<value> osn-serial=<any value>

Basic Scheduling The JALUNA approach provides for the secondary OSN instances some kind of real time behaviour, which was a major requirement. RT behaviour is guaranteed in the granularity of a predefined Real Time Cycle (called RTC). Within this time interval each call engine VM must be scheduled at least once. If an call engine VM is scheduled several times within a RTC then exactly once the 5ms interrupt has to be executed. This will be triggered by a 5ms-interrupt indication that will be set once at the beginning of an RTC for each

Alcatel 5020 MGC