{{docname|Device:2 Root Data Model: Common Object definitions [COMMON]}} {{appdate|November 2020}} {{trname|TR-181i2a14}} November 2020: {{xmlref|tr-181-2-14-0-common|Original}} * Added WWC (5G Wireline Wireless Convergence), PDU (Protocol Data Unit) and FWE (5G Wireline wireless Encapsulation) top-level objects * Updated Cellular object to be applicable to 5G Residential Gateways * Extended support for TR-471 IP-layer metrics, including new IP-layer capacity test * Supported LAN device time-based access-control * Various Wi-Fi improvements November 2020: {{xmlref|tr-181-2-14-1-common|Corrigendum 1}} * Removed duplicate remarks about CWMP BOOTSTRAP from descriptions * Fixed typos Pair of 32-bit signed integers a(i),b(i) with each pair representing a complex component of the uncalibrated echo response (UER); # Real UER component, a(i) # Imaginary UER component, b(i) for values of i starting at i=0. Both values are represented as signed integers. The interpretation of the UER value is as defined in {{bibref|G.996.2|Clause A.2.2.1}}. # the Power Spectral Density (PSD) breakpoint sub-carrier index in the range [0:49152] with Df = 4.3125 kHz frequency spacing, and # the value of the level of the PSD at this sub-carrier expressed in ''0.1 dBm/Hz'' with an offset of -200 dBm/Hz. The range of valid values for PSD is -30 to -200 dBm/Hz. Both values are represented as unsignedInt. # The PSM breakpoint sub-carrier index in the range [0:4095], and # the value of the level of the PSM at this sub-carrier expressed in ''0.1 dBm/Hz'' with an offset of -140 dBm/Hz. Both values are represented as unsignedInt. {{bibref|G.9964|Clause 5.2}} defines limits on PSM breakpoint levels. # The paired frequency spacing index in the range [0:8191], and # The transfer function log value, i.e. [i, TFlog(i * {{param|TFlogGroupSize}} * Df)], where the reference frequency spacing Df = 4.3125 kHz, the index i valid range is 0 to 8191, and TFlog(i * {{param|TFlogGroupSize}} * Df) spans a range from +6.0 dB down to -96.2 dB with units of 0.1 dB. Both values are represented as unsignedInt. Service Slice Type (SST). {{enum}} See {{bibref|3GPP-TS.23.501|Clause 5.15.2.2}}. 5G Enhanced Mobile Broadband Ultra-Reliable Low Latency Communications Massive IoT Vehicle to Everything {{reference}} This is the interface over which the test is to be performed. Downstream actual power spectral density. Interpretation of the value is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation {{bibref|G.997.1}}. Upstream actual power spectral density. Interpretation of the value is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation {{bibref|G.997.1}}. Downstream actual aggregate transmitter power. Interpretation of the value is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation {{bibref|G.997.1}}. Upstream actual aggregate transmitter power. Interpretation of the value is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation {{bibref|G.997.1}}. Downstream linear representation scale. Interpretation of the value is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation {{bibref|G.997.1}}. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 0. Scaling used to represent the upstream linear channel characteristics. Interpretation of the value is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation {{bibref|G.997.1}}. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 0. Number of sub-carriers per sub-carrier group in the downstream direction for {{param|HLINpsds}}. Valid values are 1, 2, 4, and 8. Note: See ITU-T Recommendation {{bibref|G.997.1}}. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 1. Number of sub-carriers per sub-carrier group in the downstream direction for {{param|HLINpsus}}. Valid values are 1, 2, 4, and 8. Note: See ITU-T Recommendation {{bibref|G.997.1}}. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 1. Number of sub-carriers per sub-carrier group in the downstream direction for {{param|HLOGpsds}}. Valid values are 1, 2, 4, and 8. Note: See ITU-T Recommendation {{bibref|G.997.1}}. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 1. Number of sub-carriers per sub-carrier group in the upstream direction for {{param|HLOGpsus}}. Valid values are 1, 2, 4, and 8. Note: See ITU-T Recommendation {{bibref|G.997.1}}. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 1. {{list}} List items represent downstream logarithmic channel characteristics per sub-carrier group. The maximum number of elements is 256 for G.992.3, and 512 for G.992.5. For G.993.2, the number of elements will depend on the value of {{param|HLOGGds}} but will not exceed 512. Interpretation of the values is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation {{bibref|G.997.1}}. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to ''None''. Note: {{param}} is measured during initialization and is not updated during Showtime. {{list}} List items represent upstream logarithmic channel characteristics per sub-carrier group. The maximum number of elements is 64 for G.992.3 and G.992.5. For G.993.2, the number of elements will depend on the value of {{param|HLOGGus}} but will not exceed 512. Interpretation of the values is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation {{bibref|G.997.1}}. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to ''None''. Note: {{param}} is measured during initialization and is not updated during Showtime. Indicates the number of symbols over which {{param|HLOGpsds}} was measured. Note: See ITU-T Recommendation {{bibref|G.997.1}}. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 0. Indicates the number of symbols over which {{param|HLOGpsus}} was measured. Note: See ITU-T Recommendation {{bibref|G.997.1}}. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 0. {{list}} List items represent downstream line attenuation per usable band, as computed during initialization. Number of elements is dependent on the number of downstream bands but will exceed one only for G.993.2. Interpretation of {{param}} is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation {{bibref|G.997.1}}. {{list}} List items represent upstream line attenuation per usable band, as computed during initialization. Number of elements is dependent on the number of upstream bands but will exceed one only for G.993.2. Interpretation of {{param}} is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation {{bibref|G.997.1}}. {{list}} List items represent downstream signal attenuation per usable band, as computed during the L0 (i.e., Showtime) state. Number of elements is dependent on the number of downstream bands but will exceed one only for G.993.2. Interpretation of {{param}} is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation {{bibref|G.997.1}}. {{list}} List items represent upstream signal attenuation per usable band, as computed during the L0 (i.e., Showtime) state. Number of elements is dependent on the number of downstream bands but will exceed one only for G.993.2. Interpretation of {{param}} is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation {{bibref|G.997.1}}. {{list}} List items represent downstream linear channel characteristics per subcarrier group. Maximum number of complex pairs is 256 for G.992.3, and 512 for G.992.5. For G.993.2, the number of pairs will depend on the value of {{param|HLINGds}} but will not exceed 512. Interpretation of the value is as defined in ITU-T Rec. G.997.1. Note: HLIN is not applicable in PLOAM for G.992.1 or G.992.2. Note: See ITU-T Recommendation {{bibref|G.997.1}}. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to ''None''. {{list}} List items represent upstream linear channel characteristics per sub-carrier group. Maximum number of complex pairs is 64 for G.992.3, and G.992.5. For G.993.2, the number of pairs will depend on the value of {{param|HLINGus}} but will not exceed 512. Interpretation of the values is as defined in ITU-T Rec. G.997.1. Note: HLIN is not applicable in PLOAM for G.992.1 or G.992.2. Note: See ITU-T Recommendation {{bibref|G.997.1}}. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to ''None''. Number of sub-carriers per sub-carrier group in the downstream direction for {{param|QLNpsds}}. Valid values are 1, 2, 4, and 8. Note: See ITU-T Recommendation {{bibref|G.997.1}}. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 1. Number of sub-carriers per sub-carrier group in the upstream direction for {{param|QLNpsus}}. Valid values are 1, 2, 4, and 8. Note: See ITU-T Recommendation {{bibref|G.997.1}}. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 1. {{list}} List items represent downstream quiet line noise per subcarrier group. Maximum number of elements is 256 for G.992.3, 512 for G.992.5. For G.993.2, the number of elements will depend on the value of {{param|QLNGds}} but will not exceed 512. Interpretation of the value is as defined in ITU-T Rec. G.997.1. Note: QLN is not applicable in PLOAM for G.992.1 or G.992.2. Note: See ITU-T Recommendation {{bibref|G.997.1}}. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to ''None''. {{list}} List items represent upstream quiet line noise per subcarrier group. The maximum number of elements is 64 for G.992.3, and G.992.5. For G.993.2, the number of elements will depend on the value of {{param|QLNGus}} but will not exceed 512. Interpretation of the values is as defined in ITU-T Rec. G.997.1. Note: QLN is not applicable in PLOAM for G.992.1 or G.992.2. Note: See ITU-T Recommendation {{bibref|G.997.1}}. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to ''None''. Indicates the number of symbols over which {{param|QLNpsds}} was measured. Note: See ITU-T Recommendation {{bibref|G.997.1}}. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 0. Indicates the number of symbols over which {{param|QLNpsus}} was measured. Note: See ITU-T Recommendation {{bibref|G.997.1}}. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 0. Number of sub-carriers per sub-carrier group in the downstream direction for {{param|SNRpsds}}. Valid values are 1, 2, 4, and 8. Note: See ITU-T Recommendation {{bibref|G.997.1}}. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 1. Number of sub-carriers per sub-carrier group in the upstream direction for {{param|SNRpsus}}. Valid values are 1, 2, 4, and 8. Note: See ITU-T Recommendation {{bibref|G.997.1}}. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 1. {{list}} List items represent downstream SNR per subcarrier group. Maximum number of elements is 256 for G.992.3, 512 for G.992.5. For G.993.2, the number of elements will depend on the value of {{param|SNRGds}} but will not exceed 512. Interpretation of the value is as defined in ITU-T Rec. G.997.1. Interpretation of the value is as defined in ITU-T Rec. G.997.1. Note: SNRps is not applicable in PLOAM for G.992.1 or G.992.2. Note: See ITU-T Recommendation {{bibref|G.997.1}}. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to ''None''. {{list}} List items represent upstream SNR per subcarrier group. The maximum number of elements is 64 for G.992.3, and G.992.5. For G.993.2, the number of elements will depend on the value of {{param|SNRGus}} but will not exceed 512. Interpretation of the values is as defined in ITU-T Rec. G.997.1. Note: SNRps is not applicable in PLOAM for G.992.1 or G.992.2. Note: See ITU-T Recommendation {{bibref|G.997.1}}. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to ''None''. Indicates the number of symbols over which {{param|SNRpsds}} was measured. Note: See ITU-T Recommendation {{bibref|G.997.1}}. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 0. Indicates the number of symbols over which {{param|SNRpsus}} was measured. Note: See ITU-T Recommendation {{bibref|G.997.1}}. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 0. {{list}} List items represent downstream bit allocation per subcarrier group. Maximum number of elements is 256 for G.992.3, 512 for G.992.5. Interpretation of the value is as defined in ITU-T Rec. {{bibref|G.997.1}}. {{list}} List items represent upstream bit allocation per subcarrier group. Maximum number of elements is 256 for G.992.3, 512 for G.992.5. Interpretation of the value is as defined in ITU-T Rec. {{bibref|G.997.1}}. {{reference}} This is the interface over which the test is to be performed. This parameter is the SELT UER maximum measurement duration (MMD) measured in {{units}}. This parameter is defined as SELT_UER_MMD_R in ITU-T Recommendation {{bibref|G.996.2|Clause A.2.1.1}}. This parameter indicates if the option for extended bandwidth SELT is applied ({{true}}) or not applied ({{false}}). If the option for extended bandwidth SELT is applied to UER, then {{param|UERGroupSize}} has three valid values: 1, 2 and 12. If the option for extended bandwidth SELT is not applied to UER, then {{param|UERGroupSize}} has two valid values: 1 and 2. {{param|UERGroupSize}} is reported if the option for extended bandwidth UER SELT is supported; otherwise, reporting of the group size is optional. The Uncalibrated Echo Response (UER) [a(0),b(0)], [a(1),b(1)], ... {{list|with each list item consisting of the following}} {{datatype|expand}} The value of UER at frequency i*{{param|UERGroupSize}}*Df = ({{param|UERScaleFactor}}/(2^31))*(a(i)+j*b(i))/(2^31) where Df = 4.3125 kHz. This parameter is defined as CPE SELT uncalibrated echo response (SELT-UER-R) in ITU-T Recommendation {{bibref|G.996.2|Clause A.2.2.1}}. The Uncalibrated Echo Response (UER) scale factor. This parameter is defined as part of the CPE SELT uncalibrated echo response (SELT-UER-R) in ITU-T Recommendation {{bibref|G.996.2|Clause A.2.2.1}}. Note that the scale factor is chosen such that max(abs(a(i)), abs(b(i))) over all i is equal to 2^31 - 1, which doesn't allow {{param}} to be zero. The Uncalibrated Echo Response (UER) group size, UER_G. In units of {{units}}. This parameter is defined as part of the CPE SELT uncalibrated echo response (SELT-UER-R) in ITU-T Recommendation {{bibref|G.996.2|Clause A.2.2.2}}. This parameter represents the variance of the {{param|UER}}. List items represent v(i), for values of i starting at i=0. The variance of the uncalibrated echo response for frequency i*{{param|UERGroupSize}}*Df is VAR(i*{{param|UERGroupSize}}*Df) = 3 - v(i)/2 dB where Df = 4.3125 kHz. This parameter is defined as SELT variance of uncalibrated echo response R (SELT UER-VAR-R) in {{bibref|G.996.2|Clause A.2.2.2}}. {{reference}} This is the interface over which the test is to be performed. This parameter is the SELT QLN maximum measurement duration (MMD) measured in {{units}}. This parameter is defined as SELT_QLN_MMD_R in ITU-T Recommendation {{bibref|G.996.2|Clause A.2.1.2}}. This parameter indicates if the option for extended bandwidth SELT is applied ({{true}}) or not applied ({{false}}). If the option for extended bandwidth SELT is applied to QLN, then {{param|QLNGroupSize}} has three valid values: 1, 2 and 12. If the option for extended bandwidth SELT is not applied to QLN, then {{param|QLNGroupSize}} has two valid values: 1 and 2. {{param|QLNGroupSize}} is reported if the option for extended bandwidth QLN SELT is supported; otherwise, reporting of the group size is optional. {{list}} List items represent SELT quiet line noise (QLN) per subcarrier group. Each list element is n(i), with i starting at 0. The value of QLN at frequency i*{{param|QLNGroupSize}}*Df with Df=4.3125 kHz is defined as QLN(i*{{param|QLNGroupSize}}*Df) = -23 - (n(i)/2) dBm/Hz. This data format supports a QLN granularity of 0.5 dB and an dynamic range of -150 to -23 dBm/Hz. Interpretation of the SELT_QLN_R value is defined in {{bibref|G.996.2|Clause A.2.2.3}}. This parameter represents the Quiet Line Noise (QLN) group size. In units of {{units}}. This parameter is defined as part of the SELT_QLN_R in ITU-T Recommendation {{bibref|G.996.2|Clause A.2.2.4}}. {{reference}} This is the interface over which the test is to be performed. Capacity estimate calculation enabling: This parameter is expressed as a boolean and takes the value {{false}} if xDSL performance estimation is not required, {{true}} otherwise. The capacity estimate calculation enabling parameter is defined in {{bibref|G.996.2|Clause B.2.1.1}}. The capacity estimate signal Power Spectral Density (PSD): {{list|with each list item consisting of the following}} {{datatype|expand}} This capacity estimate signal PSD parameter is defined in ITU-T Recommendation {{bibref|G.996.2|Clause B.2.1.2}}. The capacity estimate noise Power Spectral Density (PSD): {{list|with each list item consisting of the following}} {{datatype|expand}} This capacity estimate noise PSD parameter is defined in ITU-T Recommendation {{bibref|G.996.2|Clause B.2.1.3}}. The capacity estimate target noise margin. The range of valid values is 0 to 31 dB, in steps of {{units}}. This capacity estimate target noise margin parameter is defined in ITU-T Recommendation {{bibref|G.996.2|Clause B.2.1.4}}. Loop termination indicator. {{enum}} This parameter is defined as LOOP-TERM in ITU-T Recommendation {{bibref|G.996.2|Clause B.1.1.1}}. This value has been removed from the ITU-T Recommendation. This parameter is the loop length with units of {{units}}. This parameter is defined as the loop length parameter LOOP_LEN in ITU-T Recommendation {{bibref|G.996.2|Clause B.1.1.2}}. {{list}} List items represent paired parameters [LOOP_SEG_LEN, LOOP_SEG_BTAP] representing a concatenation of loop segment types, where LOOP_SEG_LEN represents the length of the segment in meters; and LOOP_SEG_BTAP is a string that identifies the segment type as either "in series" or "bridged tap". The first loop segment in the list shall be the segment connected to the SELT-PMD block, subsequent loop segments in the list shall describe the loop in the direction toward the far-end loop termination. This Loop Topology parameter is defined in ITU-T Recommendation {{bibref|G.996.2|Clause B.1.1.3}}. Specifies the list of attenuation characteristics. {{list|with each list item consisting of the following}} {{datatype|expand}} TFlog(i * {{param|TFlogGroupSize}} * Df) is represented by an integer k, 0 <= k <= 1022, where TFlog(i * {{param|TFlogGroupSize}} * Df) = 6.0 - k * 0.1. The special value of k of 1023 is used to indicate that no measurement could be done for this subcarrier because the attenuation is out of the range that can be represented. The attenuation characteristics TFlog(f) parameter is defined in ITU-T Recommendation {{bibref|G.996.2|Clause B.1.1.6}}. This parameter represents the Transfer Function Log (TFlog) group size. In units of {{units}}. This parameter is defined as part of the SELT attenuation characteristics, {{param|AttenuationCharacteristics}}, defined in ITU-T Recommendation {{bibref|G.996.2|Clause B.1.1.6}}. Missing micro-filter or splitter: This parameter is a binary indication of a missing or incorrectly installed splitter or micro-filter at the U-R reference point. A value of true represents a missing splitter. The missing micro-filter or splitter parameter is defined in {{bibref|G.996.2|Clause B.1.1.4}}. Capacity Estimate: {{list}} This parameter represents the downstream and/or upstream capacity estimates in {{units}}. If only one value is supplied, then it's not specified whether it's the downstream value, the upstream value or some combination of the two. If two values are supplied, then the first is the downstream value and the second is the upstream value. The capacity estimate parameters are defined in {{bibref|G.996.2|Clause B.1.1.7}}. {{reference}} This is the interface over which the test is to be performed. Number of repetitions of the ping test to perform before reporting the results. Timeout in {{units}} for the ping test. Result parameter indicating the number of successful pings (those in which a successful response was received prior to the timeout) in the most recent ping test. Result parameter indicating the number of failed pings in the most recent ping test. Result parameter indicating the average response time in {{units}} over all repetitions with successful responses of the most recent ping test. If there were no successful responses, this value MUST be zero. Result parameter indicating the minimum response time in {{units}} over all repetitions with successful responses of the most recent ping test. If there were no successful responses, this value MUST be zero. Result parameter indicating the maximum response time in {{units}} over all repetitions with successful responses of the most recent ping test. If there were no successful responses, this value MUST be zero. {{reference}} This is the interface over which the test is to be performed. Number of test packet in burst to be send during PHY diagnostics test from each HPNA device to other HPNA device in the HPNA network. Test packet burst interval length (expressed in {{units}}). Payload length in the test packets. HPNA payload encoding in PHY diagnostics. 0 is used for negotiated payload between devices according to line conditions. Test packets payload data generator value. Test packets payload type. {{enum}} In Pattern mode the PayloadDataGen value is repeated pattern in the payload. In IncrementByte mode LSByte in PayloadDataGen is used as first payload and next bytes in payload are incremented. Priority level of PHY diagnostics packets (0 lowest -7 highest). {{reference}} This is the interface over which the test is to be performed. Time in {{units}} between automatic collection of performance monitoring data. A value of zero disables automatic collection of data. The CPE MAY impose a minimum sample interval, in which case an attempt to set a (non-zero) interval that is less than this minimum MUST set the interval to the minimum and MUST NOT be regarded as an error. If SampleInterval is a simple fraction of a day, e.g. 900 (a quarter of an hour) or 3600 (an hour), the CPE MAY choose to align sample intervals with time of day, but is not required to do so. The interface over which the test is to be performed. The MAC address of the originating G.hn interface of the link that is being diagnosed. Note: This MAC address might belong to another node of the domain. The interface over which the test is to be performed. The MAC address of the originating G.hn interface of the link that is being diagnosed. Note: This MAC address might belong to another node of the domain. Time in {{units}} between automatic collection of performance monitoring data. A value of zero disables automatic collection of data. The node MAY impose a minimum sample interval, in which case an attempt to set a (non-zero) interval that is less than this minimum MUST set the interval to the minimum and MUST NOT be regarded as an error. If SampleInterval is a simple fraction of a day, e.g. 900 (a quarter of an hour) or 3600 (an hour), the device MAY choose to align sample intervals with time of day, but is not required to do so. The number of sub-carriers in a group to be used for averaging SNR values when providing SNR information for a channel. MAC address target of the magic packet. The SecureOn password. The parameter value can be empty or, if present, can contain either 4 bytes or 6 bytes. Indicates the type of port measurement test to be carried out. {{enum}}. Signal-to-Noise-Ratio Channel Frequency Response {{reference}} This is the local UPA interface from which the test is to be performed. PLC port being measured. This identifies which PLC connection to measure between the local interface (indicated by {{param|Interface}}) and the remote device (implied by {{param}}). {{list}} Result of Signal-to-Noise-Ratio measurement (if {{param|Type}} is {{enum|SNR|Type}}) or Channel Frequency Response measurement (if {{param|Type}} is {{enum|CFR|Type}}). List items indicate measurements per carrier for a PLC port (expressed in {{units}}). Reception gain of the adapter (expresssed in {{units}}). {{reference}} The layer 2 or layer 3 interface over which the test is to be performed. Example: ''Device.IP.Interface.1'', ''Device.Bridge.1.Port.2'' If {{empty}} is specified, the CPE MUST use the interface as directed by its bridging or routing policy (''Forwarding'' table entries) to determine the appropriate interface. Indicates the IP protocol to be used. Use either IPv4 or IPv6 depending on the system preference Use IPv4 for the Ping requests Use IPv6 for the Ping requests Host name or address of the host to ping. In the case where {{param}} is specified by name, and the name resolves to more than one address, it is up to the device implementation to choose which address to use. Number of repetitions of the ping test to perform before reporting the results. Timeout in {{units}} for the ping test. Size of the data block in bytes to be sent for each ping. DiffServ codepoint to be used for the test packets. By default the CPE SHOULD set this value to zero. Indicates which IP address was used to send the Ping request. The parameter is only valid if the {{param|DiagnosticsState}} is {{enum|Complete|DiagnosticsState}}. Result parameter indicating the number of successful pings (those in which a successful response was received prior to the timeout) in the most recent ping test. Result parameter indicating the number of failed pings in the most recent ping test. Result parameter indicating the average response time in {{units}} over all repetitions with successful responses of the most recent ping test. If there were no successful responses, this value MUST be zero. Result parameter indicating the minimum response time in {{units}} over all repetitions with successful responses of the most recent ping test. If there were no successful responses, this value MUST be zero. Result parameter indicating the maximum response time in {{units}} over all repetitions with successful responses of the most recent ping test. If there were no successful responses, this value MUST be zero. Result parameter indicating the average response time in {{units}} over all repetitions with successful responses of the most recent ping test. If there were no successful responses, this value MUST be zero. Result parameter indicating the minimum response time in {{units}} over all repetitions with successful responses of the most recent ping test. If there were no successful responses, this value MUST be zero. Result parameter indicating the maximum response time in {{units}} over all repetitions with successful responses of the most recent ping test. If there were no successful responses, this value MUST be zero. {{reference}} The layer 2 or layer 3 interface over which the test is to be performed. Example: ''Device.IP.Interface.1'', ''Device.Bridge.1.Port.2'' If {{empty}} is specified, the CPE MUST use the interface as directed by its bridging or routing policy (''Forwarding'' table entries) to determine the appropriate interface. Indicates the IP protocol to be used. Use either IPv4 or IPv6 depending on the system preference Use IPv4 for the TraceRoute Use IPv6 for the TraceRoute Host name or address of the host to find a route to. In the case where {{param}} is specified by name, and the name resolves to more than one address, it is up to the device implementation to choose which address to use. Number of tries per hop. Set prior to running Diagnostic. By default, the CPE SHOULD set this value to 3. Timeout in {{units}} for each hop of the trace route test. By default the CPE SHOULD set this value to 5000. Size of the data block in bytes to be sent for each trace route. By default, the CPE SHOULD set this value to 38. DiffServ codepoint to be used for the test packets. By default the CPE SHOULD set this value to 0. The maximum number of hop used in outgoing probe packets (max TTL). By default the CPE SHOULD set this value to 30. Indicates which IP address was used for TraceRoute. The parameter is only valid if the {{param|DiagnosticsState}} is {{enum|Complete|DiagnosticsState}}. Result parameter indicating the response time in {{units}} the most recent trace route test. If a route could not be determined, this value MUST be zero. Supported ''DownloadDiagnostics'' transport protocols for a CPE device. Indicates the maximum number of connections that are supported by Download Diagnostics. The maximum number of rows in {{object|IncrementalResult}} that the CPE will store. {{reference}} The IP-layer interface over which the test is to be performed. Example: Device.IP.Interface.1 If {{empty}} is specified, the CPE MUST use the interface as directed by its routing policy (''Forwarding'' table entries) to determine the appropriate interface. The {{datatype}} for the CPE to perform the download on. This parameter MUST be in the form of a valid HTTP {{bibref|RFC2616}} or FTP {{bibref|RFC959}} URL. * When using FTP transport, FTP binary transfer MUST be used. * When using HTTP transport, persistent connections MUST be used and pipelining MUST NOT be used. * When using HTTP transport the HTTP Authentication MUST NOT be used. Note: For time based tests ({{param|TimeBasedTestDuration}} > 0) the Controller MAY add a hint to duration of the test to the URL. See {{bibref|TR-143|Section 4.3}} for more details. The DiffServ code point for marking packets transmitted in the test. The default value SHOULD be zero. Ethernet priority code for marking packets transmitted in the test (if applicable). The default value SHOULD be zero. Controls time based testing {{bibref|TR-143|Section 4.3}}. When {{param}} > 0, {{param}} is the duration in {{units}} of a time based test. If {{param}} is 0, the test is not based on time, but on the size of the file to be downloaded. The default value SHOULD be 0. The measurement interval duration in {{units}} for objects in {{object|IncrementalResult}} for a time based FTP/HTTP download test (when {{param|TimeBasedTestDuration}} > 0). The default value SHOULD be 0, which implies {{object|IncrementalResult}} collection is disabled. For example if {{param|TimeBasedTestDuration}} is 90 {{units}} and {{param}} is 10 {{units}}, there will be 9 results in {{object|IncrementalResult}}, each with a 10 {{units}} duration. This {{param}} works in conjunction with {{param|TimeBasedTestMeasurementInterval}} to allow the interval measurement to start a number of {{units}} after {{param|BOMTime}}. The test measurement interval in {{object|IncrementalResult}} starts at time {{param|BOMTime}} + {{param}} to allow for slow start window removal of file transfers. This {{param}} is in {{units}}. The default value SHOULD be 0. Indicates the IP protocol version to be used. The default value SHOULD be {{enum|Any}}. Use either IPv4 or IPv6 depending on the system preference. Use IPv4 for the requests Use IPv6 for the requests. The number of connections to be used in the test. The default value SHOULD be 1. {{param}} MUST NOT be set to a value greater than {{param|DownloadDiagnosticMaxConnections}}. The results must be returned in the {{object|PerConnectionResult}} table for every connection when set to {{true}}. The default value SHOULD be {{false}}. Indicates which IP address was used to send the request. Request time in UTC, which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456Z * For HTTP this is the time at which the client sends the GET command. * For FTP this is the time at which the client sends the RTRV command. If multiple connections are used, then {{param}} is set to the earliest {{param}} across all connections. Begin of transmission time in UTC, which MUST be specified to microsecond precision For example: 2008-04-09T15:01:05.123456Z * For HTTP this is the time at which the first data packet is received. * For FTP this is the time at which the client receives the first data packet on the data connection. If multiple connections are used, then {{param}} is set to the earliest {{param}} across all connections. End of transmission in UTC, which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456Z * For HTTP this is the time at which the last data packet is received. * For FTP this is the time at which the client receives the last packet on the data connection. If multiple connections are used, then {{param}} is set to the latest {{param}} across all connections. The number of {{units}} received during the FTP/HTTP transaction including FTP/HTTP headers, between {{param|BOMTime}} and {{param|EOMTime}} across all connections. The total number of {{units}} (at the IP layer) received on the Interface between {{param|BOMTime}} and {{param|EOMTime}}. This MAY be calculated by sampling Stats.bytesReceived on the {{param|Interface}} object at {{param|BOMTime}} and at {{param|EOMTime}} and subtracting. The total number of {{units}} (at the IP layer) sent on the Interface between {{param|BOMTime}} and {{param|EOMTime}}. This MAY be calculated by sampling Stats.bytesSent on the {{param|Interface}} object at {{param|BOMTime}} and at {{param|EOMTime}} and subtracting. The number of {{units}} of the test file received between the latest {{param|PerConnectionResult.{i}.BOMTime}} and the earliest {{param|PerConnectionResult.{i}.EOMTime}} across all connections. The total number of {{units}} (at the IP layer) received in between the latest {{param|PerConnectionResult.{i}.BOMTime}} and the earliest {{param|PerConnectionResult.{i}.EOMTime}}. This MAY be calculated by sampling Stats.bytesReceived on the {{param|Interface}} object at the latest {{param|PerConnectionResult.{i}.BOMTime}} and at the earliest {{param|PerConnectionResult.{i}.EOMTime}} and subtracting. The total number of {{units}} (at the IP layer) sent between the latest {{param|PerConnectionResult.{i}.BOMTime}} and the earliest {{param|PerConnectionResult.{i}.EOMTime}}. This MAY be calculated by sampling Stats.bytesSent on the {{param|Interface}} object at the latest {{param|PerConnectionResult.{i}.BOMTime}} and at the earliest {{param|PerConnectionResult.{i}.EOMTime}} and subtracting. The period of time in {{units}} between the latest {{param|PerConnectionResult.{i}.BOMTime}} and the earliest {{param|PerConnectionResult.{i}.EOMTime}} of the test. Request time in UTC, which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456Z * For HTTP this is the time at which the TCP socket open (SYN) was sent for the HTTP connection. * For FTP this is the time at which the TCP socket open (SYN) was sent for the data connection. Note: Interval of 1 microsecond SHOULD be supported. If multiple connections are used, then {{param}} is set to the latest {{param}} across all connections. Response time in UTC, which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456Z * For HTTP this is the time at which the TCP ACK to the socket opening the HTTP connection was received. * For FTP this is the time at which the TCP ACK to the socket opening the data connection was received. Note: Interval of 1 microsecond SHOULD be supported. If multiple connections are used, then {{param}} is set to the latest {{param}} across all connections. Supported ''UploadDiagnostics'' transport protocols for a CPE device. Indicates the maximum number of connections that are supported by Upload Diagnostics. The maximum number of rows in {{object|IncrementalResult}} that the CPE will store. {{reference}} The IP-layer interface over which the test is to be performed. Example: Device.IP.Interface.1 If {{empty}} is specified, the CPE MUST use the interface as directed by its routing policy (''Forwarding'' table entries) to determine the appropriate interface. The {{datatype}} for the CPE to Upload to. This parameter MUST be in the form of a valid HTTP {{bibref|RFC2616}} or FTP {{bibref|RFC959}} URL. * When using FTP transport, FTP binary transfer MUST be used. * When using HTTP transport, persistent connections MUST be used and pipelining MUST NOT be used. * When using HTTP transport the HTTP Authentication MUST NOT be used. DiffServ code point for marking packets transmitted in the test. The default value SHOULD be zero. Ethernet priority code for marking packets transmitted in the test (if applicable). The default value SHOULD be zero. The size of the file (in bytes) to be uploaded to the server. The CPE MUST insure the appropriate number of bytes are sent. Controls time based testing {{bibref|TR-143|Section 4.3}}. When {{param}} > 0, {{param}} is the duration in {{units}} of a time based test. If {{param}} is 0, the test is not based on time, but on the size of the file to be uploaded. The default value SHOULD be 0. The measurement interval duration in {{units}} for objects in {{object|IncrementalResult}} for a time based FTP/HTTP upload test (when {{param|TimeBasedTestDuration}} > 0). The default value SHOULD be 0, which implies {{object|IncrementalResult}} collection is disabled. For example if {{param|TimeBasedTestDuration}} is 90 {{units}} and {{param}} is 10 {{units}}, there will be 9 results in {{object|IncrementalResult}}, each with a 10 {{units}} duration. This {{param}} works in conjunction with {{param|TimeBasedTestMeasurementInterval}} and allows the interval measurement to start a number of {{units}} after {{param|BOMTime}}. The test measurement interval in {{object|IncrementalResult}} starts at time {{param|BOMTime}} + {{param}} to allow for slow start window removal of file transfers. This {{param}} is in {{units}}. The default value SHOULD be 0. Indicates the IP protocol version to be used. The default value SHOULD be {{enum|Any}}. Use either IPv4 or IPv6 depending on the system preference. Use IPv4 for the requests Use IPv6 for the requests. The number of connections to be used in the test. The default value SHOULD be 1. {{param}} MUST NOT be set to a value greater than {{param|UploadDiagnosticsMaxConnections}}. The results must be returned in the {{object|PerConnectionResult}} table for every connection when set to {{true}}. The default value SHOULD be {{false}}. Indicates which IP address was used to send the request. Request time in UTC, which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456Z * For HTTP this is the time at which the client sends the GET command. * For FTP this is the time at which the client sends the RTRV command. If multiple connections are used, then {{param}} is set to the earliest {{param}} across all connections. Begin of transmission time in UTC, which MUST be specified to microsecond precision For example: 2008-04-09T15:01:05.123456Z * For HTTP this is the time at which the first data packet is received. * For FTP this is the time at which the client receives the first data packet on the data connection. If multiple connections are used, then {{param}} is set to the earliest {{param}} across all connections. End of transmission in UTC, which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456Z * For HTTP this is the time at which the last data packet is received. * For FTP this is the time at which the client receives the last packet on the data connection. If multiple connections are used, then {{param}} is set to the latest {{param}} across all connections. The number of {{units}} of the test file sent during the FTP/HTTP transaction including FTP/HTTP headers, between {{param|BOMTime}} and {{param|EOMTime}} acrosss all connections. The total number of {{units}} (at the IP layer) received on the Interface between {{param|BOMTime}} and {{param|EOMTime}}. This MAY be calculated by sampling Stats.bytesReceived on the {{param|Interface}} object at {{param|BOMTime}} and at {{param|EOMTime}} and subtracting. The total number of {{units}} (at the IP layer) sent on the Interface between {{param|BOMTime}} and {{param|EOMTime}}. This MAY be calculated by sampling Stats.bytesSent on the {{param|Interface}} object at {{param|BOMTime}} and at {{param|EOMTime}} and subtracting. The number of {{units}} of the test file sent between the latest {{param|PerConnectionResult.{i}.BOMTime}} and the earliest {{param|PerConnectionResult.{i}.EOMTime}} across all connections. The total number of {{units}} (at the IP layer) received between the latest {{param|PerConnectionResult.{i}.BOMTime}} and the earliest {{param|PerConnectionResult.{i}.EOMTime}} across all connections in the test. This MAY be calculated by sampling Stats.bytesReceived on the {{param|Interface}} object at the latest {{param|PerConnectionResult.{i}.BOMTime}} and at the earliest {{param|PerConnectionResult.{i}.EOMTime}} and subtracting. The total number of {{units}} (at the IP layer) sent between the latest {{param|PerConnectionResult.{i}.BOMTime}} and the earliest {{param|PerConnectionResult.{i}.EOMTime}} across all connections in the test. This MAY be calculated by sampling Stats.bytesSent on the {{param|Interface}} object at the latest {{param|PerConnectionResult.{i}.BOMTime}} and at the earliest {{param|PerConnectionResult.{i}.EOMTime}} and subtracting. The period of time in {{units}} between the latest {{param|PerConnectionResult.{i}.BOMTime}} and the earliest {{param|PerConnectionResult.{i}.EOMTime}} of the test. Request time in UTC, which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456Z * For HTTP this is the time at which the TCP socket open (SYN) was sent for the HTTP connection. * For FTP this is the time at which the TCP socket open (SYN) was sent for the data connection. Note: Interval of 1 microsecond SHOULD be supported. If multiple connections are used, then {{param}} is set to the latest {{param}} across all connections. Response time in UTC, which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456Z * For HTTP this is the time at which the TCP ACK to the socket opening the HTTP connection was received. * For FTP this is the time at which the TCP ACK to the socket opening the data connection was received. Note: Interval of 1 microsecond SHOULD be supported. If multiple connections are used, then {{param}} is set to the latest {{param}} across all connections. The maximum number of rows in {{object|IndividualPacketResult}} that the CPE will store. If a test would create more rows than {{param}} only the first {{param}} rows are present in {{object|IndividualPacketResult}}. {{reference|the IP-layer interface over which the test is to be performed|ignore}} Example: Device.IP.Interface.1 If {{empty}} is specified, the CPE MUST use the interface as directed by its routing policy (''Forwarding'' table entries) to determine the appropriate interface. Host name or address of the host to perform tests to. Port on the host to perform tests to. Number of repetitions of the test to perform before reporting the results. The default value SHOULD be 1. Timeout in {{units}} for the test. That is, the amount of time to wait for the return of a packet that was sent to the {{param|Host}}. Size of the data block in {{units}} to be sent for each packet. The default value SHOULD be 24. DiffServ codepoint to be used for the test packets. The default value SHOULD be zero. The time in {{units}} between the {{param|NumberOfRepetitions}} of packets sent during a given test. The default value SHOULD be 1000. Indicates the IP protocol version to be used. The default value SHOULD be {{enum|Any}}. Use either IPv4 or IPv6 depending on the system preference. Use IPv4 for the requests Use IPv6 for the requests. The results must be returned in the {{object|IndividualPacketResult}} table for every repetition of the test when set to {{true}}. The default value SHOULD be {{false}}. Indicates which IP address was used to send the request. Result parameter indicating the number of successful packets (those in which a successful response was received prior to the timeout) in the most recent test. Result parameter indicating the number of failed packets (those in which a successful response was not received prior to the timeout) in the most recent test. Result parameter indicating the average response time in {{units}} over all repetitions with successful responses of the most recent test. If there were no successful responses, this value MUST be zero. Result parameter indicating the minimum response time in {{units}} over all repetitions with successful responses of the most recent test. If there were no successful responses, this value MUST be zero. Result parameter indicating the maximum response time in {{units}} over all repetitions with successful responses of the most recent test. If there were no successful responses, this value MUST be zero. Indicates the maximum number of connections that are supported for an IP-Layer Capacity test. The maximum number of rows in {{object|IncrementalResult}} that the device will store. Indicates the test metrics from {{bibref|TR-471|Section 5.2}} that are supported by the device. IP packet Loss Ratio Sampled Round Trip Time IP packet Delay Variation IP packet Reordering Ratio Note that {{bibref|TR-471}} mandates support for and use of IPLR and Sampled RTT. {{reference}} The IP-layer interface over which the test is to be performed. Example: Device.IP.Interface.1 If {{empty}} is specified, the device MUST use the interface as directed by its routing policy (''Forwarding'' table entries) to determine the appropriate interface. Indicates whether the device will act as Sender or Receiver of test packets. The device will act as the Receiver. The device will act as the Sender. The Fully Qualified Domain Name (FQDN) or IP address of the Test Endpoint to perform the UDP Capacity tests with. Port on the Test Endpoint host. If {{true}}, jumbo frames are allowed. Default SHOULD be {{false}}. The number of connections to be used in the test. The default value SHOULD be 1. {{param}} MUST NOT be set to a value greater than {{param|#.IPLayerMaxConnections}}. Ethernet priority code for marking packets transmitted in the test (if applicable). The default value SHOULD be zero. The DiffServ code point for marking packets transmitted in the test. The default value SHOULD be zero. Indicates the IP protocol version to be used. The default value SHOULD be {{enum|Any}}. Use either IPv4 or IPv6 depending on the system preference. Use IPv4 for the requests Use IPv6 for the requests. Minimum reference size of UDP payload in {{units}}. No default. The implementation will algorithmically determine a value if none is configured. The value SHOULD be set to a value that avoids fragmentation (i.e., using path MTU discovery). Maximum reference size of UDP payload in {{units}}. No default. The implementation will algorithmically determine a value if none is configured. The value SHOULD be set to the largest value that avoids fragmentation (i.e., using path MTU discovery). If {{param|JumboFramesPermitted}} is {{false}}, the maximum value MUST be 1472 octets. If {{param|JumboFramesPermitted}} is {{true}}, this value can be as large as 9000 octets. {{param}} MUST be greater than or equal to {{param|UDPPayloadMin}}. Starting value for range of Dynamic Ports supported for test traffic and status feedback messages. Indicates the upper bound of the supported Dynamic Port range, where {{param|PortMin}} indicates the starting port number. {{param}} MUST be greater than or equal to {{param|PortMin}}. Starting value for range of User Ports supported for test traffic and status feedback messages. A value of zero (0) indicates no User Ports are used for test traffic or status feedback messages. Indicates the upper bound of the supported User Port range, where {{param|PortOptionalMin}} indicates the starting port number. {{param}} MUST be greater than or equal to {{param|PortOptionalMin}}. A value of zero (0) indicates no User Ports are used for test traffic or status feedback messages. Indicates the type of IP-Layer Capacity test being run. The default value SHOULD be {{enum|Search}}. Search algorithm will be used to determine sending rate. Fixed sending rate will be used. Enables IPDV (IP packet Delay Variation) metric. Default SHOULD be {{false}}. Enables IPRR (IP packet Reordering Ratio) metric. Default SHOULD be {{false}}. Duration of the preamble testing, when traffic is being sent and/or received but the test clock has not been started. This is done to ensure all network elements in the path are "awake". The default value SHOULD be 2 {{units}}. Value specified in {{units}}. The Sending Rate for a {{enum|Fixed|TestType}} test or the initial Sending Rate value for a {{enum|Search|TestType}} test. Value specified in {{units}}. The default SHOULD be 500 {{units}}. Number of intermediate measurement reporting intervals. The value MUST NOT be greater than {{param|#.IPLayerMaxIncrementalResult}}. The default value SHOULD be 10. Duration of intermediate measurement reporting intervals. {{param}} * {{param|NumberTestSubIntervals}} MUST result in an integer value in seconds, in the range 5 seconds <= {{param}} * {{param|NumberTestSubIntervals}} <= 60 seconds. The default value SHOULD be 1000 {{units}}. Value specified in {{units}}. Period of status feedback message (receiver of offered load returns messages to the sender with results of measured metrics). Value specified in {{units}}. The default SHOULD be 50 {{units}}. Timeout value. Value specified in {{units}}. The default value SHOULD be 5 {{units}}. Maximum waiting time for packets to arrive. Value specified in {{units}}. The default SHOULD be 1000 {{units}}. Maximum Round Trip Time waiting time for packets to arrive. Value specified in {{units}}. The default SHOULD be 3000 {{units}}. Indicates the requested precision of timestamp values. The test implementation will determine the actual precision to use based on the implemented resolution capabilities of the protocols used and this requested value. If the implemented resolution capabilities of the {{param|#.IPLayerCapSupportedMetrics}} protocols being used are able to provide the requested resolution, this resolution SHOULD be provided. Value specified in {{units}}. The default SHOULD be 1 {{units}}. This parameter is only meaningful if {{param|TestType}} is {{enum|Search|TestType}}. The lower threshold on the range of Round Trip Time (RTT) variation. Value specified in {{units}}. The default SHOULD be 30 {{units}}. This parameter is only meaningful if {{param|TestType}} is {{enum|Search|TestType}}. The upper threshold on the range of Round Trip Time (RTT) variation. Value specified in {{units}}. The default SHOULD be 90 {{units}}. This parameter is only meaningful if {{param|TestType}} is {{enum|Search|TestType}}. The number of rows to move in a single adjustment when initially increasing offered load (to ramp up quickly). The default SHOULD be 10. This parameter is only meaningful if {{param|TestType}} is {{enum|Search|TestType}}. Threshold on the measured number of consecutive status reports indicating loss and/or delay variation above {{param|UpperThresh}} (SlowAdjCount). The default SHOULD be 2. This parameter is only meaningful if {{param|TestType}} is {{enum|Search|TestType}}. Threshold for transition between low and high sending rate step sizes (such as 1Mbps and 100 Mbps). If {{param|JumboFramesPermitted}} is {{true}} this may result in use of jumbo frames. The default SHOULD be 1 {{units}}. Beginning of transmission send/receive time in UTC, which MUST be specified to {{param|TimestampResolution}} precision. If multiple connections are used, then {{param}} is set to the earliest value across all connections. For example: 2008-04-09T15:01:05.123456Z End of transmission in UTC, which MUST be specified to {{param|TimestampResolution}} precision. If multiple connections are used, then {{param}} is set to the latest value across all connections. For example: 2008-04-09T15:01:05.123456Z Configured value of {{param|Tmax}} used in the test. This value is expressed in {{units}}. Duration of the test (either downlink or uplink). This value is expected to equal {{param|TestSubInterval}} * {{param|NumberTestSubIntervals}}. This value is expressed in {{units}}. The maximum IP-Layer Capacity metric from among all {{param|IncrementalResult.{i}.IPLayerCapacity}} values measured between {{param|BOMTime}} and {{param|EOMTime}} across all connections for this test. This is calculated according to {{bibref|TR-471}} Equation 1. Result is expressed in {{units}} with 3 digits beyond the decimal. 10^6 bits/second = 1 Mbps. Time in UTC of end of the sub-interval when {{param|MaxIPLayerCapacity}} was measured. If the value of {{param|MaxIPLayerCapacity}} occurred in multiple sub-intervals, this MUST be the earliest of these sub-intervals. Value MUST be specified to {{param|TimestampResolution}} precision. For example: 2008-04-09T15:01:05.123456Z Ratio of lost packets to total packets during sub-interval of {{param|MaxIPLayerCapacity}}. This value is expressed as a decimal to 9 decimal digits. The range of Round Trip Time (RTT) during sub-interval of {{param|MaxIPLayerCapacity}}. This value is expressed in {{units}}. This value is expressed as a decimal to 9 decimal digits. The range of Packet Delay Variation (PDV) during sub-interval of {{param|MaxIPLayerCapacity}}. This value is expressed in {{units}}. This value is expressed as a decimal to 9 decimal digits. The minimum one-way delay during the sub-interval of {{param|MaxIPLayerCapacity}}. The minimum one-way delay is calculated at the conclusion of the test and SHALL be calculated using the conditional distribution of all packets with a finite one-way delay value (undefined delays are excluded). This value is expressed in {{units}}. This value is expressed as a decimal to 9 decimal digits. Ratio of reordered packets to total packets during the sub-interval of {{param|MaxIPLayerCapacity}}. This value is expressed as a decimal to 9 decimal digits. Configured value of {{param|TmaxRTT}} used in the test. This value is expressed in {{units}}. Indicates the timestamp resolution of reported results. Value specified in {{units}}. {{reference|the IP-layer interface over which the test is to be performed|ignore}} Example: Device.IP.Interface.1 If {{empty}} is specified, the CPE MUST use the interface as directed by its routing policy (''Forwarding'' table entries) to determine the appropriate interface. Indicates the IP protocol version to be used. Use either IPv4 or IPv6 depending on the system preference. Use IPv4 for the requests. Use IPv6 for the requests. The protocol over which the test is to be performed. Each entry is a Host name or address of a host to ping. Number of repetitions of the ping test to perform for each {{param|HostList}} entry before reporting the results. Timeout in {{units}} for each iteration of the ping test where the total number of iterations is the value of {{param|NumberOfRepetitions}} times the number of entities in the {{param|HostList}} Parameter. Result parameter indicating the Host (one of the items within the {{param|HostList}} Parameter) with the smallest average response time. Result parameter indicating the minimum response time in {{units}} over all repetitions with successful responses of the most recent ping test for the Host identified in {{param|FastestHost}}. Success is defined by the underlying protocol used. If there were no successful responses across all Hosts, this value MUST be zero. Result parameter indicating the average response time in {{units}} over all repetitions with successful responses of the most recent ping test for the Host identified in {{param|FastestHost}}. Success is defined by the underlying protocol used. If there were no successful responses across all Hosts, this value MUST be zero. Result parameter indicating the maximum response time in {{units}} over all repetitions with successful responses of the most recent ping test for the Host identified in {{param|FastestHost}}. Success is defined by the underlying protocol used. If there were no successful responses across all Hosts, this value MUST be zero. Indicates which IP address was used to send the request to the host identified in {{param|FastestHost}}. Results of self-test (vendor specific). {{reference}} The layer 2 or layer 3 interface over which the test is to be performed. Example: ''Device.IP.Interface.1'', ''Device.Bridge.1.Port.2'' If {{empty}} is specified, the CPE MUST use the interface as directed by its bridging or routing policy (''Forwarding'' table entries) to determine the appropriate interface. Specifies the Host Name that NS Lookup is to look for. The current domain name MUST be used unless the name is a fully qualified name. Specifies the DNS Server name or IP address that NS Lookup is to use for the lookup. The name of this server will be resolved using the default DNS server unless an IP address is provided. If {{empty}} is specified, the device's default DNS server will be used. Timeout in {{units}} that indicates that a request has failed. The number of times the device SHOULD repeat the execution of the NSLookup using the same input parameters. If the diagnostics test fails the CPE MAY terminate the test without completing the full number of repetitions. Each repetition will use a Result instance to hold the NSLookup result data. Number of successfully executed repetitions. A reference to a (layer 2 or above) interface object that will be the target of this packet capture diagnostic. This indicates whether the network trace will be recorded in libpcap {{bibref|LIBPCAP}} or pcapng format, and is dependent on the underlying method of performing a network trace. The packet data is recorded in libpcap {{bibref|LIBPCAP}} format. The packet data is recorded in pcapng format. The duration in {{units}} to copy packets to the file target. The diagnostic completes when either the {{param}}, {{param|PacketCount}}, or {{param|ByteCount}} conditions are met. The maximum number of packets to record to the file target. A value of zero (0) indicates no limit. The diagnostic completes when the {{param|Duration}}, {{param|ByteCount}}, or {{param}} conditions are met. The maximum number of bytes to record to the file target. A value of zero (0) indicates no limit. The diagnostic completes when {{param|Duration}}, {{param|PacketCount}} or {{param}} conditions are met. The {{datatype}} specifying the destination file location. HTTP and HTTPS transports MUST be supported. Other transports MAY be supported. A ({{bibref|BPF}}) formatted expression used to restrict the types of network packets that are recorded to {{param|FileTarget}}. Username to be used by the Agent to authenticate with the file location. This string is set to {{empty}} if no authentication is required. Password to be used by the Agent to authenticate with the file location. This string is set to {{empty}} if no authentication is required. When read, this parameter returns an empty string, regardless of the actual value. The Public Land Mobile Network (PLMN) globally identifies the service provider. A PLMN consists of a country code (MCC) and a network code (MNC). See {{bibref|3GPP-TS.23.003|Clause 12.1}}. For example, a PLMN of 50101 refers to MCC 501 (Australia) and MNC 01 (Telstra). The AMFId identifies an AMF instance within a service provider's network. In conjunction with the PLMN, it forms a Globally Unique AMF Id (GUAMI) which globally uniquely identifes an AMF. See {{bibref|3GPP-TS.23.003|Clause 2.10}}. The Temporary Mobile Subscriber Identity (TMSI) is allocatred by the AMF at the time of registration and uniquely identifies the CPE. See {{bibref|3GPP-TS.23.003|Clause 2.4}}. The components necessary to uniquely describe a S-NSSAI. {{enum}} For example * The most common usage where network slicing is not used: * ServiceSliceType=eMBB * When network slicng is used * ServiceSliceType=eMBB * SliceDifferentiator=3 The Slice Service Type (SST). {{enum}} See {{bibref|3GPP-TS.23.501|Clause 5.15.2.2}}. The Slice differentiator is an optional number used to differentiate network slices with the same SST. See {{bibref|3GPP-TS.23.501|Clause 5.15.2.1}}.