RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
<work in progress>
Table of Contents | ||
---|---|---|
|
Background Color | ||
---|---|---|
| ||
Overview |
Device Manager, as the name suggests, is an application to manage different devices by fetching the device details, adding devices, adding device groups, managing device reservations etc.
Please note: All the non-mandatory request fields are marked as “optional”.
Background Color | ||
---|---|---|
| ||
Tags |
Tag Name | Desscription |
---|---|
Device Group | APIs which handle requests for device group. |
Device Category | APIs which handle requests for device category. |
Device Feature | APIs which handle requests for device feature. |
Device | APIs which handle requests for device details. |
Device Model | APIs which handle requests for device models. |
Head End | APIs which handle requests for head end. |
Device Management | API for Device Management. |
User | APIs which handle requests for user management. |
Background Color | ||
---|---|---|
| ||
Paths |
These APIs handle requests for device details.
This API adds a device to the Device Manager database. Devices to be used in the Automatics System should be configured in Device Manager. These devices are provided to Automatics Orchestration during test execution.
Before adding a device, the user must add Head End (/headEnd/add), Device Group (/deviceGroup/add), Device Feature (/deviceFeature/add) and Device Model(/deviceModel/add) to Device Manager. These values will be provided as the input to the device details fields request.
Responses
Code | Description | Links |
---|---|---|
200 | OK Content | No Links |
201 | Created | No Links |
401 | Unauthorized | No Links |
403 | Forbidden | No Links |
404 | Not Found | No Links |
This API lists all devices configured in the Device Manager application.
Responses
Code | Description | Links |
---|---|---|
200 | OK Content application/json/ | No Links |
401 | Unauthorized | No Links |
403 | Forbidden | No Links |
404 | Not Found | No Links |
This API deletes the device from Device Manager application. The input given to the REST API is mac address and it deletes the device with given mac address.
Responses
Code | Description | Links |
---|---|---|
200 | OK Content | No Links |
201 | Created | No Links |
401 | Unauthorized | No Links |
403 | Forbidden | No Links |
404 | Not Found | No Links |
This API gets name of the head end system to which the device is connected. The input to the REST API is the device mac address.
Parameters
Type | Name | Description | Schema |
---|---|---|---|
query | mac required | mac | string |
Responses
Code | Description | Links |
---|---|---|
200 | OK Content application/json/ | No Links |
401 | Unauthorized | No Links |
403 | Forbidden | No Links |
404 | Not Found | No Links |
This API gets details of the device with given ecm mac address from Device Manager application. Input to the REST API is device ecm mac address.
Parameters
Type | application/jsonName | Description | Schema |
---|---|---|---|
query | mac required | mac | string |
Responses
Code | Description | Links |
---|---|---|
200 | OK Content | No Links |
401 | Unauthorized | No Links |
403 | Forbidden | No Links |
404 | Not Found | No Links |
This API gets details of the device with the given mac address from Device Manager application. Input to the RSER API is device mac address.
Parameters
Type | Name | Description | Schema |
---|---|---|---|
query | mac required | mac | string |
Responses
Code | Description | Links |
---|---|---|
200 | OK Content | No Links |
401 | Unauthorized | No Links |
403 | Forbidden | No Links |
404 | Not Found | No Links |
This API gets the list of devices that matches the given search criteria and gateway mac address of the device. The input to the REST API is device mac address. The search criteria include device status, feature name, device group name, head end name, ip type, consider devices excluded from pool and skip device group application/json fields.
Responses
Code | Description | Links |
---|---|---|
200 | OK Content application/json/ | No Links |
201 | Created | No Links |
401 | Unauthorized | No Links |
403 | Forbidden | No Links |
404 | Not Found | No Links |
This API gets ecm mac address of the device. The input to the REST API is device mac address.
Parameters
Type | Name | Description | Schema |
---|---|---|---|
query | mac required | mac | string |
Responses
Code | Description | Links |
---|---|---|
200 | OK Content application/json/ | No Links |
401 | Unauthorized | No Links |
403 | Forbidden | No Links |
404 | Not Found | No Links |
This API gets gateway mac address of the device. The input to the REST API is device mac address. This will return the mac address of the gateway device to which the given client device is connected.
Parameters
Type | Name | Description | Schema |
---|---|---|---|
query | mac required | mac | string |
Responses
Code | Description | Links |
---|---|---|
200 | OK Content application/json/ | No Links |
401 | Unauthorized | No Links |
403 | Forbidden | No Links |
404 | Not Found | No Links |
This API G=gets IP address of the device. The input to the REST API is device mac address and mac type.
Mac type refers to the type of mac address. The expected values are ‘DEVICE’ and ‘ECM’.
‘DEVICE’ refers to mac address of the device.
‘ECM’ refers to ecm mac address of the device.
Parameters
Type | Name | Description | Schema |
---|---|---|---|
query | macType required | macType | string |
query | mac | string |
Responses
Code | Description | Links |
---|---|---|
200 | OK Content application/json/ | No Links |
401 | Unauthorized | No Links |
403 | Forbidden | No Links |
404 | Not Found | No Links |
This API updates the device status to IN_USE. This refers that the device is being in use for test execution in Automatics. Devices with status IN_USE will not be considered for other test executions. This facilitates exclusive access to devices during testing.
Responses
Code | Description | Links |
---|---|---|
200 | OK Content application/json/ | No Links |
201 | Created | No Links |
401 | Unauthorized | No Links |
403 | Forbidden | No Links |
404 | Not Found | No Links |
This API updates the device status to GOOD. After test execution, Automatics will update the status of the device to ‘GOOD’. This means that the device is available for the next test execution.
Responses
Code | Description | Links |
---|---|---|
200 | OK Content application/json/ | No Links |
201 | Created | No Links |
401 | Unauthorized | No Links |
403 | Forbidden | No Links |
404 | Not Found | No Links |
These APIs handle requests for device category.
This API is used to add a new Device Category to the Device Manager application. Valid values are RDKV, RDKV, and RDKC.
Responses
Code | Description | Links |
---|---|---|
200 | OK Content | No Links |
201 | Created | No Links |
401 | Unauthorized | No Links |
403 | Forbidden | No Links |
404 | Not Found | No Links |
This API returns all the Device Category details configured in the Device Manager application.the Device Manager application.
Responses
Code | Description | Links |
---|---|---|
200 | OK Content application/json/ | No Links |
401 | Unauthorized | No Links |
403 | Forbidden | No Links |
404 | Not Found | No Links |
This API is used to delete an existing Device Category from the Device Manager application.
Responses
Code | Description | Links |
---|---|---|
200 | OK Content application/json | No Links |
201 | Created | No Links |
401 | Unauthorized | No Links |
403 | Forbidden | No Links |
404 | Not Found | No Links |
These APIs handle requests for device features.
This API adds device features to the system. The field ‘specialFeature’ specifies whether the given feature is a special device feature. Valid values are ‘Y’ and ‘N’. ‘Y’ refers to special feature and ‘N’ refers to not-a-special feature. This field has no impact on fetching device data currently; however, this is added as part of future enhancement to the Device Manager application.
Responses
Code | Description | Links |
---|---|---|
200 | OK Content | No Links |
201 | Created | No Links |
401 | Unauthorized | No Links |
403 | Forbidden | No Links |
404 | Not Found | No Links |
This API returns all the device features available in the Device Manager application.
Responses
Code | Description | Links |
---|---|---|
200 | OK application/json Content application/json / | No Links |
401 | Unauthorized | No Links |
403 | Forbidden | No Links |
404 | Not Found | No Links |
This API is used to delete an existing device feature from the Device Manager application.
Responses
Code | Description | Links |
---|---|---|
200 | OK Content application/json | No Links |
201 | Created | No Links |
401 | Unauthorized | No Links |
403 | Forbidden | No Links |
404 | Not Found | No Links |
This API adds a device group to the Device Manager application. This is done for logical grouping and managing access to the devices. Admin must first configure these groups in Automatics Orchestration and then must map the device groups to the users. This will allow users to execute tests only from mapped device groups.
Responses
Code | Description | Links |
---|---|---|
200 | OK Content application/json | No Links |
201 | Created | No Links |
401 | Unauthorized | No Links |
403 | Forbidden | No Links |
404 | Not Found | No Links |