Abstract: Techniques for routing a user command to a speechlet and resolving conflicts between potential speechlets are described. A system determines an intent of an input command. The system also receives context information associated with the input command. The system determines speechlets (e.g., speechlets and/or skills) that may execute with respect to the input command given the intent and the context data. The system then determines whether conditions of routing rules, associated with the speechlets, are satisfied given the context data. If the conditions of only one routing rule are satisfied, the system causes the speechlet associated with the routing rule to execute with respect to the input command. If the conditions of more than one routing rule are satisfied, the system may determine a speechlet to execute with respect to the input command based on the speechlets' priorities in a list of speechlets and/or based on potential output data provided by the speechlets.

Abstract: Validating proof of possession (POP) of a private key by a device. A computer system generates a provisioning package for a device catalog. The provisioning package including a POP challenge. After generating the provisioning package, the computer system receives a device activation request for a device. The device activation request includes a public key, a device identifier, and a signature. The computer system validates POP of a private key corresponding to the public key, including using the public key, the device identifier, and the POP challenge to cryptographically verify the signature. The computer system establishes a trust relationship with the device, including registering the public key and the device identifier into the device catalog.

Abstract: Techniques for configuring device-specific skills as top-level skills are described. When a system receives a user input the system performs NLU processing to determine an intent of the user input. In some instances, the system may identify a device-specific skill associated with the device interacted with by the user. At least partially in parallel to performing NLU processing to determine the intent of the user input, the system may also perform NLU processing to determine a likelihood that the user input corresponds to an intent actionable by the device-specific skill. Once the system has finished NLU processing, the system may implement one or more prioritization rules to determine whether the user input should be sent to the device-specific skill or another skill of the system.

Abstract: Techniques for routing a user command to a speechlet and resolving conflicts between potential speechlets are described. A system determines an intent of an input command. The system also receives context information associated with the input command. The system determines speechlets (e.g., speechlets and/or skills) that may execute with respect to the input command given the intent and the context data. The system then determines whether conditions of routing rules, associated with the speechlets, are satisfied given the context data. If the conditions of only one routing rule are satisfied, the system causes the speechlet associated with the routing rule to execute with respect to the input command. If the conditions of more than one routing rule are satisfied, the system may determine a speechlet to execute with respect to the input command based on the speechlets' priorities in a list of speechlets and/or based on potential output data provided by the speechlets.

Abstract: Techniques for transferring control of a system-user dialog session are described. A first speechlet component may interact with a user until the first speechlet component receives user input that the first speechlet component cannot handle. The first speechlet component may output an action representing the user input. A system may determine a second speechlet component configured to execute the action. The system may send the second speechlet component a navigator object that results in the second speechlet component handling the user interaction that the first speechlet component could not handle. Once the second speechlet component is finished processing, the second speechlet component may output an updated navigator object, which causes the first speechlet component to either further interact with a user or cause a current dialog session to be closed.

Abstract: Techniques for routing a user command to a speechlet and resolving conflicts between potential speechlets are described. A system determines an intent of an input command. The system also receives context information associated with the input command. The system determines speechlets (e.g., speechlets and/or skills) that may execute with respect to the input command given the intent and the context data. The system then determines whether conditions of routing rules, associated with the speechlets, are satisfied given the context data. If the conditions of only one routing rule are satisfied, the system causes the speechlet associated with the routing rule to execute with respect to the input command. If the conditions of more than one routing rule are satisfied, the system may determine a speechlet to execute with respect to the input command based on the speechlets' priorities in a list of speechlets and/or based on potential output data provided by the speechlets.

Abstract: Techniques for configuring device-specific skills as top-level skills are described. When a system receives a user input the system performs NLU processing to determine an intent of the user input. In some instances, the system may identify a device-specific skill associated with the device interacted with by the user. At least partially in parallel to performing NLU processing to determine the intent of the user input, the system may also perform NLU processing to determine a likelihood that the user input corresponds to an intent actionable by the device-specific skill. Once the system has finished NLU processing, the system may implement one or more prioritization rules to determine whether the user input should be sent to the device-specific skill or another skill of the system.

Abstract: Techniques for configuring device-specific skills as top-level skills are described. When a system receives a user input the system performs NLU processing to determine an intent of the user input. In some instances, the system may identify a device-specific skill associated with the device interacted with by the user. At least partially in parallel to performing NLU processing to determine the intent of the user input, the system may also perform NLU processing to determine a likelihood that the user input corresponds to an intent actionable by the device-specific skill. Once the system has finished NLU processing, the system may implement one or more prioritization rules to determine whether the user input should be sent to the device-specific skill or another skill of the system.