August 3-4, 2004 San Jose, CA Service Creation in Next-Generation Networks Atul Varshneya Chief Architect BayPackets

August 3-4, 2004 San Jose, CA Agenda Why Service Creation? Service Creation Requirements Service Creation: Definition and Process –GUI Approach –Coding Approach –Trade-offs –Debugging and Testing Examples Q&A

August 3-4, 2004 San Jose, CA Why Service Creation? Save Money: More Cost Effective –Utilize internal development resources –Open API’s to OSS / OAM&P provide lower integration costs Stay Competitive: Faster Time to Market –Faster development, testing, and deployment Better Service: Retain Control of Application –Enhance and customize application features for specific customers without dependence on application vendor

August 3-4, 2004 San Jose, CA Network Evolution: Service Control Point (SCP) Service Control Point (SCP) Challenges  Slow Time-to-market  High Capex / Opex  Proprietary Architecture  Point Solution for Services  Lack of Service Portability  Limited 3rd Party Apps  Lack of OSS/BSS Integration  Switch Dependencies PSTN PSTN SS7 AIN/INAP Wireless SS7 Class 4 PBX Class 5 Service Node PBX Service Node

August 3-4, 2004 San Jose, CA Requirements for Next-Gen SCP Requirements  Voice, Data & Multimedia Apps Support  Open and Extensible Architecture  Multi-protocol Support  Flexible Framework for Apps Development  Integration with OSS Infrastructure  Real-time End-user Control Next Generation Service Control Point

August 3-4, 2004 San Jose, CA Requirement: Multi-media Applications Support Enhanced Messaging ApplicationsVoic Unified Communications Single Number Service Internet Call Manager Click-to-TalkPresence Advanced Voice Applications Voice VPN Advanced 800 PrePaidPostPaid WirelessApplications SMS, EMS, MMS Hot Call Routing Location-Based Services

August 3-4, 2004 San Jose, CA TDM Switches Media Gateways Soft Switches Media Servers Requirement: OSS Integration Carrier Provisioning Next Generation Service Control Point VoiceVPN800UCSNS3rd Party Carrier Billing

August 3-4, 2004 San Jose, CA Next-Gen SCP: Multi-protocol Support Call Model (JCC, CS1, CS2) TCAP INAP CAMEL/WIN SIP MGCP Call Control APIs

August 3-4, 2004 San Jose, CA Wireline Carriers Cable MSOs Wireless Operators VOIP Carriers Heterogeneous Networks Requirement: An Open & Extensible Architecture Next Generation Service Control Point Open APIs Application DevelopersEnterprise ITCarrier IT Applications Development

August 3-4, 2004 San Jose, CA Agility Network Apps Suite Network applications for immediate revenue generation Agility Network Services Platform (NSP) Carrier-grade application server for hosting multiple network services across multiple networks Agility Mediate Scalable real-time mediation platform for seamless OSS/BSS integration Next Gen SCP Internet Web-based End-user Control Media Server Packet Switch Packet Switch OSS/BSS (billing) SMS TDM Switch Agility TM System RSI Advanced Network Voice Applications RSI Enhanced Network Messaging Applications Agility Mediate “The New Service Point” Agility Network Service Platform TM VoVPNATFPrePaid/PostPaidVMUCPCMICMHCR CAMEL/ WIN SIP/ MGCP SIP/ H.323 AIN/ TCAP CDRs/Events from Switches/Gateways BayPackets’ Approach to Next Gen SCP Wireless Switch

August 3-4, 2004 San Jose, CA VoIP, TDM Gateways, Softswitches TDM Switches Next Gen SCP: Flexible Framework for Applications Development Subscription Database Call ControlMedia ControlMessagingNotification Instant Messaging Sample External Application SCE Carrier Provisioning Call Model Manager Messaging Server Media Servers Internet SLEE Parlay Framework Call Control User Interaction MessagingNotification Instant Messaging UC Application Resources Sample Internal Application Billing Mediation Management Provisioning Interface Single Number Notification Server Instant Messaging Server

August 3-4, 2004 San Jose, CA Service Creation: Definition and Process Service Creation: Implementing the flow of network protocol interactions, data modifications and control-flow decisions to deliver the intended features to the end user.

August 3-4, 2004 San Jose, CA GUI Approach to Service Creation Typically includes Service-Independent Building Blocks (SIBs): Pre-built blocks of service logic User creates a “flow graph” by dragging, dropping, and connecting SIBs Configure SIBs with intended behavior –Assign values, bind variables, etc

August 3-4, 2004 San Jose, CA GUI Approach Screen Shot

August 3-4, 2004 San Jose, CA GUI Development Process

August 3-4, 2004 San Jose, CA Hand-Coding Approach to Service Creation Traditional Software Engineering Approach –design, code, test Application Programming Interface (API) –Environment-based Servlet Model –Abstracted model: Parlay/JAIN

August 3-4, 2004 San Jose, CA Trade-offs – GUI and Hand Coding CharacteristicsGUI DevelopmentHand-coding Development Ease of UseHigh – rapid creation, lots of reusability, does not require advanced programming skills. Medium – Requires programming skills. Requires longer development time. Reusability limited. RobustnessHigh – all SIBs pre-tested and certified. Medium – Depends on quality of software development process by programmer/company. PerformanceMedium – Typically 10-15% lower performance metrics versus hand- coding because of extra overhead in SIBs. High – Programmer has more control on resource allocation and use of constructs / service flow to optimize performance. Capabilities / Features Medium – Limited by set of SIBs provided by tool vendor. Also have structural limitations to the logic flow (e.g., no looping) High – Programmer has complete control and full access to all platform capabilities. Support and Maintenance Full support from Vendor when using SIBs. Support and Maintenance to be provided by programmer/company – not the tools vendor. When to Use  Prototyping / proof of concept  Simple application requirements / narrow domain  Performance and throughput not paramount  Complex, demanding application requirements  Performance critical  High degree of application integration requirements

August 3-4, 2004 San Jose, CA Debugging and Testing Requirements Simulated Test Environment – including network and OSS systems Remote debugger: Capability to set “Break Points” for real-time testing and step-by- step execution Automated test cases Other “plug-ins” such as a test harness, etc.

August 3-4, 2004 San Jose, CA Test Environment and Simulation SERVICE LOGIC Enhanced JCC APIs Network Events & Call Backs Service Logic Execution Environment Test Logic Execution Framework Other APIs Test Logic 1 JCC Events & Callbacks EVENTROUTOREVENTROUTOR SCE Test Logic 2 Test Logic 3

August 3-4, 2004 San Jose, CA Example #1: Calling Card Service

August 3-4, 2004 San Jose, CA Q&A: Service Creation in Next-Generation Networks Atul Varshneya Chief Architect BayPackets

August 3-4, 2004 San Jose, CA Service Creation Requirements Design, develop and maintain services in a fast and flexible manner Web based Easy-to-Use GUI programming environment or SDK for traditional coding approach Support for JAIN and Parlay/OSA Based on standard software tools and builders Rich collection of integrated SIBs Provide for integration of user-defined SIBs Rich set of editing facilities - cut/paste, alignment, drag and drop, etc. Internationalization/ Localization Testing of applications in a simulated environment Version management of service and library objects (integrated with ClearCase, others)