RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
This Page is under Development
Briefly describe in general terms the system/application and the purpose for which it is intended, written in non-technical terminology. Consider including a high-level architecture diagram for the system. The description should include, but is not limited to, the following:
1. Talaria: This service maintains the secure websocket connections from the device and passes the messages from or to the device.
2. Scytale: This accepts the inbound requests and delivers the messages to the Talaria machines that could be hosting the device connection.
3. Tr1d1um: The Webpa micro-service that encode TR-181 requests.
On client-side
4. Parodus: Parodus is the light weight client that reaches out to the xmidt cloud to establish the connection from CPE devices.
Optional:
5. Petasos : Petasos helps reduce the load on the Talaria machines by calculating which specific Talaria a device should connect to & redirecting the incoming request.
6. Caduceus: Caduceus provides the pub-sub message delivery (notification) mechanism for xmidt
1. The mentioned sevices need to be actively running with the basic key authorization.
2. Auth token: The auth token will be used when configuring different webPA components as well while performing GET/SET requests to the CPE from a 3rd party application.
Once the Turris-Omnia set-up is active with client services, communication between turris and WebPA server can be established.
The following are the major components/services involved in the fetching the data,
The validation artifacts that are essential to ensure the functionality,
CPE Device mac address
The data from the client device can be fetched through the curl commands,
Curl command to retrieve the data(get parameter):
<Identify the error messages that a user may receive and the likely cause(s) and/or possible corrective actions for the error>
<If applicable, describe any special circumstances, actions, exceptions, etc., that should be considered for troubleshooting.>
Contact | Organization | Phone | Role | |
<Contact Name> | <Organization> | <Phone> | <Email> | <Role> |