august 3-4, 2004 san jose, ca service creation in next-generation networks atul varshneya chief...

August 3-4, 2004 • San Jose, CA • www.voipdeveloper.com

Service Creation in Next-Generation Networks

Atul Varshneya

Chief Architect

BayPackets


Agenda

• Why Service Creation?• Service Creation Requirements• Service Creation: Definition and Process

– GUI Approach– Coding Approach– Trade-offs– Debugging and Testing

• Examples• Q&A


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


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

PSTNPSTN

SS7

AIN/INAP

WirelessWireless

SS7SS7

Class 4

PBX

Class 5Service Node

PBX

Service Node


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


Requirement: Multi-media Applications Support

Enhanced Messaging Enhanced Messaging ApplicationsApplications

VoicemailVoicemailUnified CommunicationsUnified CommunicationsSingle Number ServiceSingle Number ServiceInternet Call ManagerInternet Call Manager

Click-to-Talk Click-to-Talk PresencePresence

Advanced Voice Advanced Voice ApplicationsApplications

Voice VPNVoice VPNAdvanced 800Advanced 800

PrePaidPrePaidPostPaidPostPaid

Wireless Wireless ApplicationsApplications

SMS, EMS, MMSSMS, EMS, MMSHot Call RoutingHot Call Routing

Location-Based ServicesLocation-Based Services


TDMSwitches

MediaGateways

Soft Switches

MediaServers

Requirement: OSS Integration

CarrierProvisioning

Next Generation


VoiceVoiceVPNVPN

800800 UCUC SNSSNS 3rd Party

CarrierBilling


Next-Gen SCP: Multi-protocol Support

Call Model(JCC, CS1, CS2)

TCAP

INAP

CAMEL/WIN

SIP

MGCP

Call Control APIs


WirelineCarriers

Cable MSOs

WirelessOperators

VOIP Carriers

Heterogeneous Networks

Requirement: An Open & Extensible Architecture

Next Generation


Open APIs

Application DevelopersEnterprise IT Carrier IT

Applications Development


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

MediaServerMediaServer

Packet

Switch

Packet

Switch

OSS/BSS(billing) SMS

TDM SwitchTDM

Switch

AgilityTM System

RSI Advanced NetworkVoice Applications

RSI Enhanced NetworkMessaging Applications

Ag

ilit

y

Me

dia

te

“The New Service Point”Agility Network Service PlatformTM

VoVPN ATF PrePaid/PostPaid VM UC PCM ICM HCR

CAMEL/

WIN

SIP/MGCP

SIP/H.323

AIN/TCAP

CDRs/Events from

Switches/Gateways

BayPackets’ Approach to Next Gen SCP

Wireless Switch

Wireless Switch


VoIP, TDM

Gateways,Softswitches

TDM Switches

Next Gen SCP: Flexible Framework for Applications Development

SubscriptionDatabase Call Control Media Control Messaging Notification

Instant Messaging

Sample External ApplicationSCE

Carrier Provisioning

Call Model Manager

MessagingServer

Media Servers

Internet

SLEE

Parlay Framework

Call ControlUser

InteractionMessaging Notification

Instant Messaging

UC Application

Resources

Sample Internal Application

Billing Mediation

Management

ProvisioningInterface

SingleNumber

NotificationServer

Instant Messaging

Server


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.

SCE Graphical Editor

SLEE

SLEESDK

Servicecode

IDE

Serviceexecutable

Service Development by hand-coding

Service Development using Graphical SCE

Serviceexecutable

SCE


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


GUI Approach Screen Shot


GUI Development Process

SIB

Outputs

INPUTS:• Used for SIB’s functioning – Mandatory / Optional• Sources:

Service Variables output by other SIBsEvents dataConstant values

OUTPUTS:• Generated by SIB’s functioning• Assign to local variables

Connections

Inputs

Outputs

CONNECTIONS:• Passing of Control to other SIBs• Connections selected on:

Success/Failure of operationSome other o/p specific to the SIB


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


Trade-offs – GUI and Hand CodingCharacteristics GUI Development Hand-coding Development

Ease of Use High – rapid creation, lots of reusability, does not require advanced programming skills.

Medium – Requires programming skills. Requires longer development time. Reusability limited.

Robustness High – all SIBs pre-tested and certified.

Medium – Depends on quality of software development process by programmer/company.

Performance Medium – 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


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.


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

EVENT

ROUTOR

SCE

Test Logic 2

Test Logic 3


Example #1: Calling Card Service


Q&A:Service Creation in Next-Generation

Networks

Atul Varshneya

Chief Architect

BayPackets


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)

august 3-4, 2004 san jose, ca service creation in next-generation networks atul varshneya chief...

Documents