Page History

...

Validation - TBD

Feature Validation (LogUpload)

Configuration

1. Create upload repository via DCM->Upload repository -> Create.   Here we can add where to configure the log upload, is the upload url and which protocol is used)

2. Create rule via DCM->Formulas->Create. 

3.  Once you save the created formula  , then a ‘define Settings’ tab with ‘Create Device Settings’, ‘Create log settings’, Create VOD settings’ will be available

4.  Edit the  Device Settings tab

5.  Edit the Log upload Setting (Create schedule & Add the upload repository created beforehand.

Validation - TBD

Feature Validation (Telemetry)

1. Telemetry configuration can be done by adding a permanent profile which contains below objects
   1. Upload repository
   2. Profile options (Header, content, frequency etc.)
2. Creating a targeting rule which is basically mapping the profile to a set of MAC/IP/Device etc.

Configuration

1. Create a permanent profile Telemetry - > Permanent Profiles -> Create

     2. Once you save the permanent profile, you will get a message overlay ‘Profile added to the pending changes’. Then go to Changes -> select the profile you create -> Click on “Approve selected changes”.
Then the permanent profile will be listed under Telemetry - > Permanent profiles

...

Verification

1. Verification of feature and feature rule via test page.

After creating the feature and feature rule, go to RFC->Test page and give a parameter that will match the one of the rules that you have created. Then matched rule and the json response will be displayed like below.

Image Added

    2.  Verification via curl command

The curl command mocks the request being sent from an STB like below and sample response is also given. It can be given as a curl command or as a get request via postman or browser

eg : curl 'http://<XCONF_IP>:19092/featureControl/getSettings?estbMacAddress= B8:27:EB:94:71:82’

Sample Response:

{

    "featureControl": {

        "features": [

            {

                "name": "EmulatorFeature",

                "effectiveImmediate": true,

                "enable": false,

                "configData": {

                    "ENABLE_AAMP": "false"

                },

                "featureInstance": "AAMP-mock feature"

            }

        ]

    }

}

Client end verification (RPI)

Feature Validation (LogUpload)

Configuration

1. Create upload repository via DCM->Upload repository -> Create.   Here we can add where to configure the log upload, is the upload url and which protocol is used)

2. Create rule via DCM->Formulas->Create. 

3.  Once you save the created formula  , then a ‘define Settings’ tab with ‘Create Device Settings’, ‘Create log settings’, Create VOD settings’ will be available

4.  Edit the  Device Settings tab

5.  Edit the Log upload Setting (Create schedule & Add the upload repository created beforehand.

Verification

1. Verification of log upload settings test page.

After creating the feature and feature rule, go to DCM->Test page and give a parameter that will match the one of the formulas that you have created. Then matched rule and the settings will be displayed like below

Image Added

2. Verification via curl command

The curl command mocks the request being sent from an STB like below and sample response is also given. It can be given as a curl command or as a get request via postman or browser

eg : curl 'http://<XCONF_IP>: 19092/loguploader/getSettings?estbMacAddress=B8:27:EB:94:71:82’

Sample response : 

{

    "urn:settings:GroupName": "RPI_Device_Settings",

    "urn:settings:CheckOnReboot": true,

    "urn:settings:CheckSchedule:cron": "10 00 * * *",

    "urn:settings:CheckSchedule:DurationMinutes": 0,

    "urn:settings:LogUploadSettings:Message": null,

    "urn:settings:LogUploadSettings:Name": "Log upload settings test",

    "urn:settings:LogUploadSettings:NumberOfDays": 5,

    "urn:settings:LogUploadSettings:UploadRepositoryName": "Upload repository test",

    "urn:settings:LogUploadSettings:RepositoryURL": "http://35.155.171.121/xconf/logupload.php",

    "urn:settings:LogUploadSettings:UploadOnReboot": false,

    "urn:settings:LogUploadSettings:UploadImmediately": false,

    "urn:settings:LogUploadSettings:upload": true,

    "urn:settings:LogUploadSettings:UploadSchedule:cron": "10 00 * * *",

    "urn:settings:LogUploadSettings:UploadSchedule:levelone:cron": null,

    "urn:settings:LogUploadSettings:UploadSchedule:leveltwo:cron": null,

    "urn:settings:LogUploadSettings:UploadSchedule:levelthree:cron": null,

    "urn:settings:LogUploadSettings:UploadSchedule:DurationMinutes": 0,

    "urn:settings:VODSettings:Name": null,

    "urn:settings:VODSettings:LocationsURL": null,

    "urn:settings:VODSettings:SRMIPList": null

}

Client end verification (RPI)

Feature Validation (Telemetry)

1. Telemetry configuration can be done by adding a permanent profile which contains below objects
   1. Upload repository
   2. Profile options (Header, content, frequency etc.)
2. Creating a targeting rule which is basically mapping the profile to a set of MAC/IP/Device etc.

Configuration

1. Create a permanent profile Telemetry - > Permanent Profiles -> Create

     2. Once you save the permanent profile, you will get a message overlay ‘Profile added to the pending changes’. Then go to Changes -> select the profile you create -> Click on “Approve selected changes”.
Then the permanent profile will be listed under Telemetry - > Permanent profiles

     3. Create targeting rule via Telemetry -> Targeting rules. Targeting rules is to map the profiles with rules.

Verification

1. Verification of telemetry test page.

After creating the permanent profile and targeting rules, go to Telemetry->Test page and give a parameter that will match the one of the rule that you have created. Then matched rule will be displayed like below.

Image Added

      2.  Verification via curl command

The curl command mocks the request being sent from an STB like below and sample response is also given. It can be given as a curl command or as a get request via postman or browser. The same url used for logupload verification is used here, the response will have telemetry settings data like below (urn:settings:TelemetryProfile)

eg : curl 'http://<XCONF_IP>: 19092/loguploader/getSettings?estbMacAddress=B8:27:EB:94:71:82’

Sample Response :

{

    "urn:settings:GroupName": "RPI_Device_Settings",

    "urn:settings:CheckOnReboot": true,

    "urn:settings:CheckSchedule:cron": "10 00 * * *",

    "urn:settings:CheckSchedule:DurationMinutes": 0,

    "urn:settings:LogUploadSettings:Message": null,

    "urn:settings:LogUploadSettings:Name": "Log upload settings test",

    "urn:settings:LogUploadSettings:NumberOfDays": 5,

    "urn:settings:LogUploadSettings:UploadRepositoryName": "Upload repository test",

    "urn:settings:LogUploadSettings:RepositoryURL": "http://35.155.171.121/xconf/logupload.php",

    "urn:settings:LogUploadSettings:UploadOnReboot": false,

    "urn:settings:LogUploadSettings:UploadImmediately": false,

    "urn:settings:LogUploadSettings:upload": true,

    "urn:settings:LogUploadSettings:UploadSchedule:cron": "10 00 * * *",

    "urn:settings:LogUploadSettings:UploadSchedule:levelone:cron": null,

    "urn:settings:LogUploadSettings:UploadSchedule:leveltwo:cron": null,

    "urn:settings:LogUploadSettings:UploadSchedule:levelthree:cron": null,

    "urn:settings:LogUploadSettings:UploadSchedule:DurationMinutes": 0,

    "urn:settings:VODSettings:Name": null,

    "urn:settings:VODSettings:LocationsURL": null,

    "urn:settings:VODSettings:SRMIPList": null,

    "urn:settings:TelemetryProfile": {

        "id": "b160a5a8-c753-4e71-b267-992965a4437b",

        "telemetryProfile": [

            {

                "header": "Firewall",

                "content": "starting firewall service",

                "type": "FirewallDebug.txt",

                "pollingFrequency": "1"

            }

        ],

        "schedule": "5",

        "expires": 0,

        "telemetryProfile:name": "Permanent profile test",

        "uploadRepository:URL": "http://35.155.171.121/xconf/logupload.php",

        "uploadRepository:uploadProtocol": "HTTP"

    }

}

Client end verification (RPI)

Feature Validation (Firmware update)

Please refer below links for firmware update

XConf - Configuring Firmware Download Location

XConf - Configuring Firmware

...

...