CDRouter Support

CDRouter USP Test Summaries (Full)

test-summary version 13.3

Test Case Descriptions

  • Modules: 11
  • Test Cases: 1568

Below is a full description of the testcases in each module


usp.tcl

Extended USP functionality tests

Test Module Name Synopsis
Get Message - Integrity with USP Records usp.tcl usp_1 Get Message - Integrity with USP Records


    Test Procedure:

    1. Allow the Controller to send a Get message to the Agent.
    2. Allow the Controller and Agent to establish an E2E Session
       Context with the payload security established in the test
       setup.
    3. Allow the Agent to send a GetResp or Error message to the
       Controller within the E2e Session Context.
    4. Allow the Controller to process the GetResp or Error
       message.
    5. Repeat steps 1, 3, and 4.

    Test Metrics:

    1. The Agent and Controller are able to establish an E2E Session
       Context.
    2. The Get messages and GetResp messages are sent and received
       within the E2E Session Context.


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Integrity with USP Records - Session Re-Establishment usp.tcl usp_2 Integrity with USP Records - Session Re-Establishment


    Test Procedure:

    1. Allow the Controller to send a Get message to the Agent.
    2. Allow the Controller and Agent to establish an E2E Session
       Context with the payload security established in the test
       setup.
    3. Allow the Agent to send a GetResp or Error message to the
       Controller within the E2e Session Context.
    4. Allow the Controller to process the GetResp or Error
       message.
    5. Interrupt the connection, or cause the Controller to wait more
       than 5 seconds.
    6. Repeat steps 1, 3, and 4.

    Test Metrics:

    1. The Agent and Controller are able to establish an E2E Session
       Context.
    2. The E2E Session Context expires after 5 seconds.
    3. The E2E Session Context is re-established after expiration.
    4. The Get messages and GetResp messages are sent and received
       within the E2E Session Context.


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Get Message - Integrity at MTP Layer usp.tcl usp_3 Get Message - Integrity at MTP Layer


    Test Procedure :

    1. Allow the Controller to send a Get message to the Agent.
    2. Allow the Agent to send a GetResp or Error message to the
       Controller outside of an E2E Session Context.
    3. Allow the Controller to process the GetResp or Error
       message.

    Test Metrics:

    1. Integrity at the MTP layer is successfully established.
    2. The Get messages and GetResp or Error messages can be sent
       and received without an E2E Session Context.


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Add Message - Allow Partial True usp.tcl usp_4 Add Message - Allow Partial True


    Test Procedure:

    1. Allow the Controller to send an Add message to the Agent with
       the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: ADD
    }
    body {
        request {
            add {
                allow_partial: true
                create_objs {
                    obj_path: "<Object selected in test setup>"
                    param_settings {
                        param: "<Valid Parameter selected in test setup>"
                        value: "<Valid Value>"
                        required: false
                    }


                    obj_path: "<Object selected in test setup>"
                    param_settings {
                        param: "<Invalid Parameter>"
                        value: "<Any Value>"
                        required: true
                    }
                }
            }
        }
    }

    2. Allow the Agent to send an AddResp message to the
       Controller.

    Test Metrics:

    1. The Agent understands the Add message and creates the Object
       instances in its Instantiated Data Model.

    2. The Controller understands the AddResp and is able to learn
       the created Object(s) unique keys.


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Add Message - Allow Partial False usp.tcl usp_5 Add Message - Allow Partial False


    Test Procedure:

    1. Allow the Controller to send an Add message to the Agent with
       the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: ADD
    }
    body {
        request {
            add {
                allow_partial: false
                create_objs {
                    obj_path: "<Object selected in test setup>"
                    param_settings {
                        param: "<Valid Parameter selected in test setup>"
                        value: "<Valid Value>"
                        required: false
                    }
                    obj_path: "<Object selected in test setup>"
                    param_settings {
                        param: "<Invalid Parameter>"
                        value: "<Any Value>"
                        required: true
                    }
                }
            }
        }
    }

    2. Allow the Agent to send an Error message to the Controller.

    Test Metrics:

    1. The Agent rejects the Add message and sends an Error message.
    2. The Controller understands the Error and is able to learn which
       Objects and Parameters caused the Error.


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Set Message - Allow Partial True usp.tcl usp_6 Set Message - Allow Partial True


    Test Procedure:

    1. Allow the Controller to send a Set message to the Agent with
       the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: SET
    }
    body {
        request {
            set {
                allow_partial: true
                update_objs {
                    obj_path: "<Object selected in test setup>"
                    param_settings {
                        param: "<Valid Parameter selected in test setup>"
                        value: "<Valid Value>"
                        required: false
                    }

                    obj_path: "<Object selected in test setup>"
                    param_settings {
                        param: "<Invalid Parameter>"
                        value: "<Any Value>"
                        required: true
                    }
                }
            }
        }
    }

    2. Allow the Agent to send a SetResp message to the
       Controller.

    Test Metrics:

    1. The Agent understand the Set message and updates the Object
       parameters in its Instantiated Data Model.
    2. The Controller understands and processes the SetResp
       message.


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Set Message - Allow Partial False usp.tcl usp_7 Set Message - Allow Partial False


    Test Procedure:

    1. Allow the Controller to send a Set message to the Agent with
       the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: SET
    }
    body {
        request {
            set {
                allow_partial: false
                update_objs {
                    obj_path: "<Object selected in test setup>"
                    param_settings {
                        param: "<Valid Parameter selected in test setup>"
                        value: "<Valid Value>"
                        required: false
                    }

                    obj_path: "<Object selected in test setup>"
                    param_settings {
                        param: "<Invalid Parameter>"
                        value: "<Any Value>"
                        required: true
                    }
                }
            }
        }
    }

    2. Allow the Agent to send an SetResp message to the
       Controller.

    Test Metrics:

    1. The Agent rejects the Set message and sends an Error message.
    2. The Controller understands the Error and is able to learn which
       Parameters caused the Error.


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Set Message - Search Paths usp.tcl usp_8 Set Message - Search Paths


    Test Procedure:

    1. Allow the Controller to send a Set message to the Agent with
       the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: SET
    }
    body {
        request {
            set {
                allow_partial: <any value>
                update_objs {
                    obj_path: "<Valid Search Expression Using the Parameter selected in test setup>"
                    param_settings {
                        param: "<Valid Parameter selected in test setup>"
                        value: "<Valid Value>"
                        required: <any value>
                    }
                }
            }
        }
    }

    2. Allow the Agent to send an SetResp message to the
       Controller.

    Test Metrics:

    1. The Agent understand the Set message and updates, in its
       Instantiated Data Model, the parameter of each Object matched
       in the given Search Expression.
    2. The Controller understands and processes the SetResp.


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Delete Message - Allow Partial True usp.tcl usp_9 Delete Message - Allow Partial True


    Test Procedure:

    1. Allow the Controller to send a Delete message to the Agent with
       the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: DELETE
    }
    body {
        request {
            delete {
                allow_partial: true
                obj_paths:
                "<Deletable Object selected in test setup>"
                "<Non-Deletable Object selected in test setup>"
            }
        }
    }

    2. Allow the Agent to send a DeleteResp message to the
       Controller.

    Test Metrics:

    1. The Agent understands the Delete message and removes the Object
       instance from its Instantiated Data Model.
    2. The Controller understands and processes the DeleteResp.


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Delete Message - Allow Partial False usp.tcl usp_10 Delete Message - Allow Partial False


    Test Procedure:

    1. Allow the Controller to send a Delete message to the Agent with
       the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: DELETE
    }
    body {
        request {
            delete {
                allow_partial: true
                obj_paths:
                "<Deletable Object selected in test setup>"
                "<Non-Deletable Object selected in test setup>"
            }
        }
    }

    2. Allow the Agent to send an Error message to the Controller.

    Test Metrics:

    1. The Agent rejects the Delete message and sends an Error
       message.
    2. The Controller understands and processes the Error message and
       understands which Objects caused the error.


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Get Message - Parameter Path Only usp.tcl usp_11 Get Message - Parameter Path Only


    Test Procedure:

    1. Allow the Controller to send a Get message to the Agent with
       the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: GET
    }
    body {
        request {
            get {
                param_paths: "<First Parameter Path selected in test setup>"
                param_paths: "<Second Parameter Path selected in test setup>"
            }
        }
    }

    2. Allow the Agent to send a GetResp message to the
       Controller.

    Test Metrics:

    1. The Agent understands the Get message and sends a GetResp
       containing the requested parameters.
    2. The Controller understands and processes the Get message, and
       is able to learn the values of the requested parameters.


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Get Message - Object Paths Only usp.tcl usp_12 Get Message - Object Paths Only


    Test Procedure:

    1. Allow the Controller to send a Get message to the Agent with
       the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: GET
    }
    body {
        request {
            get {
                param_paths: "<First Object Path selected in test setup>"
                param_paths: "<Second Object Path selected in test setup>"
            }
        }
    }

    2. Allow the Agent to send a GetResp message to the
       Controller.

    Test Metrics:

    1. The Agent understands the Get message and sends a GetResp
       containing the parameters and values of the requested Objects.
    2. The Controller understands and processes the Get message, and
       is able to learn the values of the parameters in the requested
       Objects.


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Get Message - Mixed Path usp.tcl usp_13 Get Message - Mixed Path


    Test Procedure:

    1. Allow the Controller to send a Get message to the Agent with
       the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: GET
    }
    body {
        request {
            get {
                param_paths: "<Parameter Path selected in test setup>"
                param_paths: "<Object Path selected in test setup>"
            }
        }
    }

    2. Allow the Agent to send a GetResp message to the
       Controller.

    Test Metrics:

    1. The Agent understands the Get message and sends a GetResp
       containing the value of the requested Parameter and the
       parameters and values of the requested Object.

    2. The Controller understands and processes the Get message, and
       is able to learn the values of the parameters requested.


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Get Message - Search Path usp.tcl usp_14 Get Message - Search Path


    Test Procedure:

    1. Allow the Controller to send a Get message to the Agent with
       the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: GET
    }
    body {
        request {
            get {
                param_paths: "<Search Path selected in test setup>"
            }
        }
    }

    2. Allow the Agent to send a GetResp message to the
       Controller.

    Test Metrics:

    1. The Agent understands the Get message and sends a GetResp
       containing the parameters and values of the Object(s) matched
       by the Search Expression.
    2. The Controller understands and processes the Get message, and
       is able to learn the values of the parameters requested.


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Get Message - Valid and Invalid Paths usp.tcl usp_15 Get Message - Valid and Invalid Paths


    1. Allow the Controller to send a Get message to the Agent with
       the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: GET
    }
    body {
        request {
            get {
                param_paths: "<Valid Parameter Path selected in test setup>"
                param_paths: "<Valid but non-existent Parameter Path selected in test setup>"
                param_paths: Device.InvalidPath.
            }
        }
    }

    2. Allow the Agent to send a GetResp message to the
       Controller.

    Test Metrics:

    1. The Agent understands the Get message and sends a GetResp
       containing the value of the requested valid Parameter, and
       error conditions explaining the failure to retrieve the other
       paths.
    2. The Controller understands and processes the Get message, is
       able to learn the values of the parameters requested, and
       process the paths that were in error.


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
GetInstances - First Level = False usp.tcl usp_16 GetInstances - First Level = False


    Test Procedure:

    1. Allow the Controller to send a GetInstances message to the
       Agent with the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: GET_INSTANCES
    }
    body {
        request {
            GetInstances {
                obj_paths : <Object selected in test setup>
                bool first_level_only : false
            }
        }
    }

    2. Allow the Agent to send a GetInstancesResp message to the
       Controller.

    Test Metrics:

    1. The Agent understands the GetInstances message and sends a
       GetInstancesResp containing the Instance Identifiers and
       unique keys of Object Instances in the Agent's Instantiated
       Data Model from the specified Object and all multi-instance
       child objects.
    2. The Controller understands and processes the GetInstances
       message, and is able to learn the Instance Identifiers and
       unique keys.


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
GetInstances - First Level = True usp.tcl usp_17 GetInstances - First Level = True


    Test Procedure:

    1. Allow the Controller to send a GetInstances message to the
       Agent with the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: GET_INSTANCES
    }
    body {
        request {
            GetInstances {
                obj_paths : <Object selected in test setup>
                bool first_level_only : true
            }
        }
    }

    2. Allow the Agent to send a GetInstancesResp message to the
       Controller.

    Test Metrics:

    1. The Agent understands the GetInstances message and sends a
       GetInstancesResp containing the Instance Identifiers and
       unique keys of Object Instances in the Agent's Instantiated
       Data Model, with no information about child objects.
    2. The Controller understands and processes the GetInstances
       message, and is able to learn the Instance Identifiers and
       unique keys.


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
GetSupportedDM - All Objects Only usp.tcl usp_18 GetSupportedDM - All Objects Only


    Test Procedure:

    1. Allow the Controller to send a GetSupportedDM message to the
       Agent with the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: GET_SUPPORTED_DM
    }
    body {
        request {
            GetSupportedDM {
                obj_paths {
                    obj_path : Device.
                }
                first_level_only : false
                return_commands : false
                return_events : false
                return_params : false
            }
        }
    }

    2. Allow the Agent to send a GetSupportedDMResp message to the
       Controller.

    Test Metrics:

    1. The Agent understands the GetSupportedDM message and sends a
       GetSupportedDMResp containing the Objects that it supports
       in its Supported Data Model.
    2. The Controller understands and processes the GetSupportedDM
       message, and is able learn the supported Objects.


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
GetSupportedDM - All Info, Single Object usp.tcl usp_19 GetSupportedDM - All Info, Single Object


    Test Procedure:

    1. Allow the Controller to send a GetSupportedDM message to the
       Agent with the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: GET_SUPPORTED_DM
    }
    body {
        request {
            GetSupportedDM {
                obj_paths {
                    obj_path : <Object selected in test setup>
                }
                first_level_only : true
                return_commands : true
                return_events : true
                return_params : true
            }
        }
    }

    2. Allow the Agent to send a GetSupportedDMResp message to the
       Controller.

    Test Metrics:

    1. The Agent understands the GetSupportedDM message and sends a
       GetSupportedDMResp containing the supported Object and its
       parameters, commands, and events.
    2. The Controller understands and processes the GetSupportedDM
       message, and is able learn the information about the supported
       Object.


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
GetSupportedDM - All Info usp.tcl usp_20 GetSupportedDM - All Info


    Test Procedure:

    1. Allow the Controller to send a GetSupportedDM message to the
       Agent with the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: GET_SUPPORTED_DM
    }
    body {
        request {
            GetSupportedDM {
                obj_paths {
                    obj_path : Device.
                }
                first_level_only : false
                return_commands : true
                return_events : true
                return_params : true
            }
        }
    }

    2. Allow the Agent to send a GetSupportedDMResp message to the
       Controller.

    Test Metrics:

    1. The Agent understands the GetSupportedDM message and sends a
       GetSupportedDMResp containing its entire Supported Data
       Model.
    2. The Controller understands and processes the GetSupportedDM
       message, and is able learn the Agent's entire Supported Data
       Model.


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Notification - Subscription Creation Using ValueChange usp.tcl usp_21 Notification - Subscription Creation Using ValueChange


    Purpose:

    The purpose of this test is to demonstrate that the Controller can
    subscribe to a notification on the Agent using the
    Device.LocalAgent.Subscription.{i} table.

    Test Steps:

    1. Allow the Controller to send an Add message to the Agent with
       the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: ADD
    }
    body {
        request {
            add {
                allow_partial: false
                create_objs {
                    obj_path: "Device.LocalAgent.Subscription."
                    param_settings {

                        {
                            param: "Enable"
                            value: "true"
                            required: true
                        }
                        {
                            param: "Recipient"
                            value: "Device.LocalAgent.Controller.<instance number of participating Controller>"
                            required: true
                        }
                        {
                            param: "ID"
                            value: "<subscription ID determined by the Controller>"
                            required: true
                        }
                        {
                            param: "NotifType"
                            value: "ValueChange"
                            required: true
                        }
                        {
                            param: "ReferenceList"
                            value: "<parameter selected during test setup>"
                            required: true
                        }
                    }
                }
            }
        }
    }

    2. Allow the Agent to send an AddResp message, and allow the
       Controller to process the response and learn the instance
       number of the created Subscription object.
    3. Alter the value of the parameter chosen during test setup.
    4. Allow the Agent to send a Notify message to the Controller with
       the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: NOTIFY
    }
    body {
        request {
            notify {
                subscription_id: "<subscription_id>"
                send_resp: true
                value_change {
                    param_path: "<parameter selected during test setup>"
                    param_value: "<new value of the parameter selected during test setup>"
                }
            }
        }
    }

    5. Allow the Controller to process the Request and send a
       NotifyResp message to the Agent.

    Test Metrics:

    1. The Controller is able to subscribe to the ValueChange event on
       the Agent.
    2. The Controller is able to learn about the changed value of the
       parameter.


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Notification - Subscription Disable Using ValueChange usp.tcl usp_22 Notification - Subscription Disable Using ValueChange


    Purpose:

    The purpose of this test is to demonstrate that the Controller can
    disable a notification on the Agent by disabling the associated
    object in the Device.LocalAgent.Subscription. table.

    Test Procedure:

    1. Allow the Controller to send a Set message to the Agent with
       the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: SET
    }
    body {
        request {
            set {
                allow_partial: false
                update_objs {
                    obj_path: "Device.LocalAgent.Subscription.<instance identifier of subscription object>."
                    param_settings {
                        param: "Enable"
                        value: "false"
                        required: true
                    }
                }
            }
        }
    }

    2. Allow the Agent to send a SetResp to the Controller.
    3. Alter the value of the parameter chosen during test setup of
       the test Subscription Creation Using ValueChange.

    Test Metrics:

    1. The Controller is able to disable the Subscription object on
       the Agent.
    2. No Notify message is sent when the parameter is altered.


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Notification - Subscription Deletion Using ValueChange usp.tcl usp_23 Notification - Subscription Deletion Using ValueChange


    Purpose:

    The purpose of this test is to demonstrate that the Controller can
    disable a notification on the Agent by deleting the associated
    object in the Device.LocalAgent.Subscription. table.

    Test Setup:

    1. Allow the Controller to send a Delete message to the Agent with
       the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: DELETE
    }
    body {
        request {
            delete {
                allow_partial: false
                obj_paths {
                    "Device.LocalAgent.Subscription.<instance identifier of subscription object>."
                }
            }
        }
    }

    2. Allow the Agent to send a DeleteResp to the Controller.
    3. Alter the value of the parameter chosen during test setup of
       the test Subscription Creation Using ValueChange.

    Test Metrics:

    1. The Controller is able to delete the Subscription object on the
       Agent.
    2. No Notify message is sent when the parameter is altered.


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Notification - Object Creation usp.tcl usp_24 Notification - Object Creation


    Purpose:

    The purpose of this test is to demonstrate that the Controller can
    enable Notification for the creation of new object instances of a
    given object.

    Test Steps:

    1. Allow the Controller to send an Add message to the Agent with
       the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: ADD
    }
    body {
        request {
            add {
                allow_partial: false
                create_objs {
                    obj_path: "Device.LocalAgent.Subscription."
                    param_settings {

                        {
                            param: "Enable"
                            value: "true"
                            required: true
                        }
                        {
                            param: "Recipient"
                            value: "Device.LocalAgent.Controller.<instance number of participating Controller>"
                            required: true
                        }
                        {
                            param: "ID"
                            value: "<subscription ID determined by the Controller>"
                            required: true
                        }
                        {
                            param: "NotifType"
                            value: "ObjectCreation"
                            required: true
                        }
                        {
                            param: "ReferenceList"
                            value: "<object selected during test setup>"
                            required: true
                        }
                    }
                }
            }
        }
    }

    2. Allow the Agent to send an AddResp to the Controller.
    3. Initiate the creation of an instance of the Object selected
       during test setup.
    4. Allow the Agent to send a Notify message to the Controller with
       the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: NOTIFY
    }
    body {
        request {
            notify {
                subscription_id: "<subscription_id>"
                send_resp: true
                obj_creation {
                    obj_path: "<path to created object using instance number addressing>"
                    unqiue keys {
                        key: <one of one or more unique keys>
                        value: <value of the unique key>
                    }
                }
            }
        }
    }

    5. Allow the Controller to send a NotifyResp message to the
       Agent.

    Test Metrics:

    1. The Controller is able to subscribe to the ObjectCreation event
       on the Agent.
    2. The Controller is able to learn about the new Object Instance.


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Notification - Object Deletion usp.tcl usp_25 Notification - Object Deletion


    Purpose:

    The purpose of this test is to demonstrate that the Controller can
    enable Notification for the removal or expiration of new object
    instances of a given object.

    Test Steps:

    1. Allow the Controller to send an Add message to the Agent with
       the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: ADD
    }
    body {
        request {
            add {
                allow_partial: false
                create_objs {
                    obj_path: "Device.LocalAgent.Subscription."
                    param_settings {

                        {
                            param: "Enable"
                            value: "true"
                            required: true
                        }
                        {
                            param: "Recipient"
                            value: "Device.LocalAgent.Controller.<instance number of participating Controller>"
                            required: true
                        }
                        {
                            param: "ID"
                            value: "<subscription ID determined by the Controller>"
                            required: true
                        }
                        {
                            param: "NotifType"
                            value: "ObjectDeletion"
                            required: true
                        }
                        {
                            param: "ReferenceList"
                            value: "<object selected during test setup>"
                            required: true
                        }
                    }
                }
            }
        }
    }

    2. Allow the Agent to send an AddResp to the Controller.
    3. Initiate the removal of an instance of the Object selected
       during test setup.
    4. Allow the Agent to send a Notify message to the Controller with
       the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: NOTIFY
    }
    body {
        request {
            notify {
                subscription_id: "<subscription_id>"
                send_resp: true
                obj_deletion {
                    obj_path: "<path to deleted object using instance number addressing>"
                }
            }
        }
    }

    5. Allow the Controller to send a NotifyResp message to the
       Agent.

    Test Metrics:

    1. The Controller is able to subscribe to the ObjectDeletion event
       on the Agent.
    2. The Controller is able to learn about the removed Object
       Instance.


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Notification - OnBoardRequest usp.tcl usp_26 Notification - OnBoardRequest


    Purpose:

    The purpose of this test is to demonstrate that the Controller can
    receive an OnBoardRequest notification when triggered on the Agent
    via the SendOnBoardRequest() Operation.

    Test Procedure:

    1. Allow the Controller to send an Operate message to the Agent
       with the following minimum structure:

    Operate Request:
    header {
        msg_id: "<msg_id>"
        msg_type: OPERATE
    }
    body {
        request {
            operate {
                command: "Device.LocalAgent.Controller.<instance identifier of participating controller>.SendOnBoardRequest()"
                command_key: "onboard_command_key"
            }
        }
    }

    Note:

    The use of send_resp has been omitted here, as it is not the focus
    of the test case.  If the participants wish to have the Operate
    request confirmed by the Agent they are free to do so by setting
    send_resp to true, in which case, the Agent will send an
    OperateResp to the Controller.

    2. Allow the Agent to send a Notify message to the Controller with
       the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: NOTIFY
    }
    body {
        request {
            notify {
                subscription_id: "<subscription_id>"
                send_resp: true
                on_board_req {
                    oui: "<oui of the Agent>"
                    product_class: "<product class string, if any>"
                    serial_number: "<serial number of the Agent, if any>"
                    agent_supported_protocol_version: "1.0"
                }
            }
        }
    }

    3. Allow the Controller to send a NotifyResp to the Agent.

    Test Metrics:

    1. The Controller is able to trigger an OnBoardRequest event on
       the Agent.
    2. The Controller receives and understands the OnBoardRequest
       event.


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Notification - Notification Retry usp.tcl usp_27 Notification - Notification Retry


    Purpose:

    The purpose of this test is to demonstrate that the Controller and
    Agent can recover from a lost notification when the NotifRetry
    parameter in the Subscription object is set to true.

    Test Procedure:

    1. Allow the Controller to send an Add message to the Agent with
       the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: ADD
    }
    body {
        request {
            add {
                allow_partial: false
                create_objs {
                    obj_path: "Device.LocalAgent.Subscription."
                    param_settings {

                        {
                            param: "Enable"
                            value: "true"
                            required: true
                        }
                        {
                            param: "Recipient"
                            value: "Device.LocalAgent.Controller.<instance number of participating Controller>"
                            required: true
                        }
                        {
                            param: "ID"
                            value: "<subscription ID determined by the Controller>"
                            required: true
                        }
                        {
                            param: "NotifType"
                            value: "ValueChange"
                            required: true
                        }
                        {
                            param: "ReferenceList"
                            value: "<parameter selected during test setup>"
                            required: true
                        }
                        {
                            param: "NotifRetry"
                            value: "true"
                            required: true
                        }
                    }
                }
            }
        }
    }

    2. Allow the Agent to send an AddResp message, and allow the
       Controller to process the response and learn the instance
       number of the created Subscription object.
    3. Alter the value of the parameter chosen during test setup.
    4. Allow the Agent to send a Notify message to the Controller with
       the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: NOTIFY
    }
    body {
        request {
            notify {
                subscription_id: "<subscription_id>"
                send_resp: true
                value_change {
                    param_path: "<parameter selected during test setup>"
                    param_value: "<new value of the parameter selected during test setup>"
                }
            }
        }
    }

    5. Prevent the delivery of the NotifyResp from the Controller
       by either causing it to not be emitted, or by interrupting the
       connection between the Controller and the Agent.
    6. Allow the Agent to engage in the Notification Retry algorithm
       using the default values for 30 seconds.
    7. Allow the Controller to successfully send a NotifyResp to
       the Agent.

    Test Metrics:

    1. The Agent retries the Notify message in accordance with the
       retry algorithm specified in the "Responses to Notifications
       and Notification Retry" section of TR-369.
    2. The Controller receives the Notification after it has been
       retried.
    3. The Agent stops sending the Notify message after it has been
       acknowledged.


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Notifications - Subscription Expiration usp.tcl usp_28 Notifications - Subscription Expiration


    Purpose:

    The purpose of this test is to demonstrate that the Controller can
    set a Subscription to expire using the TimeToLive parameter in the
    Subscription object.

    Test Procedure:

    1. Allow the Controller to send an Add message to the Agent with
       the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: ADD
    }
    body {
        request {
            add {
                allow_partial: false
                create_objs {
                    obj_path: "Device.LocalAgent.Subscription."
                    param_settings {

                        {
                            param: "Enable"
                            value: "true"
                            required: true
                        }
                        {
                            param: "Recipient"
                            value: "Device.LocalAgent.Controller.<instance number of participating Controller>"
                            required: true
                        }
                        {
                            param: "ID"
                            value: "<subscription ID determined by the Controller>"
                            required: true
                        }
                        {
                            param: "NotifType"
                            value: "ValueChange"
                            required: true
                        }
                        {
                            param: "ReferenceList"
                            value: "<parameter selected during test setup>"
                            required: true
                        }
                        {
                            param: "TimeToLive"
                            value: "60"
                            required: true
                        }
                    }
                }
            }
        }
    }

    2. Allow the Agent to send an AddResp message, and allow the
       Controller to process the response and learn the instance
       number of the created Subscription object.
    3. Within 30 seconds, alter the value of the parameter chosen
       during test setup.
    4. Allow the Agent to send a Notify message to the Controller with
       the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: NOTIFY
    }
    body {
        request {
            notify {
                subscription_id: "<subscription_id>"
                send_resp: true
                value_change {
                    param_path: "<parameter selected during test setup>"
                    param_value: "<new value of the parameter selected during test setup>"
                }
            }
        }
    }

    5. Allow the Controller to process the Request and send a
       NotifyResp message to the Agent.
    6. Allow the TimeToLive time to expire (60 seconds).
    7. Alter the value of the parameter chosen during test setup.
    8. Allow the Controller to send a GetInstances message to the
       Agent with the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: GET_INSTANCES
    }
    body {
        request {
            GetInstances {
                obj_paths : "Device.LocalAgent.Subscription."
                bool first_level_only : true
            }
        }
    }

    9. Allow the Agent to send a GetInstancesResp to the
       Controller.

    Test Metrics:

    1. No Notify message is sent after the TimeToLive has expired.
    2. The Subscription Object Instance has been removed from the
       Agent's Instantiated Data Model.


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Operations - Synchronous Operation Test Using Device.Reboot() usp.tcl usp_29 Operations - Synchronous Operation Test Using Device.Reboot()


    Purpose:

    The purpose of this test is to exercise the Controller and Agent
    abilities to handle synchronous operations initiated using the
    Operate message. The Device.Boot! event is exercised in the
    process.

    Test Steps:

    1. If there are no entries in the
       Device.LocalAgent.Controller.<instance id of
       controller>.BootParameter. table: a. Allow the Controller to
       send an Add message to the Agent with the following minimum
       structure:

    header {
        msg_id: "<msg_id>"
        msg_type: ADD
    }
    body {
        request {
            add {
                allow_partial: false
                create_objs {
                    obj_path: "Device.LocalAgent.Controller.<instance id of participating controller>.BootParameter."
                    param_settings {
                        {
                            param: "Enable"
                            value: "true"
                            required: true
                        }
                        {
                            param: "ParameterName"
                            value: "Device.DeviceInfo.SoftwareVersion"
                            required: true
                        }
                    }
                }
            }
        }
    }

       b. Allow the Agent to send an AddResp message to the
       Controller.

    2. If the Controller does not currently have a subscription to the
       Device.LocalAgent.Boot! event on the Agent: i. Allow the
       Controller to send an Add message to the Agent with the
       following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: ADD
    }
    body {
        request {
            add {
                allow_partial: false
                create_objs {
                    obj_path: "Device.LocalAgent.Subscription."
                    param_settings {

                        {
                            param: "Enable"
                            value: "true"
                            required: true
                        }
                        {
                            param: "Recipient"
                            value: "Device.LocalAgent.Controller.<instance number of participating Controller>"
                            required: true
                        }
                        {
                            param: "ID"
                            value: "boot-1"
                            required: true
                        }
                        {
                            param: "NotifType"
                            value: "Event"
                            required: true
                        }
                        {
                            param: "ReferenceList"
                            value: "Device.Boot!"
                            required: true
                        }
                    }
                }
            }
        }
    }

    3. Allow the Controller to send an Operate message to the Agent
       with the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: OPERATE
    }
    body {
        request {
            operate {
                command: "Device.Reboot()"
                command_key: "reboot_command_key"
                send_resp: true
            }
        }
    }

    4. Allow the Agent to send an OperateResp to the Controller.
    5. Allow the Agent to restart.
    6. Allow the Agent to send a Notify message to the Controller with
       the following minimum structure :

    header {
        msg_id: "<msg_id>"
        msg_type: NOTIFY
    }
    body {
        request {
            notify {
                subscription_id: "<subscription id>"
                send_resp: true
                event {
                    obj_path: "Device.LocalAgent."
                    event_name: "Boot!"
                    params {
                        {
                            key: "Cause"
                            value: "RemoteReboot"}
                        {
                            key: "CommandKey"
                            value: "reboot_command_key"}
                        {
                            key: "ParameterMap"
                            value: "{"Device.DeviceInfo.SoftwareVersion":"<software version>"}"
                        }
                    }
                }
            }
        }
    }

    7. Allow the Controller to send a NotifyResp message to the
       Agent.

    Test Metrics:

    1. The Controller is able to initiate the Reboot operation on the
       Agent.
    2. The Agent reboots.
    3. The Controller receives and process the Boot! event from the
       Agent.


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Operations - Asynchronous Operation Test Using Device.Firmware.Download() usp.tcl usp_30 Operations - Asynchronous Operation Test Using Device.Firmware.Download()


    Purpose:

    The purpose of this test is to exercise the Controller and Agent
    abilities to handle asynchronous operations initiated using the
    Operate message. The ability of the Controller to do a managed
    firmware upgrade through the Agent is exercised in the process.

    Test Procedure:

    1. If the Controller does not currently have a subscription to the
       Device.LocalAgent.TransferComplete! event assigned in the
       Agent, allow the Controller to send an Add message to the Agent
       with the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: ADD
    }
    body {
        request {
            add {
                allow_partial: false
                create_objs {
                    obj_path: "Device.LocalAgent.Subscription."
                    param_settings {

                        {
                            param: "Enable"
                            value: "true"
                            required: true
                        }
                        {
                            param: "Recipient"
                            value: "Device.LocalAgent.Controller.<instance number of participating Controller>"
                            required: true
                        }
                        {
                            param: "ID"
                            value: "<subscription ID determined by the Controller>"
                            required: true
                        }
                        {
                            param: "NotifType"
                            value: "Event"
                            required: true
                        }
                        {
                            param: "ReferenceList"
                            value: "Device.LocalAgent.TransferComplete!"
                            required: true
                        }
                    }
                }
            }
        }
    }

    2. Allow the Agent to send an AddResp message to the
       Controller.
    3. Allow the Controller to send an Operate message to the Agent
       with the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: OPERATE
    }
    body {
        request {
            operate {
                command: "Device.LocalAgent.Firmware.<instance id of non-active firmware bank>.Download()"
                command_key: "download_command_key"
                send_resp: true
                input_args {
                    {
                        key: "URL"
                        value: "<URL of the firmware determined in test setup>"}
                    {
                        key: "Username"
                        value: ""}
                    {
                        key: "Password"
                        value: ""}
                }
            }
        }
    }

    4. Allow the Agent to create an instance of the
       Device.LocalAgent.Request. object.
    5. Allow the Agent to send an OperateResp with the following
       minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: OPERATE_RESP
    }
    body {
        request {
            operate_resp {
                operation_results {
                    executed_command: "Device.LocalAgent.Firmware.<instance number of the Firmware object>.Download()"
                    req_object_path: "Device.LocalAgent.Request.<instance number of the Request object>."
                }
            }
        }
    }

    6. Allow the system modeled by the Agent to download the file.
    7. Allow the Agent to send a Notify message to the Controller with
       the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: NOTIFY
    }
    body {
        request {
            notify {
                subscription_id: "<subscription id>"
                send_resp: true
                event {
                    obj_path: "Device.LocalAgent."
                    event_name: "TransferComplete!"
                    params {
                        {
                            key: "Cause"
                            value: "Device.LocalAgent.Firmware.<instance number of the Firmware object>.Download()"}
                        {
                            key: "CommandKey"
                            value: "download_command_key"}
                        {
                            key: "Requestor"
                            value: "<Endpoint ID of the Controller>"}
                        {
                            key: "TransferType"
                            value: "Download"}
                        {
                            key: "Affected"
                            value: "Device.LocalAgent.Firmware.<instance number of the Firmware object>."}
                        {
                            key: "TransferURL"
                            value: "<URL of the firmware determined in test setup>"}
                        {
                            key: "StartTime"
                            value: "<time the download was started>"}
                        {
                            key: "CompleteTime"
                            value: "<time the download was completed>"}
                    }
                }
            }
        }
    }

    8. Allow the Controller to send a NotifyResp to the Agent.
    9. Allow the Controller to send an Operate message to the Agent
       with the following minimum structure:

    header {
        msg_id: "<msg_id>"
        msg_type: OPERATE
    }
    body {
        request {
            operate {
                command: "Device.LocalAgent.Firmware.<instance id of non-active firmware bank>.Activate()"
                command_key: "activate_command_key"
                send_resp: true
            }
        }
    }

    10. Allow the Agent to send an OperateResp message to the
        Controller.
    11. Allow the Agent to create an instance of the
        Device.LocalAgent.Request. object.
    12. Allow the Agent to complete the firmware activation.

    Test Metrics:

    1. The Controller is able to manipulate the Agent to download the
       new firmware.
    2. The Controller is able to activate the new firmware on the
       Agent.


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/


usp_annex_a.tcl

USP Tests for Annex A Bulk Data Collection

Test Module Name Synopsis
Verify bulk data transfer (single parameter) via HTTP POSTs and ParameterPerRow CSV encoding usp_annex_a.tcl usp_annex_a_1 Verify bulk data transfer (single parameter) via HTTP POSTs and ParameterPerRow CSV encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTP
            using POSTs and encode the data using ParameterPerRow CSV
    step 2. Ensure the EUT sends a POST to the HTTP host using CSV encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (single parameter) via HTTP POSTs and ObjectHierarchy JSON encoding usp_annex_a.tcl usp_annex_a_2 Verify bulk data transfer (single parameter) via HTTP POSTs and ObjectHierarchy JSON encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTP
            using POSTs and encode the data using ObjectHierarchy JSON
    step 2. Ensure the EUT sends a POST to the HTTP host using JSON encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (multiple parameters) via HTTP POSTs and ParameterPerRow CSV encoding usp_annex_a.tcl usp_annex_a_3 Verify bulk data transfer (multiple parameters) via HTTP POSTs and ParameterPerRow CSV encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTP
            using POSTs and encode the data using ParameterPerRow CSV
    step 2. Ensure the EUT sends a POST to the HTTP host using CSV encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (multiple parameters) via HTTP POSTs and ObjectHierarchy JSON encoding usp_annex_a.tcl usp_annex_a_4 Verify bulk data transfer (multiple parameters) via HTTP POSTs and ObjectHierarchy JSON encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTP
            using POSTs and encode the data using ObjectHierarchy JSON
    step 2. Ensure the EUT sends a POST to the HTTP host using JSON encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (single parameter) via HTTP POSTs and ParameterPerColumn CSV encoding usp_annex_a.tcl usp_annex_a_5 Verify bulk data transfer (single parameter) via HTTP POSTs and ParameterPerColumn CSV encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTP
            using POSTs and encode the data using ParameterPerColumn CSV
    step 2. Ensure the EUT sends a POST to the HTTP host using CSV encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (single parameter) via HTTP POSTs and NameValuePair JSON encoding usp_annex_a.tcl usp_annex_a_6 Verify bulk data transfer (single parameter) via HTTP POSTs and NameValuePair JSON encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTP
            using POSTs and encode the data using NameValuePair JSON
    step 2. Ensure the EUT sends a POST to the HTTP host using JSON encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (multiple parameters) via HTTP POSTs and ParameterPerColumn CSV encoding usp_annex_a.tcl usp_annex_a_7 Verify bulk data transfer (multiple parameters) via HTTP POSTs and ParameterPerColumn CSV encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTP
            using POSTs and encode the data using ParameterPerColumn CSV
    step 2. Ensure the EUT sends a POST to the HTTP host using CSV encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (multiple parameters) via HTTP POSTs and NameValuePair JSON encoding usp_annex_a.tcl usp_annex_a_8 Verify bulk data transfer (multiple parameters) via HTTP POSTs and NameValuePair JSON encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTP
            using POSTs and encode the data using NameValuePair JSON
    step 2. Ensure the EUT sends a POST to the HTTP host using JSON encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (single parameter) via HTTPS POSTs and ParameterPerRow CSV encoding usp_annex_a.tcl usp_annex_a_10 Verify bulk data transfer (single parameter) via HTTPS POSTs and ParameterPerRow CSV encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTPS
            using POSTs and encode the data using ParameterPerRow CSV
    step 2. Ensure the EUT sends a POST to the HTTPS host using CSV encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (single parameter) via HTTPS POSTs and ObjectHierarchy JSON encoding usp_annex_a.tcl usp_annex_a_11 Verify bulk data transfer (single parameter) via HTTPS POSTs and ObjectHierarchy JSON encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTPS
            using POSTs and encode the data using ObjectHierarchy JSON
    step 2. Ensure the EUT sends a POST to the HTTP host using JSON encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (multiple parameters) via HTTPS POSTs and ParameterPerRow CSV encoding usp_annex_a.tcl usp_annex_a_12 Verify bulk data transfer (multiple parameters) via HTTPS POSTs and ParameterPerRow CSV encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTPS
            using POSTs and encode the data using ParameterPerRow CSV
    step 2. Ensure the EUT sends a POST to the HTTP host using CSV encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (multiple parameters) via HTTPS POSTs and ObjectHierarchy JSON encoding usp_annex_a.tcl usp_annex_a_13 Verify bulk data transfer (multiple parameters) via HTTPS POSTs and ObjectHierarchy JSON encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTPS
            using POSTs and encode the data using ObjectHierarchy JSON
    step 2. Ensure the EUT sends a POST to the HTTP host using JSON encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (single parameter) via HTTPS POSTs and ParameterPerColumn CSV encoding usp_annex_a.tcl usp_annex_a_14 Verify bulk data transfer (single parameter) via HTTPS POSTs and ParameterPerColumn CSV encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTPS
            using POSTs and encode the data using ParameterPerColumn CSV
    step 2. Ensure the EUT sends a POST to the HTTP host using CSV encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (single parameter) via HTTPS POSTs and NameValuePair JSON encoding usp_annex_a.tcl usp_annex_a_15 Verify bulk data transfer (single parameter) via HTTPS POSTs and NameValuePair JSON encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTP
            using POSTs and encode the data using NameValuePair JSON
    step 2. Ensure the EUT sends a POST to the HTTP host using JSON encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (multiple parameters) via HTTPS POSTs and ParameterPerColumn CSV encoding usp_annex_a.tcl usp_annex_a_16 Verify bulk data transfer (multiple parameters) via HTTPS POSTs and ParameterPerColumn CSV encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTPS
            using POSTs and encode the data using ParameterPerColumn CSV
    step 2. Ensure the EUT sends a POST to the HTTP host using CSV encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (multiple parameters) via HTTPS POSTs and NameValuePair JSON encoding usp_annex_a.tcl usp_annex_a_17 Verify bulk data transfer (multiple parameters) via HTTPS POSTs and NameValuePair JSON encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTPS
            using POSTs and encode the data using NameValuePair JSON
    step 2. Ensure the EUT sends a POST to the HTTP host using JSON encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (single parameter) via HTTP POSTs and ParameterPerRow CSV encoding with URI parameters usp_annex_a.tcl usp_annex_a_20 Verify bulk data transfer (single parameter) via HTTP POSTs and ParameterPerRow CSV encoding with URI parameters


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTP
            using POSTs and encode the data using ParameterPerRow CSV, and URI parameters
    step 2. Ensure the EUT sends a POST to the HTTP host using CSV encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (single parameter) via HTTP POSTs and ObjectHierarchy JSON encoding with URI paramaters usp_annex_a.tcl usp_annex_a_21 Verify bulk data transfer (single parameter) via HTTP POSTs and ObjectHierarchy JSON encoding with URI paramaters


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTP
            using POSTs and encode the data using ObjectHierarchy JSON, and URI parameters
    step 2. Ensure the EUT sends a POST to the HTTP host using JSON encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (multiple parameters) via HTTP POSTs and ParameterPerRow CSV encoding with URI parameters usp_annex_a.tcl usp_annex_a_22 Verify bulk data transfer (multiple parameters) via HTTP POSTs and ParameterPerRow CSV encoding with URI parameters


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTP
            using POSTs and encode the data using ParameterPerRow CSV, and URI parameters
    step 2. Ensure the EUT sends a POST to the HTTP host using CSV encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (multiple parameters) via HTTP POSTs and ObjectHierarchy JSON encoding with URI parameters usp_annex_a.tcl usp_annex_a_23 Verify bulk data transfer (multiple parameters) via HTTP POSTs and ObjectHierarchy JSON encoding with URI parameters


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTP
            using POSTs and encode the data using ObjectHierarchy JSON, and URI parameters
    step 2. Ensure the EUT sends a POST to the HTTP host using JSON encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (single parameter) via HTTP POSTs and ParameterPerColumn CSV encoding with URI parameters usp_annex_a.tcl usp_annex_a_24 Verify bulk data transfer (single parameter) via HTTP POSTs and ParameterPerColumn CSV encoding with URI parameters


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTP
            using POSTs and encode the data using ParameterPerColumn CSV, and URI parameters
    step 2. Ensure the EUT sends a POST to the HTTP host using CSV encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (single parameter) via HTTP POSTs and NameValuePair JSON encoding with URI paramaters usp_annex_a.tcl usp_annex_a_25 Verify bulk data transfer (single parameter) via HTTP POSTs and NameValuePair JSON encoding with URI paramaters


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTP
            using POSTs and encode the data using NameValuePair JSON, and URI parameters
    step 2. Ensure the EUT sends a POST to the HTTP host using JSON encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (multiple parameters) via HTTP POSTs and ParameterPerColumn CSV encoding with URI parameters usp_annex_a.tcl usp_annex_a_26 Verify bulk data transfer (multiple parameters) via HTTP POSTs and ParameterPerColumn CSV encoding with URI parameters


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTP
            using POSTs and encode the data using ParameterPerColumn CSV, and URI parameters
    step 2. Ensure the EUT sends a POST to the HTTP host using CSV encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (multiple parameters) via HTTP POSTs and NameValuePair JSON encoding with URI parameters usp_annex_a.tcl usp_annex_a_27 Verify bulk data transfer (multiple parameters) via HTTP POSTs and NameValuePair JSON encoding with URI parameters


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTP
            using POSTs and encode the data using NameValuePair JSON, and URI parameters
    step 2. Ensure the EUT sends a POST to the HTTP host using JSON encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (single parameter) via HTTPS POSTs and ParameterPerRow CSV encoding with URI parameters usp_annex_a.tcl usp_annex_a_30 Verify bulk data transfer (single parameter) via HTTPS POSTs and ParameterPerRow CSV encoding with URI parameters


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTPS
            using POSTs and encode the data using ParameterPerRow CSV, and URI parameters
    step 2. Ensure the EUT sends a POST to the HTTP host using CSV encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (single parameter) via HTTPS POSTs and ObjectHierarchy JSON encoding with URI parameters usp_annex_a.tcl usp_annex_a_31 Verify bulk data transfer (single parameter) via HTTPS POSTs and ObjectHierarchy JSON encoding with URI parameters


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTPS
            using POSTs and encode the data using ObjectHierarchy JSON, and URI parameters
    step 2. Ensure the EUT sends a POST to the HTTP host using JSON encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (multiple parameters) via HTTPS POSTs and ParameterPerRow CSV encoding with URI parameters usp_annex_a.tcl usp_annex_a_32 Verify bulk data transfer (multiple parameters) via HTTPS POSTs and ParameterPerRow CSV encoding with URI parameters


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTPS
            using POSTs and encode the data using ParameterPerRow CSV, and URI parameters
    step 2. Ensure the EUT sends a POST to the HTTP host using CSV encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (multiple parameters) via HTTPS POSTs and ObjectHierarchy JSON encoding with URI parameters usp_annex_a.tcl usp_annex_a_33 Verify bulk data transfer (multiple parameters) via HTTPS POSTs and ObjectHierarchy JSON encoding with URI parameters


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTPS
            using POSTs and encode the data using ObjectHierarchy JSON, and URI parameters
    step 2. Ensure the EUT sends a POST to the HTTP host using JSON encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (single parameter) via HTTPS POSTs and ParameterPerColumn CSV encoding with URI parameters usp_annex_a.tcl usp_annex_a_34 Verify bulk data transfer (single parameter) via HTTPS POSTs and ParameterPerColumn CSV encoding with URI parameters


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTPS
            using POSTs and encode the data using ParameterPerColumn CSV, and URI parameters
    step 2. Ensure the EUT sends a POST to the HTTP host using CSV encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (single parameter) via HTTPS POSTs and NameValuePair JSON encoding with URI parameters usp_annex_a.tcl usp_annex_a_35 Verify bulk data transfer (single parameter) via HTTPS POSTs and NameValuePair JSON encoding with URI parameters


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTPS
            using POSTs and encode the data using NameValuePair JSON, and URI parameters
    step 2. Ensure the EUT sends a POST to the HTTP host using JSON encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (multiple parameters) via HTTPS POSTs and ParameterPerColumn CSV encoding with URI parameters usp_annex_a.tcl usp_annex_a_36 Verify bulk data transfer (multiple parameters) via HTTPS POSTs and ParameterPerColumn CSV encoding with URI parameters


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTPS
            using POSTs and encode the data using ParameterPerColumn CSV, and URI parameters
    step 2. Ensure the EUT sends a POST to the HTTP host using CSV encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (multiple parameters) via HTTPS POSTs and NameValuePair JSON encoding with URI parameters usp_annex_a.tcl usp_annex_a_37 Verify bulk data transfer (multiple parameters) via HTTPS POSTs and NameValuePair JSON encoding with URI parameters


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTPS
            using POSTs and encode the data using NameValuePair JSON, and URI parameters
    step 2. Ensure the EUT sends a POST to the HTTP host using JSON encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (single parameter) via USPEventNotif and ParameterPerRow CSV encoding usp_annex_a.tcl usp_annex_a_40 Verify bulk data transfer (single parameter) via USPEventNotif and ParameterPerRow CSV encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via USP
            usings and encode the data using ParameterPerRow CSV
    step 2. Ensure the EUT sends a Push! event using CSV encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (single parameter) via USPEventNotif and ObjectHierarchy JSON encoding usp_annex_a.tcl usp_annex_a_41 Verify bulk data transfer (single parameter) via USPEventNotif and ObjectHierarchy JSON encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via USP
            usings and encode the data using ObjectHierarchy JSON
    step 2. Ensure the EUT sends a Push! event using JSON encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (multiple parameters) via USPEventNotif and ParameterPerRow CSV encoding usp_annex_a.tcl usp_annex_a_42 Verify bulk data transfer (multiple parameters) via USPEventNotif and ParameterPerRow CSV encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via USP
            usings and encode the data using ParameterPerRow CSV
    step 2. Ensure the EUT sends a Push! event using CSV encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (multiple parameters) via USPEventNotif and ObjectHierarchy JSON encoding usp_annex_a.tcl usp_annex_a_43 Verify bulk data transfer (multiple parameters) via USPEventNotif and ObjectHierarchy JSON encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via USP
            usings and encode the data using ObjectHierarchy JSON
    step 2. Ensure the EUT sends a Push! event using JSON encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (single parameter) via USPEventNotif and ParameterPerColumn CSV encoding usp_annex_a.tcl usp_annex_a_44 Verify bulk data transfer (single parameter) via USPEventNotif and ParameterPerColumn CSV encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via USP
            usings and encode the data using ParameterPerColumn CSV
    step 2. Ensure the EUT sends a Push! event using CSV encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (single parameter) via USPEventNotif and NameValuePair JSON encoding usp_annex_a.tcl usp_annex_a_45 Verify bulk data transfer (single parameter) via USPEventNotif and NameValuePair JSON encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via USP
            usings and encode the data using NameValuePair JSON
    step 2. Ensure the EUT sends a Push! event using JSON encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (multiple parameters) via USPEventNotif and ParameterPerColumn CSV encoding usp_annex_a.tcl usp_annex_a_46 Verify bulk data transfer (multiple parameters) via USPEventNotif and ParameterPerColumn CSV encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via USP
            usings and encode the data using ParameterPerColumn CSV
    step 2. Ensure the EUT sends a Push! event using CSV encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (multiple parameters) via USPEventNotif and NameValuePair JSON encoding usp_annex_a.tcl usp_annex_a_47 Verify bulk data transfer (multiple parameters) via USPEventNotif and NameValuePair JSON encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via USP
            usings and encode the data using NameValuePair JSON
    step 2. Ensure the EUT sends a Push! event using JSON encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (single parameter) via MQTT and ParameterPerRow CSV encoding usp_annex_a.tcl usp_annex_a_50 Verify bulk data transfer (single parameter) via MQTT and ParameterPerRow CSV encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via MQTT
             and encode the data using ParameterPerRow CSV
    step 2. Ensure the EUT sends a PUBLISH to the MQTT broker using CSV encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (single parameter) via MQTT and ObjectHierarchy JSON encoding usp_annex_a.tcl usp_annex_a_51 Verify bulk data transfer (single parameter) via MQTT and ObjectHierarchy JSON encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via MQTT
            and encode the data using ObjectHierarchy JSON
    step 2. Ensure the EUT sends a PUBLISH to the MQTT broker using JSON encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (multiple parameters) via MQTT and ParameterPerRow CSV encoding usp_annex_a.tcl usp_annex_a_52 Verify bulk data transfer (multiple parameters) via MQTT and ParameterPerRow CSV encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via MQTT
            and encode the data using ParameterPerRow CSV
    step 2. Ensure the EUT sends a PUBLISH to the MQTT broker using CSV encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (multiple parameters) via MQTT and ObjectHierarchy JSON encoding usp_annex_a.tcl usp_annex_a_53 Verify bulk data transfer (multiple parameters) via MQTT and ObjectHierarchy JSON encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via MQTT
            and encode the data using ObjectHierarchy JSON
    step 2. Ensure the EUT sends a PUBLISH to the MQTT broker using JSON encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (single parameter) via MQTT and ParameterPerColumn CSV encoding usp_annex_a.tcl usp_annex_a_54 Verify bulk data transfer (single parameter) via MQTT and ParameterPerColumn CSV encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via MQTT
            and encode the data using ParameterPerColumn CSV
    step 2. Ensure the EUT sends a PUBLISH to the MQTT broker using CSV encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (single parameter) via MQTT and NameValuePair JSON encoding usp_annex_a.tcl usp_annex_a_55 Verify bulk data transfer (single parameter) via MQTT and NameValuePair JSON encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via MQTT
            and encode the data using NameValuePair JSON
    step 2. Ensure the EUT sends a PUBLISH to the MQTT broker using JSON encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (multiple parameters) via MQTT and ParameterPerColumn CSV encoding usp_annex_a.tcl usp_annex_a_56 Verify bulk data transfer (multiple parameters) via MQTT and ParameterPerColumn CSV encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via MQTT
            and encode the data using ParameterPerColumn CSV
    step 2. Ensure the EUT sends a PUBLISH to the MQTT broker using CSV encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (multiple parameters) via MQTT and NameValuePair JSON encoding usp_annex_a.tcl usp_annex_a_57 Verify bulk data transfer (multiple parameters) via MQTT and NameValuePair JSON encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via MQTT
            and encode the data using NameValuePair JSON
    step 2. Ensure the EUT sends a PUBLISH to the MQTT broker using JSON encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (single parameter) via MQTTS and ParameterPerRow CSV encoding usp_annex_a.tcl usp_annex_a_60 Verify bulk data transfer (single parameter) via MQTTS and ParameterPerRow CSV encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via MQTTS
             and encode the data using ParameterPerRow CSV
    step 2. Ensure the EUT sends a PUBLISH to the MQTTS broker using CSV encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (single parameter) via MQTTS and ObjectHierarchy JSON encoding usp_annex_a.tcl usp_annex_a_61 Verify bulk data transfer (single parameter) via MQTTS and ObjectHierarchy JSON encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via MQTTS
            and encode the data using ObjectHierarchy JSON
    step 2. Ensure the EUT sends a PUBLISH to the MQTTS broker using JSON encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (multiple parameters) via MQTTS and ParameterPerRow CSV encoding usp_annex_a.tcl usp_annex_a_62 Verify bulk data transfer (multiple parameters) via MQTTS and ParameterPerRow CSV encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via MQTTS
            and encode the data using ParameterPerRow CSV
    step 2. Ensure the EUT sends a PUBLISH to the MQTTS broker using CSV encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (multiple parameters) via MQTTS and ObjectHierarchy JSON encoding usp_annex_a.tcl usp_annex_a_63 Verify bulk data transfer (multiple parameters) via MQTTS and ObjectHierarchy JSON encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via MQTTS
            and encode the data using ObjectHierarchy JSON
    step 2. Ensure the EUT sends a PUBLISH to the MQTTS broker using JSON encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (single parameter) via MQTTS and ParameterPerColumn CSV encoding usp_annex_a.tcl usp_annex_a_64 Verify bulk data transfer (single parameter) via MQTTS and ParameterPerColumn CSV encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via MQTTS
            and encode the data using ParameterPerColumn CSV
    step 2. Ensure the EUT sends a PUBLISH to the MQTTS broker using CSV encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (single parameter) via MQTTS and NameValuePair JSON encoding usp_annex_a.tcl usp_annex_a_65 Verify bulk data transfer (single parameter) via MQTTS and NameValuePair JSON encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via MQTTS
            and encode the data using NameValuePair JSON
    step 2. Ensure the EUT sends a PUBLISH to the MQTTS broker using JSON encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (multiple parameters) via MQTTS and ParameterPerColumn CSV encoding usp_annex_a.tcl usp_annex_a_66 Verify bulk data transfer (multiple parameters) via MQTTS and ParameterPerColumn CSV encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via MQTTS
            and encode the data using ParameterPerColumn CSV
    step 2. Ensure the EUT sends a PUBLISH to the MQTTS broker using CSV encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer (multiple parameters) via MQTTS and NameValuePair JSON encoding usp_annex_a.tcl usp_annex_a_67 Verify bulk data transfer (multiple parameters) via MQTTS and NameValuePair JSON encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via MQTTS
            and encode the data using NameValuePair JSON
    step 2. Ensure the EUT sends a PUBLISH to the MQTTS broker using JSON encoding


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer ForceCollection() via HTTP with JSON encoding usp_annex_a.tcl usp_annex_a_70 Verify bulk data transfer ForceCollection() via HTTP with JSON encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTP with JSON encoding
    step 2. Send an Operate message to the EUT for the ForceCollection() operation
    step 3. Ensure the EUT sends a POST to the HTTP host


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer ForceCollection() via HTTP with CSV encoding usp_annex_a.tcl usp_annex_a_71 Verify bulk data transfer ForceCollection() via HTTP with CSV encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTP with CSV encoding
    step 2. Send an Operate message to the EUT for the ForceCollection() operation
    step 3. Ensure the EUT sends a POST to the HTTP host


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer ForceCollection() via HTTPS with JSON encoding usp_annex_a.tcl usp_annex_a_72 Verify bulk data transfer ForceCollection() via HTTPS with JSON encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTPS with JSON encoding
    step 2. Send an Operate message to the EUT for the ForceCollection() operation
    step 3. Ensure the EUT sends a POST to the HTTPS host


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer ForceCollection() via HTTPS with CSV encoding usp_annex_a.tcl usp_annex_a_73 Verify bulk data transfer ForceCollection() via HTTPS with CSV encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via HTTPS with CSV encoding
    step 2. Send an Operate message to the EUT for the ForceCollection() operation
    step 3. Ensure the EUT sends a POST to the HTTPS host


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer ForceCollection() via USP with JSON encoding usp_annex_a.tcl usp_annex_a_74 Verify bulk data transfer ForceCollection() via USP with JSON encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via USP with JSON encoding
    step 2. Send an Operate message to the EUT for the ForceCollection() operation
    step 3. Ensure the EUT sends a POST to the USP host


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer ForceCollection() via USP with CSV encoding usp_annex_a.tcl usp_annex_a_75 Verify bulk data transfer ForceCollection() via USP with CSV encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via USP with CSV encoding
    step 2. Send an Operate message to the EUT for the ForceCollection() operation
    step 3. Ensure the EUT sends a POST to the USP host


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer ForceCollection() via MQTT with JSON encoding usp_annex_a.tcl usp_annex_a_76 Verify bulk data transfer ForceCollection() via MQTT with JSON encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via MQTT with JSON encoding
    step 2. Send an Operate message to the EUT for the ForceCollection() operation
    step 3. Ensure the EUT sends a POST to the MQTT host


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer ForceCollection() via MQTT with CSV encoding usp_annex_a.tcl usp_annex_a_77 Verify bulk data transfer ForceCollection() via MQTT with CSV encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via MQTT with CSV encoding
    step 2. Send an Operate message to the EUT for the ForceCollection() operation
    step 3. Ensure the EUT sends a POST to the MQTT host


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer ForceCollection() via MQTTS with JSON encoding usp_annex_a.tcl usp_annex_a_78 Verify bulk data transfer ForceCollection() via MQTTS with JSON encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via MQTTS with JSON encoding
    step 2. Send an Operate message to the EUT for the ForceCollection() operation
    step 3. Ensure the EUT sends a POST to the MQTTS host


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/

Test Module Name Synopsis
Verify bulk data transfer ForceCollection() via MQTTS with CSV encoding usp_annex_a.tcl usp_annex_a_79 Verify bulk data transfer ForceCollection() via MQTTS with CSV encoding


    Test Procedure:

    step 1. Configure the EUT to perform regular bulk data transfers via MQTTS with CSV encoding
    step 2. Send an Operate message to the EUT for the ForceCollection() operation
    step 3. Ensure the EUT sends a POST to the MQTTS host


    References:

    BBF TR-369 Version 1.1.2 "User Services Platform (USP)"

    https://usp.technology/


usp_scenarios.tcl

General USP configuration testing for user defined USP scenarios

Test Module Name Synopsis
Execute all defined scenarios or single scenario usp_scenarios.tcl usp_scenario_1 Execute all defined scenarios or single scenario


    step 1. Find the list of all defined USP scenarios
    step 2. If the testvar cwmpScenarioSingleMode is set to yes, run the next scenario.
            Otherwise, run all the scenarios.

    NOTE: For more help on USP scenarios, please visit the CDRouter USP
    user guide section on USP scenarios.



usp_conformance.tcl

Broadband Forum TP-469 USP conformance tests

Test Module Name Synopsis
Add message with allow partial false, single object, required parameters succeed usp_conformance.tcl usp_conformance_1_1 Add message with allow partial false, single object, required parameters succeed


    Purpose:

    The purpose of this test is to validate that the EUT properly handles an Add
    message when the allow_partial element is set to false, and all required
    parameters to be set upon Object Creation succeed.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Add message with allow partial true, single object, required parameters succeed usp_conformance.tcl usp_conformance_1_2 Add message with allow partial true, single object, required parameters succeed


    Purpose:

    The purpose of this test is to validate that the EUT properly handles an Add
    message when the allow_partial element is set to true, and all required
    parameters to be set upon Object Creation succeed.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Add message with allow partial false, single object, required parameters fail usp_conformance.tcl usp_conformance_1_3 Add message with allow partial false, single object, required parameters fail


    Purpose:

    The purpose of this test is to validate that the EUT properly handles an Add
    message when the allow_partial element is set to false, and at least one
    required parameter fails, and only a single object is set.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Add message with allow partial false, single invalid object usp_conformance.tcl usp_conformance_1_4 Add message with allow partial false, single invalid object


    Purpose:

    The purpose of this test is to validate that the EUT properly handles an Add
    message when the allow_partial element is set to false, and a single invalid
    object is set.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Add message with allow partial false, multiple objects usp_conformance.tcl usp_conformance_1_5 Add message with allow partial false, multiple objects


    Purpose:

    The purpose of this test is to validate that the EUT properly handles an Add
    message when the allow_partial element is set to false, multiple objects are
    attempted, and all required parameters to be set upon Object Creation
    succeed.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Add message with allow partial false, muliple objects with an invalid object usp_conformance.tcl usp_conformance_1_6 Add message with allow partial false, muliple objects with an invalid object


    Purpose:

    The purpose of this test is to validate that the EUT properly handles an Add
    message when the allow_partial element is set to false, multiple objects are
    attempted, and one of the objects are invalid.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Add message with allow partial false, multiple objects, required parameters fail in single object usp_conformance.tcl usp_conformance_1_7 Add message with allow partial false, multiple objects, required parameters fail in single object


    Purpose:

    The purpose of this test is to validate that the EUT properly handles an Add
    message when the allow_partial element is set to false, and at least one
    required parameter fails in one of multiple objects.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Add message with allow partial true, required parameters fail, invalid type, single object usp_conformance.tcl usp_conformance_1_8 Add message with allow partial true, required parameters fail, invalid type, single object


    Purpose:

    The purpose of this test is to validate that the EUT properly handles an Add
    message when the allow_partial element is set to true, and at least one
    required parameter fails (with an invalid value) in a single object.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Add message with allow partial true, required parameters fail, multiple objects usp_conformance.tcl usp_conformance_1_9 Add message with allow partial true, required parameters fail, multiple objects


    Purpose:

    The purpose of this test is to validate that the EUT properly handles an Add
    message when the allow_partial element is set to true, and at least one
    required parameter fails in one of multiple objects.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Add message with unique key addressing in path usp_conformance.tcl usp_conformance_1_10 Add message with unique key addressing in path


    Purpose:

    The purpose of this test is to validate that the EUT properly handles an Add
    message when the Controller uses unique key addressing.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Set message with allow partial false, required parameters pass usp_conformance.tcl usp_conformance_1_11 Set message with allow partial false, required parameters pass


    Purpose:

    The purpose of this test is to validate that the EUT properly handles a Set
    message when the allow_partial element is set to false, and all required
    parameters to be updated succeed.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Set message with allow partial true, required parameters pass usp_conformance.tcl usp_conformance_1_12 Set message with allow partial true, required parameters pass


    Purpose:

    The purpose of this test is to validate that the EUT properly handles a Set
    message when the allow_partial element is set to true, and all required
    parameters to be updated succeed.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Set message with allow partial false, multiple objects usp_conformance.tcl usp_conformance_1_13 Set message with allow partial false, multiple objects


    Purpose:

    The purpose of this test is to validate that the EUT properly handles a Set
    message when the allow_partial element is set to false, and all required
    parameters to be updated succeed.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Set message with allow partial false, required parameters fail usp_conformance.tcl usp_conformance_1_14 Set message with allow partial false, required parameters fail


    Purpose:

    The purpose of this test is to validate that the EUT properly handles a Set
    message when the allow_partial element is set to false, and a required
    parameter fails.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Set message with allow partial false, multiple objects, required parameters fail in single object usp_conformance.tcl usp_conformance_1_15 Set message with allow partial false, multiple objects, required parameters fail in single object


    Purpose:

    The purpose of this test is to validate that the EUT properly handles a Set
    message when the allow_partial element is set to false, and required
    parameters in one of multiple objects fail.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Set message with allow partial true, required parameter fails, multiple objects usp_conformance.tcl usp_conformance_1_16 Set message with allow partial true, required parameter fails, multiple objects


    Purpose:

    The purpose of this test is to validate that the EUT properly handles a Set
    message when the allow_partial element is set to true, and a required
    parameter on one of multiple objects fails.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Set message with allow partial true, non-required parameter fails, multiple parameters usp_conformance.tcl usp_conformance_1_17 Set message with allow partial true, non-required parameter fails, multiple parameters


    Purpose:

    The purpose of this test is to validate that the EUT properly handles a Set
    message when the allow_partial element is set to true, and one of multiple
    non-required parameters fail.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Set message with unique key addressing in path usp_conformance.tcl usp_conformance_1_18 Set message with unique key addressing in path


    Purpose:

    The purpose of this test is to validate that the EUT properly handles a Set
    message when the Controller uses unique key addressing.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Set message with wildcard search path, allow partial false, required parameters pass usp_conformance.tcl usp_conformance_1_19 Set message with wildcard search path, allow partial false, required parameters pass


    Purpose:

    The purpose of this test is to validate that the EUT properly handles a Set
    message when the Controller uses a wildcard search path and the requested
    updates succeed.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Set message with wildcard search path, allow partial false, required parameters fail usp_conformance.tcl usp_conformance_1_20 Set message with wildcard search path, allow partial false, required parameters fail


    Purpose:

    The purpose of this test is to validate that the EUT properly handles a Set
    message when the Controller uses a wildcard search path, allow_partial
    element is set to false, and required parameters multiple objects fail.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Set message with wildcard search path, allow partial true, required parameters fail usp_conformance.tcl usp_conformance_1_21 Set message with wildcard search path, allow partial true, required parameters fail


    Purpose:

    The purpose of this test is to validate that the EUT properly handles a Set
    message when the Controller uses a wildcard search path, the allow_partial
    element is set to true, and a required parameter on multiple objects fails.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Set message with search expression search path usp_conformance.tcl usp_conformance_1_22 Set message with search expression search path


    Purpose:

    The purpose of this test is to validate that the EUT properly handles a Set
    message when the Controller uses a search path.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Set message with path that matches no objects usp_conformance.tcl usp_conformance_1_23 Set message with path that matches no objects


    Purpose:

    The purpose of this test is to validate that the EUT properly handles a Set
    message when the requested path does not match any objects.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Delete message with allow partial false, valid object instance usp_conformance.tcl usp_conformance_1_24 Delete message with allow partial false, valid object instance


    Purpose:

    The purpose of this test is to validate that the EUT properly handles a
    Delete message when the allow_partial element is set to false, and the
    object to be deleted is valid.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Delete message with allow partial false, object instance doesn't exist usp_conformance.tcl usp_conformance_1_25 Delete message with allow partial false, object instance doesn’t exist


    Purpose:

    The purpose of this test is to validate that the EUT properly handles a
    Delete message when the allow_partial element is set to false, and the
    object instance to be deleted does not exist.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Delete message with allow partial false, invalid object usp_conformance.tcl usp_conformance_1_26 Delete message with allow partial false, invalid object


    Purpose:

    The purpose of this test is to validate that the EUT properly handles a
    Delete message when the allow_partial element is set to false, and the
    object to be deleted is invalid.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Delete message with allow partial false, multiple objects usp_conformance.tcl usp_conformance_1_27 Delete message with allow partial false, multiple objects


    Purpose:

    The purpose of this test is to validate that the EUT properly handles a Delete
    message when the allow_partial element is set to false, with multiple valid objects.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Delete message with allow partial false, multiple objects, invalid object usp_conformance.tcl usp_conformance_1_28 Delete message with allow partial false, multiple objects, invalid object


    Purpose:

    The purpose of this test is to validate that the EUT properly handles a Delete message
    when the allow_partial element is set to false, and one of the objects to be deleted is invalid.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Delete message with allow partial true, object instance doesn't exist usp_conformance.tcl usp_conformance_1_29 Delete message with allow partial true, object instance doesn’t exist


    Purpose:

    The purpose of this test is to validate that the EUT properly handles a Delete
    message when the allow_partial element is set to true, and the object instance
    to be deleted does not exist.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Delete message with allow partial true, invalid object usp_conformance.tcl usp_conformance_1_30 Delete message with allow partial true, invalid object


    Purpose:

    The purpose of this test is to validate that the EUT properly handles a
    Delete message when the allow_partial element is set to true, and the
    object is not valid in the Agent's supported data model.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Delete message with allow partial true, multiple objects, invalid object usp_conformance.tcl usp_conformance_1_31 Delete message with allow partial true, multiple objects, invalid object


    Purpose:

    The purpose of this test is to validate that the EUT properly handles a Delete
    message when the allow_partial element is set to true, and one of multiple
    objects is invalid.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Delete message with allow partial true, multiple objects, object doesn't exist usp_conformance.tcl usp_conformance_1_32 Delete message with allow partial true, multiple objects, object doesn’t exist


    Purpose:

    The purpose of this test is to validate that the EUT properly handles a Delete
    message when the allow_partial element is set to true, and one of multiple objects
    does not exist in the Agent's instantiated data model.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Delete message with unique key addressing usp_conformance.tcl usp_conformance_1_33 Delete message with unique key addressing


    Purpose:

    The purpose of this test is to validate that the EUT properly handles a
    Delete message when the Controller uses unique key addressing.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Delete message with wildcard search path, valid objects usp_conformance.tcl usp_conformance_1_34 Delete message with wildcard search path, valid objects


    Purpose:

    The purpose of this test is to validate that the EUT properly handles a Delete
    message when the Controller uses a wildcard search to delete multiple valid objects.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Delete message with search expression search path usp_conformance.tcl usp_conformance_1_35 Delete message with search expression search path


    Purpose:

    The purpose of this test is to validate that the EUT properly handles a Delete
    message when the Controller uses a search expression to delete one or more valid objects.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Get message with full parameter path usp_conformance.tcl usp_conformance_1_36 Get message with full parameter path


    Purpose:

    The purpose of this test is to ensure the Controller can retrieve the values
    of parameters in the Agent's Instantiated Data Model when a single full parameter
    path is specified.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Get message with multiple full parameter paths, same object usp_conformance.tcl usp_conformance_1_37 Get message with multiple full parameter paths, same object


    Purpose:

    The purpose of this test is to ensure the Controller can retrieve the values of parameters
    in the Agent's Instantiated Data Model when multiple full parameter paths are specified
    within the same object.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Get message with multiple full parameter paths, different objects usp_conformance.tcl usp_conformance_1_38 Get message with multiple full parameter paths, different objects


    Purpose:

    The purpose of this test is to ensure the Controller can retrieve the values of parameters in
    the Agent's Instantiated Data Model when multiple full parameter paths are specified within
    multiple objects.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Get message with object path usp_conformance.tcl usp_conformance_1_39 Get message with object path


    Purpose:

    The purpose of this test is to ensure the Controller can retrieve the values of parameters in
    the Agent's Instantiated Data Model when an object path is specified.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Get message with object instance path usp_conformance.tcl usp_conformance_1_40 Get message with object instance path


    Purpose:

    The purpose of this test is to ensure the Controller can retrieve the values
    of parameters in the Agent's Instantiated Data Model when a path to an object
    instance is specified.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Get message with invalid parameter usp_conformance.tcl usp_conformance_1_41 Get message with invalid parameter


    Purpose:

    The purpose of this test is to ensure the EUT can properly handle
    a Get message when a single invalid parameter is requested.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Get message with invalid parameter and valid parameter usp_conformance.tcl usp_conformance_1_42 Get message with invalid parameter and valid parameter


    Purpose:

    The purpose of this test is to ensure the Controller can retrieve the values of
    parameters in the Agent's Instantiated Data Model when both a valid and invalid
    parameter are requested.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Get message using unique key addressing usp_conformance.tcl usp_conformance_1_43 Get message using unique key addressing


    Purpose:

    The purpose of this test is to ensure the Controller can retrieve the values
    of parameters in the Agent's Instantiated Data Model when the requested path
    uses unique key addressing.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Get message using wildcard search path on full parameter usp_conformance.tcl usp_conformance_1_44 Get message using wildcard search path on full parameter


    Purpose:

    The purpose of this test is to ensure the Controller can retrieve the values of
    parameters in the Agent's Instantiated Data Model when the requested path uses
    a wildcard to retrieve a single parameter from multiple objects.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Get message using wildcard search path on object path usp_conformance.tcl usp_conformance_1_45 Get message using wildcard search path on object path


    Purpose:

    The purpose of this test is to ensure the Controller can retrieve the values of
    parameters in the Agent's Instantiated Data Model when the requested path uses
    a wildcard to retrieve all parameters from multiple object instances.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Get message using search expression search path (equivalence) usp_conformance.tcl usp_conformance_1_46 Get message using search expression search path (equivalence)


    Purpose:

    The purpose of this test is to ensure the Controller can retrieve the values of
    parameters in the Agent's Instantiated Data Model when the requested path uses
    a search path to retrieve objects that parameters that match a particular value.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Get message using search expression search path (non-equivalence) usp_conformance.tcl usp_conformance_1_47 Get message using search expression search path (non-equivalence)


    Purpose:

    The purpose of this test is to ensure the Controller can retrieve the values of
    parameters in the Agent's Instantiated Data Model when the requested path uses
    a search path to retrieve objects that parameters that do not match a particular value.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Get message using search expression search path (exclusive greater comparison) usp_conformance.tcl usp_conformance_1_48 Get message using search expression search path (exclusive greater comparison)


    Purpose:

    The purpose of this test is to ensure the Controller can retrieve the values of parameters
    in the Agent's Instantiated Data Model when the requested path uses a search path to
    retrieve objects that parameters that are greater than a particular value.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Get message using search expression search path (exclusive lesser comparison) usp_conformance.tcl usp_conformance_1_49 Get message using search expression search path (exclusive lesser comparison)


    Purpose:

    The purpose of this test is to ensure the Controller can retrieve the values of parameters
    in the Agent's Instantiated Data Model when the requested path uses a search path to
    retrieve objects that parameters that are less than a particular value.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Get message using search expression search path (inclusive greater comparison) usp_conformance.tcl usp_conformance_1_50 Get message using search expression search path (inclusive greater comparison)


    Purpose:

    The purpose of this test is to ensure the Controller can retrieve the values of
    parameters in the Agent's Instantiated Data Model when the requested path uses
    a search path to retrieve objects that parameters that are greater than or
    equal to a particular value.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Get message using search expression search path (inclusive lesser comparison) usp_conformance.tcl usp_conformance_1_51 Get message using search expression search path (inclusive lesser comparison)


    Purpose:

    The purpose of this test is to ensure the Controller can retrieve the values of
    parameters in the Agent's Instantiated Data Model when the requested path uses
    a search path to retrieve objects that parameters that are less than or
    equal to a particular value.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Notify - Subscription creation using Value Change usp_conformance.tcl usp_conformance_1_52 Notify - Subscription creation using Value Change


    Purpose:

    The purpose of this test is to ensure that the Agent will create and
    acknowledge Subscriptions requested by the Controller, and notifies
    the Controller when the conditions of the subscription are triggered.
    This test uses the ValueChange event to exercise these functions,
    validating the behavior of ValueChange in the process.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Notify - Subscription Deletion Using Value Change usp_conformance.tcl usp_conformance_1_53 Notify - Subscription Deletion Using Value Change


    Purpose:

    The purpose of this test is to ensure that the Agent will remove and terminate
    a Subscription when the Controller uses the Delete message.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Notification Retry using Value Change usp_conformance.tcl usp_conformance_1_54 Notification Retry using Value Change


    Purpose:

    The purpose of this test is to ensure that the Agent will attempt to
    resend Notify messages when the NotifRetry parameter in a Subscription
    object is set to true and the Controller does not send a NotifyResp.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Subscription Expiration using Value Change usp_conformance.tcl usp_conformance_1_55 Subscription Expiration using Value Change


    Purpose:

    The purpose of this test is to ensure that the Agent removes a Subscription
    from the Subscription table after its TimeToLive has expired.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Notification Retry Expiration using Value Change usp_conformance.tcl usp_conformance_1_56 Notification Retry Expiration using Value Change


    Purpose:

    The purpose of this test is to ensure that the Agent will cease attempts to retry
    Notify messages after an amount of time specified in value of the NotifExpiration
    parameter in the Subscription object has passed.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
ObjectCreation Notification usp_conformance.tcl usp_conformance_1_57 ObjectCreation Notification


    Purpose:

    The purpose of this test is to ensure that the Agent will cease attempts to retry
    Notify messages after an amount of time specified in value of the NotifExpiration
    parameter in the Subscription object has passed.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
ObjectDeletion Notification usp_conformance.tcl usp_conformance_1_58 ObjectDeletion Notification


    Purpose:

    The purpose of this test is to ensure that the Agent will send a
    Notify message to the Controller when the Controller is Subscribed
    to the ObjectDeletion event.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Event Notification using Periodic! usp_conformance.tcl usp_conformance_1_59 Event Notification using Periodic!


    Purpose:

    The purpose of this test is to ensure that the Agent will send a
    Notify message to the Controller when the Controller is Subscribed
    to an Event notification that correlates with an event defined in
    its supported data model.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
OnBoardRequest Notification usp_conformance.tcl usp_conformance_1_60 OnBoardRequest Notification


    Purpose:

    The purpose of this test is to ensure that the Agent will send a Notify
    message to the Controller when the Controller initiates a SendOnBoardRequest()
    operation.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Operate message using Reboot() with send_resp true usp_conformance.tcl usp_conformance_1_61 Operate message using Reboot() with send_resp true


    Purpose:

    The purpose of this test is to ensure that the Agent will correctly process an
    Operate message using the Reboot() operation as a trigger when send_resp is true.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Operate message using Reboot() with send_resp false usp_conformance.tcl usp_conformance_1_62 Operate message using Reboot() with send_resp false


    Purpose:

    The purpose of this test is to ensure that the Agent will correctly process an
    Operate message using the Reboot() operation as a trigger when send_resp is false.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Asynchronous operation with send_resp true usp_conformance.tcl usp_conformance_1_64 Asynchronous operation with send_resp true


    Purpose:

    The purpose of this test is to ensure that the Agent will correctly process an
    Operate message where the operation is asynchronous and send_resp is set to true.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Asynchronous operations with send_resp false usp_conformance.tcl usp_conformance_1_65 Asynchronous operations with send_resp false


    Purpose:

    The purpose of this test is to ensure that the Agent will correctly process an
    Operate message where the operation is asynchronous and send_resp is set to false.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
GetInstances using a single object, first_level_only true usp_conformance.tcl usp_conformance_1_66 GetInstances using a single object, first_level_only true


    Purpose:

    The purpose of this test is to ensure that the Agent will correctly process a GetInstances
    message on a single object when first_level_only is true.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
GetInstances using a single object, first_level_only false usp_conformance.tcl usp_conformance_1_67 GetInstances using a single object, first_level_only false


    Purpose:

    The purpose of this test is to ensure that the Agent will correctly process a GetInstances
    message on a single object when first_level_only is false.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
GetInstances with multiple objects usp_conformance.tcl usp_conformance_1_68 GetInstances with multiple objects


    Purpose:

    The purpose of this test is to ensure that the Agent will correctly process
    a GetInstances message on multiple objects.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
GetInstances with wildcard search path usp_conformance.tcl usp_conformance_1_70 GetInstances with wildcard search path


    Purpose:

    The purpose of this test is to ensure that the Agent will correctly process
    a GetInstances message when a wildcard search path is used.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
GetInstances with search expression search path usp_conformance.tcl usp_conformance_1_71 GetInstances with search expression search path


    Purpose:

    The purpose of this test is to ensure that the Agent will correctly process
    a GetInstances message when a search expression search path is used.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
GetSupportedDM using a single object, first_level_only false, all options usp_conformance.tcl usp_conformance_1_72 GetSupportedDM using a single object, first_level_only false, all options


    Purpose:

    The purpose of this test is to ensure that the Agent will correctly process
    a GetSupportedDM message using a single object, when first_level_only is false
    and all options are true.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
GetSupportedDM using a single object, first_level_only true, all options usp_conformance.tcl usp_conformance_1_73 GetSupportedDM using a single object, first_level_only true, all options


    Purpose:

    The purpose of this test is to ensure that the Agent will correctly process
    a GetSupportedDM message using a single object, when first_level_only is true
    and all options are true.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
GetSupportedDM using a single object, first_level_only true, no options usp_conformance.tcl usp_conformance_1_74 GetSupportedDM using a single object, first_level_only true, no options


    Purpose:

    The purpose of this test is to ensure that the Agent will correctly process
    a GetSupportedDM message using a single object, when first_level_only is true
    and all options are false.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
GetSupportedDM using multiple objects, first_level_only true, all options usp_conformance.tcl usp_conformance_1_75 GetSupportedDM using multiple objects, first_level_only true, all options


    Purpose:

    The purpose of this test is to ensure that the Agent will correctly process
    a GetSupportedDM message using multiple objects, when first_level_only is true
    and all options are true.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
GetSupportedDM on root object, all options usp_conformance.tcl usp_conformance_1_76 GetSupportedDM on root object, all options


    Purpose:

    The purpose of this test is to ensure the Agent will correctly process
    a GetSupportedDM message when the requested path is the root of the data model.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
GetSupportedDM on unsupported object usp_conformance.tcl usp_conformance_1_77 GetSupportedDM on unsupported object


    Purpose:

    The purpose of this test is to ensure the Agent will correctly process a
    GetSupportedDM message when the requested path is an unsupported object.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Removal of subscriptions that have no associated controller usp_conformance.tcl usp_conformance_1_78 Removal of subscriptions that have no associated controller


    Purpose:

    According to the Device.LocalAgent.Subscription.{i}.Recipient parameter:

    The value MUST be the Path Name of the Controller instance that will receive
    the Notification associated with this Subscription. If the referenced object
    is deleted, this instance MUST also be deleted (so the parameter value will
    never be an empty string).

    This test validates that if a Controller is removed from the Agent's
    Device.LocalAgent.Controller.{i}. table, any associated Subscription objects
    are also removed.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Operate message using input args usp_conformance.tcl usp_conformance_1_79 Operate message using input args


    Purpose:

    The purpose of this test is to ensure that the Agent will correctly process an
    Operate message with input args.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
GetSupportedProtocol usp_conformance.tcl usp_conformance_1_80 GetSupportedProtocol


    Purpose:

    The purpose of this test is to ensure the Controller can learn the supported
    USP protocol version(s) of the EUT.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Automatic unique key generation usp_conformance.tcl usp_conformance_1_81 Automatic unique key generation


    Purpose:

    The purpose of this test is to validate that the EUT assigns unique
    keys which are not supplied in the Add message.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Get message with unmatched search expression usp_conformance.tcl usp_conformance_1_82 Get message with unmatched search expression


    Purpose:

    The purpose of this test is to verify that the EUT sends a successful empty
    response when a Get request using a search expression returns no objects.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
GetInstances message with unmatched search expression usp_conformance.tcl usp_conformance_1_83 GetInstances message with unmatched search expression


    Purpose:

    The purpose of this test is to verify that the EUT sends a successful empty
    response when a GetInstances request using a search expression returns no objects.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Notification - Subscription using search paths usp_conformance.tcl usp_conformance_1_84 Notification - Subscription using search paths


    Purpose:
    
    The purpose of this test is to ensure that the Agent will create and
    acknowledge Subscriptions containing a search path, and notifies the
    Controller when the conditions of the subscription are triggered.
    

    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Agent does not accept messages from it's own Endpoint ID usp_conformance.tcl usp_conformance_2_1 Agent does not accept messages from it’s own Endpoint ID


    Purpose:

    The purpose of this test is to ensure the EUT does not respond to a USP message
    when the from_id is the EUT’s endpoint ID.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Agent rejects messages that do not contain it's to_id in the USP Record usp_conformance.tcl usp_conformance_2_2 Agent rejects messages that do not contain it’s to_id in the USP Record


    Purpose:

    The purpose of this test is to ensure the EUT does not respond to a USP
    message when the USP record doesn’t contain the EUT’s to_id.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Connecting without absolute time usp_conformance.tcl usp_conformance_2_6 Connecting without absolute time


    Purpose:

    The purpose of this test is to ensure the EUT can communicate with a
    Controller if it cannot obtain an absolute time.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Agent ignored unsigned or invalid record signatures usp_conformance.tcl usp_conformance_2_7 Agent ignored unsigned or invalid record signatures


    Procedure:

    The purpose of this test is to ensure the EUT will ignore a USP record
    when the signature field is invalid.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Agent ignores invalid TLS certificate usp_conformance.tcl usp_conformance_2_8 Agent ignores invalid TLS certificate


    Purpose:

    The purpose of this test is to ensure the EUT rejects TLS connections
    when an Endpoint’s TLS certificate is invalid.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Use of the Untrusted Role usp_conformance.tcl usp_conformance_2_9 Use of the Untrusted Role


    Purpose:

    The purpose of this test is to ensure the EUT correctly assigns
    new a Role of Untrusted.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Adding a Role usp_conformance.tcl usp_conformance_2_10 Adding a Role


    Purpose:

    The purpose of this test is to ensure that the Add message can be used to
    add new Roles to the EUT’s data model.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Permissions - Object Creation Allowed usp_conformance.tcl usp_conformance_2_11 Permissions - Object Creation Allowed


    Purpose:

    The purpose of this test is to ensure the EUT adheres to permissions
    set to allow the creation of a particular object.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Permissions - Object Creation Not Allowed usp_conformance.tcl usp_conformance_2_12 Permissions - Object Creation Not Allowed


    Purpose:

    The purpose of this test is to ensure the EUT adheres to permissions
    set to restrict the creation of a particular object.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Permissions - Object Deletion Allowed usp_conformance.tcl usp_conformance_2_13 Permissions - Object Deletion Allowed


    Purpose:

    The purpose of this test is to ensure the EUT adheres to permissions
    set to allow the deletion of a particular object.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Permissions - Object Deletion Not Allowed usp_conformance.tcl usp_conformance_2_14 Permissions - Object Deletion Not Allowed


    Purpose:

    The purpose of this test is to ensure the EUT adheres to permissions
    set to restrict the deletion of a particular object.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Permissions - Parameter Update Allowed usp_conformance.tcl usp_conformance_2_15 Permissions - Parameter Update Allowed


    Purpose:

    The purpose of this test is to ensure the EUT adheres to permissions set
    to allow the update of a particular object.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Permissions - Parameter Update Not Allowed usp_conformance.tcl usp_conformance_2_16 Permissions - Parameter Update Not Allowed


    Purpose:

    The purpose of this test is to ensure the EUT adheres to permissions
    set to restrict the update of a particular object.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Permission - Operation Allowed usp_conformance.tcl usp_conformance_2_17 Permission - Operation Allowed


    Purpose:

    The purpose of this test is to ensure the EUT adheres to permissions
    set to allow the invocation of commands on a particular object.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Permissions - Operation Not Allowed usp_conformance.tcl usp_conformance_2_18 Permissions - Operation Not Allowed


    Purpose:

    The purpose of this test is to ensure the EUT adheres to permissions
    set to restrict the invocation of commands on a particular object.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Permissions - Value Change Notification Allowed on Parameter usp_conformance.tcl usp_conformance_2_19 Permissions - Value Change Notification Allowed on Parameter


    Purpose:

    The purpose of this test is to ensure the EUT adheres to permissions set to
    allow a Controller to subscribe to the ValueChange notification of a particular parameter.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Permissions - Value Change Notification Not Allowed on Parameter usp_conformance.tcl usp_conformance_2_20 Permissions - Value Change Notification Not Allowed on Parameter


    Purpose:

    The purpose of this test is to ensure the EUT adheres to permissions set to restrict
    a controller from subscribing to the ValueChange notification of a particular parameter.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Permissions - Overlapping Permissions usp_conformance.tcl usp_conformance_2_21 Permissions - Overlapping Permissions


    Purpose:

    The purpose of this test is to ensure the EUT allows for the creation of
    Permission instances, and when Permissions overlap the EUT behaves correctly.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Using Get when no read permissions are available on some parameters usp_conformance.tcl usp_conformance_2_22 Using Get when no read permissions are available on some parameters


    Purpose:

    The purpose of this test is to ensure the EUT correctly returns parameters
    that are readable while ignoring parameters that do not have read permissions.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Bad request outside a session context usp_conformance.tcl usp_conformance_3_1 Bad request outside a session context


    Purpose:

    The purpose of this test is to ensure the EUT correctly responds
    to a bad request outside a session context.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Agent Verifies Non-payload Field Integrity usp_conformance.tcl usp_conformance_3_2 Agent Verifies Non-payload Field Integrity


    Purpose:

    The purpose of this test is to ensure the EUT verifies the integrity of
    the non-payload fields in a USP record.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Agent reject invalid signature starting a session context usp_conformance.tcl usp_conformance_3_3 Agent reject invalid signature starting a session context


    Purpose:

    The purpose of this test is to ensure the EUT handles an attempt to start a session
    context with an invalid mac_signature.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Using TLS for USP Record Integrity usp_conformance.tcl usp_conformance_3_4 Using TLS for USP Record Integrity


    Purpose:

    The purpose of this test is to ensure the EUT uses TLS to validate the integrity
    of USP records when payload_security is TLS12 and the TLS handshake has completed.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Failure to Establish TLS usp_conformance.tcl usp_conformance_3_5 Failure to Establish TLS


    Purpose:

    The purpose of this test is to ensure the EUT behaves correctly when the TLS
    session used to encapsulate the payload cannot be established


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Agent ignores TLS renegotiation for E2E message exchange usp_conformance.tcl usp_conformance_3_6 Agent ignores TLS renegotiation for E2E message exchange


    Purpose:

    The purpose of this test is to ensure the EUT correctly ignores TLS
    renegotiation frames during an E2E message exchange.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Use of X.509 Certificates usp_conformance.tcl usp_conformance_3_7 Use of X.509 Certificates


    Purpose:

    The purpose of this test is to ensure the EUT correctly uses X.509 certificates
    to authenticate other endpoints, and in turn provides a X.509 Certificate for the
    purpose of authentication.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Establishing a Session Context usp_conformance.tcl usp_conformance_3_8 Establishing a Session Context


    Purpose:

    The purpose of this test is to ensure the EUT can use a session context
    to exchange USP messages.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Receipt of a Record out of a Session Context usp_conformance.tcl usp_conformance_3_9 Receipt of a Record out of a Session Context


    Purpose:

    The purpose of this test is to ensure the EUT correctly handles the
    receiving of a USP record outside of a session context.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Session Context Expiration usp_conformance.tcl usp_conformance_3_10 Session Context Expiration


    Purpose:

    The purpose of this test is to ensure the EUT correctly adheres to the
    SessionExpiration parameter.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Use of Sequence ID and Expected ID usp_conformance.tcl usp_conformance_3_11 Use of Sequence ID and Expected ID


    Purpose:

    The purpose of this test is to ensure the EUT correctly uses the
    sequence_id and expected_id attributes found in the session context.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Preservation of USP Records usp_conformance.tcl usp_conformance_3_12 Preservation of USP Records


    Purpose:

    The purpose of this test is to ensure the EUT preserves a sent
    record in the event the receiving endpoint requests a restransmission.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Agent Rejects Records with Different Payload Security than the Established Context usp_conformance.tcl usp_conformance_3_13 Agent Rejects Records with Different Payload Security than the Established Context


    Purpose:

    The purpose of this test is to ensure the EUT does not accept USP Records
    that have a different payload_security value than that of the established
    session context.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Use of retransmit_id usp_conformance.tcl usp_conformance_3_14 Use of retransmit_id


    Purpose:

    The purpose of this test is to ensure the EUT correctly used the retransmit_id value in a
    USP record and adheres to the related parameters in the data model.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Handling Duplicate Records usp_conformance.tcl usp_conformance_3_15 Handling Duplicate Records


    Purpose:

    The purpose of this test is to ensure the EUT can correctly handle receiving
    duplicate records.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Use of X.509 Certificates at the MTP Layer usp_conformance.tcl usp_conformance_4_1 Use of X.509 Certificates at the MTP Layer


    Purpose:

    The purpose of this test is to ensure the EUT can use X.509 certificates
    to secure communication at the MTP layer.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Mapping a USP Record to a CoAP message usp_conformance.tcl usp_conformance_5_1 Mapping a USP Record to a CoAP message


    Purpose:

    The purpose of this test is to ensure the EUT can properly use CoAP to
    transport USP Records.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
USP Records exceed CoAP message size usp_conformance.tcl usp_conformance_5_2 USP Records exceed CoAP message size


    Purpose:

    The purpose of this test is to ensure the EUT properly segments large USP
    records and transports them using block encapsulation.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Successful CoAP Exchange usp_conformance.tcl usp_conformance_5_3 Successful CoAP Exchange


    Purpose:

    The purpose of this test is to ensure the EUT correctly sends a 2.04 Changed
    response to CoAP messages.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Failed CoAP exchange - timeout usp_conformance.tcl usp_conformance_5_4 Failed CoAP exchange - timeout


    Purpose:

    The purpose of this test is to ensure the EUT behaves correctly when a timeout
    occurs at the MTP layer when using CoAP.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Failed CoAP Exchange - Invalid Method usp_conformance.tcl usp_conformance_5_5 Failed CoAP Exchange - Invalid Method


    Purpose:

    The purpose of this test is to ensure the EUT correctly responds when
    it receives a CoAP message with an invalid method.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Failed CoAP Exchange - Invalid Content-Format usp_conformance.tcl usp_conformance_5_6 Failed CoAP Exchange - Invalid Content-Format


    Purpose:

    The purpose of this test is to ensure the EUT properly responds to CoAP
    messages that feature invalid Content-Format options.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Failed CoAP Exchange - Invalid USP Record usp_conformance.tcl usp_conformance_5_7 Failed CoAP Exchange - Invalid USP Record


    Purpose:

    The purpose of this test is to ensure the EUT properly responds to a CoAP message containing
    a malformed USP record.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Use of DTLS usp_conformance.tcl usp_conformance_5_8 Use of DTLS


    Purpose:

    The purpose of this test is to ensure the EUT can secure communication with
    another CoAP endpoint at the CoAP layer


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Support of Required Profiles usp_conformance.tcl usp_conformance_6_1 Support of Required Profiles


    Purpose:

    The purpose of this test is to ensure the EUT supports the required
    STOMP profiles.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
STOMP session establishment usp_conformance.tcl usp_conformance_6_2 STOMP session establishment


    Purpose:

    The purpose of this test is to ensure the EUT can properly start
    a STOMP session.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
STOMP Connection Retry usp_conformance.tcl usp_conformance_6_3 STOMP Connection Retry


    Purpose:

    The purpose of this test is to ensure the EUT properly enters a retry state
    when it fails to connect to the STOMP server.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Successful USP message over STOMP with required headers usp_conformance.tcl usp_conformance_6_4 Successful USP message over STOMP with required headers


    Purpose:

    The purpose of this test is to ensure the EUT can communicate over STOMP
    using the correct headers.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
STOMP destination - provided in subscribe-dest usp_conformance.tcl usp_conformance_6_5 STOMP destination - provided in subscribe-dest


    Purpose:

    The purpose of this test is to ensure the EUT is correctly subscribes to a destination
    found in the subscribe-dest header in a CONNECTED frame.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
STOMP destination - configured in USP data model usp_conformance.tcl usp_conformance_6_6 STOMP destination - configured in USP data model


    Purpose:

    The purpose of this test is to ensure the EUT can use the
    Device.LocalAgent.MTP.{i}.STOMP.Destination parameter to select a STOMP
    destination.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
STOMP Destination - Terminates Unconfigured Session usp_conformance.tcl usp_conformance_6_7 STOMP Destination - Terminates Unconfigured Session


    Purpose:

    The purpose of this test is to ensure the EUT terminates a STOMP session when no destination
    is configured.

    Note:

    This test waits the number of seconds defined in testvar uspRebootTimeout. Ensure this value
    is adequate to allow the EUT to reboot and contact the USP controller.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Use of STOMP heartbeat mechanism usp_conformance.tcl usp_conformance_6_8 Use of STOMP heartbeat mechanism


    Purpose:

    The purpose of this test is to ensure the EUT correctly implements the STOMP heartbeat
    mechanism and the relevent parameters in the data model.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Error Handling - Unprocessed Record usp_conformance.tcl usp_conformance_6_9 Error Handling - Unprocessed Record


    Purpose:

    The purpose of this test is to ensure the EUT will correctly send an ERROR STOMP frame
    when a malformed record is received.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Agent's STOMP destination is changed usp_conformance.tcl usp_conformance_6_10 Agent’s STOMP destination is changed


    Purpose:

    The purpose of this test is to ensure that when the EUT's destination is
    altered it properly unsubscribes and subscribes to the new destination.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
STOMP - Use of TLS usp_conformance.tcl usp_conformance_6_11 STOMP - Use of TLS


    Purpose:

    The purpose of this test is to ensure the EUT can secure STOMP
    communication via TLS.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
WebSocket - Session Establishment usp_conformance.tcl usp_conformance_7_1 WebSocket - Session Establishment


    Purpose:

    The purpose of this test is to ensure the EUT can establish a session
    using WebSocket as the MTP.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Use of only one session usp_conformance.tcl usp_conformance_7_2 Use of only one session


    Purpose:

    The purpose of this test is to ensure the EUT maintains only one WebSocket
    connection to the controller at a time.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Closing a WebSocket Connection usp_conformance.tcl usp_conformance_7_4 Closing a WebSocket Connection


    Purpose:

    The purpose of this test is to ensure the EUT correctly implements the
    procedure to close a WebSocket connection.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Rejection of Session Establishment usp_conformance.tcl usp_conformance_7_5 Rejection of Session Establishment


    Purpose:

    The purpose of this test is to ensure the EUT will correct reject
    WebSocket sessions.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Error Handling - Unprocessed Records usp_conformance.tcl usp_conformance_7_6 Error Handling - Unprocessed Records


    Purpose:

    The purpose of this test is to ensure the EUT correctly closes the Web
    Socket connection with a malformed USP Record is received.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Use of Ping and Pong frames usp_conformance.tcl usp_conformance_7_7 Use of Ping and Pong frames


    Purpose:

    The purpose of this test is to ensure the EUT correctly uses Ping and Pong
    control frames to keep the WebSocket session alive.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
WebSocket Session Retry usp_conformance.tcl usp_conformance_7_8 WebSocket Session Retry


    Purpose:

    The purpose of this test is to ensure the EUT will correctly attempt to reestablish
    a WebSocket session if a session is unexpectedly closed.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
WebSocket - Use of TLS usp_conformance.tcl usp_conformance_7_9 WebSocket - Use of TLS


    Purpose:

    The purpose of this test is to ensure the EUT can establish and use a
    secure WebSocket connection.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
DHCP Discovery - Agent Request Requirements usp_conformance.tcl usp_conformance_8_1 DHCP Discovery - Agent Request Requirements


    Purpose:

    The purpose of this test is to ensure the EUT correctly requests controller
    information via DHCP.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
DHCP Discovery - Agent handling of received options usp_conformance.tcl usp_conformance_8_2 DHCP Discovery - Agent handling of received options


    Purpose:

    The purpose of this test is to ensure the EUT can properly handle the USP
    options provided by a DHCP server.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
DHCP Discovery - FQDN Leads to DNS Query usp_conformance.tcl usp_conformance_8_3 DHCP Discovery - FQDN Leads to DNS Query


    Purpose:

    The purpose of this test is to ensure the EUT correctly uses DNS to retrieve
    additional controller information upon receiving a FQDN of a controller.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
mDNS usp_conformance.tcl usp_conformance_8_4 mDNS


    Purpose:

    The purpose of this test is to ensure the EUT correctly implements mDNS.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
mDNS and Message Transfer Protocols usp_conformance.tcl usp_conformance_8_5 mDNS and Message Transfer Protocols


    Purpose:

    The purpose of this test is to ensure the EUT correctly advertises the MTP
    it supports. This use case is exclusive to CoAP, so this test only applies to
    CoAP based endpoints.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
DNS - DNS Record Requirements usp_conformance.tcl usp_conformance_8_6 DNS - DNS Record Requirements


    Purpose:

    The purpose of this test is to ensure the EUT provides valid DNS-SD.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
mDNS request response usp_conformance.tcl usp_conformance_8_7 mDNS request response


    Purpose:

    The purpose of this test is to ensure the EUT will respond to mDNS requests.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Use of Device.LocalAgent.AddCertificate() usp_conformance.tcl usp_conformance_9_2 Use of Device.LocalAgent.AddCertificate()


    Purpose:

    The purpose of this test is to ensure the AddCertificate()
    operation on the EUT functions correctly.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Upgrading the Agent's Firmware - Autoactivate enable usp_conformance.tcl usp_conformance_9_3 Upgrading the Agent’s Firmware - Autoactivate enable


    Purpose:

    The purpose of this test is to ensure the EUT can download firmware and
    automatically activate it using the AutoActivate parameter.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Upgrading the Agent's Firmware - Using TimeWindow, Immediate usp_conformance.tcl usp_conformance_9_4 Upgrading the Agent’s Firmware - Using TimeWindow, Immediate


    Purpose:

    The purpose of this test is to ensure the EUT can activate a firmware image
    when a TimeWindow object is used with Immediately mode.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Upgrading the Agent's Firmware - Use TimeWindow, AnyTime usp_conformance.tcl usp_conformance_9_5 Upgrading the Agent’s Firmware - Use TimeWindow, AnyTime


    Purpose:

    The purpose of this test is to ensure the EUT can activate a firmware image
    when a TimeWindow instance is used with the AnyTime mode.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Upgrading the Agent's Firmware - Validated Firmware usp_conformance.tcl usp_conformance_9_6 Upgrading the Agent’s Firmware - Validated Firmware


    Purpose:

    The purpose of this test is to ensure the EUT can validate the integrety of
    downloaded firmware.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Upgrading the Agent's Firmware - Download to Active Bank usp_conformance.tcl usp_conformance_9_7 Upgrading the Agent’s Firmware - Download to Active Bank


    Purpose:

    The purpose of this test is to ensure the EUT is capable of downloading and
    installing new firmware for EUTs that may support only the active firmware
    bank


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Upgrading the Agent's Firmware - Cancelling a request using the Cancel() command usp_conformance.tcl usp_conformance_9_8 Upgrading the Agent’s Firmware - Cancelling a request using the Cancel() command


    Purpose:

    The purpose of this test is to ensure the EUT can correctly cancel a Download() operation.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Adding a New Controller- OnBoardingRequest usp_conformance.tcl usp_conformance_9_9 Adding a New Controller- OnBoardingRequest


    Purpose:

    The purpose of this test is to ensure the EUT can handle the manual adding
    of a new Controller.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Use of the Boot! event and BootParameters usp_conformance.tcl usp_conformance_9_10 Use of the Boot! event and BootParameters


    Purpose:

    The purpose of this test is to ensure the EUT correctly triggers the Boot!
    event correctly and includes the configured BootParameters.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Use of the Timer! Event usp_conformance.tcl usp_conformance_9_11 Use of the Timer! Event


    Purpose:

    The purpose of this test is to ensure the Timer! event
    can be configured, and the EUT correctly triggers the event.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Use BulkData collection using HTTP and JSON usp_conformance.tcl usp_conformance_10_1 Use BulkData collection using HTTP and JSON


    Purpose:

    The purpose of this test is to verify that EUT supports JSON BulkData
    collection over HTTP.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Use BulkData collection using HTTPS and JSON usp_conformance.tcl usp_conformance_10_2 Use BulkData collection using HTTPS and JSON


    Purpose:

    The purpose of this test is to verify that EUT supports JSON BulkData
    collection over HTTPS.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Use BulkData collection using HTTP and CSV usp_conformance.tcl usp_conformance_10_3 Use BulkData collection using HTTP and CSV


    Purpose:

    The purpose of this test is to verify that EUT supports CSV BulkData
    collection over HTTP.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Use BulkData collection using HTTPS and CSV usp_conformance.tcl usp_conformance_10_4 Use BulkData collection using HTTPS and CSV


    Purpose:

    The purpose of this test is to verify that EUT supports CSV BulkData
    collection over HTTPS.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Use BulkData collection using HTTP and URI Parameters usp_conformance.tcl usp_conformance_10_5 Use BulkData collection using HTTP and URI Parameters


    Purpose:

    The purpose of this test is to verify that EUT supports BulkData collection
    over HTTP with extra URI parameters.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Use BulkData collection using HTTPS and URI Parameters usp_conformance.tcl usp_conformance_10_6 Use BulkData collection using HTTPS and URI Parameters


    Purpose:

    The purpose of this test is to verify that EUT supports BulkData collection
    over HTTPS with extra URI parameters.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Use BulkData collection retry mechanism over HTTP usp_conformance.tcl usp_conformance_10_7 Use BulkData collection retry mechanism over HTTP


    Purpose:

    The purpose of this test is to verify that EUT supports BulkData collection
    retry mechanism.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Use BulkData collection using HTTP with wildcard parameter usp_conformance.tcl usp_conformance_10_8 Use BulkData collection using HTTP with wildcard parameter


    Purpose:

    The purpose of this test is to verify that EUT supports BulkData collection
    over HTTP with a wildcarded parameter


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Use BulkData collection using HTTP with Object Path usp_conformance.tcl usp_conformance_10_9 Use BulkData collection using HTTP with Object Path


    Purpose:

    The purpose of this test is to verify that EUT supports BulkData collection
    over HTTP with an Object Path.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Use BulkData collection using Push event usp_conformance.tcl usp_conformance_10_10 Use BulkData collection using Push event


    Purpose:

    The purpose of this test is to verify that EUT supports BulkData collection
    via the Push event.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Use BulkData collection using Push event with wildcard parameter usp_conformance.tcl usp_conformance_10_11 Use BulkData collection using Push event with wildcard parameter


    Purpose:

    The purpose of this test is to verify that EUT supports BulkData collection
    via the Push event using a wildcard path.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/

Test Module Name Synopsis
Use BulkData collection using Push event with Object Path usp_conformance.tcl usp_conformance_10_12 Use BulkData collection using Push event with Object Path


    Purpose:

    The purpose of this test is to verify that EUT supports BulkData collection
    via the Push event using an object path.


    References:

    BBF TP-469 Issue 1 Amendment 1 "Conformance Test Plan for USP Agents"

    https://usp-compliance.broadband-forum.org/


USP_Device2_profiles.tcl

TR-181 Issue 2 USP profile testing for Device:2 root data model

Test Module Name Synopsis
Verify USP_Device2 MemoryStatus Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_MemoryStatus_get_1 Verify USP_Device2 MemoryStatus Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MemoryStatus Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_MemoryStatus_gsdm_4 Verify USP_Device2 MemoryStatus Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MemoryStatus Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_MemoryStatus_gsdm_req_5 Verify USP_Device2 MemoryStatus Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ProcessStatus Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_ProcessStatus_get_1 Verify USP_Device2 ProcessStatus Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ProcessStatus Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_ProcessStatus_gsdm_4 Verify USP_Device2 ProcessStatus Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ProcessStatus Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_ProcessStatus_gsdm_req_5 Verify USP_Device2 ProcessStatus Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 TempStatus Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_TempStatus_get_1 Verify USP_Device2 TempStatus Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 TempStatus Profile using Set message USP_Device2_profiles.tcl USP_Device2_TempStatus_set_2 Verify USP_Device2 TempStatus Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 TempStatus Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_TempStatus_gsdm_4 Verify USP_Device2 TempStatus Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 TempStatus Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_TempStatus_gsdm_req_5 Verify USP_Device2 TempStatus Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Processors Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_Processors_get_1 Verify USP_Device2 Processors Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Processors Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_Processors_gsdm_4 Verify USP_Device2 Processors Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Processors Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_Processors_gsdm_req_5 Verify USP_Device2 Processors Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 VendorLogFiles Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_VendorLogFiles_get_1 Verify USP_Device2 VendorLogFiles Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 VendorLogFiles Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_VendorLogFiles_gsdm_4 Verify USP_Device2 VendorLogFiles Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 VendorLogFiles Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_VendorLogFiles_gsdm_req_5 Verify USP_Device2 VendorLogFiles Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Location Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_Location_get_1 Verify USP_Device2 Location Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Location Profile using Set message USP_Device2_profiles.tcl USP_Device2_Location_set_2 Verify USP_Device2 Location Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Location Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_Location_ado_3 Verify USP_Device2 Location Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Location Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_Location_gsdm_4 Verify USP_Device2 Location Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Location Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_Location_gsdm_req_5 Verify USP_Device2 Location Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DeviceImage Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_DeviceImage_get_1 Verify USP_Device2 DeviceImage Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DeviceImage Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_DeviceImage_gsdm_4 Verify USP_Device2 DeviceImage Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DeviceImage Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_DeviceImage_gsdm_req_5 Verify USP_Device2 DeviceImage Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Time Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_Time_get_1 Verify USP_Device2 Time Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Time Profile using Set message USP_Device2_profiles.tcl USP_Device2_Time_set_2 Verify USP_Device2 Time Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Time Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_Time_gsdm_4 Verify USP_Device2 Time Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Time Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_Time_gsdm_req_5 Verify USP_Device2 Time Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UserInformationBasic Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_UserInformationBasic_get_1 Verify USP_Device2 UserInformationBasic Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UserInformationBasic Profile using Set message USP_Device2_profiles.tcl USP_Device2_UserInformationBasic_set_2 Verify USP_Device2 UserInformationBasic Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UserInformationBasic Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_UserInformationBasic_gsdm_4 Verify USP_Device2 UserInformationBasic Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UserInformationBasic Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_UserInformationBasic_gsdm_req_5 Verify USP_Device2 UserInformationBasic Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UserInformationExtended Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_UserInformationExtended_get_1 Verify USP_Device2 UserInformationExtended Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UserInformationExtended Profile using Set message USP_Device2_profiles.tcl USP_Device2_UserInformationExtended_set_2 Verify USP_Device2 UserInformationExtended Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UserInformationExtended Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_UserInformationExtended_gsdm_4 Verify USP_Device2 UserInformationExtended Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UserInformationExtended Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_UserInformationExtended_gsdm_req_5 Verify USP_Device2 UserInformationExtended Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ADSL Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_ADSL_get_1 Verify USP_Device2 ADSL Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ADSL Profile using Set message USP_Device2_profiles.tcl USP_Device2_ADSL_set_2 Verify USP_Device2 ADSL Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ADSL Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_ADSL_gsdm_4 Verify USP_Device2 ADSL Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ADSL Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_ADSL_gsdm_req_5 Verify USP_Device2 ADSL Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ADSL2 Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_ADSL2_get_1 Verify USP_Device2 ADSL2 Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ADSL2 Profile using Set message USP_Device2_profiles.tcl USP_Device2_ADSL2_set_2 Verify USP_Device2 ADSL2 Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ADSL2 Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_ADSL2_gsdm_4 Verify USP_Device2 ADSL2 Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ADSL2 Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_ADSL2_gsdm_req_5 Verify USP_Device2 ADSL2 Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 VDSL2 Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_VDSL2_get_1 Verify USP_Device2 VDSL2 Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 VDSL2 Profile using Set message USP_Device2_profiles.tcl USP_Device2_VDSL2_set_2 Verify USP_Device2 VDSL2 Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 VDSL2 Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_VDSL2_gsdm_4 Verify USP_Device2 VDSL2 Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 VDSL2 Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_VDSL2_gsdm_req_5 Verify USP_Device2 VDSL2 Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BondedDSL Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_BondedDSL_get_1 Verify USP_Device2 BondedDSL Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BondedDSL Profile using Set message USP_Device2_profiles.tcl USP_Device2_BondedDSL_set_2 Verify USP_Device2 BondedDSL Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BondedDSL Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_BondedDSL_gsdm_4 Verify USP_Device2 BondedDSL Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BondedDSL Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_BondedDSL_gsdm_req_5 Verify USP_Device2 BondedDSL Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FAST Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_FAST_get_1 Verify USP_Device2 FAST Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FAST Profile using Set message USP_Device2_profiles.tcl USP_Device2_FAST_set_2 Verify USP_Device2 FAST Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FAST Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_FAST_gsdm_4 Verify USP_Device2 FAST Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FAST Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_FAST_gsdm_req_5 Verify USP_Device2 FAST Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Optical Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_Optical_get_1 Verify USP_Device2 Optical Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Optical Profile using Set message USP_Device2_profiles.tcl USP_Device2_Optical_set_2 Verify USP_Device2 Optical Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Optical Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_Optical_gsdm_4 Verify USP_Device2 Optical Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Optical Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_Optical_gsdm_req_5 Verify USP_Device2 Optical Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 CellularInterfaceBase Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_CellularInterfaceBase_get_1 Verify USP_Device2 CellularInterfaceBase Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 CellularInterfaceBase Profile using Set message USP_Device2_profiles.tcl USP_Device2_CellularInterfaceBase_set_2 Verify USP_Device2 CellularInterfaceBase Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 CellularInterfaceBase Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_CellularInterfaceBase_ado_3 Verify USP_Device2 CellularInterfaceBase Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 CellularInterfaceBase Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_CellularInterfaceBase_gsdm_4 Verify USP_Device2 CellularInterfaceBase Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 CellularInterfaceBase Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_CellularInterfaceBase_gsdm_req_5 Verify USP_Device2 CellularInterfaceBase Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 CellularInterfaceExtended Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_CellularInterfaceExtended_get_1 Verify USP_Device2 CellularInterfaceExtended Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 CellularInterfaceExtended Profile using Set message USP_Device2_profiles.tcl USP_Device2_CellularInterfaceExtended_set_2 Verify USP_Device2 CellularInterfaceExtended Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 CellularInterfaceExtended Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_CellularInterfaceExtended_ado_3 Verify USP_Device2 CellularInterfaceExtended Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 CellularInterfaceExtended Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_CellularInterfaceExtended_gsdm_4 Verify USP_Device2 CellularInterfaceExtended Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 CellularInterfaceExtended Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_CellularInterfaceExtended_gsdm_req_5 Verify USP_Device2 CellularInterfaceExtended Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 CellularInterfaceStats Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_CellularInterfaceStats_get_1 Verify USP_Device2 CellularInterfaceStats Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 CellularInterfaceStats Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_CellularInterfaceStats_gsdm_4 Verify USP_Device2 CellularInterfaceStats Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 CellularInterfaceStats Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_CellularInterfaceStats_gsdm_req_5 Verify USP_Device2 CellularInterfaceStats Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ATMLink Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_ATMLink_get_1 Verify USP_Device2 ATMLink Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ATMLink Profile using Set message USP_Device2_profiles.tcl USP_Device2_ATMLink_set_2 Verify USP_Device2 ATMLink Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ATMLink Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_ATMLink_ado_3 Verify USP_Device2 ATMLink Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ATMLink Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_ATMLink_gsdm_4 Verify USP_Device2 ATMLink Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ATMLink Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_ATMLink_gsdm_req_5 Verify USP_Device2 ATMLink Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 PTMLink Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_PTMLink_get_1 Verify USP_Device2 PTMLink Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 PTMLink Profile using Set message USP_Device2_profiles.tcl USP_Device2_PTMLink_set_2 Verify USP_Device2 PTMLink Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 PTMLink Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_PTMLink_ado_3 Verify USP_Device2 PTMLink Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 PTMLink Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_PTMLink_gsdm_4 Verify USP_Device2 PTMLink Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 PTMLink Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_PTMLink_gsdm_req_5 Verify USP_Device2 PTMLink Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 EthernetRMONStats Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_EthernetRMONStats_get_1 Verify USP_Device2 EthernetRMONStats Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 EthernetRMONStats Profile using Set message USP_Device2_profiles.tcl USP_Device2_EthernetRMONStats_set_2 Verify USP_Device2 EthernetRMONStats Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 EthernetRMONStats Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_EthernetRMONStats_gsdm_4 Verify USP_Device2 EthernetRMONStats Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 EthernetRMONStats Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_EthernetRMONStats_gsdm_req_5 Verify USP_Device2 EthernetRMONStats Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 VLANTermination Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_VLANTermination_get_1 Verify USP_Device2 VLANTermination Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 VLANTermination Profile using Set message USP_Device2_profiles.tcl USP_Device2_VLANTermination_set_2 Verify USP_Device2 VLANTermination Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 VLANTermination Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_VLANTermination_ado_3 Verify USP_Device2 VLANTermination Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 VLANTermination Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_VLANTermination_gsdm_4 Verify USP_Device2 VLANTermination Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 VLANTermination Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_VLANTermination_gsdm_req_5 Verify USP_Device2 VLANTermination Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 EthernetLink Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_EthernetLink_get_1 Verify USP_Device2 EthernetLink Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 EthernetLink Profile using Set message USP_Device2_profiles.tcl USP_Device2_EthernetLink_set_2 Verify USP_Device2 EthernetLink Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 EthernetLink Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_EthernetLink_ado_3 Verify USP_Device2 EthernetLink Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 EthernetLink Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_EthernetLink_gsdm_4 Verify USP_Device2 EthernetLink Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 EthernetLink Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_EthernetLink_gsdm_req_5 Verify USP_Device2 EthernetLink Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 EthernetInterface Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_EthernetInterface_get_1 Verify USP_Device2 EthernetInterface Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 EthernetInterface Profile using Set message USP_Device2_profiles.tcl USP_Device2_EthernetInterface_set_2 Verify USP_Device2 EthernetInterface Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 EthernetInterface Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_EthernetInterface_gsdm_4 Verify USP_Device2 EthernetInterface Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 EthernetInterface Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_EthernetInterface_gsdm_req_5 Verify USP_Device2 EthernetInterface Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 USBHostsBasic Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_USBHostsBasic_get_1 Verify USP_Device2 USBHostsBasic Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 USBHostsBasic Profile using Set message USP_Device2_profiles.tcl USP_Device2_USBHostsBasic_set_2 Verify USP_Device2 USBHostsBasic Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 USBHostsBasic Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_USBHostsBasic_gsdm_4 Verify USP_Device2 USBHostsBasic Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 USBHostsBasic Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_USBHostsBasic_gsdm_req_5 Verify USP_Device2 USBHostsBasic Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 USBInterface Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_USBInterface_get_1 Verify USP_Device2 USBInterface Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 USBInterface Profile using Set message USP_Device2_profiles.tcl USP_Device2_USBInterface_set_2 Verify USP_Device2 USBInterface Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 USBInterface Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_USBInterface_gsdm_4 Verify USP_Device2 USBInterface Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 USBInterface Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_USBInterface_gsdm_req_5 Verify USP_Device2 USBInterface Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 USBPort Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_USBPort_get_1 Verify USP_Device2 USBPort Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 USBPort Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_USBPort_gsdm_4 Verify USP_Device2 USBPort Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 USBPort Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_USBPort_gsdm_req_5 Verify USP_Device2 USBPort Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 HPNA Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_HPNA_get_1 Verify USP_Device2 HPNA Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 HPNA Profile using Set message USP_Device2_profiles.tcl USP_Device2_HPNA_set_2 Verify USP_Device2 HPNA Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 HPNA Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_HPNA_gsdm_4 Verify USP_Device2 HPNA Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 HPNA Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_HPNA_gsdm_req_5 Verify USP_Device2 HPNA Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 HPNAQoS Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_HPNAQoS_get_1 Verify USP_Device2 HPNAQoS Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 HPNAQoS Profile using Set message USP_Device2_profiles.tcl USP_Device2_HPNAQoS_set_2 Verify USP_Device2 HPNAQoS Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 HPNAQoS Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_HPNAQoS_ado_3 Verify USP_Device2 HPNAQoS Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 HPNAQoS Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_HPNAQoS_gsdm_4 Verify USP_Device2 HPNAQoS Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 HPNAQoS Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_HPNAQoS_gsdm_req_5 Verify USP_Device2 HPNAQoS Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MoCA Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_MoCA_get_1 Verify USP_Device2 MoCA Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MoCA Profile using Set message USP_Device2_profiles.tcl USP_Device2_MoCA_set_2 Verify USP_Device2 MoCA Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MoCA Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_MoCA_gsdm_4 Verify USP_Device2 MoCA Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MoCA Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_MoCA_gsdm_req_5 Verify USP_Device2 MoCA Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Ghn Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_Ghn_get_1 Verify USP_Device2 Ghn Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Ghn Profile using Set message USP_Device2_profiles.tcl USP_Device2_Ghn_set_2 Verify USP_Device2 Ghn Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Ghn Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_Ghn_gsdm_4 Verify USP_Device2 Ghn Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Ghn Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_Ghn_gsdm_req_5 Verify USP_Device2 Ghn Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 HomePlug Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_HomePlug_get_1 Verify USP_Device2 HomePlug Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 HomePlug Profile using Set message USP_Device2_profiles.tcl USP_Device2_HomePlug_set_2 Verify USP_Device2 HomePlug Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 HomePlug Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_HomePlug_gsdm_4 Verify USP_Device2 HomePlug Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 HomePlug Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_HomePlug_gsdm_req_5 Verify USP_Device2 HomePlug Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UPA Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_UPA_get_1 Verify USP_Device2 UPA Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UPA Profile using Set message USP_Device2_profiles.tcl USP_Device2_UPA_set_2 Verify USP_Device2 UPA Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UPA Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_UPA_ado_3 Verify USP_Device2 UPA Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UPA Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_UPA_gsdm_4 Verify USP_Device2 UPA Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UPA Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_UPA_gsdm_req_5 Verify USP_Device2 UPA Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 WiFiRadio Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_WiFiRadio_get_1 Verify USP_Device2 WiFiRadio Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 WiFiRadio Profile using Set message USP_Device2_profiles.tcl USP_Device2_WiFiRadio_set_2 Verify USP_Device2 WiFiRadio Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 WiFiRadio Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_WiFiRadio_gsdm_4 Verify USP_Device2 WiFiRadio Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 WiFiRadio Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_WiFiRadio_gsdm_req_5 Verify USP_Device2 WiFiRadio Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 WiFiSSID Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_WiFiSSID_get_1 Verify USP_Device2 WiFiSSID Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 WiFiSSID Profile using Set message USP_Device2_profiles.tcl USP_Device2_WiFiSSID_set_2 Verify USP_Device2 WiFiSSID Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 WiFiSSID Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_WiFiSSID_ado_3 Verify USP_Device2 WiFiSSID Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 WiFiSSID Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_WiFiSSID_gsdm_4 Verify USP_Device2 WiFiSSID Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 WiFiSSID Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_WiFiSSID_gsdm_req_5 Verify USP_Device2 WiFiSSID Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 WiFiAccessPoint Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_WiFiAccessPoint_get_1 Verify USP_Device2 WiFiAccessPoint Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 WiFiAccessPoint Profile using Set message USP_Device2_profiles.tcl USP_Device2_WiFiAccessPoint_set_2 Verify USP_Device2 WiFiAccessPoint Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 WiFiAccessPoint Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_WiFiAccessPoint_ado_3 Verify USP_Device2 WiFiAccessPoint Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 WiFiAccessPoint Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_WiFiAccessPoint_gsdm_4 Verify USP_Device2 WiFiAccessPoint Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 WiFiAccessPoint Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_WiFiAccessPoint_gsdm_req_5 Verify USP_Device2 WiFiAccessPoint Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 WiFiEndPoint Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_WiFiEndPoint_get_1 Verify USP_Device2 WiFiEndPoint Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 WiFiEndPoint Profile using Set message USP_Device2_profiles.tcl USP_Device2_WiFiEndPoint_set_2 Verify USP_Device2 WiFiEndPoint Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 WiFiEndPoint Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_WiFiEndPoint_ado_3 Verify USP_Device2 WiFiEndPoint Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 WiFiEndPoint Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_WiFiEndPoint_gsdm_4 Verify USP_Device2 WiFiEndPoint Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 WiFiEndPoint Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_WiFiEndPoint_gsdm_req_5 Verify USP_Device2 WiFiEndPoint Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ZigBeeInterface Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_ZigBeeInterface_get_1 Verify USP_Device2 ZigBeeInterface Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ZigBeeInterface Profile using Set message USP_Device2_profiles.tcl USP_Device2_ZigBeeInterface_set_2 Verify USP_Device2 ZigBeeInterface Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ZigBeeInterface Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_ZigBeeInterface_gsdm_4 Verify USP_Device2 ZigBeeInterface Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ZigBeeInterface Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_ZigBeeInterface_gsdm_req_5 Verify USP_Device2 ZigBeeInterface Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ZigBeeAssociatedDevices Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_ZigBeeAssociatedDevices_get_1 Verify USP_Device2 ZigBeeAssociatedDevices Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ZigBeeAssociatedDevices Profile using Set message USP_Device2_profiles.tcl USP_Device2_ZigBeeAssociatedDevices_set_2 Verify USP_Device2 ZigBeeAssociatedDevices Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ZigBeeAssociatedDevices Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_ZigBeeAssociatedDevices_gsdm_4 Verify USP_Device2 ZigBeeAssociatedDevices Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ZigBeeAssociatedDevices Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_ZigBeeAssociatedDevices_gsdm_req_5 Verify USP_Device2 ZigBeeAssociatedDevices Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ZigBeeDisc Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_ZigBeeDisc_get_1 Verify USP_Device2 ZigBeeDisc Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ZigBeeDisc Profile using Set message USP_Device2_profiles.tcl USP_Device2_ZigBeeDisc_set_2 Verify USP_Device2 ZigBeeDisc Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ZigBeeDisc Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_ZigBeeDisc_ado_3 Verify USP_Device2 ZigBeeDisc Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ZigBeeDisc Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_ZigBeeDisc_gsdm_4 Verify USP_Device2 ZigBeeDisc Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ZigBeeDisc Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_ZigBeeDisc_gsdm_req_5 Verify USP_Device2 ZigBeeDisc Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ZDOBasic Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_ZDOBasic_get_1 Verify USP_Device2 ZDOBasic Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ZDOBasic Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_ZDOBasic_gsdm_4 Verify USP_Device2 ZDOBasic Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ZDOBasic Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_ZDOBasic_gsdm_req_5 Verify USP_Device2 ZDOBasic Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ZDOAdv Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_ZDOAdv_get_1 Verify USP_Device2 ZDOAdv Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ZDOAdv Profile using Set message USP_Device2_profiles.tcl USP_Device2_ZDOAdv_set_2 Verify USP_Device2 ZDOAdv Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ZDOAdv Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_ZDOAdv_ado_3 Verify USP_Device2 ZDOAdv Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ZDOAdv Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_ZDOAdv_gsdm_4 Verify USP_Device2 ZDOAdv Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ZDOAdv Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_ZDOAdv_gsdm_req_5 Verify USP_Device2 ZDOAdv Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ZigBeeStats Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_ZigBeeStats_get_1 Verify USP_Device2 ZigBeeStats Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ZigBeeStats Profile using Set message USP_Device2_profiles.tcl USP_Device2_ZigBeeStats_set_2 Verify USP_Device2 ZigBeeStats Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ZigBeeStats Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_ZigBeeStats_gsdm_4 Verify USP_Device2 ZigBeeStats Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ZigBeeStats Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_ZigBeeStats_gsdm_req_5 Verify USP_Device2 ZigBeeStats Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Bridge Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_Bridge_get_1 Verify USP_Device2 Bridge Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Bridge Profile using Set message USP_Device2_profiles.tcl USP_Device2_Bridge_set_2 Verify USP_Device2 Bridge Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Bridge Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_Bridge_ado_3 Verify USP_Device2 Bridge Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Bridge Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_Bridge_gsdm_4 Verify USP_Device2 Bridge Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Bridge Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_Bridge_gsdm_req_5 Verify USP_Device2 Bridge Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 VLANBridge Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_VLANBridge_get_1 Verify USP_Device2 VLANBridge Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 VLANBridge Profile using Set message USP_Device2_profiles.tcl USP_Device2_VLANBridge_set_2 Verify USP_Device2 VLANBridge Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 VLANBridge Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_VLANBridge_ado_3 Verify USP_Device2 VLANBridge Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 VLANBridge Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_VLANBridge_gsdm_4 Verify USP_Device2 VLANBridge Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 VLANBridge Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_VLANBridge_gsdm_req_5 Verify USP_Device2 VLANBridge Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BridgeFilter Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_BridgeFilter_get_1 Verify USP_Device2 BridgeFilter Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BridgeFilter Profile using Set message USP_Device2_profiles.tcl USP_Device2_BridgeFilter_set_2 Verify USP_Device2 BridgeFilter Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BridgeFilter Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_BridgeFilter_ado_3 Verify USP_Device2 BridgeFilter Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BridgeFilter Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_BridgeFilter_gsdm_4 Verify USP_Device2 BridgeFilter Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BridgeFilter Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_BridgeFilter_gsdm_req_5 Verify USP_Device2 BridgeFilter Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BridgeL3L4Filter Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_BridgeL3L4Filter_get_1 Verify USP_Device2 BridgeL3L4Filter Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BridgeL3L4Filter Profile using Set message USP_Device2_profiles.tcl USP_Device2_BridgeL3L4Filter_set_2 Verify USP_Device2 BridgeL3L4Filter Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BridgeL3L4Filter Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_BridgeL3L4Filter_ado_3 Verify USP_Device2 BridgeL3L4Filter Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BridgeL3L4Filter Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_BridgeL3L4Filter_gsdm_4 Verify USP_Device2 BridgeL3L4Filter Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BridgeL3L4Filter Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_BridgeL3L4Filter_gsdm_req_5 Verify USP_Device2 BridgeL3L4Filter Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ProviderBridge Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_ProviderBridge_get_1 Verify USP_Device2 ProviderBridge Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ProviderBridge Profile using Set message USP_Device2_profiles.tcl USP_Device2_ProviderBridge_set_2 Verify USP_Device2 ProviderBridge Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ProviderBridge Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_ProviderBridge_ado_3 Verify USP_Device2 ProviderBridge Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ProviderBridge Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_ProviderBridge_gsdm_4 Verify USP_Device2 ProviderBridge Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ProviderBridge Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_ProviderBridge_gsdm_req_5 Verify USP_Device2 ProviderBridge Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UDPEcho Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_UDPEcho_get_1 Verify USP_Device2 UDPEcho Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UDPEcho Profile using Set message USP_Device2_profiles.tcl USP_Device2_UDPEcho_set_2 Verify USP_Device2 UDPEcho Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UDPEcho Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_UDPEcho_gsdm_4 Verify USP_Device2 UDPEcho Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UDPEcho Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_UDPEcho_gsdm_req_5 Verify USP_Device2 UDPEcho Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UDPEchoPlus Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_UDPEchoPlus_get_1 Verify USP_Device2 UDPEchoPlus Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UDPEchoPlus Profile using Set message USP_Device2_profiles.tcl USP_Device2_UDPEchoPlus_set_2 Verify USP_Device2 UDPEchoPlus Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UDPEchoPlus Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_UDPEchoPlus_gsdm_4 Verify USP_Device2 UDPEchoPlus Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UDPEchoPlus Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_UDPEchoPlus_gsdm_req_5 Verify USP_Device2 UDPEchoPlus Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 TWAMPReflectorBasic Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_TWAMPReflectorBasic_get_1 Verify USP_Device2 TWAMPReflectorBasic Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 TWAMPReflectorBasic Profile using Set message USP_Device2_profiles.tcl USP_Device2_TWAMPReflectorBasic_set_2 Verify USP_Device2 TWAMPReflectorBasic Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 TWAMPReflectorBasic Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_TWAMPReflectorBasic_ado_3 Verify USP_Device2 TWAMPReflectorBasic Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 TWAMPReflectorBasic Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_TWAMPReflectorBasic_gsdm_4 Verify USP_Device2 TWAMPReflectorBasic Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 TWAMPReflectorBasic Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_TWAMPReflectorBasic_gsdm_req_5 Verify USP_Device2 TWAMPReflectorBasic Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LLDPBaseline Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_LLDPBaseline_get_1 Verify USP_Device2 LLDPBaseline Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LLDPBaseline Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_LLDPBaseline_gsdm_4 Verify USP_Device2 LLDPBaseline Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LLDPBaseline Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_LLDPBaseline_gsdm_req_5 Verify USP_Device2 LLDPBaseline Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LLDPRemOrgDefInfo Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_LLDPRemOrgDefInfo_get_1 Verify USP_Device2 LLDPRemOrgDefInfo Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LLDPRemOrgDefInfo Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_LLDPRemOrgDefInfo_gsdm_4 Verify USP_Device2 LLDPRemOrgDefInfo Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LLDPRemOrgDefInfo Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_LLDPRemOrgDefInfo_gsdm_req_5 Verify USP_Device2 LLDPRemOrgDefInfo Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPsec Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_IPsec_get_1 Verify USP_Device2 IPsec Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPsec Profile using Set message USP_Device2_profiles.tcl USP_Device2_IPsec_set_2 Verify USP_Device2 IPsec Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPsec Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_IPsec_ado_3 Verify USP_Device2 IPsec Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPsec Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_IPsec_gsdm_4 Verify USP_Device2 IPsec Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPsec Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_IPsec_gsdm_req_5 Verify USP_Device2 IPsec Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPsecAdv Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_IPsecAdv_get_1 Verify USP_Device2 IPsecAdv Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPsecAdv Profile using Set message USP_Device2_profiles.tcl USP_Device2_IPsecAdv_set_2 Verify USP_Device2 IPsecAdv Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPsecAdv Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_IPsecAdv_ado_3 Verify USP_Device2 IPsecAdv Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPsecAdv Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_IPsecAdv_gsdm_4 Verify USP_Device2 IPsecAdv Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPsecAdv Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_IPsecAdv_gsdm_req_5 Verify USP_Device2 IPsecAdv Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 GREBasic Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_GREBasic_get_1 Verify USP_Device2 GREBasic Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 GREBasic Profile using Set message USP_Device2_profiles.tcl USP_Device2_GREBasic_set_2 Verify USP_Device2 GREBasic Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 GREBasic Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_GREBasic_ado_3 Verify USP_Device2 GREBasic Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 GREBasic Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_GREBasic_gsdm_4 Verify USP_Device2 GREBasic Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 GREBasic Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_GREBasic_gsdm_req_5 Verify USP_Device2 GREBasic Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 GREAdv Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_GREAdv_get_1 Verify USP_Device2 GREAdv Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 GREAdv Profile using Set message USP_Device2_profiles.tcl USP_Device2_GREAdv_set_2 Verify USP_Device2 GREAdv Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 GREAdv Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_GREAdv_ado_3 Verify USP_Device2 GREAdv Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 GREAdv Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_GREAdv_gsdm_4 Verify USP_Device2 GREAdv Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 GREAdv Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_GREAdv_gsdm_req_5 Verify USP_Device2 GREAdv Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 L2TPv3Basic Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_L2TPv3Basic_get_1 Verify USP_Device2 L2TPv3Basic Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 L2TPv3Basic Profile using Set message USP_Device2_profiles.tcl USP_Device2_L2TPv3Basic_set_2 Verify USP_Device2 L2TPv3Basic Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 L2TPv3Basic Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_L2TPv3Basic_ado_3 Verify USP_Device2 L2TPv3Basic Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 L2TPv3Basic Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_L2TPv3Basic_gsdm_4 Verify USP_Device2 L2TPv3Basic Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 L2TPv3Basic Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_L2TPv3Basic_gsdm_req_5 Verify USP_Device2 L2TPv3Basic Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 L2TPv3Adv Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_L2TPv3Adv_get_1 Verify USP_Device2 L2TPv3Adv Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 L2TPv3Adv Profile using Set message USP_Device2_profiles.tcl USP_Device2_L2TPv3Adv_set_2 Verify USP_Device2 L2TPv3Adv Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 L2TPv3Adv Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_L2TPv3Adv_ado_3 Verify USP_Device2 L2TPv3Adv Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 L2TPv3Adv Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_L2TPv3Adv_gsdm_4 Verify USP_Device2 L2TPv3Adv Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 L2TPv3Adv Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_L2TPv3Adv_gsdm_req_5 Verify USP_Device2 L2TPv3Adv Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 VXLANBasic Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_VXLANBasic_get_1 Verify USP_Device2 VXLANBasic Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 VXLANBasic Profile using Set message USP_Device2_profiles.tcl USP_Device2_VXLANBasic_set_2 Verify USP_Device2 VXLANBasic Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 VXLANBasic Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_VXLANBasic_ado_3 Verify USP_Device2 VXLANBasic Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 VXLANBasic Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_VXLANBasic_gsdm_4 Verify USP_Device2 VXLANBasic Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 VXLANBasic Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_VXLANBasic_gsdm_req_5 Verify USP_Device2 VXLANBasic Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 VXLANAdv Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_VXLANAdv_get_1 Verify USP_Device2 VXLANAdv Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 VXLANAdv Profile using Set message USP_Device2_profiles.tcl USP_Device2_VXLANAdv_set_2 Verify USP_Device2 VXLANAdv Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 VXLANAdv Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_VXLANAdv_ado_3 Verify USP_Device2 VXLANAdv Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 VXLANAdv Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_VXLANAdv_gsdm_4 Verify USP_Device2 VXLANAdv Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 VXLANAdv Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_VXLANAdv_gsdm_req_5 Verify USP_Device2 VXLANAdv Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MAPBasic Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_MAPBasic_get_1 Verify USP_Device2 MAPBasic Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MAPBasic Profile using Set message USP_Device2_profiles.tcl USP_Device2_MAPBasic_set_2 Verify USP_Device2 MAPBasic Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MAPBasic Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_MAPBasic_ado_3 Verify USP_Device2 MAPBasic Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MAPBasic Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_MAPBasic_gsdm_4 Verify USP_Device2 MAPBasic Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MAPBasic Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_MAPBasic_gsdm_req_5 Verify USP_Device2 MAPBasic Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MAPAdv Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_MAPAdv_get_1 Verify USP_Device2 MAPAdv Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MAPAdv Profile using Set message USP_Device2_profiles.tcl USP_Device2_MAPAdv_set_2 Verify USP_Device2 MAPAdv Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MAPAdv Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_MAPAdv_ado_3 Verify USP_Device2 MAPAdv Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MAPAdv Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_MAPAdv_gsdm_4 Verify USP_Device2 MAPAdv Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MAPAdv Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_MAPAdv_gsdm_req_5 Verify USP_Device2 MAPAdv Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 CaptivePortal Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_CaptivePortal_get_1 Verify USP_Device2 CaptivePortal Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 CaptivePortal Profile using Set message USP_Device2_profiles.tcl USP_Device2_CaptivePortal_set_2 Verify USP_Device2 CaptivePortal Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 CaptivePortal Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_CaptivePortal_gsdm_4 Verify USP_Device2 CaptivePortal Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 CaptivePortal Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_CaptivePortal_gsdm_req_5 Verify USP_Device2 CaptivePortal Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Routing Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_Routing_get_1 Verify USP_Device2 Routing Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Routing Profile using Set message USP_Device2_profiles.tcl USP_Device2_Routing_set_2 Verify USP_Device2 Routing Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Routing Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_Routing_ado_3 Verify USP_Device2 Routing Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Routing Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_Routing_gsdm_4 Verify USP_Device2 Routing Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Routing Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_Routing_gsdm_req_5 Verify USP_Device2 Routing Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPv6Routing Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_IPv6Routing_get_1 Verify USP_Device2 IPv6Routing Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPv6Routing Profile using Set message USP_Device2_profiles.tcl USP_Device2_IPv6Routing_set_2 Verify USP_Device2 IPv6Routing Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPv6Routing Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_IPv6Routing_ado_3 Verify USP_Device2 IPv6Routing Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPv6Routing Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_IPv6Routing_gsdm_4 Verify USP_Device2 IPv6Routing Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPv6Routing Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_IPv6Routing_gsdm_req_5 Verify USP_Device2 IPv6Routing Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPInterface Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_IPInterface_get_1 Verify USP_Device2 IPInterface Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPInterface Profile using Set message USP_Device2_profiles.tcl USP_Device2_IPInterface_set_2 Verify USP_Device2 IPInterface Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPInterface Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_IPInterface_ado_3 Verify USP_Device2 IPInterface Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPInterface Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_IPInterface_gsdm_4 Verify USP_Device2 IPInterface Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPInterface Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_IPInterface_gsdm_req_5 Verify USP_Device2 IPInterface Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Babel Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_Babel_get_1 Verify USP_Device2 Babel Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Babel Profile using Set message USP_Device2_profiles.tcl USP_Device2_Babel_set_2 Verify USP_Device2 Babel Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Babel Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_Babel_gsdm_4 Verify USP_Device2 Babel Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Babel Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_Babel_gsdm_req_5 Verify USP_Device2 Babel Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BabelMAC Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_BabelMAC_get_1 Verify USP_Device2 BabelMAC Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BabelMAC Profile using Set message USP_Device2_profiles.tcl USP_Device2_BabelMAC_set_2 Verify USP_Device2 BabelMAC Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BabelMAC Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_BabelMAC_ado_3 Verify USP_Device2 BabelMAC Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BabelMAC Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_BabelMAC_gsdm_4 Verify USP_Device2 BabelMAC Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BabelMAC Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_BabelMAC_gsdm_req_5 Verify USP_Device2 BabelMAC Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BabelDTLS Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_BabelDTLS_get_1 Verify USP_Device2 BabelDTLS Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BabelDTLS Profile using Set message USP_Device2_profiles.tcl USP_Device2_BabelDTLS_set_2 Verify USP_Device2 BabelDTLS Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BabelDTLS Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_BabelDTLS_ado_3 Verify USP_Device2 BabelDTLS Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BabelDTLS Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_BabelDTLS_gsdm_4 Verify USP_Device2 BabelDTLS Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BabelDTLS Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_BabelDTLS_gsdm_req_5 Verify USP_Device2 BabelDTLS Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 NeighborDiscovery Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_NeighborDiscovery_get_1 Verify USP_Device2 NeighborDiscovery Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 NeighborDiscovery Profile using Set message USP_Device2_profiles.tcl USP_Device2_NeighborDiscovery_set_2 Verify USP_Device2 NeighborDiscovery Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 NeighborDiscovery Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_NeighborDiscovery_ado_3 Verify USP_Device2 NeighborDiscovery Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 NeighborDiscovery Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_NeighborDiscovery_gsdm_4 Verify USP_Device2 NeighborDiscovery Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 NeighborDiscovery Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_NeighborDiscovery_gsdm_req_5 Verify USP_Device2 NeighborDiscovery Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 RouterAdvertisement Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_RouterAdvertisement_get_1 Verify USP_Device2 RouterAdvertisement Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 RouterAdvertisement Profile using Set message USP_Device2_profiles.tcl USP_Device2_RouterAdvertisement_set_2 Verify USP_Device2 RouterAdvertisement Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 RouterAdvertisement Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_RouterAdvertisement_ado_3 Verify USP_Device2 RouterAdvertisement Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 RouterAdvertisement Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_RouterAdvertisement_gsdm_4 Verify USP_Device2 RouterAdvertisement Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 RouterAdvertisement Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_RouterAdvertisement_gsdm_req_5 Verify USP_Device2 RouterAdvertisement Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPv6rd Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_IPv6rd_get_1 Verify USP_Device2 IPv6rd Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPv6rd Profile using Set message USP_Device2_profiles.tcl USP_Device2_IPv6rd_set_2 Verify USP_Device2 IPv6rd Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPv6rd Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_IPv6rd_gsdm_4 Verify USP_Device2 IPv6rd Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPv6rd Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_IPv6rd_gsdm_req_5 Verify USP_Device2 IPv6rd Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DSLite Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_DSLite_get_1 Verify USP_Device2 DSLite Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DSLite Profile using Set message USP_Device2_profiles.tcl USP_Device2_DSLite_set_2 Verify USP_Device2 DSLite Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DSLite Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_DSLite_gsdm_4 Verify USP_Device2 DSLite Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DSLite Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_DSLite_gsdm_req_5 Verify USP_Device2 DSLite Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ProviderBridgeQoS Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_ProviderBridgeQoS_get_1 Verify USP_Device2 ProviderBridgeQoS Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ProviderBridgeQoS Profile using Set message USP_Device2_profiles.tcl USP_Device2_ProviderBridgeQoS_set_2 Verify USP_Device2 ProviderBridgeQoS Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ProviderBridgeQoS Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_ProviderBridgeQoS_ado_3 Verify USP_Device2 ProviderBridgeQoS Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ProviderBridgeQoS Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_ProviderBridgeQoS_gsdm_4 Verify USP_Device2 ProviderBridgeQoS Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ProviderBridgeQoS Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_ProviderBridgeQoS_gsdm_req_5 Verify USP_Device2 ProviderBridgeQoS Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 QoS Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_QoS_get_1 Verify USP_Device2 QoS Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 QoS Profile using Set message USP_Device2_profiles.tcl USP_Device2_QoS_set_2 Verify USP_Device2 QoS Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 QoS Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_QoS_ado_3 Verify USP_Device2 QoS Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 QoS Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_QoS_gsdm_4 Verify USP_Device2 QoS Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 QoS Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_QoS_gsdm_req_5 Verify USP_Device2 QoS Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 QoSDynamicFlow Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_QoSDynamicFlow_get_1 Verify USP_Device2 QoSDynamicFlow Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 QoSDynamicFlow Profile using Set message USP_Device2_profiles.tcl USP_Device2_QoSDynamicFlow_set_2 Verify USP_Device2 QoSDynamicFlow Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 QoSDynamicFlow Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_QoSDynamicFlow_ado_3 Verify USP_Device2 QoSDynamicFlow Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 QoSDynamicFlow Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_QoSDynamicFlow_gsdm_4 Verify USP_Device2 QoSDynamicFlow Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 QoSDynamicFlow Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_QoSDynamicFlow_gsdm_req_5 Verify USP_Device2 QoSDynamicFlow Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 QoSStats Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_QoSStats_get_1 Verify USP_Device2 QoSStats Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 QoSStats Profile using Set message USP_Device2_profiles.tcl USP_Device2_QoSStats_set_2 Verify USP_Device2 QoSStats Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 QoSStats Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_QoSStats_ado_3 Verify USP_Device2 QoSStats Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 QoSStats Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_QoSStats_gsdm_4 Verify USP_Device2 QoSStats Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 QoSStats Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_QoSStats_gsdm_req_5 Verify USP_Device2 QoSStats Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Hosts Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_Hosts_get_1 Verify USP_Device2 Hosts Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Hosts Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_Hosts_gsdm_4 Verify USP_Device2 Hosts Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Hosts Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_Hosts_gsdm_req_5 Verify USP_Device2 Hosts Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 AccessControl Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_AccessControl_get_1 Verify USP_Device2 AccessControl Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 AccessControl Profile using Set message USP_Device2_profiles.tcl USP_Device2_AccessControl_set_2 Verify USP_Device2 AccessControl Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 AccessControl Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_AccessControl_gsdm_4 Verify USP_Device2 AccessControl Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 AccessControl Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_AccessControl_gsdm_req_5 Verify USP_Device2 AccessControl Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DNSRelay Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_DNSRelay_get_1 Verify USP_Device2 DNSRelay Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DNSRelay Profile using Set message USP_Device2_profiles.tcl USP_Device2_DNSRelay_set_2 Verify USP_Device2 DNSRelay Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DNSRelay Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_DNSRelay_ado_3 Verify USP_Device2 DNSRelay Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DNSRelay Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_DNSRelay_gsdm_4 Verify USP_Device2 DNSRelay Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DNSRelay Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_DNSRelay_gsdm_req_5 Verify USP_Device2 DNSRelay Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DNS_SD Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_DNS_SD_get_1 Verify USP_Device2 DNS_SD Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DNS_SD Profile using Set message USP_Device2_profiles.tcl USP_Device2_DNS_SD_set_2 Verify USP_Device2 DNS_SD Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DNS_SD Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_DNS_SD_gsdm_4 Verify USP_Device2 DNS_SD Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DNS_SD Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_DNS_SD_gsdm_req_5 Verify USP_Device2 DNS_SD Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 NAT Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_NAT_get_1 Verify USP_Device2 NAT Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 NAT Profile using Set message USP_Device2_profiles.tcl USP_Device2_NAT_set_2 Verify USP_Device2 NAT Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 NAT Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_NAT_ado_3 Verify USP_Device2 NAT Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 NAT Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_NAT_gsdm_4 Verify USP_Device2 NAT Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 NAT Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_NAT_gsdm_req_5 Verify USP_Device2 NAT Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv4Server Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_DHCPv4Server_get_1 Verify USP_Device2 DHCPv4Server Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv4Server Profile using Set message USP_Device2_profiles.tcl USP_Device2_DHCPv4Server_set_2 Verify USP_Device2 DHCPv4Server Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv4Server Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_DHCPv4Server_ado_3 Verify USP_Device2 DHCPv4Server Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv4Server Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_DHCPv4Server_gsdm_4 Verify USP_Device2 DHCPv4Server Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv4Server Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_DHCPv4Server_gsdm_req_5 Verify USP_Device2 DHCPv4Server Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv4CondServing Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_DHCPv4CondServing_get_1 Verify USP_Device2 DHCPv4CondServing Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv4CondServing Profile using Set message USP_Device2_profiles.tcl USP_Device2_DHCPv4CondServing_set_2 Verify USP_Device2 DHCPv4CondServing Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv4CondServing Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_DHCPv4CondServing_ado_3 Verify USP_Device2 DHCPv4CondServing Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv4CondServing Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_DHCPv4CondServing_gsdm_4 Verify USP_Device2 DHCPv4CondServing Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv4CondServing Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_DHCPv4CondServing_gsdm_req_5 Verify USP_Device2 DHCPv4CondServing Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv4Relay Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_DHCPv4Relay_get_1 Verify USP_Device2 DHCPv4Relay Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv4Relay Profile using Set message USP_Device2_profiles.tcl USP_Device2_DHCPv4Relay_set_2 Verify USP_Device2 DHCPv4Relay Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv4Relay Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_DHCPv4Relay_ado_3 Verify USP_Device2 DHCPv4Relay Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv4Relay Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_DHCPv4Relay_gsdm_4 Verify USP_Device2 DHCPv4Relay Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv4Relay Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_DHCPv4Relay_gsdm_req_5 Verify USP_Device2 DHCPv4Relay Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv4ServerClientInfo Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_DHCPv4ServerClientInfo_get_1 Verify USP_Device2 DHCPv4ServerClientInfo Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv4ServerClientInfo Profile using Set message USP_Device2_profiles.tcl USP_Device2_DHCPv4ServerClientInfo_set_2 Verify USP_Device2 DHCPv4ServerClientInfo Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv4ServerClientInfo Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_DHCPv4ServerClientInfo_ado_3 Verify USP_Device2 DHCPv4ServerClientInfo Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv4ServerClientInfo Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_DHCPv4ServerClientInfo_gsdm_4 Verify USP_Device2 DHCPv4ServerClientInfo Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv4ServerClientInfo Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_DHCPv4ServerClientInfo_gsdm_req_5 Verify USP_Device2 DHCPv4ServerClientInfo Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv6Client Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_DHCPv6Client_get_1 Verify USP_Device2 DHCPv6Client Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv6Client Profile using Set message USP_Device2_profiles.tcl USP_Device2_DHCPv6Client_set_2 Verify USP_Device2 DHCPv6Client Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv6Client Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_DHCPv6Client_ado_3 Verify USP_Device2 DHCPv6Client Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv6Client Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_DHCPv6Client_gsdm_4 Verify USP_Device2 DHCPv6Client Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv6Client Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_DHCPv6Client_gsdm_req_5 Verify USP_Device2 DHCPv6Client Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv6Server Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_DHCPv6Server_get_1 Verify USP_Device2 DHCPv6Server Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv6Server Profile using Set message USP_Device2_profiles.tcl USP_Device2_DHCPv6Server_set_2 Verify USP_Device2 DHCPv6Server Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv6Server Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_DHCPv6Server_ado_3 Verify USP_Device2 DHCPv6Server Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv6Server Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_DHCPv6Server_gsdm_4 Verify USP_Device2 DHCPv6Server Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv6Server Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_DHCPv6Server_gsdm_req_5 Verify USP_Device2 DHCPv6Server Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv6ServerAdv Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_DHCPv6ServerAdv_get_1 Verify USP_Device2 DHCPv6ServerAdv Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv6ServerAdv Profile using Set message USP_Device2_profiles.tcl USP_Device2_DHCPv6ServerAdv_set_2 Verify USP_Device2 DHCPv6ServerAdv Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv6ServerAdv Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_DHCPv6ServerAdv_ado_3 Verify USP_Device2 DHCPv6ServerAdv Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv6ServerAdv Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_DHCPv6ServerAdv_gsdm_4 Verify USP_Device2 DHCPv6ServerAdv Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv6ServerAdv Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_DHCPv6ServerAdv_gsdm_req_5 Verify USP_Device2 DHCPv6ServerAdv Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv6ServerClientInfo Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_DHCPv6ServerClientInfo_get_1 Verify USP_Device2 DHCPv6ServerClientInfo Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv6ServerClientInfo Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_DHCPv6ServerClientInfo_ado_3 Verify USP_Device2 DHCPv6ServerClientInfo Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv6ServerClientInfo Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_DHCPv6ServerClientInfo_gsdm_4 Verify USP_Device2 DHCPv6ServerClientInfo Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv6ServerClientInfo Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_DHCPv6ServerClientInfo_gsdm_req_5 Verify USP_Device2 DHCPv6ServerClientInfo Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE8021xAuthentication Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_IEEE8021xAuthentication_get_1 Verify USP_Device2 IEEE8021xAuthentication Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE8021xAuthentication Profile using Set message USP_Device2_profiles.tcl USP_Device2_IEEE8021xAuthentication_set_2 Verify USP_Device2 IEEE8021xAuthentication Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE8021xAuthentication Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_IEEE8021xAuthentication_ado_3 Verify USP_Device2 IEEE8021xAuthentication Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE8021xAuthentication Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_IEEE8021xAuthentication_gsdm_4 Verify USP_Device2 IEEE8021xAuthentication Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE8021xAuthentication Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_IEEE8021xAuthentication_gsdm_req_5 Verify USP_Device2 IEEE8021xAuthentication Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv4Client Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_DHCPv4Client_get_1 Verify USP_Device2 DHCPv4Client Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv4Client Profile using Set message USP_Device2_profiles.tcl USP_Device2_DHCPv4Client_set_2 Verify USP_Device2 DHCPv4Client Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv4Client Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_DHCPv4Client_ado_3 Verify USP_Device2 DHCPv4Client Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv4Client Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_DHCPv4Client_gsdm_4 Verify USP_Device2 DHCPv4Client Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv4Client Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_DHCPv4Client_gsdm_req_5 Verify USP_Device2 DHCPv4Client Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 User Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_User_get_1 Verify USP_Device2 User Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 User Profile using Set message USP_Device2_profiles.tcl USP_Device2_User_set_2 Verify USP_Device2 User Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 User Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_User_ado_3 Verify USP_Device2 User Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 User Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_User_gsdm_4 Verify USP_Device2 User Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 User Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_User_gsdm_req_5 Verify USP_Device2 User Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UPnPDev Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_UPnPDev_get_1 Verify USP_Device2 UPnPDev Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UPnPDev Profile using Set message USP_Device2_profiles.tcl USP_Device2_UPnPDev_set_2 Verify USP_Device2 UPnPDev Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UPnPDev Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_UPnPDev_gsdm_4 Verify USP_Device2 UPnPDev Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UPnPDev Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_UPnPDev_gsdm_req_5 Verify USP_Device2 UPnPDev Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UPnPDiscBasic Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_UPnPDiscBasic_get_1 Verify USP_Device2 UPnPDiscBasic Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UPnPDiscBasic Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_UPnPDiscBasic_gsdm_4 Verify USP_Device2 UPnPDiscBasic Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UPnPDiscBasic Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_UPnPDiscBasic_gsdm_req_5 Verify USP_Device2 UPnPDiscBasic Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UPnPDiscAdv Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_UPnPDiscAdv_get_1 Verify USP_Device2 UPnPDiscAdv Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UPnPDiscAdv Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_UPnPDiscAdv_gsdm_4 Verify USP_Device2 UPnPDiscAdv Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UPnPDiscAdv Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_UPnPDiscAdv_gsdm_req_5 Verify USP_Device2 UPnPDiscAdv Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 SimpleFirewall Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_SimpleFirewall_get_1 Verify USP_Device2 SimpleFirewall Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 SimpleFirewall Profile using Set message USP_Device2_profiles.tcl USP_Device2_SimpleFirewall_set_2 Verify USP_Device2 SimpleFirewall Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 SimpleFirewall Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_SimpleFirewall_gsdm_4 Verify USP_Device2 SimpleFirewall Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 SimpleFirewall Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_SimpleFirewall_gsdm_req_5 Verify USP_Device2 SimpleFirewall Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 AdvancedFirewall Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_AdvancedFirewall_get_1 Verify USP_Device2 AdvancedFirewall Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 AdvancedFirewall Profile using Set message USP_Device2_profiles.tcl USP_Device2_AdvancedFirewall_set_2 Verify USP_Device2 AdvancedFirewall Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 AdvancedFirewall Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_AdvancedFirewall_ado_3 Verify USP_Device2 AdvancedFirewall Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 AdvancedFirewall Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_AdvancedFirewall_gsdm_4 Verify USP_Device2 AdvancedFirewall Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 AdvancedFirewall Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_AdvancedFirewall_gsdm_req_5 Verify USP_Device2 AdvancedFirewall Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 PeriodicStatsBase Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_PeriodicStatsBase_get_1 Verify USP_Device2 PeriodicStatsBase Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 PeriodicStatsBase Profile using Set message USP_Device2_profiles.tcl USP_Device2_PeriodicStatsBase_set_2 Verify USP_Device2 PeriodicStatsBase Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 PeriodicStatsBase Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_PeriodicStatsBase_ado_3 Verify USP_Device2 PeriodicStatsBase Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 PeriodicStatsBase Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_PeriodicStatsBase_gsdm_4 Verify USP_Device2 PeriodicStatsBase Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 PeriodicStatsBase Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_PeriodicStatsBase_gsdm_req_5 Verify USP_Device2 PeriodicStatsBase Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FaultMgmtSupportedAlarms Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_FaultMgmtSupportedAlarms_get_1 Verify USP_Device2 FaultMgmtSupportedAlarms Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FaultMgmtSupportedAlarms Profile using Set message USP_Device2_profiles.tcl USP_Device2_FaultMgmtSupportedAlarms_set_2 Verify USP_Device2 FaultMgmtSupportedAlarms Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FaultMgmtSupportedAlarms Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_FaultMgmtSupportedAlarms_gsdm_4 Verify USP_Device2 FaultMgmtSupportedAlarms Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FaultMgmtSupportedAlarms Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_FaultMgmtSupportedAlarms_gsdm_req_5 Verify USP_Device2 FaultMgmtSupportedAlarms Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FaultMgmtActive Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_FaultMgmtActive_get_1 Verify USP_Device2 FaultMgmtActive Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FaultMgmtActive Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_FaultMgmtActive_gsdm_4 Verify USP_Device2 FaultMgmtActive Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FaultMgmtActive Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_FaultMgmtActive_gsdm_req_5 Verify USP_Device2 FaultMgmtActive Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FaultMgmtHistory Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_FaultMgmtHistory_get_1 Verify USP_Device2 FaultMgmtHistory Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FaultMgmtHistory Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_FaultMgmtHistory_gsdm_4 Verify USP_Device2 FaultMgmtHistory Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FaultMgmtHistory Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_FaultMgmtHistory_gsdm_req_5 Verify USP_Device2 FaultMgmtHistory Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FaultMgmtExpedited Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_FaultMgmtExpedited_get_1 Verify USP_Device2 FaultMgmtExpedited Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FaultMgmtExpedited Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_FaultMgmtExpedited_gsdm_4 Verify USP_Device2 FaultMgmtExpedited Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FaultMgmtExpedited Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_FaultMgmtExpedited_gsdm_req_5 Verify USP_Device2 FaultMgmtExpedited Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FaultMgmtQueued Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_FaultMgmtQueued_get_1 Verify USP_Device2 FaultMgmtQueued Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FaultMgmtQueued Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_FaultMgmtQueued_gsdm_4 Verify USP_Device2 FaultMgmtQueued Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FaultMgmtQueued Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_FaultMgmtQueued_gsdm_req_5 Verify USP_Device2 FaultMgmtQueued Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FAP_GPS Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_FAP_GPS_get_1 Verify USP_Device2 FAP_GPS Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FAP_GPS Profile using Set message USP_Device2_profiles.tcl USP_Device2_FAP_GPS_set_2 Verify USP_Device2 FAP_GPS Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FAP_GPS Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_FAP_GPS_gsdm_4 Verify USP_Device2 FAP_GPS Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FAP_GPS Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_FAP_GPS_gsdm_req_5 Verify USP_Device2 FAP_GPS Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FAP_PerfMgmt Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_FAP_PerfMgmt_get_1 Verify USP_Device2 FAP_PerfMgmt Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FAP_PerfMgmt Profile using Set message USP_Device2_profiles.tcl USP_Device2_FAP_PerfMgmt_set_2 Verify USP_Device2 FAP_PerfMgmt Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FAP_PerfMgmt Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_FAP_PerfMgmt_gsdm_4 Verify USP_Device2 FAP_PerfMgmt Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FAP_PerfMgmt Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_FAP_PerfMgmt_gsdm_req_5 Verify USP_Device2 FAP_PerfMgmt Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FAP_ApplicationPlatform Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_FAP_ApplicationPlatform_get_1 Verify USP_Device2 FAP_ApplicationPlatform Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FAP_ApplicationPlatform Profile using Set message USP_Device2_profiles.tcl USP_Device2_FAP_ApplicationPlatform_set_2 Verify USP_Device2 FAP_ApplicationPlatform Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FAP_ApplicationPlatform Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_FAP_ApplicationPlatform_gsdm_4 Verify USP_Device2 FAP_ApplicationPlatform Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 FAP_ApplicationPlatform Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_FAP_ApplicationPlatform_gsdm_req_5 Verify USP_Device2 FAP_ApplicationPlatform Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BulkDataColl Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_BulkDataColl_get_1 Verify USP_Device2 BulkDataColl Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BulkDataColl Profile using Set message USP_Device2_profiles.tcl USP_Device2_BulkDataColl_set_2 Verify USP_Device2 BulkDataColl Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BulkDataColl Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_BulkDataColl_ado_3 Verify USP_Device2 BulkDataColl Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BulkDataColl Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_BulkDataColl_gsdm_4 Verify USP_Device2 BulkDataColl Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BulkDataColl Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_BulkDataColl_gsdm_req_5 Verify USP_Device2 BulkDataColl Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BulkDataReports Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_BulkDataReports_get_1 Verify USP_Device2 BulkDataReports Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BulkDataReports Profile using Set message USP_Device2_profiles.tcl USP_Device2_BulkDataReports_set_2 Verify USP_Device2 BulkDataReports Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BulkDataReports Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_BulkDataReports_ado_3 Verify USP_Device2 BulkDataReports Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BulkDataReports Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_BulkDataReports_gsdm_4 Verify USP_Device2 BulkDataReports Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BulkDataReports Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_BulkDataReports_gsdm_req_5 Verify USP_Device2 BulkDataReports Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BulkDataJSONEncoding Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_BulkDataJSONEncoding_get_1 Verify USP_Device2 BulkDataJSONEncoding Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BulkDataJSONEncoding Profile using Set message USP_Device2_profiles.tcl USP_Device2_BulkDataJSONEncoding_set_2 Verify USP_Device2 BulkDataJSONEncoding Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BulkDataJSONEncoding Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_BulkDataJSONEncoding_ado_3 Verify USP_Device2 BulkDataJSONEncoding Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BulkDataJSONEncoding Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_BulkDataJSONEncoding_gsdm_4 Verify USP_Device2 BulkDataJSONEncoding Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BulkDataJSONEncoding Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_BulkDataJSONEncoding_gsdm_req_5 Verify USP_Device2 BulkDataJSONEncoding Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BulkDataCSVEncoding Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_BulkDataCSVEncoding_get_1 Verify USP_Device2 BulkDataCSVEncoding Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BulkDataCSVEncoding Profile using Set message USP_Device2_profiles.tcl USP_Device2_BulkDataCSVEncoding_set_2 Verify USP_Device2 BulkDataCSVEncoding Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BulkDataCSVEncoding Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_BulkDataCSVEncoding_ado_3 Verify USP_Device2 BulkDataCSVEncoding Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BulkDataCSVEncoding Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_BulkDataCSVEncoding_gsdm_4 Verify USP_Device2 BulkDataCSVEncoding Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BulkDataCSVEncoding Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_BulkDataCSVEncoding_gsdm_req_5 Verify USP_Device2 BulkDataCSVEncoding Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BulkDataHTTP Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_BulkDataHTTP_get_1 Verify USP_Device2 BulkDataHTTP Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BulkDataHTTP Profile using Set message USP_Device2_profiles.tcl USP_Device2_BulkDataHTTP_set_2 Verify USP_Device2 BulkDataHTTP Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BulkDataHTTP Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_BulkDataHTTP_ado_3 Verify USP_Device2 BulkDataHTTP Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BulkDataHTTP Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_BulkDataHTTP_gsdm_4 Verify USP_Device2 BulkDataHTTP Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BulkDataHTTP Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_BulkDataHTTP_gsdm_req_5 Verify USP_Device2 BulkDataHTTP Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 XMPPBasic Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_XMPPBasic_get_1 Verify USP_Device2 XMPPBasic Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 XMPPBasic Profile using Set message USP_Device2_profiles.tcl USP_Device2_XMPPBasic_set_2 Verify USP_Device2 XMPPBasic Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 XMPPBasic Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_XMPPBasic_ado_3 Verify USP_Device2 XMPPBasic Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 XMPPBasic Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_XMPPBasic_gsdm_4 Verify USP_Device2 XMPPBasic Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 XMPPBasic Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_XMPPBasic_gsdm_req_5 Verify USP_Device2 XMPPBasic Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 XMPPAdvanced Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_XMPPAdvanced_get_1 Verify USP_Device2 XMPPAdvanced Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 XMPPAdvanced Profile using Set message USP_Device2_profiles.tcl USP_Device2_XMPPAdvanced_set_2 Verify USP_Device2 XMPPAdvanced Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 XMPPAdvanced Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_XMPPAdvanced_ado_3 Verify USP_Device2 XMPPAdvanced Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 XMPPAdvanced Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_XMPPAdvanced_gsdm_4 Verify USP_Device2 XMPPAdvanced Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 XMPPAdvanced Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_XMPPAdvanced_gsdm_req_5 Verify USP_Device2 XMPPAdvanced Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 XMPPReconnect Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_XMPPReconnect_get_1 Verify USP_Device2 XMPPReconnect Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 XMPPReconnect Profile using Set message USP_Device2_profiles.tcl USP_Device2_XMPPReconnect_set_2 Verify USP_Device2 XMPPReconnect Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 XMPPReconnect Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_XMPPReconnect_ado_3 Verify USP_Device2 XMPPReconnect Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 XMPPReconnect Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_XMPPReconnect_gsdm_4 Verify USP_Device2 XMPPReconnect Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 XMPPReconnect Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_XMPPReconnect_gsdm_req_5 Verify USP_Device2 XMPPReconnect Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905Device Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_IEEE1905Device_get_1 Verify USP_Device2 IEEE1905Device Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905Device Profile using Set message USP_Device2_profiles.tcl USP_Device2_IEEE1905Device_set_2 Verify USP_Device2 IEEE1905Device Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905Device Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_IEEE1905Device_gsdm_4 Verify USP_Device2 IEEE1905Device Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905Device Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_IEEE1905Device_gsdm_req_5 Verify USP_Device2 IEEE1905Device Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905TopologyMetric Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_IEEE1905TopologyMetric_get_1 Verify USP_Device2 IEEE1905TopologyMetric Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905TopologyMetric Profile using Set message USP_Device2_profiles.tcl USP_Device2_IEEE1905TopologyMetric_set_2 Verify USP_Device2 IEEE1905TopologyMetric Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905TopologyMetric Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_IEEE1905TopologyMetric_gsdm_4 Verify USP_Device2 IEEE1905TopologyMetric Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905TopologyMetric Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_IEEE1905TopologyMetric_gsdm_req_5 Verify USP_Device2 IEEE1905TopologyMetric Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905TopologyNeighbor Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_IEEE1905TopologyNeighbor_get_1 Verify USP_Device2 IEEE1905TopologyNeighbor Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905TopologyNeighbor Profile using Set message USP_Device2_profiles.tcl USP_Device2_IEEE1905TopologyNeighbor_set_2 Verify USP_Device2 IEEE1905TopologyNeighbor Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905TopologyNeighbor Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_IEEE1905TopologyNeighbor_gsdm_4 Verify USP_Device2 IEEE1905TopologyNeighbor Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905TopologyNeighbor Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_IEEE1905TopologyNeighbor_gsdm_req_5 Verify USP_Device2 IEEE1905TopologyNeighbor Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905TopologyHigherLayer Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_IEEE1905TopologyHigherLayer_get_1 Verify USP_Device2 IEEE1905TopologyHigherLayer Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905TopologyHigherLayer Profile using Set message USP_Device2_profiles.tcl USP_Device2_IEEE1905TopologyHigherLayer_set_2 Verify USP_Device2 IEEE1905TopologyHigherLayer Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905TopologyHigherLayer Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_IEEE1905TopologyHigherLayer_gsdm_4 Verify USP_Device2 IEEE1905TopologyHigherLayer Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905TopologyHigherLayer Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_IEEE1905TopologyHigherLayer_gsdm_req_5 Verify USP_Device2 IEEE1905TopologyHigherLayer Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905Power Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_IEEE1905Power_get_1 Verify USP_Device2 IEEE1905Power Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905Power Profile using Set message USP_Device2_profiles.tcl USP_Device2_IEEE1905Power_set_2 Verify USP_Device2 IEEE1905Power Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905Power Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_IEEE1905Power_gsdm_4 Verify USP_Device2 IEEE1905Power Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905Power Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_IEEE1905Power_gsdm_req_5 Verify USP_Device2 IEEE1905Power Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905InterfaceSelection Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_IEEE1905InterfaceSelection_get_1 Verify USP_Device2 IEEE1905InterfaceSelection Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905InterfaceSelection Profile using Set message USP_Device2_profiles.tcl USP_Device2_IEEE1905InterfaceSelection_set_2 Verify USP_Device2 IEEE1905InterfaceSelection Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905InterfaceSelection Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_IEEE1905InterfaceSelection_ado_3 Verify USP_Device2 IEEE1905InterfaceSelection Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905InterfaceSelection Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_IEEE1905InterfaceSelection_gsdm_4 Verify USP_Device2 IEEE1905InterfaceSelection Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905InterfaceSelection Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_IEEE1905InterfaceSelection_gsdm_req_5 Verify USP_Device2 IEEE1905InterfaceSelection Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905LinkMetric Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_IEEE1905LinkMetric_get_1 Verify USP_Device2 IEEE1905LinkMetric Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905LinkMetric Profile using Set message USP_Device2_profiles.tcl USP_Device2_IEEE1905LinkMetric_set_2 Verify USP_Device2 IEEE1905LinkMetric Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905LinkMetric Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_IEEE1905LinkMetric_gsdm_4 Verify USP_Device2 IEEE1905LinkMetric Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905LinkMetric Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_IEEE1905LinkMetric_gsdm_req_5 Verify USP_Device2 IEEE1905LinkMetric Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905NetworkTopology Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_IEEE1905NetworkTopology_get_1 Verify USP_Device2 IEEE1905NetworkTopology Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905NetworkTopology Profile using Set message USP_Device2_profiles.tcl USP_Device2_IEEE1905NetworkTopology_set_2 Verify USP_Device2 IEEE1905NetworkTopology Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905NetworkTopology Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_IEEE1905NetworkTopology_gsdm_4 Verify USP_Device2 IEEE1905NetworkTopology Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IEEE1905NetworkTopology Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_IEEE1905NetworkTopology_gsdm_req_5 Verify USP_Device2 IEEE1905NetworkTopology Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MQTTClientCon Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_MQTTClientCon_get_1 Verify USP_Device2 MQTTClientCon Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MQTTClientCon Profile using Set message USP_Device2_profiles.tcl USP_Device2_MQTTClientCon_set_2 Verify USP_Device2 MQTTClientCon Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MQTTClientCon Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_MQTTClientCon_gsdm_4 Verify USP_Device2 MQTTClientCon Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MQTTClientCon Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_MQTTClientCon_gsdm_req_5 Verify USP_Device2 MQTTClientCon Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MQTTClientBase Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_MQTTClientBase_get_1 Verify USP_Device2 MQTTClientBase Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MQTTClientBase Profile using Set message USP_Device2_profiles.tcl USP_Device2_MQTTClientBase_set_2 Verify USP_Device2 MQTTClientBase Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MQTTClientBase Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_MQTTClientBase_gsdm_4 Verify USP_Device2 MQTTClientBase Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MQTTClientBase Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_MQTTClientBase_gsdm_req_5 Verify USP_Device2 MQTTClientBase Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MQTTClientSubscribe Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_MQTTClientSubscribe_get_1 Verify USP_Device2 MQTTClientSubscribe Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MQTTClientSubscribe Profile using Set message USP_Device2_profiles.tcl USP_Device2_MQTTClientSubscribe_set_2 Verify USP_Device2 MQTTClientSubscribe Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MQTTClientSubscribe Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_MQTTClientSubscribe_gsdm_4 Verify USP_Device2 MQTTClientSubscribe Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MQTTClientSubscribe Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_MQTTClientSubscribe_gsdm_req_5 Verify USP_Device2 MQTTClientSubscribe Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MQTTBrokerBase Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_MQTTBrokerBase_get_1 Verify USP_Device2 MQTTBrokerBase Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MQTTBrokerBase Profile using Set message USP_Device2_profiles.tcl USP_Device2_MQTTBrokerBase_set_2 Verify USP_Device2 MQTTBrokerBase Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MQTTBrokerBase Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_MQTTBrokerBase_gsdm_4 Verify USP_Device2 MQTTBrokerBase Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MQTTBrokerBase Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_MQTTBrokerBase_gsdm_req_5 Verify USP_Device2 MQTTBrokerBase Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MQTTBrokerBridgeBase Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_MQTTBrokerBridgeBase_get_1 Verify USP_Device2 MQTTBrokerBridgeBase Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MQTTBrokerBridgeBase Profile using Set message USP_Device2_profiles.tcl USP_Device2_MQTTBrokerBridgeBase_set_2 Verify USP_Device2 MQTTBrokerBridgeBase Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MQTTBrokerBridgeBase Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_MQTTBrokerBridgeBase_gsdm_4 Verify USP_Device2 MQTTBrokerBridgeBase Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MQTTBrokerBridgeBase Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_MQTTBrokerBridgeBase_gsdm_req_5 Verify USP_Device2 MQTTBrokerBridgeBase Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MQTTBrokerExtended Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_MQTTBrokerExtended_get_1 Verify USP_Device2 MQTTBrokerExtended Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MQTTBrokerExtended Profile using Set message USP_Device2_profiles.tcl USP_Device2_MQTTBrokerExtended_set_2 Verify USP_Device2 MQTTBrokerExtended Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MQTTBrokerExtended Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_MQTTBrokerExtended_gsdm_4 Verify USP_Device2 MQTTBrokerExtended Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MQTTBrokerExtended Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_MQTTBrokerExtended_gsdm_req_5 Verify USP_Device2 MQTTBrokerExtended Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LEDBasic Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_LEDBasic_get_1 Verify USP_Device2 LEDBasic Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LEDBasic Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_LEDBasic_gsdm_4 Verify USP_Device2 LEDBasic Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LEDBasic Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_LEDBasic_gsdm_req_5 Verify USP_Device2 LEDBasic Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LEDAdv Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_LEDAdv_get_1 Verify USP_Device2 LEDAdv Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LEDAdv Profile using Set message USP_Device2_profiles.tcl USP_Device2_LEDAdv_set_2 Verify USP_Device2 LEDAdv Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LEDAdv Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_LEDAdv_ado_3 Verify USP_Device2 LEDAdv Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LEDAdv Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_LEDAdv_gsdm_4 Verify USP_Device2 LEDAdv Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LEDAdv Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_LEDAdv_gsdm_req_5 Verify USP_Device2 LEDAdv Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BASAPM Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_BASAPM_get_1 Verify USP_Device2 BASAPM Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BASAPM Profile using Set message USP_Device2_profiles.tcl USP_Device2_BASAPM_set_2 Verify USP_Device2 BASAPM Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BASAPM Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_BASAPM_ado_3 Verify USP_Device2 BASAPM Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BASAPM Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_BASAPM_gsdm_4 Verify USP_Device2 BASAPM Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BASAPM Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_BASAPM_gsdm_req_5 Verify USP_Device2 BASAPM Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LMAPPreconfiguration Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_LMAPPreconfiguration_get_1 Verify USP_Device2 LMAPPreconfiguration Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LMAPPreconfiguration Profile using Set message USP_Device2_profiles.tcl USP_Device2_LMAPPreconfiguration_set_2 Verify USP_Device2 LMAPPreconfiguration Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LMAPPreconfiguration Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_LMAPPreconfiguration_ado_3 Verify USP_Device2 LMAPPreconfiguration Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LMAPPreconfiguration Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_LMAPPreconfiguration_gsdm_4 Verify USP_Device2 LMAPPreconfiguration Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LMAPPreconfiguration Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_LMAPPreconfiguration_gsdm_req_5 Verify USP_Device2 LMAPPreconfiguration Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LMAPController Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_LMAPController_get_1 Verify USP_Device2 LMAPController Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LMAPController Profile using Set message USP_Device2_profiles.tcl USP_Device2_LMAPController_set_2 Verify USP_Device2 LMAPController Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LMAPController Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_LMAPController_ado_3 Verify USP_Device2 LMAPController Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LMAPController Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_LMAPController_gsdm_4 Verify USP_Device2 LMAPController Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LMAPController Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_LMAPController_gsdm_req_5 Verify USP_Device2 LMAPController Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LMAPCollector Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_LMAPCollector_get_1 Verify USP_Device2 LMAPCollector Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LMAPCollector Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_LMAPCollector_gsdm_4 Verify USP_Device2 LMAPCollector Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LMAPCollector Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_LMAPCollector_gsdm_req_5 Verify USP_Device2 LMAPCollector Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BinaryControl Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_BinaryControl_get_1 Verify USP_Device2 BinaryControl Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BinaryControl Profile using Set message USP_Device2_profiles.tcl USP_Device2_BinaryControl_set_2 Verify USP_Device2 BinaryControl Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BinaryControl Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_BinaryControl_gsdm_4 Verify USP_Device2 BinaryControl Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BinaryControl Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_BinaryControl_gsdm_req_5 Verify USP_Device2 BinaryControl Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LevelControl Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_LevelControl_get_1 Verify USP_Device2 LevelControl Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LevelControl Profile using Set message USP_Device2_profiles.tcl USP_Device2_LevelControl_set_2 Verify USP_Device2 LevelControl Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LevelControl Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_LevelControl_gsdm_4 Verify USP_Device2 LevelControl Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LevelControl Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_LevelControl_gsdm_req_5 Verify USP_Device2 LevelControl Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LevelControlIntensity Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_LevelControlIntensity_get_1 Verify USP_Device2 LevelControlIntensity Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LevelControlIntensity Profile using Set message USP_Device2_profiles.tcl USP_Device2_LevelControlIntensity_set_2 Verify USP_Device2 LevelControlIntensity Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LevelControlIntensity Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_LevelControlIntensity_gsdm_4 Verify USP_Device2 LevelControlIntensity Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LevelControlIntensity Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_LevelControlIntensity_gsdm_req_5 Verify USP_Device2 LevelControlIntensity Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 EnumControl Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_EnumControl_get_1 Verify USP_Device2 EnumControl Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 EnumControl Profile using Set message USP_Device2_profiles.tcl USP_Device2_EnumControl_set_2 Verify USP_Device2 EnumControl Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 EnumControl Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_EnumControl_gsdm_4 Verify USP_Device2 EnumControl Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 EnumControl Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_EnumControl_gsdm_req_5 Verify USP_Device2 EnumControl Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BinarySensor Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_BinarySensor_get_1 Verify USP_Device2 BinarySensor Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BinarySensor Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_BinarySensor_gsdm_4 Verify USP_Device2 BinarySensor Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 BinarySensor Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_BinarySensor_gsdm_req_5 Verify USP_Device2 BinarySensor Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LevelSensor Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_LevelSensor_get_1 Verify USP_Device2 LevelSensor Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LevelSensor Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_LevelSensor_gsdm_4 Verify USP_Device2 LevelSensor Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LevelSensor Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_LevelSensor_gsdm_req_5 Verify USP_Device2 LevelSensor Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LevelSensorLowThreshold Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_LevelSensorLowThreshold_get_1 Verify USP_Device2 LevelSensorLowThreshold Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LevelSensorLowThreshold Profile using Set message USP_Device2_profiles.tcl USP_Device2_LevelSensorLowThreshold_set_2 Verify USP_Device2 LevelSensorLowThreshold Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LevelSensorLowThreshold Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_LevelSensorLowThreshold_gsdm_4 Verify USP_Device2 LevelSensorLowThreshold Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LevelSensorLowThreshold Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_LevelSensorLowThreshold_gsdm_req_5 Verify USP_Device2 LevelSensorLowThreshold Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LevelSensorHighThreshold Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_LevelSensorHighThreshold_get_1 Verify USP_Device2 LevelSensorHighThreshold Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LevelSensorHighThreshold Profile using Set message USP_Device2_profiles.tcl USP_Device2_LevelSensorHighThreshold_set_2 Verify USP_Device2 LevelSensorHighThreshold Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LevelSensorHighThreshold Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_LevelSensorHighThreshold_gsdm_4 Verify USP_Device2 LevelSensorHighThreshold Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 LevelSensorHighThreshold Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_LevelSensorHighThreshold_gsdm_req_5 Verify USP_Device2 LevelSensorHighThreshold Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MultiLevelSensor Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_MultiLevelSensor_get_1 Verify USP_Device2 MultiLevelSensor Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MultiLevelSensor Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_MultiLevelSensor_gsdm_4 Verify USP_Device2 MultiLevelSensor Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MultiLevelSensor Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_MultiLevelSensor_gsdm_req_5 Verify USP_Device2 MultiLevelSensor Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 EnumSensor Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_EnumSensor_get_1 Verify USP_Device2 EnumSensor Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 EnumSensor Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_EnumSensor_gsdm_4 Verify USP_Device2 EnumSensor Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 EnumSensor Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_EnumSensor_gsdm_req_5 Verify USP_Device2 EnumSensor Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Download Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_Download_get_1 Verify USP_Device2 Download Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Download Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_Download_gsdm_4 Verify USP_Device2 Download Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Download Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_Download_gsdm_req_5 Verify USP_Device2 Download Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPLayerCapacity Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_IPLayerCapacity_get_1 Verify USP_Device2 IPLayerCapacity Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPLayerCapacity Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_IPLayerCapacity_gsdm_4 Verify USP_Device2 IPLayerCapacity Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPLayerCapacity Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_IPLayerCapacity_gsdm_req_5 Verify USP_Device2 IPLayerCapacity Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPLayerCapacityTest Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_IPLayerCapacityTest_get_1 Verify USP_Device2 IPLayerCapacityTest Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPLayerCapacityTest Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_IPLayerCapacityTest_gsdm_4 Verify USP_Device2 IPLayerCapacityTest Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPLayerCapacityTest Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_IPLayerCapacityTest_gsdm_req_5 Verify USP_Device2 IPLayerCapacityTest Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DownloadTCP Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_DownloadTCP_gsdm_4 Verify USP_Device2 DownloadTCP Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DownloadTCP Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_DownloadTCP_gsdm_req_5 Verify USP_Device2 DownloadTCP Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Upload Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_Upload_get_1 Verify USP_Device2 Upload Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Upload Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_Upload_gsdm_4 Verify USP_Device2 Upload Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Upload Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_Upload_gsdm_req_5 Verify USP_Device2 Upload Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UploadTCP Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_UploadTCP_gsdm_4 Verify USP_Device2 UploadTCP Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UploadTCP Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_UploadTCP_gsdm_req_5 Verify USP_Device2 UploadTCP Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 SelfTestDiag Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_SelfTestDiag_gsdm_4 Verify USP_Device2 SelfTestDiag Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 SelfTestDiag Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_SelfTestDiag_gsdm_req_5 Verify USP_Device2 SelfTestDiag Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 NSLookupDiag Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_NSLookupDiag_gsdm_4 Verify USP_Device2 NSLookupDiag Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 NSLookupDiag Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_NSLookupDiag_gsdm_req_5 Verify USP_Device2 NSLookupDiag Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Baseline Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_Baseline_get_1 Verify USP_Device2 Baseline Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Baseline Profile using Set message USP_Device2_profiles.tcl USP_Device2_Baseline_set_2 Verify USP_Device2 Baseline Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Baseline Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_Baseline_ado_3 Verify USP_Device2 Baseline Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Baseline Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_Baseline_gsdm_4 Verify USP_Device2 Baseline Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 Baseline Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_Baseline_gsdm_req_5 Verify USP_Device2 Baseline Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPPingDetailed Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_IPPingDetailed_gsdm_4 Verify USP_Device2 IPPingDetailed Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPPingDetailed Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_IPPingDetailed_gsdm_req_5 Verify USP_Device2 IPPingDetailed Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPPing Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_IPPing_gsdm_4 Verify USP_Device2 IPPing Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPPing Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_IPPing_gsdm_req_5 Verify USP_Device2 IPPing Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 TraceRoute Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_TraceRoute_gsdm_4 Verify USP_Device2 TraceRoute Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 TraceRoute Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_TraceRoute_gsdm_req_5 Verify USP_Device2 TraceRoute Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ATMLoopback Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_ATMLoopback_gsdm_4 Verify USP_Device2 ATMLoopback Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ATMLoopback Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_ATMLoopback_gsdm_req_5 Verify USP_Device2 ATMLoopback Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DSLDiagnostics Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_DSLDiagnostics_gsdm_4 Verify USP_Device2 DSLDiagnostics Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DSLDiagnostics Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_DSLDiagnostics_gsdm_req_5 Verify USP_Device2 DSLDiagnostics Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ADSL2Diagnostics Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_ADSL2Diagnostics_gsdm_4 Verify USP_Device2 ADSL2Diagnostics Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ADSL2Diagnostics Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_ADSL2Diagnostics_gsdm_req_5 Verify USP_Device2 ADSL2Diagnostics Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 VDSL2Diagnostics Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_VDSL2Diagnostics_gsdm_4 Verify USP_Device2 VDSL2Diagnostics Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 VDSL2Diagnostics Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_VDSL2Diagnostics_gsdm_req_5 Verify USP_Device2 VDSL2Diagnostics Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 SELTDiagnostics Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_SELTDiagnostics_gsdm_4 Verify USP_Device2 SELTDiagnostics Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 SELTDiagnostics Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_SELTDiagnostics_gsdm_req_5 Verify USP_Device2 SELTDiagnostics Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 HPNADiagnostics Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_HPNADiagnostics_gsdm_4 Verify USP_Device2 HPNADiagnostics Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 HPNADiagnostics Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_HPNADiagnostics_gsdm_req_5 Verify USP_Device2 HPNADiagnostics Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UPADiagnostics Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_UPADiagnostics_gsdm_4 Verify USP_Device2 UPADiagnostics Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UPADiagnostics Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_UPADiagnostics_gsdm_req_5 Verify USP_Device2 UPADiagnostics Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UDPEchoDiag Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_UDPEchoDiag_gsdm_4 Verify USP_Device2 UDPEchoDiag Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 UDPEchoDiag Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_UDPEchoDiag_gsdm_req_5 Verify USP_Device2 UDPEchoDiag Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ServerSelectionDiag Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_ServerSelectionDiag_gsdm_4 Verify USP_Device2 ServerSelectionDiag Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 ServerSelectionDiag Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_ServerSelectionDiag_gsdm_req_5 Verify USP_Device2 ServerSelectionDiag Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 STOMPConn Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_STOMPConn_get_1 Verify USP_Device2 STOMPConn Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 STOMPConn Profile using Set message USP_Device2_profiles.tcl USP_Device2_STOMPConn_set_2 Verify USP_Device2 STOMPConn Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 STOMPConn Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_STOMPConn_ado_3 Verify USP_Device2 STOMPConn Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 STOMPConn Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_STOMPConn_gsdm_4 Verify USP_Device2 STOMPConn Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 STOMPConn Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_STOMPConn_gsdm_req_5 Verify USP_Device2 STOMPConn Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 STOMPHeartbeat Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_STOMPHeartbeat_get_1 Verify USP_Device2 STOMPHeartbeat Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 STOMPHeartbeat Profile using Set message USP_Device2_profiles.tcl USP_Device2_STOMPHeartbeat_set_2 Verify USP_Device2 STOMPHeartbeat Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 STOMPHeartbeat Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_STOMPHeartbeat_ado_3 Verify USP_Device2 STOMPHeartbeat Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 STOMPHeartbeat Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_STOMPHeartbeat_gsdm_4 Verify USP_Device2 STOMPHeartbeat Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 STOMPHeartbeat Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_STOMPHeartbeat_gsdm_req_5 Verify USP_Device2 STOMPHeartbeat Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 TempStatusAdv Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_TempStatusAdv_get_1 Verify USP_Device2 TempStatusAdv Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 TempStatusAdv Profile using Set message USP_Device2_profiles.tcl USP_Device2_TempStatusAdv_set_2 Verify USP_Device2 TempStatusAdv Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 TempStatusAdv Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_TempStatusAdv_gsdm_4 Verify USP_Device2 TempStatusAdv Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 TempStatusAdv Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_TempStatusAdv_gsdm_req_5 Verify USP_Device2 TempStatusAdv Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 USBHostsAdv Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_USBHostsAdv_get_1 Verify USP_Device2 USBHostsAdv Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 USBHostsAdv Profile using Set message USP_Device2_profiles.tcl USP_Device2_USBHostsAdv_set_2 Verify USP_Device2 USBHostsAdv Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 USBHostsAdv Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_USBHostsAdv_gsdm_4 Verify USP_Device2 USBHostsAdv Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 USBHostsAdv Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_USBHostsAdv_gsdm_req_5 Verify USP_Device2 USBHostsAdv Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 PeriodicStatsAdv Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_PeriodicStatsAdv_get_1 Verify USP_Device2 PeriodicStatsAdv Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 PeriodicStatsAdv Profile using Set message USP_Device2_profiles.tcl USP_Device2_PeriodicStatsAdv_set_2 Verify USP_Device2 PeriodicStatsAdv Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 PeriodicStatsAdv Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_PeriodicStatsAdv_ado_3 Verify USP_Device2 PeriodicStatsAdv Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 PeriodicStatsAdv Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_PeriodicStatsAdv_gsdm_4 Verify USP_Device2 PeriodicStatsAdv Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 PeriodicStatsAdv Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_PeriodicStatsAdv_gsdm_req_5 Verify USP_Device2 PeriodicStatsAdv Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPv6Interface Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_IPv6Interface_get_1 Verify USP_Device2 IPv6Interface Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPv6Interface Profile using Set message USP_Device2_profiles.tcl USP_Device2_IPv6Interface_set_2 Verify USP_Device2 IPv6Interface Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPv6Interface Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_IPv6Interface_ado_3 Verify USP_Device2 IPv6Interface Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPv6Interface Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_IPv6Interface_gsdm_4 Verify USP_Device2 IPv6Interface Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 IPv6Interface Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_IPv6Interface_gsdm_req_5 Verify USP_Device2 IPv6Interface Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 PPPInterface Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_PPPInterface_get_1 Verify USP_Device2 PPPInterface Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 PPPInterface Profile using Set message USP_Device2_profiles.tcl USP_Device2_PPPInterface_set_2 Verify USP_Device2 PPPInterface Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 PPPInterface Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_PPPInterface_ado_3 Verify USP_Device2 PPPInterface Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 PPPInterface Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_PPPInterface_gsdm_4 Verify USP_Device2 PPPInterface Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 PPPInterface Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_PPPInterface_gsdm_req_5 Verify USP_Device2 PPPInterface Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv6ClientServerIdentity Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_DHCPv6ClientServerIdentity_get_1 Verify USP_Device2 DHCPv6ClientServerIdentity Profile using Get from top level


    step 1. Perform a Get on the top level object for the profile
    step 2. Verify all required parameters exist
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv6ClientServerIdentity Profile using Set message USP_Device2_profiles.tcl USP_Device2_DHCPv6ClientServerIdentity_set_2 Verify USP_Device2 DHCPv6ClientServerIdentity Profile using Set message


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all parameters that should be writable based on the profile definition
    step 3. For each parameter, attempt to set its current value using a Set message
    step 4. Fail the test if any of the Sets fail
    step 5. Report a summary of all Sets at the end of the test
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv6ClientServerIdentity Profile using Add and Delete on all creatable objects USP_Device2_profiles.tcl USP_Device2_DHCPv6ClientServerIdentity_ado_3 Verify USP_Device2 DHCPv6ClientServerIdentity Profile using Add and Delete on all creatable objects


    step 1. Perform a Get on the top level object for the profile
    step 2. Find all objects that can be created based on the profile definition (either PC or POC)
    step 3. For each object, attempt to create a new instance using Add
    step 4. Fail the test if any Add fails
    step 5. Perform a Get on new object instance
    step 6. Verify all subparameters have been created based on the profile
    step 7. After creating all objects, delete each object using Delete
    step 8. Fail the test if any Delete fails
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv6ClientServerIdentity Profile using GetSupportedDM from top level USP_Device2_profiles.tcl USP_Device2_DHCPv6ClientServerIdentity_gsdm_4 Verify USP_Device2 DHCPv6ClientServerIdentity Profile using GetSupportedDM from top level


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify all returned names against the profile definition
    step 3. Fail the test if any required parameters are missing
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 DHCPv6ClientServerIdentity Parameters have at least as much access as defined in the profile USP_Device2_profiles.tcl USP_Device2_DHCPv6ClientServerIdentity_gsdm_req_5 Verify USP_Device2 DHCPv6ClientServerIdentity Parameters have at least as much access as defined in the profile


    step 1. Initiate a GetSupportedDM on the top level object for the profile
            with first_level_only = false
    step 2. Verify the returned parameter requirements field matches the profile
    step 3. Fail the test if any required parameters are missing
    step 4. Ensure the access for each parameter returned by the DUT
            is at least as accessible as the parameter defined in the profile
    

    References:

    BBF USP Data Model Device:2.15 Root Data Model "TR-181 Issue 2 Amendment 15"

    https://usp-data-models.broadband-forum.org/tr-181-2-15-0-usp.html

Test Module Name Synopsis
Verify USP_Device2 MQTTClientExtended Profile using Get from top level USP_Device2_profiles.tcl USP_Device2_MQTTClientExtended_get_1