This object provides bulk data collection capabilities and global collection settings that affect the entire device. Bulk Data utilizes various solutions (e.g., IPDR, HTTP) to collect data from devices and transfer the data to a collection server. The IPDR solution is based on a service specification described in {{bibref|TR-232}}. The HTTP solution is based on transfer mechanisms described in {{template|BULK-DATA-HTTP-REF}}. {{template|BULK-DATA-OPT-SOLNS}} The Bulk Data Collection Profiles are measured over a reporting interval (which can be aligned with absolute time) and are made available to the collection server. Enables or disables all collection profiles. If {{false}}, bulk data will not be collected or reported. Indicates the status of the Bulk Data Collection mechanism. Bulk Data Collection is enabled and working as intended. Bulk Data Collection is disabled. Bulk Data Collection is enabled, but there is an error condition preventing the successful collection of bulk data. Minimum reporting interval in {{units}} that the CPE is capable of supporting. A value of 0 indicates no minimum reporting interval. Represents the IPDR and transport protocols that this device is capable of supporting. Hypertext Transfer Protocol {{bibref|RFC2616}} Message Queuing Telemetry Transport {{bibref|MQTT31}}, {{bibref|MQTT311}}, and {{bibref|MQTT50}} Represents the Encoding Types for the protocols that this device is capable of supporting. Comma Separated Values. Used with the HTTP Protocol. {{bibref|RFC4180}} JavaScript Object Notation. Used with the HTTP Protocol. {{bibref|RFC7159}} When {{true}}, the Device supports the use of wildcards to determine the parameters that are reported using a Profile. The maximum number of profiles that can exist at any given time. Specifically, the maximum number of {{object|Profile.{i}.}} instances that the Controller can create. If the value of this parameter is -1, then it means that the CPE doesn't have a limit to the number of profiles that can exist. The maximum number of parameters that can be referenced via the bulk data collection mechanism. Specifically, the maximum number of parameters that can be referenced via {{param|Profile.{i}.Parameter.{i}.Reference}} across all Profile and Parameter instances (including the expansion of partial paths within the Reference parameter). If the value of this parameter is -1, then it means that the CPE doesn't have a limit to the number of parameter that can be referenced via the bulk data collection mechanism. {{numentries}} A set of Bulk Data Collection profiles. Each profile represents a bulk data report, including its own timing configuration, communications configuration, and set of parameters. This allows the Controller to configure multiple reports to be generated at different times for different sets of data. Enables or disables this specific bulk data profile. If {{false}}, this profile will not be collected or reported. {{datatype|expand}} The name of the profile. The number of failed reports to be retained and transmitted (in addition to the current report) at the end of the current reporting interval. If the value of the {{param|EncodingType}} parameter is modified any outstanding failed reports are deleted. If the CPE cannot retain the number of failed reports from previous reporting intervals while transmitting the report of the current reporting interval, then the oldest failed reports are deleted until the CPE is able to transmit the report from the current reporting interval. A value of 0 indicates that failed reports are not to be retained for transmission in the next reporting interval. A value of -1 indicates that the CPE will retain as many failed reports as possible. The Bulk Data Protocol being used for this collection profile. The Bulk Data encoding type being used for this collection profile. The reporting interval in {{units}}. Each report is generated based on this interval and {{param|TimeReference}}. The CPE MAY reject a request to set {{param}} to less than {{param|#.MinReportingInterval}}. Reporting intervals MUST begin every {{param}} {{units}}. If {{param}} is changed while collection is enabled, the first reporting interval begins immediately. For example, if {{param}} is 86400 (a day) and if {{param|TimeReference}} is set to UTC midnight on some day (in the past, present, or future) then the CPE will generate (and transmit) its report at midnight every 24 hours. An absolute time reference in UTC to determine when will be transmitted. Each reporting interval MUST complete at this reference time plus or minus an integer multiple of {{param|ReportingInterval}}, unless unable to due to higher prioritized operations. {{param}} is used only to set the "phase" of the reporting intervals. The actual value of {{param}} can be arbitrarily far into the past or future. If {{param}} is changed while collection of bulk data is enabled, the first reporting interval begins immediately. The Unknown Time value as defined in {{bibref|TR-106}} indicates that no particular time reference is specified. That is, the CPE MAY locally choose the time reference, and is required only to adhere to the specified reporting intervals. If absolute time is not available to the CPE, its reporting interval behavior MUST be the same as if the {{param}} parameter was set to the Unknown Time value. For example, if {{param|ReportingInterval}} is 86400 (a day) and if {{param}} is set to UTC midnight on some day (in the past, present, or future) then the CPE will generate (and transmit, if in a "ITPush" mode) its report at midnight every 24 hours. Note that, if {{param}} is set to a time other than the Unknown Time, the first reporting interval (which has to begin immediately) will almost certainly be shorter than {{param|ReportingInterval}}). This is why {{param}} is defined in terms of when reporting intervals complete rather than start. {{numentries}} Bulk data parameter table. Each entry in this table represents a parameter (or set of parameters if a partial path is provided) to be collected and reported. Name of the parameter in the report body. If the value of this parameter is {{empty}}, then the value of the {{param|Reference}} parameter is used as the name. When the value {{param|Reference}} parameter contains wildcards and/or partial parameter names, the rules for determining the value of this parameter are specified in {{template|BULK-DATA-WILD-REF}}. Represents the parameter(s) that are part of this Bulk Data collection profile. The value MUST be a path name of a parameter or an object. When the {{param|##.ParameterWildCardSupported}} parameter has a value of {{true}}, patterns for instance identifiers are permitted with wildcards (an "*" character) in place of instance identifiers; any attempt to set the value otherwise MUST be rejected by the CPE. In the case where an Object Path is specified, the sub-objects of the resolved pattern and contained parameters will be part of the bulk data collected and reported. If the path name refers to an object then it MUST end with a '.'. This object defines the properties to be used when the {{object|##.Profile}} object's {{param|#.EncodingType}} parameter value is {{enum|CSV|##.EncodingTypes}}. Field separator to use when encoding CSV data. Row separator to use when encoding CSV data. Escape character to use when encoding CSV data. This parameter describes the formatting used for reports defined by this profile as described in {{template|BULK-DATA-CSV-REF}}. Note: This parameter is encoded as a token in the BBF-Report-Format header field and MUST NOT include spaces or other characters excluded from token characters defined in {{bibref|RFC2616}}. Reports are formatted with each parameter formatted as a row entry. Reports are formatted with each parameter formatted as a column entry. The format of the timestamp to use for data inserted into the row. Timestamp is inserted using the UNIX epoch time (milliseconds since Jan 1, 1970 UTC) timestamp format. If the CPE is unable to acquire a time, then the time that has elapsed since the last reboot of the device is used. Timestamp is inserted using the ISO-8601 timestamp format{{template|BULK-DATA-TIMESTAMP}}. Timestamp is not inserted in the row. This object defines the properties to be used when the {{object|##.Profile}} object's {{param|#.EncodingType}} parameter value is {{enum|JSON|##.EncodingTypes}}. This parameter describes the formatting used for the report as described in {{template|BULK-DATA-JSON-REF}}. Note: This parameter is encoded as a token in the BBF-Report-Format header field and MUST NOT include spaces or other characters excluded from token characters defined in {{bibref|RFC2616}}. Reports are formatted with each object in the object hierarchy of the data model encoded as a corresponding hierarchy of JSON Objects with the parameters of the object specified as name/value pairs of the JSON Object. Reports are formatted with each parameter of the data model encoded as a corresponding array of JSON Objects with the parameters specified as name/value pairs. The format of timestamp to use for the JSON Object named "CollectionTime" as described in {{template|BULK-DATA-JSON-REF}}. Timestamp is inserted using the UNIX epoch time (milliseconds since Jan 1, 1970 UTC) timestamp format. If the CPE is unable to acquire a time, then the time that has elapsed since the last reboot of the device is used. Timestamp is inserted using the ISO-8601 timestamp format{{template|BULK-DATA-TIMESTAMP}}. Timestamp is not inserted. This object defines the properties to be used when transporting bulk data using the HTTP/HTTPS protocol. This object is used when the {{param|#.Protocol}} parameter has a value of {{enum|HTTP|##.Protocols}}. For authentication purposes the CPE MUST support HTTP Basic and Digest Access Authentication as defined in {{bibref|RFC2616}}. The {{datatype}} for the collection server to receive the Bulk Data transmitted by the CPE. Username used to authenticate the CPE when making a connection to the collection server. Password used to authenticate the CPE when making a connection to the collection server. Indicates the HTTP Compression mechanism(s) supported by this CPE for the purposes of transferring bulk data. As defined in {{bibref|RFC2616|Section 3.5}} As defined in {{bibref|RFC2616|Section 3.5}} As defined in {{bibref|RFC2616|Section 3.5}} The value of this parameter represents the HTTP Compression mechanism to be used by the CPE when transferring data to the collection server. Indicates the HTTP method(s) supported by this CPE for the purposes of transferring bulk data. As defined in {{bibref|RFC2616|Section 9.5}} As defined in {{bibref|RFC2616|Section 9.6}} The value of this parameter represents the HTTP method to be used by the CPE when transferring data to the collection server. When {{true}}, the CPE encodes the HTTP Date Header {{bibref|RFC2616|Section 14.18}} in the HTTP client request. When {{true}}, the CPE retries unsuccessful attempts to transfer data. Configures the data transfer retry wait interval, in seconds, as specified in {{template|BULK-DATA-HTTP-RETRY-REF}}. The device MUST use a random value between {{param}} and ({{param}} * {{param|RetryIntervalMultiplier}} / 1000) as the first retry wait interval. Other values in the retry pattern MUST be calculated using this value as a starting point. Configures the retry interval multiplier as specified in {{template|BULK-DATA-HTTP-RETRY-REF}}. This value is expressed in units of 0.001. Hence the values of the multiplier range between 1.000 and 65.535. The device MUST use a random value between {{param|RetryMinimumWaitInterval}} and ({{param|RetryMinimumWaitInterval}} * {{param}} / 1000) as the first retry wait interval. Other values in the retry pattern MUST be calculated using this value as a starting point. {{numentries}} Determines whether or not data transfers that have failed are required to be persisted across reboots. If {{param}} is {{true}}, then failed data transfers MUST be persisted across reboots. If {{param}} is {{false}}, then failed data transfers are not required to be persisted across reboots. This object represents an instance of a parameter to be used in the report header used as part of the HTTP Request-URI transmitted by the CPE to the collection server using the Request-URI in addition to the parameters required by {{template|BULK-DATA-HTTP-QUERY-REF}}. Name of the Request-URI parameter. If {{param}} is {{empty}}, the name of the Request-URI parameter is the value of {{param|Reference}}. The value MUST be the path name of a parameter to be used as the Request-URI parameter. If the value of this parameter is empty, then this object is not encoded in the report header. This object defines the properties to be used when transporting bulk data using the MQTT protocol. This object is used when the {{param|#.Protocol}} parameter has a value of {{enum|MQTT|##.Protocols}}. A reference to the MQTT Client used by this Bulk Data Collection Profile when communicating via the MQTT Protocol. The topic name the Agent MUST use when sending the Bulk Data report. The Agent MUST use this QoS value when sending the Bulk Data report. If the referenced MQTT Client uses MQTT 5.0 and the MQTT server only indicates support for a QoS value in the CONNACK Maximum QoS property lower than this QoS value, the Agent MUST use the highest QoS value that is supported by the server. If set to {{true}} the Agent MUST set the RETAIN flag in MQTT PUBLISH messages carrying the Bulk Data report to 1, unless the MQTT server sent Retain Available = 0 (MQTT 5.0) in its CONNACK (in which case, the Agent MUST set the RETAIN flag to 0).