Untitled record

(54) Title: METHOD AND SYSTEM FOR ANSWERING ELECTRONIC MESSAGE AND RESPECTIVE MESSAGE, AND MOBILE PHONE (30) Unionist Priority: 01/09/2007 GB0700376.7, 09/01/2007 GB 0700379.1, 12/02/2007 GB 0702706.3, 04/05/2007 GB 0708658.0 (73) Holder (s): spinvox Limited (72) Inventor (s): daniel michael doulton (74) Attorney (s): Marcas e Patentes Ltda symbol (86) International Request: pct GB2008000047 of 09/01/2008 (87) International Publication: W0 2008 / 0842i3de 17/07/2008 (57) Abstract: method and system for answering ELECTRONIC MESSAGE AND THE RESPECTIVE MESSAGE, AND MOBILE PHONE. For dealing with the invention of a link, called X-LinkTM, placed in a message (SMS, MMS, email, etc.) that is sent to a user and displayed on his device (for example, mobile phone). When the link is selected by the user, it connects the user's device to a conversion system, allowing the user to speak a response that is then converted into a text-based response message; the reply message is then sent to the sender of the original message (and / or to another appropriate recipient). This approach allows a text message to be answered by voice: it is an example of asymmetric communication. There are many circumstances in which this approach is very useful - for example, when the message is an SMS and the recipient does not know how to respond using SMS, or when the recipient is in an environment where it is difficult to respond (perhaps walking or driving) ).

Recipient: Reply Voice-to-Text or SaT

<img file="BRPI0806206A2_D0001.tif" />

Pr OW

1/129

METHOD AND SYSTEM FOR RESPONSE TO ELECTRONIC MESSAGE AND THE RESPECTIVE MESSAGE, AND MOBILE PHONE

Technical Field

The present invention relates to a method and system for responding to an electronically received message; the message being sent from an original sender to a user who receives the message using electrical hardware. Electrical hardware includes, without limitation, mobile phones, smart phones, communications, wireless messaging terminals, personal computers, computers and devices for specific applications. It also includes devices capable of communicating in any mode over any type of network, such as GSM or UMTS, CDMA and WCDMA mobile radio, Bluetooth, IrDA etc.

Description of Prior Arts

In previous arts, exchanges of messages and communications are generally symmetrical - that is, you either exchange texts (SMS, email, Fax, letter) or you talk to the other person. You rarely mix the two modes in the same message exchange. If someone sends you a message, you don't reply with an email.

Sending SMS, e-mail and IM (instant messaging) texts is highly popular. But, as these are fundamentally symmetrical forms of communication, once someone sends you, for example, an SMS, the normal way to respond is with a reply SMS. For many people, the voice remains one of the preferred communication mechanisms, but it may be inappropriate to respond to someone who sent you an SMS with just a callback: the natural assumption is that she has sent you an SMS because it was the preferred type of messaging (perhaps she was in a meeting, driving, etc., or simply prefers SMSs) and therefore calling her over the phone would 'break' the protocol established by the SMS sender. A large number of consumers also need to learn how to send SMS messages; their inability to respond adequately is not only frustrating for them, but it also clearly means a loss of income for telecom operators.

The method of converting a mobile phone user's voice messages to text is known, and this text is then sent

2/129 as SMS or email to the user. This method is described in more detail in WO 2004/095821 A2, for SpinVox, the content of which is incorporated herein by reference.

SpinVox therefore performs an asymmetric form of communication: people can speak messages that are converted to text and sent as text to the recipient of the message. This influences the growing capacity of mobile phones for both voice and display: speech to leave a voicemail, doing what a mobile phone does best (which is voice communication); and then the text to display an incoming text SMS (which is a quick and non-intrusive way to receive the message sent).

A feature implemented in the SpinVox service, which converts voice messages into SMS text messages, is a link contained in the SMS text message that allows the recipient to directly access and listen to the message - QuickLinks ™ (see document GB2420942B, the content of the which is incorporated herein by reference).

The present invention has as concept a link embedded in a text message and the construction of a response mechanism to a new message around it.

Description of the Invention

The present invention consists of a method and system for providing a response to a received message, which was sent from an original sender to a user who receives the message using electrical hardware, the method including the steps of:

<td></td><td>(The)</td><td>display of a link in the received message;</td>

<td></td><td>(B)</td><td>the user selecting the link;</td>

<td></td><td>(ç)</td><td>the user being connected to a system of</td>

<td colspan="3">conversion;</td>

<td></td><td>(d)</td><td>the user speaking an answer which is then</td>

<td>converted into</td><td colspan="2">a text-based reply message by the</td>

<td colspan="3">conversion, and</td>

<td></td><td>(and)</td><td>the original sender of the message, or another</td>

recipient associated with the link receiving the text-based reply message.

3/129

A link, called X-Link ™, is placed in a message (SMS, MMS, email, IM, WAP - or in any other message, document or image or sound file, etc.) that is sent to a user and displayed on your device (for example, mobile phone). When the link is selected by the user, it connects the user's device to a conversion system, allowing the user to speak a response, which is then converted to a text-based response message; the reply message is then sent to the original sender of the message (and / or to another appropriate sender).

This approach allows a text message to be answered by voice: it is an example of asymmetric communication. There are many circumstances in which this approach is very useful - for example, if the message is an SMS and the recipient does not know how to respond using SMS, or if he is in an unfavorable environment (possibly while walking or driving).

The original message can be converted from the voice, but it does not necessarily need to be converted. When converted, the effect is to transform voice messages into a complete exchange of two-way messages.

The reply text can be converted into any format (SMS, e-mail, IM, etc.) that the original sender of the message defined as being of your preference.

In situations where an original voice message has not been converted to text, there may only be a notification that a voice message has been received, along with a link to listen to it. This is a very valuable product for developing economies, for which a low-cost product suitable for all intellectual levels is needed.

This approach works with different messaging products - for example, original messages can be in SMS format, but the returned text can be an SMS, an email or vice versa.

All links can be unique addresses of some kind - for example, a phone number, an email, an IP address, IM, VolP, etc. Each link can be formed from a service number (which acts to access the conversion system) and a unique identifier (which acts to

4/129 identify the original sender of the message).

Alternatively, the link can be a word or 'click to call' words.

Alternatively, each link can be a virtual number (a complete number that ends in the network and is then mapped over the network in real numbers associated with the end user's equipment).

Unique addresses can act as implicit address books. For example, each user can have their own list of X-Links, each X-Link being associated with the MSISDN of a person who sent a text to that user. The individual X-Links can be deleted, if desired.

X-Links can be saved in an address book since X-Link is associated with an MSISDN, the X-Link call initiates a normal voice call; in the same way, the user can send a text to X-Link. Selecting an X-Link can cause a communication application to start (for example, VolP).

X-Link can allow any device to be used to make a text message appear on a recipient's screen: non-subscribers to SpinVox can also respond to a text message by speaking the message that is then converted.

The implementation of the present invention can be based entirely on networks and use existing network services / technologies.

Brief Description of Drawings

Figure 1 shows a spoken text message from 'Dan Mobile'. It includes the X-Link 8400p123 in the message.

Figure 2 shows how to use the XLink address book. Anyone who receives a spoken message as a text can now call and listen to the original voice message that was left for them.

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

Figure 4 shows that the message sender Zac Sandler left a voice message that was automatically converted to text using SpinVox's voice conversion system.

Figure 5 shows another variant, in which links are embedded in the message, with the address' 20E &amp; 9^th St 'in the body of

5/129 message being selectable to start the map browser, showing this address.

Figure 6 shows schematically the transformation of the business model and how SpinVox itself positions itself as an intermediary between the consumer and the search engine based on aggregate advertising, such as Google.

Figure 7 shows the end-to-end experience when a caller leaves a message and how the recipient (recipient) sees the message.

Figure 8 shows a photograph taken by a phone camera.

Figure 9 shows the option Speak a Comment from the Options menu, which can be used to comment on the photo in Figure 8.

Figure 10 shows an MCM with SpinVox Voice Mail for Text, also implemented.

Figure 11 shows how several conventional message exchange products (voicemail, e-mail, SMS, IM and voice) are distributed along Time versus Dialog axes.

Figure 12 shows how various SpinVox products change the landscape in Figure 11.

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

Figure 14 shows an example of an implementation of a Spoken email with a French mobile service provider - standardized telephony and synchronized data.

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

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

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

Figure 18 shows the typical user experience

6/129 speaking a message from within a Speak a Message application.

Figure 19 shows the typical user experience for Talking on a Blog.

Figure 20 shows the typical experience of a user speaking a response on a Mobile IM client.

Figure 21 shows the user's '3 clicks' experience.

Figure 22 shows the 'Disposal &amp; Ignore' system used by Speak a Message.

Figure 23 shows the Quick Address List showing recent contacts that Called, were Called, received Texts (SMS or MMS) or received E-mails (or any other processes used to exchange messages / communications).

Figure 24 illustrates screenshots that demonstrate the ideal user experience: the Quick Address List of recent contacts (people who called, were called, received texts, received emails, etc.) is selected, and the individual (David Wood) 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 perspective of group A &amp; B.

Figure 26 shows the typical behavior of a Speak-a-Message application on the phone's home screen.

Figure 27 shows the application being accessed using a shortcut displayed as the SpinVox logo, after pressing the 'Multimedia Key' on a Nokia N95 (model 1).

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

Figure 29 shows that any contacts can receive a spoken message, changing from the 'Recent' view to the 'Contacts' view.

Figure 30 shows that if a contact is selected in the 'Contacts' view that contains one or more phone numbers, then all

7/129 the numbers are shown and the user is given the choice to use any of them.

Figure 31 shows when the user connects to the SpinVox service, and the name of the contact to whom the text is being sent.

Figure 32 schematically shows the User Experience with the Speak-a-Text product.

Figure 33 shows the typical behavior of a central email device before installing the SpinVox software plug-in.

Figure 34 shows what the Inbox looks like after installing the SpinVox plug-in.

Figure 35 shows what a SpinVox voicemail message looks like after the recipient has opened it.

Figure 36 shows what happens when a user clicks on a real name that has not been placed in the From field.

Figure 37 shows what happens when a user clicks on a real name that was not placed in the message text in the section that starts with 'You received a new voicemail from'.

Figure 38 shows an example of a Quick Link that was inserted in the footer of the converted email message.

Figure 39 shows how a new feature was added to the device with the addition of new items to the menu.

Figure 40 shows how SpinVox unifies various types of communications and channels.

Figure 41 shows the end-to-end experience of SpinVox's SMS Voice service.

Detailed Description of the Invention

SpinVox has developed a simpler and more natural user interface for exchanging messages - Voice. The exchange of messages and communications are generally, in the prior arts, symmetrical - that is, you either exchange texts (SMS, e-mail, Fax, letters, etc.) or you speak to the other person. With the conversion of free-form and user-independent speech, SpinVox transforms and enables asymmetric communications, which now change the rules of the game. It allows the exchange of complete voice messages and creates the category of

8/129 Voice-to-Screen ™ message exchange, which simply enables existing services / products and markets / users with speech input and text output from any phone or voice input device to any screen.

In doing so, it promotes the increasing asymmetric capacity of telephones: telephone reading screens (which are currently becoming good text display devices) and human speech are the most natural forms of communication and that virtually all humans in the world. planet can use and, in addition, it is with these characteristics that phones stand out. Or, put another way, phones are poor devices for text input, but excellent for voice input and respectable for displaying texts.

This transformation also makes possible the appearance of new and more comprehensive services, such as the unification of all sources of voice messages in texts easily accessible on the screen, which solve many of the complex issues of the systems in receiving two discrepant words appearing as being one (telephony or email / weó pages). And, remarkably, the display of voice messages from any source in text format, allows them to be indexed and intelligent search results embedded in them. The advantage results from the fact that the majority of searches are triggered by information communicated between the parties, and voicemail and voicemail have a high percentage of such data points. This process resolves many of the limitations of telephone input methods based on keyboards or pens, for searching traditional forms of search engines and at different stages to obtain the results. And, since this process is performed on the server side, it becomes intelligent for its context - Inteligente-paramim ™.

This Detailed Description will describe a wide variety of innovations and features of SpinVox products, in addition to the specific invention defined in the Claims.

The Key Elements of SpinVox products include the following:

X-Links ™ that enable communities

9/129 easily share the use of SpinVox services, which allow non-subscribers / users of SpinVox services to respond by speaking a text and which allow users to speak texts in different products, and not just some • The implicit X-Links ™ address book makes links appear seamlessly • Exchange network-based spoken text messages • Callback via spoken text messages • Speaks of an SMS / MMS or e-mail • Speaks of an Instant Message • Mobile participation in blogs • Mobile messaging with photos • 'Push to message' - push to talk app • All services / products are based on the 'discard and ignore' principle • They all transform existing voicemails into full, two-way messaging services and, from existing technology, create new products and markets • They use the fact that we trust the people in our community who, instead of calling us, send us posts; 80% of messages come from a limited number of people Voicemail - 8 people SMS - 4-6 people o Instant Messaging - 2-3 people • Missed Message Messenger (No Reply)

10/129

- Fale-um-Texto ™) - On-net + Off-net behavior, 1st use of X-Links, and new revenue sources such as the evolution and implementation of a Spanish operator • Unified Communication for the Exchange of Voice Messages - disconnected services, unified by conversion and distributed to any screen create a new multipoint mode of exchanging voice messages • S-Links detailing the embedded nature of context-based smart links within text messages converted from voice messages - a new approach to mobile search and advertising search markets • Smart-for-Me ™: passive and intelligent embedded search capability derived from many-to-one communications, unlike the one-to-one methods commonly found in current searches • exchange of messages spoken in communities via the web and SMS - Twitter, Facebook, MySpace, etc. ..

• Voice Explosions ™ - concept of speaking a message and sending it instantly as text in any format to your web-based community as a message spread directly by you

The next section will consider these (and other resources) in more detail:

Section A: X-Links

Section B: S-Links

Section C: Web 2.0

Section D: Missed Messages Messenger

11/129

<td>Section E:</td><td>An overview of the main products SpinVox</td>

<td>Appendix I:</td><td>Speak-a-Text</td>

<td>Appendix II:</td><td>Voicemail to email</td>

<td>Appendix III:</td><td>Viral / link marketing campaigns</td>

<td>Appendix IV:</td><td>Unified Communications</td>

<td>Appendix V:</td><td>Voice SMS</td>

<td>Appendix VI:</td><td>Acronyms</td>

Section A: X-Links ™

They extend the original SpinVox feature implemented within Voice-to-Text ™, through which a link embedded in the message allows a recipient to directly access and listen to the QuickLinks ™ message (see document GB2420942B, the content of which incorporated as a reference).

X-Links allow any recipient of any message converted by the SpinVox system to speak a reply to the sender. When selecting the link, the user is directly connected to a SpinVox conversion service and alerted to speak his message, which is then sent back directly to the person from whom the original message was received.

X-Links are placed in all messages, so that two people can communicate indefinitely through spoken messages sent as text whenever they want.

For example, a user may receive a 25 voicemail message in the form of text containing an X-Link. He simply selects it and speaks to the person who originally sent the voicemail, a text response. Likewise, if you are the recipient of a Spoken text message, you will be offered an X-Link to provide a text response.

For example, Figure 1 shows a text message

Spoken by 'Dan Mobile'. It includes the X-Link 84004p123 in the message &lt;To speak a text response call 84004p123&gt;

X-Links work with different messaging products, so if you receive a spoken message like SMS with

12/129 an X-Link embedded in it, you can speak a response to the person by email, or vice versa.

Technology

A link is made up of a service number and a unique identifier shown as;

&lt;service number&gt; + &lt;unique identifier&gt;

for example, Links in the UK should look like this:

02079652000p123 or 84004p123 • Service number - telephone number that acts as an access point for the conversion system, for example, the complete and standardized telephone number (for example, a DDI such as 02079652000) the short voice code (for example, 84004) the VolP or network number if used in IP-based telecommunications or message exchange • Unique Identifier - identifies who the sender is receiving the response from, for example the dial-in digits used in traditional telephony

Often uses a 'p' (pause) or equivalent network symbol on DTMF systems

It can be a special digit to further identify the type of service - for example, * or a '1' digit.

o It can be either the complete phone number (for example MSISDN), or a code that connects you to the system

13/129

84004p123ou

84004p07812101742

On next generation systems, the link can be a 'click to call' link like those found on WAP pages and used extensively by operators such as Hutchinson 3G in the UK. The benefit lies in the fact that these links can be simple words, instead of phone numbers, in such a way that the reading would be Speak Text Response instead of Speak Text Response: 84004p123.

X-List: Implicit Address Book

In the examples mentioned above, the unique identifier is shown as a three-digit code (for example, 123). The length is arbitrary and becomes the full phone number if it reaches the same number of digits as the mapped phone number (for example, p12345678910 is no longer a usable code in the UK, as all phone numbers are 11 digits).

X-Links are based on the service, creating a list of people from whom you have received a message and to whom you want to reply. The reason the process works as a limited list is because the number of people who call you 80% of the time is just 10-12 on average.

Example:

1. Davíd speaks a text message to Jim. Jim is not a SpinVox subscriber.

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

3. When Jim's call is completed, the system uses his CLI to identify who sent him the message - David's number is one of them.

4. The unique identifier then tells the system which of these SpinVox people spoke to Jim. In this case he finds David's CLI (MSISDN).

5. Jim speaks his text message.

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

7. The link continues to infinity.

14/129

The key elements of this implicit XLink address book are:

• A list of MSISDNs (or equivalent phone numbers) is created from all callers who left a message for each SpinVox user on the X-Link service.

• This list is unique for all SpinVox users, identified by their MSISDN (or equivalent phone numbers). Each user has their own X-Link list controlled from their MSISDNs.

• Each new person who leaves a message for a SpinVox user has a new entry created in this list, and a correspondingly allocated unique identifier.

• The list grows to the permitted limit which, with just 3 numbers, is 1,000 users. It can be longer or shorter depending on the needs of the user and the service provider.

• Every time the SpinVox user calls using an X-Link, the system knows which list is his (using his MSISDN), and then decodes the digits of the unique identifier in MSISDN of the person to whom he wants to speak a message .

• SpinVox users can save these X-Links directly in their address books for future reference, and know that by calling them they can always speak a text message to the associated person.

• Optional: the system recycles the user's X-Link list in such a way that, once it is full, it returns and replaces the last used entry with a new one. This method keeps the identifier unique

15/129 short (for example, with 3 numbers), assuming that you will most likely use the X-Link of the message you recently received to reply, and with that you will correctly connect with that person. It is possible to discover a very old message with an XLink that now points to a new person.

Note: Users of this service do not need to be subscribers of SpinVox. They just need to receive a message with an X-Link to benefit from the method.

X-List Mechanism

Unique X-Lists are created for each person (AF in this example), as well as list elements generated using the CLI of callers / speakers and an associated unique identifier (UID). In this case, the

UID is '*' + '3-digit'

<td></td><td colspan="6">List Owners</td>

<td>Recipients</td><td>THE</td><td>B</td><td>ç</td><td>D</td><td>AND</td><td>F</td>

<td>THE</td><td> -</td><td> *001</td><td> *079</td><td> *022</td><td> *333</td><td> *010</td>

<td>B</td><td> *003</td><td> -</td><td> *012</td><td> *025</td><td> *334</td><td> *099</td>

<td>Ç</td><td> *011</td><td> *007</td><td> -</td><td> *003</td><td> *351</td><td> *015</td>

<td>D</td><td> *002</td><td> *011</td><td> *001</td><td> -</td><td> *002</td><td> *101</td>

<td>AND</td><td> *139</td><td> *099</td><td> *006</td><td> *011</td><td> -</td><td> *069</td>

<td>F</td><td> *001</td><td> *010</td><td> *589</td><td> *287</td><td> *006</td><td> -</td>

The address book is constructed simply by creating a list for each person who is a recipient or sender of a SpinVox message. The list contains links (shown as * xyz) that map them to the current phone number (CLI / MSISDN). Every time a new person sends a message to another person through this system, they are added to your list. In this way, both SpinVox subscribers and non-subscribers have their lists created for them.

For example: A's unique address book is shown

16/129 by the vertical list below A.

A was called by F first (* 001), D second (* 002), B third (* 003), and then after 7 others, by C (* 011) and by E 139 ° (* 139).

Thus, if A uses X-Link at the end of message 5 that they receive (for example, Telephone_no. * 002), the system knows that A is calling from their CLI network (MSISDN), and that they want to speak a text to number 2 on the list. The system has defined number 2 in list A's for telephone number D's.

X-Lists are built through patterns of call / message exchange between communities of people.

Bidirectional message exchange

Using the list of examples above, it shows how A and B are connected to each of the other Address Lists:

1. A is a SpinVox user. B is not.

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

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

3. Now A speaks a text response to B using the

X-Link of the message.

The. This is the first time that B has had a spoken message sent to him via SpinVox, so the B's list is now created and A is added as the first entry (* 001) in the B's list.

4. The system sends message A's to B with an XLink UID as * 001.

5. B receives the message and using the X-Link calls the SpinVox service, is identified as B (CLI / MSISDN) and presents * 001 as the recipient - that is, A.

6. A now receives a return message with B's

UID (* 003) and the link can continue to infinity.

Saving X-Links: reliable for using the local address book

Because the X-Link service reliably connects people to each other, users can safely save X-Link

17/129 in the address / contact list of your mobile phones for future use. In this way A can, in this example, reliably save 84004p * 003 in the address book of her mobile phone as the entry to speak a text message to B. In the same way, in this example, B can also save an entry to A speaking a text message like 84004p * 001.

This method allows communities to connect reliably 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 80% of our Instant Messages from just 4 people.

Naturally, X-Links have a finite limit, so in the example shown, the unique 3-digit identifiers limit them to 1,000 other people. Changing the number of digits in the unique identifier changes the possible number of people you can connect through your X-List.

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

X-List: Any Address or Identifier

Although the X-Lists method is explained with the use of telephone numbers, in fact any type of address can be used - e-mail, IP address, Instant Message, VolP number, etc. as long as it is a trusted identifier to address a message. So X-Lists can be used by any message exchange community, and not just communities based on phone numbers.

This also means that a user can choose to receive messages as e-mail, but always returns messages spoken as SMS.

X-Link: Launch messaging application

The X-Link concept reaches another level when used with any community application. The link is not just a phone number or address, but also a link to launch the relevant application.

For example, the X-Link embedded within a standard spoken SMS or voice-to-text mail can be a link to a callback via a VolP application, rather than a voice call

Conventional 18/129.

The link could just show: VolP Callback?

Clicking on the link (or selecting it within the application's menu, typically 'usage detail') could result in the following actions:

1. Launch the phone's VolP application - for example,

Skype.

2. Automatically return the call to the caller using the VolP application.

3. If the VolP application does not exist, it could connect to the VolP provider's web service and download the application, or request a 'callback' so that they can connect using this method.

Note: this can be a very efficient method of acquiring subscribers for a VolP service, as each link is a call to connect and / or download your customer and use their services.

X-Link as a public QuickLink

QuickLinks are used by SpinVox subscribers to be able to dial and listen to (retrieve) any voice message simply by entering the QuickLink digits (for example, * 12) found at the bottom of each message.

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

For example:

• You are not a SpinVox subscriber, but you receive a spoken message from a friend.

• Either the message is ambiguous, or it has not been converted, but you have a public QuickLink at the end of the message (see the figure below) to call and listen to the message.

• You select the link (or dial the full number) and the original voice message is played for you.

19/129

Technician

Because the X-Link service has a list of numbers from both senders and recipients, it is able to match the CLI (MSISDN) of any caller to the list of a history of numbers that have been connected. Then, the unique identifier allows the service to match the exact CLI of this list that relates to the message the user wants to hear.

The requests for QuickLinks and X-Links to the SpinVox service can be distinguished by:

• Different characters / commands being inserted at the beginning of the Unique identifier to identify the type of call o Using a '*' o Always beginning with a 1 o Using the 'p' command to mark the beginning of the unique identifier • Using different service numbers o Calls to speak a text message are in a range of service numbers (e.g. 84004, 84007, 84009, etc ...) o Calls to retrieve / listen to a message received as text are in a separate range of services (for example, 94004, 94007,

94009) • Using the same number, but then alerting the caller / speaker to select which option he wants.

o For example: Please select 1 if you want to hear this message, or 2 to send a reply to the sender

Dedicated service numbers allow users to retrieve data automatically, instead of calling a number and entering the unique identifier manually. They simply select one

20/129 number to call from within the message.

X-Links with messaging products

The above description shows how X-Links can be used within a given message exchange product. However, if a user sets their preference, SpinVox or the service provider can send the converted message back to any message format / application that the user wishes.

For example • James is not registered with SpinVox (or with the Spinvox service provider). He receives a spoken SMS from Adam who is registered with SpinVox.

• James receives a spoken SMS from Adam.

• James uses X-Link to respond and speaks his message.

• SpinVox knows that Adam has in fact chosen to have spoken messages sent to him by email, rather than SMS. Thus, the system converts James' messages into texts and sends them by email to Adam.

• Adam sees James' response in an email, and uses X-Link to return a spoken SMS to him.

This can work with any text-based messaging application - SMS, MMS, Instant Messaging, email, etc.

User Experiences with X-Links

As noted above, X-Links is a new product from

SpinVox designed to increase the value of every voice message converted and sent by a SpinVox product. It achieves this by including a chargeable response path, and allows anyone to speak a response to a message they have received.

For the first time, a trajectory of spoken response is available, creating opportunities. In addition to offering an experience of

21/129 improved subscriber, this unique integration provides a means of charging all messages sent to or from a SpinVox customer. X-Links provide significant, sustainable and incremental returns for Operators.

The solution consists primarily of:

• SMS, MMS or e-mail messages with a highlighted reply path; or a phone number or an HTML-style link.

• New ability to identify the calling partner and connect their number with a unique identifier that allows integration • Spoken with a superior billing solution to monetize each message sent.

The following sections will be covered in this document: General requirements - key features and product benefits.

User experience - customer experience with calls and called partners.

Product requirements - end-to-end life cycle experience.

General Requirements

The product must meet the following criteria:

End User Benefits

It provides an ultra-fast response path, for situations in which the client cannot or does not want to stop what he is doing, or does not have the skill or technical knowledge to use a keyboard.

Ease of Use

It should be obvious to the user that the highlighted word or number can be 'clicked'. It must have a simple way of being activated and a number automatically dialed. Ideally, just one click should be needed to initiate the call to the IVR.

Simple, Fast, Intuitive

It should be obvious that a click on a highlighted link produces a reaction. It is assumed that MMS support is present in most of the targeted devices and that these devices support clicks.

22/129

User Experiences

Figure 3 illustrates a typical sequence of messages and the recurring use of the X-Link 'Speak a Response'.

Demo Definitions

In order to quickly demonstrate the capabilities and potential of X-Links, there will be 2 separate demonstration scenarios and relevant milestones:

SMS-based demo

The purpose of the canned demonstration is to show proof of concept for the X-Links.

SMS / MMS Field Experience

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

1. User interaction considerations

Even if the recipient of an X-Link message reads a message as an email on a PC or a high-end smart phone, the expectation is that most users are using a more common mobile phone. Consequently, interactions with X-Link messages must be designed with these users in mind. Access to the data that the user is requesting by clicking on a link must be immediate and require the least number of clicks to obtain the desired information.

Calling Partner

The calling partner experience is consistent with SpinVox's current voice-to-text products. Callers hear an IVR greeting, to leave a message that also alerts them to the embedded SpinVox brand.

Partner Called

The called partner receives an SMS message, or an MMS message or an email from the converted voice message. When the message is displayed, a link at the bottom of the message will be highlighted and give you the option of replying by clicking on a number or link.

Once he has initiated the answer, the caller hears

23/129 an IVR greeting, to leave a message that also alerts you to the incorporated SpinVox brand.

2. Implementation considerations

There will be 2 types of X-Links service offerings - X-Links for SMS and X-Links for MMS and e-mail.

SMS

While SMS has the greatest reach in terms of subscribers and device support, there are limitations on the number of characters available in each message. This limit impacts the number and type of links that can be incorporated into an SMS message. A second consideration is the device's ability to automatically dial a phone number. If the link is according to a common number +44207772222 some but not all devices will allow the link to be clicked and a phone call to be made.

The focus for SMS will include a phrase at the end of the message such as 'To speak a reply call &lt;+4420777222&gt;'.

MMS and Email

MMS and e-mail messages provide a richer X-Links experience for the end user in terms of message display and usability. Even though its use is not so widespread when compared to SMS, the use of MMS has recently experienced significant market growth.

For MMS, the X-Links message contains a link at the end of the message that states:

'Click here to speak an answer'

- spoken through SpinVox

When the link is selected, the call to a number (hidden by the end user) is made. This can be a geographic or non-geographic landline number or a short Voice code.

X-Links Product Requirements 1. Service Level

Application

12/24 calling partner does not need to be a SpinVox or Operator subscriber to use this service.

Customers can cancel the service by calling customer service or by sending an SMS message to a short code.

The service must meet the same availability requirements as the prevailing SpinVox service.

At the initial launch the service must support the following languages:

English UK

English US

Canadian English

Canadian French

German

French

Spanish

Australian English

South African English

The SpinVox SMS server must maintain a DDI operator profile to determine whether the message should be delivered to the SMSC operator or to an aggregator to send it to the customer.

In this profile, there must be a reference for the injection and ejection of validation rules for this operator.

2. IVR

Once connected to the SpinVox IVR, the customer simply needs to record their message and then hang up for the 5 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.

25/129

Requirements

The voice intonation used to record any new voice alerts must be the same as that currently used on the SpinVox IVR platform.

IVR alerts must be recorded in all languages ​​supported by SpinVox's IVR.

The recipient will be automatically recognized and no additional number entry is required.

The duration of a spoken response will be programmed to 30 seconds.

The option to re-record the message will be accessible by pressing * (the asterisk key) at any time during recording.

The first three (3) times a customer initiates a call to respond with the use of an X-Link, he will be alerted to confirm the charge for using the service.

The subsequent times that a customer connects to the IVR, he will not be alerted to confirm the cost.

X-Link Confirmation Alert (played the first 3 times) Welcome. This service costs 25 pence per message. Please press 1 to continue.

By pressing key 1 the action will be confirmed and the customer will hear the following alert

X-Link normal alert:

Speak your answer Now !.

Once the message has been deposited a billing trigger is

12/26 activated and, if appropriate, the customer will be charged for the message.

3. Delivery to recipient

When a voice message is successfully converted to text, an SMS, MMS, is sent to the intended recipient.

Application

The text message must be sent from the telephone number of the original caller (that is, partner A).

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

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

WILL DIFFER DEPENDING ON THE DELIVERY METHOD

The delivered message must automatically contain an X-Link, connecting the sender (only) with the recipient.

4. X-Link

There are no prerequisites for using an X-Link. It is not necessary to have a SpinVox account, in fact, many recipients will not know who or what SpinVox is until they click on the link.

Application

It must be possible to connect the numbers of two people only, using a single geographic or non-geographic number that can be dialed from any handset.

27/129

5. Report

Application

It should be possible to report on all messages from this service.

Additional X-Link concepts • The original sender has an adjustment that can specify that the voice-to-text response should be forwarded to more than one recipient, for example, to an SMS, to different email addresses (office) and to an additional email address (home). This setting can also be changed on a message-by-message basis. This adjustment can be practical, as it can automatically back up SMS messages received on a mobile phone to an email account at the workplace, or to a support team at the workplace who can provide coverage for a busy individual .

• Every user has their own list of X-Links, each X-Link being associated with the unique MSISDN of a person who sent a text to this user. Individual X-Links can be deleted, if desired.

• Option included to save spoken text messages to an intermediate location for later sending at a specific time. For example, in environments dominated by unions, it may not be possible to send such a message outside of working hours. Once selected it can be sent exactly at 9 am, which can be

12/28 be the exact start time of the working day. The option can be called Speak the delayed text message, with the future time (and possible date) when it was typed to be sent using the numeric keys.

• Inserting an X-Link in the message is deselectable through an option. For example, if the recipient speaks with a strong dialect or a dialect that cannot be reliably converted to text using existing technology, and if you do not want to waste time trying to decipher a text message of this type.

• When a text message is sent to a SpinVox non-customer, include a link such that the SpinVox non-customer can click on it to subscribe to SpinVox, for example, via a website, or by speaking with an operator .

• X-Link inside a blog, or in a closed group of users.

SECTION B: Content Based Links - S-Links ™

Spoken Links (or smart links)

One of the most useful features when receiving a spoken message as text is the fact that if the speaker has provided specific data regarding a place, time, address, name or other keywords, they are in the text and you, as a user, you can quickly reference them anytime you need them.

The transformation of telephone numbers, email addresses and websites into hyperlinked objects is common in messaging applications (SMS, MMS, e-mail, IM, etc ...). In spoken messages, users often provide references to locations that are not so obviously structured, but are equally important to the recipient.

The concept of S-Links is to transform the text of a spoken message and use keywords to generate a set of useful and

12/29 related. The relevant links are inserted in the message and take the user to a website or a web resource that expands on the linked content.

For example, in Figure 4, the message sender Zac Sandler leaves a voice message that was automatically converted to text using the SpinVox speech conversion system (see WO 2004/095821 and WO 2007/091096, the contents of which are hereby incorporated by reference). At the bottom of the converted message are two separate links, one for directions and the other for a drink called 'cava'. Clicking on the 'Directions' link opens a map browser on the phone (in this Figure, for clarity, an image of Google Maps for PC is shown), showing the address mentioned in the voice message, now converted to SMS.

In another mode, shown in Figure 5, the links are embedded within the message, with the address' 20E &amp; 9^th St 'in the message body being selectable to start the map browser and show the address. Likewise, the word 'cava' in the body of the message is selectable to start the browser with places where this wine can be purchased and which (optionally) are close to the address mentioned. In this example, the user is presented with options found on the planned route for the purchase of a bottle of Cava, instead of in any location, optimizing the relevance and thus the implicit value of the search result. In addition, these options can be added to the displayed map to show where these items are on the route.

Thus, in this case, the message contains two clear opportunities from which a relevant link can be created; an address and a product type.

The system first looks for keywords or phrases that contain similar words for links. He takes these words or phrases and automatically searches for similar resources for each one, and then presents what he estimates to be the best result.

The value of this procedure lies in the fact that relevant links are inserted, which the user will accept for being useful and relevant and generally not inopportune. This is a very valuable way of marketing 'down the line' using User Generated Content to

12/30 find and create valuable links for the recipient.

In this way, S-Links increase the value of converted voice messages with the inclusion of relevant contextual elements. With the incorporation of links in external information, such as maps, directions, advertisements or others, messages with enabled S-Links can provide an improved experience - evolving from the current and explicit search paradigm to a significantly more implicit search, that is, for something that was actually mentioned in a conversation.

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

Technician

The way to create these links consists first of processing the converted text, finding relevant keywords, creating the links and then adding them to the message, before sending them to the recipient.

The SpinVox Voice Message Conversion System performs post-processing of all messages, and is able to make a call to a routine to analyze the texts and create any relevant S-Links. The VMGS is defined in more detail in document W02007 / 091096, the content of which is incorporated herein by reference. Alternatively, the message can first be sent to an intermediary who can perform this link creation step.

Types of Links

Links can be either the full URL at which the application reading the text is unable to create full hyperlink pseudonyms, or just the hyperlink itself from the keyword.

For example:

URL only: http://maps.google.com/

Hyperlinked '. 20E 90^th St

If the links are not completely hyperlinked,

12/31 they can be placed within the message text:

From: Zac Sandler

Hello. The party starts at 9 pm on 20 east 9th Street. Don't forget to bring a bottle of cava for Mandy's Spanish silver bullet game. See you soon.

Implicit Search with Smart-for-Me ™

The system can be improved to provide truly intelligent links, which are not only relevant to the message, but also to the user and their habits, usage history and preferences. The concept lies in the fact that the S-Links service learns and uses other resources to ensure that any links are presented in an Intelligent way to the specific user, or Intelligent-to-Mim ™.

Question

The question of mobile search is stated today in the fact that users behave in the same way and have the same needs both when they are mobile and with their PCs. There are three basic issues when transmitting searches from a PC to a mobile:

1. When people leave and go somewhere, they usually know where they are going, why and with key information about the trip, even if it is local. So your search requirements are generally contextually restricted to hand-held tasks.

2. In the event that people choose to search while they are mobile, it is well known that current solutions require the entry of information on a small alphanumeric keyboard or even on a touch screen that is not easy to use and that requires the user generally stop somewhere to search.

3. Even if a person cannot enter the search term, they still need to click and scroll through several pages to find the relevant result. This process can take 30-40 sequences of keystrokes including opening the browser,

32/129 typing in the search series or question (often more than once to find the correct result), scrolling and then selecting the /// nks pages for viewing.

Key criteria

The source of many of our searches is usually determined by messages we receive from others, such as names or something we are not aware of, locations, brands, etc ... On a PC, these sources are broad as they come not just from our community or from colleagues. But, fortunately, bigger keyboards, shiny screens and io connectivity make our explicit task of transposing the idea to some keywords, opening our browser and typing some search words and then navigating through many options, an acceptable task. This is an 'Explicit' search, because the user must consciously think about what he needs to find and when, and then filter the results for his target.

The messages we receive from our community or voicemails contain a high proportion of information about key tasks for our daily lives - for example, a meeting time, an address, items to bring / buy, things to do / see and even reminders.

SpinVox surveys converted to results from voice-to-text messages show a surprisingly high number of appointments: around 25% of locations, tasks and items are received by voice messages. And people use them to navigate and successfully work through the day.

This means that a considerable part of a person's initiative to initiate a search comes from voice messages. The solution becomes apparent in conjunction with the fact that people often rely on text messages (SMS, MMS, e-mail, etc ...) when they are performing their tasks or while traveling, to see route details (for example example, check addresses, times or the name of items to receive).

By connecting keywords in any message, the user has direct access to the recipient (search response), and the user's life becomes simpler and more effective. There is no need to think explicitly about the search and how to do it, just click on the link to be taken directly to an answer. All intermediate steps

33/129 that the explicit search requires are removed. Use the highlighted word or reference in the message and go directly to the answer: Implicit Search.

Implicit Search

Converting all voice messages to text first, the SpinVox system has all the keywords that can be used to perform an intelligent search. In addition, it also has the ability to build a history of the user's messages, who they originated from, what source and the response to the links to continually improve the way they will be presented in the future and thus fit within the needs current recipient / user. This way the system learns what the user is likely to look for through the complete history of his messages sent and received - not just by the specific search.

Keys to optimize implicit search include:

&gt; Calling / sending partner (partner-A)&gt; Keywords used and their relative meanings&gt; Types of messages - voicemail, SMS, e-mail, social network, broadcast / explosion, etc ...

&gt; Location of both the called partner (partner-B) and the calling / sending partner (partner-A)&gt; Location-based services (LBS) to improve the context of keywords (for example, addresses, or locations of certain items in the route)&gt; Recipient's clicks and actions history&gt; Message response history to better understand what was said ambiguously or possibly to be done next in a typical sequence between these two partners&gt; Time of day, date and places where actions were taken to optimize what's relevant or not&gt; Preferences by brand, place, method or mode based on purchase history or purchase history

34/129 messages and use of links

WO 2007/091096 regarding the VMCS patent describes the system used to implement the indexing of keywords / terms necessary to generate a complete index that can form the basis of a search system supported by advertisements - that is, that is sufficiently trustworthy, robust and scalable to assure advertisers that the particular bet on an indexed term is reliably and properly referenced or linked in a message when that indexed term appears.

By looking at all of a user's messages, whether they received or sent them, a significant amount of personal context can be derived to learn and thereby provide a user with options or smart links to what he wants. This constant learning helps to provide a network-based service that is with you and is: Smart for Me ™.

Many-to-one broadens scope and relevance

This method also modifies the traditional search which is in essence a one-to-one relationship. That is, as a user, it is just my entry that you request from Google or Yahoo! that generate results, and only what they know about me is my IP address, which changes as I move. With S-Links, the search entry is expanded to become many-to-one. It is also reliable for a user, as the phone number rarely changes. Consequently, the search is significantly more relevant to the user than using a complete set of keywords on which a user depends, instead of the few that are remembered and transposed from one application to another. The search can be equally specific to the user's demographic situation, as the information is either provided explicitly to the system by the user, or it can be assumed by the system by looking (with the user's consent) at the content and profile of their messages.

We believe that a significant amount of mobile searches will come from implicit search options embedded in messages, and are likely to be greater than traditional and explicit forms of searching on mobile systems.

35/129

Based on permission

One of the key issues that this idea solves on mobile phones, is the fact that there is great resistance to any advertising that is explicit or that is clearly known as 'above the line' and that occupies part of the user's screen. On mobile phones, the clean area of ​​the screen is critical.

Embedding the links as the words, this problem is immediately solved and the service and any other events associated with it will only appear when the user effectively selects that he really wants to use this option. This process transforms the user experience and the acceptance of commercial services and advertisements on mobile phones.

Gesture-based search

As the system provides single-click responses to typical search tasks, the user needs to perform only the simplest of actions. One click, which is a common gesture and takes the user directly to his recipient, instead of working with his keyboard and navigation keys through 20-30 or more entries (key presses and clicks) to get the same result. It is known that each stage loses around 30% of users, which is even more pronounced with mobile phones. SLinks reduce this to just 1 step.

Location Based Search

A simple feature is the option of not only displaying the Address someone has provided you with, but using the intelligence of the network (typically Location Based Search) to provide you with:

&gt; The current route to be taken to take you from where you are to the address provided in the message&gt; If you have other items to see or collect (buy) along the way, the mapping function can now fill your route with options for find these items, instead of just informing them in a unidirectional radius around you&gt; Your history to know which places, routes and

36/129 features you prefer to improve the relevance of the results shown&gt; The location of the A-partner to also optimize local references and instructions or the information to improve the relevance of the results presented - for example, 'find me at my Starbucks' will be able to automatically map the Starbucks closest to the phone of the caller who placed the call.

Business Model Transformers The use of implicit links leads mobile users to online resources, many of which are paid for online advertisements that appear. Implicit search performs several tasks for users in the value chains provided by both mobile services and web-based searches:

&gt; Increases the traditional revenue in the Search for Advertisements (online advertisements) such as those derived from Google, Yahoo !, MSN, etc ...

&gt; Increases mobile revenue from data traffic and purchased data products.

&gt; Increases online mobile phone transactions.

&gt; Provides revenue sources for the networks to subsidize the Spinvox service, which enables this capacity. Users may no longer have to pay, but instead receive better service.

&gt; Encourages the use of new products or messaging modes, such as MMS and WAP, both of which are underutilized, but are also very capable multimedia resources and which networks would like to get a return on.

<td></td><td>Benefits</td><td>Business Benefits</td>

37/129

<td></td><td>Commercials</td><td>Rationals</td>

<td>SpinVox</td><td>Income increment in share then revenue from clicks</td><td>Strengthens the position of SpinVox as an innovator and market leader</td>

<td>Operator</td><td>It increases the income from sessions data / WAP</td><td>Encourages new sales of data plans and improvement selling phones compatible</td>

<td>Mechanism</td><td>Increments</td><td>Monetize SMS</td>

<td>the of</td><td>all</td><td>previously not possible</td>

<td>Search</td><td>recipes through the clicks</td><td>depending on routing and volume</td>

Figure 6 schematically illustrates the transformation of the business model and how SpinVox itself positions itself as an intermediary between the customer and the aggregator of advertisements based on search engines, such as Google.

Results Single Search Award

Depending on the nature of the unique link and its design to take you directly to the correct result (destination), this service additionally increases the value of search results for advertisers and commercial service providers, as only one or a few others will be shown search results, rather than the result pages provided by explicit PC-based searches, which tend to dilute the space value

38/129 purchased.

This service outweighs industry concerns about mobile advertising, which is generally less valuable than web content, and with features that are generally less available to mobile users.

Summary of S-Links features

The voice now being incorporated into the text can be massively indexed • Voicemail is the second largest form of mail after e-mail.

• Voice messages present a rich personal context - information on key tasks.

• The search can be perfectly defined and relevant.

• Based on permission: Smart-for-Me ™.

• Smart links: learn from the history and use of all messages sent by my community to me, and not just from my individual searches (for example, Google).

• Implicit versus Explicit search.

• The current search is PC-central - Explicit search.

• Requires the user to think about the search term, switch applications, type entries through complicated keyboards, browse to find results = 20-30 clicks exercise (30% loss in each step).

• Naturally limited market - in mobile telephony!

• S-Links provide results in context (message) - Implicit Search.

• Voice mails (and SMS) contain more than 70% of key information for daily tasks: addresses, times, names, sequences, products,

39/129 ideas, etc ... - that is, keywords that define typical searches.

• Take you directly to your destination, not on long trips - 1 gesture = result!

• Recurrent implicit behavior - voice messages are received every day.

• The link exists discreetly in the message and takes you directly to the result.

• Links are smart - they can provide local context to ensure that the results shown are correct for the user the first time - for example, providing local options for maps, products, places and services.

• Implicit navigation - it knows where you are and where you are going. It uses network LBS (location-based services) to find you and provide you with map services with a route to your destination. It updates dynamically depending on where and when you click on a link.

• 1 simple click to reach the destination - the link is persistent and is in the message after you close and reopen the message many days later; there is no need to type it again.

• Preferences allow different business features to be displayed.

• Provide individual search results of much greater value.

User Experience with S-Links

This document details the user experience and highlights specific requirements and considerations for S-Links SpinVox. The solution consists primarily of:

1. SMS, MMS or email message with words

40/129 key highlighted.

2. New ability to identify and highlight keywords in speech to text processing.

3. Integration with third party advertising and content servers to support the business model.

The following sections are covered in this document:

1. General requirements - key features and product benefits.

2. User experience - customer experience to call and with the called partner.

3. Product requirements - end-to-end life cycle experience.

General Requirements

The product must meet the following criteria:

End User Benefits

Highlighted words must be relevant to the message content and have perceived value for the user. The consensus says that 2 or 3 links per message is the maximum limit.

Ease of Use

It should be obvious to the user that the highlighted words can be 'clicked'. The method of activating links must be simple to generate the associated results. Ideally, just one click should be needed to retrieve and display the requested information.

Simple, Quick Results on Display

Clicking on highlighted words should require as few additional clicks as possible to display results. WAP support is assumed to be available on most target devices.

Performance

The time involved (TAT) for delivering the message should not be impacted. The message TAT must remain within the current SLA parameters.

Figure 7 shows the end-to-end experience of when a calling partner leaves a message even when the recipient (called partner) receives the message. The content of the message, the display and the

41/129, 15 interaction will differ depending on the message sent and the type of screen.

1. The calling partner initiates a call to a called partner. Alternatively, the caller may be responding to an email, creating a note, preparing a blog or post on a social network, or responding to an instant message. The calling partner is prompted to speak their message using normal IVR product alerts.

2. The voice message is recorded in the audio capture system of an operator, service operator or Spinvox. The WAV file is then sent to the VMCS for conversion.

3. SpinVox's VMCS converts the WAV voice file into a text message.

4. SpinVox interrogates the message to determine if any relevant keywords are present.

5. SpinVox highlights the relevant keywords and inserts one or more of the following associated links:

The. Add a click

B. Map

ç. Add a tag to the message

d. Add a tag at the bottom of the message

6. The message goes back to the operator to be delivered to the destination of the called partner via SMS-C, MMS-C, or e-mail port.

7. The called partner receives the message on the device. The display of the message and the link capabilities will depend on the type of message sent (SMS, MMS).

8. The called partner clicks on words highlighted with embedded links to display more information.

9. The links are sent to third-party providers of map services, advertisements or search results.

10. The results of the links are displayed to the user. The results displayed and the speed will be dependent on the WAP / weò capabilities of the called partner device.

Demo Definitions

In order to quickly demonstrate the capabilities and potential of S-Links, there will be 2 demonstration scenarios in

Separate 42/129 and relevant milestones:

Canned Demonstration

The purpose of the canned demonstration is to show the S-Links proof of concept. The demo will be limited to a predefined set of keywords and the results displayed.

Field Testing

The purpose of the field trial version is to demonstrate the capabilities of S-Línks to customers, partners and key industry influencers. The field test is performed with a working version of the product, although there may be limitations on the availability of keywords and search results.

1. User Interaction Considerations

Although the recipient of an S-Link message can read the message as an email on a PC or a high-end smartphone, the expectation is that most users are using a more common mobile phone. Consequently, interactions with S-Links messages must be designed with these users in mind. Access to the data that the user is requesting by clicking on a link must be immediate and require the least number of clicks to obtain the desired information.

Partner

The calling partner experience is consistent with SpinVox's current voice-to-text products. Callers hear an IVR greeting, to leave a message that also alerts them to the embedded SpinVox brand.

Partner Called

The called partner receives either an SMS message, MMS message or an email from the converted voice message. When the message is displayed, certain keywords will be highlighted, usually those that are most relevant to the content of the message. The message must contain a minimum of 1 and a maximum of 2 or 3 keyword links. The type of content displayed and user interaction with this content will vary depending on the type of message and the capabilities of the device (see Implementation Considerations below).

On compatible devices, selecting a word

43/129 highlighted key starts a WAP or web session and displays an advertisement, map or search results associated with the keywords.

<td></td><td>Canned Demonstration</td><td>Field Testing</td>

<td>Strategy</td><td>Predefined minimum list</td><td>List developed jointly</td>

<td>of Word Key</td><td>of keywords</td><td>with commercial servers or search partners.</td>

<td>Link Type The. Add click B. Map ç. Add label on message d. Add tag no footer message</td><td>Keywords connect directly to a predefined set of results The. Hotel -&gt; WAP site B. Map -&gt; Map static ç. Audio Clip d. Movie Clip</td><td>Based on keywords selected and links related.</td>

<td>Adaptation in Device</td><td>AT</td><td>Outsourcing for adaptation / device transcoding furniture</td>

<td>services based in location</td><td>AT</td><td>Simple user profiles containing the most frequent</td>

44/129

<td>Opt-in / Out</td><td>AT</td><td>The default is opt out</td>

2. Implementation considerations

There will be 2 types of S-Links service offerings - SLinks for SMS and S-Links for MMS and e-mail.

SMS

While SMS has greater reach in terms of subscribers and device support, there are limitations on the number of characters available in each message. This limit impacts the number and type of link that can be incorporated into an SMS message. A second consideration is the device's ability to render the link. If the link conforms to the common URL format http://www.anysite.com, some but not all devices will allow the link to be clicked to open a WAP browser.

SMS's focus is to embed a single link or an advertising tag line in the message. The link must be relevant to at least one of the words in the message. Alternatively there may also be an answer option, for example, - Answer M for more information - which can be sponsored. Another approach is to auction off specific keywords to the highest bidder - for example, Hotels = Hilton, Café = Starbucks. This approach will not be used initially, as keywords are of low value until the advertising inventory increases, as more advertising-sponsored messages are implemented.

<td></td><td>Canned Demonstration</td><td>Field Testing</td>

<td>Word Key</td><td>Coffee</td><td>List developed in with servers commercial partners or search.</td>

45/129

<td>Results displayed</td><td>Label lines Option 1: To find a Local Starbucks, go to http://mobile.starbucks.com Option 2: Looking for Starbucks? answer Y to find the closest to you</td><td>TBD based on lists of partners</td>

<td></td><td>MMS and Email MMS and SMS messages</td><td>e-mail provide a</td>

much richer experience of S-Links to the end user in terms of displaying 5 messages and usability. Although its use is not as widespread as the

SMS, the use of MMS has recently experienced significant market growth. MMS has the ability to support rich types of data such as images, audio and video, and does not have the same character limitations as SMS. Mobile phones that support MMS are more likely to have some type of web access built into the device. SLinks can be additionally important promoters of increased traffic and MMS messaging services of greater value for operators.

For MMS, the S-Link message can contain between 1 and highlighted keywords. When a keyword is selected, a WAP or web browser will be started and the relevant information displayed. If the information is an address, the browser should open a map with the address highlighted and show options for receiving directions, if possible. If a word such as coffee or Starbucks is highlighted, clicking on the link will display a list of coffee shops or Starbucks that are close to these users. These may or may not be relevant when the user is viewing the message. Clicking on a highlighted item can also bring an advertisement, either separately or as part of other results. A future option

46/129 will also consider integrating an advertisement as part of the current message.

E-mail and IM messages will work similarly to MMS.

Product requirements

1. Customer interaction with IVR

There will be no change in the calling partner's experience.

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

B SMS / MMS partner

The text message must be sent from the telephone number of the original caller (that is, partner A).

Message body

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

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

WILL DIFFER DEPENDING ON THE DELIVERY METHOD

Message Delivery

Canned demonstration - outsourced aggregator.

Field Test - MMSC operator.

3. S-Link

47/129

Highlighted keywords

A minimum of 1 and a maximum of 3 keywords will be highlighted in the message body.

User actions when clicking - see table below for test demonstration requirements.

Impact on message loads (see 2.2).

Choice of words

1. Operator specific

2. Action

3. Definition of the search-advertising partner Inclusion of the location in the click?

<td></td><td>Canned Demonstration</td><td>Field Testing</td>

<td>Strategy Keyword</td><td>Predefined minimum list of keywords.</td><td>List developed in with servers commercial partners or search.</td>

48/129

<td>Results displayed The. click in advertising. B. Map. ç. Label of advertisement on message. d. Label of advertisement in footer message.</td><td>Keywords connect directly to a set of results predefined. The. Hotel -&gt; site \ NAP do Hilton. B. Map -&gt; Map static. ç. Audio -&gt; Foo Fighters - Flash page. d. Movie -&gt; I Am Legend flash page.</td><td>Based on words selected keys and links related. For example: The. Hotel -&gt; Hilton - show a list of Hilton hotels, preferably those that are relevant to the user location. B. Map -&gt; Dynamic Map (such as Google Maps) showing local commerce and driving options. ç. Partner-based TBD. d. Partner-based TBD.</td>

<td>Sources of Content</td><td>Demo site made by SpinVox.</td><td>Service content outsourced.</td>

4. Service Level - Test Only

Subscription requirements

The calling partner does not need to sign up with SpinVox or the Operator to use this service.

Customers can unsubscribe from the service.

Service level

The service must meet the same availability requirements as the prevailing SpinVox Services.

VMCS Language Support

49/129

At 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

Operator Profile

The SpinVox SMS server must maintain a DDI operator profile to determine whether the message should be delivered to the SMSC operator or to an aggregator to send it to the customer.

In this profile, there must be a reference for the injection and ejection of validation rules for this operator.

7. Report - Test Only

It will be necessary to report the activity of the S-Links. The hearing for all reports will be both internal and external, from the Operator and from advertisers or network advertisers.

Reporting requirements

It should be possible to generate reports for all messages from this service.

Reporting requirements

50/129

It should be possible to generate reports on the values ​​of the following products:

• Usage • Traffic

Reporting requirements

Word impressions per day / week / month.

Clicks on each word per day / week / month.

Clicked links versus links displayed for each word per day / week / month.

Filter by Operator, service provider, etc.

SECTION C: WEB 2.0 Mobile Blogging - MoBlo ™

Blogs have become a very popular method for 5 people to share ideas, facts, photographs, images and other information freely available on the internet. Blogs are widely used around the concept that you are sharing something with a community that your blog is relevant to, and often highly personal.

Blogs exist to share information about movies, concerts, shows and all kinds of entertainment, and, more recently, they have seen a wide increase in their use by Citizen Journalism through which any member of the public can post news or information on a current topic. . The BBC recently introduced such services together with other major news providers.

The point is that people often want to post something on a blog site when they are not in front of their computers (PC), but during an event or when a subject is relevant. For example, when you have just left the theater, you would more likely like to post a comment about the movie you just saw, than wait until you get home. Likewise, if you heard or saw news that affected you or that interested you, you would probably like to post the entry immediately. In many cases you are away from home, and

51/129 necessarily in front of your PC.

The current solution is to use the micro-browsers available on high-end mobile phones to connect, and use an alphanumeric keyboard or a micro-keyboard to enter the entry. This works if you are patient, technically competent and skilled enough to type more than one or two sentences. For most of us, the process is highly impractical.

SpinVox Mobile Blogging is simple. Just call the blog site phone number, speak your blog message and it is converted to text and posted as an entry.

Imagine seeing a movie or a new release that you liked and being the first to post a blog about it: I saw the new X-Men movie last night and MoBlo'd on its five-star rating website !. Or imagine being able to blog a news item: I just saw a big accident on the M4 with junction 10 involving an oil tanker truck. Avoid this route. The police are on their way.

How it works • The owner of a blog site decides whether he wants to allow spoken blog entries on his blog site.

• He contacts SpinVox to open an account and provides standardized information, including the host of his blog site.

• It records the location (URL) and e-mail address.

• SpinVox provides the blog owner with a phone number (DDI).

• SpinVox converts any voice messages left in your DDI into text and either:

o sends them by email to the blog site email address.

o Post via HTTP or similar IP protocol directly to your blog site.

If the owner then decides to publish this number, for

52/129 example, by placing it on your blog site or sending it by e-mail to selected people, anyone can use this number to speak a comment on the blog. He can simply save this phone number in his contacts / addresses book, so that the speech on this blog and his entry will always be available.

Registering your name or nickname

When people blog, they often want to say who they are. SpinVox's Mobile Blogging provides users with the following options:

1. When you call the blog phone number for the first time, the SpinVox service will prompt you to speak your name or nickname.

For example:

The. Welcome to the SpinVox mobile blog. Please say your name or nickname as you want it to appear every time you blog, or press # to remain anonymous.

B. The user speaks his name or surname (Fred

Flinstone), or press #.

ç. Thank you. Please speak your blog post after the beep. It will be converted to text and posted on this blog site.

2. You can access a Spin-Vox website and register that when you call a given blog site (for example, blog URL: wwwfilmmaxblog.com) from a phone number that you have provided (for example, your mobile phone: 07812101742), it you must display your name (for example, Fred Flinstone) or enter a pattern, such as 'Anonymous'.

3. You can optionally specify that any other details are displayed with your entries^r, such as:

The. Your e-mail address.

B. Your Instant Messaging ID.

ç. Your VolP ID (for example, your Skype name).

d. Your phone number.

and. A web address.

f. Etc...

Technical solution

53/129

The major blog site providers (for example, blogspot, blogger.com, Yahoo !, Google, etc ...) provide an interface in such a way that the blog sites they host can receive an email that is then automatically posted on the intended blog site. They also provide standardized HTTP post interfaces that allow applications to post entries via the internet.

SpinVox determines which of the blog providers a user is connected to, and then automatically provides the correct type of interface to be used so that the text can be posted on the blog hosted by the provider, either via email or a posting method HTTP.

The converted text is then formatted and the relevant fields distributed to ensure that the posted text is displayed correctly on the blog site and has the correct information being displayed. For example:

• Hour and date.

• The text is optionally found between quotes (for example, I just saw Madonna's confessions and they have an unpleasant odor!).

• User name displayed on the Blog spoken by: &lt;user name or nickname&gt; (for example, Fred Flinstone).

o Anonymous blog entry.

• Any other data that the user has registered and chosen to be displayed o For example, email address, IM ID, phone number, VolP ID, web address, etc ...

X-Links on the Blog

Blog providers are able to automatically alert users when a new item has been added, including via email, SMS or IM.

By simply adding the phone number to the spoken blog message (SpinVox Mobile Blog phone number) to the text message or email, all recipients can select to

54/129 reply to this entry by calling this number (by clicking on it in the SMS).

Additionally, SpinVox directly helps people to respond to a particular blog entry by placing an X-Link within the text message, in such a way that it is posted with a particular reference.

IO

For example:

• Albert speaks a blog entry via SpinVox by calling the SpinVox blog number.

• SpinVox publishes its entry with an X-Link (for example, 02079652000p101).

• The blog site automatically alerts reader subscribers with a message that contains this X-Link.

• Readers who call this X-Link will have their responses associated with Albert's original entry and thereby create a list below his entry.

Exchanging Mobile Messages with Photos - MoPho ™

The market for photographs taken by mobile devices connected to the internet, typically from mobile phones with cameras, is evolving in the way of sending a picture message (typically MMS) to other phone users or downloading the image from a device to a computer and then save it, send it by e-mail or burn it to a CD.

A new modality of mobile photography has emerged, whereby a photograph taken by a mobile device can be automatically uploaded to a website for private or shared use. It solves several problems with copying or moving photos on the device, also sharing them on larger screens where the quality of the photos can be better appreciated.

However, users often want to post a comment with their photo while it is being uploaded to a website. The impact of a photograph (fun or serious) is most significant at the time it was taken, not hours, days or weeks later when

55/129 you are near a PC to view it and add comments. Using the device's small alphanumeric keypad to perform this task on the move is at least unpleasant.

SpinVox makes it possible for current standardized mobile photography services (for example, Cognima's Shozu) to add, with simple means, comments as they happen. The user now simply speaks his comment, which is converted to text and automatically published along with the photograph.

Example:

• Max takes a picture with his mobile phone while on vacation with two friends in front of a famous building.

• He decides to add a comment to the photo before posting it.

• I just met Bill and Ben in front of, guess what, Big Ben!

• The message is converted and published together with the photo on your photo sharing website.

• Max's two youngest daughters are at home in Scotland. They note that a new photograph has just been added to their father's photo sharing website.

• They laugh and call on their dad to see if he can take another picture of Bill and Ben with Scherlock Holmes.

The mobile photography service provider updates its application to provide the user with a phone number, which is automatically called when they select 'Speak a Photo Comment'. This number is mapped to the SpinVox conversion service, which then converts the message and sends it back to a designated location for publication with the user's photo.

1. Photograph taken by a telephone camera - Figure

56/129

2. The user then selects from the Options menu: Speak a Comment - Figure 9.

3. The application connects to a SpinVox service, sends a unique identifier to connect the speaker, the photo and the message.

4. The user is then prompted to speak his message: please speak your comment for the photo after the beep.

5. The converted message is sent to a mobile photo service provider's system that adds the comment to the photo.

Exchanging Mobile Messages Spoken in an Online Community

SpinVox has made available to the market several products from the SpinX family that allow users to be able to speak a message, have this message converted and automatically published on a blog site, or speak a message and have this message converted and sent to multiple recipients or as an SMS, email, MMS, IM or other message exchange format.

Twitter

SpinVox has made available to the market a service with which users of the increasingly popular Twitter service (www.twitter.com) can simply use their phones to call a local number, speak their messages and have them automatically published as text in their Twitter account. Of course, there is no longer a need for users to be in front of a PC and online to use Twitter.

Echo message - live posting confirmation

Every time users post something, they will receive an SMS response (or an echo) confirming that their post was made live or not, allowing them to try again. This idea applies to all types of web-based services that can receive posts, as users should know that their entries / posts have been successfully converted and posted live on the web, simply because users are not online, but yes on a phone. Echoes can be returned as email or IM or another form of messaging and shared widely to also keep a group informed.

57/129

This echo behavior complements the service that Twitter offers, which users can configure to receive an SMS every time someone in their group posts an entry. Thus, with SpinVox, all users can be in effective contact with their Twitter communities by phone, wherever they are. If someone in the group posts something on SpinVox, the rest of the group will automatically receive an SMS with what he said, and of course the option to give a reply or update. This way there is no longer any dependence on someone in the group to be online so that the group stays in touch.

Removing the existing dependency on Twitter represents a significant step forward, and indeed, for all other messaging service providers (PC-based).

Exchanging Messages on Social Networks

Any social network, community forum or other type of online community can benefit from the fact that SpinVox provides a simple way to stay in touch with your community just by calling your messages, letting SpinVox convert and post them on their accounts and then leveraging existing messaging services for others to view the new posts. These communities can also be mobile.

X-Links open the capacity for these communities to use SpinVox without signatures and complex decisions. Once they receive a converted message, they can also be offered a link that allows them to speak a response that is also posted online, thereby enabling the entire group to stay in touch, wherever they are, with a simple phone call. .

For example, Yahoo! offers messaging services to its users, and these as groups can now broadcast messages via Yahoo! online to each of them, but only when all are online and authenticated. With SpinVox, they will have the ability to 'spread' a message to group members and know that it will be received by everyone whether they are online or not.

Voice Explosion

The idea is for a 'Voice explosion' to reach users who are both online and offline, like a text message from one or

58/129 otherwise (SMS, email, IM, etc ...). It consists of a form of group diffusion via voice to text in which the group is defined by its online connections, but transmitted to all places, particularly mobile.

Dial tone = web tone

In short, this expands around the idea that as SpinVox is a network service, anyone can now use telephone networks of any kind to speak a message that will appear as an online text in an account or place of their choice.

What this also means, is that no user, in fact the whole group, does not need to be authenticated in their online service / account (for example, Twitter, Yahoo !, etc ...) to be in contact with others. This means that these services can be used by the whole group, completely offline, and through a simple phone call.

Reducing the User Name / PIN barrier to a phone call

What this also means is that a user's phone number (that is, their CLI or MSISDN on mobile networks) becomes their identity for posting on online services. The advantage of this lies in the fact that to post to an account or blog or other online service, there is no need to remember URLs, usernames or passwords - just make a phone call and you're done!

Implementation of Micro-ô / og Twitter

This section addresses the requirements for launching a new product specially designed for use with www.Twitter.com. Twitter is a m \ cro-blogging environment, to which users (tweeters) connect and then publish with small updates (tweets) what they are doing, using IM, SMS or the web. These newsletters appear on www.twitter.com on their personal pages and are then sent to their friends as web updates or via SMS. Tweets are limited to 140 characters. Twitter provides an API that allows third-party developers to integrate applications and services.

There are two paths to the product strategy. The first is the demo: A user can test the SpinVox Twitter demo by calling a local country IDD, and see the resulting conversion on the SpinVox Twitter demo account. This does not require any

59/129 subscription: just call the number and check on the website. It is analogous to the Create-my-Blog demo on our website. The second way is a more typical Create-my-Tweet service: Users can sign up for a Create-my-Tweet account. They can then call a local country IDD to leave a short message, which is converted and sent to Twitter.

Product Overview DEMONSTRATION • Customers can try the demo at www.spinvox.com by calling the local SpinVox demo number for twitter. Your tweets will appear on the SpinVox twitter page at www.spinvox.com and on the SpinVox demo page on twitter.com. No account is created.

• An SMS is returned upon successful / non-convertible conversion.

• No SMS is sent on disconnections.

• Entries will be moderated, however after submitting to Twitter.

LIVE • The customer opens SpinVox to his Twitter account at www.spinvox.com and enters his Twitter username and password. The user is encouraged to subscribe to SpinVox and use a mobile number.

• The user receives the initial PIN via SMS and is asked to authenticate to create an account.

• When authenticating, the customer receives a second welcome SMS from SpinVox asking them to save their Tweets from DDI to the incoming phone.

• The customer calls the local SpinVox number to the Twitter number and leaves a message.

60/129 • If the message is converted, the text is sent to Twitter.

• Optional SMS notification on conversion and non-conversion.

• On disconnections, no SMS notification is sent.

• All SpinVox Twitter accounts are automatically added to SpinVox Corporate friends lists at www.twitter.com (via an API).

Twitter implementation requirements

1. Service Level

1.10 end user subscribes to www.spinvox.com to use SpinVox's full Twitter service.

1.2 The service must meet the same availability requirements as the Crie-meu-Vmail service.

1.3 Recordings must be limited to 30 seconds.

This limit will be reviewed periodically after launch to decide whether the limit should be lowered (for example, 20 or 15 seconds).

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

There must be a configuration parameter to specify the number of characters, which will initially be set to 160.

1.5 The TAT should be 98% of messages within 10 minutes, measured over a calendar month, in which the daily average is 18 seconds or less. That is, it must meet the same TAT requirements of Crie-meu-Vmail.

1.8 At the initial launch the service (demo and live) must support the following languages:

• English UK • US English • Canadian English

61/129 • Canadian French • German • French • Spanish • Australian English • South African English

1.9 At the initial launch, local country DDIs must be provided for the following countries, for both the demo and live (ie, two DDIs for each entry in the list below).

• UK (language: en-GB) • US (language: in-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 Local country DDIs should be golden memorable numbers, that is, in US - 415 TWITTER or similar. Priority should be given to live numbers over demo numbers and US and UK numbers.

1.11 After the initial launch, LIVE service numbers must be able to handle high volumes of competing calls.

2. Customer interaction with IVR

It is expected that there will be minimal interaction between a customer depositing a message and the IVR system.

Live CLI service retention

2.1 For live service, if the caller has retained his CLI, the caller must be informed to hang up the held number and call again.

Language selection

62/129

2.2. LIVE Service - If the caller has a SpinVox account and the language of the account is one of those listed in application 1.9, he must use this language. Otherwise, the language must be that associated with the dialed number. Note for the DEMO service - the customer does not need to have a SpinVox or Twitter account to call the Demo DDIs. If, however, the caller has a SpinVox account, the language of your choice should be used, rather than using the language associated with the country's local IDD.

Use from unregistered phone

2.3 If the caller's number is not associated with a Spin / Vox or Twitter account, the caller must be directed to the SpinVox website.

Demonstration greeting

2.4 When a user calls SpinVox for a DDI Twitter demo, they should hear the following greeting:

Welcome to SpinVox for Twitter, please speak your message that will appear on the screen at the tbc-address web address. If the caller has retained his CLI, he should also hear:

You will not receive any confirmation SMS, as you have retained your number.

Live service greeting

2.5 When a customer calls a regular Twitter DDI, he / she will hear the following message:

Please speak your Twitter message after the tone. The voice to be used for all IVRs will be female and the same as for all other SpinVox products.

2.6 During the recording of the voice message, the caller must be able to press the # key to re-record his message. The caller must be informed of this feature, the first three (3) times he uses the service. In this case, the alert for requirement 2.5 must be:

Please speak your Twitter message after the tone. To re-record your message, press the cerquinha (#) key at any time.

2.7 If a customer exceeds the recording limit specified in requirement 1.3, he will be prompted to re-record the message or

63/129 leave message as it is. This mirrors the current behavior of other SpinVox products.

2.8 There will be no DPA alert.

3. Account provision / management Subscription information

3.1 To create a SpinVox account for Twitter at www.spinvox.com, the user must provide the following information:

• mobile phone number • Twitter user name and password • email address • preferred language • parents

If the country is the US, the user must also provide the state

A DDI must not be assigned to the user, but rather, he must be informed which of the country's local DDIs (see requirement 1.9) he should use. The use of the SpinVox Twitter demo does not require the creation of an account.

SpinVox tweet-out

3.2 By default, when a user signs up for a SpinVox account for Twitter, a tweet must be posted to their Twitter account:

I just subscribed to SpinVox for Twitter at www.spinvox.com/twitter.

The subscription page must have a bookmark that controls whether the ad was posted. It should be normally turned on.

Twitter account validation

3.3 When a user is registering for a SpinVox account for Twitter, the account details must be checked for validity. If the account is not valid, a link will be provided to the user directing them to the account creation page at www.twitter.com.

PIN notification via SMS

3.4 When an account is created according to the step

64/129

3.1, an SMS is sent to the user with an initial PIN, which he needs to authenticate himself on the website.

Welcome SMS

3.5 A welcome SMS is sent to the customer as soon as 5 he successfully authenticates the first time. Welcome SMS copy

TBC.

SMS notifications

3.6 The customer can control how he will receive SMS notifications in these two cases:

· message converted and sent to Twitter.

• the message could not be converted.

These notifications can be controlled independently through proper care, so the user can turn off the notification of converted messages, but leave the notification of non-convertible messages on, for example. On new accounts, SMS notification must be turned off for successful conversions, and turned on for non-convertibles. These options should not be provided on the subscription page.

SpinVox Friends

3.7 By default all new SpinVox accounts for

Twitter should be added to the Friends list on the SpinVox Twitter page

Corporate (own Marketing page). A user must be able to unsubscribe from the list through a personal care check. This fact must be included in the T &amp; C's, which will be linked on the subscription and personal care page.

Personal cares

3.8 The customer can modify the following information in the personal care section:

• Twitter username • Twitter password

The user will be able to modify all other fields provided during the subscription as part of the regular use of the personal care section.

PIN access control

3.9 The user can enable PIN access to deposit

65/129 messages in your account. If enabled, the caller may be asked to provide the account PIN before receiving the regular alert (requirement 2.5).

4. SMS message to the caller

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

4.1 For the demonstration service, if the caller's CLI has been retained, no attempt should be made to send any confirmation SMS's.

4.2 The text message will come from the called number - either from the DEMONSTRATION number or from the LIVE number of the local country IDD.

4.3 On successful conversion, the message body should show in Citation marks, for example,

DEMONSTRATION = From: &lt;SV Twitter Demo

DDI&gt;

Your tweet &lt;extract from the tweet&gt; is posted at www.spinvox.com/twitter (tbc)

LIVE = From: &lt;SV Twitter Local IDD&gt;

Your tweet &lt;extract from the tweet&gt; was posted to Twitter managed by SpinVox

The total SMS text cannot exceed the limit specified in application 1.4. If the full tweet cannot be included, then the extract must be ended with ... (ellipse).

4.4 If not successful, the mobile caller will receive a

SMS as below.

Sorry, the tweet you left could not be converted to text. Please call &lt;dialed number&gt; and try again. Thank you - www.spinvox.com.

4.5 There will be no QuickLink ™ at the end of the message.

4.6 No SMS will be sent to the caller when a call is disconnected.

5. Conversion

If the message was successfully converted, the tweet should

66/129 be sent to the client's twitter page. The message must be tagged with a SpinVox hyperlink.

5.1 LIVE = Converted messages should be sent to the customer's twitter page, with the SpinVox source link directing the user to the product page www.spinvox.com/twitter.

Demo tweets moderation

5.2 All tweets for the SpinVox Twitter demo can be removed by a moderator after posting to Twitter.

5.3 Twitter messages must start with the word say and followed by conversion to double quotation marks to indicate spoken messages, that is, say hello I'm here talking to twitter. The total post must not exceed 140 characters. If the converted text is too long, it must be truncated, and the extract must end with ... (ellipse).

6. Reporting

It will be necessary to report the activities of the SpinVox service to Twitter. The hearing of all reports is internal to SpinVox, there are no external reports.

6.1 It should be possible to generate reports of all messages from this service • Divided by language.

• Separate conversion per product and per customer (conversions, non-converted and disconnections).

• Daily number of authentications and accounts successfully created (authentication = not authenticated on website to open an account).

• Daily active users.

• Average message duration.

• Conversion length (in characters).

• Average number of messages / users per period (hour / day / month).

• Traffic profile by time of day / week / month.

7. Future requirements • Option to charge for this service in the future

67/129 using credit card.

• Option to switch the terminating number to a classified number to generate time revenue from deposited calls.

• Ability to track call duration for billing per minute / second.

• Review of private messages / commands and how to use them.

• Ability to block callers from calling certain number / tariff ranges.

8. Web Experience

Customers arrive at www.spinvox.com and see the Twitter brand logo or button on their home page. They can also access the SpinVox page for Twitter through the product links on the home page.

When customers click on them, they see a SpinVox page for Twitter - containing:

1) A Twitter logo.

2) Instructions about the product and how it works with the

Twitter.

3) Instructions on how to set up Twitter to work with SpinVox, and how to tell your friends to receive SMS updates.

4) SpinVox FAQ for Twitter button (tweets posted using existing privacy settings, etc.).

5) A SpinVox demo for Twitter and a demo button (showing the page www.Twitter.com/spinvox OR www.spinvox.com/twitter). No account is created during the demo process as all entries are posted as SpinVox.

6) Button click here to invite the user to create an account.

7) The user must enter his Twitter username and password, along with his mobile phone number and email. Encourage the user to put their mobile phone number as a choice

68/129 primary.

8) Ability to manage the service from within the

My account.

SECTION D: MESSENGER OF LOST MESSAGES Missing Messages ™ Messenger

Missed Messages Messenger (MCM) solves the problem faced by many callers and operators - that is, in markets where voicemail is not enabled, callers now have the option to speak a text message or any other format to the person they tried to call and so stay in touch.

Many markets have less than 50% market share with voicemail, such as southern Europe (Spain, Italy, Greece, etc ...). The two main reasons are:

1. Voicemail is a chargeable service and, in significant markets for prepaid mobile phones, users tend to turn it off to reduce costs, as calls for placing and removing voice messages are in the 20 cent range. per event.

2. Culturally, voicemail is perceived as too formal and commercial, and often seen as a rude way of exchanging daily messages.

Overview

The general view of what callers do in this scenario is not to leave a voice message - where the voicemail exists, or where it does not exist to type a termination (for example, no call, busy, disconnected) - but instead this to hang up and in about 30% of cases to type a text message to the person they tried to call. So, currently, and in these cases, the message exchange format chosen is to send a text when they are unable to contact the person they are calling.

For operators, missed calls (not completed) of this type account for several billion events per year. In Spain, the second largest network (Vodafone) has around

2.3 billion missed calls per year.

MCM solves this problem in an elegant way for all participants. It is a network-based service, so there is no

69/129 no dependency on a handset and works as follows:

&gt; When a call is being placed to a subscriber / customer who does not have good voicemail services, the network knows how to pick up the call before it fails - busy tone, no call, phone disconnected or unavailable / out of reach.

&gt; The network then answers the call and plays an IVR recording for the caller like: If you want to speak a text message to the person you are calling, press 1.

&gt; If the user selects this option (for example, 1), then he is simply offered an alert to let him speak his message - for example, speak his text message after the tone.

&gt; The system then records the audio, sends it to SpinVox VMCS for conversion, and the converted text is then sent to the called partner, and sent as if the message originated from the calling partner, and not from a system number or name. This is typically done using the caller's CLI by placing it in the 'from' field of the sent message.

Currently, this process is being used with SMS, but any other modalities of exchanging text messages such as MMS, e-maii and WAP / HTML pages can be used depending on the capacity of the networks and the user's requirements.

The benefits are simple, but quite broad:

&gt; Callers are able to connect the first time when they need it.

&gt; Recipients immediately see who called them and can read the current message.

&gt; The function of choosing the message and charging is reversed. Typically, voicemail is a

70/129 B-partner service (recipient) for which he pays and chooses to receive it. With MCM, voicemail is in fact a partner-A service (caller / sender) that the user chooses every time they use it (without subscription) and can also be charged for using the service.

&gt; Operators can generate new lost call revenues, because now the caller (partner-A) can be charged for the option of speaking a text, or for call termination charges, premium category SMS or inter-network charging models - all of which exist today.

o Likewise, a more classic partner-B charging model is also possible, just as it is today with voicemail.

&gt; Call continuity (the number of additional calls, text messages or data traffic generated as a result) increases. This continuity is expected to be greater than the missed call alert products which are known to be 2-3%, and the SpinVox MCM is expected to be more similar to the SpinVox voice-to-text mail it has an impressive 7% voice lift and 17% text lift.

&gt; This service answers callers from any network, not just those on the home network. For example, Callers can call a person on network y from the network x. Network y has MCM enabled and can offer this service to callers on network x and generate additional revenue from any missed calls, not just the network. Similarly, the process can be

71/129 reversed, in such a way that this service can be offered to callers from the host network (network y) when it is impossible to connect to users on other networks (network x). These combinations provide the host network with the ability for the MCM to capture all missed calls related to its independent subscribers / customers if they are partners A or B. See the table below.

&gt; Some networks can implement this process as a recipient service (B-partner) and charge users for the service as much as voicemail is being used today, so MCM can be adapted to existing business models.

How MCM is being implemented:

Figure 10 shows the MCM with SpinVox Correio de

Voice to Text also implemented.

MCM allows the host network to service partner-A callers regardless of whether or not they are on the home (host) network, providing 100% reach to handle missed calls related to their subscribers / customers:

<td>Partner-A (caller)</td><td>Partner-B (recipient)</td><td>MCM available</td>

<td>On the network</td><td>On the network</td><td>Yes</td>

<td>On the network</td><td>On the network</td><td>Yes</td>

<td>On the network</td><td>On the network</td><td>Yes</td>

<td>On the network</td><td>On the network</td><td>Not</td>

Clearly, missed calls that occur among 25 other networks are beyond reach.

Pricing Options

When required, MCM can be priced in different ways:

72/129&gt; Rates of termination of calls to the A-partner (caller) based on a minimum value and / or tariffs per second / minute. This process is similar to the way in which deposited voice mails are charged.

&gt; Award category confirmation SMS sent to partner-A to charge him whenever he chooses to use the MCM.

&gt; Inter-network tariffs for the service, so x &amp; y networks can agree on mutual charging and, consequently, charging their users with a certain amount for each event that appears in their account. The difference here is that this pricing can be done through premium product APIs or protocols to place the product / service in a different pricing category, rather than in standardized voice calls.

&gt; Free - the impact of call continuity and call completion can be highly favorable and offset any need to generate explicit revenue at each event.

Again, this process can be reversed in such a way that it is a service for a B-partner and that it pays for it as shown in any of these methods, or that it is a standard feature as voicemail currently is.

Product Options

Since not all networks can handle calls as shown in the descriptions above, there are other ways to provide MCM:

Option 1: Callback for message • A call is attempted for partner-B, fails and is discarded.

73/129 • Partner-A is called by the network and receives the service offer.

• If accepted, the message is recorded and processed.

• Partner-A is charged only if the message is converted.

• If not converted, the B-partner receives a standard lost message alert.

Option 2: Return text for the message • Similar to Option 1, but the service is offered via SMS.

• Partner-A responds to SMS if you want to call the service.

• Partner-A calls the IVR via the link embedded in the SMS (free call) - see XLinks above.

• Charging by the service only if the message was successfully converted.

• If it was not successfully converted, the B-partner receives a standard missed message alert (MCA).

Recovery options

In all of the above for MCM, partner-B (recipient) may want to hear the voice message. In this case he may be offered a number to call and have the message replayed for him.

This modality is an extension of SpinVox's existing QuickLink ™ technology in which the converted text message to partnerB contains a link that places a call to a network service (typically IVR) which then automatically plays the message. The link itself can be a real phone number and a set of digits, which when entered by the user inform the system exactly what the message is to be reproduced.

Alternatively, this can be a virtual number that the network can create, which means that with a call the network recognizes the type of call and exactly what message is related to it.

74/129

Attached or embedded audio

Alternatively, the audio is hosted on a website and is returned as a stream over a data channel, or it is sent as an attached / embedded file, which is possible with MMS, e-mail and other methods of exchanging messages with multimedia capabilities.

Of course, audio recovery can create new incremental revenue for the operator that did not exist before.

SECTION E: OVERVIEW OF SPINVOX PRODUCTS

The preceding Section D described a specific innovation, the Missed Messages Messenger. This Section E provides an overview of the SpinVox product suite.

Two generic types of products are available:

• Sender: where you choose to speak a text message.

• Recipient: where you want people to text you.

All of these products share a person's ability to speak a text message of some format to another person. Figure 11 shows how several conventional messaging products (voicemail, e-mail, SMS, IM and voice) are distributed along Time versus Dialog axes. Figure 12 shows how the different SpinVox products change this scenario.

• Recipient products extend a dialogue; reduce inherent delays in receiving messages; provide voice mails (push); use a seamless interface; they are ubiquitous and work with any device, any technology and any network.

• Sender products initiate new dialogues; use a simpler interface to make mobile messaging more intuitive; allow ordinary users to Speak, and Don't Type with Thumb !; do not require

75/129 no new learning; allow existing applications to be improved; generate new modes of message exchange to provide real 'mobility' - such as safe use and quick use even while driving, walking, etc .; allow new recipes for existing products.

We will now look at each category in greater depth.

Recipient Products

These are all products for which you actively decide to enable others to send you messages by speaking text messages to you.

E.1 Voice-to-Text ™

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

QuickLink ™ allows users to listen to the original message to which the text refers.

E.2 Voice-to-E-mail ™

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

When the message has not been converted, the original audio message can be sent to him as an e-mail attachment.

QuickLink ™ allows users to listen to the original message to which the text refers.

E.3 Call-to-Mail ™

Designed for call centers, direct marketing responses and other direct functions with customers. Callers can:

• choose to leave the list and speak a message that is converted and sent as an email.

• always be asked to speak a message that will be converted and sent as an email.

76/129

Ε.4 No Answer - Speaking a Text - (Missed Messages Messenger see also Section D)

Designed for users who do not have voicemail, or who want voicemail, typically a large number of mobile phones in the prepaid market, or not associated with the voicemail market.

This is a network-based service that manages unanswered calls and offers callers the option of speaking a text to the person they were trying to call. It applies to unanswered, busy or rejected calls (sends busy signal).

A network operator implements these options on all user accounts that do not have a voicemail or equivalent voice messaging service.

1. When a subscriber does not answer your call, 15 a new option is offered to the caller: Sorry, this person is not available. To speak a text to her, press 1 now.

The. Optionally, the caller is charged either for the time connected on the line, or per event, for example, Calls cost 50p per minute, minimum charge 20p.

2. The caller then records your message.

3. The subscriber who missed the call receives a text message from the caller, with what was said in text form.

The. Optionally, the subscriber is given a number to call and listen to the original message.

What is unique about this service is the fact that subscribers do not need to subscribe or pay for the benefit. This option is given to callers, as it can be important to send a message to the person they were trying to connect to.

Subscribers can choose how they want the message to be delivered: SMS, email, etc ...

Sender Products - Network Based

These are all products for which you decide to send a message to someone, which is then converted and sent to them as text.

77/129

Ε.5 Callback - through Speak a Text

Service providers have offered subscribers a way to return a call within voicemail - callback - that the subscriber starts by selecting an option before or after the message is played. This adds a new callback option, giving them a text response message:

1. Users call to listen to voicemail messages. At the beginning or at the end of each message played, the option of leaving a text response to the caller is offered:

ío To speak a text to this person, press 1 now.

2. The user then presses 1 and speaks his message; it is converted and sent directly to the caller's number.

The. The voicemail system has the CLI of both the caller and the subscriber, and can thus correctly format a converted message that is sent from the subscriber directly to the original caller. The recipient (original caller) is offered a link so that he can hear the original message.

E.6 IVR - Speak a Text (see also Appendix I)

In any IVR system, an option can be provided to all callers, with which they can speak a message to anyone having it converted and sent as text.

1. The user calls either a dedicated number, or calls his voicemail and receives this option to speak a text to someone:

To speak a text to someone, press 1.

2. The user is then prompted to enter the recipient's phone number. He enters the numbers on the telephone keypad and the system detects the DTMF signaling tones or equivalent, or selects them from his address book.

3. The system checks whether the phone number is valid.

4. The user is then prompted to speak his message:

Please speak your message after the tone.

5. It speaks your message, which is converted and sent directly to the caller's number.

The. The voicemail system has the CLI of both

78/129 caller as the subscriber, and can thus correctly form a converted message that is sent from the subscriber directly to the original caller.

E.7 Network Service - Speak a Text

This service is typically used for terrestrial networks where people are used to dialing phone numbers, but it can also be technically used on any type of network - fixed, mobile, wireless, VolP.

If you want to speak a message to someone, simply place a call 'modifier' (prefix or suffix) next to the number of the person you want to send the message to. The user then hears the message 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 so that he can hear the original message.

Sender Products - Handset Based

These apply to users who want to text someone instead of calling them, much like sending an email or SMS to someone. More details are provided in Section E.10 below.

E.8 Spoken SMS

There are four Talk-to-Text options on a handset:

1. The application on the 'main' screen.

2. The menu option in the Address Book / Contacts.

3. The menu option in messaging applications.

4. The menu option in the Calls / Calls list

Lost.

The. Natural extension of existing native applications.

B. New option: 'FaleTxt'.

Note: Although a Spoken SMS is being shown, the concept is the same for speaking an MMS, an email, an Instant Message or any other type of messaging product.

79/129

Correio.9 Spoken Mail

An application on the handset allows a user to select who he or she wants to send an email, SMS or MMS to. He is then offered a Talk to Mail function. The user is connected to SpinVox's spoken message service, in which he is prompted to record his message. The application detects who the mail is for - via email address or address list, subject, and any other message parameters.

Figure 13 shows an example of an implementation of a Spoken email and a Spoken SMS / MMS with a mobile service provider - SIP phone connectivity.

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

Do &amp; Ignore Principle

In any of the methods shown, there is a simple principle that makes the user experience unique:

• minimal effort - just speak your message.

• nothing to learn - the same as leaving a voicemail in a standard voicemail.

• reliable - as few steps as possible to avoid confusion or technical failure.

• robust - only if the message was not converted do you need to do something, otherwise you know it has been converted.

The next section will focus on handset-based sender products.

E.10 Speaking a message from a mobile device Speaking a message

SpinVox created the software application Fale-umamensagem (also called CrieMeuTexto), which when loaded on a device such as a Nokia mobile phone (model 1), allows the user to speak the message that is then delivered to the recipient as text.

The purpose of this service is to provide the user with

80/129 the ability to speak the message instead of typing it on your phone's keyboard. This process is more convenient, easier and faster than typing the message on your phone's keyboard.

Messages can be sent to recipients in the form of email, SMS or MMS messages, depending on the details stored in the device's Address Book. The same message can be sent to multiple recipients using the application's 'broadcast' facility, and messages can also be forwarded to customer blogs or other web-based applications.

Embedded items in the menu

Additional functionality is brought to the device with the addition of new menu items in the standard menu tree. The Speak-a-Message menu option is added to the following applications:

• Text Messaging Application.

• MMS message exchange application.

• E-mail application.

• Instant Messaging (IM) application.

• Address Book.

• Call log.

• Standard screen, using a soft key.

The functionality that the menu options provide changes dynamically depending on the application the user is using, as detailed below.

Text messaging app

Selecting the Speak-a-message option allows the user to:

• Create a new message using the mobile numbers of the contacts as a destination.

• Respond to a previous message using the number provided.

• Apply to SMS, MMS, IM or another messaging application on the device.

81/129

Email application

Selecting the Speak-a-message option allows the user to:

• Create a new message using the contacts' email addresses as a destination.

• Create a new message for multiple recipients using their email addresses as a destination.

• Reply to a previous message using the contacts' email addresses as a destination.

Below are the generic actions that a user will take either in the text messaging application or in the email application to send a message.

1. The user selects the Message / SMS exchange application, selects the option 'Speak the message' from the menu and is directed to Contacts.

2. When the Contact was selected, a connection to the SpinVox platform is established.

3. An advertisement requesting the user to speak their text message is then played.

4. The user leaves an audio message.

5. The information from Partner B is passed to SpinVox (Selected in Step 2).

6. The SpinVox platform converts the audio into a text message for delivery.

7. The message is then sent from Partner A to Partner B as if he had typed it.

8. Partner B receives the message and it appears as coming from Partner A. No special system numbers have been used or replaced.

Figure 15 shows the typical experience of a user speaking a message from within the Text Messaging or E-mail Application.

Address Book

82/129

Selecting the Speak-a-message option allows the user to:

Create a new message (Smart addressing decides the message path). Below are the steps taken by a user accessing the Speak-a-message service from within the address book application:

1. The user selects a contact from the Address Book.

2. The user is presented with a menu option to

Speak a message.

3. When Speak a message is selected, the smart addressing function checks the available methods of delivering messages and connects to the SpinVox platform.

4. An advertisement requesting the user to speak their text message is then played.

5. The user leaves a message.

6. Partner B's email address or phone number is passed to SpinVox's service (Selected in Step 1).

7. The SpinVox platform converts the audio into a text message for delivery.

8. The message is then sent from Partner A to Partner B as if he had typed it.

9. Partner B receives the message and it appears as coming from Partner A. No special system numbers have been used or replaced.

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

Call Log

Selecting the Speak-a-message option allows the user to:

• Create a message for the numbers listed in the Missed Calls log, using SMS as the answer path.

• Create a message for the numbers listed in the

83/129 Call Out record using SMS as the answer path.

• Create a message to the numbers listed in the Call Entry log using SMS as the answer path.

The methods described above are easily accessed using the device's main navigation buttons, such as Call, or Menu. There is no need to use the alphanumeric keyboard with less accessibility to enter information.

The steps outlined below represent the generic actions a user takes to answer someone whose phone call was missed, or to answer someone they recently spoke to.

1. The user selects a contact from the

Calls.

2. The user is presented with a menu option to

Speak a message.

3. When the Speak a message option has been selected, a connection to the SpinVox platform is established.

4. An advertisement requesting the user to speak their text message is then played.

5. The user leaves an audio message.

6. The Partner B number is passed to the SpinVox platform (Selected in Step 1).

7. The SpinVox platform converts the audio into a text message for delivery.

8. The message is then sent from Partner A to Partner B as if he had typed it.

9. Partner B receives the message and it appears as coming from Partner A. No special system numbers have been used or replaced.

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

Soft key access

84/129

To activate the Speak a message application from the Standard Screen of a mobile phone, it is possible to use one of the soft key shortcuts, instead of having to navigate to a particular application first, such as the Address Book.

Caller Access - Soft Key

Below are the steps a user will take to speak a message from a device's Standard Screen.

1. The caller selects the Speak a message soft key and is directed to a list of Contacts that can receive spoken messages, from which he then selects a contact.

2. When the option Speak a message is selected, a connection to the SpinVox platform is established.

3. A warning requesting the user to speak his message is then played.

4. The user leaves an audio message.

5. The Partner B number must be passed to the SpinVox platform (Selected in Step 1).

6. The SpinVox platform converts the audio into a text message for delivery.

7. The message is then sent from Partner A to the

Partner B as if he typed it.

8. Partner B receives the message and it appears as coming from Partner A. No special system numbers have been used or replaced.

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

Extensible application

The Speak a Message app can be easily extended to provide additional functionality for many different types of

Exchange of Spoken Messages. Additional types of messages include Social Media applications such as Blogging and peer-to-peer communications, such as Instant Messaging.

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

85/129

Figure 20 shows a typical user experience of speaking a response on a Mobile IM client.

'Do &amp; Ignore' user experience in 3 clicks

The Speak a message app uses a unique 'Do &amp; Ignore' system to create and deliver messages. It differs from other systems that require the user to speak, review (on the screen) and confirm before finally sending the message.

Do &amp; Ignore means:

• minimal effort - just speak your message.

• nothing to learn - the same as leaving a voicemail in a standard voicemail.

• reliable - as few steps as possible to avoid confusion or technical failure.

• robust - only if the message is not converted do you need to do something, otherwise you know it has been converted.

The Speak a message app takes control of the mobile device, providing a means for it to always be 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 who to send a message to ... say a message.

3. Disconnect.

Figure 21 shows the user's '3 clicks' experience

The Do and Ignore system combined with the 'no more than 3 clicks' approach means that the user can send messages with which other systems could not be used, such as walking along a street, or in a situation where it is not possible to look at the screen for a certain period of time.

The Speak a message app is also designed to be used with just one hand, with all functions easily accessible with the activation of a single key click and with the menu.

86/129 handset navigation.

Figure 22 shows the 'Do &amp; Forget' system used by Speak a Message.

Addressing and intelligent message delivery

When a user decides to speak a message to someone on their list or in their Address Book, the type of message to be sent is decided by the contact details available in the address book.

• If only one e-mail address is available, the message is sent via e-mail.

• If only one mobile phone number is available, the message is sent via SMS or MMS.

• If an online account name is present for IM or another, the message is sent through them.

• If multiple are available, the message can be sent to a selection of recipients, however, by default the message will be delivered to the mobile number.

Quick address list

The quick address list is a smart list compiled from recent contacts, and produced comprising the previous behavior of users.

The algorithm builds a list of people with whom the user was most recently in contact, taking into account the following aspects:

• The type of communication (email, text message, phone call or spoken text).

• The frequency of communication with this contact.

• How recent the last communication was.

• Alphabetical order.

The list is then presented as a single, easy-to-read list, which still provides easy access to any contact in the customer Address Book. The list differs from existing 'Call Lists', such as

87/129 as the Sent SMS folder, as there is significant intelligence applied in creating the list of Quick Addresses.

Figure 23 shows the Quick Address List showing the recent contacts that Called, were Called, received Texts (SMS or MMS) or received E-mails (or any other messaging / communications used). Because the Quick Address List is comprehensive, it becomes the central resource for all unified communication tasks that the user needs to perform.

The exchange of unified messages breaks down barriers between various forms of communication, such as voice, email and voicemail.

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

Having the ability to respond to voice messages using text or text messages, the use of voice seems to be trivial, however, it is a means for the end user to improve or even increase their productivity, especially if it saves time in communication with someone else.

For mobile users, accessing and using the phone is essential, especially while on the road. With the Speak a Message app offering a unified messaging experience, mobile users can receive and respond to voice messages, email messages and fax messages, speaking an answer, and can maintain a higher level of productivity while are out of the office.

Automated message transport selection

Messages are sent to the SpinVox platform using the most appropriate transport method available. For example, a spoken email will be captured on the device typically as a WAV file, it can also be of any audio file format, and forwarded to WMCS as an email using 3G or GPRS data channels, if available. Once the message conversion is complete, the result is sent by email to the recipient.

The routing of messages from the mobile device to the

88/129 SpinVox platform runs on an intelligent basis depending on the availability of transportation methods. The choice is made from the following list:

· GPRS data connection 3G data connection. SMTP interface, http interface.

IVR (fixed line).

MMS.

If the optimized method of transportation is unavailable, the application automatically checks the availability of the next most appropriate method and uses it.

Asymmetric message exchange

This software creates a new and unique set of options for the user and recipient to keep in touch using a range of connected messaging options.

Outgoing call becomes a text message

What makes this service unique is the fact that the original message begins its existence as a spoken message, and when it is finally delivered to the end customer's device, it not only appears in their inbox, but it is also transposed in an email or SMS.

Incoming call answered by e-mail or text message

With the creation of this service, SpinVox allows the recipient of the original voice message (or missed call) to choose to respond by speaking a text message or e-mail, instead of the traditional way of calling the sender of the message using the telephone or typing a message on the device's keyboard. This process is unique in that, once the recipient responds to the original message via an e30 mail or text, the end-to-end communication method changes from voice to text and, once the response was sent to the person who generated it, this person can also reply via text message, email or speaking a message.

89/129

CreateMyText (SMT) product requirements

The key to the success of this application lies in its simplicity of activation. It must be possible to invoke it by pressing a single button, which is available on any handset, and to complete the process from start to finish in no more than 3 key presses. The SMT product offering will be ideally positioned with Mobile Operators and Business Customers, allowing 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 speak an email message) -mail). The audio file is captured by the SpinVox platform and converted into a text message for delivery.

The product must meet the following criteria:

Accessible with one hand, one finger - The application must be so simple to start and use that it feels like a 'hands-free' application. The crucial test for the success of this application is the fact that it can be used on the fast lane of a highway in a safe and legal way.

Nothing new to learn - It should be as simple as making a voice call, requiring no more than 3 keystrokes to start, use and complete the service.

Do &amp; ignore - It should be as reliable as any other service, for example, voicemail or text messaging, and there should be no need to check the content of the message.

Customer Touch Points - It should be a simple and single click that initiates SMT addressing. Familiar interaction &amp; metaphors used by the current UI should be used.

Information about the Called Partner ('B') automatically sent - No further interaction, for example, speaking or entering a number, must be necessary for the customer to use the service.

Simple Implementation - An application to enable the new functionality must be available for download using a simple URL, WAP link or low-range wireless connection such as Bluetooth. The application must also be upgradeable using the same method.

Upgradeable - It should be possible to update the product to add new features, with minimal customer intervention and without having to

90/129 terminate the application manually.

Non-intrusive - The application cannot prevent another application from running on the handset, and attention should be paid to events that may impact the application, for example, how the application reacts to an incoming call during SMT call setup.

Customer insight

There are many situations in which a person may prefer to speak a text message, rather than typing it or making a voice call. The common issue is that a user needs a quick and simple way to send information to someone, and generally cannot or does not want to stop what they are doing. The key view here lies in the fact that accessing functionality and simplifying message addressing is just as important (if not more important) than the voice-to-text element (which must be taken into account).

NB. The customer experience should be the push of a button to start the process (on any device), a click to select the recipient, and the final click should be to end the phone call / recording process.

The user experience should also exploit the fact that sending text messages to mobile users and the caller's logging ecosystem are typically limited to a handful of numbers.

Storing Contact Numbers

The format in which mobile phone numbers are stored on a mobile handset is the key to successfully delivering a text message from the SpinVox system.

Certain assumptions must be made to determine the Country of destination of a text message, if the number submitted to SpinVox is of a non-international format.

The following behaviors shape the assumptions that must be made, to define the Country of destination of delivery of a text message.

The International Business Traveler

Anyone who regularly travels internationally has at least 80% of their contact list filled with

91/129 numbers of International format.

The remaining 20% ​​is probably stored in the local format of the country where the traveler resides. It is very unlikely that he will have a number stored in the local format of a country in which he does not reside.

The unusual business traveler • It is likely that he has a mix of numbers in an International and non-international format.

• Any non-international format numbers stored on your handset will be from the country where you live.

The non-traveler

The contact list of the non-traveler will be filled with numbers in the local format of the country where he resides.

It can contain a unique number stored in an international format, which was updated during a vacation abroad, in case he needed to call home.

From this it can be concluded that when a customer uses SMT and the number of 'partner B' is identified as a local number, the most likely country of origin is the user's country of residence.

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

It is therefore essential that the user's 'Country of Residence' is captured in some way and associated with his MSISDN.

SMT application

The SMT app runs in the background on the handset, waiting to be activated with a single 'special' click of a button. In order to keep the user experience identical with any device or platform, the same button must be available on any device and on any mobile platform.

This clearly limits the choice of keys available for the following:

Numeric (0-9)

Special keys (* #)

92/129

Call keys (start &amp; end)

This limit is something that SpinVox can effectively exploit; with a specific SpeedDial key # 2 becoming the 'SpinVox key', for example, in a very similar way as the SpeedDial key # 1, which is the Voicemail key.

An application working in this way requires much less integration in the functionality of the handsets, and for the customer it means not thinking, not looking, not feeling.

For prototyping purposes the 'right hand soff key often used by operators to access WAP Portals, must be reprogrammed to provide one-button access to the SMT application.

User Interface

The use of a single key to access SMT functionality has the effect of simplifying the user's experience and greatly reducing integration into numerous menu options, in all possible places from where someone might want to send a message.

A user can still interact with his handset to initiate an SMT message in the following scenarios, however, the single button mode means that he will be taken into the SMT application.

Call logs

Contacts

Messaging / SMS applications

Through an SMT icon on the screen

Navigation

It should be possible to start an SMT message with the press of 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 must be able to use the application through recognizable controls on the handset.

Entering Information

It should not be necessary for the user to physically enter a recipient's number as part of the IVR process; he must be

93/129 automatically sent from the handset to the IVR platform.

Information Presentation • The text used in menus must be familiar to the user.

• Attention should be paid to the icon used for the SMT application (if one is required).

• Attention should be paid to color or sound requirements that may affect the handset.

• Attention should be paid to possible error conditions and how they will be displayed or announced, for example, audio not captured, conversation not possible, text message not sent.

Caller Access - Contacts

1. The caller selects a contact from the contact menu.

2. The 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. A warning requesting the user to speak their text message will then be played.

5. The caller leaves an audio message.

6. Partner B number must be passed to SpinVox (Selected in Step 1)

7. The SpinVox platform converts the audio into a text message for delivery.

Caller Access - Call Log

1. The caller selects a contact from the Call Log

Calls.

2. The 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. A notice requesting the user to speak his

94/129 text message will then be played.

5. The caller leaves an audio message.

6. Partner B number must be passed to SpinVox (Selected in Step 1)

7. The SpinVox platform converts the audio into a text message for delivery.

Caller Access - Soft Key

1. The caller selects an SMT soft key and is directed to Contacts in which a contact is selected.

2. The 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. A warning requesting the user to speak their text message will then be played.

5. The caller leaves an audio message.

6. Partner B number must be passed to SpinVox (Selected in Step 1)

7. The SpinVox platform converts the audio into a text message for delivery.

Caller Access - Message Exchange Application

1. The caller selects a Messaging / SMS application, selects the SMT option from the menu and is directed to Contacts.

2. When the Contact has been selected a connection to a voicemail platform needs to be established.

3. A warning requesting the user to speak their text message will then be played.

4. The caller leaves an audio message.

5. Partner B number must be passed to SpinVox (Selected in Step 2)

6. The SpinVox platform converts the audio into a text message for delivery.

Handset user experience

The screenshot in Figure 24 demonstrates the experience

95/129 user ideal: the list of Quick Addresses of recent contacts (people who called, were called, received texts, received emails, etc.) is selected, and the individual (David Wood) is selected to automatically start a connection to SpinVox's voice conversion system so that the user can speak the message. This process is easily replicable on all selected devices, to provide a consistent user experience.

End-to-end user experience

The diagram in Figure 25 below shows the end-to-end experience from the perspective of A &amp; B partners.

1. Suzy holds down the SMM soft key on her handset and is presented to the last 5 contacts 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 call is not present in the list.

2. She selects the contact she wants to send a message to, and a message on the screen of her device informs her that the SmT service is being contacted and that she hears an audio alert.

3. The SpinVox Service is contacted and information about partner A is sent to the SMM service.

4. Information about partner B is converted for transfer to the SpinVox Service.

5. Once the connection has been established with the SMM service, the DTMF information from partner B is sent.

6. The voice to text conversion starts and partner B receives the text message.

7. Partner B replies the original message.

8. Partner A can choose to speak another answer or use the keyboard-based method to answer.

Handset / Target Platform Support

The following platforms will be supported in subsequent versions.

• Windows Mobile 5 • Windows Mobile 6

96/129 • RIM OS 4.1 and higher (Reference: BlackBerry device models (model 2) and OS versions) • Symbian Series 60 (2^The Edition) • Symbian Series 60 (3^The Edition) • Java MIDP 2.0 compatible devices Provisioning Application

The option to provide handsets with applications installed before launch / shipment is possible, as it is a simple mechanism to download the application for users with existing handsets. Options include:

• Bluetooth • WAP link • Memory card

Attention should also be given to removing the application from the handset.

The screenshots in Figures 26 to 31 demonstrate only a small part of the Speak-a-Message application. They show the functionality of a user choosing to speak a text message to an individual. They do not, however, show sending to more than one person, or sending messages directly to a web application, such as a blog.

All screenshots below were taken from a Nokia N95 mobile phone (model 1), however, the service is not restricted to any particular device.

Figure 26 shows typical application behavior on the standard phone screen. The application automatically takes control of a soft button on the Standard screen (Speak a Text at the bottom right of the screen), allowing access to the Talk-a-Message functionality with just one button.

The application can also be programmed to present itself using other shortcut keys, if they are available on the device. For example, in Figure 27, the application is accessed using a shortcut displayed as the SpinVox logo, after pressing the 'Multimedia Key' on a Nokia N95 (model 1).

97/129

Figure 28 shows the list of Quick Addresses, which on a N95 device (model 1) is limited to the last 5 people you spoke to, sent an email, sent or received a text message or spoke a message with. They are presented in chronological and alphabetical order.

Speaking of a message is not limited to this group of five people, any contact can receive a spoken message by moving it from the 'Recent' screen to the 'Contacts' screen as seen in Figure 29.

When a contact is selected on the 'Contacts' screen that contains more than one phone number, then both numbers are shown and the user is given the option to choose either one, as shown in Figure 30.

Once the number has been selected, the SpinVox service is contacted and the customer is prompted to leave a message. The destination information is automatically sent to the SpinVox 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, and displays the name of the contact to whom the text is being sent.

APPENDIX I

SPEAK A TEXT (BASED ON IVR)

Key features:

• Exchanging messages that you can use when you can't or don't want to stop what you're doing.

• No special applications are needed on the handset.

• It is not necessary to remember someone's number.

• It is intuitive to use, 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

98/129 specific product requirements Speak-a-Text. The solution consists of:

• A dedicated phone number, voice codes or network access codes.

• A Voice recognition system, connected to the IVR platform.

The solution provides the ability to:

Speak a Message &amp; have it delivered as Text (SMS or E-mail).

Listen to previously saved Voicemails.

User Experience is shown schematically in Figure 32.

Product Requirements

1. Service level

To use the product Speak a text (IVR) the client must I5 have an account with SpinVox.

Requirements

The end user will already have a Voicemail account.

The service will have the same availability as SpinVox Voicemail.

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

TAT - must be the same as defined for SpinVox Voicemail or SpinVox Explosion.

Language support. At the initial launch the service must support the following languages:

English UK English US English Canadian

99/129

Canadian French

German

French

Spanish

Australian English

South African English

At the initial launch the service will be limited to retail customers only.

2. IVR

An access number, voice code or network access code will connect the caller directly to the SpinVox IVR.

The IVR tree will be modified to include an option to speak a message to someone. It will also have options for a previously received voicemail to be 'read' to the customer, using a text-to-speech system.

The caller can then access his list of contacts already registered. This list will be limited to 10 people.

Requirements

The voice intonation used to record any new voice alerts must be the same as that currently used on the SpinVox IVR platform.

The languages ​​with which the IVR is recorded must mirror the languages ​​available for current products.

Access to the service will be determined by the CLI recognition of the incoming caller.

If the customer's CLI is retained, he will hear the following voice alert:

Excuse me, your phone number has been withheld, please call again

100/129 without retaining it.

The call will then end.

The IVR system must be able to receive Voice-based commands, as well as DTMF commands.

The IVR system must be able to concatenate commands and names to create a simple voice-based interface.

For example [E-mail] [Dan Doulton]

Where [E-mail] is the desired delivery method and [Dan Doulton] is the recipient.

The following Voice Commands must be recognized to create and send messages:

Email

mail

Text

SMS

The following Voice Commands must be recognized to hear messages already saved:

Run

Listen

The following Voice Commands must be recognized to manage messages already saved:

Run

101/129

Listen

Delete

To save

3. Revenues

The Speak a text service is charged per event. This means that every time a message is sent the customer will have his account 5 decreased and a billing event will be triggered resulting in an SMS Premium that will be sent to him or, in the case of billing with a Credit Card.

Credit, a credit will be deducted from the package.

Requirements

It should be possible to charge customers per conversion event using any payment method the account uses.

It must be possible to exclude customers that are defined as UFTAs from being charged.

It must be possible to exclude customers who were placed in the No conversion status due to non-payment.

4. Supply

To use the service speak a text (IVR) it is necessary to sign and register the details of the people with whom you intend to have contact.

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

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

102/129

Requirements

The delivery system should work with all popular browsers, such as Internet Explorer, Firefox, Safari and Netscape (PC &amp; Mac versions).

It should be possible to add contact details for up to ten people.

The following information is required when adding a contact:

First Name Last Name

Mobile Phone Number E-mail Address

It must be possible to choose and provide a payment plan from the web interface.

Payment plan options must include credit cards and Premium SMS.

5. Voice recognition

Once connected to the IVR SpinVox, it should be possible to 5 navigate the menu system in a 'hands-free' mode, in which it is not necessary to press a key to select the recipient or type of message to be sent.

Requirements

The speech recognition system must integrate seamlessly with the SpinVox IVR platform.

It should be possible to concatenate names and commands, such as: E-mail

103/129

David Ponsford and having this command understood by the Voice Recognition system, without having to include unnatural pauses.

The voice recognition system must be able to recognize names (First name and Last name) when spoken using the IVR platform.

6. Report

Application

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

APPENDIX II

VOICE MAIL CONTACT PLUG-IN FOR EMAIL

Mobile Plug-in: Voicemail Resolution for Email Contact

Voicemail converted to email

Spin-Vox's Create-my-Vmail service replaces the customer's voicemail service, using call forwarding to a new voicemail system hosted by SpinVox. SpinVox converts incoming spoken voicemail messages into text, and then sends this text to the recipient either as an SMS text message or as an email message.

In addition to this method, SpinVox created a new software that, when loaded on a mobile device such as a RIM BlackBerry (model 2), recognizes the incoming e-mail message from the SpinVox system and performs a number of actions on it before the email to be replaced in the inbox of the client device.

The sender's phone number is included in the email 20 that is sent, and the SpinVox software on the device reads this number and then looks in the Address Book of the recipient's device for a match with this number. He not only looks for an exact match, but

104/129 also looks for a match against the number stored in a local format.

For example, the number +442079232854 sent by the SpinVox system will be equated with a real name on the recipient's device and with your contact details found in the recipient's address book (contact) with the following numbers:

+442079232854 - An exact match +44 (0) 20 79232854 - The same number in another International format

020 7923 2854 - The 'local' portion of the number

Number matching is independent of the type of phone numbers the sender is using. Matching numbers can include mobile numbers (07x), landline geographic numbers (01x, 02x) and non-landline geographic numbers (05x), often used in Voice over IP (VolP) services, such as Skype. In fact, any type of telephone number allowed and sent to the service can be equated.

If a match is found in the recipient's Address Book, the following actions take place.

1. The e-mail will be marked with a special icon, or the standard icon will be modified to signal the recipient that this is a different type of e-mail - a voicemail converted to e-mail. This process is very important when sorting and managing a crowded email inbox and is also able to find key messages by type as well as content.

2. The name of the contact in the address book is noted and displayed in the From: field of the email. In this way, the user knows whose e-mail address is and the name is displayed in the format with which he is familiar and which has been recorded in his address book.

For example, a call from +447812101742 will be resolved to Daniel Doulton with the associated email address being DANIEL.DOULTON@SPINVOX.COM

3. The From: field in the email now also contains the caller's current email address allowing the recipient to also respond by email, not just via a phone call or SMS

105/129 (if the sender's mobile number is also stored in the Address Book).

In the body of the email the phrase 'You just received a new voicemail from' is appended to the contact's name, allowing the recipient to respond via a phone call or SMS (if the sender's mobile number is also stored Address Book).

4. Whether the phone number is resolved or not against a contact in the Address Book, the subject line is replaced with the first 30 characters of the converted message, prefixed with SpinVox.

For example, SpinVox: Hello Dave. We will be at 7.30 in ...

5. A QuickLink (see GB2420942B, whose content is incorporated here as a reference) is inserted at the end of the body of the email, which will allow with a simple one-click method that the recipient will only hear this voicemail message. The link calls SpinVox's voicemail service, finds only this specific message and reproduces it immediately.

For example, Click here to listen is shown. The user selects this option within the message and is forwarded to SpinVox's voicemail service, and precisely this message is reproduced without the user having to take any other action.

Embedded menu items

Additional functionality is brought to the device, with the addition of new menu items in the standard menu tree.

'Listen'; offers the ability to listen to the original voicemail message by simply clicking on the menu item when reading a converted voicemail message.

'Call Support'; connects the user instantly with the SpinVox User Support team, allowing them to chat about their account status.

These menu items are dynamically embedded. They become available when a customer is viewing a converted voicemail. This process ensures that they are available only when it makes sense for a customer to use them, not when they could cause confusion.

106/129

Asymmetric message exchange

This plug-in creates a new and unique set of options for the user and recipient to keep in touch using a range of connected messaging options:

Incoming call ends in an email

What makes this service unique is the fact that the original message started out as a spoken message. When it is finally delivered to the end customer’s device, it not only appears in the Inbox of the device’s messaging app, but has also been transposed in an email. It contains a valid From: field, which, depending on the contents of the recipient's Address Book, will provide a reply path via email.

Incoming call answered by email

With the creation of this service, SpinVox allows the recipient of the original voice message to choose to reply by email, instead of the traditional method of calling the message sender using the telephone. This method is unique in that, once the recipient responds to the original message via an email, the point-to-point communication method changes from the voice system to an email system and, once the reply is sent to the sender both can then reply by email.

Summary of Key Features • Conversion of an incoming phone call to an email.

• Resolution of the sender's phone number against a contact number and an email address stored on the recipient's mobile device.

• E-mail Reply Path available for the message originally spoken.

• Listening to specific voicemail messages using the push of a single button.

• New functionality embedded in the standard menu tree.

107/129 • Communication changed from voice to e-mail.

Business Voicemail Requirements for Email Introduction

This section presents the business requirements that 5 allow users to use central email devices such as RIMs' BlackBerry (model 2) with a simple variation of the standard Voice-to-Text service. The BlackBerry (model 2) is used primarily as a commercial business tool for PIM synchronization, reading and replying to emails. This will be reflected in the business requirements detailed in this document.

An Enterprise customer can implement the BlackBerry solution (model 2) using any of the following deployment models:

BlackBerry Solution (model 2) Enterprise - in the 15 implementation of a BES premise (BlackBerry Server (model 2)

Business)

BlackBerry Internet Solution (model 2) - the offer of internet-based services can be used with web-based email providers such as Gmail and Yahoo! and to provide access to corporate e20 mail.

BlackBerry Hosted Solution (model 2) - where a host service provider implemented the BlackBerry platform (model 2) in a data center environment. A company will be able to purchase this solution on a per user and per month basis.

This product improvement will allow SpinVox to target both BlackBerry users (model 2) and mobile phones within the company, promoting greater user activation as a result of more text or email messages being generated, as opposed to voice. In further improvements, SpinVox positions itself as a device independent service provider.

This service will also allow SpinVox to 'turn off' text delivery, by default for BlackBerry users (model 2), in such a way that conflicting messages are not received on the device, bringing significant savings to the company.

108/129

The service will allow a Company to have all voicemail conversions delivered only as email (default setting) to its BlackBerry (model 2) or other central email devices. Users will be given the option to enable SMS delivery if required.

Converted Messages

A converted voice message will be sent as an email with no WAVE file attached. The option to use the Quick-Link message to find and listen to your voicemail will also be available.

Unconverted messages

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

The service will be available for both GSM and CDMA networks and for Companies located in the US, Europe and Australia.

For the delivery of e-mails, the CLI of the sender must be resolved against the Local Address Book (LAB), in such a way that the From: field is filled with the real name of the Sender as stored in the address book of the device .

It is also necessary that in the body of the email the first line contains the information 'You received a new voicemail from John Smith'; where John Smith is the contact's real name.

109/129

The user will be able to click on the caller's name to send a reply via email, send a text or initiate a call.

If it is not possible to resolve the number against the content of the LAB, the CLI of the incoming number must be shown.

The subject line of the email will contain the first 32 characters of the converted message prefixed with 'SpinVox¹.

The service will be tested with the following implementation models with:

BlackBerry Business Solution (model 2) (BES Ver 4.0) BlackBerry Internet Solution (model 2)

BlackBerry Hosted Solution (model 2)

The service will be tested at least with the following devices:

Pearl 8100

BlackBerry 8700 (model 2)

BlackBerry 7130 (model 2)

BlackBerry 8707 (model 2)

The application must be compatible with RIM OS version 4.1 and higher.

Modifications will be required in the following commercial support systems:

SpinVox Website - The user must be given the option to identify himself as the user of a device

110/129 e-mail center, such as a BlackBerry (model 2), and must then be confronted with a profile of specific services, that is, delivery of E-mails only as standard, Converted messages sent without an audio attachment, Unconverted messages sent with audio attached.

A link to a downloadable application will be available on the SpinVox website.

Customer Service Interface - Modified to include a BlackBerry services profile (model 2).

Enterprise Self-Service Web Tool - Will be modified to capture BlackBerry devices (model 2) with provisioning against a BlackBerry services profile (model 2).

Screenshots

The following screenshots show how the service works, when a voicemail is left for a customer, the message is converted into text and the email sent to the customer.

All screenshots below were taken from a BlackBerry device (model 2), however the service is not restricted to any particular device of this type.

Figure 33 shows the typical behavior of a central email device before installing the SpinVox software plug-in. The From and Subject fields do not provide any indication of who the message originated from and what its subject is. 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 what the Inbox looks like after the SpinVox plug-in has been installed. The standard email icon has been replaced by a special icon, which signals that the message is a

111/129 SpinVox voicemail message. The From: field has been replaced with the actual name of the sender, as stored in the recipient's Address Book on the device, and the subject line has been modified to include the first part of the converted voicemail message, prefixed with SpinVox :, which allows the message to be classified and grouped with other SpinVox email messages.

Figure 35 shows how a SpinVox voicemail message will look after 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 soon as a match is found the sender's real name is displayed in the From field. In the example below the real name is Vadiraj Patel.

The subject line has been modified to display the first part of the converted message prefixed with SpinVox:

Figure 36 shows what happens when a user clicks on the real name that has now been placed in the From: field. He can now reply directly to the sender of the message via e-mail by clicking on E-mail Vadiraj in the menu. It is important to remember that the original message was a spoken message that was answered with an email, changing the method of communication from voice to screen.

Figure 37 shows what happens when a user clicks on the real name that has now been placed in the message text in the section that starts with 'You received a new voicemail from'. It is now possible to reply directly via SMS, MS or voice to the message sender, by clicking on the appropriate menu item. It is important to remember that the original message was a spoken message that is being answered via SMS or MMS, changing the communication method from voice to screen.

Figure 38 shows an example of a QuickLink, which was inserted at the base of the converted email message. QuickLink provides a simple and easy one-click method to listen to the original voicemail message that the customer is currently reading. It dials SpinVox's voicemail service and automatically plays the correct message.

Figure 39 shows how additional features were added to the device with the addition of new items to the menu. These

112/129 new menu items were shipped in specific places, to ensure that its functionality is shown to the user only when it is useful to him. If they were introduced all the time, they would lead to great confusion.

Appendix III

VIRAL / L / NK CAMPAIGNS

This section describes viral or link marketing methods used to spread and market SpinVox products.

• Refer a friend (RAFit) to SpinKey:

Call your own mobile phone from your mobile phone • We now know that you are trying to make a special call • Please enter your friend's mobile phone number o Enter it, or if you are an experienced user, find it in contacts and press Call / Send DTMF to us o Thank you. Activation codes have been sent to you and your friend o This means that you have your activation code on the screen and can help you through this complicated process or ...

Call your voicemail box - new IVR option

113/129

Call 84004 (we are enabling the voice)

Enter your friend's mobile phone to 84004 • Call your own voice mailbox / 84004 and leave a message: Subscribe 07812101742 • CrieDemo:

o Call your own mobile phone from your mobile phone

SV IVR but this time enter * and then the friend's number, and now you speak a text to him

APPENDIX IV Unified Communications

This market, and its Communications derivative

Unified, it tried to unify all communications so that a user can manage them in a single inbox, typically in e-mail format and accessible from their PC.

The point is that:

&gt; It is accessible only from one point - from your email inbox or from a web page, meaning that you need to be in a specific place such as your desk, to access your communications. This does not help the growing mobile workforce, estimated to be away from a desk at more than 50% of a working day.

&gt; Any audio (voice messages) that can now appear as an attachment to an email or other format, requires you to listen to it, write key remarks and actually get the job done. In short, it is not transformed into a medium that is synonymous with the task - keyboard, screen,

114/129 IP-based messages as entered. So the user must be in front of his PC, he must listen to the messages and he will have the job of transforming the audio into, say, an e-mail reply or notes to a colleague.

&gt; The implementation of UC services requires dedicated hardware and software and typically consists of an expensive IT update to be delivered and which then requires maintenance.

SpinVox solves these issues in a very elegant way, converting all voice messages to text and distributing them immediately to all devices:

&gt; SpinVox uses existing network services and call management features to unify your voice messages, usually voicemail messages, or direct calls to a single voicemail box, or collect voicemails from different mailboxes of voice. These voicemail messages are then sent to SpinVox's VMCS for conversion into text. There is no need for any new IT hardware or software, or complex management systems.

&gt; For users there is no need to work through complex call management decisions or message exchange settings, typically based on the time of day and day of the week, to ensure that the caller forwards a message to you. By converting any voice message to text, users can instantly receive and view all of their messages regardless of where they are and where the messages were from

115/129 originating - for example, from a desk phone, cell phone, switching table, home phone, etc ...

&gt; Once the messages are in text format, they are presented in a format that is now synonymous with the medium in which they will be managed - that is, SMS, MMS, email, IP, Web formats. SpinVox can provide the outgoing text to your email inbox, to a web page / service or as text of any format for mobile phones. Now the user can choose whether to call or return a text / mail, or manage this information for colleagues or friends in the most appropriate format. And because it is in text format, it is immediately indexable and searchable, which increases the power of computers to improve information management and retrieval.

&gt; With the execution of this transformation (conversion), SpinVox removes all the existing limitations of the UC services and allows the message not only to be delivered to a single point (your inbox / PC), but also as text to any device in anywhere, thereby solving the 'country-blocked' problem of most UC projects. This means that users can now perform the key tasks that UC promises, but wherever they are and at any time.

The reason why the unification of voice messages from different sources (mailboxes) makes sense and creates real value, is because it facilitates access and management for users. E-mail is already widely unified and in a good format for indexing, storing and

116/129 management, and increasingly accessible from mobile devices (BlackBerry) (model 2).

Figure 40 shows how SpinVox unifies different types of channel communications.

The power of using SpinVox services lies in the fact that you can simply connect users (that is, the UI level) to systems that are traditionally 'disconnected systems' (for example, voice, blogs, SMS, email, etc.). ..), both due to the standard management resources (divert / forward) and the conversion of messages into text, thereby overcoming the technical barriers that would otherwise exist between different communication systems.

Appendix V Voice SMS

SpinVox Voice SMS allows people to speak a voice message and have the recipient notified by SMS, then requesting the recipient to call a number and listen to the message.

The service overcomes language and readability issues around messaging, opening new revenue streams for wireless operators, without any additional investment in both infrastructure and handset resources. The service is more cost-effective and more discreet than traditional voicemail, and more expressive than traditional SMS.

SpinVox Voice SMS provides the following benefits to the end user:

• New and highly personal method of communicating.

• It costs (typically) less than a voice conversation.

• Easy to use o Overcomes text usability issues, o Available in all languages, o No reading required, o Simpler than typing an SMS.

• Operates with current handsets.

• Requires no end user training.

117/129

As there is no barrier to entry, and making a phone call is a natural behavior for a wireless phone user, this product represents a mass appeal to the entire user base of an Operator.

Product Overview

<td>Product's name</td><td>SpinVox Voice SMS</td>

<td>description</td><td>Allows a spoken voice message be deposited from any handset mobile phone and a notification is sent to a recipient via SMS. The recipient can then dial a QuickLink code to hear the caller's message.</td>

<td>Source Network</td><td>GSM and CDMA</td>

<td>Finishing Network</td><td>GSM and CDMA</td>

Voice SMS works in a very similar way to SMS. Instead of sending texts, callers can easily send voice messages, using expressions to carry more information than just text. For the called partner, the service is easy to use and adds an emotional dimension to the exchange of messages.

A caller simply prefixes a standard mobile phone number with a code, for example *, the service records the voice message and sends an SMS notification to the called partner, who can then respond to the voice message simply by clicking on the QuickLink code, for example * 3.

SpinVox Voice SMS creates an incremental and sustainable stream of revenue for Wireless Operators without cannibalizing existing services. The availability of Voice SMS creates new situations, in which people can use the exchange of messages in a way that they did not think they could use it previously. Subscribers are using Voice SMS to send more emotional messages, in a way that text-based messaging is not able to achieve.

118/129

The user experience will be natural and direct - the calling partner makes a normal voice call, prefixing the mobile number with a short code to start a session with the SpinVox Voice SMS platform. The calling partner will receive an IVR, which will prompt them to speak their message and then simply select the option to send from the IVR.

A typical voice message is expected to be an intentional short message. The maximum recording time will be limited to 30 seconds.

The product must meet the following criteria: ío 1. No change in behavior

In many developing countries the level of reading ability may be low, as well as, there is an inability of the SMS interface to manipulate local languages ​​- in these cases sending voice instead of text is a more relevant service proposal. Sending and retrieving a Voice SMS should be as simple as making or receiving a normal voice call.

2. Easy &amp; economical to implement

The appeal to Operators is that the implementation of the service does not require any infrastructure updates on their networks. The service must be able to be implemented within 8 weeks.

3. Universal service offer

Any customer must be able to use the service on any handset, without any need for pre-delivery or handset configuration. This will help penetrate markets aimed at masses of the Operator's user base.

End-to-end user experience

Figure 41 shows the end-to-end experience of SpinVox's Voice SMS service:

1. Interaction of the Calling Partner with the IVR 30 It is considered that there will be minimal interaction between the deposition of a message and the Voice SMS platform. The calling partner will be presented with options to send, re-record or cancel their Voice SMS message.

119/129

Language to be used

Voice SMS is an autonomous integration; it does not require integration with the Operator's voicemail platform.

The Voice SMS platform will support multi-language alerts in the following languages:

<td>O</td><td>Arabic</td>

<td>O</td><td>French</td>

<td>O</td><td>English</td>

<td>O</td><td>Persian</td>

<td>O</td><td>Hebrew</td>

<td>O</td><td>Standard Chinese</td>

<td>O</td><td>Bahasa Indonesia</td>

<td>O</td><td>Japanese</td>

<td>O</td><td>Korean</td>

<td>O</td><td>Filipino</td>

<td>O</td><td>Sinhala</td>

<td>O</td><td>Thai</td>

<td>O</td><td>Vietnamese</td>

<td>O</td><td>Spanish</td>

<td>O</td><td>Portuguese</td>

Initial voice alert

120/129

The calling partner will hear the following introduction after the Voice SMS service has dialed and connected to the IVR:

Please record your message after the tone

Press 1 to send this Voice SMS Press 2 to re-record this Voice SMS Press 3 to cancel this Voice SMS

<td>Very long message alert</td>

<td>If a caller exceeds the time allowed to deposit an message, he will be prompted to rewrite the message or leave it how are you doing.</td>

<td>End of message alert</td>

<td>When the caller approaches the end of the recording time, a series of beeps will be played, which will accelerate as you go approaches the end of the message before Req 1.4 alerts the user.</td>

<td>Forecast</td>

<td>The Operator will provide a volume forecast for the service SpinVox Voice SMS.</td>

<td>Support</td>

<td>Technical support for the SpinVox Voice SMS service will be guaranteed by the support agreement, as outlined in the Operator.</td>

<td>Storage</td>

<td>The Voice SMS platform will provide the audio storage of the voice message. In standard mode the audio file will be retained for a period of 5 days.</td>

<td>Audio</td>

<td>The audio of the sent voice message will not be accessible to the partner caller.</td>

121/129

1. SMS delivery to recipient

When a voice message has been successfully deposited, an SMS will be sent to the intended recipient. The following requirements meet this SMS only.

SMS to Partner B

The text message must be sent from the telephone number of the original calling partner. If this CLI is retained then 'Retained' will be presented to the called partner.

Message body

The message body will be specified as part of a new Message Classification model for this operator.

Note: it will include a SpinVox message tag with 'Spoken via SpinVox'

Message Recovery - QuickLink

Message recovery will be performed using a short code QuickLink, for example, * 3 * will recover the 3^The message.

2. Recipient interaction with IVR

After the recipient has listened to the voice message, they will be presented with a number of additional options to manage their Voice SMS experience. These are outlined below:

Mailbox Configuration

Each recipient of Voice SMS will be allocated a virtual mailbox. The Operator will specify the capacity of this mailbox, however, it is recommended that it does not contain more than 5 messages for a given period of time, for example 5 days.

IVR - Recovery of old messages

122/129

A recipient should be able to hear old messages stored in his mailbox. LIFO message reproduction will be used.

IVR - Share Voice SMS

A recipient must have the option of forwarding his Voice SMS to another user. This option will be available from the IVR, for example:

Press 4 to share this Voice SMS

Enter the recipient's number followed by the closed key.

IVR - Deleting voice messages

A recipient must have the option to delete a voice message.

IVR - Skip to the next message

A recipient must have the option to skip to the next voice message.

IVR - Repeat the voice message

A recipient must have the option to return to the beginning of the current voice message.

IVR - Responding to a Voice SMS

A recipient must have the following response options: o Respond to Partner A via Voice SMS o Respond to Partner A via voice call

IVR - Saving a Voice SMS

A recipient must have the option to save a Voice SMS.

3. Service Levels

Subscription requirements

It should not be necessary for the caller to sign with the Operator to use this service - all they have to do is dial a call prefix followed by the recipient's number.

123/129

Compatibility

The calling partner must be able to dial a call prefix, for example *.

Setting prices

Depending on the Operator's pricing model, a Voice SMS can be a premium to normal SMS level. Therefore, the calling partner can be greeted with an announcement before the call stating the cost of delivering the Voice SMS.

The Operator may also include a number of free messages before being charged.

Service level

The service must meet the same availability requirements as the SpinVox service, that is, 99.99%.

Recording time

The recording time should be limited to a duration of 30 seconds.

The caller will be notified via an appropriate voice alert if he exceeds the recording timeout of 30 seconds.

Number of SMS supported

All SMS deliveries must be limited to 1 SMS.

4. Operator interoperability

SpinVox's Voice SMS service must be interoperable with alternative Voice SMS providers, thereby enabling a Voice SMS 5 to be sent to recipients regardless of the Operator service they are using.

Interoperability between operators

124/129

Third-party operators must be able to interconnect with the SpinVox Voice SMS service, via an API specified by SpinVox or through the appropriate GSM Association standards.

SpinVox-SpinVox interoperability

Interoperability will only be available between those operators that have implemented SpinVox's Voice SMS service.

Interoperability between operators

A single Operator implementing multiple instances of Voice SMS must be able to interoperate between instances.

Commercial

A business architecture will be specified to support inter-operator accounting.

5. Platform Requirements

The service platform must be able to deliver Voice SMS as a managed service offering. Operators should 5 be able to easily introduce new SpinVox services, such as the SpinVox Messenger and Voicemail to their user base without major changes to their infrastructure.

Recording &amp; Playback

The Voice SMS platform must be able to record and reproduce messages deposited by unique callers.

Voice Alerts

The Voice SMS platform must have the ability to reproduce IVR alerts from multiple languages.

DTMF Tone Recognition

The Voice SMS platform must be able to recognize key presses with ringing tones.

Platform Availability

125/129

The Voice SMS platform must support a high availability architecture to ensure a maximum uptime of 99.99%.

Inter-Operator Accounting

The Voice SMS platform must have the ability to record and report inter-operator traffic, supporting the interconnectivity of Voice SMS between operators.

SMS formats

The Voice SMS platform must have the ability to build and format an SMS and to interconnect with an SMSC structure of an Operator.

6. Demonstration

The Voice SMS product must be able to be demonstrated to the Operator by SpinVox. The Operator must also be able to schedule a product demonstration for its customers to market the service.

SpinVox Website - Demo

It must be possible to demonstrate the Voice SMS service through the SpinVox website.

Operator - Demo

SpinVox requires a way to demonstrate the Voice SMS service to an Operator as part of its sales process.

Operator - Billing Demo

It must be possible for the Operator Demonstration to be free of charge to the caller.

Operator - User Experience

The SpinVox Demo must provide the same user experience as the Operator's product.

7. Reporting

It will be necessary to report service activities. THE

126/129 audience for all SpinVox Voice SMS reports will be both internal and external to SpinVox, targeted at Operators. Where SpinVox is offering interconnection capabilities to specific Operators, detailed Inter-Operators reports must be provided.

Reporting Requirements

It should be possible to report on all messages from this service.

Reporting Requirements

It should be possible to report on the following product measures.

• Users by Operator • Traffic by Operator • Average audio duration

Reporting Requirements

It must be possible to report on the following measures, in which the user is defined as the number calling the service (ie, the CLI).

• Frequency • Traffic • Average audio duration

8. Revenues

Billing Requirements

SpinVox must have the billing capability to support billing models based on pay per message / package.

Billing Requirements

It must be possible to issue a billing invoice to the Operator on a monthly basis for the service.

9. Future phases

127/129

Future improvements

In a future phase, it should be possible to extend the service to fixed lines. The following call scenarios will be supported:

o Fixed line for mobile o Fixed line for fixed line o Mobile for fixed line

Note: A landline recipient will receive a ring tone, and after picking up the receiver, they will hear the voice message.

Future improvements

In a future phase, it should be possible for the called partner to receive a Voice SMS delivered via email.

Future improvements

In a future phase, it should be possible for the caller to send a Voice SMS to multiple recipients (Options include using a web portal to set up address / list management books or using a Voice SMS handset application) .

Future improvements

In a future phase, it should be possible for the caller to send a reserved Voice SMS, that is, on a specific date and time.

APPENDIX VI Acronyms

The list below represents a guide to the normal meaning of the following acronyms.

ACR - anonymous call rejection Al - artificial intelligence ASR - automated voice recognition CLI - caller line identification

128/129

CPU - central db processing unit - database

IDD - incoming direct dialing

DTMF - multifrequency double tone

G728 - standard specified in the ITU-T recommendation

G.728, 16 kbit / s voice coding using linear prognosis activated by low delay code.

HTTP - hypertext transfer protocol IM - instant messaging IP - internet protocol

ISO - international standards organization

IVR - interactive voice response

MM - exchange of multimedia messages

MMS - multimedia messaging service

MoBlo - mobile blogging

MSF - mail summary file

MSISDN - integrated services mobile network digital station

N / O - OTA network operator - over-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

SDK - set of software development tools

SIP - simple internet protocol SLA - SMPP software license agreement - end-to-end short message

129/129 communication) voice

<img file="BRPI0806206A2_D0002.tif" />

SMS - short message service

SMTP - simple mail transfer protocol

SOAP - Simple Object Access Protocol

SSL - secure socket layer (a security protocol

SV - SpinVox

TAT - execution and response time

TLP - transaction layer package

UI - user interface

UID - unique identifier

URL - uniform resource locator

VAS - value added service

VF - Vodafone

VG - video game

VM2T - voice to text mail

VMCS - message exchange conversion system

VMP - variational message passing

VolP - voice over internet protocol

WAP - wireless application protocol

1/5