Die Technik der Netze Seminar Teil 9: Baukasten (2)

Seminarprogramm Einführung – Wir bauen ein Netz Übersicht über TK-Netze Mobilfunk – Was steckt hinter meinem Händi Internet – Das Netz der Netze WiMAX – auch ein mobiles Netz Geht das auch etwas allgemeiner, oder müssen wir jede Implementierung kennen? – Netzarchitekuren Sicherheit im Netz – Verfügbarkeit, Integrität, Vertraulichkeit Kontron - Baukasten Teil 1 Beispiel: VoIP Call Server; Media Server: Netzdesign, Systemdesign; ATCA Baukasten; mTCA Baukasten; Kontron - Baukasten Teil 2 Anwendungen; Anwendungsprofile; Musterkonfigurationen; Validierungstools; System Validation Kits für ATCA und mTCA Die Zukunft der Netze

Netzdesign und Systemdesign für Call Server und Media Server Ein Blick zurück Netzdesign und Systemdesign für Call Server und Media Server

Gymnastik: Fast-Food Restaurant Eingang Ausgang Selbstbedienung & Kasse Restaurant mit Platz für 200 Gäste Mittlere Aufenthaltsdauer pro Gast: 15 Minuten Frage: Wie viele Gäste pro Stunde (bzw. pro Minute) muss die Kasse bedienen können?

Session Control and Media Processing Video/Audio On demand Life TV/ local TV Media Server announcements IVR conferences voice mail customised tunes streaming media trunking gateways PSTN Media Server Trunking GW/ Signalling Gateway Call Server/ Gateway Controller IP Network (Carrier) Call Server control call sessions (SIP/H.323 call control) control Media Server & Gateways PLMN Trunking GW

Controller Model 1 Mio Subscribers 1000 tps (80% load) 100 s per transaction Input buffer Output buffer 30 Mbps 13 Gbps Processor 30 Mbps 13 Gbps control messages, traffic control messages, traffic Cache Physical memory (volatile) 500 MB (160 GB) Data: Data base, File system, OS specific 500 MB 160 GB (1600 GB) Disks (persistent) Load, Store, Paging Call Processor (e.g. SIP Server): transaction profile (e.g. 30 kbit SIP messages per call transaction) Media Processor (e.g. Streaming Server/Proxy): traffic profile (e.g. 128 kbit/s of media streams of 100 seconds per transaction)

Musteranwendungen, Netzdesign

Marktsegmente für VoIP and Medien Wireline Enterprise IP Centrex VoIP Trunking Gateways IPTV NGN Media Servers Wireless Wireless Enterprise WiMAX 2G/3G Media Servers Fixed-Mobile Convergence Media Server Capabilities Conferences Announcements Voice Mail and Voice Recording Media Streaming IVR/Voice Portals/VXML ACD and Contact Server Unified Messaging Transcoding DTMF/FAX processing SIP Control, MGCP/Megaco/H.323 IVR: Interactive Voice Response (Ansagemenüs mit Ziffertasten) VXML: Voice XML (Sprachführung und Spracherkennung per Web-Seite)

Enterprise and Wireless Enterprise PSTN IP Network PBX Media Server IP phones voice mail unified messaging conferences call center transcoder bypass PSTN to connect to other PBXs TA

IP Centrex Media Server PSTN IP Network (Centrex Operator) SME SME trunking gateway SIP control announcements conferences voice mail unified messaging transcoder PSTN Call Server IP Network (Centrex Operator) IP Network Media GW PBX TA SME SME SOHO

Call Server & Media Server NGN and VoIP Trunking Media Server trunking gateway SIP control conferences voice mail announcements streaming media Media Server PSTN Trunking GW Siehe Teil 8: Call Server & Media Server IP Network (Carrier) Call Server PLMN Trunking Gateway SIP control H.323 control MGCP/Megaco transcoding Trunking GW

WiMAX PSTN/ PLMN Media Server Core Network (IP Network) WiMAX RAN Content Server Media Server Call Server Core Network (IP Network) Trunking GW AAA PSTN/ PLMN WiMAX RAN (IP Network) Access Controller BS Internet

2G/3G Media Servers Media Server PSTN/ PLMN Media Core Network Server SIP/Megaco ctrl. announcements IVR conferences transcoding Media Server Core Network (IP Network) Call Server/ MSC Server HLR 2G RAN Trunking GW BSC SGSN PSTN/ PLMN BTS 3G RAN GGSN Internet Node B RNC

Wireline Access Network IP-TV On demand Media Server Media Streaming interactive voice support conferences IVR/VXML Media Server Life TV/ local TV Media Controller AAA RAN (3G/WiMAX) BSC/AC DSLAM/NAS BS Wireline Access Network (DSL/CaTV) “triple play”

Fixed-Mobile Convergence Media Server Call Server/ Application Server/ MGCF Media Server SIP/Megaco ctrl. announcements IVR conferences transcoding Lawful interception IMS S-CSCF AAA/HSS IMS P-CSCF RAN (2G/3G) BSC/RNC/ SGSN BTS/Node B DSLAM/NAS Visited Network Wireline Access Network

Musterkonfigurationen mit ATCA und mTCA Systemdesign Anwendungsprofile, Systemarchitektur, Musterkonfigurationen mit ATCA und mTCA

How to design ATCA systems? Each network element can be profiled in terms of Subscribers Transactions Traffic Interfaces Sample configurations correspond to the application profile Same building blocks for the same functions Same patterns for the same profiles: Bundles Sub-systems Pre-integrated systems Chose system components from building blocks Application Profiles Building Blocks

Application Profiles - Summary Call Servers/Gateway Controllers/IMS-CSCF HLR/HSS Media Gateway/Trunking GW Media Server Signalling Gateway Radio Network Controller (RNC) Line Termination (DSLAM) WiMAX Access Controller (WAC) Base Station (BTS, Node B) IP-PBX Media Server Military (Radar, image processing, communications) Medical Industrial

Dimensionierung – Einige Faustregeln Subscribers: for orientation; Transactions: according to traditional design PSTN: 10% of subscribers are simultanously active (0,1 Erlang); one transaction (call) takes about 100 seconds -> 1 mtps per subscriber PLMN: according to traffic models, the most significant transaction are location updates of typically 4 updates per busy hour -> 1 mtps per subscriber (with 1h = 4000 seconds) Traffic: Signalling traffic (control plane): tps x subscribers x message lenght Data traffic (user plane): TDM interface x subscribers; for IP networks: service dependent or design guideline (e.g. 50 kbits/s per subscriber) DSP: 60 voice ports per DSP; 8 DSPs per AMC -> 500 voice ports per AMC Data Base: subscriber profiles and associated service profiles and state information to be handled in physical memory follows number of subscribers with 1 - 10 kBytes per subscriber

Sample Profiles Media Server 50.000 subscribers 50 tps (200.000 BHCA) 13 Gbits/s of traffic HLR/HSS 10 Mio subscribers 10.000 tps 100 Mbits/s throughput 30 GBytes of subscriber profiles & state info Media/Trunking GW Transcoding and media processing 12.000 subscribers 12 tps (48.000 BHCA) 800 Mbits/s of traffic Signaling Gateway 1 Mio subscribers 1000 tps (4 Mio BHCA), 30 Mbits/s control traffic (IP) 6 Mbits/s control traffic (SS7) Radio Network Controller 5000 channels 50 tps (200.000 BHCA) 3 Mbits/s control traffic 320 Mbits/s user traffic

Sample Profiles Each System is either Transaction Profile or Traffic Profile Max Traffic for Transaction Profiles: 100 Mbits/s Traffic for traffic profiles: 300 Mbits/s to 13 Gbits/s (Media Server) Data bases <10 GBytes, except for HLR/HSS (30 GBytes) and Media Servers (Media Proxy, Media Storage > 1000 GBytes)

HLR/HSS (w/o CS7 signaling) Storage Storage Subsystem N+1 Redundanz Redundant DB Server 1 2 3 4 5 6 7 8 Fabric (GbE) Processor 1 2 3 4 … N Fabric (GbE) Switch Processor Subsystem Network 10 Mio subscribers 10.000 tps 100 Mbits/s throughput 30 GBytes of subscriber profiles & state info (in DB Server RAM and on HDD)

Redundante Datenbanken Siehe Teil 7: Redundanz Data Base Data Base Nodes Fragments F1 F2 F3 F4 F1 F2 F3 F4 (F4) (F1) (F2) (F3) N1 N2 N3 N4 Verteilte Datenbank Fragmente definieren (F1, F2, …) Fragmente den Data Base Nodes mit Spiegelfragmenten zuordnen (werden im Arbeitsspeicher synchronisiert) DB Nodes (logische) auf Data Base Server (physikalisch) verteilen M+1 Redundanz for DB Servers Allocate Nodes to Servers N1 N2 Data Base Servers F1 F2 (F4) (F1) F3 F4 (F2) (F3) N3 N4 Server 1 Server 2

Transaction profiles – HSS Storage & Processor Subsystems Space for main controller (PrAMC & HDD) HLR/HSS (ohne SS7 Signalisierung)

HLR/HSS (w/o CS7 signaling) MCH CPU CPU CPU CPU CPU CPU CPU CPU MCH Storage Subsystem MCH CPU CPU <Spare> <Spare> CPU CPU CPU CPU <Spare> <Spare> CPU CPU MCH Processor Subsystem 10 Mio subscribers 10.000 tps 100 Mbits/s throughput 30 GBytes of subscriber profiles & state info (in DB Server RAM and on HDD)

HLR/HSS - mTCA Profile Implications on fabric and MCH 1 GbE as basic fabric is sufficient (max. 100 Mbps throughput) Dual star to 12 slots for each MCH (as in mTCA spec) 1GbE uplink on each MCH to interconnect each shelf 1 GbE uplink for Network interface on tier 1 MCH No need for PCIe or other fabric on MCH Special backplane design for storage subsystem Point-to-point connections on backplane for SAS/SATA disks in redundant storage sub-system (storage and processor) Does not need to pass MCH Basic MCH is sufficient

Media Server – N+1 Redundancy 50.000 subscribers (processing „ports“) 50 tps (200.000 BHCA) 13 Gbits/s of traffic storage capacity 1000 GB and more option: DSPs

Media Server sample configuration ATCA configuration: 5 slot system Network I/F: 4x 10GbE on hub switches CPU power: 3 ATCA CPU boards with 2x SAS disks Spare capacity: 4 AMC slots on hub switches Options: DSP for signal processing Options: STM-1 or E1/T1 Interface AMCs for Signalling or Trunking GW Uplinks (10GbE)

Media Server – N+1 Redundancy MCH CPU CPU CPU CPU MCH Storage Subsystem MCH CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU MCH Processor Subsystem 50.000 subscribers (processing „ports“) 50 tps (200.000 BHCA) 13 Gbits/s of traffic storage capacity 1000 GB and more option: DSPs

Media Server - mTCA Profile Implications on fabric and MCH 2x 10 GbE uplink capacity for network interconnection (1x 10 GbE on each MCH of tier 1) 2x 10 GbE uplink capacity to interconnect both tiers (1x 10 GbE on each MCH tier 1 and tier 2) 1 GbE as basic fabric is NOT sufficient (total 13 Gbps throughput to be distributed to 8-10 processors) Use 2x 1GbE on AMC ports 0 and 2 from both MCH Use extra GbE fabric in dual star to 12 slots, e.g. on AMC port 8 and port 9 ports 8-11 avoid conflicts with other fabrics on AMC ports 4-11 such as PCIe No need for PCIe or other fabric on MCH Special backplane design for storage subsystem Point-to-point connections for SAS/SATA disks in redundant storage sub-system (storage and processor) Does not need to pass MCH Basic MCH plus GbE fabric for AMC ports 8-11

Signaling Gateway 1 Mio subscribers 1000 tps (4 Mio BHCA), RAID IP Network (NGN) Switch Traffic Processor Fabric (GbE) 1 2 3 4 TDM Network (SS7) I/O E1/T1 Call & Main ctrl. Fabric (GbE) Uplinks Call Processor Subsystem Traffic Processor Subsystem 1 Mio subscribers 1000 tps (4 Mio BHCA), 30 Mbits/s control traffic (IP) 6 Mbits/s control traffic (SS7)

Transaction Profiles – Signalling Gateway Signalling Gateway: transactions 1 Mio subscribers (controlled by Call Server/Gateway Controller) 1000 tps (4 Mio BHCA), 30 Mbits/s throughput of control traffic 6 Mbits/s of TDM control traffic (trunks with CS7) Signalling Gateway

Signaling Gateway <Spare> <Spare> <Spare> MCH <Spare> <Spare> <Spare> <Spare> CPU CPU CPU CPU MCH Call Processor Subsystem MCH CPU E1 CPU CPU E1 CPU <Spare> <Spare> CPU CPU MCH Traffic Processor Subsystem

Signaling Gateway - mTCA Profile Implications on fabric and MCH 1 GbE uplink capacity for network uplink (NGN) on tier 1 MCHs 1 GbE uplink on each MCH to interconnect both tiers Uplink for TDM traffic (SS7) over E1 interface AMCs Dual star to 12 slots for each MCH sufficient (AMC ports 0 and 1 as in mTCA spec) No need for PCIe or other fabric on MCH (multi processor operation for traffic processors not feasible with PCIe) Special backplane design for storage subsystem Point-to-point connections for SAS/SATA disks in redundant storage sub-system (storage and processor) Does not need to pass MCH Basic MCH is sufficient

Radio Network Controller Call Processor & Main ctrl. Call Processor Subsystem 1 2 3 4 5 6 Fabric (GbE) Traffic Processor 1 2 3 4 5 6 Traffic Processor Subsystem Fabric (GbE) I/O STM-1 I/O STM-1 I/O STM-1 Switch Uplinks TDM Network (2G/3G BS) IP Network (SGSN) 5000 channels 50 tps (200.000 BHCA) 3 Mbits/s control traffic 320 Mbits/s user traffic Option: DSPs

Radio Network Controller Traffic Profiles - RNC Radio Network Controller (RNC) 50.000 subscribers (5000 channels) 3G base stations (Node B) 2G base stations (BTS) converted to 3G core net protocols 50 tps (200.000 BHCA) 3 Mbits/s throughput of control traffic 320 Mbits/s throughput of user traffic Radio Network Controller

Radio Network Controller Call Processor Subsystem MCH CPU CPU CPU CPU CPU CPU MCH MCH <Spare> <Spare> <Spare> CPU CPU CPU CPU CPU CPU STM-1 STM-1 STM-1 MCH Traffic Processor Subsystem 5000 channels 50 tps (200.000 BHCA) 3 Mbits/s control traffic 320 Mbits/s user traffic Option: DSPs

Radio Network Controller - mTCA Profile Implications on fabric and MCH 1 GbE uplink capacity for network uplink (SGSN) on tier 1 MCHs 1 GbE uplink on each MCH to interconnect both tiers Uplink for TDM traffic (2G/3G BS) over STM-1 interface AMCs Dual star to 12 slots for each MCH sufficient (AMC ports 0 and 1 as in mTCA spec) No need for PCIe or other fabric on MCH (multi processor operation for traffic processors not feasible with PCIe) Special backplane design for storage subsystem Point-to-point connections for SAS/SATA disks in redundant storage sub-system (storage and processor) Does not need to pass MCH Basic MCH is sufficient

Media Gateway/Trunking Gateway Call Processor Subsystem Media Processor (DSP) transcoding Media Processor Subsystem Call Processor & Main ctrl. Fabric (GbE) Traffic Processor 1 2 3 4 5 6 7 8 Traffic Processor Subsystem Fabric (GbE) Switch I/O STM-1 I/O STM-1 I/O STM-1 I/O STM-1 Uplinks TDM Network (trunks) IP Network (NGN) Media Processing (e.g. VoIP to TDM) 12.000 subscribers 12 tps (48.000 BHCA) 800 Mbits/s of traffic

Media Gateway/Trunking Gateway Call Processor Subsystem Media Processor Subsystem Traffic Processor Subsystem Media Processing (e.g. VoIP to TDM) 12.000 subscribers 12 tps (48.000 BHCA) 800 Mbits/s of traffic

Traffic Profiles – Media Gateway Media Gateway/Trunking GW: traffic Transcoding and media processing using DSPs: VoIP to TDM TDM to VoIP 12.000 subscribers 12 tps (48.000 BHCA) 800 Mbit/s of traffic DSP load: 12.000 data streams Media Gateway/Trunking Gateway

Media/Trunking Gateway - mTCA Profile Implications on fabric and MCH 10 GbE uplink capacity for network uplink (NGN) on each tier 2 MCH 10 GbE uplink on each MCH to interconnect both tiers 10 GbE uplink on each tier 1 MCH to interconnect Call Processor Subsystem on upper shelf Uplink for TDM traffic (SS7) over STM-1 interface AMCs Dual star to 12 slots for each MCH sufficient (AMC ports 0 and 1 as in mTCA spec); No need for PCIe or other fabric on MCH (multi processor operation for traffic processors not feasible with PCIe) Special backplane design for storage subsystem Point-to-point connections for SAS/SATA disks in redundant storage sub-system (storage and processor) Does not need to pass MCH Basic MCH is sufficient

Typische Konfigurationen vorher testen erspart Überraschungen Systems Validation Typische Konfigurationen vorher testen erspart Überraschungen

Services supporting systems design Professional Services: Training & tutorials in ATCA systems and systems design Consulting in design & engineering of ATCA/mTCA systems Pre-integrated systems to develop customer specific designs Engineering support for customer projects Systems Validation Conformance, interoperability, performance and benchmarks Pre-integrated systems Customer designed systems 3rd party systems Using of Kontron validation tools Validation of AMCs in ATCA and mTCA environments Validate configurations of customer projects Set-up OS&HA environment Remote diagnosis and repair

Kontron R&D Lab Systems under test Load & conformance Lab environment for validation and tests

ATCA System Validation Kit Starthilfe für Kundenprojekte, für den internen Gebrauch und Demos

Media Server start-up configuration KAVE terminal switch Internet (e.g DSL& dynamic DNS) Streaming client Streaming Clients

Applications Start-up Configuration: Application Demo: 2x AT 8901 Hub with 2x AT 8020 CPU 2x SATA AMC each; Linux installed (Red Hat, CentOS) Application Demo: Quicktime Streaming Server (H.264, MPEG-4, 3GPP) or other free streaming server (t.b. defined) Systems Validation & Demo: KAVE tools installed Extensions: HA platform (Linux HA cluster, ENEA, others to validate) RAID Options: SATA RAID & SAS RAID configuration DSP AMCs for media processing on carrier board (t.b. defined) 1x E1 AMC/STM-1 + 1x AMC CPU + 2x DSP AMC for TDM/VoIP (Trunking Gateway) on carrier board 1x E1 AMC/STM-1 + 1x CPU AMC for CS7 signalling (Signalling Gateway) on hub board 1st step

Extension 1: HA Platform System Architecture: HA Platform based on Linux OS virtualisation (DRDB, Keep Alive), copy of Kontron Web-Server with support of Kontron IT to demonstrate Switch-over Fail-over ENEA HA platform & GUI Others to validate storage processor synch state Switch (Hub) LAN

Extension 2: RAID Options LAN RAID synch state Option 1: SATA RAID 2 disks per CPU Option 2: SAS RAID 2 disks partitions per CPU (2 ports on SAS disks)

Extension 3: Legacy Interfaces System Configuration: 2x AM 4002 CPU 2x Interphase E1/T1 AMC (iSpan 3639) and 2x Interphase STM-1/OC3 AMC (iSpan 3632) as option Linux & higher layer protocols on CPU AMC Applications: Trunking Gateway: VoIP to TDM and vice versa incl. Voice processing on DSPs Signalling Gateway: CS7 signalling

Extension 4: DSP System Configuration: 1x AT 8400 carrier board 1x AM4002 CPU 3x Surf Rider DSP CPU Linux installed Application 1: Trunking Gateway VoIP to TDM conversion (DSP) DSP & CPU: RTP & call ctrl. E1/STM1 & CPU: Lower protocol layers & higher protocol layers To be validated with sample applications provided by partners (ready to run ) Application 2: Media Transcoding (t.b.d.)

mTCA System Validation Kit Gleicher Fahrplan wie ATCA, jedoch andere technische Basis

IP-PBX start-up configuration MCH CPU Spare Spare Spare Spare Spare Spare CPU MCH WLAN switch 2 SIP WiFi phones in Kontron WLAN Internet e.g. SipGate, PBXnet 2 SIP hardphones public SIP phones

Extension 1: HA Platform MCH CPU Spare Spare Spare Spare Spare Spare CPU MCH System Architecture: HA Platform included based on OS virtualisation for Linux Option: ENEA Option: other implementations for the sake of comparison storage processor synch state Switch (MCH) LAN

Extension 2: RAID Versions MCH assumed to support meshed configuration to CPUs MCH CPU Spare Spare Spare Spare CPU MCH RAID RAID Version 2: SAS RAID 2 disks partitions per CPU (2 ports on SAS disks) Version 1: SATA RAID 2 disks per CPU RAID RAID synch state synch state LAN LAN

Extension 3: Interfaces MCH CPU I/O 8x E1 8x E1 I/O CPU MCH System Architecture: Line cards for POTS, ISDN phones PSTN PRI Extra I/O ports for mir SIP connectivity and IP based signalling protocols

Das nächste Mal (Teil 10) Die Zukunft der Netze Ein Blick zurück Öffentliche und private TK-Netze Anwendungen in Netzen Organisation von Netzen Mikroprozessoren – in Zukunft alle vernetzt Anwendungen aus der Industrie, Transport Medizintechnik

Ende Teil 9