CPE Fault Codes from 9000 to 9799 * 9000 - Method not supported * 9001 - Request denied (no reason specified) * 9002 - Internal error * 9003 - Invalid arguments * 9004 - Resources exceeded * 9005 - Invalid parameter name * 9006 - Invalid parameter type * 9007 - Invalid parameter value * 9008 - Attempt to set a non-writable parameter * 9009 - Notification request rejected * 9010 - File transfer failure * 9011 - Upload failure * 9012 - File transfer server authentication failure * 9013 - Unsupported protocol for file transfer * 9014 - File transfer failure: unable to join multicast group * 9015 - File transfer failure: unable to contact file server * 9016 - File transfer failure: unable to access file * 9017 - File transfer failure: unable to complete download * 9018 - File transfer failure: file corrupted * 9019 - File transfer failure: file authentication failure * 9020 - File transfer failure: unable to complete download within specified time windows * 9021 - Cancelation of file transfer not permitted in current transfer state * 9022 - Invalid UUID Format * 9023 - Unknown Execution Environment * 9024 - Disabled Execution Environment * 9025 - Deployment Unit to Execution Environment Mismatch * 9026 - Duplicate Deployment Unit * 9027 - System Resources Exceeded * 9028 - Unknown Deployment Unit * 9029 - Invalid Deployment Unit State * 9030 - Invalid Deployement Unit Update – Downgrade not permitted * 9031 - Invalid Deployement Unit Update – Version not specified * 9032 - Invalid Deployment Unit Update – Version already exists Range of CPE Fault Codes from 9033 to 9799 for future extension Vendor Extension range for CPE Fault Codes from 9800 to 9899 ACS Fault Codes from 8000 to 8005 * 8000 - Method not supported * 8001 - Request denied (no reason specified) * 8002 - Internal error * 8003 - Invalid arguments * 8004 - Resources exceeded * 8005 - Retry request Vendor Extension range for ACS Fault Codes from 8800 to 8899 This type is used for AllQueuedTransferStruct and AutonomousTransferComplete This pattern allows the following File Types: * 1 Firmware Upgrade Image * 2 Web Content * 3 Vendor Configuration File * 4 Vendor Log File * 4 Tone File * 5 Ringer File This pattern allows the following File Types: * 6 Vendor Configuration File [1-9]\d* * 7 Vendor Log File [1-9]\d* This type is used for Download and RequestDownload This pattern allows the following File Types: * 1 Firmware Upgrade Image * 2 Web Content * 3 Vendor Configuration File * 4 Tone File * 5 Ringer File This type is used for Upload This pattern allows the following File Types: * 1 Vendor Configuration File * 2 Vendor Log File This pattern allows the following File Types: * 3 Vendor Configuration File [1-9]\d* * 4 Vendor Log File [1-9]\d* This pattern allows the following Event Codes: * 0 BOOTSTRAP * 1 BOOT * 2 PERIODIC * 3 SCHEDULED * 4 VALUE CHANGE * 5 KICKED * 6 CONNECTION REQUEST * 7 TRANSFER COMPLETE * 8 DIAGNOSTICS COMPLETE * 9 REQUEST DOWNLOAD * 10 AUTONOMOUS TRANSFER COMPLETE * 11 DU STATE CHANGE COMPLETE * 12 AUTONOMOUS DU STATE CHANGE COMPLETE This pattern allows the following Event Codes: * M Reboot * M ScheduleInform * M Download * M ScheduleDownload * M Upload * M ChangeDUState This pattern allows the following Time Window Modes: * 1 At Any Time * 2 Immediately * 3 When Idle * 4 Confirmation Needed Restricted subset of CPEFaultCodeType that are specific for the TransferComplete and AutonomousTransferComplete RPCs Fault information for TransferComplete and AutonomousTransferComplete Fault codes only related to TransferComplete RPCs No fault Restricted subset of CPEFaultCodeType that are specific for a single operation in the DUStateChangeComplete and AutonomousDUStateChangeComplete RPCs Structure used to convey success or failure status of an operation performed on a Deployment Unit Fault codes only related to DUStateChangeComplete RPCs No fault An optional detail message providing further context for the fault Notification off. The CPE need not inform the ACS of a change to the specified parameter(s) Passive notification. Whenever the specified parameter value changes, the CPE MUST include the new value in the ParameterList in the Inform message that is sent the next time a session is established to the ACS Active notification. Whenever the specified parameter value changes, the CPE MUST initiate a session to the ACS, and include the new value in the ParameterList in the associated Inform message Reserved for future use Reserved for future use Reserved for future use Reserved for future use Not yet started In progress Completed A unique identifier for a Deployment Unit The state of a Deployment Unit on the device The Deployment Unit has been Installed. The Deployment Unit has been Uninstalled. The Deployment Unit Installed failed such that the Deployment Unit instance could not be created. Install of a Deployment Unit Update of a Deployment Unit Uninstall of a Deployment Unit Vendor specific operation types A base type for Deployment Unit operations that can be performed on a device An operation indicating a Deployment Unit should be installed The URL of the Deployment Unit to download The UUID to be used for the Deployment Unit being installed. An optional username with which to authenticate against the url An optional password with which to authenticate against the url A reference to the Execution Environment upon which the Deployment Unit is to be associated (e.g., ".SoftwareModules.ExecEnv.1.") An operation indicating an individual or all Deployment Units should be updated The UUID of the Deployment Unit to update. If the UUID is not present and the URL is present then the URL will be used to determine the Deployment Unit to update. If both the UUID and the URL are not specified, the operation indicates all installed Deployment Units should be updated. An optional Version used to clarify which Deployment Unit to update. Only required in the case where multiple versions of the same Deployment Unit are installed on the device, in which case if not specified the update request will be rejected. The URL to be used when updating a Deployment Unit. If a UUID is provided and the URL is present then it serves as an updated URL for the existing installed Deployment Unit. If the UUID is not present and the URL is, it is used to determine the Deployment Unit to update. If neither the URL or UUID is specified then all Deployment Units are to be updated. An optional username with which to authenticate against the url An optional password with which to authenticate against the url An operation indicating a Deployment Unit should be un-installed The UUID of the Deployment Unit to un-install An optional Version used to clarify which Deployment Unit to uninstall. If not specified and there are multiple versions of the same Deployment Unit installed on the device, then all of them will be uninstalled. A reference to the Execution Environment upon which the Deployment Unit is to be removed from (e.g., ".SoftwareModules.ExecEnv.1.") The result of a Deployment Unit operation performed on the device The UUID of the affected Deployment Unit A reference to the affected Deployment Unit The Version of the affected Deployment Unit The current state of the affected Deployment Unit after performing the operation Whether or not the Deployment Unit resolved all of its dependencies after the Installation or Update A comma-separated list of execution unit references (e.g., ".SoftwareModules.ExecutionUnit.2, .SoftwareModules.ExecutionUnit.3"). In the case of an install, the execution units are those created by the operation. In the case of an uninstall, the execution units are those removed by the operation. In the case of an update, the execution units are those that remain after the operation has completed. The time on the device the operation on the affected Deployment Unit started. If the CPE cannot determine this, then the value should be the Unknown Time value. The time on the device the operation on the affected Deployment Unit completed (successfully or otherwise). If the CPE cannot determine this, then the value should be the Unknown Time value. Fault structure conveying the success or, in the case of failure, reason for the failure, of the operation The result of a Deployment Unit operation performed autonomously on the device (i.e., not at the direct request of the ACS) The operation that was performed against the deployment unit Option is disabled and not setup Option is enabled and not setup Option is disabled and setup Option is enabled and setup 0 - Disabled 1 - Enabled with expiration 2 - Enabled without expiration Non-transferable Transferable GeRPCMethods message - Annex A.3.1.1 GeRPCMethodsResponse message - Annex A.3.1.1 SetParameterValues message - Annex A.3.2.1 SetParameterValuesResponse message - Annex A.3.2.1 All Parameter changes have been validated and applied All Parameter changes have been validated and committed, but some or all are not yet applied (for example, if a reboot is required before the new values are applied) GetParameterValues message - Annex A.3.2.2 GetParameterValuesResponse message - Annex A.3.2.2 GetParameterNames message - Annex A.3.2.3 GetParameterNamesResponse message - Annex A.3.2.3 SetParameterAttributes message - Annex A.3.2.4 SetParameterAttributesResponse message - Annex A.3.2.4 GetParameterAttributes message - Annex A.3.2.5 GetParameterAttributesResponse message - Annex A.3.2.5 AddObject message - Annex A.3.2.6 AddObjectResponse message - Annex A.3.2.6 The object has been created The object creation has been validated and committed, but not yet applied DeleteObject message - Annex A.3.2.7 DeleteObjectResponse message - Annex A.3.2.7 The object has been deleted The object deletion has been validated and committed, but not yet applied Download message - Annex A.3.2.8 DownloadResponse message - Annex A.3.2.8 Download has completed and been applied Download has not yet been completed and applied Reboot message - Annex A.3.2.9 RebootResponse message - Annex A.3.2.9 GetQueuedTransfers message - Annex A.4.1.1 GetQueuedTransfersResponse message - Annex A.4.1.1 ScheduleInform message - Annex A.4.1.2 ScheduleInformResponse message - Annex A.4.1.2 SetVouchers message - Annex A.4.1.3 SetVouchersResponse message - Annex A.4.1.3 GetOptions message - Annex A.4.1.4 GetOptionsResponse message - Annex A.4.1.4 Upload message - Annex A.4.1.5 UploadResponse message - Annex A.4.1.5 Upload has been completed Upload has not yet completed FactoryReset message - Annex A.4.1.6 FactoryResetResponse message - Annex A.4.1.6 GetAllQueuedTransfers message - Annex A.4.1.7 GetAllQueuedTransfersResponse message - Annex A.4.1.7 ScheduleDownload message - Annex A.4.1.8 ScheduleDownloadResponse message - Annex A.4.1.8 CancelTransfer message - Annex A.4.1.9 CancelTransferResponse message - Annex A.4.1.9 A request to perform an action on a Deployment Unit on the device The operations to be performed. The content of an operation is contained within the operation sub-type. An optional command key used to correlate future results of the operation or changes made to the device as a result of the operation. Response to a ChangeDUState message Inform message - Annex A.3.3.1 InformResponse message - Annex A.3.3.1 TransferComplete message - Annex A.3.3.2 TransferCompleteResponse message - Annex A.3.3.2 AutonomousTransferComplete message - Annex A.3.3.3 AutonomousTransferCompleteResponse message - Annex A.3.3.3 Kicked message - Annex A.4.2.1 KickedResponse message - Annex A.4.2.1 RequestDownload message - Annex A.4.2.2 RequestDownloadResponse message - Annex A.4.2.2 A message indicating a prior ChangeDUState request to perform an action on a Deployment Unit on the device has completed The results of the operation performed. The ordering of the operation results matches the order of the operations in the corresponding ChangeDUState message. The command key specified in the corresponding ChangeDUState message, if any Response to a DUStateChangeComplete message A message indicating an autonomous action for a Deployment Unit on the device has completed The results of the operation performed Response to a AutonomousDUStateChangeComplete message