Skip to content

8.3 Resource [myCertFileCred] primitive mappings

8.3.1 Introduction

This clause contains information regarding the procedures for establishing a certificates presented by the managed entity in order for the peer to authenticate the managed entity.

8.3.2 Creation of Resource [myCertFileCred]

8.3.2.1 Introduction

The creation of a [myCertFileCred] resource requires the use of the TR-069 Download RPC to establish the credential on the managed entity. Once the managed entity has obtained the credential, the Device.Security.Certificate.{i} instance's SUIDs parameter is set from the [myCertFileCred] attribute using the TR-069 Set RPC.

8.3.2.2 Procedure for creation of Resource [myCertFileCred]

The Create Request and Response primitives for Resource [myCertFileCred] that results in a download file transfer shall use the Download mechanism defined in TR-069 [4]. The Download mechanism is an asynchronous command that consists of the synchronous Download RPC for the Download and the asynchronous TransferComplete RPC. The Download RPC returns a successful response or one of the following fault codes in Table 8.3.2.2-1. A successful response means that the CPE has accepted the Download RPC.

Table 8.3.2.2-1: Download Fault Code Mapping

Fault code Description Response Status Code
9000 Method not supported 4000 (BAD_REQUEST)
9001 Request denied (no reason specified) 4000 (BAD_REQUEST)
9002 Internal error 4000 (BAD_REQUEST)
9003 Invalid arguments 4000 (BAD_REQUEST)
9004 Resources exceeded (when used in association with SetParameterValues, this cannot be used to indicate Parameters in error) 4000 (BAD_REQUEST)
9010 File transfer failure (associated with Download, ScheduleDownload, TransferComplete or AutonomousTransferComplete methods). 4000 (BAD_REQUEST)
9012 File transfer server authentication failure (associated with Upload, Download, TransferComplete, AutonomousTransferComplete, DUStateChangeComplete, or AutonomousDUStateChangeComplete methods). 4000 (BAD_REQUEST)
9013 Unsupported protocol for file transfer (associated with Upload, Download, ScheduleDownload, DUStateChangeComplete, or AutonomousDUStateChangeComplete methods). 4000 (BAD_REQUEST)

Once the CPE has attempted to download the file, the CPE reports the result of the download operation using the TransferComplete RPC. The TransferComplete RPC indicates a successful operation or one of the following fault codes in Table 8.3.2.2-2.

Table 8.3.2.2-2: TransferComplete Fault Code Mapping

Fault code Description Response Status Code
9001 Request denied (no reason specified) 4000 (BAD_REQUEST)
9002 Internal error 4000 (BAD_REQUEST)
9010 File transfer failure (associated with Download, ScheduleDownload, TransferComplete or AutonomousTransferComplete methods). 4000 (BAD_REQUEST)
9011 Upload failure (associated with Upload, TransferComplete or AutonomousTransferComplete methods). 4000 (BAD_REQUEST)
9012 File transfer server authentication failure (associated with Upload, Download, TransferComplete, AutonomousTransferComplete, DUStateChangeComplete, or AutonomousDUStateChangeComplete methods). 4000 (BAD_REQUEST)
9014 File transfer failure: unable to join multicast group (associated with Download, TransferComplete or AutonomousTransferComplete methods). 4000 (BAD_REQUEST)
9015 File transfer failure: unable to contact file server (associated with Download, TransferComplete, AutonomousTransferComplete, DUStateChangeComplete, or AutonomousDUStateChangeComplete methods). 4000 (BAD_REQUEST)
9016 File transfer failure: unable to access file (associated with Download, TransferComplete, AutonomousTransferComplete, DUStateChangeComplete, or AutonomousDUStateChangeComplete methods). 4000 (BAD_REQUEST)
9017 File transfer failure: unable to complete download (associated with Download, TransferComplete, AutonomousTransferComplete, DUStateChangeComplete, or AutonomousDUStateChangeComplete methods). 4000 (BAD_REQUEST)
9018 File transfer failure: file corrupted or otherwise unusable (associated with Download, TransferComplete, AutonomousTransferComplete, DUStateChangeComplete, or AutonomousDUStateChangeComplete methods). 4000 (BAD_REQUEST)
9019 File transfer failure: file authentication failure (associated with Download, TransferComplete or AutonomousTransferComplete methods). 4000 (BAD_REQUEST)
9020 File transfer failure: unable to complete download within specified time windows (associated with TransferComplete method). 4000 (BAD_REQUEST)

Upon successful TransferComplete notification from the CPE, the newly created Device.Security.Certificate.{i} object instance shall be assigned the values of the SUIDs attribute using the procedure for updating parameters in clause 8.1.4.