{{docname|Component Objects for CWMP}} {{appdate|November 2015}} {{trname|TR-157a10}} Update Bulk Data Collection for HTTP Transport 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 {{bibref|TR-157a10|Annex A}}. 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. Represents the IPDR and transport protocols that this device is capable of supporting. Hypertext Transfer Protocol {{bibref|RFC2616}} Represents the Encoding Types for the protocols that this device is capable of supporting. Used with the IPDR Streaming and File Protocols. {{bibref|IPDR-XML}} Used with the IPDR Streaming and File Protocols. {{bibref|IPDR-XDR}} 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 Bulk Data Protocol being used for this collection profile. The Bulk Data encoding type being used for this collection profile. 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. 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 {{bibref|TR-157a10|Annex A.3.2.1}}. 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 a partial parameter 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 {{bibref|TR-157a10|Annex A.3.4}}. 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. If the CPE is unable to acquire a time, then the processing described by the dateTime type in {{bibref|TR-069|Table 12}} is followed. 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 {{bibref|TR-157a10|Annex A.3.5}}. 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 {{bibref|TR-157a10}}. 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. If the CPE is unable to acquire a time, then the processing described by the dateTime type in {{bibref|TR-069|Table 12}} is followed. 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 URL, as defined in {{bibref|RFC3986}}, 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 {{bibref|TR-157a10|Annex A.2.2.1}}. 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 {{bibref|TR-157a10|Annex A.2.2.1}}. 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}} 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 {{bibref|TR-157a10|Annex A.2.1}}. 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 the Request-URI parameter. If the value of this parameter is empty, then this object is not encoded in the report header.