Your SlideShare is downloading. ×
0
Solaiemes AVISG Technology 2009
Solaiemes AVISG Technology 2009
Solaiemes AVISG Technology 2009
Solaiemes AVISG Technology 2009
Solaiemes AVISG Technology 2009
Solaiemes AVISG Technology 2009
Solaiemes AVISG Technology 2009
Solaiemes AVISG Technology 2009
Solaiemes AVISG Technology 2009
Solaiemes AVISG Technology 2009
Solaiemes AVISG Technology 2009
Solaiemes AVISG Technology 2009
Solaiemes AVISG Technology 2009
Solaiemes AVISG Technology 2009
Solaiemes AVISG Technology 2009
Solaiemes AVISG Technology 2009
Solaiemes AVISG Technology 2009
Solaiemes AVISG Technology 2009
Solaiemes AVISG Technology 2009
Solaiemes AVISG Technology 2009
Solaiemes AVISG Technology 2009
Solaiemes AVISG Technology 2009
Solaiemes AVISG Technology 2009
Solaiemes AVISG Technology 2009
Solaiemes AVISG Technology 2009
Solaiemes AVISG Technology 2009
Solaiemes AVISG Technology 2009
Solaiemes AVISG Technology 2009
Solaiemes AVISG Technology 2009
Solaiemes AVISG Technology 2009
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Solaiemes AVISG Technology 2009

726

Published on

This is the AVISG product sheet specification as ppt. The document describes what is AVISG platform, the multimodal interaction being enabled in different working modes, and also the roadmap for …

This is the AVISG product sheet specification as ppt. The document describes what is AVISG platform, the multimodal interaction being enabled in different working modes, and also the roadmap for coming 2 quarters.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
726
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
26
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Multimodal and Voice Solutions A new approach based on network intelligence
  • 2. Company information Solaiemes
  • 3. Solaiemes • Start-up founded Q4-2006 • Focused on mobile services • Combinatorial services in NGNs, UC, Mobility • Mobile usability • We develop our own technology • Multimodal voice/web application server platform: AVISG • Media server platform: LiveServe • PTT application server platform: VoxServe • Objectives  become an infrastructure provider of mobile service platforms Feb’09, mencionado en el informe Frost&Sullivan H1 H2 H1 H2 H1 MWC 2009 Key 07 07 08 08 09 TakeAways Briefing (slide 8)
  • 4. Platforms AVISGTM • Voice/Web multimodal platform • Simplifies access to information services from mobile devices • Allows integration with most IVR systems • Do not require installing specialized software in the device LiveServeTM • Media server compatible with web infrastructures • With support for live video from: mobile devices, IP cameras, webcams, etc. • Interoperates with most CRM/ERP systems to provide multimedia in IT services VoxServeTM • Application server for PTT • Allows emulating TETRA services with much lower costs • Allows integration with most IVR systems
  • 5. Solaiemes voice/web multimodal platform AVISG 2.0
  • 6. AVISG 2.0 Customer Care • Multimodal customer care • Operator assisted browsing • Rich Media Alerts Mobile Push Platform •Web Contents Vocal Browsing •Multidevice • Multimodalization of web portals •Asynchronous •Event Driven Mobile Marketing • Multimedia push campaigns
  • 7. AVISG 2.0: Mobile Multimodal Services Multimodal System Seamless Mix Leverages Integrates with Solaiemes simultaneous AVISG existent vocal existent IT visual and vocal infrastructure systems interaction
  • 8. AVISG General Basic functionality • Builds multimodal services combining a web session and a simultaneous plain old phone call • Both, phone call and web session are synchronized • The user can talk and see the results on the device screen • Web navigation can be commanded by voice commands • Voice dialogs can be switched by keyboard based web navigation • Vocal information and web information are always coordinated AVISG differentiating ingredients • Service intelligence located at the network side • Most 3G subscribers are potential users • Works in most 3G devices and in many GPRS/EDGE devices • Do not require installing special software in the device • Works over a wide range of 3G handsets, from low profile like Nokia 6210 to high-end like iPhone • Ajax support is not required in the mobile browser • The voice session is established through a conventional phone call • The web session is based on standard HTTP/HTML technologies • Can be integrated with existing IVR platforms, no need for special voice service equipments.
  • 9. AVISG from the user perspective Best user perception • User navigates the service using his voice • Or manually through the browser whatever he prefers • Simultaneous vocal and visual information enrich user experience What the user needs • A mobile phone with multi-rab support (most 3G and many GPRS/EDGE devices comply) • 3G coverage • AVISG can fallback to a just vocal service in the same phone call, in case of going out of 3G coverage What the user does • Dial the system phone number (a standard phone call) • Listen the TTS instructions and accept a SMS message • Look at the screen device and see how the web browser opens • Navigate using voice • The web information shown in the screen will evolve accordingly • Navigate using the keyboard to follow hyperlinks and press buttons • The TTS information will evolve accordingly
  • 10. AVISG standards based Web content presentation • HTTP 1.0 and HTTP 1.1 whatever the handset supports • Also the corresponding secure versions (HTTPS) • XHTML according to whatever the handset supports Vocal content presentation • VoiceXML 2.0 y 2.1, whatever the IVR platform supports Interconnection with IVR • Using CCXML 1.0 internally to AVISG Multimodal coordination • Coordination among all modes is done using SCXML 0.9 internally
  • 11. Multi-device Push Engine • Web content push to mobile. AVISG is capable of getting web content into the handset browser without user intervention. Content is pushed asynchronously to the terminal according to predefined navigations (autonavigations) and externally generated events, like those coming form an IVR. AVISG implements a content push mechanism (patent pending) on top of standard web technology that does not requires neither javascript nor AJAX capabilities, enabling the use of any handset compatible with WAP 2.0 standard. NOTICE: Content PUSH does not require on-device applications, AJAX or javascript • Multidevice. AVISG maintains a device database and is able to identify each web agent. This information enables the selection of the best suited push mechanism and content formats. • Fast user perception (just the net delay). One of the most important features in AVISG is the user perception of fast response to vocal commands. The main effect of AVISG push engine is that the only delay perceived by the user are those caused by network data transfer and IVR operation. • Without unnecesary traffic consumption. AVISG avoids polling to implement the push mechanism and so it also avoids wasting data traffic .
  • 12. Multimodal Function • Simultaneous vocal and visual browsing. AVISG implements a multimodal engine able to synchronize one Web mode (channel) with the browser in the handset and a BUS mode with the IVR. The multimodal engine collects events from any mode and propagates proper actions to all of them. Any voice command or web request will cause both web and grammar change. • Session based. AVISG is session based. It host a single session with multiple modes. Session can be initiated either by the Web mode (access to a web page) or by the BUS mode (phone call to an IVR). • Easy integration with IVR Systems. AVISG supports interaction with IVR carried out by a CCXML & VoiceXML standards. It also implements a bidirectional proprietary BUS to be used with IVRs no supporting CCXML • Easy development of services. Multimodal services just consist of: – Dynamic Web contents. They may be templates deployed directly on AVISG or web pages proxied on-line from external Web portals. – Dynamic Vocal contents, VoiceXML files representing dialogs associated to each page. They can also be templates deployed on AVISG or can be inferred from the web page presented simultaneously – Service definition. Web and Vocal contents association, and automatic navigations rules definition. AVISG provides an authoring tool. • SaaS Ready. A multimodal AVISG platform on a SaaS configuration allows each final client to self provision and deploy services.
  • 13. Integration Data Bus • It allows data integration with external sources. It implements an ESB (Enterprise Service Bus) that eases integration with any external IT system. That way web pages (and voiceXML pages) are templates with dynamic data from external systems. It allows implementing transactional services on AVISG. • Integration with external IT systems. Web content, vocal content and even auto-navigations need not be just static content. AVISG is ready to integrate with heterogeneous external information systems to achieve several goals: – Introduce dynamic information in contents delivered to the user, both in the web side and in the vocal side – Capability of initiate transactions from AVISG. A multimodal interaction from a user (vocal o manual) can input data in a form and trigger a transaction. – Dynamic web content presentation and auto-navigations. Data got from an external system can be used to determine the navigation of a given user and the information to present to him • Standards based and SOA ready. AVISG is ready to integrate in a SOA ecosystem, where information sources and transactions systems are exposed as services. This is achieved by means of an ESB integrated in AVISG. This ESB allows to directly integrate standard services (Web services, REST services, etc) and to easily develop custom connectors to ad-hoc systems • Corporate environments and SaaS environments. The integrated ESB allows to easily integrate ad-hoc IT systems in a corporate environment and Internet services (REST or WS) in a SaaS service where the IT services are in the client premises and are exposed through standard Internet technologies (REST or WS). • Push services. External services may behave in a request/response way to retrieve data or trigger transactions, but is also possible that external IT systems trigger interactions or navigations in AVISG. The integrated ESB allows working much alike an Event Driven Architecture.
  • 14. Content repository, web and vocal • Complete solution, no need for external web or vocal content repository. A client of this service does not need to update several systems to publish a new service, all related assets: HTML files, images, CSS files, VoiceXML files and auto-navigation definitions are published to a single deployment node. This enhances the availability of multimodal services as is less error- pone than maintaining separate repositories for each type of asset. • Web access. Content repository can be accessed via Web, thus allowing a remote operator to administer the contents of a service. This web access is secured and allows different services published on AVISG to be administered by different administrators • Versioning support. Each time a service is updated a version is stored, thus allowing to rollback to previous versions of the service (that means previous versions of all assests: web files, VoiceXML files, etc.) • SaaS ready and client self-administration. A single AVISG server can host different services, each of them for different clients. Each client can have one (or several) administrators of his services that will have complete access to all the assets of his services, and only to those assets, he won’t be able to see anything of any other different client service. • Template contents, both vocal and web. Textual contents stored in the repository can be templated. That means that all textual content can be fed with dynamical data got from external IT systems or user input. That means Web and VoiceXML content is dynamic. • Also allows external web portals. In any case is possible to multimodalize existent web portals without storing those web contents in the AVISG content repository. The vocal contents (VoiceXML) can be inferred from the web content or can also be stored in the AVISG content repository.
  • 15. Clustering, scalability and HA • Clustering. AVISG is able to work in a cluster mode, that means that several physical AVISG servers can be configured to work as a single Web traffic server. This provides: – High availability , if one server goes down the other takes care of the service even AVISG1 AVISG2 ongoing sessions are transferred to the server that stays alive. – High scalability. This makes possible to grow the server capacity without having to J2EE Server J2EE Server purchase bigger and more expensive equipment. AVISG Web Push AVISG Web Push • Web clustering. This is achieved using classic techniques AVISG Core servicfes AVISG Core services implemented by the Java EE container in which we have deployed the AVISG server. • Event clustering. Regardless of which physical server host a given Clusterable DB Clusterable DB RDBMS RDBMS session, browsing events for that session will get into the system using any of the alive servers in the cluster. The events will be internally routed to the server that hosts a given session. If the server Browsing event bus Browsing event bus that is getting browsing events for the IVR goes down, the events will be rerouted to one of the alive servers in the system. • Highest SLA. Carrier grade system availability Browsing events
  • 16. Monitoring JMX and SNMP • JMX monitoring. AVISG can be completely monitored administered and operated using JMX, the Java Managemente standard. Any standard JMX console, even the jconsole included in the JVM can ne used to monitor the system. The elements managed with JMX include all Java EE Container elements and the specific AVISG elements. All of this elements have: – JMX attributes that can be read or write to get the configuration or configure that element – JMX operations that allow to operate on that element – JMX events, that send asynchronous alerts that some condition has arised (errors, alerts, warnings, etc.) • SNMP monitoring. All JMX elements can be also exposed using SNMP. They just need to be configured in an included JMX-SNMP bridge. • Web access. The Java EE container chosen include a web JMX console that allows managing the entire platform from web • AVISG specific elements monitored: – Session Manager. Allows managing the AVISG session lifecycle and interaction with the session. Even browsing event s can be sent to that session – Campaign manager, allows management of the content repository and auto-navigations definitions – Configuration Manager, allows managing the complete configuration of the AVISG server
  • 17. AVISG Operation Modes • AVISG supports two operation modes: self contained web contents and external web portals • Self Contained Web contents. In this mode all web content is stored in the internal content repository, and dynamic content (templating engine) takes place in AVISG. This mode of operation is most suited to enhance existent vocal services with multimodality capabilities, as it provides: – A single deployment point of all multimodal service resources (web, content, vocal content, navigation definitions, etc.) with versioning capabilities to ensure allways consistency of all involved elements (vocal, web, data, etc.) – It is easier to get web content suited to multimodal browsing, that is without vertical scrolling, and even more suited to several type of handsets. – Most adequate for SaaS enviroments where clients need not have any web infrastructure. A single SaaS offering includes hosting of all elements (vocal and web) – Allows a seamless transition from vocal-only service to multimodal service and back to vocal-only service, all in the same call. Thus the system ensures that a user is allways served with the highest quality of service according to his circumstances. Even in the case of data connection loss the user can continue in the same call with at least vocal service. • External Web Portals (AVISG Proxy). This operation mode can be considered as a multimodal proxy. It allows an existent web portal to become multimodal. It takes web requests and relays them to the existent portal. The response web page is modified to implement the push mechanism and navigation can be started both from the web interface or the vocal interface. This mode of operation is most suited to enhance existent portals to give mutlimodal service, as it provides: – No need to modify the existent web portal – AVISG can infere the vocal content by parsing the web pages from the portal to ensure consistency between the vocal and web part. Anyway it is also possible to add custom VoiceXML content . – Most adequate for SaaS offerings where the clients do have their own web infrastructure.
  • 18. Solaiemes application server for the AVISG multimodal platform AVISG Self contained
  • 19. AVISG Self contained architecture Web session Multidevice Web Push Dispatcher Engine Web session 3G Network Voice Navigation Integration bus Voice call CCXML Voice or call event Browsing event External IT event bus engine ESB Engine systems Voice call Navigation Start/stop dialog events Multimodal event Voice->web ASR event (change of VXML dialog) Web->voice Multidevice Content VXML VXML req repository Browser Servlet Voxeo Prophecy AVISG 2.0 Server
  • 20. Self contained service development cycle Configuration And data integration <XML> <XML> <XML> AVISG 2.0 Bus de Servicios Service Templating Design Multidispositivo <XML> <XML> <XML> Bus de Eventos Integración Personalización <XML> <XML> <XML> <XML> <XML> <XML> Content Contenidos Navegación Creation <XML> <XML> <XML> Design Development Deployment
  • 21. Self contained web contents: repository model • An AVISG service just consists of Web contents, vocal contents and auto-navigation definitions. Those all are just normal files that just need to be deployed in the content repository • Simple model. Content repository is represented Web and Vocal by a web folder. Each folder inside it represents an contents AVISG service. There are no requirements on the inner organizations of each of the AVISG service folders. All web and vocal contents are stored in the AVISG service folder. Navigation definitions are stored in a separate folder. • Web accessible. Each AVISG service folder can be accessed using a web interface or a WebDAV Navigation interface. Remote web access is secured to ensure definitions only the service owner can access his contents. • SaaS capable. A single repository can be used for several clients. Each client will be able to manage only his own contents, and will be able to self- manage all contents in his service
  • 22. Self contained web contents: IT systems integration • Embbeded ESB in AVISG is Mule • State-of the-art and Standards based. It complies to the most important standards in SOA environment and Java Environment (JAX-WS, JBI, WS, REST, etc.) • In Mule all integration is declared in an XML file • Mule provides authoring tools for that XML file embedded in the eclipse development platform. • There are several connectors to standard systems available • Connectors to ad-hoc systems can be developed in Java following Mule development guidelines.
  • 23. Solaiemes web proxy for the AVISG multimodal platform AVISG Proxy
  • 24. AVISG Proxy: a brief description What is the AVISGTM Proxy? • It is a proxy module allowing the reuse of external web sites on the AVISG Platform • It allows using all the AVISG multimodal capabilities • With the AVISG Proxy you • … do not need to create any web contents if you want to navigate on an existing site • … can automatically generate the VXML dialogs from the contents of a web page … • .. or can create your own VXML dialogs associated to a given web page What are the requirements of the external web sites • Must be based on HTML/WML documents (flash or other proprietary formats are not supported) • Preferably should use correct XHTML • Must generate appropriate contents for the particular device being used • The AVISG Proxy does not adapt the contents to the device • Preferably, the contents of a web page should fit in the device screen to avoid scrolling • Not special requirements with respect to HTML/WML derived technologies • Support for: images, forms, CCS, etc. • Limited support for: javascript/wmlscript
  • 25. AVISG Proxy Architecture AVISG Proxy Web req Proxy HTTP Client Web External Servlet Unit Unit Dispatcher Web Site URL and Form DOM Page Rewriting Unit Unit Generation Unit Session variables Dialog data Form data Voice Proxy Dialog event Session and Voice req SCXML Unit Interaction Servlet Engine Manager VXML Generator Unit VXML req VXML Servlet Dispatcher Manual generation Servlet or JSP Servlet or JSP AVISG Runtime
  • 26. AVISG Proxy in action What happens with the multimodal synchronization? • The multimodal stuff is managed by the AVISG Platform • The AVISG Proxy only acts on the web mode of the multimodal session When the AVISG Proxy mode is active • If a web request arrives to the AVISG Platform • It is dispatched to the AVISG proxy • The AVISG Proxy maps the requested URI to an external URL • The AVISG Proxy downloads the external URL document • The AVISG Proxy obtains the DOM of the external document • From the DOM, useful information for the automatic generation of the VXML is extracted • All URLs and forms found in the DOM are rewritten (with the Proxy URL) • The final page obtained after this process is send back to the requesting device • The intelligence on how to coordinate everything is in a SCXML state machine • The VXML dialogs can be generated automatically from the DOM data • The VXML dialogs can be also generated though specific JSPs or Servlets which have access to the DOM data
  • 27. Last enhancements and feature roadmap AVISG Roadmap
  • 28. X+V Support X+V is a standard endorsed by the W3C initially EXAMPLE: developed by Opera and IBM some years ago <?xml version="1.0"?> to bring vocal functionality to web browsers. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+Voice //EN" "xhtml+voice10.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" Among its nice features is to allow to embed xmlns:vxml="http://www.w3.org/2001/voicexml20" voice content (using VXML 2.0) on XHTML xmlns:ev="http://www.w3.org/2001/xml-events"> <head> content. This allows to leverage current web <title>What You See Is What You Can Say</title> applications architecture to bring also vocal and <!—Declare this page as voice aware --> <meta name=”solaiemes-avisg-voice-embed” content=”yes”/> multimodal functionality to voice enabled web <!-- first declare the voice handlers. --> browsers. <vxml:form id=”menu”> <vxml:prompt>Welcome to your Hotel reservation The Solaiemes approach is to use the AVISG application</vxml:prompt> </vxml:form> infrastructure to implement X+V using current <vxml:form id="voice_city"> web browsers that do not have any voice <vxml:field name="field_city"> <vxml:grammar src="city.srgf" type="application/x-srgf"/> functionality and using current IVR systems. <vxml:prompt id="city_prompt"> This allows bringing multimodal (web + vocal) Please choose a city. </vxml:prompt> interaction to users that just have a simple web <vxml:catch event="help nomatch noinput"> browser and a vocal phone (POTS, mobile, SIP, For example, say Chicago. </vxml:catch> VoIP, widgets enabling VoIP embeded in a </vxml:field> webpage, etc). </vxml:form> <vxml:form id="voice_hotel"> <vxml:field name="field_hotel"> Already implemented ……..ask for complete examples
  • 29. Q4/2009 – Q1/2010 Features 1. Multimodal support of JavaScript 2. Multimodal AJAX controlled engine 3. Fully SaaS/Cloud offer with admin & monitoring tools 4. Interoperability with cloud telephony leader vendors and cloud IVR providers 5. Desktop multimodal support with internet telephony API’s 6. Enhanced multi-device support
  • 30. www.solaiemes.com

×