Date: Thu, 28 Mar 2024 14:52:23 +0000 (UTC) Message-ID: <2002297456.17208.1711637543879@localhost> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_17207_1650694167.1711637543879" ------=_Part_17207_1650694167.1711637543879 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Modified |
&nbs= p;by SHIBUTHOMAS |
||||||||
---|---|---|---|---|---|---|---|---|---|
Version | Future Release | ||||||||
Contact |
|
||||||||
Jira |
|
To demonstrate a method to integrate Alexa Echo Dot with RDK 4.0 by deve= loping Alexa skills and integrate on RDK 4.0 reference platforms:-
Following sections will give the architecture details and end to end flo= w diagram
*Note: Above is the stable stat= e end goal of the product architecture. Rest of the section is for demonstr= ation purposes as an example and not realizing the full scope of the above = architecture as end goal.
This above mentioned application helps to demonstrate E2E working of&nbs= p; Alexa voice and can easily extend to a more scalable, performant and SPOF(Single point of failure= ) handling design.
It is customer responsibility to create Alexa Use account and STB accoun= t once Alexa voice feature has enabled. Following steps explains how can we= create a user account. STB account has to mapped with amazon user id= and this mapping will ensure that respective alexa voice will reach to the= right STB
Below section give the details of the each components involved:-
Follow the process outlined in the attached document to configure the se= rver.
8.1 Is this a ready to deploy service integration ?
No, this is not. It is only meant for demonstration of capability purpos= es.
8.1 What is pending from this proof of concept to actually integrate ech= o dot as part of RDK 4.0 Voice ecosystem ?
Scalability and security of product deployment is missing in this implem= entation.
8.3 Do I have to sign any special license or pay a fee to use this servi= ce if I have Alexa Echo Dot configured in my home Wifi ?
No.
8.4 Who shall we contact in case we have to integrate more skills to thi= s mode ?
TBD
8.5 Which version of Alexa devices are supported ? What about STB models= ? RDK Software versions ?
TBD
8.6 What happens if my echo device does not recognize the commands in th= e prescribed formats of the API ? Which are the areas I should look for tri= aging ?
TBD
8.7 How scalable is the current solution ?
End state architecture has scalability built into it, current PoC is onl= y for demonstration purposes.
8.8 How secure is the current solution ?
End state architecture has security built into it, current PoC is only f= or demonstration purposes.
8.9 Is there a plan in RDK community to realize the end state architectu= re ?
Currently No. We will revisit the plan based on the users feedback and i= nterest in using this service.