The Broadband Forum is a non-profit corporation organized to create guidelines for broadband network system development and deployment. This Test Plan is owned and copyrighted by the Broadband Forum, and portions of this Test Plan may be owned and/or copyrighted by Broadband Forum members.
Intellectual Property
Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of this Test Plan, and to provide supporting documentation.
Terms of Use
Recipients of this document may use it (a) for internal review and study purposes, (b) to provide to the Broadband Forum the comments and notification requested in the preceding paragraph, and (c) if the Recipient is a Broadband Forum member, to implement the Test Plan in a product or service made commercially available. Any other use of this Test Plan is expressly prohibited without the prior written consent of the Broadband Forum.
THIS TEST PLAN IS BEING OFFERED WITHOUT ANY WARRANTY WHATSOEVER, AND IN PARTICULAR, ANY WARRANTY OF NONINFRINGEMENT AND ANY IMPLIED WARRANTIES ARE EXPRESSLY DISCLAIMED. ANY USE OF THIS TEST PLAN SHALL BE MADE ENTIRELY AT THE USER’S OR IMPLEMENTER’S OWN RISK, AND NEITHER THE FORUM, NOR ANY OF ITS MEMBERS OR SUBMITTERS, SHALL HAVE ANY LIABILITY WHATSOEVER TO ANY USER, IMPLEMENTER OR THIRD PARTY FOR ANY DAMAGES OF ANY NATURE WHATSOEVER, DIRECTLY OR INDIRECTLY, ARISING FROM THE USE OF THIS TEST PLAN, INCLUDING BUT NOT LIMITED TO, ANY CONSEQUENTIAL, SPECIAL, PUNITIVE, INCIDENTAL AND INDIRECT DAMAGES.
All copies of this Test Plan (or any portion hereof) must include the notices, legends and other provisions set forth on this page.
NOTE: The right to display a Broadband Forum Certification Logo may only be granted by the Broadband Forum, and that right is available only to Broadband Forum members that have successfully passed certification testing by a duly authorized Test Agency. Further details on the Broadband Forum Certification Programs can be found at http://www.broadband-forum.org.
Adds test 1.78 Removal of subscriptions that have no associated
controller
Adds test 1.80 GetSupportedProtocol
Adds language reinforcing required tests based on supported features
Adds test case 1.81 to test automatic unique key generation by the
Agent
Adds negative test metrics to several Set and Delete tests to
validate that operations did not occur upon error (1.7, 1.8, 1.14,
1.15, 1.20, 1.24, 1.27, 1.28, 1.31, 1.32, 1.33, 1.34, 1.35)
Adds section 10 for bulk data collection tests
Adds tests 1.82 and 1.83 to validate Get and GetInstances using
expressions that match zero objects
Adds test 1.84 to exercise the use of search paths in Subscriptions
Defines deprecation for tests
Deprecates test 1.63 in favor of test 1.79
Deprecates test 9.1 in favor of test 9.11
Deprecates tests 2.3, 2.4, and 2.5
Completely deletes test 1.69
Updates functionality tag on test 1.71 to “supports at least one
multi-instance object”
Clarifies the definition of an empty oper_success element in test 1.32
Rewrites test 2.20 to accomplish its original intent
Changes test 3.6 to check that an Agent does not accept TLS
renegotiation
Changes test 2.15 and 2.16 to use “Enable” rather than “Alias” as a
test parameter
Simplifies test 4.1
Various typographical fixes, some in test procedure path names
Normalizes all protobuf examples in test procedures
Fixes test 2.20 to use the correct permissions
Fixes test 1.47 to use the correct operator
Eases the requirements of test 9.7 for implementation flexibility
Removes the concept of “not-in-force” test cases and features
Updates tests 1.59, 1.84 to use allow_partial false”
Allows tests 1.3, 1.7, 1.8, 1.21 to use only an invalid parameter
value (not an invalid parameter) and accept 7012 as an acceptable
error code
Adds tests 1.86, 1.87 to test Get with unmatched search path
Adds new Connect Record test cases to STOMP and WebSocket sections
Adds MQTT bulk data collection test cases
Adds test 1.88 to check that unique keys are always treated as required
Adds test 1.89 to exercise max_depth feature in Get
Adds test 1.90 to check Delete with unmatched search path
Adds test 1.91 to very an Agent ignores unknown arguments in a command
Adds test 1.92 to test that operate uses default values when absent
Updates test 1.23 metrics to require the return of an empty oper_success
Updates GetSupportedDM test cases to check for new USP 1.2 fields
Updates tests 1.3, 1.4, 1.6, 1.21 to include additional test metrics
Updates tests 1.64 and 1.65 to check for correct command_key value
Updates tests to account for requirement R-MTP.5 in USP 1.2
Fixes metric in test 1.20 and 1.21 to allow for single failure
Fixes test setup in 9.4, 9.5, 9.6
Fixes test 8.5 to remove MTP specific language and require mDNS info
Reverts metric in test 6.7
Fixes test 1.47 test metrics for correct equivalence
Set send_resp to true for several Operate tests where needed
Various typographical fixes
Work Area Directors
Name
Company
Email
Role
Jason Walls
QA Cafe, LLC
jason@qacafe.com
Broadband User Services Work Area Director
John Blackford
CommScope
john.blackford@commscope.com
Broadband User Services Work Area Director
Editors
Name
Company
Email
Role
Jason Walls
QA Cafe, LLC
jason@qacafe.com
Editor
Executive Summary
Testing is crucial to promoting the interoperability and adoption of
standards. To meet this, the Broadband Forum regularly produces test
suites that validate the conformance of implementations of their
standards. This specification defines the test setup, test procedures,
and test metrics to validate Agent and implementations of the
User Services Platform (USP),
published as BBF TR-369.
This test plan is used to validate USP Agent implementations for the
BBF.369 USP Agent Certification Program. Companies
looking to certify their products, or to acquire certified products, can find
full details on the program, approved test tools and labs, and the list of
certified products
here.
Purpose
This purpose of this document is to provide a definitive guide for validating
the compliance of USP Agents in accordance with the specification.
Scope
The tests defined below are intended to validate the specific
requirements outlined in the USP specification, as well as those
requirements defined in the Device:2 Data Model for USP Agents for
objects, parameters, commands, and events necessary for the operation of
USP.