This object serves as the central control for managing file uploads to a remote server. It allows for periodic transfers of various file types, such as logs, crash dumps, and kernel oopses. Individual upload configurations are defined within instances of the {{object|Profile}} object. Globally enables or disables the entire file transfer service managed by this object. When disabled, no file transfers will occur, regardless of individual profile or transfer configurations. Indicates the protocols that are supported. As defined in {{bibref|RFC9110}}. Indicates the file types that are supported for upload. The file to be uploaded is a vendor-specific log file and is part of {{object|.DeviceInfo.VendorLogFile.}}. The file to be uploaded is a process fault file and is part of {{object|.DeviceInfo.ProcessFaults.}}. The file to be uploaded is a kernel fault file and is part of {{object|.DeviceInfo.KernelFaults.}}. The file to be uploaded is a log file that is rotated and is part of {{object|.DeviceInfo.LogRotate.}}. Indicates the HTTP Compression mechanism(s) supported by this Device for the purposes of transferring the 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}} Indicates the HTTP method(s) supported by this Device for the purposes of transferring data. As defined in {{bibref|RFC2616|Section 9.5}} As defined in {{bibref|RFC2616|Section 9.6}} {{numentries}} {{numentries}} This object defines a reusable profile for configuring file uploads. Each profile specifies the common parameters for transferring files to a remote server, such as the protocol to be used. Multiple transfer tasks ({{object|#.Transfer}}) can reference the same profile. The textual name of the profile as assigned by the Device. Protocol being used. This object defines the HTTP/HTTPS transport properties for a transfer file upload profile. This object is used when the {{param|#.Protocol}} parameter has a value of {{enum|HTTP|##.ProtocolsSupported}}. For authentication purposes the Device MUST support HTTP Basic and Digest Access Authentication as defined in {{bibref|RFC7617}} and {{bibref|RFC7616}}. The URL of the server receiving the periodic file uploads. Username used to authenticate the Device when making a connection to the file upload server. {{empty}} indicates that the username will not be used during the authentication process. Password used to authenticate the Device when making a connection to the file upload server. {{empty}} indicates that the password will not be used during the authentication process. The value of this parameter represents the HTTP Compression mechanism to be used by the Device when transferring data to the file upload server. The value of this parameter represents the HTTP method to be used by the Device when transferring data to the file upload server. When {{true}}, the Device retries unsuccessful attempts to transfer the remaining files. Configures the data transfer retry wait interval, in {{units}}. 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 data transfer retry maximum wait interval, in {{units}}. If the calculated interval is higher than the specified {{param}} value then {{param}} value should be used. Configures the retry interval multiplier. 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}} {{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 {{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 allows defining custom HTTP request header fields to be included in the outbound HTTP requests to the remote server when using this profile. As defined in {{bibref|RFC2616|Section 5.3 Request Header Fields}}. Each instance can specify either a static value or dynamically reference a device parameter. The name of the custom HTTP header field to be added to the request. Either {{param|Value}} or {{param|Reference}} MUST be specified. If both are specified, the value of {{param|Value}} will be used. If both are {{empty}}, this object is not included in the HTTP request. The static value of the HTTP header field. If this parameter is {{empty}}, the value of the header field will be the current value of the device parameter specified in {{param|Reference}}. The path name of a device parameter whose current value will be used as the value of this HTTP header field. This object specifies the parameters for an individual file transfer task. Each instance specifies a file to be transferred, the method of transfer (periodic or on-demand), and a reference to a {{object|#.Profile.{i}.}} object containing the server connection details. The {{param|Status}} parameter reflects the current state of the transfer process, which can transition through the following sequences: * Idle → Uploading → Success → Idle * Idle → Uploading → Error → Idle * Idle → Creating → Error → Idle * Idle → Creating → Uploading → Success → Idle * Idle → Creating → Uploading → Error → Idle Enables or disables this specific file transfer task. If this entry is disabled then the transfer is not performed. Indicates the current status of this file transfer task. The transfer task is currently inactive and waiting for a trigger or scheduled time. The Device is currently preparing the file for transfer (e.g., running a pre-hook script). The Device is currently in the process of uploading the file to the remote server. The file transfer was completed successfully. The file transfer encountered an error. Indicates the Origin of the {{object}} instance. Used for indicating that the transfer task was created by the end-user. For example through the web user interface. Used for indicating that the transfer task was created by the system itself. Used for indicating that the transfer task was created by a Controller. Specifies the type of file to be uploaded. The actual file path and any pre- or post-processing scripts associated with this file type are implementation-specific on the Device. The path reference to the object that contains the file(s) to be uploaded. Only applicable when {{param|Type}} matches values of {{enum|VendorLogFile|Type}} or {{enum|LogRotate|Type}}. For other {{param|Type}} values, this parameter is not applicable, because all files of the selected type will be uploaded, e.g. when {{param|Type}} equals {{enum|ProcessFaults|Type}} all process faults will be uploaded. When {{param}} is {{empty}}, depending on the {{param|Type}} all references will be uploaded. Reference to profile instance to be used to perform the transfer. The file upload interval in {{units}}. Each file upload is tried based on this interval and {{param|TimeReference}}. File upload intervals MUST begin every {{param}} {{units}}. If {{param}} is changed while Periodic File Upload is enabled, the first file upload 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 Device will upload its file(s) at midnight every 24 hours. An absolute time reference in UTC to determine when the file will be transmitted. Each file upload interval MUST complete at this reference time plus or minus an integer multiple of {{param|UploadInterval}}, unless unable to due to higher prioritized operations. {{param}} is used only to set the "phase" of the file upload intervals. The actual value of {{param}} can be arbitrarily far into the past or future. If {{param}} is changed while periodic file upload is enabled, the first file upload interval begins immediately. The Unknown Time value as defined in {{bibref|TR-106}} indicates that no particular time reference is specified. That is, the Device MAY locally choose the time reference, and is required only to adhere to the specified file upload intervals. If absolute time is not available to the Device, its file upload interval behavior MUST be the same as if the {{param}} parameter was set to the Unknown Time value. For example, if {{param|UploadInterval}} is 86400 (a day) and if {{param}} is set to UTC midnight on some day (in the past, present, or future) then the Device will upload its file(s) at midnight every 24 hours. Note that, if {{param}} is set to a time other than the Unknown Time, the first file upload interval (which has to begin immediately) will almost certainly be shorter than {{param|UploadInterval}}). This is why {{param}} is defined in terms of when file upload intervals complete rather than start. The UTC date and time of the next scheduled file upload for this periodic transfer task. This object provides statistical information about the success and failure of individual file transfer tasks. The date and time at which of the last successful transfer. The date and time at which of the last failed transfer. Error code of the last failed transfer as described in https://tr369.org/tr-369-usp-error-code-details/. Counter of successful transfer. Counter of failed transfer. This object provides aggregated statistical information about all file upload activities managed by the {{object|Device.PeriodicFileTransfer.}} object. A counter representing the total number of successful file uploads across all transfer tasks since the last system reset or counter reset. A counter representing the total number of failed file uploads across all transfer tasks since the last system reset or counter reset. User Services Platform (USP - {{bibref|TR-369|Annex A}}) Event Notification {{reference|the {{object|.LocalAgent.Controller}} instance that created {{object}}|delete}} The value of this parameter is automatically populated by the USP Agent upon {{object}} creation using the reference to the USP Controller that created the instance. Only the USP Controller referenced by {{param}} parameter will receive a {{event|#.Transfer.{i}.Push!}} Event (assuming it has an associated Subscription) when the Profile has {{param|Protocol}} configured to {{enum|USPEventNotif|Protocol}}, even if another USP Controller has an associated Subscription. This command forces the Device to immediately attempt to transfer the file associated with this transfer task, regardless of the scheduled time; The {{param|Status}} is updated to {{enum|Uploading|Status}}, the {{param|NextTransferDate}} remains unchanged. All results of the actual upload will be contained within the {{event|.LocalAgent.TransferComplete!}} event. Note: The device MUST NOT perform any retries of the forced transfer. If the transfer fails, the USP Controller is responsible for retrying the operation by invoking {{command}} again. Push event for delivering a periodic file transfer report within a USP Notification message. The contents of the periodic file transfer report.