FR3036570A1 - TECHNIQUE FOR INTERACTING A USER DEVICE WITH A DEVICE CALLED - Google Patents

Abstract

The invention relates to a technique for interaction of a user device (10, 11) with a called device (20). When a request for establishing a voice communication between the user device and the called device is issued, the user device detects that the called device implements automated voice interaction steps. An interaction menu is then received by means of a multimedia session established between the user device and the called device and is displayed in form on a screen of the user device. A selection data relating to the received interaction menu is then entered by a user of the user device and is sent by the user device in text form by means of the multimedia session.

Description

The invention relates to the general field of telecommunications. The invention relates more particularly to a technique of interaction of a user device with a called device, especially when the called device is an interactive voice server. Such a voice interaction device implements automated voice interaction steps. It often happens that an online hotline service ("hotline" in English) implements interaction steps with a calling device in the form of interaction menu and choice in this menu successively according to a logic of 'interaction. During these interaction steps, several choices are proposed vocally and the user of the calling device selects one of these choices vocally or by pressing a key on his keyboard. As an illustrative example, a menu offers the following choices: "Press key 1 to modify your personal data, press key 2 to be put in contact with an operator, press key 3 for any other request, press the * key to return to the previous menu ". When the selection is made by pressing a key claver, the user of the calling device must listen to the choices that are available and enter his choice on the keyboard of his terminal. This is particularly tedious, especially when the user of the calling device does not wish to switch the voice communication on loudspeaker. When the selection is made by voice recognition, a choice of the user of the calling device may be poorly recognized. This results in a navigation in the various interaction menus particularly tedious. Thus, many users do not like to interact with a machine, because of these constraints and reliability issues. In addition, hearing-impaired users find it difficult to interact with such a voice server. One of the aims of the invention is to remedy the shortcomings / disadvantages of the state of the art and / or to make improvements thereto.

According to a first aspect, the subject of the invention is a method of interaction of a user device with a called device. This method comprises, when a request for establishing a voice communication between the user device and the called device is issued: - a detection by the user device that the called device implements automated voice interaction steps; a display on a screen of the user device in text form of an interaction menu received by means of a multimedia session established between the user device and the called device; - A sending by the user device in text form by means of the multimedia session of a selection data item relating to the interaction menu received. Correlatively, at the level of the called device, the method of interaction of a device user with a called device includes, when a request for establishing a voice communication between the user device and the called device is received: - a provision by the called device to the user device of an indication that the called device sets implementing automated voice interaction steps; a sending to the user device of an interaction menu by means of a multimedia session established between the user device and the called device for a textual display on a screen of the user device; a reception by the called device of a selection data item relating to the sent interaction menu, received in text form by means of the multimedia session. A device implementing automated steps corresponds, for example, to an interactive voice server, offering selection choices via interaction menus 15 in voice form according to an interaction logic. A multimedia session is a communication session, capable of transmitting different types of information: texts, files, instant messages, contents, etc. Thus, the interaction of a user of the calling device with the called device is done in a simple and user-friendly way. Hearing impaired users can, through the interaction process, have access to the voice service. The time required for the interactions of the user device with the called voice interaction device or voice server is also shortened and more reliable, especially with respect to interaction logic based on voice recognition to obtain the selection data. Commonly, an interactive voice server implements a speech synthesis, ie a text to speech conversion, in order to render the interaction menus in voice form. As a result, the transmission of interaction menus directly in text form to the calling device does not result in an increase in the processing means required at the voice server level. Furthermore, the selection data being obtained directly in textual form, this reduces the processing time especially for interactive voice servers 30 implementing a voice recognition algorithm to identify the selection data. The selection data can be converted upon reception as a DTMF (Dual-Tone Multi-Frequency) multi-frequency signal to limit changes to the interaction logic of the voice server. The interaction technique is particularly advantageous for use on next-generation user devices. Such devices, for example "smartphones", have in fact a screen whose size is suitable for displaying menus in textual form. For a touch screen, the input of the selection data can be done directly without requiring interaction with a keyboard. The selection in the menus can also be done using the up / down arrows. The user experience is thus improved thanks to the use of the graphic capabilities of this type of terminal. The display in textual form also allows a faster interaction. It is not necessary to read a proposal in extenso to decide not to select it. In voice interaction, the proposal must be heard as a whole before listening to the next proposition. A faster and more effective interaction is particularly valuable for interactive voice services intended to handle an emergency.

Depending on the selection data, the voice interaction device or voice server selects the following menu for textual display. The new menu is displayed on the screen of the user device, until the user is connected to an operator via a call transfer or terminates interaction with the voice server. In a particular embodiment, the interaction technique is implemented by means of enhanced communication functionalities RCS (for "Rich Communication Services"), available for the Joyn service. The implementation of the interaction method does not require prior knowledge if the device called is a device implementing automated voice interaction steps. Indeed, when the called device is another user device, it is detected that this other user device does not implement automated voice interaction steps and voice communication can be established in a conventional manner. The various modes or features of embodiment mentioned below may be added independently or in combination with each other, to the steps of the interaction method as defined above.

According to a particular characteristic of the interaction method, the detection comprises sending to the called device a communication capability discovery message and receiving a communication capability indicating a PLC mode of operation. Note that, for an implementation of the method using the RCS enhanced communication functionalities, the discovery message corresponds to the SIP-OPTIONS message and the "isAutomata" communication capability received in return allows the called device to communicate. indicate an operating mode of the PLC type (Boolean set to the value "true"). Thus, the interaction method relies on exchanges already specified in the RCS standard and to ensure interoperability between the user device and the voice interaction device or voice server.

Correspondingly, the supply comprises a reception by the called device of a communication capability discovery message and a sending of a communication capability indicating a PLC type operating mode. According to a particular characteristic of the interaction method, the multimedia session is established following the detection that the called device implements automated voice interaction steps. This makes it possible to establish a multimedia session only when it is necessary, that is to say when it is detected that the called device implements automated voice interaction steps.

In another embodiment, the multimedia session is pre-established. According to a particular characteristic of the interaction method, the interaction menu is sent by the called device and is received by the user device in text form by means of the multimedia session. In this embodiment, the menu can be displayed directly.

In another embodiment, the menu is received in voice form and the user device converts the textual menu by voice recognition. According to a second aspect, the invention also relates to a user device comprising: an interaction module, arranged to: detect a device for which a request for setting up a voice communication is sent, said device called implements automated voice interaction steps; receiving an interaction menu by means of a multimedia session established between the user device and the called device; 25 - sending in textual form by means of the multimedia session a selection data relating to the interaction menu received; - A human-machine interface module, arranged to display on a screen of the user device in text form the received interaction menu. According to a third aspect, the invention also relates to a voice interaction device, arranged to interact by means of a voice communication with a user device, said voice interaction device comprising: a communication module, arranged to provide an enriched communication service and for providing an applicant user device with an indication that said voice interaction device implements automated voice interaction steps; An interaction module, arranged to: provide in response to a request from a user device an interaction menu by means of a multimedia session established between the user device and the voice interaction device for a textual display on a screen of the user device; receiving a selection data relating to the sent interaction menu, received in text form by means of the multimedia session. According to a fourth aspect, the invention relates to a program for a user device, comprising program code instructions intended to control the execution of those of the steps of the previously described interaction method implemented by the user device, when this program is executed by this device and a recording medium readable by a device on which a program for a device is recorded. The advantages stated for the interaction method according to the first aspect are directly transferable to the program for a user device and to the recording medium. According to a fifth aspect, the invention relates to a program for a voice interaction device, comprising program code instructions for controlling the execution of those of the steps of the previously described interaction method implemented by the device. , when this program is executed by this entity and a recording medium readable by a device on which a program for a device is recorded. The advantages stated for the interaction method according to the first aspect are directly transferable to the program for such a device and to the recording medium. The interaction technique will be better understood with the aid of the following description of particular embodiments, with reference to the appended drawings, in which: FIG. 1 represents an environment in which the interaction method is implemented in a particular embodiment; FIG. 2 represents a user device according to a particular embodiment; FIG. 3 represents a voice interaction device according to a particular embodiment; FIGS. 4a and 4b illustrate steps of an interaction method implemented by a user device and by a device called according to particular embodiments; FIGS. 5a and 5b illustrate an exemplary implementation of the interaction method on a user device.

FIG. 1 represents an environment in which the method of interaction of a user device with a controller device in a particular embodiment is implemented. The environment comprises two user devices 10, 11 accessing a communication network 1 via a mobile access network, not shown in FIG. 1. The mobile access network corresponds, for example, to a network. mobile communication network of GSM, EDGE, 3G, 3G + or 4G type (also called LTE for "Long Term Evolution") ... An IMS architecture, for "IP Multimedia Subsystem", allows to establish 5 IP multimedia communication (for "Internet Protocol") between the different devices. The RCS service, for Rich Communication Service, uses this IMS architecture to offer an enriched communication service. This service allows two or more devices using a multimedia communication session to exchange instant messages (known as "chat"), share multimedia files, and make voice calls on LTE 10 ( VoLTE), video calls on LTE, ... The communication network 1 can correspond to several communication networks of different communication operators interconnected with each other. The user devices 10, 11 can establish voice communications with each other or with a controller type device 20 via the communication network 1. This type of device 20, or voice interaction device, offers a voice interaction. with a user device in the form of interchange of interaction menus and selection data in an interaction menu according to interaction logic. Such a device implements automated voice interaction steps. Subsequently, this device 20 is called indifferently voice interaction device or interactive voice server. This device 20 transmits 20 in voice form an interaction menu and receives in return a DTMF code, representing a selection data relative to the current interaction menu. In another embodiment, the selection data is transmitted in voice form from the user device to the voice interaction device 20 and the latter uses a voice recognition algorithm to identify the selection in the interaction menu. It is emphasized here that in these two cases the selection data is transmitted in the form of an audible signal. Moreover, it is also emphasized that this environment is represented in a simplified way so as not to overload the figure. In particular, no limitation is attached to the number of user devices or the number of devices of the PLC type. The user devices 10 and 11 can be any type of terminal for establishing a telephone or videophone communication, such as a mobile phone, a smartphone, a tablet, a television connected to a network. of communication, a personal computer on which a telephony application, also called "softphone", is installed. In the example described here, the user device 10 is a "smartphone" type terminal with a touch screen. The user device 10 is connected to the communication network 1 and can transmit and receive any type of communication via the communication network 1.

In the example described here, the user device 11 is a terminal with a screen and a keyboard. The user device 11 is connected to the communication network 1 and can transmit and receive any type of communication, via the communication network 1. FIG. 2 represents a user device 10 in a particular embodiment.

The user device 10 comprises in particular: a memory zone 101, arranged to store an application that includes code instructions for implementing the steps of the interaction method; - A storage memory, not shown, arranged to store data used in the implementation of the interaction method; A processor 100 for executing software module code instructions; an interface module 102 with a communication network, arranged to transmit and receive data; a communication module 103 for proposing an enriched communication service RCS, referred to as the RCS module; An interaction module 104, arranged to interact with an interaction module of a device of the PLC type; a human-machine interface module 105, arranged to interact with a user, in particular for transmitting and receiving voice communications. The interaction module 104 communicates with the RCS module 103 via a programming interface (often referred to as the API for "Application Programming Interface"). This programming interface is defined in the GSMA specification document, entitled "RCS Device API 1.5 Specification", Version 2.0, 16 October 2014. It is emphasized here that the user device 10 also includes other processing modules, not represented in FIG. 2, arranged to implement the various user device functions. FIG. 3 represents a device of the automaton type in a particular embodiment. This device 20 comprises in particular: a memory area 201, arranged to store an application that includes code instructions for implementing the steps of the interaction method; A storage memory, not shown, arranged to store data used during the implementation of the interaction method; a processor 200 for executing code instructions of software modules; an interface module 202 with a communication network, arranged to transmit and receive data; A communication module 203 for proposing an enriched communication service RCS, referred to as the RCS module; An interaction module 204, arranged to interact with an interaction module of a user device; a voice service application module 205, arranged to interact in voice form with a user via a user device; 5 - a memory zone 206, arranged to store a menu tree and interaction logic with a user. In a particular embodiment, the memory zone 206 stores the menus in text form. In another particular embodiment, the memory zone 206 memorizes the menus 10 in voice form. The interaction module 204 communicates with the RCS module 203 by means of an API programming interface. In a particular embodiment, the voice service application module 205 is a software module programmed using VoiceXML or VXML (for "Voice eXtensible Markup Language") defined by the organization. W3C standardization (for "World Wide Web Consortium"). This language allows you to create dialogs with an interactive voice server, including synthesized speech, voice recognition or DTMF code recognition, voice input recording, telephony, ...

It is emphasized here that the device 20 also comprises other processing modules, not shown in FIG. 3, arranged to implement the different functions of voice interaction device or voice server. The interaction modules 104 for the user device 10 and 204 for the device 20 exchange data through their respective RCS communication modules 103 and 203. The interaction module 104 of the user device 10 is arranged to control the interaction module 204 of the device 20. The interaction module 204 is arranged to provide an interface between the RCS commands and the voice service application module 205, in particular to provide a selection data in sound form and to obtain a menu associated with a current state of the voice dialogue according to the interaction logic.

FIG. 4a illustrates steps of an interaction method implemented by a user device 10 and by the device 20 according to a particular embodiment. The interaction method is initiated by the selection by a user of the device 10 on a human-machine interface menu of a request for establishing a voice communication with a device 20, called called device. This triggers a sending by the HMI module 105 to the interaction module 104 of a request for establishing a voice call M1 between the user device and the called device. This request M1 is received by the interaction module 104 in a step El.

Still in this step E1, the interaction module 104 transmits a command N1 to the RCS module 103, in order to detect whether the called device 20 implements automated voice interaction steps. In a step F1, the user device, more precisely the RCS module 103, sends the device 20 a message 01 for discovering the communication capabilities of the called device 20. In a particular embodiment, the discovery message 01 is for example a SIP OPTIONS message according to the SIP protocol (for "Session Initiation Protocol"). This message is sent without requiring prior communication session opening between the two devices. The communication capabilities are defined in the GSMA specification document, entitled "RCS Device API 1.5 Specification", in a "package" group "com.gsma.services.rcs.capability". In a particular embodiment, the discovery message 01 requires all the communication capabilities of the device 20. In another particular embodiment, the discovery message specifically requests one or more communication capabilities, including a communication capability. indicating that the operating mode is of the PLC type. Specifically, this communication capability is named "rcs.isAutomata" and is a boolean that takes a "true" or "false" value. In a step G1, the device called, more specifically the module RCS 203, receives the communication capability discovery message 01 from the user device 10. In this step G1, the module RCS 203 sends to the module RCS 103 from the user device 10 a response message 02 to the discovery message 01. This response message 02 includes an indication that the called device implements automated voice interaction steps. In a particular embodiment, this message 02 is for example a SIP message 200 OK, comprising a communication capability indicating a PLC type operating mode. In the particular case where the called device is a voice interaction device or voice server 20, implementing automated voice interaction steps. In this case, the communication capacity indicates that the operating mode is of PLC type. In a step F2, the RCS module 103 receives the response message 02 and transmits to the interaction module 104 a notification N2 indicating a detection that the called device implements automated interaction steps. In a step E2, the interaction module 104 detects that the called device implements automated voice interaction steps, due to the request for establishing a voice call and the receipt of the notification N2. The interaction module 104 requests by a message N3 from the RCS module 103 to establish a multimedia session with the called device.

In a step F3, the RCS module 103 transmits to the RCS module 203 of the called device a multimedia session establishment request message 03. In a particular embodiment, the message 03 is a SIP Multimedia Session Init message. This message 03 is received in a step G2 by the RCS module 203. Still in this step G2, the module RCS 203 notifies by a message P1 the interaction module 204 of the request to establish a multimedia session. In a particular embodiment, the message P1 is an interface message "SIP Session ends callback". It is emphasized here that for reasons of readability, only the function is indicated in this interface message. Those skilled in the art are able to easily determine from this function the corresponding SIP message. The same is true afterwards. The message P1 is received in a step H1 by the interaction module 204. Also in this step H1, the interaction module 204 sends an acknowledgment request P2 to the RCS module 203. The latter then sends an acknowledgment 04 of multimedia session setup at the RCS module 103, having requested the establishment of the multimedia session. In a particular embodiment, this acknowledgment message is a 200 OK SIP message. The acknowledgment message 04 is received by the RCS module 103 in a step F4. The RCS module 103 then notifies the interaction module 104 by a message N4 that the multimedia session has been established. This notification message N4 is received by the interaction module 104 in a step E3.

Following these steps, the user device 10 obtains the information that the called device 20 is a voice server implementing automated interaction steps and has established a multimedia communication session. This multimedia session allows a dialogue between the user device 10 and the voice server device 20, in order successively to exchange an interaction menu and a selection relating to the interaction menu received, made by a user of the calling device. Still in this step E3, the interaction module 104 requests by an N5 message the provision of the first Menu interaction menu (1). This message N5 is sent to the interaction module 204 by means of the multimedia session. In a step H2, the interaction module 204 notifies by a Q1 message "CS Voice 30 Call" the voice service application module 205 of the reception of an incoming call. The reception of this message Q1 is acknowledged by the voice service application module 205 by a message Q2. The interaction module 204 then requests by a message Q3 "Get menu in text format" to the voice service application module 205 the provision of the first Menu interaction menu (1). The interaction module 204 receives in response in a message Q4 the first menu Menu (1) in text form. Still in this step H2, the first Menu interaction menu (1) is sent by the interaction module 204 to the RCS module 203. The latter sends it to the RCS module 103 of the calling device 3036570 in a step G3 by a message 05. This menu (1) is sent in text form by means of the established multimedia session for display in text form on a screen of the user device. The first menu interaction menu (1) is received by the RCS module 103 in a step 5 F5. The RCS module 103 then commands the interaction module 104 to display the interaction menu received by a control message N6. In a step E4, the interaction module 104 requests, by an M2 message, the HMI module 105 to display under textual form the first menu Menu (1) on the screen. The HMI module 105 then displays the first Menu interaction menu (1) in a secondary window (called "pop-up 10 window"). The reception of the various messages is then acknowledged (represented in the form of dashed lines in FIG. 4a). Figure Sa illustrates such a display in a secondary window W1. The menu (1) displayed includes a sentence "Blablal" and two proposals for answer "Yes" or "No" to be selected by the user of the device 10.

The user interacts with the calling device to select one of the response proposals that are displayed in the first menu interaction menu (1). When the user device has a touch screen, the selection data is entered by touching the screen. In another embodiment, the selection data relating to the first menu is entered by means of a keyboard of the device 10. In another embodiment, the selection data is entered using up / down arrows. . No limitation is attached to how the usage captures the selection data. FIG. 4b illustrates steps of an interaction method implemented by a user device 10 and by the device 20 according to a particular embodiment, following the selection of a selection data item by the user.

The selection data relating to the first Menu menu (1) is obtained by the HMI module 105. This triggers a sending by the HMI module 105 to the interaction module 104 of a transmission request M3 of the selection data to the device. called. This request M3 is received by the interaction module 104 in a step E5. Still in this step E5, the interaction module 104 transmits an N7 transmission command in text form of the selection data to the RCS module 103. During a step F6, the user device, more specifically the RCS module 103, sends to the device 20 a message 06 comprising the selection data in text form by means of the established multimedia session. In a step G4, the device called, more precisely the module RCS 203, receives from the user device 10 the message 06 comprising the selection data relating to the interaction menu previously sent, in textual form by means of the session 3036570 12 multimedia. Still in this step G4, the module RCS 203 transmits the selection data by a message P4 to the interaction module 204. The message P4 is received in a step H3 by the interaction module 204. Also in this step H3, the Interaction module 204 converts the selection data as a multifrequency bi-ton tone (DTMF) and sends the converted selection data to the voice service application module 205 in a Q5 message. Then in a step H4, the interaction module 204 requests by a message Q6 "Get next menu in text format" to the voice service application module 205 the supply of the next Menu interaction menu (x). This menu depends on the selection data that has been received according to the interaction logic.

The interaction module 204 receives in response in a Q7 message the next menu Menu (x), said current interaction menu. Still in this step H4, the current interaction menu Menu (x) is sent by the interaction module 204 to the RCS module 203 in a message P5. The RCS module 203 sends it to the RCS module 103 of the calling device in a step G5 by a message 07. This current menu 15 Menu (x) is sent in text form by means of the established multimedia session. The current menu interaction menu (x) is received by the RCS module 103 in a step F7, similar to the previously described step F5. The RCS module 103 then commands the interaction module 104 to display the interaction menu received by a control message N8. The interaction module 104 then requests the message M4 to the HMI module 105 to display the current menu. (x) on the screen. The HMI module 105 then displays in textual form in a step E6 the menu of current interaction Menu (x) in the secondary window. The reception of the various messages is then acknowledged (represented in the form of dashed lines in FIG. 4b). Figure Sb illustrates such a display in the secondary window W1. The current menu 25 Menu (x) displayed thus includes a phrase "Blabla2" and two "Choice l" or "Choice2" response proposals to be selected by the user of the device 10. The user interacts with the calling device to select a response proposals that are displayed in the current Menu (x) interaction menu. These different steps are thus implemented successively when the user selects a new piece of data, until the interaction of the user with the voice server 20 is over. The communication can be terminated, or else the The embodiment has been described with a reception in step E2 by the RCS module 103 of a response message 02, in which a communication capability indicates a mode of operation. PLC type. It is emphasized here that when the called device is another user device 11, the communication capability indicates that the operating mode is not of PLC type. The boolean rcs.isAutomata () then takes the value "false". In this case, at step E2, the RCS module 103 transmits to the interaction module 104 a notification indicating that the called device does not implement automated interaction steps. It is therefore a standard user device. In this case, the interaction module 104 establishes voice communication with the conventionally called device. Thus, when the device 5 called is a conventional terminal, the establishment of the voice communication is not disturbed because of the implementation of steps E1, E2 by the interaction module 104. In the embodiment described , an interaction menu is transmitted in text form by means of the established multimedia session. In another embodiment, the interaction menu is transmitted in voice form and the interaction module 104 converts the received menu 10 into textual form. This has the advantage of not modifying the mode of storage interaction menus at the voice server, when they are stored in voice form. In the described embodiment, the selection data is converted into a DTMF tone and transmitted in this form by the interaction module 204 to the voice service application module 205. No limitation is attached to this conversion mode. The selection data may for example be converted to voice form when the user's interaction with the voice server is effected in this manner. The interaction module 204 converts the selection data by speech synthesis and the voice service application module 205 then implements a speech recognition algorithm to recognize the selection data. This makes it possible to limit the modifications to be made for certain types of voice servers. In another embodiment, the selection data is transmitted directly in textual form to the voice service application module 205. In the embodiment described, a multimedia session is established following the detection that the called device implements automated steps of voice interaction. In another embodiment, the multimedia session is established following the request to establish a voice communication between the user device and the called device. This speeds up the display of the first interaction menu. In the embodiment described, a display of an interaction menu is provided, followed by a selection in the displayed interaction menu, this selection making it possible to select the following menu. In the context of an interaction with a voicemail server, the multimedia session also makes it possible to transmit a voice message left by a correspondent. In this embodiment, an audio tag (tag <audio> in VXML for example) corresponds to a pointer to a voice message left by a correspondent. An audio tag in an interaction menu is then transformed by the interaction module 204 into another tag for the interaction module 104. The latter then transforms the other tag into a link to be displayed on the user device. . This link is selectable by a click through the human-machine interface of the user device. On selection by the user, the interaction module 104 detects this other tag and triggers the playback of the audio stream associated with the selected voice message. Playback or audio playback can be performed in continuous download mode (known as streaming) with the voice server. In this case, the interaction module 104 connects by means of the link to an audio download server associated with the voice server. As an illustrative example, this link takes the form <audio src = 5 "www.server.com/mystreaming/audio.mp3">. Audio playback can also be performed locally if the audio file has been downloaded via the multimedia session. As an illustrative example, this link takes the form <audio src = "/sdcard/mystreaming/audio.mp3">. When playing the audio stream associated with the voice message, a second secondary window ("pop-up") is displayed on the screen with play control buttons (ex: play, pause, stop). The interaction menu 10 remains displayed on the screen in the first secondary window. Once the audio playback is finished or if the user returns to the interruption, an interaction menu is displayed. The ergonomics of the consultation and voice message management service is thus improved. In another embodiment, the voice message is converted to a text message. For this purpose, the voice server requests a speech conversion module to text to perform this conversion. More precisely, in step H4, the interaction module 204 requests the message Q6 "Get next menu in text format" from the voice service application module 205 to provide the next Menu interaction menu (x). This menu depends on the selection data that has been received according to the interaction logic. The interaction module 204 receives in response in a message Q7 the next menu Menu (x), the current interaction menu. The interaction module 204 detects in this current interaction menu an audio tag, for example a <audio> VXML tag. In this case, the interaction module 204 requests the voice service application module 205 by a "get voice message in text format" message to transmit in text form the voice message identified by the audio tag. The voice service application module 205 then requests the conversion module to obtain the voice message in text form and transmits it to the interaction module 204. The message in textual form is then sent with the current menu interaction menu. (x) by the interaction module 204 to the RCS module 203 in a message P5. The module RCS 203 sends it to the RCS module 103 of the calling device during the step G5 by the message 07. This current menu Menu (x) and the voice message are thus sent in textual form by means of the multimedia session established. . The current menu then includes a link directly containing the contents of the voice message (for example, <audio txt = "blah">). The display of the current interaction menu in textual form is then performed as described above. The display of the text corresponding to the voice message is displayed in a second secondary window ("pop-up") at the request of the user. This embodiment has the advantage of being entirely in text form and thus makes it possible to interact with a voicemail server to hear voice messages in a silent manner. This consultation can thus be carried out easily in public. This embodiment is also advantageous for hearing-impaired persons. Alternatively, the voice message is converted to text when it is received by the user device. It can thus be seen that from the point of view of the user, in these different embodiments, the interaction with the voice server is very simplified. The user should not listen to a menu in its entirety and memorize the choices that are proposed to him. All he has to do is read the menu displayed in the secondary window. Similarly, when the screen is touch, the selection of the choice is made more naturally. Thus, the interaction method makes it possible to simplify an interaction of a user with a voice server implementing automated voice interaction steps.

No limitation is attached to these various embodiments and one skilled in the art is able to define others to display on the screen interaction menus in text form in a secondary window. The interaction technique is implemented by means of software and / or hardware components. In this context, the term "module" may correspond in this document to both a software component, a hardware component or a set of hardware and / or software components, capable of implementing a function or a set of functions, as described above for the module concerned. A software component corresponds to one or more computer programs, one or more subroutines of a program, or more generally to any element of a program or software. Such a software component is stored in memory and then loaded and executed by a data processor of a physical entity and is able to access the hardware resources of this physical entity (memories, recording media, communication buses, electronic cards of a physical entity). input / output, user interfaces, etc.). In the same way, a hardware component corresponds to any element of a hardware set. It may be a programmable hardware component or not, with or without an integrated processor for running software. This is for example an integrated circuit, a smart card, an electronic card for executing a firmware, etc. In a particular embodiment, the modules 103, 104 are arranged to implement the previously described interaction method. These are preferably software modules 30 comprising software instructions for executing those of the steps of the interaction method described above, implemented by a user device. The invention therefore also relates to: - a program for a user device, comprising program code instructions for controlling the execution of the steps of the previously described interaction method, when said program is executed by that user device; a recording medium readable by a user device on which the program for a device is recorded.

In a particular embodiment, the modules 203, 204 are arranged to implement the previously described interaction method. These are preferably software modules comprising software instructions for executing those of the steps of the interaction method described above, implemented by a voice interaction device.

The invention therefore also relates to: a program for a voice interaction device, comprising program code instructions for controlling the execution of the steps of the previously described interaction method, when said program is executed by this device voice interaction; a recording medium readable by a voice interaction device on which the program is recorded for a voice interaction device. The software modules can be stored in or transmitted by a data carrier. This may be a hardware storage medium, for example a CD-ROM, a magnetic diskette or a hard disk, or a transmission medium such as an electrical signal, optical or radio, or a telecommunications network. 15

Claims (13)

REVENDICATIONS1. A method of interacting a user device (10, 11) with a called device, said method comprising, when a request for establishing a voice communication between the user device and the called device is issued: - a detection ( E2) by the user device that the called device implements automated voice interaction steps; a display (E4, E6) on a screen of the user device in text form of an interaction menu received by means of a multimedia session established between the user device and the called device; a sending (E5) by the user device in textual form by means of the multimedia session of a selection data item relating to the interaction menu received. The interaction method according to claim 1, wherein the detection comprises sending (F1) to the called device a communication capability discovery message and receiving (F2) a communication capability indicating a communication mode. PLC type operation. 3. Interaction method according to claim 1, wherein the multimedia session is established following the detection that the called device implements automated voice interaction steps. 4. Interaction method according to claim 1, wherein the interaction menu is received in text form by means of the multimedia session. A method of interacting a user device (10, 11) with a called device, said method comprising, when a request for establishing a voice communication between the user device and the called device is received: providing (G1) by the device called to the user device an indication that the called device implements automated voice interaction steps; - A sending (G3) to the user device of an interaction menu by means of a multimedia session established between the user device and the called device for display in text form on a screen of the user device; a reception (G4) by the called device of a selection data item relating to the sent interaction menu, received in text form by means of the multimedia session. The interaction method according to claim 5, wherein the providing comprises receiving (G1) by the called device of a communication capability discovery message and sending (G1) a communication capability indicating a mode of operation of the automaton type. 7. Interaction method according to claim 5, wherein the interaction menu is sent in text form by means of the multimedia session. 8. User device (10, 11) comprising: - an interaction module (104), arranged to: - detect a device for which a request for setting up a voice communication is sent, called called device, implements automated voice interaction steps; receiving an interaction menu by means of a multimedia session established between the user device and the called device; sending, in textual form by means of the multimedia session, a selection data item relating to the interaction menu received; a human-machine interface module (105), arranged to display on a screen of the user device in textual form the received interaction menu. A voice interaction device (20) arranged to interact by means of a voice communication with a user device, said voice interaction device comprising: a communication module (203) arranged to provide a voice communication service; communication enriched and to provide to a user device the applicant an indication that said voice interaction device implements automated voice interaction steps; an interaction module (204), arranged to: - provide in response to a request from a user device an interaction menu by means of a multimedia session established between the user device and the voice interaction device for a textual display on a screen of the user device; receiving selection data relating to the sent interaction menu, received in text form by means of the multimedia session. Program for a user device, comprising program code instructions for controlling the execution of those of the steps of the interaction method according to one of claims 1 to 4 implemented by the device, when said program is executed by said device. 3036570 19 11. Recording medium readable by a user device on which the program according to claim 10 is recorded. 12. Program for a voice interaction device, comprising program code instructions for controlling the execution of those of the steps of the interaction method according to one of claims 5 or 6 implemented by the device, when said program is executed by said device. 13. A recording medium readable by a voice interaction device on which the program according to claim 12 is recorded.