The architecture of the processor on the underlying hardware. Enumeration of:

• arm
• i386
• m68010
• m68k
• mipseb (big-endian)
• mipsel (little-endian)
• powerpc
• sh3eb (big-endian)
• sh3el (little-endian)
• x86_64 For processor architectures not included in this list, the vendor MAY include vendor-specific values, which MUST use the format defined in [Section 3.3/TR-106a4].

The current state that the process is in. Enumeration of:

• Running
• Sleeping
• Stopped
• Idle (OPTIONAL)
• Uninterruptible (OPTIONAL)
• Zombie (OPTIONAL)

The status of this temperature sensor. Enumeration of:

• Disabled (The sensor is not currently sampling the temperature)
• Enabled (The sensor is currently sampling the temperature)
• Error (The sensor error currently prevents sampling the temperature)

When set to true, resets the temperature sensor.

When read, this parameter returns false, regardless of the actual value.

• Status transition from Disabled to Enabled
• Reset set to true.
• An internal reset of the temperature sensor (including a reboot of the device). The Unknown Time value, as defined in [TR-106a2], indicates that this temperature sensor has never been reset, which can only happen if it has never been enabled.

This temperature sensor’s low alarm value in degrees celsius. A value of -274 (which is below absolute zero) indicates a non configured value.

A change to this value will cause LowAlarmTime to be reset.

This temperature sensor’s high alarm value in degrees celsius. A value of -274 (which is below absolute zero) indicates a non configured value.

A change to this value will cause HighAlarmTime to be reset.

Comma-separated list of strings. Indicates the TCP congestion control mechanism(s) implemented. Each list item is an enumeration of:

• Tahoe (Represents the base TCP implementation in [RFC793] and elements of [RFC2582])
• Reno (Represents the base TCP implementation in [RFC793] with the additional algorithms defined in [RFC2581])
• New Reno (Described as a modification to the Reno algorithms in [RFC2582])
• Vegas (An emerging TCP congestion control mechanism) Tahoe, Reno, and New Reno are defined in [RFC2582]

Identifies the source of the location data. Enumeration of:

• GPS
• AGPS
• Manual
• External

URL, MAC address, or other identifier that identifies an “External” source of this location. Meaningful only if Source has a value of External, otherwise it MUST be an empty string. If ExternalProtocol has a value of CWMP, this is the URL or IP address of the ACS.

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

Protocol used to acquire a location from an “External” source. Enumeration of:

• <Empty> (An empty string)
• CWMP
• OMA-DM
• SNMP
• UPnP
• HELD
• DHCPv4
• DHCPv6
• LLDP-MED
• MLP
• Other Meaningful only if Source has a value of External, otherwise it MUST be an empty string.

The currently valid location information. Writable only when ExternalProtocol has a value of CWMP. If obtained through the local GPS/AGPS then the location information is formatted according to [RFC5491].

If manually configured then location information will be XML-formatted according to [RFC5491] (geographical information) and [RFC5139] (civic addresses). If obtained by an external source this is the location information as received. If it’s an XML document (e.g. CWMP, OMA-DM, UPnP, HELD, MLP) the location information will be represented as-is, otherwise it will be converted to base64. CWMP configured location information will be XML-formatted according to [RFC5491] (geographical information) and [RFC5139] (civic addresses). Only zero or one Location object instance with value CWMP MUST exist at any given time.

• <feature name=“DNSServer”/>
• <feature name=“Router”/>
• <feature name=“X_MyDeviceFeature”/> then the value of this parameter might be DNSServer,Router,X_MyDeviceFeature. The order in which the features are listed is not significant.

Organizationally unique identifier of the associated CPE Proxier. Represented as a six hexadecimal-digit value using all upper-case letters and including any leading zeros. Possible patterns:

• [0-9A-F]{6} The value MUST be a valid OUI as defined in [OUI].

The protocol being used to communicate between the CPE Proxier and this Proxied Device. Enumeration of:

• Z-Wave (see [Z-Wave])
• ZigBee (see [ZigBee])
• UPnP-DM (see [UPnP-DM:1])
• ETSI-M2M (see [ETSIM2MFA]) Vendors can extend the enumerated values with vendor specific extensions, in which case the rules outlined in [Section 3.3/TR-106a6] MUST be adhered to.

Comma-separated list of strings. Indicates the Deployment Unit operations that MUST be included when the CPE notifies the ACS of “12 AUTONOMOUS DU STATE CHANGE COMPLETE” events. Operation types not indicated by this list MUST NOT be included when the CPE notifies the ACS. An empty string is essentially the same as setting Enable to false. Each list item is an enumeration of:

• Install
• Update
• Uninstall

Indicates the Deployment Unit state change results that MUST be included when the CPE notifies the ACS of “12 AUTONOMOUS DU STATE CHANGE COMPLETE” events. State change results omitted from this filter MUST NOT be included when the CPE notifies the ACS. Enumeration of:

• Success (The autonomous state change completed successfully; i.e., the FaultCode was zero)
• Failure (The autonomous state change did not complete successfully; i.e., the FaultCode was non-zero)
• Both (All result types independent of Success or Failure)

Comma-separated list of strings. Indicates the Deployment Unit state change fault codes that MUST be included when the CPE notifies the ACS of “12 AUTONOMOUS DU STATE CHANGE COMPLETE” events. State change fault codes omitted from this filter MUST NOT be included when the CPE notifies the ACS. This filter has no effect on the notification of a successful autonomous state change. This filter only applies when ResultTypeFilter is set to either Failure or Both. An empty string means that failed autonomous state changes will not be sent to the ACS. Each list item is an enumeration of:

• 9001
• 9003
• 9012
• 9013
• 9015
• 9016
• 9017
• 9018
• 9022
• 9023
• 9024
• 9025
• 9026
• 9027
• 9028
• 9029
• 9030
• 9031
• 9032

Indicates the transfer types that MUST be included when the CPE notifies the ACS of AUTONOMOUS TRANSFER COMPLETE events. Transfer types not indicated by this filter MUST NOT be included when the CPE notifies the ACS. Enumeration of:

• Upload
• Download
• Both (Upload and Download) Note that this includes any backup or restore operations that were not specifically requested by the ACS. A backup is regarded as an Upload and a restore is regarded as a Download.

Indicates the transfer results that MUST be included when the CPE notifies the ACS of AUTONOMOUS TRANSFER COMPLETE events. Transfer results omitted from this list MUST NOT be included when the CPE notifies the ACS. Note that this includes any backup or restore operations that were not specifically requested by the ACS. A backup is regarded as an Upload and a restore is regarded as a Download. Enumeration of:

• Success (The autonomous file transfer completed successfully; i.e., the FaultCode was zero)
• Failure (The autonomous file transfer did not complete successfully; i.e., the FaultCode was non-zero)
• Both (Success and Failure)

Comma-separated list (maximum number of characters per item 1024) of strings. Indicates the file types that MUST be included when the CPE notifies the ACS of AUTONOMOUS TRANSFER COMPLETE events. File types omitted from this list MUST NOT be included when the CPE notifies the ACS.

Each list item matches one of:

• 1 Firmware Upgrade Image (Download Only)
• 2 Web Content (Download Only)
• 3 Vendor Configuration File (Download or Upload)
• 4 Vendor Log File (Upload Only)
• X [0-9A-F]{6} .* (For Vendor-Specific File Types, could be for either Download or Upload) Additionally, the following format is defined to allow the unique definition of vendor-specific file types:
• “X <OUI> <Vendor-specific identifier>” <OUI> is replaced by a 6 hexadecimal-digit OUI (organizationally unique identifier) as defined in [OUI], with all upper-case letters and any leading zeros included. The OUI used for a given vendor-specific file type MUST be one that is assigned to the organization that defined this file type (which is not necessarily the same as the vendor of the CPE or ACS). Note that an empty string indicates that all file types are excluded from this filter, effectively disabling CPE notification of AUTONOMOUS TRANSFER COMPLETE events to the ACS.

Identifier of the controller that is responsible for a sub-network of Proxied Devices within the LAN. An empty string indicates that this Proxied Device either:

• Isn’t part of a sub-network, within the LAN, with a controller entity.
• Doesn’t need a ControllerID to ensure its ProxiedDeviceID is unique throughout the LAN.

The protocol being used to communicate between the CPE Proxier and this Proxied Device. Enumeration of:

• Z-Wave (see [Z-Wave])
• ZigBee (see [ZigBee])
• UPnP-DM (see [UPnP-DM:1])
• ETSI-M2M (see [ETSIM2MFA]) Vendors can extend the enumerated values with vendor specific extensions, in which case the rules outlined in [Section 3.3/TR-106a6] MUST be adhered to.

Comma-separated list of strings, that represents the discovery protocol(s) for this proxied device. Each list item is an enumeration of:

• Z-Wave (see [Z-Wave])
• ZigBee (see [ZigBee])
• UPnP (see [UPnP-DAv1])
• ETSI-M2M (see [ETSIM2MFA]) Vendors can extend the enumerated values with vendor specific extensions, in which case the rules outlined in [Section 3.3/TR-106a3] MUST be adhered to.

• {{object: non-existent .UPnP.Discovery.RootDevice}}
• {{object: non-existent .UPnP.Discovery.Device}}
• {{object: non-existent .UPnP.Discovery.Service}} For objects discovered by the ETSI-M2M discovery protocol, the DiscoveryProtocolReference would contain items that are references to instances of ETSIM2M.SCL.{i}.AreaNwkDeviceInfoInstance.

Whether or not the CPE Proxier has successfully communicated all pending configuration commands down to the Proxied Device. Enumeration of:

• Pending
• Retrying
• Success
• Error

Organizationally unique identifier of the associated Proxied Device. Represented as a six hexadecimal-digit value using all upper-case letters and including any leading zeros. Possible patterns:

• [0-9A-F]{6} The value MUST be a valid OUI as defined in [OUI].

The protocol being used to communicate between the CPE Proxier and this Proxied Device. Enumeration of:

• Z-Wave (see [Z-Wave])
• ZigBee (see [ZigBee])
• UPnP-DM (see [UPnP-DM:1])
• ETSI-M2M (see [ETSIM2MFA]) Vendors can extend the enumerated values with vendor specific extensions, in which case the rules outlined in [Section 3.3/TR-106a6] MUST be adhered to.

Comma-separated list of strings, that represents the discovery protocol(s) for this proxied device. Each list item is an enumeration of:

• Z-Wave (see [Z-Wave])
• ZigBee (see [ZigBee])
• UPnP (see [UPnP-DAv1])
• ETSI-M2M (see [ETSIM2MFA]) Vendors can extend the enumerated values with vendor specific extensions, in which case the rules outlined in [Section 3.3/TR-106a3] MUST be adhered to.

• {{object: non-existent .UPnP.Discovery.RootDevice}}
• {{object: non-existent .UPnP.Discovery.Device}}
• {{object: non-existent .UPnP.Discovery.Service}} For objects discovered by the ETSI-M2M discovery protocol, the DiscoveryProtocolReference would contain items that are references to instances of ETSIM2M.SCL.{i}.AreaNwkDeviceInfoInstance.

Comma-separated list of strings. Indicates the protocols that are supported by the CPE for the purpose of remotely accessing the user interface. Each list item is an enumeration of:

• HTTP (As defined in [RFC2616])
• HTTPS (As defined in [RFC2818])

[Alias]

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

The user’s password.

When read, this parameter returns an empty string, regardless of the actual value.

Indicates the status of this smart card reader. Enumeration of:

• Disabled
• Enabled (Indicates the smart card reader is enabled and functioning properly)
• Error (Indicates the smart card reader is enabled and not functioning properly)

When set to true, resets the SmartCard Reader and the associated SmartCard.

When read, this parameter returns false, regardless of the actual value.

• Status transition from Disabled to Enabled
• Reset set to true.
• An internal reset of the SmartCard Reader (including a reboot of the device). Unknown Time value indicates that this SmartCard Reader has never been reset, which can only happen if it has never been enabled.

Status of the Smart Card. Enumeration of:

• None (Indicates that no Smart Card is inserted)
• Running (Indicates a Smart Card is present and working normally)
• Error (Indicates the Smart Card is present and in an error condition)

Smart Card Type. Enumeration of:

• CA
• DRM
• UICC Vendors can extend the enumerated values with vendor specific extensions, in which case the rules outlined in [Section 3.3/TR-106a2] MUST be adhered to.

Comma-separated list of strings. Indicates Smart Card Application(s). Application is only relevant when Type has a value of UICC, otherwise it is an empty string. Each list item is an enumeration of:

• SIM
• USIM
• ISIM Vendors can extend the enumerated values with vendor specific extensions, in which case the rules outlined in [Section 3.3/TR-106a2] MUST be adhered to.

Indicates availability of diagnostic data. Enumeration of:

• None (READONLY)
• Requested
• Complete (READONLY)
• Error_Internal (READONLY)
• Error_Other (READONLY) If the ACS sets the value of this parameter to Requested, the CPE MUST initiate the corresponding diagnostic test. When writing, the only allowed value is Requested. To ensure the use of the proper test parameters (the writable parameters in this object), the test parameters MUST be set either prior to or at the same time as (in the same SetParameterValues) setting the DiagnosticsState to Requested. When requested, the CPE SHOULD wait until after completion of the communication session with the ACS before starting the diagnostic. When the test is completed, the value of this parameter MUST be either Complete (if the test completed successfully), or one of the Error values listed above. If the value of this parameter is anything other than Complete, the values of the results parameters for this test are indeterminate. When the diagnostic initiated by the ACS is completed (successfully or not), the CPE MUST establish a new connection to the ACS to allow the ACS to view the results, indicating the Event code “8 DIAGNOSTICS COMPLETE” in the Inform message. After the diagnostic is complete, the value of all result parameters (all read-only parameters in this object) MUST be retained by the CPE until either this diagnostic is run again, or the CPE reboots. After a reboot, if the CPE has not retained the result parameters from the most recent test, it MUST set the value of this parameter to None. Modifying any of the writable parameters in this object except for this one MUST result in the value of this parameter being set to None. While the test is in progress, modifying any of the writable parameters in this object except for this one MUST result in the test being terminated and the value of this parameter being set to None. While the test is in progress, setting this parameter to Requested (and possibly modifying other writable parameters in this object) MUST result in the test being terminated and then restarted using the current values of the test parameters.

Indicates availability of diagnostic data. Enumeration of:

• None (READONLY)
• Requested
• Complete (READONLY)
• Error_DNSServerNotResolved (Unable to resolve DNSServer Name, READONLY)
• Error_Internal (READONLY)
• Error_Other (READONLY) If the ACS sets the value of this parameter to Requested, the CPE MUST initiate the corresponding diagnostic test. When writing, the only allowed value is Requested. To ensure the use of the proper test parameters (the writable parameters in this object), the test parameters MUST be set either prior to or at the same time as (in the same SetParameterValues) setting the DiagnosticsState to Requested. When requested, the CPE SHOULD wait until after completion of the communication session with the ACS before starting the diagnostic. When the test is completed, the value of this parameter MUST be either Complete (if the test completed successfully), or one of the Error values listed above. If the value of this parameter is anything other than Complete, the values of the results parameters for this test are indeterminate. When the diagnostic initiated by the ACS is completed (successfully or not), the CPE MUST establish a new connection to the ACS to allow the ACS to view the results, indicating the Event code “8 DIAGNOSTICS COMPLETE” in the Inform message. After the diagnostic is complete, the value of all result parameters (all read-only parameters in this object) MUST be retained by the CPE until either this diagnostic is run again, or the CPE reboots. After a reboot, if the CPE has not retained the result parameters from the most recent test, it MUST set the value of this parameter to None. Modifying any of the writable parameters in this object except for this one MUST result in the value of this parameter being set to None. While the test is in progress, modifying any of the writable parameters in this object except for this one MUST result in the test being terminated and the value of this parameter being set to None. While the test is in progress, setting this parameter to Requested (and possibly modifying other writable parameters in this object) MUST result in the test being terminated and then restarted using the current values of the test parameters.

Result Parameter to represent whether the NS Lookup was successful or not. Errors for individual Result instances do not get bubbled up to DiagnosticsState. A failure on a specific attempt does not mean that the overall test failed, but a failure on all attempts means that DiagnosticsState SHOULD be Error_Other. Enumeration of:

• Success
• Error_DNSServerNotAvailable
• Error_HostNameNotResolved
• Error_Timeout
• Error_Other

Result parameter to represent whether the answer is Authoritative or not. Enumeration of:

• None (Indicates that the NS Lookup failed to find the host)
• Authoritative
• NonAuthoritative

How this firewall is configured. Enumeration of:

• High (The firewall implements the “Traffic Denied Inbound” and “Minimally Permit Common Services Outbound” components of the ICSA residential certification’s Required Services Security Policy [ICSA-Residential]. If DoS and vulnerability protections are implemented [ICSA-Baseline], these are enabled)
• Low (All Outbound traffic and pinhole-defined Inbound traffic is allowed. If DoS and vulnerability protections are implemented [ICSA-Baseline], these are enabled)
• Off (All Inbound and Outbound traffic is allowed, and the CPE is only protected by NAT settings (if supported and enabled). If DoS and vulnerability protections are implemented [ICSA-Baseline], these are disabled) Vendors can extend the enumerated values with vendor specific extensions, in which case the rules outlined in [Section 3.3/TR-106a2] MUST be adhered to.

Type of USB Host Enumeration of:

• OHCI (Open Host Controller Interface)
• EHCI (Enhanced Host Controller Interface)
• UHCI (Universal Host Controller Interface)
• xHCI (Extensible Host Controller Interface)

When set to true, reset the Host Controller and apply the reset signaling (see [Chapter 7.1.7.5/USB2.0]) to all of the Host Controller Hub downstream ports. The value is not saved in the device’s state and setting it to false has no effect.

When read, this parameter returns false, regardless of the actual value.

Speed of the USB device. Enumeration of:

• Low (1.5 Mbits/sec (187.5 KB/sec) defined in [USB1.0])
• Full (12 Mbits/sec (1.5 MB/sec) defined in [USB1.0])
• High (480 Mbits/sec (60 MB/sec) defined in [USB2.0])
• Super (5.0 Gbits/sec (625 MB/sec) defined in [USB3.0]) Internal signaling between the connected USB device and the USB Host Controller provide the information needed to determine the negotiated rate.

The status of the announcement service. Enumeration of:

• Disabled
• Enabled
• Error (MAY be used by the CPE to indicate a locally defined error condition, OPTIONAL)

[Alias]

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

The status of this group table entry. Enumeration of:

• Disabled
• Enabled
• Error (MAY be used by the CPE to indicate a locally defined error condition, e.g. unable to parse received announcements, OPTIONAL)

The status of the query service. Enumeration of:

• Disabled
• Enabled
• Error (MAY be used by the CPE to indicate a locally defined error condition, e.g. unable to contact query response server, OPTIONAL)

Indicates the status of this SoftwareModules.ExecEnv.{i}.. Enumeration of:

• Up
• Error (OPTIONAL)
• Disabled

1. All Deployment Units that were installed after the last “0 BOOTSTRAP” Inform event MUST be removed
2. All persistent storage, configuration files, and log files that were associated with the removed Deployment Units MUST be removed
3. Any Deployment Unit that is still installed against the Execution Environment MUST be restored to the version present when the last “0 BOOTSTRAP” Inform event was issued
4. Any Deployment Unit that was present when the last “0 BOOTSTRAP” Inform event was issued, but was subsequently uninstalled and is now not present, MUST be installed with the version that was present when the last “0 BOOTSTRAP” Inform event was issued
5. The Execution Environment MUST be restored to the version and configuration present when the last “0 BOOTSTRAP” Inform event was issued
6. The Execution Environment MUST be restarted after all other restoration requirements have been met

Indicates the status of this SoftwareModules.DeploymentUnit.{i}.. Enumeration of:

• Installing (This instance is in the process of being Installed and SHOULD transition to the Installed state)
• Installed (This instance has been successfully Installed. The Resolved flag SHOULD also be referenced for dependency resolution)
• Updating (This instance is in the process of being Updated and SHOULD transition to the Installed state)
• Uninstalling (This instance is in the process of being Uninstalled and SHOULD transition to the Uninstalled state)
• Uninstalled (This instance has been successfully Uninstalled. This status will typically not be seen within a SoftwareModules.DeploymentUnit.{i}. instance)

Indicates the status of this SoftwareModules.ExecutionUnit.{i}.. Enumeration of:

• Idle (This instance is in an Idle state and not running)
• Starting (This instance is in the process of Starting and SHOULD transition to the Active state)
• Active (This instance is currently running)
• Stopping (This instance is in the process of Stopping and SHOULD transition to the Idle state)

Indicates the state transition that the ACS is requesting for this SoftwareModules.ExecutionUnit.{i}.. Enumeration of:

• Idle (If this SoftwareModules.ExecutionUnit.{i}. is currently in Starting or Active the CPE will attempt to Stop the Execution Unit; otherwise this requested state is ignored)
• Active (If this SoftwareModules.ExecutionUnit.{i}. is currently in Idle the CPE will attempt to Start the Execution Unit. If this SoftwareModules.ExecutionUnit.{i}. is in Stopping the request is rejected and a fault raised. Otherwise this requested state is ignored) If this SoftwareModules.ExecutionUnit.{i}. is associated with an Execution Environment that is disabled and an attempt is made to alter this value, then a CWMP Fault MUST be generated.

If while running or transitioning between states this SoftwareModules.ExecutionUnit.{i}. identifies a fault this parameter embodies the problem. The value of NoFault MUST be used when everything is working as intended. Enumeration of:

• NoFault
• FailureOnStart
• FailureOnAutoStart
• FailureOnStop
• FailureWhileActive
• DependencyFailure
• UnStartable For fault codes not included in this list, the vendor MAY include vendor-specific values, which MUST use the format defined in [Section 3.3/TR-106a4].

Indicates the relative level of urgency for operator attention, see [ITU-X.733]. Enumeration of:

• <Empty> (An empty string)
• *
• Cleared
• Critical
• Major
• Minor
• Warning
• Indeterminate This will be an empty string if the device doesn’t support unique indexing of the table using PerceivedSeverity. The string can be set to “*” to indicate the default case if only a subset of PerceivedSeverity are to be contained within the table.

Indicates the reporting mechanism setting of the alarm. Enumeration of:

• 0 Expedited (The device inserts the alarm into the {{object: non-existent .FaultMgmt.ExpeditedEvent.{i}.}} table and the {{object: non-existent .FaultMgmt.ExpeditedEvent.{i}.}} table)
• 1 Queued (The device inserts the alarm into the {{object: non-existent .FaultMgmt.QueuedEvent.{i}.}} table and the {{object: non-existent .FaultMgmt.QueuedEvent.{i}.}} table)
• 2 Logged (The device inserts the alarm into the {{object: non-existent .FaultMgmt.HistoryEvent.{i}.}} table)
• 3 Disabled (The device ignores the alarm)

Indicates the relative level of urgency for operator attention, see [ITU-X.733]. Enumeration of:

• Critical
• Major
• Minor
• Warning
• Indeterminate

Indicates the reason for the specific alarm notification event. Enumeration of:

• NewAlarm
• ChangedAlarm
• ClearedAlarm

Indicates the relative level of urgency for operator attention, see [ITU-X.733]. Enumeration of:

• Cleared
• Critical
• Major
• Minor
• Warning
• Indeterminate

Indicates the reason for the specific alarm notification event. Enumeration of:

• NewAlarm
• ChangedAlarm
• ClearedAlarm

Indicates the relative level of urgency for operator attention, see [ITU-X.733]. Enumeration of:

• Cleared
• Critical
• Major
• Minor
• Warning
• Indeterminate

Indicates the reason for the specific alarm notification event. Enumeration of:

• NewAlarm
• ChangedAlarm
• ClearedAlarm

Indicates the relative level of urgency for operator attention, see [ITU-X.733]. Enumeration of:

• Cleared
• Critical
• Major
• Minor
• Warning
• Indeterminate

[Alias]

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

Indicates availability of Sample statistics. Enumeration of:

• Disabled (Collection is disabled)
• Enabled (Collection is enabled)
• Trigger (Collection is enabled and the ACS SHOULD now fetch the collected data) The Trigger value is only used for triggering the ACS to fetch the collected data and can only be used when FetchSamples is in the range [1:ReportSamples]. The transition from Enabled to Trigger to Enabled MUST be instantaneous and so will result in only a single value change for notification purposes.

• TimeReference has been set to a time other than the Unknown Time and the current sample interval started part of the way through a scheduled sample interval.
• ForceSample has been used to force statistics for the current sample to be calculated and updated in the data model.

[Alias]

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

Controls how this parameter’s value is sampled. Enumeration of:

• Current (Sampled value is current value)
• Change (Sampled value is change in value since start of sample interval) Parameters of non-numeric types can only support Current. The value of the SampleMode MUST be ignored for such parameters.

Controls how this parameter’s statistic is calculated from the sampled value(s). Enumeration of:

• Latest (Statistic is sampled value at end of sample interval)
• Minimum (Statistic is minimum sampled value during sample interval)
• Maximum (Statistic is maximum sampled value during sample interval)
• Average (Statistic is average (mean) sampled value during sample interval) Parameters of non-numeric types can only support Latest. The value of the CalculationMode MUST be ignored for such parameters. SampleMode MUST be applied before CalculationMode, i.e. the inputs to the calculation will have already accounted for SampleMode.

• Any of the reasons for which {{param: non-existent .PeriodicStatistics.SampleSet.{i}.SampleSeconds}} values might be less than {{param: non-existent .PeriodicStatistics.SampleSet.{i}.SampleInterval}}.
• The parameter doesn’t exist, or was created or deleted during a sample interval.

• “in range” : current value is greater than LowThreshold and less than HighThreshold.
• “out of range” : current value is less than or equal to LowThreshold, or greater than or equal to HighThreshold.
• “out of range (low)” : current value is less than or equal to LowThreshold.
• “out of range (high)” : current value is greater than or equal to HighThreshold. Note that, if LowThreshold and HighThreshold are both the same, the threshold/failure mechanism is disabled, so the value of this parameter will not increment. This parameter can be incremented at any time during a sample interval, and might be incremented more than once during a single sample interval. For this reason, the CPE SHOULD place a locally specified limit on the frequency at which it will notify the ACS of such changes, as described in [Section 3.2.1/TR-069a2]. Parameters of non-numeric types cannot support the threshold/failure mechanism. The value of this parameter MUST be ignored for such parameters.

Indicates the status of the Bulk Data Collection mechanism. Enumeration of:

• Enabled (Bulk Data Collection is enabled and working as intended)
• Disabled (Bulk Data Collection is disabled)
• Error (Bulk Data Collection is enabled, but there is an error condition preventing the successful collection of bulk data, OPTIONAL)

Comma-separated list of strings. Represents the IPDR Protocols that this device is capable of supporting. Each list item is an enumeration of:

• Streaming (IPDR Streaming Protocol [IPDR-SP])
• File (IPDR File Transfer Protocol [IPDR-FTP])

Comma-separated list of strings. Represents the IPDR Encoding Types that this device is capable of supporting. Each list item is an enumeration of:

• XML ([IPDR-XML])
• XDR ([IPDR-XDR])

[Alias]

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

Password used for authentication of the FileTransferURL. This is the FileTransferPassword that the IPDR Collector uses to access the CPE when this collection profile is configured for the IPDR File Transfer Protocol [IPDR-FTP] (the Protocol parameter has a value of File).

When read, this parameter returns an empty string, regardless of the actual value.

• <ControlFilePrefix>_<ControlFilePolicy>.<ControlFileSuffix> Where the following rules apply:
• ControlFilePrefix MUST NOT contain an underscore ‘_’ or any other character not suitable for a file name.
• ControlFilePolicy MUST contain one or more ‘N’ characters, where the number of ‘N’ characters denotes the number of digits in the sequence number, including leading zeros as necessary to match the number of ‘N’ characters.
• ControlFileSuffix is a file extension. For example, BulkData_NNNN.log where “BulkData” would be the prefix, “NNNN” would be the policy, and “log” would be the suffix. Files adhering to this file format would look like: BulkData_0000.log, BulkData_0001.log, etc.

The status of the UPnP root device. Enumeration of:

• LeaseActive (Device is active and UPnP lease has not expired)
• LeaseExpired (Device is inactive because UPnP lease has expired)
• ByebyeReceived (Device is inactive because byebye message was received) The ability to list inactive UPnP root devices is OPTIONAL. The length of time an inactive device remains listed in this table is a local matter to the CPE.

This UPnP root device’s UUID (Universally Unique IDentifier) [RFC4122], extracted from any of its USN (Unique Service Name) headers. This is a 36-byte string that uniquely identifies the device, the following is an example:

• 02c29d2a-dbfd-2d91-99c9-306d537e9856

Possible patterns:

• [[0-9A-Fa-f]{8}-(0-9A-Fa-f]{4}-){3}[0-9A-Fa-f]{12}

• uuid:device-UUID::urn:domain-name:device:deviceType:v SSDP is an unreliable protocol and it is possible that no discovery message containing the USN header of the above form was ever received. If so, one of the other two forms MAY be used:
• uuid:device-UUID::upnp:rootdevice
• uuid:device-UUID (for root device UUID)

• OS/version UPnP/udaversion product/version where UPnP is a literal string, udaversion is the version of the UPnP Device Architecture.

The status of the UPnP embedded device. Enumeration of:

• LeaseActive (Device is active and UPnP lease has not expired)
• LeaseExpired (Device is inactive because UPnP lease has expired)
• ByebyeReceived (Device is inactive because byebye message was received) The ability to list inactive UPnP embedded devices is OPTIONAL. The length of time an inactive device remains listed in this table is a local matter to the CPE.

This UPnP embedded device’s UUID (Universally Unique IDentifier) [RFC4122], extracted from any of its USN (Unique Service Name) headers. This is a 36-byte string that uniquely identifies the device, the following is an example:

• 02c29d2a-dbfd-2d91-99c9-306d537e9856

Possible patterns:

• [[0-9A-Fa-f]{8}-(0-9A-Fa-f]{4}-){3}[0-9A-Fa-f]{12}

• uuid:device-UUID::urn:domain-name:device:deviceType:v SSDP is an unreliable protocol and it is possible that no discovery message containing the USN header of the above form was ever received. If so, the other form MAY be used:
• uuid:device-UUID

• OS/version UPnP/udaversion product/version where UPnP is a literal string, udaversion is the version of the UPnP Device Architecture.

The status of the UPnP embedded service. Enumeration of:

• LeaseActive (Service is active and UPnP lease has not expired)
• LeaseExpired (Service is inactive because UPnP lease has expired)
• ByebyeReceived (Service is inactive because byebye message was received) The ability to list inactive UPnP embedded services is OPTIONAL. The length of time an inactive service remains listed in this table is a local matter to the CPE.

The value of the USN (Unique Service Name) header for this UPnP embedded service. This is of the following form:

• uuid:device-UUID::urn:domain-name:service:serviceType:v

• OS/version UPnP/udaversion product/version where UPnP is a literal string, udaversion is the version of the UPnP Device Architecture.

The UPnP Device Architecture version extracted from the specVersion element in the Device Description Document of the discovered root device. The SpecVersion is encoded as “major revison.minor revision”. Possible patterns:

• \d+.\d+

The Transport Protocol associated with the service as defined by the DNS-SD service [Section 4.1.2 Service Names/DNS-SD]. Enumeration of:

• TCP
• UDP

The status of the discovered DNS.SD.Service.{i}. at LastUpdate time. Enumeration of:

• LeaseActive (The DNS.SD.Service.{i}. has received a response record with TTL > 0 and the Service.{i}.TimeToLive has not expired yet. The DNS.SD.Service.{i}. is considered active)
• GoodbyeReceived (The device has received a response record containing TTL=0 indicating a goodbye message and the Service.{i}.TimeToLive has not expired yet. The DNS.SD.Service.{i}. is considered inactive)
• LeaseExpired (The Service.{i}.TimeToLive has expired. The DNS.SD.Service.{i}. is considered inactive) The ability to instantiate an inactive DNS.SD.Service.{i}. is OPTIONAL. The time an inactive DNS.SD.Service.{i}. remains listed in this table is a local matter to the device.