2.2.2.5.2 SECURECLOCK_RESPONSE_DATA

The SECURECLOCK_RESPONSE_DATA complex type is the payload for a response to the SECURECLOCK_CHALLENGE message. It contains information used to ensure that the device's clock conforms to policy. Policy is specified within the license.

 <xs:complexType name="SECURECLOCK_RESPONSE_DATA">
   <xs:sequence>
     <xs:element name="TID" type="xs:string" />
     <xs:element name="GMTTIME" type="xs:string" />
     <xs:element name="REFRESHDATE" type="xs:string" />
   </xs:sequence>
 </xs:complexType>
  

TID: Identifies a unique transaction between the device and the secure clock server. The same value MUST be used from the device's secure clock challenge message. This value MUST NOT be re-used in future messages or transactions.

GMTIME: A string representation of Greenwich mean time (GMT) time, indicating the current GMT at the time the message was sent. This string is derived using the time conversion method specified in [ISO-8601]. This value is used to set the device's internal clock. MUST be set to the secure clock server's time when sent.

REFRESHDATE: Contains a string representation of the refresh date, in GMT time. This element MUST be set to the secure clock server's time, plus a policy configurable time delta. When this date is reached, the device MUST request resynchronization with the secure clock server.

This string is derived using the time conversion method specified in section 3.3.5.3. The device SHOULD use this value to determine when its secure clock is in need of refresh. This action SHOULD cause the indirect license acquisition host to perform a new secure clock synchronization procedure. In a non-tethered scenario, the device synchronizes with a secure clock after this date.