Using Service Oriented Architecture (SOA) for Speaker-Biometrics Applications

Size: px

Start display at page:

Download "Using Service Oriented Architecture (SOA) for Speaker-Biometrics Applications"

Magdalene Rogers
10 years ago
Views:

1 Using Service Oriented Architecture (SOA) for Speaker-Biometrics s Ken Rehor & Judith Markowitz Co-chairs Speaker Biometrics Committee Forum Biometrics in Web Services Biometric Consortium 2006 Baltimore, MD 1 What Is the Forum? Founded: 1999 by AT&T, IBM, Lucent, and Motorola 2000 Partnership with W3C Fundamentally a Web-services orientation First Release: 1999 (now working on version 3.0) Mission: Promote adoption of worldwide Develop and run certification programs Establish requirements for new technologies Deployments: Tens of thousands, (e.g., Amtrak Julie) Members: 380+ SIV: Speaker Biometrics Committee 2 1

Founded: 1999 by AT&T, IBM, Lucent, and Motorola 2000 Partnership with W3C Fundamentally a Web-services orientation First Release: 1999 (now working on

2 Protocols & Standards in Voice Web Architecture SIP Netann MSCML MOML / MSML MSCP DMSP MGCP etc. Conference/ Media Media Control Interface CCXML Call Control Scripts CCXML S CCXML Browser SOAP VXML S GRXML Scripts Audio SSML Caller Phone Network T1 / E1 ISDN SS7 Gateway SIP RFC 2833 RTP Telephony Control Interface Media Mixer / Dialog Control Interface Browser ECMAScript 262 DTMF Audio GRXML G.711, WAV,.au, mp3, etc. MRCP Client Telephony Control Interface: SIP, etc. Dialog Control Interface: SIP, MSCP, etc. M R C P MRCP v1 MRCP v2 SIV You are here SSML GRXML ** no standards yet ** 3 Why Web Services? Core technologies allow creation of granular Web Services from multiple systems Combine several granular Web Services into composite Web Services Combine composite Web Services into composite applications Base functions and high level services are reusable again to create new business services Reference: Web Service Architecture: W3C Note (Feb 2004) 4 2

Telephony Control Interface Media Mixer / Dialog Control Interface Browser 2.0 2.1 ECMAScript 262 DTMF Audio GRXML G.711, WAV,.au, mp3, etc. MRCP Client Telephony Control Interface: SIP, etc.

3 Why Web Services? Phone user or Internet or Intranet Web user Corporate Security Policies Composite Biometric Service Corporate Identity Management System Composite Composite Speaker Web Service Granular Speaker Service SIV Granular Non-Biometric Service Password System Granular Non-Biometric Service Password System Composite Biometric Web Service Granular Biometric Service BSP BSP 5 Example: Voice Portal Phone user or platform Internet Web App. server Weather Stocks Sports News ATM Locator Traffic 6 3

Management System Composite Composite Speaker Web Service Granular Speaker Service SIV Granular Non-Biometric Service Password

4 SOA helps deliver the seamless end user experience Tightly integrated channels and touchpoints Contact Center Web Fax/Fax back Single view of the end user End user has single view of your organization Consistent delivery of service and information across modalities Internal alignment; harmonized assets and processes across the organization Office Service Center Kiosk Catalog 7 Phone / Web Architecture <SIV> Phone user or <grxml>.wav Grammars Audio files Scripts platform Internet or <html> Intranet (web) server Web user Images Audio files Scripts logic Content and data Transaction processing Database interface 8 4

processes across the organization Office Service Center Kiosk Catalog 7 Phone / Web Architecture <SIV> Phone user or <grxml>.

5 Example: Phone / Web Union Pacific RR Railcar release Date: September 17, 2006 User ID: Railcar ID: Mainframe user Mainframe Railcar Database Call Center or Voice Model Database Phone user platform <html> Internet Web user Web App. server 9 Example: VeriSign Multi-Factor Secure Host Phone and Web user External Phone Directory Client information Database or platform Voice Model Database <html> Internet 10 5

6 Issue Security, Trust, and Protocol Considerations in Distributed Voice Web s 11 Security, Trust, and Protocol Considerations in Distributed Voice Web s Basic topology of a application without SIV or IP network browser Voice Web Web Services MRCP Web Service interface 12 6

Distributed Voice Web s Basic topology of a application without SIV

7 Security, Trust and Protocol Considerations in Distributed Voice Web s Basic data movement within a application without SIV or IP network browser.wav Voice Web Web Services MRCP <ssml> <grxml> Web Service interface 13 Security, Trust and Protocol Considerations in Distributed Voice Web s Many possible variations of network / application topology or IP network browser Voice Web Web Service Web Services MRCP SIV Voice database Voice database Web Service interface 14 7

wav Voice Web Web Services MRCP <ssml> <grxml> Web Service interface 13 Security, Trust and Protocol Considerations

8 Security, Trust and Protocol Considerations in Distributed Voice Web s Architecture options produce security implications.wav or IP network browser Voice Web Web Service MRCP SIV? Voice database Web Services <ssml> <grxml> voice Voice database Voice DEFF may be used between SIV components and services Web Service interface 15 Thank you Ken Rehor [email protected] Dr. Judith Markowitz [email protected] Forum

Voice database Web Services <ssml> <grxml> voice Voice database Voice DEFF may be used between SIV

VoiceXML and VoIP. Architectural Elements of Next-Generation Telephone Services. RJ Auburn

VoiceXML and VoIP. Architectural Elements of Next-Generation Telephone Services. RJ Auburn VoiceXML and VoIP Architectural Elements of Next-Generation Telephone Services RJ Auburn Chief Network Architect, Voxeo Corporation Editor, CCXML Version 1.0, W3C Ken Rehor Software Architect, Nuance Communications