|
|
Using the NLU Gateway
Reference Number: AA-02446 Views: 103 |
0 Rating/ Voters
|
    |
Usage of the NLU Gateway is done as an added feature of using the LumenVox Transcription ASR engine. When activating the transcription engine a simple "dummy" grammar is supplied with a meta tag within the grammar triggering transcription mode. When also using the gateway, a further meta tag is supplied to signal which NLU end-point is to be used to do the NLU processing. In this example, US English transcription will be done on the audio. The text results will then be sent to the NLU Gateway, using the end-point set up with the name "TravelBot". <?xml version='1.0'?> <!-- This is a dummy grammar that should not be used for speech recognition. This should only be used to switch LumenVox licensing to "SLM" mode. --> <grammar xml:lang="en-US" version="1.0" root="root" mode="voice" xmlns="http://www.w3.org/2001/06/grammar" tag-format="semantics/1.0">
<meta name="switch_license_type" content="SLM"/> <meta name="lv_nlu_gateway_model_id" content="TravelBot"/> <rule id="root" scope="public">
<ruleref special="NULL"/>
</rule> </grammar>
The ASR engine will process the audio, create the transcription text, and then send the text to the NLU service via the NLU Gateway. The results from the NLU service will be returned in the semantic interpretation portion of the overall results returned by the ASR engine. This will be in xml format as defined by W3C SISR specification. However, there is a configuration option available, that will return the results as a JSON formatted string. This may simplify the task of parsing the NLU results within the speech application's code.
Sample XML style output.
Sample JSON style output.
|
|
|