Carrier Class Deployments

1
(No Transcript)
2
Building a Carrier Grade ServiceRob
MarchandVoiceGenie Technologies
3
Overview

• What is Carrier Grade?
• Setting Requirements
• Achieving the Goal
• Architectural Guidelines
• Application Guidelines
• Platform Selection

4
What is a Carrier Class service?

• Service that can demonstrate satisfaction of
  Direct Measures of Quality
• User vs. Carrier metrics
• Usability
• Availability
• Performance
• Scalability
• Reliability Maintainability
• Manageability

5
RequirementsUsability

• Measurements of user satisfaction
• Repeat calls
• Minimal transfer to live operators
• Ongoing monitoring of usage and results
• Ultimately driven by other metrics

6
RequirementsAvailability

• What is acceptable to the user?
• Conditioned for telephony service availability,
  as opposed to web availability
• What is acceptable to the deployment agency?
• Capital and operational costs

7
RequirementsPerformance

• Drives the user experience
• Metrics
• Application delivery
• Time to first speech
• ASR response
• Barge-in response

8
RequirementsPerformance

• Application location
• Caching, prefetching policies
• Platform implementation
• Architectural support

9
RequirementsScalability

• Sizing from trial to commercial deployment
• Port, TTS, ASR Density
• TTS and ASR footprints
• Software architecture
• Cost
• OAM issues

10
RequirementsReliability Maintainability

• Reduce impact of failure
• Failover/recovery strategy
• Failure granularity
• Reliability of components
• MTBF/MTTR
• Sparing requirements
• n k installation of (NOC box board)
• Hot swap?

11
RequirementsManageability

• Integration into existing infrastructure
• Alarms, management
• Provisioning, billing
• OAM Support
• Security!!
• Architectural application

12
Achieving the Goal

• Combination of factors
• Implementation Architecture
• Application Architecture
• External Dependencies

13
Architectural Considerations

• VoiceXML Gateway faces the network
• Integrates telephony, ASR, TTS, DTMF, audio
  services
• Gateway to familiar traditional (!) Web
  architecture

14
Architectural Considerations

• VoiceXML model leads to use of commodity Web
  infrastructure components
• N-tier solutions
• Web server farms
• Database clustering
• Load balancing
• Redundant paths
• Content delivery tools

15
Architectural Considerations

• No single points of failure
• Stateless where possible
• Scalable deployment management paradigm
• Centralized vs. distributed?
• Reliability and failure management planning
• Choose mature products

16
Application Guidelines

• Multi-tiered, supporting flexibility of
  distribution, and minimizing impact of failure
• Separation of presentation from service logic
• Reuse of existing components
• Design with eye to scaling
• Think about it now

17
Application Guidelines

• Use a framework of components that meet the goals
• Dynamic content generation
• Pooled database access
• Caching
• Centralization vs. distributed

18
Platform Selection

• Reliability NEBS/Industrial/COTS
• Scalability
• Density tradeoffs (form factor, ports)
• Standards based
• Service logic
• Networking
• Versatility

19
Platform Selection

• Installation Model?
• Assessment of tradeoffs
• ASP (how partitioned?)
• On premise solution (enterprise, carrier)
• Installation facility
• NOC
• CO
• Installation requirements
• Heat, power, survivability

20
In Summary

• Set your requirements for availability,
  reliability, etc.
• Design architecture to achieve these goals
• Select components and deployment method to
  support the application and infrastructure design
• Leverage investment in existing infrastructure
  and skills
• Trial, tune, deploy!
• Measure your performance against the metrics

21
About VoiceGenie

• Carrier-class VoiceXML Platform Provider
• Any VoiceXML application, any speech engine
• http//www.voicegenie.com
• http//developer.voicegenie.com

22
(No Transcript)