04 BroadSoft Technical Overview

BroadSoft BroadWorks platform technical overview

BroadSoft Overview

Service providers are transforming their business models through IP-based applications Our software, BroadWorks, is the platform over which these applications are delivered We are the global market leader to partner with

BroadSoft ®, Inc. Proprietary and Confidential, do not copy, duplicate or distribute. 2

Architectures

Applications

Applications and Architectures Hosted PBX/IP Centrex

Mobile PBX

IMS

Standalone

Standards Architecture Single Converged Infrastructure Extensible Application Framework

Fixed

Cable

Mobile

Residential Broadband

Fixed

Cable

Mobile

BroadWorks Standalone Architecture

BW SIP Network I/F

IP Networks

SGW BW SIP Access I/F

SBC

MGW

T1/E1, DSL, Broadband SBC

Fixed Network

Large Enterprise

MGC

Small / Medium Residential Enterprise SOHO

PacketCable PCMM PS

SBC

GSM/CDMA MGC

MGW

HLR

MSC

Cable Network


Mobile Network

Mobiles

TDM Networks

BW SIP Network I/F

BroadWorks in an IMS Network Architecture

IP Networks

Ma

IWF I-BCF

I-CSCF

Sh HSS

Dh

S-CSCF

SLF

SGF MGCF

BGCF

IMS Core Network

BGF

MGW

TISPAN

PacketCable 2.0

3GPP

P-CSCF

P-CSCF

P-CSCF

PDF

A-BGF

Fixed Network

Large Enterprise

Isc


PDF

BGF

PDF

Cable Network


GGSN

Mobile Network

Mobiles

TDM Networks

IMS SIP AS IMS MRF

BroadWorks Platform Components Core Servers

Application Server Call Control and Features

Media Server Media Resource Function

Auxiliary Servers

Web Server Web and API Security

Session Continuity Function

Xtended Services Platform Xtended Services Interface

Call Detail Server Call Log Storage

Profile Server File Repository Network Server Translations, Routing, and Scalability Engine

Element Management Server Access MediationServer

BroadWorks Standalone Components Web Server / XSP Subscriber Web Portal Web Services Interface

Media Server SIP User Agent Playback and Recording DTMF Detection Conferencing

HTTP

SIP UA

Application Server SIP Back-to-Back User Agent Call Control and Service Logic Provisioning Business Logic Service Profile Database

Network Server SIP Redirect Server Subscriber Location Number Translations Routing Services

HTTP

Browser / Web Services

RTP

Endpoints / Gateways

SIP B2B NCS

SIP Redirect

SIP Redirect

Endpoints

SBCs / Softswitches

BroadWorks IMS Components Application Server Web Server / XSP Ut Subscriber Web Portal Web Services Interface

UE

Media Resource Function

Network Server

Mr SIP Redirect Server Subscriber Location Number Translations

Sh

Isc

Rf/Ro Media Server

Application Server OCF/CCF

CSCF

HSS

SIP Back-to-Back User Agent Call Control and Service Logic Provisioning Business Logic Service Profile Database

SIP User Agent Playback and Recording DTMF Detection Conferencing

Applicable 3GPP IMS Specifications BroadWorks is 3GPP Release 7 Compliant (commercial) Now tracking with Release 8/9 features and enhancements Interface

Functional Spec

Protocol Spec

Isc/Ma/Mr

TS 23.218 – Session Handling

TS 24.229 – Call Control with SIP/SDP

Rf /Ro

TS 32.240 – Charging Principles

TS 32.229 – Charging Applications TS 32.260 – IMS Charging Subsystem

Sh

Cr/Sr Ut

TS 29.328 - Sh Message flows TS 29.329 – Diameter AVPs for Sh TS 29.364 – MMTel Schema TR 24.880 – Media Server Control Technical Report TS 24.623 – XCAP over Ut General/architecture: • 23.002 – IMS Network Architecture • 23.228 – IMS Stage 2

9

BroadSoft ®, Inc. Proprietary and Confidential, do not copy, duplicate or distribute.

BroadWorks Application Server Functionality Call and Service Logic Subscriber Database

Network Devices

Components Execution Server Provisioning Server Database

S I P

Architecture

HTTP

OCI

FTP

SOAP

Radius

S I P

M G C P

Interfaces SMDI SMPP

Access Devices

SIP Back to Back User Agent Call Session Based Patented Service Execution and Feature Interaction Engine Key

SIP, MGCP Open Client Interface (OCI) Simple Object Access Protocol (SOAP) File Transfer Protocol (FTP) SMDI (Call History) Call Naming (SIP), Radius Short Message Peer-to-peer Protocol (SMPP)

Redundancy Active/Active

Regulatory Signaling Information via TCP/IP

Application Server Architecture Services CFA

SCA

VM

3WC

CM

ServiceBus

SNMP

SMTP POP3 OCI-C IMAP4 MGCP SIP SMDI SMPP

SIP

Adapters

RADIUS

Execution Server

POP3 SMTP IMAP4

MGCP OCI-C

OCI-C

JDBC System Monitor

SNMP Agent

TimesTen Database

OCS

Tomcat Servlet Engine

Apache Web Server

JDBC

Provisioning Server OCI-P

CLI

FTP

SSH

OCI-P

HTTP/S HTML

Core Technology - SIP

SIP

• Industry’s most mature SIP stack • Homegrown allowing for quick customization and problem resolution • Interoperable with over 450 SIP based devices • BroadWorks used by Adtran, Cisco and Polycom as their reference for testing • Validated and deployed with IMS core networks from ALU, E///, Huawei and NSN • BroadSoft developed SIP customization for busy lamp fields, advanced call control and bridged line appearances • Programmable controls on a per device basis for ultimate compatibility and interoperability


Core Technology – Java Based Solution

SIP

Java Based

• One of the first real-time Java applications in the industry • Proven to allow rapid software development with better quality than C/C++ • Native Java application without reliance on third party service delivery platform • All software source managed by BroadSoft except for database (Oracle Timesten) • Leverage open source software for quick time to market • Years of development in fine tuning garbage collection for real-time operation • Validated approach as supported by Oracle, IBM and Sun


Core Technology – Call Control Architecture

SIP

• BroadSoft developed “service” operating system

Java Based

• A common architecture for event routing, service execution and precedence

Call Control

• Provides an extensible pattern for creating and adding new services and/or interfaces with no impact to existing functionality • Provides a product which is easier to test and subsequently has less defects • Abstracts interfaces so that services can be written to work with any protocol (SIP/MGCP) • Proven success with current support for over 200 services • Key patent on core architecture


Core Technology – Geographic Redundancy

SIP

• BroadSoft designed geographic redundancy solution tailored for call control

Java Based

• Uses standard IP networking configuration with standard IP addressing and no special software

Call Control

• Supports seamless failover for server outages and IP networking issues

Geographic Redundancy

• Allows for placement of servers in any geography with no distance limitations • Supported by leading IMS core network vendors (ALU, E///, Huawei, NSN) and SBC vendors (Acme Packet) • Proven greater than five 9’s reliability with over 5 years of historical data


Core Technology – Common OAMP Platform

SIP

• Common management container for all BroadSoft servers • Supports identical carrier grade management interfaces on all servers

Java Based

• Includes command line interface, alarms, statistics, configuration, charging and security

Call Control


• Fully tested and validated with leading carrier network management systems (Netcool, Openview, etc.) and customer care systems (Amdocs, Metasolv, etc.)

Common OAMP Platform

• Proven carrier grade in over 50 tier 1 telecommunications service providers • Works on standard servers as well as virtualized servers


Core Technology – Media Framework

SIP

• Software based media resource framework supporting DTMF detection, media playback, recording, conferencing and repeating

Java Based

• Supports standard IMS and VoIP interfaces as well as VoiceXML and CCXML • Provides de facto audio and video codecs and interfaces with all leading speech recognition and text to speech solutions

Call Control


Common OAMP Platform

Media Framework

• Very high capacity with low cost, off the shelf hardware • Homegrown using open source software with no royalties (except certain codecs) • Bundled with the application server providing a significant commercial advantage


Mobile Business by segment BroadSoft’s Solutions Mid-to-Large Enterprise (100-1000)

Small Business (11-100)

Micro Business (< 10)

Mobiles & PBX fixed (97%)

Mobiles and fixed workers

“Mobile Trunk”

“Mobile Enterprise” Mobiles only

“Mobile Office”

We are enabling two mobile architecture models Centrex features on mobile phone

BroadWorks User & Group Features

VM

Mobile extension to premises PBX PBX PBX Features

VM

BroadWorks Mobile Integration (IMS) SIP Trunking

Hosted PBX

Customer Premises PBX/KTS

Customer Premises IP Phone

ISC ISC

SIP

CSCF

SCF

CSCF SCF

SS7 (CAMEL/MAP) SS7 (CAMEL/MAP)

MSC MSC

20

BroadWorks Mobile Integration (NGN) SIP Trunking

Hosted PBX

Customer Premises PBX/KTS

Customer Premises IP Phone

SIP SIP

SIP

SIP

MGC

SCF

MGC SCF

SS7 (CAMEL/MAP)

SS7 (CAMEL/MAP)

MSC MSC

21

Mobile IP Centrex IMS Architecture (Fixed & Mobiles)

SIP

SCF

SS7

Sh

SIP

HSS/HLR Isc Cx

CSCF

MSC 2G/3G CS core

2G/3G Mobile

MGC/F

IP Phones

IMS core

IP PBX ISDN PBX

The opportunity between LTE data and VoLTE High value differentiated services Competitors Approach

“Chasm” Data

BroadSoft Approach

Data

Mobile PBX

Trunking

Call Center

Video Conf

Business Continuity

Family Svcs

SMS Info

Collab

New Segments, New Revenue Streams

BroadWorksIMS – Voice over LTE (VoLTE) Solution TAS

SCC-AS

Service data in HSS VoLTE (“OneVoice”) profile per GSMA IR.92 Enables MMTel/RCS

IMS Centralized Services and Continuity per 3GPP Software upgrade to XS

IP-SMSC

Other Enablers

IMS Core

3GPP SCC AS

BroadWorks Integrated SCC AS Functionality: –

IMS Centralized Services (ICS) per 3GPP TS 23.292

–

IMS Service Continuity per 3GPP TS 23.237

IMS Anchoring & Domain Selection (T-ADS)

E-UTRAN and 3GPP UTRAN/GERAN SR-VCC per 3GPP TS 23.216

Integrated TAS & (optional) SCC-AS on one platform ICS enhanced LTE Phones

Simplified integration Easier to deploy and maintain


Eco System Formal Interoperability Program

In operation since 2001 Three Levels Premier Partnerships BroadSoft Validated Vendor Validated

Specifications and Test plans SIP Access Specification Separate IMS Interface Specifications

Over 220 Config Guides

Open Access http://interop.broadsoft.com Test over the Internet Open community forum for partners Q&A 25

Device specific configuration recommendations


BroadSoft’s Interoperability Testing Program Partner, BroadSoft, or Customer Verification Public test system available on the internet

End-to-End Focus IP PBX’s and IADs are tested against Acme SBC Results are approved by our interop engineers Partner Configuration Guide (step by step)

Resources SIP specifications, test plans, sample call traces End to End Configuration Guides

Our Goal: “Make a SIP Trunk as plug-and-play as ISDN PRI”

IP PBX and IP Phones Interoperability - snapshot

Interoperable with 50+ IP PBXs All Major Vendors

Partner Configuration Guides Quickly reproduce working configurations

BroadWorks Configuration

PBX Configuration

Step-by-Step Configuration BroadWorks PBX

Known issues & work abounds Our customers use PCGs as the basis for the turn-up MOPS Available on BroadSoft Xchange

Deployment Models / Administrative hierarchy

Basic Hierarchy

System

System

Contains settings that apply to the entire cluster Enterprise

Group

Service Provider

Group

Group

Group

Service Provider/Enterprise

Containers to enable multi-site services (Enterprises) and wholesaling (Service Providers) Group

A common set of users which also have services that apply to all users User

User

User

User

User

User

User

User

User

A user, line, phone number, phone, etc…

Enterprise Administration Model Enterprise Model

System Administrator

For large multi-site enterprises, usually 50+ lines Each enterprise is created to contain the multiple sites

Enterprise

Each site is modeled as a group Group: New York

Group: Dallas

Group: Remote

Group: Front Office

Extension dialing performed between sites Site services can span to users in different sites

A

B

C

D

E

F

Applies to both hosted and trunking sites.

SMB/SOHO Administration Model SMB/SOHO Model


Small Businesses of <50 users. May be multi-site and include remote subscribers.

Service Provider Enterprise A

Group: Company A

A

B

Each company is modeled as a BroadWorks group. A company may have one to many lines; each line being a BroadWorks User.

Group: Company B

C

M

N

Location 1

O

Location 2

Some or all members are provided with a DID, others are provided with an extension

Residential Administration Model Consumer Model


For residential families, usually 120 lines Each household is modeled as a BroadWorks group.

Service Provider Enterprise A

Group: Family A

Dad

Mom

House

Group: Family B

Todd

Study Kitchen

House

Group: Family C

X

A household may have one to many lines; each line being a BroadWorks User. A line may be a phone in the house or a household member. Some or all members are provided with a DID, others are provided with an extension

House

Direct POTS Replacement

BroadWorks Provisioning

BroadWorks Interfaces Open Client Interface (OCI) OCI-P – The system activation interface to activate and configure all resources on BroadWorks. OCI-R – They reporting interface to signal external systems of all activation and configuration modifications on BroadWorks.

Xtended Services Interface (Xsi) Xsi – The end-user centric interface for call control, service management and call lists. Provides signaling to external systems of call and service management events.

OCI-P – The Activation Interface Primary Purpose: To perform activation and configuration of data from external portals and legacy systems for all subscriber types. External Access to All Provisioning Data

Portal/Back End Provisioning Systems

All System, User and Service Data

Designed to support personal provisioning clients, enduser portals, and back end provisioning systems

Rich Set of Provisioning Primitives

Add/Delete/Modify Entities –

OCI-P

Authorize/Assign/Modify Resources –

Service Providers, Enterprise, Groups, Users, etc.

Numbers, Services, Domains, etc.

Manage administrators, roles and policies

Multilevel Authorization Model Execution Server

Provisioning Server

Authorization level controls access –

System, Service Provider, Enterprise, Group or User

Flexible Authentication Model

Integrated authentication with MD-5

Optional external authentication interface

Multiple Protocol Support

TCP/IP (allows TLS)

SOAP

OCI-R – The Reporting Interface Primary Purpose: To notify external systems of any modifications to activation or configuration data to provide data synchronization. Notifies of changes regardless of where its initiated*

Portal/Back End Provisioning Systems

Changes from the Web Portal or CLI

Changes from 3rd Party Systems

Changes from Voice Portal or Access Device

OCI-P command used is provided OCI-R

The exact OCI-P command is provided to external system

Files (Audio, Device) are excluded

Passwords can be optionally excluded

Guaranteed Message Delivery Provided Execution Server

Provisioning Server

Messages will be queued and delivered later if the external system experiences a failure

*Note: OCI-P only reports changes to the application server, not the network server

Xsi – End User Call Control and Service Interface Primary Purpose: To allow end-user applications to perform call control and service management actions. End-User centric interface functionality

End-User Applications

Call Management

Call Status

Service Management

Call Lists

Multilevel Authorization Model

Xsi

Authorization level controls access –

System, Service Provider, Enterprise, Group or User

Flexible Authentication Model Execution Server

Provisioning Server

HTTP Basic Authentication

Optional external authentication interface

Designed to support Web 2.0 Applications

RESTful Interface for Web applications and mashups

Multiple Protocol Support

TCP/IP (allows TLS)

HTTP (REST)

Connecting to the Interfaces Xtended Services Platform (Xsp)

OCI OCI Application OCI Application Application

End-User End-User Application End-User Application Application

Key to integration that provides –

Security

–

Scalability

–

External Authentication

Open Client Server (OCS)

Process running on the Xsp or EMS (not shown)

Xsi Web Applications

DMZ Auth Server

OCI (SOAP or TCP)

OCS

Xsi (HTTP or TCP)

Xsi

Optional Web Application on the Xsp to provide the Xsi.

Manages Xsi Access

OCS and Xsi Web App Manages interfaces –

Aggregates sockets

–

Optionally authenticates requests

–

Locates Application Servers

–

Proxies Requests

–

Provide Overload Controls

–

Provide Scope Control

–

Provide Encryption

BroadWorks Web Portal

CommPilot Web Portal Reference portal exposing all BroadWorks features Multi-tenanted views User view exemplifies self-care portal Localization support Fully customizable OWASP Security Compliant SSO & External Authentication Support Supports all modern browsers Xtended interfaces for custom portal implementation. 42


Customization Customizable logo

Fully customizable with localization support

Pre-selectable color themes

43


Customization Capabilities Customization falls into several categories: -

Header and Navigation Changes Cosmetics (graphics, colors, fonts) String Changes & Localization Web Policies

Body

Left Navigation

44

Header


Simple Integration of Self Care Portal

Most operators use our APIs to provide a customized end-user experience. Xsi provides a simple, RESTful integration model

OCI

Xsi / Ut

XCAP HTTP

Self Care Portal

45


AAA

Device Management System

Device Management - How It Works Device Profile Type created on Application Server Defines the Access and Configuration Profile settings for the Device. Container for Device Template files Parent Instance for Device Profiles

Device Profile is created on Application Server and Assigned to User. Device Profile represents the physical device Device Management builds files replacing tags in template files with user data Built files are pushed to Profile Server

Device Initialized on Network Downloads files from XSP via HTTP(S) Use username/password for authentication Device Restarts via SIP NOTIFY from Application Server

Configuration Files

HTTP GET

HTTP(S) GET

HTTP PUT

Templates Files

SIP NOTIFY (sync/reset)

Service Integration Device Template files are created with Device Management Tags When files are built the Device Management tags are replaced with service data for the user.

Template files

Integrated Services

Busy Lamp Field Shared Call Appearance Voice Portal Access Feature Access Codes

User Profile Attributes Time Zone Preferred Language

End User Services Polycom Directory

Service A

Service B

Device files

Firmware Management Firmware versions are uploaded to Device Type Application Server pushes firmware files to Profile Server.

Template files can define which firmware version to use.

Firmware Files

HTTP PUT HTTP GET

Device Management can define firmware version in configuration files using custom tags. HTTP(S) GET

When Phone initializes the Device Configuration files will define which firmware file to download via the XSP. BroadWorks can manage firmware upgrades on a group by group basis.

Configuration Files

Inventory Management Use BroadWorks to Track Devices Deployed in the Field Perform queries through OCI-P or web interface.

Track Device Through Unique Identifiers Device Profile Type MAC Address Device Profile Name

Remove Device Profiles that are no longer in use

Device Management CPE Kits Packages that contain all required information necessary to deploy and configure a device using Device Management. Kits Contain:

Integration Guide – Explains how to use Device Management Device Template files and other device files. Partner Configuration Guide for Device. Partner Configuration Guide for other relevant devices (SBCs and ALGs). In some cases, the device firmware.

Kits available on Xchange for:

Polycom SoundPoint IP and VVX products Aastra 675xi and 9480i/CT and 9143i products Cisco 500 Series Products Linksys 9xx Series Products AudioCodes Access Gateways (in development) Linksys ATA/Routers (in development)

BroadWorks Accounting

Post Paid Accounting Interfaces BroadWorks supports four accounting interfaces FTP – sending of many Call Detail Records (CDRs) in a file periodically Radius – sending of an individual CDR in real-time using Radius protocol (RFC 2866 compliant) Rf – sending events using the IMS Offline Charging Interface

Billing Mediation Server Billing Mediation Server

FTP

CDS Rf

Radius

BroadWorks CDR Modules

Network Call Detail Record Header Module Basic Module Centrex Module IP Module Access

Unique ID System ID Timestamp Time zone User ID Start/Stop Release Cause Calling/Called Number Direction Group Department Service Extensions Redirection Info Access Device Route ID SIP Call ID Codec(s)

Prepaid BroadWorks provides pre-paid functionality using the Ro Interface to an Online Charging System (OCS)

OCS Ro

3GPP Specification TS 32.260 and TS 32.299 Industry is currently standardizing on the Ro Interface Available in IMS and pre-IMS Architectures Mix of pre and post-paid subscribers supported

Platform management

Element Management Server (EMS) Centralized Configuration Management – Pushes “System” data to each network element

NMS SNMPv3

HTTP/XML SSh

PROFILE

System

57

One BroadWorks network view – Auto discovery and configuration Centralized Fault Management – One SNMPv3 interface back to system wide fault management system – Fault analysis Centralized Performance Management – One SNMPv3 interface back to system wide performance management system – Performance monitoring tools Centralized Patch Management – Easily download and deploy patches across the network elements


BroadWorks Fault Management Individual node configuration of SNMP agent NMS Alarm Monitoring

Configurable SNMP Access List and Trap Management SNMP V3 User Authentication SNMP Reports in XML SNMP Proxy for external HW/SW Statefull alarms with correlation and notification parms Configurable alarm/event filtering via SNMP or CLI

SNMP

Enhanced Fault Management w/EMS Couples Performance Management with Fault Management Automatic Discovery and Configuration of added nodes Centralized Syslog management

NMS Alarm Monitoring

SNMP

“North bound”

Audible Alarming Centralized View of nodes Customizable Views Integrated Work-flow management Event List sorting/filtering

SNMP

“South bound”

BroadWorks Performance Management

NMS Performance Monitoring

• SNMP polling to each NE • Full set of PM included in MIBs • Configurable Polling intervals • CLI current and history viewing capability • FTP Reporting capability • Configurable Threshold Crossing Alarms

SNMP

Enhanced Performance Management w/EMS • Intelligent BW PM

– Composite indicators calculated to provide “Health Status” – Status visible on main alarm page – More refined views of server behavior – Reported via HTML, pdf file or HTML email

• Performance Reporting – Dedicated web page – Acrobat® “pdf” file format option – Email transfer with CSV, XSL or XML format

GUI

SNMP

• Health Monitoring

NMS Performance Monitoring

SNMP

– “BW Software Maintenance Guide” best practices coded in EMS – Real time surveillance of usage, queues lengths, etc… as per BW Maintenance Guide, – Early warning diagnostics provided as alarms – Performance statistics stored and available to operator

Overload State Transition Transition from Green to Yellow to Red based on queue delays and/or memory consumption

Criteria to Enter Yellow

Criteria to Enter Red

Engineered Capacity Orderly back-off to avoid pingpong effect between zones

Criteria to Leave Yellow

Separate state transition and criteria for Call Processing related vs. Non-Call Processing related traffic

Criteria to Leave Red

CallP in Red - OR CallP in Yellow - OR -

Non- CallP Queue Delay Sample > DelayToEnterRed

Non-CallP Queue Delay Sample > DelayToEnterYellow

- OR Memory > 85%

Engineered Capacity

Non-CallP Queue Delay Sample Non-CallP Queue Delay Sample < < DelayToLeaveRed DelayToLeaveYellow - AND - AND Memory < 85% Min time in zone - AND - AND Call not in Yellow

Min time in zone - AND CallP not in Red

HW/SW capacities/performance

How do you measure scalability?

Throughput

Measured in “CPS” and translated to “BHCA” How many calls per second can be processed? How hard is it to add more throughput capacity?

User Capacity

Measured in “Number of Users” How many users can be provisioned in one system? How hard is it to add more user capacity?

Provisioning Model

How many provisioning interfaces must be integrated? Does provisioning complexity grow with the system capacity?

User Capacity System user capacity tested to 20 Million users In-Memory Service DB

In-Memory Service DB

Network Server cluster manages one system wide user directory database

In-Memory Service DB

Add Application Server pairs to server additional user capacity System Wide User Directory Database

Service mix dictates capacity requirements per user -- and when to add more Application Servers

Performance Planning Tools System Engineering Guide Detailed engineering guidelines for BroadWorks capacity, scalability and redundancy

Recommended Hardware Guide Validated hardware configurations on both Sun and IBM platforms Small, medium and large configurations for each network element

System Capacity Planner Input call model and service penetration Input preferred hardware platform Output number of network elements and corresponding capacity

Professional Services Qualified engineering resources that can help you plan your network scalability model

Continuous Performance Tuning via EMS Collect performance measurements at the EMS Feed your real world data back into the capacity planner Adjust the model for more accurate scalability planning

Proven Reliability

Reliability tracking based on TL 9000 definitions Historically greater than 5 9s product related reliability 67


Supported Platforms Sun UltraSPARC (Solaris SPARC) Sun Intel x86-64 (Solaris x86-64, Linux) IBM Intel x86-64 (Solaris x86-64, Linux) HP x86-64 (Solaris x86-64, Linux)

THANK YOU!

04 BroadSoft Technical Overview

Recommend Documents