This object contains general device information. Each list item is a device category (e.g. "AV_TV" and "AV_Recorder"), or the value is {{empty}} if no such element is provided by the device. Note: It is assumed that this list might be used for HTIP (Home-network Topology Identifying Protocol) {{bibref|JJ-300.00}} and {{bibref|G.9973}}. Standard HTIP device categories are defined in {{bibref|JJ-300.01}}. In this case, the maximum length of the list is 127 and of each item is 31, and any non-HTIP device categories SHOULD NOT conflict with standard HTIP device categories. The manufacturer of the CPE (human readable string). Organizationally unique identifier of the device manufacturer. Represented as a six hexadecimal-digit value using all upper-case letters and including any leading zeros. {{pattern}} The value MUST be a valid OUI as defined in {{bibref|OUI}}. This value MUST remain fixed over the lifetime of the device, including across firmware updates. Model name of the CPE (human readable string). The model number of the device (human readable string), or {{empty}} if no model number is provided by the device. Note: It is assumed that this string might be used for HTIP (Home-network Topology Identifying Protocol) {{bibref|JJ-300.00}} and {{bibref|G.9973}}. In this case, the maximum length of the string is 31. A full description of the CPE device (human readable string). Identifier of the class of product for which the serial number applies. That is, for a given manufacturer, this parameter is used to identify the product or class of product over which the {{param|SerialNumber}} parameter is unique. This value MUST remain fixed over the lifetime of the device, including across firmware updates. Identifier of the particular device that is unique for the indicated class of product and manufacturer. This value MUST remain fixed over the lifetime of the device, including across firmware updates. A string identifying the particular CPE model and version. A string identifying the software version currently installed in the CPE (i.e. version of the overall CPE firmware). To allow version comparisons, this element SHOULD be in the form of dot-delimited integers, where each successive integer represents a more minor category of variation. For example, ''3.0.21'' where the components mean: ''Major.Minor.Build''. {{noreference}}A full path reference to the row in the {{object|FirmwareImage}} table representing the currently running firmware image. {{noreference}}A full path reference to the row in the {{object|FirmwareImage}} table of the firmware image that is to be loaded the next time the device boots. This parameter value cannot be empty and must point to a valid and enabled {{object|FirmwareImage}} object where the ({{param|FirmwareImage.{i}.Available}} parameter is set to 'true'). Out of the factory, this parameter should be set to point to the firmware image the CPE will attempt to boot when first powered on. The firmware image instance referenced by this parameter must also have an Available parameter value of 'true'. Attempting to set this parameter to point to a non-enabled firmware image MUST result in the CPE responding with a CWMP fault (9007). In situations where the CPE cannot boot the firmware image specified by this parameter and manages to boot a different firmware image, the CPE MUST NOT modify this value to point to the alternate firmware image that is currently active. {{list}} Each entry is an additional version. Represents any additional hardware version information the vendor might wish to supply. {{list}} Each entry is an additional version. Represents any additional software version information the vendor might wish to supply. Identifier of the primary service provider and other provisioning information, which MAY be used by the ACS to determine service provider-specific customization and provisioning parameters. Time in {{units}} since the CPE was last restarted. Date and time in UTC that the CPE first both successfully established an IP-layer network connection and acquired an absolute time reference using NTP or equivalent over that network connection. The CPE MAY reset this date after a factory reset. If NTP or equivalent is not available, this parameter, if present, SHOULD be set to the Unknown Time value. The hostname of the device {{bibref|RFC1123|Section 2 General issues}}. This can be either a Fully Qualified Domain Name (FQDN) or just the first component of an FQDN. For example, myhgw, myhgw.home, myhgw.home.arpa, myhgw.isp.net. {{numentries}} {{numentries}} {{numentries}} {{numentries}} {{numentries}} {{numentries}} Every instance of this object is a Vendor Configuration File, and contains parameters associated with the Vendor Configuration File. This table of Vendor Configuration Files is for information only and does not allow the Controller to operate on these files in any way. {{template|VENDORCONFIGFILE-DESC}} {{datatype|expand}} Name of the vendor configuration file. If the CPE is able to obtain the name of the configuration file from the file itself, then the value of this parameter MUST be set to that name. Otherwise, if the CPE can extract the file name from the URL used to download the configuration file, then the value of this parameter MUST be set to that name. {{template|VENDORCONFIGFILE-NAME}} A string identifying the configuration file version currently used in the CPE. If the CPE is able to obtain the version of the configuration file from the file itself, then the value of this parameter MUST be set to the obtained value. Otherwise, the value of this parameter MUST be {{empty}}. Date and time when the content of the current version of this vendor configuration file was first applied by the CPE. A description of the vendor configuration file (human-readable string). When {{true}}, this parameter indicates that this {{object}} instance is to be used for backup and restoration purposes. Note: The backup and restore operations may require the use of multiple {{object}} instances. In this scenario the mechanism for detemining the order and combination of {{object}} instances used for backup and restoration purposes is implementation specific. Status of the device's physical memory. The total physical volatile RAM, in {{units}}, installed on the device. The free physical volatile RAM, in {{units}}, currently available on the device. The sum total physical Non-Volatile Memory (NVM), in {{units}}, installed on the device. This memory persists across reboots and can be used by the system, applications, or users. The sum total free physical Non-Volatile Memory (NVM), in {{units}}, currently available on the device. This memory persists across reboots and is available for use by the system, applications, or users. Status of the processes on the device. The total amount of the CPU, in {{units}}, rounded up to the nearest whole {{units}}. In the case that multiple CPU are present, this value represents the average of all CPU. {{numentries}} List of all processes running on the device. The Process Identifier. The name of the command that has caused the process to exist. The size in {{units}} of the memory occupied by the process. The priority of the process where 0 is highest. The amount of time in {{units}} that the process has spent taking up CPU time since the process was started. The current state that the process is in. Status of the temperature of the device. {{numentries}} This object represents information that the device has obtained via sampling an internal temperature sensor. {{datatype|expand}} Indicates whether or not the temperature sensor is enabled. The status of this temperature sensor. The sensor is not currently sampling the temperature. The sensor is currently sampling the temperature. The sensor error currently prevents sampling the temperature. The time at which this temperature sensor was reset. Reset can be caused by: * {{param|Status}} transition from {{enum|Disabled|Status}} to {{enum|Enabled|Status}} * {{template|Reset}}. * An internal reset of the temperature sensor (including a reboot of the device). The Unknown Time value, as defined in {{bibref|TR-106}}, indicates that this temperature sensor has never been reset, which can only happen if it has never been enabled. Name of this temperature sensor. This text MUST be sufficient to distinguish this temperature sensor from other temperature sensors. This temperature sensor's last good reading in {{units}}. A value of -274 (which is below absolute zero) indicates a good reading has not been obtained since last reset. The time at which this temperature sensor's last good reading was obtained. The Unknown Time value, as defined in {{bibref|TR-106}}, indicates a good reading has not been obtained since last reset. This temperature sensor's lowest value reading in {{units}} since last reset. A value of -274 (which is below absolute zero) indicates a good reading has not been obtained since last reset. The time at which this temperature sensor's lowest value was read. The Unknown Time value, as defined in {{bibref|TR-106}}, indicates a good reading has not been obtained since last reset. This temperature sensor's highest value reading in {{units}} since last reset. A value of -274 (which is below absolute zero) indicates a good reading has not been obtained since last reset. The time at which this temperature sensor's highest value was read. The Unknown Time value, as defined in {{bibref|TR-106}}, indicates a good reading has not been obtained since last reset. This temperature sensor's low alarm value in {{units}}. A value of -274 (which is below absolute zero) indicates a non configured value. A change to this value will cause {{param|LowAlarmTime}} to be reset. Initial time at which this temperature sensor's {{param|LowAlarmValue}} was encountered. This value is only set the first time the alarm is seen and not changed until the next reset. The Unknown Time value, as defined in {{bibref|TR-106}}, indicates that an alarm has not been encountered since the last reset. This temperature sensor's high alarm value in {{units}}. A value of -274 (which is below absolute zero) indicates a non configured value. A change to this value will cause {{param|HighAlarmTime}} to be reset. The interval, measured in {{units}}, in which the device polls this {{object}}. If the value is 0 then the device selects its own polling interval. If the value is greater than 0 then the device MUST use this value as the polling interval. Initial time at which this temperature sensor's {{param|HighAlarmValue}} was encountered. This value is only set the first time the alarm is seen and not changed until the next reset. The Unknown Time value, as defined in {{bibref|TR-106}}, indicates that an alarm has not been encountered since the last reset. This object defines the parameters that describe how the device handles network traffic. The maximum number of {{units}} of outstanding data a sender can send on a particular connection prior to an acknowledgment {{bibref|RFC793}}. Any scaling factor SHOULD be included in this parameter {{bibref|RFC1323}}. {{list}} Indicates the TCP congestion control mechanism(s) implemented. {{enum}} Tahoe, Reno, and New Reno are defined in {{bibref|RFC2582}} Represents the base TCP implementation in {{bibref|RFC793}} and elements of {{bibref|RFC2582}} Represents the base TCP implementation in {{bibref|RFC793}} with the additional algorithms defined in {{bibref|RFC2581}} Described as a modification to the Reno algorithms in {{bibref|RFC2582}} An emerging TCP congestion control mechanism Each table entry represents a hardware or virtual processor that resides on this device. {{datatype|expand}} The architecture of the processor on the underlying hardware. {{enum}} For processor architectures not included in this list, the vendor MAY include vendor-specific values, which MUST use the format defined in {{bibref|TR-106|Section 3.3}}. big-endian little-endian big-endian little-endian Each table entry represents a Vendor Log File. This table of log files is informational only and does not allow the Controller to operate on these files in any way. {{datatype|expand}} Name of the log file. Typically this will be the full file system path, but provided that it is guaranteed to be unique across current and future log files, it MAY be a shorter name derived from the file system path, or be derived via another mechanism. The maximum size of the log file in {{units}}. If the device doesn't know the maximum file size then {{param}} will be 0. When {{true}}, the log file contents are preserved across a device reboot. When {{false}}, the log file contents will be purged when the device is rebooted. This object contains Location information. Identifies the source of the location data. The time when the location was acquired. URL, MAC address, or other identifier that identifies an "External" source of this location. Meaningful only if {{param|Source}} has a value of {{enum|External|Source}}, otherwise it MUST be {{empty}}. If {{param|ExternalProtocol}} has a value of {{enum|CWMP|ExternalProtocol}}, this is the URL or IP address of the Controller. Protocol used to acquire a location from an "External" source. {{enum}} Meaningful only if {{param|Source}} has a value of {{enum|External|Source}}, otherwise it MUST be {{empty}}. {{empty}} The currently valid location information. Writable only when {{param|ExternalProtocol}} has a value of {{enum|CWMP|ExternalProtocol}} or {{enum|USP|ExternalProtocol}}. If obtained through the local GPS/AGPS then the location information is formatted according to {{bibref|RFC5491}}. If manually configured then location information will be XML-formatted according to {{bibref|RFC5491}} (geographical information) and {{bibref|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 or USP configured location information will be XML-formatted according to {{bibref|RFC5491}} (geographical information) and {{bibref|RFC5139}} (civic addresses). Only zero or one Location object instance with value {{enum|CWMP|ExternalProtocol}} or {{enum|USP|ExternalProtocol}} MUST exist at any given time. This object describes an image of the device. {{datatype|expand}} The location of the device that represents the image as the user looks at the front of the device in its typical orientation (e.g., on-end, flat). The device image in PNG, JPEG or GIF format. Top-level object for mapping firmware images. This is a static table – the number of object instances in this table is defined by the firmware that is currently running. {{datatype|expand}} Firmware/software image name. Descriptive text of the image or filename. The value of {{param}} is {{empty}} if {{param|Status}} is anything other than {{enum|Active|Status}}, {{enum|Available|Status}}, {{enum|InstallationFailed|Status}}, or {{enum|ActivationFailed|Status}}. A string identifying the version of the firmware image represented by this {{object}}. Whenever this firmware image is active (ie, the device has booted this firmware image), the value of the {{param|#.SoftwareVersion}} parameter MUST be the same as the value contained in this parameter. To allow version comparisons, this element SHOULD be in the form of dot-delimited integers, where each successive integer represents a more minor category of variation. For example, 3.0.21 where the components mean: ''Major.Minor.Build''. The value of {{param}} is {{empty}} if {{param|Status}} is anything other than {{enum|Available|Status}}, {{enum|InstallationFailed|Status}}, or {{enum|ActivationFailed|Status}}. Specifies whether or not this particular firmware image can be used by the Agent. An Agent will only attempt to boot this particular firmware image if this parameter value is set to {{true}}. This value MUST be set to {{true}} by the device whenever a new firmware image is installed. This value cannot be set to {{false}} if the firmware image is active or is referenced by the {{param|#.BootFirmwareImage}} parameter. Firmware image instances cannot be deleted, so a Controller MAY use this parameter to subsequently mark a particular firmware as being invalid, which will prevent the Agent from attempting to boot it. Status of the firmware image, as determined by the Agent. {{enum}} This Firmware Image instance is empty. This value could happen on an Agent that supports multiple firmware images, but only has a single image installed. This Firmware Image instance is the currently active image. This Firmware Image instance is being downloaded. This Firmware Image instance has been downloaded, and is in the process of being validated. This Firmware Image instance has been downloaded, validated, and installed, and is ready to be activated. The Agent has attempted to download this Firmware Image instance, but ultimately failed while retrieving it from the source URL. The Agent has attempted to validate a Firmware Image downloaded to this instance, but ultimately failed while validating it. The Agent has attempted to install a Firmware Image downloaded and validated to this instance, but ultimately failed while installing it. The Agent has attempted to active this Firmware Image instance, but ultimately failed while being activated. If the Agent is unable to boot into this firmware image, when specified, the Agent can use this parameter to record some information as to why the boot failed. If the Agent successfully boots into this firmware, the value of this parameter SHOULD be {{empty}}. When a new firmware image is installed into this object instance, this parameter MUST be cleared. The length of this string is defined as implementation-specific by the Agent.