4 Test Setup

4.1 Test Equipment

The necessary set of test equipment to deliver reliable and repeatable test results is specified in Table 1.

Table 1: Required Test Equipment
Test Equipment Description and Functional Capabilities
ACS The ACS is an interoperability partner in this test plan
Traffic Analyzer To verify certain test metrics, Traffic Analyzers MUST be present between the CPE and ACS and between the CPE and any LAN Device
Access Node For infrastructure needs, an Access Node will be provided to bridge connections between the CPE and ACS
File Server The File Server MUST support HTTP PUT & GET, as well as FTP PUT & GET
CPE The CPE is an interoperability partner in this test plan
Network Router There may be one or more Network Routers between the CPE & ACS. If the CPE is a LAN CPE, one Network Router may be configured to provide a Network Address Translation (NAT) function
Firewall The Firewall MUST support the ability to selectively block traffic based on IP address
NTP Server Two NTP Servers. Public NTP Servers such as NIST Internet Time Servers may be used
RADIUS Server To authenticate end devices in WPA Enterprise test cases
DHCP Server To assign addresses and other provisioning information to the CPE on the WAN
DNS Server To resolve addresses on the WAN
LAN Device To connect to the LAN side of a Gateway CPE
Wireless LAN Device To connect to the LAN side of a Gateway CPE over wireless

4.2 Test Setup and Execution

The Interoperability test setup is shown below in Figure 1. The following pieces of test equipment needs to be connected to the Internet and reachable over IP, but there is no other topology requirement: ACS, DHCP Server, DNS Server, File Server, NTP Server, RADIUS Server. The Access Node may not be required if the primary CPE connection is Ethernet.

Figure 1: Common Topology for Interoperability Testing

4.2.1 Common Test Setup

This section describes the test setup shared between all test cases. Any additional setup steps will be described in the “Test Setup” section of the test case.

  1. ACS is connected to the network

  2. CPE is connected to the network and configured with an ACS URL that corresponds to the ACS in step 1.

  3. Have a Network Analyzer to capture traffic between ACS and CPE.

4.2.2 Determine WAN Interface

This section describes steps to determine the WAN interface of a device. These steps are referenced in the Test Procedures.

For CPE that support the Device:2 data model:

For CPE that support the InternetGatewayDevice:1 root data model [9]:

4.2.3 Test Execution

Each test is defined as a separate entity that can be run independent of all other test procedures. These tests, performed sequentially, may cause changes to the ACS & CPE states during the course of testing.

If a CPE returns a status of 1 in a SetParameterValuesResponse or an AddObjectResponse, the following steps MUST be followed:

  1. Terminate the CWMP session.

  2. Configure the ACS to issue a connection request.

  3. Configure the ACS to issue a GetParameterValues RPC for the changed variable(s) and verify that they are correct.

4.3 CPE Test Requirements and Prerequisites

  1. OD-361 section 3.4.4 [2] states that passing IR-069i2 [1] is a prerequisite for a CPE undergoing this test plan.

  2. Each test case includes a References section that refers to a version of a data model definition or other standard document. For all Broadband Forum data models and Broadband Forum Technical Reports, the test case references the earliest version the CPE can support to run the test case.

  3. Each test case includes a Profiles section that includes the profiles needed to run the test case. Any additional requirements are included in the Optional Features section. If the CPE supports the profile and the optional feature listed, the test case MUST be run.

    • Note: For test cases that require Baseline:1 or Baseline:2 support, the CPE MUST support each parameter listed in the test case, but does not need to support each parameter in the profile.

    • A list of test cases by profile is included below. Note, there may be additional parameters required or required parameter values. Refer to the test case for complete information.

Device:2 Profile Applicable Tests
None 5.1.5 GetRPCMethods
5.1.10 Encrypted Connection
Baseline:1 5.1.1 Factory Reset
5.1.4 Firmware Download
5.1.6 Configuration Backup and Restoration
5.1.9 SPV on a Boolean Parameter
5.7.1 Non-Printable ASCII Characters in SetParameterValues RPC (Device:2 Only)
5.7.2 Multi-Byte Encoding in SetParameterValues RPC (Device:2 Only)
5.7.3 Non-ASCII Characters in ParameterKey (Device:2 Only)
5.7.4 Multi-Byte Encoding in ParameterKey (Device:2 Only)
5.7.5 Non-ASCII Characters in CommandKey (Device:2 Only)
5.7.6 Multi-Byte Encoding in CommandKey (Device:2 Only)
Time:1 5.1.2 Time Setting (Device:2 Only)
PPPInterface:1 5.1.7 PPP Interface Change
DHCPv4Server:1 5.1.8 DHCP Provisioning
Vendor specific parameters 5.1.11 GetParameterNames Vendor Specific Parameters
5.1.12 SetParameterValues Vendor Specific Parameters
IPPing:1 OR IPPingDetailed:1 5.2.1 Diagnostics IPPing
Download:1 5.2.2 Download Diagnostics over HTTP
5.2.3 Download Diagnostics over FTP
Upload:1 5.2.4 Upload Diagnostics over HTTP
5.2.5 Upload Diagnostics over FTP
TraceRoute:1 5.2.6 TraceRoute
UDPEcho:1 5.2.7 UDPEcho Test
Baseline:2, IPInterface:1, EtherenetInterface:1, WiFiSSID:1, WiFiRadio:1 5.3.1 Current Interface Configuration (Device:2 Only)
Hosts:2 5.3.3 Connected LAN Devices – Wi-Fi (Device:2 Only)
Hosts:2, DHCPv4ServerClientInfo:1, DHCPv6ServerClientInfo 5.3.4 Connected LAN Devices – DHCP (Device:2 Only)
Hosts:1 5.3.5 Device Connect/Disconnect Notification Test
NAT:1 5.4.1 Create a Port Mapping – Single Interface
5.4.2 Create a Port Mapping – All Interfaces (Device:2 only)
5.4.3 Create a Port Mapping – External Port Range
5.4.4 Create a Port Mapping – Lease Duration > 0
5.4.5 Create a Port Mapping – Remote Host Restriction
5.4.6 Create a Port Mapping – Multiple Entries – Precedence Rules
5.4.7 Modify a Port Mapping
5.4.8 Delete a Port Mapping
5.4.9 Create a Port Mapping – TCP
AdvancedFirewall:1 5.5.1 Default Policy (Device:2 Only)
5.5.2 Deny/Allow Outbound Protocols (Device:2 Only)
5.5.3 Deny/Allow Outbound Ports (Device:2 Only)
5.5.4 Deny/Allow Source IP Address (Device:2 Only)
WiFiRadio:1, WiFiSSID:1, WiFiAccessPoint:1 5.6.6 Wi-Fi Setup WEP 64 (Device:2 Only)
5.6.7 Wi-Fi Setup WEP 128 (Device:2 Only)
5.6.8 Wi-Fi Setup WPA Personal (Device:2 Only)
5.6.9 Wi-Fi Setup WPA Enterprise (Device:2 Only)
5.6.10 Wi-Fi Setup WPA2 Personal (Device:2 only)
5.6.11 Wi-Fi Setup WPA2 Enterprise (Device:2 Only)
5.6.12 Wi-Fi Setup WPA-WPA2 Personal (Device:2 Only)
5.6.13 Wi-Fi Setup WPA-WPA2 Enterprise (Device:2 Only)
5.6.14 Wi-Fi Setup WPA3 Personal (Device:2 only)
5.6.15 Wi-Fi Setup WPA3-Personal-Transition (Device:2 only)
5.6.16 Wi-Fi Setup WPA3-Enterprise (Device:2 only)
5.6.17 Wi-Fi Setup – Add SSID (Device:2 Only)
5.6.18 Wi-Fi Setup – Remove SSID (Device:2 Only)
InternetGatewayDevice:1 Profile Applicable Tests
None 5.1.5 GetRPCMethods
5.1.10 Encrypted Connection
Baseline:1 5.1.1 Factory Reset
5.1.4 Firmware Download
5.1.6 Configuration Backup and Restoration
5.1.9 SPV on a Boolean Parameter
5.3.5 Device Connect/Disconnect Notification Test
5.4.1 Create a Port Mapping – Single Interface
5.4.3 Create a Port Mapping – External Port Range
5.4.4 Create a Port Mapping – Lease Duration > 0
5.4.5 Create a Port Mapping – Remote Host Restriction
5.4.6 Create a Port Mapping – Multiple Entries – Precedence Rules
5.4.7 Modify a Port Mapping
5.4.8 Delete a Port Mapping
5.4.9 Create a Port Mapping – TCP
Time:2 5.1.3 Time Setting (InternetGatewayDevice:1 Only)
Baseline:2 5.1.7 PPP Interface Change
5.3.2 Connected LAN Devices (InternetGatewayDevice:1 Only)
5.1.8 DHCP Provisioning
Vendor specific parameters 5.1.11 GetParameterNames Vendor Specific Parameters
5.1.12 SetParameterValues Vendor Specific Parameters
Baseline:1, IPPing:1 5.2.1 Diagnostics IPPing
Download:1 5.2.2 Download Diagnostics over HTTP
5.2.3 Download Diagnostics over FTP
Upload:1 5.2.4 Upload Diagnostics over HTTP
5.2.5 Upload Diagnostics over FTP
TraceRoute:1 5.2.6 TraceRoute
UDPEcho:1 5.2.7 UDPEcho Test
WiFiLan:1 5.6.1 Wi-Fi Setup WEP 64 (InternetGatewayDevice:1 Only)
5.6.2 Wi-Fi Setup WEP 128 (InternetGatewayDevice:1 Only)
5.6.3 Wi-Fi Setup WPA Personal (InternetGatewayDevice:1 Only)
5.6.4 Wi-Fi Setup WPA2 Personal (InternetGatewayDevice:1 Only)
5.6.5 Wi-Fi Setup WPA-WPA2 Personal (InternetGatewayDevice:1 Only)

4.4 ACS Test Requirements

The ACS MUST be configurable to include an interface that allows control of the ACS to execute the test procedures. An API SHOULD be provided to the test lab to support automation of this test plan. The ACS MUST allow its certificates to be configured.

4.5 Interoperability Testing

This test plan tests the ACS/CPE system, therefore a failure may indicate a deficiency from either the ACS or CPE.

4.6 Test Validation

A test is considered successful (or passed) when the corresponding test procedure has been completed and the specified success metrics are attained. Tests can be validated by observing functional changes in the DUTs, through feedback interfaces on the devices under test, results attained from the ACS, and via a Traffic Analyzer connected to the relevant links.