GB2445668A - Posting text online - Google Patents

Abstract

A user with a mobile telephone calls a specific telephone number associated with a web site with user generated content (a so-called Web 2.0 type site), speaks a message which is then converted to text and posted to the web site. A message, such as SMS, email, IM, can then be sent automatically to other users, alerting them to the new message/posting, optionally, giving its content. The alerting message includes a user-selectable link (called an X-Link in the SpinVox implementation) or ordinary telephone number etc; this allows them to respond - e.g. by speaking a response, which then gets converted to text. The response is added as a thread to the original posting, and an alert to that response then sent out, so initiating a dialogue. Texting, emailing, IMing a response to the alert message maybe possible and would again lead to a dialogue because the response would again be posted to the web site, triggering another alert.

Description

A METHOD OF POSTING TO A WEB SITE

BACKGROUND OF THE INVENTION

1. Field of the Invention

This mventi( )fl relates to a method of posting to a wcbsite -i.e. providing comments, information, text of any sort, fir display on a website, such as a blog. The posting is done by a user operating electrical hardware, such as a mobile telephone; but also includes, without limitation, hardware such as smart phones, communicators, wireless messaging terminals, personal computers, computers and application spccific devices. It includes devices able to communicate in an manner over ans kind of network, such as GSM or UMTS, CDMA and \VCDMA mobile radio, Bluetooth, 1rDA etc.

2. Description of the Prior Art

Blogs have become a very popular method of people sharing thoughts, facts, photographs, images and other information freely across the internet. Blogs are largely based around the concept that you're sharing something with a community to whom your blog is relevant, often highly personal.

Blogs now exist for sharing information on films, concerts/gigs, shows and all sorts of entertainment, and more recently, a large rise in their use fijr Citizen Journalism where any member of the public can post news or information about a current issue. The BBC has recently introduced such services along with other leading news providers.

The issue is that often people want to post something to a biog site when they're not at their computer (PC), but actuall as it's happening or when it's relevant. For instance, having just left a cinema you'd be more likel to want to post a comment up about the film you just saw than waiting till later when you're back home. likewise, ifou've seen or heard a news story that suddenly affects your or you have an interest, you want to post an entry then and there.

In many cases, ou will be out and about, not necessarily at your PC.

Current solutions are to use the micro-browsers available on high-end mobile phones to log in and use either the alpha-numeric keypads or micro keyboards to type in your entry. That's fine if you're patient, technically competent and dexterous enough to type more than a sentence or two. hr the rest of us, it's still highh impractical.

It is known to convert voicemail for a mobile telephone user into text, with that text then sent as an or email to the user. This is described in more detail in \VO 21)04/095821 A2, to SpinVox. the contents of which are incorporated by reference.

The present invention takes the idea of converting voicemail to text and builds a new mechanism for posting to websites around it.

SUMMARY OF THE INVENTION

The invention is a method of a method of posting to a web site, the method including the steps of: (a) a user operating electrical hardware to initiate communication with an electronic address associated with a web site with user generated content; Q) the user speaking a message which is then converted to text and provided to the web site; (c) the text based message being posted or otherwise displayed on the web site.

in an implementation, a user with a mobile telephone calls a specific telephone number associated with a web site with user generated content (a so-called Web 2.0 type site), speaks a message which is then converted to text and posted to the web site. This is fast and efficient and greath expands the circumstances in which people can contribute to Web 2.0 sites, such as blogs.

A message (SMS, email, IM can then be sent automatically to other users (typically in a defined small class of registered users) alerting them to the new message/posting (and, optionally, giving its content). This alerting message includes a user-selectable link (called an X-Link in the SpinVox implementation) or ordinary telephone number etc; this allows them to respond -e.g. b speaking a response, which then gets convened to text. The response is added as a thread to the original posting, and an alert to that response then sent out, so initiating a dialogue. The alert message could also he a text or email or ThE, so that or texting, emailing, IM'ing a response would then be possible and would again lead to a dialogue because the response would again be posted to the web site, triering another alert.

The present invention can he used in hiogs and micro-blogs. The blog owner then has a dedicated DD1 phone number a blogger calls; blogs left on this number are converted to text and then emailed to a blog email address or posted directi to the web site. The blog posting appears with the correct formatting and other data for that blog (e.g with the hloggers name or handle, time/date etc).

It can also be used in Mobile Photo Messaging sites to annotate a photograph. The user takes a photo, then adds a voice comment to it before posting (the client application on the mobile telephone includes an option speak a photo' comment). The voice comment is conserted to text and posted together with the photograph. This feature is especially useful in driving MMS useage.

This approach allows an ordinan phone to message anyone in an on-line communili -and they will be notified by whatever mechanism they have specified, enabling them to continue the peer to peer dialogue, but without the constraint of having to be at a web browser (in a PC. It leads to new, incremental revenues.

Typical Web 2.0 web sites cover topics such as personal profiles, news, film, theatre, gigs, art, pubs, bars, restaurants, clubs, hotels, reiews, current affairs and general gossip. An interface can he proided to major blogsites (such as blogspot, blogger.com, Yahoo, Google, etc.) so that messages for them can be readily and automatically posted to the intended hlog topic.

it is possible to run S-links' type implicit searching on the messages posted. An S-link is defined as follows: A text based message for a \X'eb 2.0 site is parsed; a keyword located by parsing is used to generate useful, related links (S-Links') to other websites. The message is displayed as a posting on the \%eb 2.0 site together with the/each link and then anone viewing the posting can then select or use the links to reach the other websites. So we have an incoming message triring an implicit search, with the results given unobtrusively in context in the original posting as an S-Link.

An X-Link can also be included in the message posted on the \\eb 2.0 site, to enable easy voicemail reply to the message in the same hlog an X-Link is a link placed in a message, such as the web site posting (or the alert that accompanies it. When the link is selected by the user, it connects the user's de ice to a conversion ss stem, enabling the user to speak a reply which is then converted to a text based reply message; the reply message is then sent to the message thread posted on the Web 2.0 site. This approach is especially useful where the X-Link is placed in the alert message since it then enables an alert message to be responded to by voice

BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 shows a Spoken text message from Dan Mobile'. It includes the X-Link 84-OO4p123 in the message.

Figure 2 show's bow using X-Link's address book, anybody who receives a spoken message as text can no call in and listen to the original voice message that was left for them.

Figure 3 shows a typical seciuence of messages and the recurring use of the Speak a Reply' X-Link.

Figure 4 shows that message sender Zac Sandier leaves a voice mail which has been automatically converted to text using the SpinVox voice conversion system.

Figure 5 shows another variant, in which the links are incorporated into the message, with the address 20E & 9" St' in the body of the message being selectable to call up the map browser, showing that address.

Figure 6 schematicall illustrates the business model transfbrmation and how' SpinVox positions itself as the intermediary between the customer and the search-engine based advertising aggregator, such as Google.

Figure 7 shows the end-to-end experience from when a calling party leaves a message and to how-the recipient (called party) views the message.

Figure 8 shows a photograph taken on a camera phone.

Figure 9 show's the Speak a Comment option from the Options menu, which may he used to annotate the photograph in Figure 8.

Figure 10 shows MCI1 with SpinVox Voicemail to Text also deployed.

Figure 11 shows how various conventional messaging products (voicemail, email, SMS, 1M and voice) are distributed on a Time v Dialogue axes.

Figure 12 shows how various Spin\'ox products alter the landscape of Figure 11.

Figure 13 shows an example of a deployment of Spoken email and Spoken SMS/MMS with a mobile sen-ice provider -SIP telephony connectivity.

Figure 14 shows an example of a dep1o ment of Spoken email with a French mobile service provider -standard telephony and synchronised data.

Figure 15 shows the apical user experience of speaking a message from within the Text Messaging or Email Application.

Figure 16 shows a typical user experience of speaking a message from within the Address Book.

Figure 17 shows the typical user experience of speaking a message using the Call Log.

Figure 18 shows a typical user experience of speaking a message from within Speak a Message application.

Figure 19 shows a typical user experience for Speaking a Blog.

Figure 20 shows a typical user experience of speaking a reph in a Mobile ThE client.

Figure 21 shows the 3 clicks' user experience.

Figure 22 shows the Fire & Forget' system employed by Speak a Message.

Figure 23 shows the Fast Address List -showing recent contacts that have Called, been Called, Texted (SNIS or NIMS) or Emailed (or any other messaging/communications process used).

Figure 24 shows screen shots which demonstrate the ideal user experience: the Fast Address list of recent contacts (people that have called, been called, texted, emailed etc is selected, the one individual (David \X'ood) is selected to automatically initiate a connection to the SpinVox voice conversion system so that the user can speak a message.

Figure 25 shows the end-to-end experience from the A & B party perspective.

Figure 26 shows the typical behaviour of the Speak-a-Message application in the home screen of the phone.

Figure 27 shows the application being accessed using a short cut displayed as the Spin Vox logo, after pressing the Multimedia Key' on a Nokia N95.

Figure 28 shows the Fast Address list, which on an N95 device is limited to the last 5 people which you spoke to, emailed, sent or received a text from or spoke a message to.

Figure 29 shows that am contact can have a message spoken to them b moving from the Recent' view to the Contacts' view.

Figure 30 shows that if a contact is selected in the Contacts' view that contains more than one phone number, then both numbers are shown and the user is given a choice of using either.

Figure 31 shows when the customer connects to the Spin Vox service the name of the contact being sent the text is displayed.

Figure 32 shows the User Experience schematicalls for the Speak-a-Text product.

Figure 33 shows the typical behaviour of an email centric device prior to the SpinVox plug-in software being installed.

Figure 34 shows how the Inbox looks after the SpinVox plug-in has been installed.

Figure 35 shows how a SpinVox voicemail message will look once the recipient has opened it.

Figure 36 shows what happens when a customer clicks on the real name that has now'

been put into the "From:" field.

Figure 37 shows what happens when a customer clicks on the real name that has now been put into the message text in the section which starts You received a new voicemail from'.

Figure 38 shows an example of a QuickLink, which has been inserted at the bottom of the converted email message.

Figure 39 shows how additional functionality has been added to the deice with the inclusion of new menu items.

Figure 40 shows how SpinVox unities various communications types and channels.

Figure 41 shows the end-to-end experience of Spin\'ox Voice SMS service.

DETAILED DESCRIPTION

Spin\'ox has developed a simpler more natural user interface for messaging -Voice.

Messaging and communications in general is, in the prior art, symmetric -namely you either exchange text (SMS, email, Fax, letter, etc...) or you talk to another person. Bs converting speaker independent free-form speech SpinVox transforms and enables asymmetric communication which now changes the rules of the game. It enables full voice messaging and is creating the \oice_toScreenTM messaging categ.r that simpl enables existing products/sen-ices and markets/users with a spoken input and a text output from any phone or speech input device to any screen.

In doing so, it leverages the increasing asymmetric ability of phones: phone screens for reading (which today are becoming good text displa devices) and human speech, which is one of the most natural forms of communicating and virtuall all humans on the planet can use, and is after all what phones are best at. Or put the other was', phones are poor text input devices, but great at voice input and decent at text display.

This transformation also enables new, deeper sen-ices, such as unifying all sources of voice messages into easily accessible text on screen and solves man)' of the complex system issues of getting two disparate worlds to appear to he one (telephony and email/web pages). But excitingh, h) having voice messages of any source as text, they can be indexed and intelligent search results embedded into the message. The value is that the majority of searches are triggered by information communicated between parties, and voicemail and voice messages have a high percentage of such data points. This solves many of the limitations of phone key-based or pen based input methods to do search in traditional forms via search engines and several stages to find the result. And because this is sen-er-side, it will become intelligent to your context -Intelligent-to-meTM.

This Detailed Description will describe a wide variety of Spin\'ox innovations and product features, in addition to the specific invention defined by the Claims.

Key Elements of Spin Vox products includes the following.

* X_LinksTM which enables communities to effbrtlesslv share usc of Spin\Tox allows non-Spin\Tox subscribers/users to reply via speaking a text allows users to speak text across products, not just within * XLinksTM implicit address hook makes links seamless * Network based spoken text messaging * Call Return via spoken text messaging * Speaking an SMS/MMS or email * Speaking an Instant Message * Mobile blogging * Mobile photo messaging * Push to message' -application for push to talk * AU services/products are hased on fire and firget' principle * They all turn existing voicemail into a full two-way push messaging service and off of existing technology, create new products and markets * They use the fact that we trust people in our communities to message us, rather than call us: 80 /n of messages come from a limited number of people U Voicemail -8 people U SMS -4-6 people U instant Messaging -2-3 people * Missed Call Messenger (No Answer -Speak-a-TextTM) -On-net + Off-net hehaiour, V use of X-I.inks, and new revenue sources as an evolution and deployment with carrier in Spain * Unified Communications for Voice Messaging -dlsa)nnected sen-ices, unified by conversion, distributed to any screen creates a new mode of multi-point voice messaging * S-Links detailing embedded nature of context based smart links within text messages converted from voice messages -a new approach to mobile search and Advertising Search markets * Intelligent-to-MeTM embedded intelligent passive search abilit) driven out of many-to-one communications, as opposed to one-to-one pull methods typically found in search today * Spoken community messaging via web and SMS -Twitter, Facehook, MvSace, etc...

* \Toice blastslM: concept of being able to speak a mcssage and have it instanth sent as text in any form to your web-based community as a broadcast message directis' from you.

The following sections will consider these (and other features) in more detail: Section A: X-Links Section B: S-Links Section C: Web 2.0 Section D: Missed Call Messenger Section E: An overview of the main Spin Vox products Appendix 1: Speak-a-Text Appendix II: \Toicemail to email Appendix 111: Viral/link marketing campaigns Appendix IV: Unified Communications Appendix V: Voicc SMS Appendix Vi: Acronyms SECTION A: XLinksTM This extends the original feature SpinVox deployed within Voicemai1_toTextTM whereby a link in the message enabled the recipient to directly access and hear that message -QuickLinksTM (see GB2420942B, the contents of which are incorporated by reference).

X-Links allows any recipient of an' message converted by Spin\Tox to speak the sender a reply. By selecting the link, the user is connect directly to a Spin\'ox conversion service, prompted to speak their message and it is then sent directly back to the person they received the original message from.

X-Links are placed in every message, so two parties can endlessly communicate via spoken messages sent as text wheneer they' like.

For example, a user might receive a voicemail message as text and it wiil now contain an Link so that they simply select it and they can speak the person who originally left them a voicemail, a text reply. Likewise, if you're the recipient of a Spoken text message, y-ou will be offered an X-Link to speak them a reply by text.

For example, Figure 1 shows a Spoken Text message from Dan Mobile'. It includes the X-Link 84004pl23 in the message <To speak a text reply call 84004p123> X-Link works across different messaging products, so if fbr example you receive a spoken message as SMS with an X-Link in it, y'ou could be speaking the person a reply by email, or visa versa.

Technology A link is formed by a service number and a unique identifier shown as: <service number> + <unique identifier> e.g. Links in the UK could look like: (12O79652000p 123 or 84004p 123 Service number -phone number which acts as access point to the conversion system, e.g. o full standard phone number (e.g. a DDI such as 02079652000) o voice sh,rt C)dC (e.g. 84004) o \ )!P or network number if used within IP based telecommunication or messaging * Unique identifier -identities who the sender is for the reply, e.g. o Over-dial digits used in standard telephony U Often uses a p' (pause) or equivalent network symbol when using DTMF driven sstems U May use a special digit to further denote service type -e.g. or a digit 1' o Can be either the full phone number (e.g. MSISDN), or a code that links this on the system U 84004pl23 or U 84004pO78121O1 742 In next generation svsl-ems, the link would be an embedded link to click to call' as found in \VAP pages and used extensively by operators such as Hurchison 3G in the UK. The benefit is that these links would he simple words, rather than phone numbers, so that it would read "Speak Text Reply" rather than "Speak Text Reply: 84004pl 23".

X-List: Implicit Address Book In the above examples, the unique identifier is shown as a 3-digit code (e.g. 123). The length is arbitrary and becomes the full phone number if it reaches the same number of digits as the mapped phone number (e.g. pl23456789l() is no longer a useful code in the UK as all phone numbers are 11 digits).

X-Links rely on the service creating a list of people who you've received a niessage from and want to rep]) to. The reason this works as a limited list is because the number of people who call you 80% of the time is on average just 10-12.

Example

1. David speaks Jim a text message. Jim is not a SpinVox subscriber.

2. Jim receies the text with an X-Link to speak David a reph. He clicks on it.

3. When Jim's call connects, the system uses his CLI to identify who has messaged him -David's number is one of these.

4. The unique identifier then tells the system which of these SpinVox people spoke Jim a message. In this case it finds David's CLI MSISDN 5. Jim speaks his text message.

6. David now receives a spoken text message from Jim with an X-Link in so that he can reph.

7. The loop goes on ad infinitum.

Ke elements of this implicit X-Link address book are: * A list of MS1SDNs (or equivalent phone numbers) is built up of a]] callers who left a message for each Spin Vox user on the X-Link service.

* This list is unique to each Spin\Tox user, identified hy their MSISDN (or equivalent phone number). Each user has their own X-Link list keyed from their MSISDN.

* Even new person that leaves a message tbr the Spin\Tox user has a new entn-created in this list, and a corresponding unique identifier allocated.

* The list grows to the allowable limit, which with just 3 numbers is 1000. It can be Ic niger, or shorter depending on the needs of the user and service provider.

* Each time the SpinVox user calls in using the X-Link, the s stem knows which list is theirs (by use of their MSISDN), and can then decode the unique identifier digits into the person's MSISDN the want to speak a message to.

* SpinVox users can save these X-Links straight into their address books for future reference and know that calling it will always allow them to speak the associated person a text message.

* Optional: the system recycles the users' X-Link]isr SO that as SOOfl as it's full, it goes back and replaces the least used entry with the new one. This keeps the unique identifier short (e.g. 3 numbers) and uses the basis that you're most likely to use the X-Link in the message you recentl received to reply and therefhre C( )rrectly connect to that person. It is possible to dig out a very old message with an X-Link that fl( )W points at a new person.

Note: Users of this service don't have to he Spin Vox subscribers. They only have to have received a message with an X-Link in to start benefiting from this.

X-List mechanism Unique X-lists are created for each person (A-F in this example) and list elements generated by using the caller/speaker's CLI and an associated unique identifier (UID). in this case, the UID is +3-dits' List owners ListeesA B C D E F A -*001 *079 *022 *333 *fflfl B *003 -*012 *025 *334 *099 C *011 *007 -*1)03 *351 *015 D *002 *011 *1)01 -*002 *101 E *139 *099 *006 *011 -*069 F *001 *010 *589 *287 *006 - 2() The address book is built up simply by creating a list for each person who is either a recipient or a sender of a Spin\Jox message. The list contains links (shown as *xyz which map to the actual phone number (CLI/MSISDN). Anytime a new person messages another via this system, they are added to their list. So both SpinVux subscribers and non-subscribers both have lists created for them.

For example: A's unique address book is shown by thc vertical list under A. A was called b F first (*001), D second (*002), B third (*003), then after 7 others, b C (*011) and by E 139th (*139).

So if A uses the X-Link at the end of a message they receive (e.g. Phone_no.i)02), the sstem knows that it's A calling from their network CU (1'sISISDN), and that the' want number 2 in the list to speak a text to. The s stem has keyed As list number 2 to D's phone number.

X-Lists are built-up through the calling/messaging patterns between communities of people.

Bi-directional messaging Using the above list example, here's bow A and B are linked in each other's Address List: 1. A is a Spin\7ox user. B is not.

2. B called and left A a voice message which was converted and sent to A as text.

a. When B's first left A a message, B was added to the list and happened to be the third, hence *flQ3 is given to B's number.

3. A now speaks B a text reply using the message X-Link.

a. This is the first time B has had a spoken message sent to them via Spin Vox, so B's list is now created and A is added as the first entry (*001) in B's list 4. The system send A's message to B with an X-Link Ull) as *Qffl 5. B receives the message and by using the X-Link calls the SpinVox service, is identified as B CLI/MSISDN) and presents *001 as the destination -namely A. 6. A now receives a message back with B's LID (*003) and the loop can continue ad infinitum.

Saving X-Links: reliable for local address book use Because the X-Link service reliahi) links people to each other, users can safel save the X-Link in say their mobile phone's address/contact list for future use. So, A in this example could reliably save 84OO4p'OO3 in their phone's address list as the entry for speaking B a text message. Likewise, in this example, B can also save an entry for speaking A a text message as S4OO4pOOl.

This method allows communities to reliably connect using X-Links. On average, we receive 80% of our calls from just 12 people, 80% of our voicemails from just 8 people, 80% of our SMS messages from just 6 people and 8(1% of our Instant Messages from just 4 people. C)

Naturally, C-Lists have a finite limit, so in the example shown, 3 digit unique identifiers limits to 1000 other people. Changing the number of digits in the unique identifier changes the possible number of people you can be connected to through vur X-List.

Note: 84004 is an example service number, but could be any other number/address depending on network and numbering plans.

X-List: Any Address or Idcntifier Although the method of X-Lists is explained using phone numhers, in fact any type of address can be used -email, IP address, Instant Message, VoIP no., etc... -as long as it is a reliable identifier with which to address a message. So X-Lists can be used for any messaging community, not just phone number based communities.

This further means that a user may choose to receive messages as email, hut always speak messages back as SMS.

X-Link: Launch messaging application The concept of the X-Link reaches to another level when applied with any communication application. The link is not only a phone number or address, but also a link to launch the relevant application.

For example, the X-Link sent inside a standard spoken SMS or voicemail-to-text could he a link to call them hack via a VoIP application rather than standard voice call.

The link might just show: VoIP Call back? Clicking on this (or selecting this inside the applications menu, tvpicall use detail') would: 1. Launch the phone's VoIP application -e.g. Skype 2. Place the call automaticall back to the caller, using the VoIP application.

3. If there was no VoW application, it might actually connect to the \1olP provider's web sen'ice and either download the application, or request a call back' so that they could connect via this method.

Note: this could be a en powerful way of acquiring subscribers to a \olP service as each link is a call to connect and/or download their client and use their sen-ice.

X-Link as public QuickLink QuickLinks are used for SpinVox subscribers to be able to dial in and listen (retrieve) to an) voice message by simply entering the QuickLink digits (e.g. Al2 found at the bottom of each message.

Using X-Link's address book, anbodv who receives a spoken message as text can no call in and listen to the original voice message that was left for them, as shown in Figure 2 ("To listen to the original call 84007P123").

For example:

* You aren't a Spin Vox subscriber, but receive a spoken message from a friend * Either the message is ambiguous, or it wasn't converted, hut you've a public QuickLink at the end of the message (see picture below) to call in and listen to it.

* You select the link (or dial the full number) and the original voice message is played back for ou.

Technical Because the X-Link service has a list of numbers of both senders and recipients, it is able to match any caller's Cli (MSISDN) to a history list of numbers that are linked. Then, the unique identifier allows the service to match which exact CLI from this list the message youwant to hear relates to.

QuickLinks and X-Links requests to the Spin\'ox sen-ice can be distinguished by: * Different characters/commands being inserted into the start of the Unique identifier to denote which type of call this is o Using an o Always starting with a I o Use of the p' command to mark the start of unique identifier * Using different service numbers o Calls to speak a message by text are on one sen ice number range (e.g. 84004, 84007, 84009, etc...) o Calls to retrieve/listen to a message received as text are on a separate sen-ice number range (e.g. 94004, 94007, 94009) Using the same numher, hut then prompting the caller/speaker to select which option they want.

o E.g.: "Please select 1 if you want to hear this message, or 2 to speak the sender a reply" Dedicated service numbers allow users to automacally retrieve, rather than call a number and enter a unique identifier manually. They are simply selecting a number to call from within the message.

X-Link across messaging products The aboe show how X-Link-s can be used within a given messaging product. However, if a user sets their preference, SpinVox or the sen-ice provider can actually send the converted message back in any message format/application the user desires.

For example

* James is not registered with SpinVox (or SpinVox sen-ice provider). He receives a spoken SMS from Adam who is registered with SpinVox.

* James receives a spoken SMS from Adam.

* James uses the X-Link to reply and speaks his message.

* Spin Vox know that in fact Adam has opted to have spoken messages sent to him b email, not SMS. So, the s stem converts James' message into text and emails this to Adam.

* Adam sees James' reph in email, and uses the X-Link to speak him an SMS back.

This could work wit-b any text based messaging application -SMS, MMS, instant Messaging, email, etc...

X-Links User Experience As noted above, X-Links is a new product line for SpinVox designed to increase the value of every converted voice message sent by a SpinVox product. It achieves this through the inclusion of a billable reply path, which allows anyone to speak a reply to a message they It) receive.

For the first time, a spoken reply path will be available, creating opportunities. In addition to offering an enhanced subscriber experience, this unique integration provides a means of monetizing every message sent to or from a SpinVox customer. X-Links will provide a huge, sustainable incremental revenue for Carriers.

The solution will primarily consist of: * Si\IS, MMS or email message with a highlighted reply path; either a phone number or 21) HTML style link.

* New capability to identif the calling parts and link their number with a unique number that allows a spoken * integration with a premium billing solution to monetize every message sent.

The following sections are covered in this document: General requirements -key features and benefits of the product User experience -customer experience for calling and called part-v Product requirements -end to end lifecycle experience General Requirements The product must meet the fiillowing criteria: End User Benefit Provide an ultra fast reply path, for situations where the customer can't or doesn't anr to stop hat the' are doing or does not have the dexterit or technical savv to use a ke board.

Ease of Use Must be obvious to user that the highlighted word or number can be dicked'. Should be simple wa to activate and have a number automatically dialed. Ideally, onl one click would he required to initiate the call to the I\TR.

Simple, Fast, Intuitive It must be obvious that clicking on the highlighted link lll. Assumption is that MMS support is available on majority of targeted devices and that these devices support User Experience Figure 3 illustrates a typical sequence of messages and the recurring use of the Speak a Reply' X-Link.

Demo Definitions In order to rapidly demonstrate the capabilities and potential of X-Links, there will be 2 separate demo scenarios and milestones: S1IS based Demo rhe purpose of the canned demo is to show X-Links proof of concept.

SMS / /MMS Field Trial

The purpose of the field trial version will be to demonstrate X-Links capabilities to customers, partner and key industry influencers. The field trial is a working version of the product.

1. User interaction considerations Although the recipient of an X-Iinks message ma be reading the message as an email on a PC or a high-end smartphonc. the expectation is that most users will he using a more typical mobile phone. Therefore, interactions with an X-I.inks message should he designed with that user in mind. Access to the data that the user is requesting b clicking on a link should be immediate and require the smallest number of clicks to reach the desired information.

Calling Party The experience for the calling party would be consistent with current Spin\Tox voice to text products. Callers would hear an IVR greeting to leave a message with prompts that incorporate Spin\'ox branding.

Called Party The called party would receive either an SIMS message, MMS message or email of the converted voice message. When the message is displayed, a link at the bottom of the message would he highlighted and give the option to reply by clicking on a numher or link.

One they have initiated the reply, callers would hear an I\TR greeting to leave a message with prompts that incorporate SpinVox branding.

2. Implementation considerations There will be 2 types of X-Links service offerings -X-Links for SMS and X-Links for MMS and email.

SMS

While SMS has the broadest reach in terms of subscribers and device support, there are limitations on the number of available characters in each message. This limit impacts the number and type of link that can he incorporated in an SMS message. A second consideration is thc ability for the device to automatically dial a phone number. If the link conforms to a common number +44207772222 some but not all de ices will allow the link to bc clicked and make a phone call.

The approach &r SMS will be to include a phrase at the end of the message such as To Speak a reply call <+4420777222>'.

MMS and Email MMS and email messas will provide a much richer X-Links experience for the end user in terms of message display and usability. Although usage is not as widespread when compared to SMS, MMS usage has recently experienced significant market growth.

For MMS, the X-Links message would Contain a link at the end of the message which states: Click here to speak a reph' -spoken through SpinVox \X'ben the link is selected a call to a number (bidden from the end-user) will be made. This could be a geographic or non-geographic fixed line number or Voice shortcode.

X-Links Product Requirements 1. Service Level Requirement The calling pam-should nor have to sign up with SpinVox or the Carrier to use this service.

Customers can opt-out of the service by caffing customer care or b sending an SMS message to a shortcode.

]he service should meet the same availability requirement as the prevailing Spin\'ox service.

On initial launch the service must support the following languages: UK English US English Canadian English Canadian French German French Spanish Australian English South African English The SpinVox SMS server must hold a protile for the Carrier DD1 to determine whether to deliver the message to the Carrier SMSC or deliver to an aregator to send to the customer in that profile, there must be a reference to the injection and ejection validation rules for that carrier 2. IVR Once connected to the SpinVox I\'R, the customer simpl\ needs to record their message then hang up in order for the message to be sent. There will be no option to review the message, nor will there be any option to receive a copy of the message.

Requirement The voice talent used to record any new voice prompts must be the same as currently used on the Spin\'ox 1\'R platform.

IVR prompts must be recorded in all languages supported by the SpinVox IVR The destination party will be automatically known and flO additional number entry is required.

The duration for a spoken reply will be set to 31) seconds The option to re-record the message will be available by pressing * (the star key) at any time during recording.

The first (3) three times a customer initiates a call to reply by using an X-Link they will be prompted to confirm the charge for using the service.

Subsequent times a customer connects to the IVR, they will not be prompted to contirm the cost.

X-Link Confirm prompt: (pla ed first 3 times) Welcome. This service cost 25 pence per message. Please Press I to continue." Pressing 1 will confirm the action and the customer will then bear the following prompt X-Link normal prompt: "Speak our rep1 Now!" Once the message has been deposited a billing trigger will be activated and if appropriate the customer will he charged for the message.

3. Delivery to recipient

D

\X hen a voice message is successfu1l converted to text, an SMS, MMS, will be sent to the intended recipient.

Requirement The text message must be sent as from the original caller's phone number (i.e. the A partv.

The body of the message must use the appropriate SpinVox SMS boilerplate, as defined in Message Classification.

This includes the definition of the branded signature and the use of quotation marks.

\(lIi. DIFFER I)EPENDINC; ON DELiVERY METHOD The delivered message must automatically contain an X-Link.. linking the sender (uniquely) with the recipient.

I () 4. X-Link There are no pre-requisites to using an X-Link. It is not necessary to have a SpinVox account, in fact, many recipients will not know who or what Spin Vox are, until they click on the link.

Requirement It must he possible to link two people's numbers uniquels using a single geographic or non-geographic number that-can be dialled direct-h from ans-handset.

5. Reporting Requirement It must be possible to report on all messages on this service.

Further X-Link Concepts * Original sender has a setting which can specify that the voice-to-text reply should go to more than one destination eg. to SMS and to distinct e-mail address (office), and to a further e-mail address (home). This setting can also he altered on a message-by-message basis. This setting could be handy as it could lead to an automatic "backup" of SMS messages received on a mobile phone to an e-mail account at the workplace, or to support staff at the workplace who can provide cover flit a busy individual.

* Each user has their own list of X-links, each N-link being associated with the unique MSISDN of a person that has sent a text to that user. Individual N-I inks can be deleted, if desired.

* Include option tin spoken text message to be saved to an intermediary, for sending on later at a specific time. Eg. in union-dominated environments, might not want to send such a message outside of working hours. Hence select it to be sent at exactly 9 am, which could be the exact start time of the working day. Option could be called "Speak delayed text message", with the future time (and possibly date) at which it is to be sent inputted using the number keys.

* insertion of X-Link in the messa is dc-selectable using an option eg. if the recipient speaks with a strong accent or dialect that cannot be converted to text reliably using existing tech nologv, and s ou do not want to waste time trying to decipher any such text message.

* When text message is sent to a non-Spinvox customer, include a link so that the non-Spinvox customer can click it to sign up to Spinvox eg. using an internet page, or by speaking to an operator.

* K-Link in a blog, or in a closed user group.

SECTION B: Content Based Links -SLinksTM Spoken Links (or smart links) One of the most useful features of receiving a spoken message as text is that if the speaker gave specific data relating to a place, time, address, name or other keywords it's in text and as the user, you can quickly refer to that at any time when \ ou next need it.

Parsing of phone numbers, email addresses and websites into hvperlinked objects is common in messaging applications (SMS, MMS, email, IM, etc...). In spoken messages, users often give reference to locations that aren't as obviously structured, but equally important to the recipient.

The concept of S-Links is to parse the text of a spoken message and use keywords to generate a set of useful, related links. The relevant links are inserted in the message and would take the user to a website or web resource that expands on the content linked.

For example, in Figure 4, message sender Zac Sandier leaves a voice mall which has been automatically converted to text using the SpinVox voice conversion system (see \X'O 2004/095821 and W() 2007/09 1096, the contents of which are incorporated by reference).

At the footer of the converted message are two separate links, one for directions and another for the drink cava'. Clicking on the Directions' link opens a map browser on the phone (in this Figure, a PC hased Google Maps image is shown for clarity), showing the address mentioned in the voice message, now converted to SMS.

In another variant, shown in Figure 5, the links are incorporated into the message, with the address 20E & 9h Sf in the body of the message being selectable to call up the map browser, showing that address. Likewise, the word cava' in the hody of the message is selectable, to call up a browser with places where this wine can he bought and which (optionalk) are near the parsed destination address. in this example, the user can be presented with options for buying a bottle of Cava that are on the planned route, rather than anywhere in their locality, optimising the relevance and therefore value (if the implicit search result. Further more, these can be added to the map presented to show where on route these items are.

So in this case, the message contained two clear opportunities from which to create a relevant link: an address and a product type.

l1he ss stem first looks for ke words or phrases that contain likel3 words for links, it then takes these and automatically looks up likely resources for each and then presents what it estimates is the best result.

The value of this is that relevant links are inserted which the user will accept as the are useful, relevant and generally unobtrusive. This is a very valuable way of marketing below the line' using User Generated Content to find and create valuable links for the recipient.

So S-Links increases the value of converted voice messages through the inclusion of relevant contextual elements. B incorporating links to external information, such as maps, directions, advertisements or offers, S-Link-enabled messages can deliver an enhanced experience -evolving from the current explicit search paradigm to the significantly more valuable implicit search, i.e. something that was actually said in conversation.

For the first time, the massive volume of P2P messaging in the mobile sector will be harmonized with search. in addition to offering an enhanced subscriber experience, this unique integration provides a highly targeted platform for mobile monetization. S-Links will provide a huge, sustainable incremental revenue for Carriers and service providers.

Technical The way to create this links is by processing the converted text first, finding relevant key words, creating the links then adding them into the message, before sending to the recipient.

Spin Vox's \oice Message Conversion System post-processes all messages and is capable of making a call to a routine to parse text and create any relevant S-Links. \MCS is defined in more detail in \V02007/091 096, the contents of which are incorporated b reference.

Alternatively, the message can be first sent to an intermediary who can perfbrm this link creation stage.

Link types The links can either he the full LTRL where the application reading the text is unable to create fully aliased hvperlinks, or just the hvperlink itself from the key word. E.g.

U RL only: http://maps.google.com/ Hperlinkcd: 20E 90th1 St If the links are fully hyperlinked, they can be placed within the text of the message: From: Zac Sandier Hi. The party's on at 20 east 9th street at 9pm. Don't forget to buy a bottle of can for Mandy's Spanish silver bullet game. See va.

2(1 Implicit Search with Intelligent-to-MeTM The system can he enhanced to provide truly smart links that are relevant not just to the message, but the user and their habits, history of use and preferences. The concept is that the S-Links service learns and uses other resources to make any links presented Intelligent to the specific user, or "Intelligent-to-MeTM". Issue

The issue of mobile search is toda predicated on the fact that users will behave the same way and have the same needs when they're mobile as when they're at their PC. Three basic issues exist when translating search from PC to mobile: 1. \\ hen people get up and go somewhere, they nearly always know where they're going, wh and key information about that trip, even if local, so their requirements for search are normally contextually constrained to the task at hand.

2. In the event that people want to search whilst mobile, it's well known that today's solutions require input on a small alpha-numeric keypad or even a touch screen that is not easy and requires the user to typically stop somewhere to perform the search.

3. Even if the person does achieve input of a search term, they still need to click through several pages and scroll to find the relevant outcome. This can equate to some 30-key press sequences including switching to their browser, typing in the search string or quer (often more than once to find the right one), scrolling and then selecting pages/links to view.

Key in sight The source of mans of our searches is actuall driven by messages we receive from others, such as names of something we didn't know ahout, locations, brands, etc... On a PC, these sources are wide as the can come from more than just our community or colleagues. But fortunately, large keyboards, rich screens and connectivity make our task of explicitly transposing the idea to some key words, invoking our browser and typing in a couple of search queries and then browsing through many options, an acceptable task. This is Explicit' search, because the user has to consciously think about what they need to find, how and then filter down results to their target.

Messages we receive from our community or voice messages contain a high proportion of kes task information for our daily lives -e.g. a time for a meeting, an address, items to bring/buy, things to do/see and even reminders.

SpinVox research into converted voicemail-to-text results shows a surprisingly high number of appointments; locations, tasks and items are received bs voice messages, some 25%. And people use this to navigate and successfully work through their day.

What this means is that a significant part of anyone's trigger to undertake search comes from voice messages. Coupled with the fact that people often rely on text messages (SMS, MMS, email, etc...) once they're on their task or p, to look up details en-route (e.g. check address, time or name of items to get, the solution becomes apparent.

By linking ke words in any message the user has directi to the destination (search answer), the user's life becomes much simpler and effective. No need to explicitly think about searching and which way to do it, just click on tile link and he taken straight to an answer.

All the middle steps that explicit search relies on are removed. Used the highlighted word or reference in tile message and get straight to the answer: Implicit Search.

Implicit Search By first converting all voice messages into text, SpinVox has all the key words that could be used to perfiirm an intelligent search. Further, it also has the ability to build up a histors oF user messages, who they were from, which source and the response to such links to continually optimise how they're presented in future and therefore fit with what the recipient/user acrualls needs. So the s stem learns what a user is likely to be searching for through its entire history of messages sent and received -not just the specific search.

Keys to optimising implied search include: o Calling/sending parts (A-parts) O Key words used and their relative meanings O Message type -voicemail, SMS, email, social network, broadcast/blast, etc...

O 14 cation of both called party (B-party) and calling/sending party (A-parts) 0 Location based senices (LBS) to improve the context of key words (e.g. addresses, or locations for certain items en-route) O 1-listory of clicks and actions of recipient O 1-listory of response to messages to better know what was say ambiguous or likely to he done next in a typical sequence herween these two parties 0 Time of day, date and place that actions were taken to optimise what things are rele ant vs. not O Preferences for brand, place, method or mode based on purchase history or message history and link usage \TMCS related patent filing \VO 2007/091096 describes the system used to implement the indexing of kenvords/rerms needed to generate a full index that can form the basis of an advertising supported search system -i.e. that is sufficiently reliable, robust and scalable to provide advertisers that hid for a particular index term to he reliahl and appropriately referenced or linked to in a message when that index term appears.

By looking at all a user's messages, whether they received them or sent them, a significant amount of personal context can be derived to learn and thereby better provide a user with intelligent options or links to delivering what they want. This constant learning helps provide a network-based service that is with you and is: intelligentto-MeTt.

Many-to-one widens scope and relevance This also changes traditional search which is in essence a one-to-one relationship, namel that as a user it is onl my input to say Google or Yahoo! that generates results and the only thing they know ahout me is my IP address, which changes as I move around. With S-Links, search input is widened to become from many-to-one, it is also reliably for one user, as your phone number rarely changes. Therefore, the search is far more relevant to the user as it's using a fuller set of key words that a user depends on, rather than the few that are rememhered or transposed from one application to another. It can also he specific to the demographic of the user, because that information is either explicitly provided to the system by the user, or can be inferred by the system by looking (with the consent of the user) at the content and profile of messages.

We believe that a significant amount of mobile search will come from implicit search options embedded in messages and probably be larger than traditional explicit forms of search in mobile.

Permission based One of the ke issues that this idea solves is that in mobile, there's a large resistance to any advertising that is explicit or cIearl what is know as above the line' and effectively occupies parts of the user's screen. ln mobile, screen real estate is at a premium.

By embedding the links as the words, it will immediately remove this problem and the service and any adverts associated with it will onl appear when the user actively selects they want to use this option. This will likely transform user experience and acceptance of commercial services and advertising in mobile.

Gesture based Search Because the system is providing single click answers to t pica! search task, the user only needs undertake the simplest of actions, a click which is a common gesture and which takes the user straight to their destination, rather than work their keyboard and navigation keys through some 20-30 or more inputs (ke strokes and clicks) to achieve the same result. It's well known that every step loses some 30% of users and this is even more accentuated in mobile. S-Links minimise this to just 1 step.

Location Based Search A simple feature is the opth n to not oniy display the Address someone has given ou, but to then use intelligence in the network (typically Location Based Services) to give you: o The actual route to take to get you from wherever you are to the address given in the message 2() U If you've other items to visit or collect (bus) on the wa), the mapping function can now populate sour route with options to find these items, rather than just in a uni-directional radius around you U Use your history to know which places, routes and features ou prefer to improve the relevance of the results presented 0 Use A-parts' !ocation to also optimise local references and instructions or information to improve relevance of results presented -e.g. meet me at m Starhucks' would he able to automatically map the nearest to the caller's phone that made the call.

Business Model Transformer Using implied links will drive mobile users to online resources, many of which are paid for by online adverts that appear. Implicit search will do several key things for players in the va]ue-chains that provide both the mobile service and web-based searches: o Increase traditional Advertising Search (online advertisin revenues such as those derived b Google, Yahoo!, MSN, etc...

O Increase mobile revenues from data traffic and data products purchased O Increase online transactions from mobile 0 Provide sources of revenue for the networks to subsidise the SpinVox sen-ice that enables this capacity. Users may no longer have to pay, hut instead get a higher ciualitv service instead.

O Drive use of new messaging products or modes, such as MMS and WAP, both of which are under-utilised but very capable multi-media resources that networks are keen to sec a return on.

Business 3usiness Rationale Upside SpinVox Incremental Reinforce Spin\'ox position as ncome from an innovator and as the market share of click eader evenue arrier Incremental)rive new sales of data plans ncome from nd uplift take-rate of data/WAP:ompatible handsets session Jearch ncremental Monetize SMS -not previously ngine ncome from,ossible due to routing and :lick-through;olume Figure 6 schematically illustrates the business model transformation and how Spin\'ox positions itself as the intermediar between the customer and the search-engine based advertising aregator, such as Google.

Single Search Result Premiums Due to the nature of the single link and its design to take you straight to the right outcome (destination), this service will further heighten the value of these search results to advertisers and commercial service providers as there will onl be one or a couple other search results shown, rather than the pages of results provided in PC based explicit search which tends to dilute the value of the slot bought.

This will offset the industry's concerns about mobile advertising in general being less valuable as web content and resources are generally less available to mobile users.

Summary of S-Link features

Now voice is in text, it can he massively indexed * Voicemail is the 2nd largest form of mail after email * Voice messages have rich personal context -key task information * Search can be er' targeted and relevant * Permission based: Intelligent-to-MeTM * Smart-links: learns from history and use from all messages to me from my communities, not just my individual searches (e.g. Google * Implicit vs. Explicit search * Current scarch is PC-centric -Explicit search * Requires user to think of search term, switch apps, type in via fiddly keypad, surf to iind results = 20-30 click exercise (30% loss at even step) * Naturally limited market -in mobile! * S-Links provide result in context (message) -Implicit Search * Voicemail (and SMS) contains over 70% of key info for day's tasks -addresses, times, names, sequences, products, ideas, etc... -i.e.keywords that drive t-pical search * Take you straight to destination, not the long ride -1 gesture = result! * Implicit recurring behaviour -voice messages are received every day * Link is discreeth in message and takes you straight to the result * Links are smart -the can give local context to ensure results shown is right for the user first time -e.g. providing local options for maps, products, places and services.

* Implicit navigation -it knows where you are and where ou are going. it uses network LBS (location based services) to find you and then map set-vices to provide you with a route to where you are going. It dynamically updates depending on where and when you clink on a link.

* 1 click simple to reach destination -the link is persistent and is there in the message after you close and then re-open the message many days alter; there is no need to re-type anything.

* Preferences enable different commercial resources to be displayed * Drives much higher value single search result.

S-Links User Experience This document details the user experience and highlights specific requirements and considerations for Spin\7ox S-Links. The solution will primarily consist of: 1. SMS, MMS or email message with highlighted keywords 2. New capability to identify and highlight kenvords in voice to text processing 3. Integration with 3(1 party ad and content servers to support business model The following sections are covered in this document 1. General requirements -kes features and benefits of the product 2. User experience -customer experience for calling and called party 3. Product requirements -end to end lifecvcle experience General Requirements The product must meet the following criteria: End User Benefit Highlighted words must be relevant to message content and have perceived value for the user. Consensus that 2 or 3 links per message is the maximum threshold.

Ease of Use Must be obvious to user that highlighted words can be clicked'. Should be simple way to activate links to render associated results. ldeallv, only one click would be required to retrieve and display the requested information.

Simple, Fast Display Results Clicking on highlighted words should require the smallest possible number of additional clicks to displas results. Assumption is that \X'AP support is available on majority of targeted devices Performance Turn around time (FAT) for message delivery should not be impacted. The message TAT should remain within the current SLA parameters.

Figure 7 shows the end-to-end experience from when a calling parts' leaves a message and to how the recipient (called party) views the message. The message content, display' and interaction will differ depending on message sent and display type.

1. Calling party initiates call to a called party. Alternatively the caller could be replying to an email, creating a memo, preparing a blog or social network posting or responding to an instant message. Calling party' is prompted to speak their message using normal product IVR prompts.

2. The voice message is recorded in the audio capture svsrrnl within a carrier, service operator or Spin Vox. The \X'A\' file is then sent to VMCS for conversion.

3. Spin Vox \MCS converts voice WAV file into text message.

4. Spin Vox interrogates message to determine if any relevant kcvtvords are present.

5. SpinVox highlights relevant ke words and inserts one or more of the flullowing associated links: a. Ad click b. Map c. Ad tag in message d. Ad tag at bottom of the message 6. Mcssage goes back to carrier for deliver to called party destination via SMS-C, MMS-C, or email gatewa 11)7. Called party receives message on device. Message display and linking capabilities will he dependant on message type sent (SMS, MMS.

8. Called pam clicks on highlighted words with embedded links to display more information.

9. Link goes to 3 part) service proiders for maps, ads or search results.

10. Link results arc displaed to the user. Displa results and speed we be dependant on the X'AP/web capabilities of the called party's device.

Demo Definitions In order to rapidly demonstrate the capabilities and potential of S-Links, there will be 2 separate demo scenarios and milestones: Canned Demo The purpose of the canned demo is to show S-Links proof of concept. The demo will be limited to a predefined set of keywords and display results.

Field Trial

The purpose of the field trial version will he to demonstrate S-Links capabilities to customers, parmer and key industry influencers. The field trial is a working version of the product though there ill likeh still be limitations on available keywords and search results.

1. User interaction considerations Although the recipient oi an S-Links message ma) be reading the message as an email on a Pc: or a high-end smartphone, the expectation is that most users will he using a more typical mobile phone. Therefore, interactions with an S-links message should he designed with that user in mind. Access to the data that the user is requesting by clicking on a link should he immediate and require the smallest number of clicks to reach the desired information.

Calling Party The experience for the calling party would be consistent with current SpinVox voice to text products. CaUers would hear an 1VR greeting to leave a message with prompts that incorporate Spin\'ox branding.

Called Party The called pam' would receive either an SMS message, MMS message or email of the converted voice message. When the message is displayed, certain keywords would he highlighted, ideall those that are most relevant to the message content. Message should contain a minimum of 1 and maximum of 2 or 3 keyword links. The type of content displayed and the user interaction with that content will vary depending on the message type and the device capabiiities. (see implementation Considerations section below) For capable devices, selecting a highlighted keyword will initiate a X'AP or web session and display ad, map or search results associated with the keywords.

Canned Demo Field Trial

Keyword Minimal pre defined list of List developed in conjunction with strategy keywords ad server or search partner.

Link Type Keywords link directly to set Based on keyword selected and of pre-detined results related links.

a. Ad click a. Hotel -> \VAP site b. Map b. Map -> static map c. Ad tag in c. Audio clip message d. Movie clip d. Ad tag at bottom of the message Device N/A Y" party for adaptation/transcoding adaptation for mobile devices Location N/A Simple user pn)iIJes for containing based most frequent locations services N/A Default is opt out Opt-in/Out 2. Implementation considerations There will be 2 types of S-Links service offerings -S-Links for SMS and S-Links for MMS and email.

SMS

While SMS has the broadest reach in terms of subscribers and device support, there are limitations on the number of available characters in each message. This limit impacts the number and type of link that can he incorporated in an SMS message. A second consideration is the abilin for the device to render the link, if the link conforms to common IJRI. fi,rm http://www.anvsite.com some but not all devices will allow' the link to he clicked and launch a VAP browser.

The approach fr SMS will be to embed a single link or advertising taglinc in the message.

The link should be relevant to at least one of the words in the message. Alternatively there could also he a response option e.g. -Reply fl for more info -that could he sponsored.

Another approach will he to auction specific keywords to the highest bidder -e.g. Hotels = Hilton, Coffee = Starbucks. This approach will not be taken initially since keywords will have low value until the ad in cntorv increases as more ad-supported messages are implemented.

Canned Demo Field Trial

Keyword Coffee List developed in conjunction with ad server or search partner.

Display Taglines TBD based on partner list results Option 1: "To find a local Starhucks, go to bttp: / /mohile.starbucks.com" Option 2: "Looking for Starhucks? Reply S to find the closest one to you" MMS and Email MMS and email messages will provide a much richer S-Links experience for the end user in terms of message display and usahilirv. Although usage is not as widespread when compared to SMS, NIMS usage has recently experienced significant market growth. MMS has the ability to support rich data types such as images, audio and video, and does not have die same character limitations as SMS. Handsets that support MMS are also more likely to have some type of web access built into the deice. Additionall S-Links can be a major driver for increasing traffic of higher priced MMS messaging services for carriers. j

For i\RlS, the S-links message would contain between I and 3 highlighted keywords. When a keyword is selected, a \X'AP or wch browser will open and the relevant information VI11 he displayed. If the information is an address, the browser should open up a map with the address highlighted and standard options for receiving directions if possible. if a like word "coffee" or "Starhucks" is highlighted, clicking the link would bring up list of coffee shops or Starbucks that are local to that users. These may or may not he relevant at the time the user is viewing the message. Clicking on a highlighted item could also bring up an ad, either separateh or as part of the other results. A future option would also he to consider integrating an ad as part (if the actual message.

Email and iM messages would function similarly to MMS.

Product requirements 1. Customer interaction with IVR There will he no change to the calling party experience.

2. Delivery to recipient When a voice message is successfully converted to text, an SMS, MMS, email or IM will he sent to the intended recipient.

SMS/MMS B Party The text message must be sent as from the original caller's phone number (i.e. the A part)).

Message body The body of the message must use the appropriate Spin'ox SMS boilerplate, as defined in Message Classification.

This includes the definition of the branded signature and the use of quotation marks.

XILL DIFFER DEPENDING ON DELIVERY METHOD

Message Delivery Canned demo -3rd par aggregator

Field Trial -Carrier MMSC

3. S-Link Highlighted Keywords A minimum of I and a maximum of 3 keywords will be highlighted in the bod of the message.

User actions when clicking -see table below for demo and trial requirements Impact on message loads (see 2.2) Choice of words I. Carrier specific 2. Auction 3. Ad-search partner defined Inclusion of location click through?

Canned Demo Field Trial

Keyword Minimal pre defined list of List developed in conjunction with strategy keywords ad server or search partner.

Display Keywords link directl to set of Based on keyword selected and results pre-de fined results related links.

a. Hotel -> 1-hilton \VAP site Eg.

a. Ad click b. Map -> static map a. Hotel -> I lilton -show list of b. Map c. Audio -> Foo Fighters -Hilton Hotels, preferably those that c. Ad tag in t1sh page are relevant to user location message d. Movie -> "I Am Legend" b. Map -> Dynamic map (like d. Ad tag at flash page Google i\laps) showing local bottom of business and options for direcwns the message c. TBD based on partner d. TBD based on partner Content Spinvox built demo site 3tui party serviced content Sources 4. Service level -Trial Only Sign-up requirements The calling pam should not have to sign up with SpinVox or the Carrier to use this sen-ice.

Customers can opt-out of the service Service Level The service should meet the same availability requirement as the prevailing Spin Vox sen-ice.

VMCS Language support On initial launch the service must support the following languages: * UK English * US English * Canadian English * Canadian French * German * French * Spanish * Australian English * South African English Carrier Profile The SpinVox SMS server must hold a profile for the Carrier DDI to determine whether to deliver the message to the Carrier SMSC or deliver to an aggregator to send to the customer In that profile, there must be a reference to the injection and ejection validation rules for that carrier 7. Reporting -Trial Only It will he necessary to report on the activity on fr S-Links. The audience for all reporting will be both internal and external, Carrier facing and for advertisers or ad networks. j

Reporting requirements It must be possible to report on all messages on this service Reporting requirements It must be possible to report on the following product metrics.

* Usage * Traffic Reporting requirements \\ord impressions per day/week/month Click through on each word per day/week/month Links clicked vs. links displayed on each work per day/week/month.

Filter by Carrier, service provider etc SECTION C: WEB 2.0 Mobile Blogging -M0B10TM Blogs have become a er popular method of people sharing thoughts, facts, photographs, images and other information freely across the internet. Blogs are largely based around the concept that you're sharing something with a community to whom sour blog is relevant, often highly personal.

Blogs now exist for sharing information on films, concerts/gigs, shows and all sorts of entertainment, and more recently, a large rise in their use for Citizen Journalism where any member of the public can post news or information about a current issue. The BBC has recentis introduced such services along with other leading news pros iders.

The issue is that often people want to post something to a blog site when they're not at their computer (PC), but actually as it's happening or when it's relevant. For instance, having just left a cinema you'd be more likely to want to post a comment up about the film you just saw than waiting till later when you're back home. Likewise, if you've seen or heard a news story that suddenly affects your or you have an interest, you want to post an entry then and there.

In many cases, you']] he out an about, not necessarily at your PC.

Current solutions are to use the micro-browsers available on high-end mobile phones to log in and use either the alpha-numeric keypads or micro keyboards to type in your entry. That's fine if you're patient, technically competent and dexterous enough to type more than a sentence or two. For the rest of us, it's still highly impractical.

Spin\Tox Mobile Blogging is simple. just call the blog site phone number, speak your blog message and it's converted to text and posted up as an entry.

Imagine seeing a film Ofl new release you love and being the first to blog about it: "I saw the new X-Men film last night and I\loBlo'd it to your site with a five star rating!". Or being able to blog a news item: "Just seen a major crash on the M4 at junction 10 involving a petrol tanker. Avoid this route. Police are on their way." How it works * The owner of a blog site decides either they want to enable spoken hiog entries on their hiog site * The' contact SpinVox and sign up for an account and provide standard information, including their blog site host * They register the location (URL and email address * SpinVox gives the blog owner a phone number DDI) * Spin Vox will convert an voice messages left on their DDI into text and eithen o Email to the blog site email address o Post it via I ITTP or similar IP protocol directly to their blog site If the owner then decides to publish this number, for instance bs' putting up on their hiog site or emailing it to select people, anyone can use this number to speak them a blog entry.

The can simpl save this phone number in their contacts/address 1)00k so that speaking this blog and entry is always to hand.

Registering your name or handle When people blog, they often want to say who they are. Spin\Tox Mobile Bloing gives users the following options: 1. \1ien you call the blogs phone number for the first time, the SpinVox service will prompt you to speak your name or your handle.

For example:

a. "Welcome to SpinVox mobile blog. Please first speak your name or handle as you want it to appear each time you speak a blog, or press # to remain anonymous" h. User either speaks their name or handle ("Fred Flinstone'), or hits # c. "Thank you. Please speak our blog message after the tone. This will be converted to text and posted on this blog site".

2. You can go to a SpinVox website and register that when you call a given blog site (e.g. blog URL: www.filmrnaxblog.com) from a phone number you provide (e.g. your mobile: 07812101742), it should display your name (e.g. Fred Flinstone) or enter a default, such as Anonmous'.

3. You can optionally chose to displa an other details with your entries such as: a. sour email address b. Your Instant Message ID c. Your Vo1P ID (e.g. Skpe name) d. Your phone number e. A web address 1. Etc...

Technical solution The major blog site providers (e.g. blogspot, blogger.com, Yahoo!, Google, etc...) provide an interface so that blog sites the host can receive an email which is then automatically posted to the intended blog site. They also provide standard HTTP post interfaces which allow applications to post entries via the internet.

SpinVox determines which of the biog providers a user is on, and then automatically provisions the right type of interface to use to be able to post the text on to a hiog hosted with the provider, either via email or an I-ITTP post method.

The converted text is then formatted and relevant fields populated to ensure the text posted is displayed correctly on the hlog site and has the right information showing. E.g.: * Time and date * Text is optionally in quotes (e.g. lust seen Madonna's confessions and it stank!') * User name displaed o Blog spoken by: <user name or handle> (e.g. Fred Flinstone) o Anon mous blog enny * An other chosen data the user registered and chose to displa) o E.g. email address, IM ID, phone numher, VoIP ID, web address, etc...

X-Links in Blog Blog providers are able to automatically alert users when a new item has been added, including via email, SMS or Psi.

B simple adding in the blog's spoken message phone number (SpinVox Mobile Blog phone number to the text message or email, all recipients can chose to respond to this entr by calling this number (clicking on it in the SMS).

In addition, SpinVox helps direct people's to respond to a particular blog entry by putting an X-Link into the text message so that it is posted with.a particular reference.

For example:

* Albert speaks a blog ent-r via Spin\'ox by calling the blogs Spin Vox number * SpinVox posts his entry with an X-Link in (e.g. O2O79ó52000plOl) * The blog site automatically alerts signed-up readers with a message that contains this X-Link * Readers who call this X-Link will have their reply associated with Albert's orinal entry and thereby create a thread under his entry.

Mobile Photo Messaging -MoPhoTM The market for taking pictures on a mobile device that's connected to the Internet, typically a mobile phone with a camera, is evolving from trying to send other phone users a picture message (typically MMS or download the picture from the device to a computer and then save it, email it or burn it to CD.

A new genre of mobile photography has emerged whereby a photograph taken on your mobile device can he automatically uploaded to a vehsite for private or shared use. It solves several problems with copying or moving photographs off the device, sharing them and on larger screens where the quality of the photograph can he best appreciated.

However, users often want to post a comment with their photograph as it is being uploaded onto a website for them. Much of the impact (fun or seriousness) of a photograph is best expressed at the moment it was taken, not hours, days or weeks later when you're next at a PC to view and add comments. Using the device's small alpha-numeric keypads to do this when mobile is fiddly at best.

SpinVox enables today's standard mobile photographs services (e.g. Cognima's Shozu) with a simple means of also adding a comment as it happens. The user simply now speaks their comment which is converted to text and automatically posted along with the photograph.

Example:

* Max takes a photograph on his mobile phone whilst on holiday of two friends in front of a famous building * They decide to add a comment to the photograph before posting it * "P ust bumped into Bill and Ben in front of yes, you guessed it, Big Ben!" * Their message is converted and posted along with their photograph on their photograph sharing website * Max's two young children are at home in Scotland. They see that a new photograph has just been added to their father's photograph sharing svebsite.

* The' laugh and call their father to see if can take another photograph of Bill and Ben with Sherlock 1-lolmes.

The mobile photography service provider would update their application to provision the user with a phone number that is automatically called when they select Speak a Photo Comment'. This number is mapped to SpinVox's conversion service which then converts their message and sends it back to a designated location for posting with the user's photograph.

1. Photograph taken on camera phone -Figure 8 2. User then selects from Options menu: Speak a Comment -Figure 9 3. Application connects to a Spin Vox service, sends over a unique identifier to link the speaker, photograph and message.

4. User then prompted to speak their message: "please speak your photo comment atrer the tone" 5. Converted message is sent to mobile photography service provider's system which adds the comment to the photograph Spoken Mobile Messaging in an online Community SpinVo has launched several products in the SpinX family which includes users being able to speak a message and have it converted and automaticallc posted to a biog site, or speak a message and have it converted and sent to multiple recipients as either an SMS, email, MMS, lI1 or other messaging format.

Twitter Spin\'ox is launching a service whereby users of the increasingly popular Twitter service can simply use their phone to call a local number, speak their message and have it automatically posted to their Twitter account for them as a text. Naturally, users no longer have to be at a PC and online to use Twitter.

Echo message -live post confirm And e er time the post, they'll get an SMS reply (or an echo) confirming their posting went live, or not to allow them to retn. This idea applies to all types of web based service you'd post to as you need to know that you're entry/post was successfully converted and ( )sted live to the web, simply because you're not online, but on a phone instead. Echos can be returned as email or IM or other form of messaging and shared wider to keep a group informed too.

This echo behaviour complements the service that Twitter has whereby users can elect to receive an SMS eer time someone in their group posts an entr). So with Spin Vox, all users can truly stay in touch with their Twitter community by phone wherever they are. If one of the group posts by Spin\Tox, the rest will automatically get an SMS with what thc said, and naturally the option to call in a reply or update. So there's no longer a dependency that anyone is actually online for the group to stay in touch.

This is a significant step forward in removing thc existing dependency of Twitter and in fact all other web (PC based) messaging service providers.

Social Network Messaging In fact, any social network, communit forum or other type of online community can benetit from Spin Vox providing them with a simple means (if stay ing in touch with their communin just by calling in their message, letting SpinVox convert it and post it to their account and then leveraging existing messaging services to let others see ( ur new post. They may be mobile too.

X-Links open up the ability for these communities to use SpinVox without complex sign-ups and decisions. Once the get a converted message, they ma also be offered a link which will allow them to speak a reply and have it also posted online, thereb enabling the whole group to stay in touch wherever the are just b a simple phone call.

For example, Yahoo! offers messenger services to its users and as groups, the can now broadcast messages via Yahoo! online to each other, but only when online and they're all logged in. With SpinVox, they'll he able to shout out' a message to members of their group and know it'll reach them all whether they're online or not.

Voice Blast The idea is a \Toice blast' that reaches users either online or off-line as a text message of one form or another (SMS, email, IM, etc...). A form of group broadcasting via voice to text where the group is defined by their online connections, but messaged anywhere, particularly mobile.

Dial-tone = web-tone in short, this expands upon the idea that with Spin\Tox as a network service, anyone can now use phone networks of any type to speak a message that will appear as text online in an account or place of their choice.

What this also means is that no user, in fact the whole group, actually needs to be loed into their online service/account (e.g. Twitter, Yahoo!, etc...) to stay in touch with each other. This means these services can be used by the whole group fully off-line and via a simple phone call. j

Reducing the Usemame/PIN barrier to a phone call What this also means is that a user's phone number (i.e. their CLI or MSISDN in mobile networks) becomes their identity for posting to online sen-ices. The elegance of this is that to post to an account or blog or other online service, ou don't have to remember URLs, user names or passwords -just make a phone call and you're in! Twitter Micro-blog implementation This section coers the requirements for launching a new product specifically for use with www.Twitter.com. Twitter is a micro-hloing environment, where users (tweeters) sign-up and then post in short updates (tweets) about what they're doing, using IM, SMS or web.

These bulletins appear on www.twitter.com in their personal page and are sent out to their friends as web updates or by SMS. Tweets are limited to 140 characters. Twitter provide an API which lets 3rd pam developers integrate applications and sen-ices.

There are two strands to the product strategy. First is the demo: A user can try out the SpinVox Twitter demo bs caffing a country-local DDI, and seeing the resulting conversion cm the SpinVox demo twitter account. This doesn't require any sign-up: just call the number and check the web site. It's analogous to the Spin-m-Blog demo on our web site. The other strand is a more typical Spin-mv-Tweet style sen-ice: Users sign up fbr a Spin-mv-Tweet st Ic account. They can then call a country local DDI to leave a short message, which is converted and sent to Twitter.

Product Overview

DEMO

* Customer can tr the demo out on www.spinvox.com by caffing the country local "SpinVox for twitter" demo number. Their tweets will show up on the Spin'Vox for twitter page within www.spinvox.com and on the SpinVox demo page within twitter.com. No account created.

* SMS delivered back on successful/unconvertible conversion * No SMS sent for hangups.

* Entries will he moderated, hut this will be after submission to Twitter.

LIVE

* Customer opens SpinVox for Twitter account on www.spirnox.com and enters their Twitter username and password. User is encouraged to sign up with, and use, a mobile number.

* User is sent initial PIN via SNIS and asked to login to create account.

* On login, customer is sent 2nd SMS welcoming them to SpinVox and asking them to save DDI to phone-in their Tweets.

* Customer calls countr -local Spin Vox for Twitter number and leaves message * If deposit is converted, the text is sent to Twitter.

* Optional notification SMS on converted and uncon%ertible.

* For hangups, no notification SMS will be sent. * All SpinVox for Twitter accounts are automatically added to friends

list of SpinVox Corporate on www.rwitter.com (through API) Twitter implementation requirements 1. Service Level 1.1 The end-user will signup at www.spinvox.com to use the full SpinVox for Twitter service.

1.2 The service should meet the same availability requirement as the Spin-mv-\'mail service.

1.3 Recordings should be limited to 30 seconds.

This will he reviewed periodically after launch, to decide whether the limit should he lowered (e.g. to 20 or 15 seconds).

1.4 All SMS deliveries should be limited to a single SMS.

There should he a configuration parameter to specify the number of characters, which will initiall he set to 160.

1.5 TAT should be 98% of messages within 10 minutes, measured across a calendar month, where the daily average is 18 seconds or less. I.e. should meet the same TAT requirements as Spin-mv-Vmail 1.8 On initial launch the service (demo and live) must support the following languages: * UK English * US English * Canadian English * Canadian French * German * French * Spanish * Australian English * South African English 1.9 On initial launch country-local DDIs must be provisioned for the following countries for both demo and live (i.e. t\vo DDls for each entr in the list below).

* UK (language: en-GB) * US (language: en-US) * US (language: es-ES initially es-US when available) * Canada (language: en-CA) * Canada (language: fr-CA) * Germany (language: de-DE) * France (language: fr-FR) * Spain (language: es-ES) * Australia (language: en-AU) * South Africa (language: en-ZA) 1.10 Country-local DDIs need to be "golden" memorable numbers e.g. in US -415 TWITTER or similar. Priority should he given to live numbers over demo numbers, and to the US and UK numbers.

1.11 After inidal launch, the LIVE service numbers need to be capable of handling high volumes of concurrent calls 2. Customer interaction with LVR it is envisaged there will he minimal interaction between a customer depositing a message and the IVR system.

Live service CLI withheld 2.1 For the live service, if the caller has withheld their CLI, the caller should be told to turn off number withholding and call back.

Language selection 2.2 LIVE service -If the caller has a SpinVox account, and the account's language is one of those listed in requirement 1.9, then we should use that language. Otherwise the language should be 1)atever is associated with the number dialed. Note for the DEMo service -customer does not need a Spin\'ox or Twitter account to call the Demo DDI's. If the caller dues have a Spin\Tux account though, we should take their language preference, rather than using the language associated with the countr -li cal DDI.

Use from unregistered phone 2.3 If the caller's numher does not have a Spin\7ox for Twitter account associated with it, the caller should be directed to the Spin Vox website.

Demo greeting 2.4 \Xlien a user calls a SpinVox for Twitter demo DDI, the should hear the greeting "Welcome to Spin Vox for Twitter, please speak your message and it will appear on screen at web address-tbc" If the caller has withheld their CLI, they should also be told: "You will not receive any conhrmation Si'vlS, as you withheld our number".

Live service greeting 2.5 When a customer calls a regular Twitter DDI, (s)he will hear the following message: "Please speak your Twitter message after the tone." \oice to be used for all IVR will he female and the same as other current Spin\'ox pmducts.

2.6 When recording the voice message, the caller should be able to hit the # key to re-record the message. The caller should he informed of this feature, the first three (3) times they use the service. In this case the prompt from requirement 2.5 should become: "Please speak your Twitter message after the tone. To re-record your message press the hash key (#) at any time" 2.7 If a customer gres over the recording limit specified in requirement 1.3, they will be prompted to re-record the message or leave the message as is. This mirrors current behaiour of other Spin\'ox products.

2.8 There will be no DPA prompt.

3. Provisioning/Account management Sign-up information 3.1 To create a SpinVox for Twitter account on:::s5..4ifl' a user has to enter: * mobile phone number * Twitter usernamc and password * email address language preference * country lithe countn is the US, then the user should also have to provide * state A DDI should not be assigned to the user, but rather they are told which of the country-local DD1s (see requirement 1.9) they should use. Use of the SpinVox Twitter demo does not require an account to be set up.

SpinVox tweet-out 3.2 B default, when a user signs up for a SpinVox for Twitter account, a tweet should be posted to their Twitter account: I've just signed up for Spin\'ox for Twitter at www.spinvox.com/twitter The sign-up page should have a checkbox which controls whether this announcement is posted. It should be on by default.

Twitter account validation 3.3 When a user is registering for a SpinVox for Twitter account, we should validate whether the Twitter account details are valid. If the account isn't valid, then the user should he given a link to the account creation page at www.twifter.com.

PIN notification by SMS 3.4 \X'hen an account is created as per 3.1, an SMS should he sent to the user with an initial PIN, which they need to log in to the web site.

Welcome SMS 3.5 XX elcorne SMS is sent to customer as the successfull log-in for the first time only.

Welcome SMS copy TBC.

SMS notification 3.6 Customer can control whether the get SMS notification for the two cases: * message converted and sent to Twitter * message was unconvertihie These can be controlled independently via self-care, so a user can turn off the converted notification, but leave on notification of unconvertibles, for example. For new accounts, SMS notification should be turned off for successful conversions, and turned on for unconvertible. These options should not be given on the sign-up page.

Friends of SpinVox 3.7 By default all new SpinVox for Twitter accounts should he added to the friends list of the Spin\'ox Corporate Twitter page (Marketing owned page). A user should he able to O)t out of this via a contiol in self-care. This control should not be provided on sign-up. This must be covered in the T&C's, which will linked on the sign-up page and in self-care.

Self-care 3.8 The customer can change the following via self-care: * Twitter username * Twitter password The user will he able to change all other fields given during signup as part of regular self-care usage.

Access control via PIN 3.9 Customer can enable PIN access to deposit message on their account. lf enabled, then the caller should be asked fir the account's PIN before getting the regular prompt (requirement 2.5).

4. SMS message to caller When a voice message is successfully or unsuccessfully converted to text, an SMS will he sent to the caller if they have selected this option (see req. 3.6 above).

4.1 For the demo service, if the caller's CLI was withheld, no attempt should be made to send any confirmation SMS's.

4.2 The text message vill come from the called number -either the DEMo or the LIVE country local DDI.

4.3 On successful conversion the bod of the message shall be shown in Quotation marks e.g. DEMo = From: <SV Twitter Demo DDI> Your tweet "<tweet extract>" is posted on www.spinvox.com/twitter (tbc) LIVE = horn: <SV Twitter Local DDI> \our tweet "<tweet extract>" was posted to Twitter -powered by Spin\Tox * 61 The full SMS text must not exceed the limit specified in req. 1.4. If the full tweet cannot he included, then the exUact should finished with "..." ellipsis).

4.4 If unsuccessful, the mobile caller will be sent an SMS as below:-Sorry, the "tweet" ou left could not he converted to text. Please call <dialled-number> and trs again. Thank you -www.sprnvox.com 4.5 There will be no QuickLinkTM at the end of the message.

4.6 No confirmation SMS should be sent to the caller when a call is a hang-Lip.

5. Conversion if the message is successfull converted the tweet shall he sent to the customer's twitter page. The message should he tagged with the Spin Vox hvperlink.

5.1 LIVE = Converted messages should he sent to the customer's twitter page with the SpinVox source link sending users to ww.spinvox.com/twitter product page.

Moderation of Demo tweet s 5.2 All nveets to the SpinVox Twitter demo can he removed by a moderator after posting to Twitter.

5.3 Twitter messages to begin with the word says and fbllowed by the conversion in double quotation marks to indicate spoken message i.e. says "hi I am here speaking to twitter" The total post must not exceed 140 characters. If the converted text is too long, it should he truncated, and the extract should he ended with "..." (ellipsis).

6. Reporting It will be necessary to report on the activit on the SpinVox for Twitter service. The audience for all reporting is internal to Spin Vox, there is no external reporting.

6. I It must be possible to report on all messages on this service * Split by language * Conversion hreakdown by product and by customer (conversions, unconverted and hang-ups) * No. of daily sign-ups and successfull created accounts (sign ups = not logged into website to open account) * Daily active users * Average message duration * Conversion length (in characters) * Avg. no of msgs/user per period (br/dav/wcck * Traffic proflle by time of day/week/month 7. Future requirements * Option to bill for this service in future using C/card.

* Option to switch terminating number to rated number to generate call time revenue from deposit calls.

* Ability to track call durations for per minute/second billing * Review private messages/commands and how use * Abiht to block callers from calling certain number ranges/rates.

8. Web experience Customers arrive at www.spinvox.com home page and see Twitter-branded logo or button on home page. They can also access the SpinVox fhr Twitter page through the products link on home page.

When customers click through they see a SpinVox for Twitter page -containing - 1) A Twitter logo 2) instructions about the product and how it works with Twitter 3) Instructions about bow to set-up Twitter to work with SpinVox and how to tell their friends to get SMS updates.

4 FAQ's button about SpinVox for Twitter (tweets posted using existing privacy settings etc) 5) A Spin\Tox for Twitter demo and demo button (showing page www.Twitter.com/spinvox C)R www.spinvox.com/rwitter) No account created during demo process as all entries posted as Spin\'ox 6) Click here button to invite them to set-up an account 7) User needs to input twitter username and password, along with mobile number and email.

Encourage user to input mobile phone no. as primary choice 8) Abilit to manage the service within M Account.

SECTION D: MISSED CALL MESSENGER Missed Call MessengerTM Missed Call Messenger (MCM) solves the problem that faces many callers and carriers -namely, in markets where voicemail isn't enabled, callers now have the option of speaking the person they tried to call a text message of somc form and so stay in touch.

Many markets see less than 50 i voicemail penetration, such as southern Europe (Spain, hal, Greece, etc...). The reasons are mainl two-fold: 1. Voicemail is a chargeable service and in high pre-paid mobile phone markets, users tend to turn it off to save on costs as calls to deposit and retrieve a voice message are in the cent per event range.

2. Culturally, voicemail is perceived as too formal and business-like and often seen as a rude way for daily messaging.

Insight The insight here is that what callers do in this scenario is to not leave a voice message -where voicemail exists, or hit a dead-end (e.g. ring out, busy, off) where none exists -but instead hang- up and in some 30% of cases type a text message to the person they tried to call. So actually, in these cases their chosen form of messaging is to send a text when they can't reach the person thes re calllng.

For carriers, missed calls (non-completed) of this type account for several billion events per year. In Spain. the second largest network Vodafone has some 2.3bn missed calls a year.

MCM solves this neatly for all parties. It is a network based service, so no handset dependency at all and works as follows: U When a call is being placed to a subscriber/customer who hasn't got voicemail services, the network knows to catch the call before it fails -hits busy tone, rings out, phone is off or unavailable/out of range.

o The network then picks up the call and plays back an 1VR recording to the caller of the form: "if OU would like to speak a text message to the person YOU are calling, press 1".

o if the user selects this option (e.g. 1), then they're simph offered a prompt to speak their message -e.g. "speak your text message after the tone".

o The sstem then records the audio, sends it to the SpinVox \I\ICS for conversion, and the converted text then sent on to the called party and sent as if the message had originated from the calling party, not a system number or name. Typically this is donc b using the callers CLI and putting it in the from' field of the sent message.

Today, this is being rolled out with SMS, but MMS, email, WAP/HTNIL pages and any other form of text messaging can he used depending on the network's capability and user requirements.

The benefits are simple, but very large: O Callers get through first time when they need to O Recipients see immediately who needs them and can read the actual message O The r)le of message choice and charging is reversed. Typically, voicemail is a B-pam service (recipient) because they pa' and opt to have it. With MCM, it's actually an A-pam' (caller/sender) service as they opt-in every time the use it (no subscription) and they can also be billed for the use of the service.

O Carriers can generate new revenue from missed calls as now the caller (A-party) can be charged for the option of speaking a text either by call termination charges, premium rate SMS or inter-network charging models -all of which exist today.

o Likewise, a more classic B-party charging model is possible two, just like soicem all is toda.

O Call continuity (the number of additional calls or text messages or data traffic generated as a consequence) rises. This is expected to he more than existing missed call alert products which are known to be some 2-3%, and Spin\'ox MCM is expected to be more similar to Spin\'ox Voicemail-to-Text which has an impressive 7% voice uplift and 17% text uplift.

0 This service serves callers from any network, not just those on the borne network.

E.g. Callers may call from network x to a person on network y. Network v has enabled MCM and can offer this service to callers from network x and generate additional revenues from any missed call, not just on-net. Likewise, this can be reversed so that callers from the host network (network v) may he offered this service when unable to reach users on other networks (network x). These combinations provide the al)lhtv for the host network for MC11 to capture all missed calls relating to their subscribers/customers regardless whether they're the A or B party. See table below.

U Some networks can deplo this as a recipient (B-party) service instead and bill them for use of service, much as voicemail is today, so MCM can it existing business models.

How MCM is being deployed: Figure 10 shows MCM with Spin Vox \oicemail to Text also deployed.

MCM allows the host network to serve A party callers regardless of whether they are on the home (host) network or not, providing 1000/0 reach for serving missed calls relating to their subscribers/customers: A party (caller) B party (recipient) MCM available On net On net Yes On net Off net Yes Off net On net Yes Off net Off net No Clearly, missed calls that occur between other networks are beyond reach.

Billing Options Where required, MCM can be charged for in different wa s: 9 Call termination charges to the A-parr (caller) based on minimum and/or per second/per minute charges. This is similar to thc way voiccrnail deposits are charged.

0 Premium rate confirmation SNIS sent to the A-part to charge them for each time the opt to use \lCM 0 Cross net charges for the service, SO networks x & Y would agree that they'd charge each other and therefore their users a certain amount for each event which would appear on their bill. The difference here is that this could he done via premium product billing API's or protocols to put the product/service into a different billing class, not standard oice call charge.

0 Free -the call-continuity and call completion impacts can he highly favourable and offset any need to generate revenue explicitly from each event.

Again, this can he reversed so that it's a B-parts' service and thes pa for it as shown in an of these methods, or it is a standard feature as voicemail currentl is today.

Product Options Given that not all networks can manage calls as shown in the above designs, there are other ways of providing MCM: Option 1: Call back for message * Call is attempted to B-parts, fails and clears * A-party is called from network and offered service * If accepted, message recorded and processed * A-parts-is charged only if message is converted * If not converted, B-party receives standard missed call alert Option 2: Text hack for message * Similar to Option I, but service offered via SMS * A-parry responds to SMS if they wish to invoke service * A- party calls l\JR via embedded link in SMS (free call) -see X-Links above * Charged for service only if message successfully converted * if not converted, B-parr' receives a standard missed call alert (MCA) Retrieval options in all the above options for MCM, the B-party (recipient) may want to hear the voice message. in this case they can be offered a number to call and have that message pla ed back to thcm.

This is either as an extension to SpinVox's existing QuickLinkTM technology whereby the converted text message for the B-party contains a link that either places a call to a network service (tvpicall IVR that then automatically plays back this message. The link itself can either be a real phone number and then a set of digits that when the user tpes them in tells the system which exact message to play back.

Alternatively, this can he a virtual number that the network can create which means that in one call the network knows both the pe of call and which exact message this relates to.

Attached or embedded audio Alternatively, the audio is hosted on a web site and streamed back over a data channel, or it's sent as an attachment/embedded file which is possible with MMS, email and other multimedia capable forms of messaging.

Naturally, retrieving the audio can create new incremental revenue for the carrier which didn't exist before.

SECTION E: OVERVIEW OF SPINVOX PRODUCTS The preceding Section D described a specific innovation, Missed Call Messenger. This Section E provides an overview of the array of Spin\Tox products.

Two generic ti pes of product are available: * Sender: where you choose to speak a text mcssagc * Recipient: where you choose that people speak you a text message All of these share the ability of one person to speak another a text message of some format.

Figure 11 shows how various conventional messaging products (voicemail, email, SMS, 1M and voice) are distributed on a Time Dialogue axes. Figure 12 shows how various SpinVox products alter this landscape.

* Recipient products extend a dialogue; reduce inherent delays in receiving message; give real-time voicemail (push); use a seamless interface; are ubiquitous, and work on any device, any technoli gv, any network.

* Sender products initiate new' dialogues; use a simpler interface to make mobile messaging more intuitive; allow ordinary users to Say it, Not Thumb Type It!; require nothing new to learn; allow existing applications to he enhanced; generate new modes for messaging to provide real mobilin' -such as safe and fast use even whilst driving, walking, etc.; allow new revenues from existing products.

We will now look at each category in more depth.

Recipient Products These are all products where you activel decide to enable others to message you by speaking you a text message.

E.1 Voicemai1toTextTM When people leave a user a voicemail message, it is converted and sent to the user as an SMS message.

Q uickLink" allows users to listen to the original message the text relates to.

E.2 VoicemailtoEmai1TM When people leave a user a voicemail message, it is converted and sent to the user as an email.

When the message was not converted, they can optionally be sent the original audio message as an email attachment.

QuickLinkTM allows users to listen to the original message the text relates to.

E.3 Call-to-MailTM Designed for call centres, direct marketing response and other customer facing functions, callers can either: * opt out of the queue in favour of speaking a message that's converted and sent as email * always be asked to speak a message that will be converted and sent as email E.4 No answer -Speak a Text -(Missed Call Messenger -see also Section D) Designed for users who don't have oicemail, or want voicemail, typically high amongst the prepaid mobile phone market, or non-associated voicemail box market.

This is a network based service that manages unanswered calls and offers callers the option of speaking a text to the person they ere trying to call. This applies to calls that are unanswered, busy or rejected (send busy tone).

A network operator simply deploys this to all accounts where there user has no voicemail or equivalent voice messaging service.

1. When a subscriber doesn't answer their call, the caller is offered a new option: "I'm sorry, this person is unavailable. To speak them a text, press 1 now." a. Optk)nalh, the caller is billed either by time on the line, or per event, e.g. "Calls cost 50p per minute, minimum charge 20p" 2. Caller now records their message.

3. Suhscriher who missed the call tets a text message from the caller with what the said as text.

a. Optionalli, subscriber given a nUmber to call in to listen to the original message.

What's unique about this is that subscribers won't have to sign-Lip or pay for the benefit.

Callers are given this choice as it might he important to get a message to the person they're trying to reach.

Suhscrihers can choose how they want messages delivered to them: SMS/MMS, email, etc...

Sender Products -Network based These are all products where you decide to speak someone a message that is then converted and sent to them as text.

E.5 Call Return -by Speak a Text Service providers have been offering subscribers a wa of returning a call within voicemail - call hack -which the suhscriber initiates b\' selecting an option before or after message play-back. This adds a new option to return the call, hut instead by speaking them a text message reply: 1. User calls into listen to voicemail messages. At the beginning or end of even' message played back, they are offered the option to speak the caller a text hack.

"To speak this person a text, press 1 now" 2. They press I, then speak their message; it's converted and sent straight to the caller's number.

a. The voicemail system has both the caller's CLI and the subscribers, so can correctly form a converted message that is sent as if directly from the subscriber, directly to the original caller. The recipient (original caller) is offered a link to listen to original message.

E.6 IVR -Speak a Text (see also Appendix I) On any l\TR system, an option can be offered to any caller wherein the can speak an) one a message and have it converted and sent as text.

1. User calls either a dedicated number, or calls their voicemail and is offered this option to speak someone a text: "To speak someone a text, press 1" 2. User then prompted to enter the phone number of the recipient. They either enter the numbers on their phone ke pad and the system detects the DTMF or equivalent signalling tones, or they select them from an address 1)00k.

3. System checks phone number is valid.

4. User then prompted to speak their message: "Please speak your message after the tone" 5. They speak their message, it's converted and sent süaight to the caller's number.

a. The voicemail system has both the caller's CLI and the subscribers, so can correctly form a converted message that is sent as if directly from the subscriber, directly to the original caller.

E.7 Network Service -Speak a Text This is typically for landline networks where people are still accustomed to dialling phone numbers, hut is technically possible on any network type -fixed, mobile, wireless, VolP.

If you want to speak someone a message, simply put a call modifier' (prefix or suffix) with the number of the person you want to message. Then the user hears "Welcome to Speak-a-Text. Speak your message after the tone." The user speaks the message and hangs up. The message is converted and then sent to the correct recipient. The recipient is offered a link to listen to the original message.

Sender Products -Handset Based This applies for users who want to speak someone a text message rather than call them, much like opting to send someone an email or an SMS. More details ofl this are given in Section E.10 below.

E.8 Spoken SMS Four options to Speak-a-Text on a handset: 1. Application on borne' screen 2. Menu option in Address Book/Contacts 3. Menu option in Messaging apps 4. Menu option in Call/Missed call list a. Natural extension of existing nathe applications b. New option: SpeakTxt' Note: Although Spoken SMS is shown, the concept is the same for speaking an MMS, an email, an instant Message or an' other messaging product type.

E.9 Spoken Mail An application on the handset allows a user to select who rhe' want to email, SMS or MMS.

The are then offered a Speak mail function. The user is connected to a SpinVox spoken message service where the are prompted to record their message. The application sends through who the mail is for -the destination email addresses or list of addresses, subject, and any other message parameters.

Figure 13 shows an example of a dep]ovment of Spoken email and Spoken SMS/MMS with a mobile service provider -SIP telephony connectivity.

Figure 14 shows an example of a deployment of Spoken email with a French mobile service provider -standard telephony and svnchronised data.

Fire & Forget Principle In an) of the methods shown, there is a simple principle that makes the user experience unique: * minimum effort -just speak your message * nothing to learn -just like leaving a voice message on standard voicemail * reliable -few steps as possible to avoid contusion or technical failures * rohust -only if the message isn't converted do you need to do anything, otherwise you know it's been done The following section will focus on handset based sender products.

E.1O Speaking a message from a mobile device Speaking a message SpinVox has created a software application; Speak-a-message (also called SpinMvTexO, which when loaded onto a device, such as a Nokia mobile phone, allows a user to speak a message, which is then delivered to the recipient as text.

The purpose of this service is to give a user the ability to speak a message rather than type it out on their phone ke)pad. This will make it more convenient, easier and faster than nping it on their phone keypad.

Messages can be sent in the form of an email, SMS or MMS message, depending upon the details stored in the Address Book of the device, fbr the recipient. Multiple recipients can be sent the same message by using the broadcast' facility of the application and messages can also hedelivered to customers Blogs or other web-based applications.

Embedded menu items Additional functk)nalitv is brought to the device, by adding new menu items into the standard menu üee. The menu option "Speak-a-Message" is added to the following applications:

D

* Text Messaging Application * MMS Messaging Application * Email Application * instant Messaging (1 Ni) Application * Address Book * Call Logs * Home screen, using a soft ke The functionalit-v that the menu option gives, changes dynamically, depending upon which application the user is in, as detailed below.

Text messaging application Selecting the Speak-a-message option allows the user to: * Create a new message using the contacts Mobile number as the destination * Reply to a previous message using the number provided * Applies to an) of SMS, MMS, 1M or other messaging application on the device Email Application Selecting the Speak-a-message option allows the user to: * Create a new message using thc contacts email address as the destination * Create a new message to multiple recipients using their email addresses as the destination * Reply to a previous message using the contacts email addresses as the destination Below are the generic actions a user will take in either the text messaging or email application to send a message.

1. Caller selects Messaging/SMS application and selects Speak a message' option from menu and is directed to Contacts.

2. When the Contact has been selected a connection to the Spin\1ox platform is established 3. An announcement recuesting the user to speak their text message will then be pIa ed 4. The caller will leave an audio message.

5. The B Party information is passed to Spin Vox (Selected in Step 2).

6. The Spin Vox platform will convert the audio to a text message for onward delivery.

7. The message is then sent from the A Party to the B Party as if they had typed it.

8. The B Pam-receives the message and it appears to have come from the A Party. No special system numbers are used or substituted.

Figure 15 shows the typical user experience of speaking a message from within the Text Messaging or Email Application Address Book Selecting the Speak-a-message option allows the user to: Create a new message (intelligent addressing decides the message path). Below: are the steps taken b' a user accessing Speak a message from within the address book application: 1. Caller selects a contact from the Address Book.

2. Caller is presented with a menu option to Speak a message 3. When the Speak a message option has been selected the intelligent addressing function looks at the available methods fin delivering a message and then makes a connection to the Spin Vox platfbrm 4. An announcement requesting the user to speak their text message will then be played 5. The caller will speak a message.

6. The B Pam' email address or phone number is passed to Spin\'ox service (Selected in Step 1) 7. The Spin Vox platform will convert the audio to a text message tbr onward delis en.

8. The message is then sent from the A Party to the B Parts as if the) had typed it.

9. The B Pam-receives the message and it appears to have come from the A Party. No special ss stem numbers are use(I or substituted.

Figure 16 shows a typical user experience of speaking a message from within the Address Book Call Logs Selecting the Speak-a-message option allows the user to: * Create a message for numhers listed in the Missed Call log using SMS as the reply path * Create a message for numbers listed in the Outgoing Call log using SMS as the reply path * Create a message for numbers listed in the Incoming Call log using SMS as the reply path The above methods are easil accessed using the main navigation buttons on the device, such as Call, or Menu. There is no need to use lesser accessible alphanumeric keyboard to type in information.

The steps below are the generic actions a user will take to reply to someone whose phone call they missed, or to whom they have recently spoken.

1. Cal]er selects a contact from the Call Log 2. Caller is presented with a menu option to Speak a message 3. When the Speak a message option has been selected a connection is made to the Spin Vox platform 4. An announcement requesting the user to speak their text message will then be played 5. The caller will leave an audio message 6. The B Party number is passed to the SpinVox platform (Selected in Step I) 7. The SpinVox platfUrm will convert the audio to a text message for onward delivery 8. The message is then sent from the A Parts to the B Pam-as if they had ped it 9. The B Party receives the message and it appears to have come from the A Part-. No special system numbers are used or substituted.

Figure 17 shows the n pical user experience of speaking a message using the Call Log.

Soft key access It is possible to activate the Speak a message application from the home Screen of a mobile phone, by using one of the soft key shortcuts, rather than having to navite to a particular application, such as the Address Book, first.

Caller Access -Soft Key Below are the steps a user will take to speak a message from the Home Screen of a device.

1. Caller selects the Speak a message soft key and is directed to a list of Contacts they can speak a message to where they then choose a contact.

2. When the Speak a message option has been selected a connection to the SpinVox platform is established 3. An announcement requesting the user to speak their text message will then be played 4. The caller will leave an audio message.

5. The B Pam number should he passed to Spin Vox (Selected in Step 1) 6. The SpinVox platform will convert the audio to a text message for onward deiven- 7. The message is then sent from the A Party to the B Party as if the had typed it.

8. The B Pam receives the message and it appears to have come from the A Pam'. NC) special system numbers are used or substituted.

Figure 18 s1io s a typical user experience of speaking a message from within Speak a Message application Extendable application The Speak a message application can be easily extended to offer additional functionality for mans different types of Spoken Messaging. Additional message types include Social Networking applications such as Blogging and peer to peer communication, such as Instant Messaging.

Figure 19 shows a typical user experience for Speaking a Blog Figure 20 shows a typical user experience of speaking a reply in a Mobile 1M client.

User experience Fire & Forget' in 3 clicks The Speak a message application uses a unique Fire & Forget' system for creating and delivering messages. This differs from oilier systems that require the user to speak, review (on screen) and confirm before finally sending the message. Fire & Forget means: minimum effort -just speak your message * nothing to learn -just like leaving a voice message on standard voicemail * reliable -few steps as possible to avoid confusion or technical failures * rohust -only if the message isn't converted do you need to do anything, othenvise OU know it's been done The Speak a niessage application takes control of the mohile device, providing a means of always being able to speak a message within 3 clicks. Typically these 3 clicks are translated into the following actions: 1. Select speak a text' 2. Choose whom to send a message to... speak a message 3. Hang-up Figure 21 shows the 3 clicks' user experience The Fire and Forget system combined with the no more than 3 clicks' approach means that the user can send messages in situations where other systems could not be used, such as walking along a street, or in a situation where it's not possible to look at the screen for any length of time.

The Speak-a-message application is also designed fbr one-handed use, with all the functions easil accessible using a single key click and the menu navigation device of the handset.

Figure 22 shows the Tire & Forget' system employed hy Speak a Message.

Intelligent message addressing and delivery \\ hen a user elects to speak a message to someone from his or her Address Book, the type of message that is to he sent is decided b the contact details available in the address book.

* If onis an email address is available the message is sent via email.

* lion])' a mobile phone number is available, the message is sent via SMS or NIMS * If an online account name is present for IM or other, the message is sent here * if multiple are available, the message can he sent to a selection of destinations, however h default the message will he delivered to the mobile number Fast address list The fast address list is an inteffigentl compiled list of recent contacts, which is produced by understanding the users previous behaviour.

The algorithm builds a list of the most recent people the user has been in contact with, taking into consideration the following: * The communicating type (email, text message, phone call, or spoken text) * The frequency of communication with that contact * I-low recent the last communication was * Alphabetical order This is then presented in a single, easy to read list; which still offers easy access to any contact in the customers Address Book. This differs from the existing Call Lists', such as the SMS Sent folder, as there is significant intelligence applied in creating the Fast Address list.

Figure 23 shows the Fast Address List -showing recent contacts that have Called, been Called, Texted (SMS or MMS or Emailed (or any other messaging/communications process used). Because the Fast Address List is comprehensive, it becomes the central resource for all unified communications tasks the user needs to perform.

Linified messaging breaks down the barriers between various forms of communication, such as voice, email, and voice mail.

The Speak a message application effectively provides the user with a single origination point for all these types of messages, thereby providing the user with a unified message centre on their mobile device.

Having the capability to respond to oice messages using text or text messages using voice may seem trivial, however, it is a means for end users to enhance or even improve upon their productivity, especially if it saves them time in communicating with one another.

For mobile users, access to and use of the phone is essential, especially while they are in transit. With the Speak a message application offering a unified messaging experience, mobile users can receive and respond to voice messages, e-mail messages, and fax messages, by speaking a reph, and can maintain a higher level of productivity while they are out of the office.

Automated message transport selection Messages are sent to the SpinVox platfbrm using the most appropriate transport method aailahle. For example, a spoken email will be captured on the device, typically as a WA\' file, l)ut can be any form of audio file, and forwarded to the \MCS as an email, using a 3G or GPRS data channel, if it is available. Once conversion of the message is complete the result will be emailed to the recipient.

The routing of messages from the mobile device to the Spin Vox platform is carried out on an intelligent basis depending upon the available transport methods. The choice is made from the following list: * GPRS data connection * 3G data connection * SMTP interface * H1TP interface * IVR (fixed line) * J\IMS if the optimum method of transport is unavailable, the application automatica11 checks flit the availability of the next most appropriate method and uses it.

Asymmetric messaging This soft-ware creates a unique new set of options fir the user and recipient to continue in contact using a range of connected messaging options.

Outgoing call becomes a text message What makes this sen-ice unique is that the original message starts life as a spoken message and when it is finally delivered to the end customer's device it not only appears in their inhox, but it has been transposed into an email or SMS.

Incoming call replied to by an email or text message B creating this service Spin Vox allows the recipient of the original voice message (or missed call) to choose to reply by speaking a text message or email, rather than b' traditionally having to call the sender of the message using the telephone or type a message using the keypad of the device. This is unique in that once the recipient replies to the original message via an email or text the end-to-end communication method has moved from being voice driven to text driven and once the reply is sent to the originator they too can then reply via a text message, email or by speaking a message.

Product requirements for SpinMyText (SMT) The key to the success of this application is in its' simplicity of activation. It must be possible to inoke it through a single key press, which is available on any handset, and complete the process from start to finish in no more than 3 key presses. The SMT product offering will ideally he positioned at Mobile Operators and Enterprise Customers, enabling a user to select an option on their handset that allows them to speak a text message (The same functionality can also be applied to speaking an email message). This audio file is captured by 31) the Spin Vox platform and converted to a text message for delivery.

The product must meet the following criteria: One hand, one thumb accessible -The application must he so simple to start and use that it almost feels like it could be a handsfree' application. The Acid test for the success of this application is whether it can he used in the fast lane of the motorwa safel and legally.

Nothing new to learn -it must he as simple as making a voice call, with no more than 3 key strokes to initiate, use and complete the service.

Fire & forget -it must he as rrustwonhv as ans' other service e.g. voice-mail or text messaging, there should he no need to check the contents of the message.

Customer Touch points -must be a simple single click to initiate SMT addressing.

Familiar interaction & metaphors employed by the current UI must he used.

Called Party (B') information automatically sent -No additional interactk)n, e.g. speaking or typing in a number, should be required by the customer to use the service.

Simple Deployment-An application to enable the new functionality must he available to download using a simple URL, \XAP link or short- range wireless connection e.g. Bluetooth.

I'he applicatk)n should also be updateahle b the same method.

Upgradeable -It must he possible to upgrade the product to add new features, with minimal customer intervention and with ut having to terminate the application manually Non-Intrusive -The application should not prevent another application on the handset from running and consideration should be given to events that ma impact the application e.g. how does the application react to an incoming call during SMT call set up.

Customer Insight There are many situations when someone would choose to speak a text message, as opposed to typing one or making a voice call. The common theme is that the user needs a fast, simple way of getting some information to someone and they either can't or don't want to stop what they are doing. The key insight here is that accessiig t/xJimctionaliiy and simplj/j'ing the addressing of the message is as important (if not more important) than the oice to text element (which should be taken for granted).

NB. The customer experience needs to he one button press to start the process (across any device) one click to select the addressee and the final click should be to end the phone call/recording process.

The user experience should also exploit the fact that the mohile users' text messaging and caller log ceo-system are tvpicalI limited to a handful of numbers.

Contact Number Storage The flirmat of how mobile phone numbers are stored on a mobile handset is key to delivering a text message successfully from the SpinVox system.

Certain assumptions must he made in order to determine the destination Country of a text message, if the number suhmitted to Spin'ox is in non-International format.

The following behaviours shape the assumptions that must be made, in order to resolve the destination delivery Country of a text message.

The International Business traveler Anyone that travels Internationally regularly is likely to have at least 80% of their contact list populated with International format numbers.

The remaining 20% are likely to be stored in the local format of the country the traveller resides in. It is very unlikely they will have a number stored in local format for a country they are not a resident of.

The infrequent Business traveler * Is like1 to have a mixture of International and non-international format nUml)ers * An noninternational format numbers stored on the handset will be from the country of residence.

The non-traveler The non-travellers contact list will be populated with numbers in local format from the country they reside.

There may be the odd nuniber that is stored in international format, which has been updated when going abroad on holiday, in case the need to call home.

From this we can conclude that when a customer uses SMT and the B party' nurnher arrives, as a local numher the most likely country of origin is the users home Country.

The development team faces similar issues today, with our current products, and the above assumption is used for prefixing the outgoing SMS.

It is therefore essential that the Home Country' of the user is captured somehow and associated with their M SI SDN.

SMT Application The SMT application sits in the background of the handset, waiting to be activated by a single special' button click. In order to keep the user experience the same across an' device or platform the same button must he available on any device, on any mobile platform.

Clearl i-his limits the choice of ke s available i-I) the following: Numeric (0-9) Special ke s (* # Call keys (si & terminate) This limit is actually something SpinVox can exploit; with a specific key e.g. SpeedDial #2 becoming the Spin\'ox key', much in the same way that SpeedDial #1 is the Voicemail key.

An application working in this manner requires tar less integration into each handsets functionality and for the customer it means 170 //inkinp,, no.cea;r/thg, Ito /iwi/ilin,.

For proton-ping purposes reprogramming the right hand soft ke' often used by carriers to access the \X'AP Portals, should be reprogrammed to give one button access to the SMT application.

User Interface Using a single key to get access to the functionality of SMT has the effect of simplit\ ing the user experience and vastly reducing the amount integration into numerous menu options, in each of die possible places that someone might want to send a message from.

A user could still interact with their handset to initiate a SMT message in the following scenarios, however, the single button approach means they would be moved into the SMT app.

Call Logs Contacts I\lessaging/SMS Application Through an SMT on-screen icon Navigation it should he possible to start a SMT message by pressing a single button For each of the above scenarios the user must know where in the application they are and what options are available to them The user should be able to use the application through recognisable conu-ols on the handset Entering Information The user should not have to physically enter a recipient's number as part of die IVR process; it should he automatically sent from the handset to the 1VR platform.

Information Presentation * Text used in menus should be familiar to the user * Consideration should he given to thc icon used for the SMT application (if one is required).

* Consideration should be given to colour or sound requirements that may affect the handset * Consideration should be given to the possible error conditions and how these will he displayed or announced e.g. audio not captured, conversion not possible, 11) text message not sent.

Caller Access -Contacts 1. Caller selects a contact from the contacts menu 2. Caller is presented with a menu option to SMT 3. When the SMT option has been selected a connection to a voicemail platform needs to be established 4. An announcement requesting the user to speak their text message will then be played 5. The caller will leave an audio message.

6. The B Parts' number should be passed to Spin Vox (Selected in Step 1) 7. The SpinVox platform will convert the audio to a text message for onward delivery.

Caller Access -Call Log I. Caller selects a contact from die (Call Log.

2. (Caller is presented with a menu option to SMT 3. When the SMT option has been selected a connection to a voicemail platform needs to be established 4. An announcement requesting the user to speak their text message will then be played 5. The caller will leave an audio message.

6. The B Pam-number should he passed to SpinVox (Selected in Step 1) 7. l'he Spin Vox platform will concrt the audit) to a text message fin onward deliver) Caller Access -Soft Key I. Caller selects a SMT soft key and is directed to Contacts where a contact is selected.

2. Caller is presented with a menu option to SMT 3. When the SMT option has been selected a connection to a voicemail platform needs to be established 4. An announcement requesting die user to speak their text message will then be played 5. The caller will leave an audio message.

6. The B Party number should be passed to Spin\'ox (Selected in Step 1) 7. The SpinVox platform will convert the audio to a text message for onward delher Caller Access -Messaging Application 1. Caller selects Messaging/SMS application and selects SMT option fr m menu and is directed to Contacts.

2. When the Contact has been selected a connection to a voicemail platform needs to be established 3. An announcement requesting the user to speak their text message will then he played 4. The caller will lease an audio message.

5. The B Pam number should he passed to Spin\Tox (Selected in Step 2) 6. The Spin Vox platform will convert the audio to a text message for onward delivery Handset user experience * 89 Thc Figure 24 screen shots denmnstrate the ideal user experience: the Fast Address list of recent contacts (people that have called, been called, texted, emailed etc) is selected, the one individual (David Wood) is selected to automatically initiate a connection to the SpinVox voice conversion system so that the user can speak a message. This is easy to replicate across all chosen devices, to provide a consistent user experience.

End-to-end user experience The Figure 25 diagram below shows the end-to--end experience from the A & B party perspective.

1. Suzs holds down the SMM soft-ke on her handset and is presented with the last 5 contacts that she contacted, either by text message, email, MMS or voice, in her Recent' list. She also has the option to select any other Contact if the person she wants to contact is not presented in the list.

2. She selects the contact she wants to send a message to and a message on the screen of her device tells her that the SmT service is being contacted and to listen for an audio prompt.

3. The SpinVox Service is contacted and A par' information is sent to the SMM service.

4. B parry inib is converted for transfer to the SpinVox Service.

5. Once the connection is estahlished with the SMII sen-ice the DTMF B party info is sent.

6. The voice to text conversion takes place and the B party receives the text message.

7. The B par-replies to the original message.

8. The A parry can choose to speak another reply or use a keyboard hased method to reply.

Handset Support / Target Platforms The following platforms will be supported in subsec1uent versions.

* Windows Mobile 5 * Windows Mobile 6 * RIM OS 4.1 and above (ReJetrrnr Blackberry device models and OS versions) * S rnhian Series 60 (2ut1 Edition) * Ss mbian Series 60 (3rd Edition) * Java MIDP 2.0 capable devices Application Provisioning The option to pre-provision handsets with tile application prior to issue/despatch is possible, as is a simple mechanism for downloading the application for users with existing handsets, options include: * Bluetooth * WAP link * Memors Card Consideration should also he given fin removal of the application from the handset.

The Figure 26 to 31 screenshots demonstrate only a small part of the Speak-a-Message application. it shows the functionalits of a customer choosing to speak a text message to an individual. It does not cover, sending to more than one person, or sending messages directly to a web application, such as a blog.

All the screenshots below are taken from a Nokia N95 mobile phone, however the service is not restricted to an particular device.

Figure 26 shows the typical behaviour of the application in the home screen of the phone.

The application automatically takes control of a soft button in the Home screen ("Speak a Text" on the screen bottom right), allowing one button access to the Speak-a-Message functionality.

The application can also he programmed to present itself using other short cut keys, if they are available on the device. For example in Figure 27, the application is accessed using a short cut displayed as the Spin\'ox lo, after pressing the Multimedia Key' on a Nokia N95. j

Figure 28 shows the Fast Address list, which on an N95 device is liniited to the last 5 people which you spoke to, emailed, sent or received a text from or spoke a message to.

These are presented in using chronological then alphabetical order.

Speaking a message is not confined to this group of five people, any contact can have a message spoken to them h moving from the Recent' view to the Contacts' iew as seen in Figure 29.

If a contact is selected in the Contacts' view that contains more than one phone number, then both numbers are shown and the user is given a choice of using either, as shown in Figure 30.

Once the number has been selected the Spin\'ox service is contacted and the customer prompted to leave a message. The destination information is automatically sent to the Spin Vox Service and when the user hangs up the message is sent to the recipient.

Figure 31 shows when the customer connects to the SpinVox service the name of the contact heing sent the text is displayed.

APPENDIX I

SPEAKA TEXT (IVR BASED) ic features: * Messaging you can use when you can't or don't want to stop what you are doing.

* No special application is needed on the handset.

* No need to remember someone's number.

* It is so intuitive to use, it requires no explanation.

* You can send both email and SMS messages to recipients.

* You can easily update the numbers of the people you want to contact.

Introduction

This appendix details the user experience and highlights specific requirement for the Speak-a-Text product. The solution will consist of: * A dedicated phone number, voice shortcode or network access code * A Voice recognition system, connected to the IVR platform This solution provides the ability to: Speak a Message & have it delivered as Text (SMS or Email).

Listen to previously saved Voicemail messages.

The User Experience is shown schematically in Figure 32 Product Requirements 1. Service Level In order to use the Speak a text (I\7R) product the customer must have signed up for an account with Spin Vox.

Requirement The end-user will already have a Voicemail account.

The service will have an availabilit the same as that of Spin\Tox Voicemail.

Only the first 30 seconds of any message will he converted.

TAT -must be the same as that defined for Spin Vox \oicemall or Spin Vox Blast.

Language support. On the initial launch the service must support the following languages: UK English US English Canadian English Canadian French German French Spanish Australian English South African English Oninitial launch the sen-ice will be limited to retail customers onls.

2. LVR

D

An access number, voice shortcode or network access code will connect the caller directly to the Spin Vox 1VR.

The IVR tree will be changed in order to include an option to speak a message to someone.

it vil1 also contain options to have previoush received voicemail read Out' to the customer, using a text to Voice system.

The caller can then access their list of aireads registered contacts. This list will be limited to people.

Requirement The voice talent used to record an' new voice prompts must be the same as currently used on the Spin Vox 1VR platform.

The languages the IVR is recorded in must mirr r the languages available for current products.

Access to the service will be b determined b recognising the CLI of the incoming caller.

If the customers CLI is withheld they will hear the fillowing voice prompt: "I'm sorry your phone number was withheld, please call hack without withholding it".

The call will then be terminated.

The I\'R system must be capable of receiving Voice based commands, as well as DTMF commands.

The IVR system must be able to concatenate commands and names, in order to create a simple voice based user interface.

E.g. [Email] [Dan Doulton] Where [Email] is the desired deivcii-method and [Dan Doulton] is the recipient.

The following Voice Commands must he recognised for creating and sending messages: Email Mail Text

SMS

The following \oice Commands must be recognised for listening to a1read saved messages: Play Listen The following Voice Commands must be recognised for managing messages that are already saved: Play Listen Delete Sa''e 3. Billing The Speak a text service is billed per event. Meaning that each time a message is sent the customer will have their account decreniented and either a billing event will be triered resulting in a Premium SMS being sent to them or in the case of Credit Card billing one credit will be deducted from their bundle.

Requirement it must he possible to bill customers per conversion event using whichever payment system their account uses.

it must be possible to exclude customers who are defined as LJFTAs from being biiJed.

It must be possible to exclude customers who have been placed onto No conversion status, due to bad debt.

D

4. Provisioning In order to use the speak a text (IVR) service it is necessary to sign up and register the details of the people you wish to be able to contact.

This will he done using a web browser on a PC or Mac, it will not be possible to do this from a Mobile device.

A maximum of ten people can be registered at any one time. It will he possible to add or amend any of the Contacts that are stored in the customer's profile.

Requirement The provisioning system must work with all popular browsers, such as; internet Explorer, Firefox, Safari and Netscape (PC & Mac versions).

It must he possible to add up to ten peoples contact details.

The frllowing informaon is mandatory when adding a contact: First Name Last Namc Mobilc Phone number Email Address It must be possible to choose and provision a payment plan from the web interface.

Payment plan options must include credit card and Premium SMS payment types.

5. Voice Recognition Once connected to the Spin\'ox IVR it must be possible top navigate the menu system in a handsfree' mode, where it is not necessary to press a key in order to select the recipient or the type of message being sent.

Requirement The voice recognition s stem must integrate seam]esslv with the SpinVox IVR platform.

it will be possible to concatenate names and commands, such as; "Email David Ponsford" and have them understood by the Voice Recognition system, without having to leave unnatural pauses.

The voice recognition system must be able to recognise the names (First name and Last name) when spoken using the I\'R platform.

6. Reporting Requirement It must be possible to report on all messages generated by this product.

APPENDIX H VOICEMAIL TO EMAIL CONTACT PLIJGIN

Mobile Plug-In: Voicemail to Email Contact Resolution Voicemail converted to email The SpinVox Spin-mv-Vmail service replaces a customer's voicemail service, by using call forw-arding to a new voicemail system hosted by SpinVox. Spin\'ox converts the incoming spoken oicemai1 messages into text and then sends that text to the recipient as either an SMS text message of as an email message.

in addition to this Spin\'ox has created softwarc, which when loaded onto a mobile device, such as a RIM BlackBerry, recognises the incoming email message from the Spin Vox system and performs a number of actions on it prior to the email being replaced in the inbox of the customer's device.

The senders phone number is included in the email that is sent and the SpinVox software, on the device, reads this number and then searches the Address Book on the recipient's device for a match of that number. It not only checks for an exact match, it also checks fort a match against the number stored in a local format.

For example, the number +442079232854 sent by the SpinVox system will be matched on the recipients device to a real name and their contact details as found in the recipient's address book (contacts) by the following numbers: +442079232854 -An exact match +44 0) 20 79232854 -The same number in another International format 7923 2854 -The local' portion of the number The number matching is independent of the type of phone number the sender is using.

Matched numbers can include mobile numbers (07x), fixed line geographic numbers (Olx, 02x) and non-fixed line geographic numbers (05x), often used with Voice over IP (VioIP) services, such as Skvpe. In fact, any allowed type of phonc number passed to the service can be matched.

if a match is found in the recipients,\ddress hook the following actions occur.

1. The email will be marked with a special icon, or the standard icon will be niodihed to signal to the recipient that this is a different type of email -voicemail converted into email. This is very important in sorting and managing a busy email inbox and being able to find key messages by type as well as content.

2. The Name of the contact in the address hook is noted and dispIa ed in the From: field of the email. This way the user knows who it's from and the name is displayed in the format that they're familiar with and have recorded in their address book.

e.g. call from +447812101742 would be resolved to Daniel Doulton with the associated email address being DANIEL.DOULTONc SPINVOX.COM 3. The from Field of the email now contains the caller's actual email address too enabling the recipient to also reply by email, not just a phone call or SMS (if the senders mobile number is also stored in the Address Book).

in the body of the email the pbrase You have just received a new voicemail from' is appended with the name of the contact, enabling the recipient to reply h a call or SMS (if the senders mobile number is stored in the Address Book).

4. Whether the phone number is resolved or nor against a contact in the Address Book, the subject line is replaced with the first 30 characters of the converted message, prefixed with Spin Vox:" e.g. SpinVox: "I-li Dave. We're on for 7.30 at..." 5. A QuickLink (see GB2420942B, the contents of which is incorporated by reference) is inserted at the end of the body of the email, which will enable a simple, one click method for the recipient to listen to just that voicemail message. The link calls the Spin\'ox voicemail service, then unicluel finds that specific message and immediately plays it back.

For Example. "Click here to listen" is shown. The user selects this within the message and they are taken to the SpinVox voicemail scrvicc and that precise message is played back, without the user having to do anything else. I0

Embedded menu items Additional functionality is brought to the device, by adding new menu items into the standard menu tree.

Listen': offers the abilitr to' hear the original voicemail message, simply by clicking on the menu item, when reading a converted voicemail message.

Call Support'; will instantly connect the customer to the Spin\Tox Customer Care team, allowing them to discuss their account status These menu items are embedded dynamically. They become available when a customer is viewing a converted voicemail. This is to ensure they are only available when it makes sense for a customer to use them and not when it might cause confusion.

Asymmetric messaging This plug-in creates a unique new set of options for the user and recipient to continue in contact using a range of connected messaging options: Incoming call ends in an email.

What makes this service unique is that the original message originally started life as a spoken message and when it is finally delivered to the end customer's device it not only appears in the Inbox of their devices message application, it has been transposed into an email and it contains a valid From: held, which, depending upon the contents of the recipients Address Book, will provide a reply path via email.

Incoming call replied to by an email th creating this service Spin\'ox allows the recipient of the original voice message to choose to reply hs email, rather than hy traditionall having to call the sender of the message using the telephone. This is unique in that once the recipient replies to the original message via an email the end-to-end communication method has moved from being oice drien to email driven and once the reply is sent to the originator the too can then reph via an email.

Summary of key features

* Conversion of an incoming phone call to an email.

* Resolution of senders telephone number against contact name and email address stored on recipient's mobile device.

* Email Repls path available to originally spoken message.

* Listen to specific oicemail messages using a single button press.

* New functionality embedded in the standard menu tree.

* Communication moved from voice to email.

Voicemail-to-email Business Requirements

Introduction

This section presents the business requirements that will enable users of email centric devices, such as RI M's BlackBerry with a simple variation of the standard Voicemail-to-Text service.

The BlackBerry is primarily used as an Enterprise business tool for PIM synchronisation and reading and responding to emails, this will be reflected in the business requirements detailed in this document.

An Enterprise customer can deplos the BlackBerr solution through any one of the following deployment models: in BlackBerry Enterprise Solution -on premise implementation of a BES (BlackBerry Enterprise Sen'er BlackBerry internet Solution -internet based service offering can he used with web-based email proiders such as Gmail, Yahoo as well as proiding access to the corporate email.

1-losted BlackBerry Solution -where a hosted service provider has deployed the BlackBerry platform in a data centre environment. An enterprise would purchase this solution on a per user per month basis.

This product enhancement will enable SpinVox to target both BlackBerry and mobile phone users within the Enterprise driving increased user activations as a result of more text or email messages being generated, as opposed to voice, it further enhances SpinVox positioning as a device independent service provider.

This service will also enable SpinVox to switch oft' text deilven, by default, to Blackberr users, so that duel messages are not received on the device, making significant savings to the business.

The service will enable an Enterprise to have all voice message conversions delivered as emails only (default settingi for it's BlackBerry or other email centric device users. The user will he given the option to enable SMS deliver if required.

Converted Messages A converted voice message will be issued as an email with NO \VAV file attached. The option to use the message Quick-Link to locate and listen the voicemail will also be available..

Unconverted Messages A user will be notified via email when a voice message cannot be converted. The option to use the message Quick-Link to locate and listen to the voicemail will also be available.

The service will be available across both GSM and CDMA networks and to Enterprises located in the US, Europe and Australia For email delivers it is required that the sender CU be resolved against the Local Address Book (LAB), so that the From: field is populated with the Senders real name as stored in the device's address book.

It is also required that in the email body the first line would read You received a new voicemail from John Smith'; where John Smith is the real name of the contact The user will have the capability to click on the caller's name to email a response, send a text or initiate a call.

If the number is not able to resolved against the contents of the LAB, the CL1 of the incoming number should be shown The subject line of the email will be contain the first 32 characters of the converted message prefixed with Spin\'ox: The service will be tested against the following deployment models with: BlackBerry Enterprise Solution (BES Ver 4.0) BlackBerry Internet Solution Hosted BlackBerry Solution The service will be tested against the fillowing devices as a minimum: Pearl 8100 BlackBerry 8700 BlackBerry 7130 BlackBerry 8707 The application must be compatible with RIM (iS version 4.1 and above.

Modifications will be required to the following business support systems: SpinVox \X'ehsite -A user should he given the option to identify themselves as a user of an email centric device, such as a BlackBerrs-and should then he provisioned against a specific service profile i.e. Email only delivery as default, Converted messages sent without audio attachment, Unconverted messages sent with audio file attached A link to a downloadable application will be available from the SpinVox.com website.

Customer Care Interface -Modified to include a BlackBerry sen-ice profile Enterprise Web Self Service Tool -Will be modified to capture device type as BlackBerry and provisioning against a BlackBerr service profile.

Screen shots The fi)lluwing screenshots show how the service wil] actually work, once a voicemail has been left for a customer and the message converted to text and the email sent to them.

All the screenshots below are taken from a BlackBerry device, however the service is not restricted to an particular de ice type.

Figure 33 shows the apical behaviour of an email centric device prior to the SpinVox plug-in software being installed. The From Field and Subject give no indication of wither who the message is from or what the message is about. It is also impossible to distinguish between a standard email and a converted voicemail message, as the message indicator icons are identical.

Figure 34 shows how the Inhox looks after the SpinVox plug-in has been installed. The default email icon has been replaced b a special icon, which shows that the message is a Spin Vox voicemail message. The From: field has been replaced b the real name of the sender, as stored in the recipients Address Book on the device and the subject line has been changed to include the first part of the converted voicemail message, prefixed with SpinVox:" which enables the message to be sorted and grouped with other SpinVox email messages.

Figure 35 displays how a SpinVox voicemail message will look once the recipient has opened it. The Sender's phone number has been compared with all the numbers stored in the recipients Address Book and as a match has been found the real name of the sender is displayed in the From field. In the example below the real name is Vadiraj Patel.

The subject line has been changed to display the first part of the converted message prefixed with SpinVox:" Figure 36 shows what happens when a customer clicks Ofl the real name that has now been put into the From: field, it is now possible to rcpl directh via email to the sender of the message, b clicking on Email \adiraj in the menu. It is important to remember that the original message was a spoken message that has been replied to via cniail, moving the communication method from voice to screen.

Figure 37 show s what happens when a customer clicks on the real name that has now been put into the mesage text in the section which starts You received a new oicemail from' It is now possible to reply directly via SMS, MS or voice to the sender of the message, 1)\ clicking on the appropriate menu item. It is important to remember that the original message was a spoken message that is being replied to via SMS or MMS, moving the communication method from voice to screen.

Figure 38 shows an example of a QuickLink, which has been inserted at the bottom of the converted email message. The QuickLink gives a simple and eas) one-click method of listening to the original voicemail message the customer is currenth' reading. It dials the Spin\'ox voicemail service and automaticall replays the C)rrect message.

Figure 39 shows how additional functiona]itv has been added to the device with the inclusion of new menu items. These new menu items have been embedded into specific places, to ensure their functionality is only shown to the user, when it is of use to them. If it were presented all the time, it would lead to a lot of confusion.

Appendix III VIRAL/LINK CAMPAIGNS This section describes viral or link marketing methods used to spread and market Spinvox products.

* Refer a friend (RAFiO 0 SpinKey: U Call your own mobile from your mobile We then know you're attempting a special call * "Please enter sour friend's mobile number" o Type it in, or if a power user, look it up in contacts and hit Call/Send -DTMF to us o "Thank you. Activation codes have been sent to you and your friend" o This means you have their activation code on screen and can help them through this fuggv process or...

o Call your voicemail box -new 1VR option o Call 84004 (we're going to get the voice enabled) 0 Text your friend's mobile to 84004 Call your own voicemail hox/84004 and leave a message: "Sigti up 07812101742" * SpinDemo: o Call your own mobile from your mobile * 5V IVR hut this time enter * then friend's number, now you speak them a text APPENDIX IV Unified Communications This market, and its derivate Unified Messaging, has tried to unif all (>1 a users' communications into a single in-box for them to manage, typically in email format and accessed from your PC.

The issue is that: o It's only accessible from one point -your email inbox or a web page meaning ou need to be at a particular point in such as our desk, to access your communications. This doesn't help the ever increasing mobile workforce that is estimated to be away from a desk over 50% of their working day.

o Any audio (voice messages) which may now appear as attachments to an email or other format, still require ou to listen to them, write down key notes and in effect do the work. In short, it's not transformed into a medium that is synonymous with the task -keyboard, screen, 1P based messaging that it came in as. So the user has to he at their PC, listen to messages and do the work of ansforming this into sa) an email repl or notes for a colleague.

o To deploy UC services requires dedicated hardware and software and t-picallv are an expensive 1T upgrade cost to deliver and then need maintaining.

SpinVox solves these issues ver neatly by converting all voice messages into text and distributing them to any device immediately: O Spin\'ox uses existing network services and call management features to unify your voice messages, typically voicemail messages, by either diverting calls to a single voice mail l)OX, or collecting the voicemails from different voicemail boxes. These voice messages are then sent to the Spin Vox \MCS for conversion into text. There is no need for any new IT hardware or software or complex systems management.

o For users, there's no need to work through what can be complex decisions on call management or messaging configurations, typically based on time of day and day of week in order to ensure that the caller gets a message to you. By converting any voice message to text, users can instantly receive and see all their messages regardless of where they are and where the message came from -e.g. desk phone, cell phone, switchboard, home phone, etc...

o Once the messages are in text, they are in a format that is now synonymous with the medium in which they are intended to he managed -namel SNIS, IMS, email, IP, Web formats. Spin\7ox can deliver the output text to your email inhox, a web page/service or as a mobile text message in an form. Now the user can choose whether to call or text/mail back or manage this information for colleagues or friends in the format most suited. And because it's in text format, it's immediately indexable and searchable which leverages the power of computers to improve information management and retrieval.

o B undertaking this transform (conversion), SpinVox removes all the existing limitations of tiC services and allows the message to not only be delivered to a single point (your inbox/PQ, but also as text to any dec-ice am-where solving the land-lock' problem of most UC design. This means users can now undertake the key tasks that UC promises. but from wherever they are and at any time.

The reason that unifying voice messages from different sources (mail boxes) makes sense and creates real value is because it the most disparate and difficult for users to access and manage.

Email is already largely unified and in a good format for indexing, storage and management, and increasingly accessible from mobile (Blackberry).

Figure 40 shows how Spins-ox unifies various communications types and channels.

The power of using SpinVox is that mu can seamlessly connect for the user (i.e. the UI level) what are traditionall' disconnected ss stems' (e.g. voice, blog, SMS, email, etc...) bs both standard call management features (diverts/forwards) and b converting the voice message into text, thereby overcoming the technical barriers that would otherwise exist between different communications systems.

Appendix V Voice SMS Spin Vox Voice SIMS allows people to speak a voice message and have the recipient notified b SMS, recpaesting them to then call a number and listen to the message.

The senice overcomes issues of language and literacs around text messaging, opening up new revenue streams for wireless Carriers without an' additional investment in either infrastructure or handset features. It is more cost-effective and discreet than traditional voicemail, and niore expressi e than traditional SMS. 11)

Spin\'ox \oice SMS provides the following end user benefits: * New, highly personal way to communicate * (Typically) costs less than a voice conversation * Easy to use * Overcomes text usability issues * Available in all languages * Does not require literacy * Less hassle than typing an SMS 21) * \\ orks with current handsets * No end user training required As there is no barrier to entry, and making a phone call is natural behavior for a wireless user, this product has mass appeal to the entire Carrier user base.

Product Overview Product name Spin\Tox Voice SMS Description Allows a spoken voice message to be deposited from an mobile handset and a notification sent to the recipient b SMS. The recipient can then dial a QuickLink short code to listen to the caller message.

Originating Network GSM and CDMA Terminating Network GSM and C1)MA Voice SIS works much like SMS, instead of sending text, callers can easily send voice messages, using expression to convey more information than text alone. For the called party the service is easy to use and acids an emotional dimension to messaging.

D

A caller simply prefixes a standard mobile number with a short code e.g. , the service records the voice message and sends an SMS notification to the called parts who can then rcpla the uice message b simpl clicking on a QuickLink short code e.g. *3 SpinVox Voice SMS will generate an incremental sustainable revenue stream for Wireless Carriers without cannibalizing existing services. The availability of \Toice SMS creates new situations where people can use messaging, where they would not have thought to use it previously. Subscribers are using \Toice SMS to convex more emotional messages in a way that text-based messaging cannot achieve.

The user experience will he natural and straightforward -the calling party makes a normal voice call, prefixing the mobile number with a short code to initiate a session with the Spin\'ox Voice SMS platkrm. The calling party will reach an IVR, which will prompt them to speak their message and then simply select the send option from the IVR.

A typical voice message is expected to he a short duration intentional message. The maximum recording duration will he limited to 30 seconds.

The product must meet the following criteria: 1. No behaviour change in many developing counties literacy levels may be low as vell as the inability of the SMS interface to handle local languages -in these cases sending voice instead of text is a more relevant service proposition. Sending and retrieving a Voice SMS must he as simple as making or receiving a normal voice call.

2. Easy & inexpensive to deploy The appeal to Carriers is that service deployment should not require an infrastructure upgrades to their net-vork. The service should l)e capable of being deployed within 8 weeks.

D

3. Universal service offering An' customer should he able to use the service on any handset, without the need for an pre-provisioning or handset configuration. This will help drive mass-market penetration across the Carrier's user base.

I U

End-to-end user experience Figure 41 shows the end-to-end experience of Spin\Tox Voice SMS service: 1. Calling Party interaction with WR It is envisaged there will be minimal interaction between depositing a message and the Voice SMS platform. The calling pam' will he presented with options to send, re-record or cancel their Voice SMS.

Language to use Voice SNIS is a standalone integration; it will not require integration with the Carrier voicemail platform.

The Voice SMS platform will support multi-lingual prompts in the following languages: o Arabic o French o English o Persian o Hebrew o Standard Chinese o Bahasa Indonesia o Japanese o Korean o Filipino o Sinhala o Thai o Vietnamese o Spanish o Portuguese Initial voice prompt The calling party will hear the following intro after the Voice SMS service has dialled and connected to the IVR: "Please record your message after the tone" Press I to send this Voice SMS Press 2 to re-record this \oice SMS Press 3 to cancel this Voice SMS Message too long prompt 11 a caller goes over the time allowed to deposit a message they will be prompted to re-record the message or leave the message as is.

End of message warning \ hen the caller is approaching the end of the recording time, a series of beeps shall be played, getting closer together as the get closer to the end of the message prior to Req 1.4 prompting the customer Forecast The Carrier will provide a volume forecast for Spin\'ox Voice SMS service Support Technical support for the SpinVox Voice SMS service will he covered by the support agreement, as outlined in the Carrier contract.

Storage The \oice SMS platform will provide storage of the voice message audio. As standard the audio file will be retained for a period of 5 days. Audio

The sent voice message audio will not be accessible to the calling party SMS delivery to recipient When a voice message has been successfully deposited an SMS will be send to the intended recipient. The tllowing requirements cover only this SMS.

SMS to the B Party The tcxt message must he sent from the originalcalling parts-phonc number. If this CL1 is withheld then Withheld' will be presented to the called parr.

Message body The body of the message will be specified as part of a new Message Classification template fir that Carrier.

Note this will include a Spin Vox message tag of Spoken through Spin Vox' Message Retrieval -QuickLink Message retrieval will he via a QuickLink short code e.g. *3* will retrieve the 3rd message 2. Recipient interaction with IVR Once the recipient has listened to the voice message they will he presented with a number of additional options to manage their Voice SMS experience. These are outlined below: Mailbox Configuration Each VoiCe SMS recipient will be allocated a virtual mailbox. The Carrier will specify the capacity of this mailbox however it is recommended this is no more than enough for 5 messages for a given time period e.g. 5 days.

IVR -Retrieval of old messages A recipient must be able to listen to old messages stored in their mailbox. L1FO message playback will be used.

IVR -Share the voice SMS A recipient must have the option to forward their Voice SMS to another user.

This option will be available from the IVR e.g. Press 4 to share this \Toice SMS Enter the recipients number followed by the hash ke IVR -Deleting voice messages A recipient must have the option to delete a voice message IVR -Skip to next message A recipient must have the option to skip to the next voice message IVR -Repeat voice message A recipient must have the option to rewind to the beginning of the current oice message IVR -Replying to a Voice SMS A recipient must have the fillowing reply options: o Rcpl to A Party via \7oicc SMS o Reply to A Party via voice call IVR -Saving a Voice SMS A rccipient will be gh en the option to save a Voice SMS 3. Service levels Sign-up requirements The caller should not have to sign up with the Carrier to use this service -all they should hae to do is dial a call prefix followed by the recipient number Compatibility The calling party will require the capability to dial a call prefix number e.g. * Pricing Depending upon the Carrier pricing model a \oice SMS can be a premium to a standard SMS. As such the calling part ma have to be greeted with a pre call announcement advising the cost of Voice SMS delivery.

The Carrier may also include a number of free messages prior to charging.

Service Level The set-vice should meet the same availability i-equiremcnt as rbc Spin\'ox service i.e. 99.99% Recording time The recording time must be limited to 34) seconds duration.

The caller will he notified via an appropriate oice prompt if tbe base exceeded the 30 second recording limit.

Number of SMS supported All SMS deliveries should be limited to I SMS 4. Carrier Interoperability The SpinVox \Toice SMS service must be interoperahie with alternative Voice SMS proiders thereby enabling a \Joice SMS to be sent to recipients regardless of the Carrier service they are using.

Inter-Carrier Interoperability 3 party Carriers should be able to interconnect to the SpinVox Voice SNIS service via a SpinVox specified API or through appropriate GSM Association standards SpinVox-SpinVox Interoperability lnteroperabihtv will be available between those Carriers that have soleh deployed the SpinVox \7oice SMS service Intra-Carrier Interoperability A single Carrier deploying multiple instances of Voice SMS must he able to interoperate between instances Commercial A commercial framework will be specified supporting inter-operator accounting 5. Platform Requirements The set-vice plattorm must he capable of delivering the Voice SMS as a managed service offering. Carriers must be able to easily introduce new Spin\'ox services such as Spin\'ox Messenger and Voicemail to their user base without major changes to infrastructure.

D

Record & Playback The \oice SMS platform must have thc ability to record and playback messages deposited by unique callers Voice Prompts the \Toice SMS platform must have the ability to play multi-lingual I\TR prompts DTMF Tone Recognition The Voice SMS platform must have the ability to recognize touch tone ke presses Platform Availability The Voice SMS platform must support a high availability architecture to ensure a maximum uptime of 99.99% Inter-Carrier Accounting The Voice SMS platform must have the capability to record and report on inter-Carrier traffic supporting Voice SMS interconnectivitv between Carriers SMS Formats rhe Voice SMS platform must have the ability to construct and format an SMS and interconnect to a Carrier's SMSC infrastructure 6. Demo There must be the capability for the \oice SMS product to be demonstrable to the Carrier by Spin Vox. The Carrier should also be able to set up a demo of the product for their customers to market the service.

SpinVox Website -Demo it should be possible to demonstrate the Voice SMS service via the Spin\'ox website Carrier -Demo Spin Vox require a wa to demonstrate the Voice SMS service to a Carrier as part of the sales process Carrier -Demo charging It should be possible for the Carrier l)emo to be free of charge to the caller Carrier -Customer Experience The SpinVox Demo should provide the same customer experience as the Carrier product 7. Reporting it will be necessary to report on service activit. The audience for all SpinVox Voice SMS reporting will be both internal to SpinVox and external, Carrier lacing. \Vhere SpinVox is 5)ffering an interconnect capabiliti to specific Carriers then detailed inter-Carrier reports must be provided.

Reporting requirements it must be possible to report on all messages on this ser ice Reporting requirements it must be possible to report C)fl the tollowing product metrics.

* Users by Carrier * Traffic by Carrier * Average audio length Reporting requirements It must he possible to report on the following metrics, where user is defined as the phone number calling the service (i.e. tbc CLI).

* Frequency * Traffic * Average audio length 8. Billing Billing Requirements SpinVox must have the hilling capahiit to support pa per message/bundled pricing models Invoicing Requirements It must be possible to invoicç the Carrier on a monthly basis for the service 9. Future phases Future enhancements in a future phase, it must be possible to extend the service to fixed line. The following call scenarios will be supported: o Fixed line to mobile o Fixed line to fixed line o Mobile to fixed line Note: a fixed line recipient would receive ringing tofle, after lifting the receiver they would hear the voice message Future enhancements in a future phase, it must he possible ftr the called party to receive Voice SMS delivery via email Future enhancements in a future phase, it must he possible for the caller to send a Voice SMS to multiple recipients (Options include the use of a web portal for setting distribution lists/address book management or through the use of Voice SMS handset application) Future enhancements In a future phase, it must he possible for a caller to send a reserved Voice SMS i.e. at a specified date and time.

APPENDIX VI Acronyms The following is a guide to the normal meaning (if the following acronyms.

ACR -anonymous call rejection Al -artificial intelligence ASR -automated speech recognition CIA -caller line identification CPU central processing unit db -database DDI -direct dial-in DTMF -dual tone multi frequenc G728 -This is specified in ITU-T recommendation G.728, "Coding of speech at 16 kbit/s using low-delay code excited linear prediction".

HTTP -hyper text transfer protocol IM -instant messaging IP -internet protocol iSO -international standards organisation IVR -interactive voice response 21) MM -multimedia messaging MMS -multimedia messaging set-vice MoBlo -mobile blogging

MSF -mail summary file

MSISDN -mobile station integrated services digital network N /0 -network operator OTA -os er-the-air p -pause RAS -Repeat Audio Submission Q -quality QA -quality assurance QC -quality control RAF -refer a friend ROM -read-only memory S-Links -spoken links, or smart links SAT -speak-a-text SDIC -software development toolkit SIP -simple internet protocol SLA -software licence agreement SNIPP -short message peer-topeer SMS -short message service SNFrP -simple mall transfer protocol S( )AP -Simple Object Access Protocol it) SSL -secure sockets layer (a communications protocol) SV-Spin Vox TAT -turn around time TLP -transaction layer packet LU -user interface U1D -unique identifier URL -uniform resource locator \AS -value added service -\odafone -video game \7N12T -voice mail to text \MCS -voice messaging conversion system VMP -variational message passing -voice over internet protocol \X"AP-wireless application protocol

Claims (26)

1. A method of posting to a web site, the method including the steps of: (a) a user operating electrical hardware to initiate communication with an electronic address associated with a web site with user generated content; (b) the user speaking a message which is then converted to text and provided to the web site; (c) the text based message being posted or otherwise displayed on the web site.

11)

2. The method of claim 1, in which a message alert is sent to users of the site, alerting them to the new posting.

3. The method of any previous claim, in which the electrical hardware is a mobile phone.

4. The method of any previous claim, in which the electronic address is a telephone number.

5. The method of an' previous claim, in which the message alert is a SMS, email, or 1M.

6. The method of an previous claim, in which the message alert also provides the user message contents.

7. method of any previous claim, in which the message alert provides a link which permits replying to the message alert by the steps of: (a) displaying the link in the message alert; (b) the message alert recipient selecting the link; (c) the message alert recipient being connected to a conversion system; (d) the message alert recipient speaking a reply which is then converted to a text based reply message b the conversion system; and (e) a destination associated with the link receiving the reply message.

8. The method of any of Claims 1 to 6, in which the message alert provides a telephone number, which allows the message alert recipient to respond by an' of: speaking a message which is converted to text, by texting, by emailing or by IMing.

9. The method of claims 7 or 8, such that the message alert recipient's resp)nse is added as a thread to the original posting, so initiating a dialogue.

10. Th method of any previous claim, in which the method is used in hlogs.

11. The method of claim 10 in which the blog owner has a dedicated DD1 phone number a blogger calls.

12. The method of claim 11, in which blogs left on this number are converted to text and then emailed to a blog email address, the blog posting appearing with the correct formatting for that blog.

13. The method of claim 11, in which blogs left on this number are converted to text and then posted directly to the web site, the blog posting appearing with the correct formatting for that blog.

14. The method of any of claims 1 to 13, in which the web site is a Mobile Photo Messaging site, permitting annotation of an image.

15. The method of claims 1 to 13, in which the web site is a Mobile Photo Messaging site in which the user additionally supplies an image.

16. The method of any previous claim, in which the website provides content which may be subjected to a further method which is a method of generating useful, related links in the text posted on the website, the further method including the steps of: (a) parsing the text posted on the website; (b) locating one or more keywords in the text posted on the website; (c) generating a link for the or each keyword; (d) displaying the text posted on the website together with a link for the or each keyword on electrical hardare [hr viewing bs the website users.

17. The method of claims 2 to 16, in which each registered user receives the message alert in the format they have previously selected.

18. The method of an' previous claim, in which the website topic is one or more of personal profiles, news, films, theatres, gigs, art exhihitions, pubs, bars, restaurants, clubs, hotels, reviews, or current affairs.

19. The method of any of claims I to 13, in which an interface associated with the website routes incoming messages to the topic intended by the user.

20. The method of any previous claim, in which the text based message is automatically shown as being posted by the user, with that user's correct name or handle.

21. The method of an)' previous claim, in which the text based message is automatically shown as being posted with other information appropriate for the web site.

21)

22. The method of claim 21, in which the text based message is automatical1 shown as being posted with the correct time and date of posting.

23. A system which facilitates posting to a web site, the system adapted to: (a) permit a user operating electrical hardware to initiate communication with an electronic address associated with a web site with user generated content; (b) convert into text a message spoken by the user, the text based message then being provided to the web site; (c) post the text based message on the web site.

24. The system of claim 23, in which a message alert is sent to registered users of the site, alerting them to the posting.

25. The system of claims 23 or 24 adapted to enable the meth)d of an) preceding claim I - 22 to be pertbrmed.

26. A mobile telephone when used as the elecüical hardware of Claims 23 or 24.