EXTENDABLE VOICE COMMANDS

• US 20110294476A1
• Filed: 08/09/2011
• Published: 12/01/2011
• Est. Priority Date: 06/22/2004
• Status: Active Grant

• Current Assignee: Cerence Operating Company (Cerence Inc.)
• Original Assignee: Nuance Communications, Inc. (Microsoft Corporation)
• Inventors: Cohen, Jordan, Roth, Daniel L., Reiner, Chris, Furnari, Mark
• Granted Patent: US 8,731,609 B2
• Time in Patent Office: Days
• US Class Current: 455/414.1
• CPC Class Codes: H04M 1/271 controlled by voice recognition
• CPC Class Codes: H04M 1/72406 by software upgrading or downloading
• CPC Class Codes: H04M 2250/74 with voice recognition means voice activated dialling H04M1/271; voice recognition algorithms G10L15/00
• CPC Class Codes: H04M 3/42178 by downloading data to substation equipment
• CPC Class Codes: H04M 3/4938 comprising a voice browser which renders and interprets, e.g. VoiceXML
• CPC Class Codes: H04W 4/18 Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals

Abstract

A mobile device, such as a cellular telephone includes a voice interface that includes one part that may not be specific to a particular carrier, and a second part that provides an interface to services that are specific to a carrier or to service or information providers that are not necessarily available with all carriers. A voice command interface provides easy access to the carrier services. The set of carrier services is optionally extendible by the carrier.

Claims

1. A method of implementing at least one functionality with respect to carrier services at a mobile device, the method comprising:

receiving first carrier interface data at a carrier interface, the first carrier interface data providing data with respect to accessing a first carrier service of a first carrier service provider;

receiving second carrier interface data at the carrier interface, the second carrier interface data providing data with respect to accessing a second carrier service of a second carrier service provider, the first carrier service provider different than the second carrier service provider; and

associating at least one respective mobile device state defined in a menu tree structure interface with each of the first carrier interface data and the second carrier interface data.

2. The method as in claim 1, wherein receiving first carrier interface data at the carrier interface includes:

receiving a definition of a relationship between the first carrier service and a first mobile device state, the relationship selectively enabled by the first carrier service provider.

3. The method as in claim 2, includes:

upon associating the at least one mobile device state in the menu tree structure interface with the first carrier interface data, implementing the relationship between the first carrier service and the first mobile device state.

4. The method as in claim 3, wherein implementing the relationship between the first carrier service and the first mobile device state includes:

prohibiting mobile device access to the first carrier service when the mobile device is set at the first mobile device state.

5. The method as in claim 3, wherein implementing the relationship between the first carrier service and the first mobile device state via the carrier interface and the menu tree structure interface includes:

setting the mobile device at the first mobile device state upon termination of a mobile device session of the first carrier service.

6. The method as in claim 3, wherein implementing the relationship between the first carrier service and the first mobile device state via the carrier interface and the menu tree structure interface includes:

updating a visual indicator associated with the first carrier service, wherein the menu tree structure interface displays the updated visual indicator when the mobile device is set at the first mobile device state.

7. The method as in claim 6, comprising:

updating the visual indicator after receiving the second carrier interface data at the carrier interface.

8. The method as in claim 3, wherein implementing the relationship between the first carrier service and the first mobile device state via the carrier interface and the menu tree structure interface includes:

initiating access to the first carrier service by the mobile device based on receipt of at least one aural cue, wherein the at least one aural cue is (i) defined in the first interface data and (ii) graphically represented in the menu tree structure interface when the mobile device is at the first mobile device state.

9. The method as in claim 8, initiating access to the first carrier service by the mobile device based on receipt of the at least one aural cue includes:

detecting a selection of the first mobile device state, the first mobile device state comprising a speech services state;

displaying a graphical representation of a first aural cue;

receiving the first aural cue;

transitioning from the first mobile device state to a second mobile device state based on receipt of the first aural cue;

generating performance of a second aural cue;

displaying a graphical representation of a third aural cue; and

upon receiving the third aural cue, accessing the first carrier service.

10. A non-transitory computer readable storage medium comprising executable instructions encoded thereon operable on a computerized device to perform processing comprising at least one instruction for:

receiving first carrier interface data at a carrier interface, the first carrier interface data providing data with respect to accessing a first carrier service of a first carrier service provider;

receiving second carrier interface data at the carrier interface, the second carrier interface data providing data with respect to accessing a second carrier service of a second carrier service provider, the first carrier service provider different than the second carrier service provider; and

associating at least one respective mobile device state defined in a menu tree structure interface with each of the first carrier interface data and the second carrier interface data.

11. The non-transitory computer readable storage medium as in claim 10, wherein the at least one instruction for receiving first carrier interface data at the carrier interface includes at least one instruction for:

receiving a definition of a relationship between the first carrier service and a first mobile device state, the relationship selectively enabled by the first carrier service provider.

12. The non-transitory computer readable storage medium as in claim 11, includes:

at least one instruction for implementing the relationship between the first carrier service and the first mobile device state upon associating the at least one mobile device state in the menu tree structure interface with the first carrier interface data.

13. The non-transitory computer readable storage medium as in claim 12, wherein the at least one instruction for implementing the relationship between the first carrier service and the first mobile device state includes at least one instruction for:

prohibiting mobile device access to the first carrier service when the mobile device is set at the first mobile device state.

14. The non-transitory computer readable storage medium as in claim 12, wherein the at least one instruction for implementing the relationship between the first carrier service and the first mobile device state via the carrier interface and the menu tree structure interface includes at least one instruction for:

setting the mobile device at the first mobile device state upon termination of a mobile device session of the first carrier service.

15. The non-transitory computer readable storage medium as in claim 12, wherein the at least one instruction for implementing the relationship between the first carrier service and the first mobile device state via the carrier interface and the menu tree structure interface includes at least one instruction for:

updating a visual indicator associated with the first carrier service, wherein the menu tree structure interface displays the updated visual indicator when the mobile device is set at the first mobile device state.

16. The non-transitory computer readable storage medium as in claim 15, comprising:

at least one instruction for updating the visual indicator after receiving the second carrier interface data at the carrier interface.

17. The non-transitory computer readable storage medium as in claim 12, wherein the at least one instruction for implementing the relationship between the first carrier service and the first mobile device state via the carrier interface and the menu tree structure interface includes at least one instruction for:

initiating access to the first carrier service by the mobile device based on receipt of at least one aural cue, wherein the at least one aural cue is (i) defined in the first interface data and (ii) graphically represented in the menu tree structure interface when the mobile device is at the first mobile device state.

18. The non-transitory computer readable storage medium as in claim 17, wherein the at least one instruction for initiating access to the first carrier service by the mobile device based on receipt of the at least one aural cue includes at least one instruction for:

detecting a selection of the first mobile device state, the first mobile device state comprising a speech services state;

displaying a graphical representation of a first aural cue;

receiving the first aural cue;

transitioning from the first mobile device state to a second mobile device state based on receipt of the first aural cue;

generating performance of a second aural cue;

displaying a graphical representation of a third aural cue; and

upon receiving the third aural cue, accessing the first carrier service.

19. A computer system comprising:

a processor;

a memory unit that stores instructions associated with an application executed by the processor; and

an interconnect coupling the processor and the memory unit, enabling the computer system to execute the application and perform operations of;

receiving first carrier interface data at a carrier interface, the first carrier interface data providing data with respect to accessing a first carrier service of a first carrier service provider;

receiving second carrier interface data at the carrier interface, the second carrier interface data providing data with respect to accessing a second carrier service of a second carrier service provider, the first carrier service provider different than the second carrier service provider; and

associating at least one respective mobile device state defined in a menu tree structure interface with each of the first carrier interface data and the second carrier interface data.

20. The computer system as in claim 19, comprising:

wherein receiving first carrier interface data at the carrier interface includes;

receiving a definition of a relationship between the first carrier service and a first mobile device state, the relationship selectively enabled by the first carrier service provider;

upon associating the at least one mobile device state in the menu tree structure interface with the first carrier interface data, implementing the relationship between the first carrier service and the first mobile device state;

wherein implementing the relationship between the first carrier service and the first mobile device state via the carrier interface and the menu tree structure interface includes;

initiating access to the first carrier service by the mobile device based on receipt of at least one aural cue, wherein the at least one aural cue is (i) defined in the first interface data and (ii) graphically represented in the menu tree structure interface when the mobile device is at the first mobile device state; and

wherein initiating access to the first carrier service by the mobile device based on receipt of the at least one aural cue includes;

detecting a selection of the first mobile device state, the first mobile device state comprising a speech services state;

displaying a graphical representation of a first aural cue;

receiving the first aural cue;

transitioning from the first mobile device state to a second mobile device state based on receipt of the first aural cue;

generating performance of a second aural cue;

displaying a graphical representation of a third aural cue; and

upon receiving the third aural cue, accessing the first carrier service.