LatestCallTimeStamp

Validations ASN.1 Parent Types

The Latest Call Timestamp is, as it implies, the Latest start of charging timestamp on any record.  It is not necessarily the start of charging timestamp of the last charge record on the file.

The timestamp contains the same timestamp as that of the latest Call Event Details when all times have been normalised to UTC time.

In case the batch contains SCU records either the completion or deposit timestamp should be taken into account according to the charging point value.

When the batch contains Content Transaction call/events the Content Charging Point value must be taken into account if more than one of Order Placed Timestamp, Requested Delivery Timestamp or Actual Delivery Timestamp are present in the call/event.  If only a single timestamp is present then this is taken as the charging point.

Timestamps from calls with severe errors should also be taken into account if possible i.e. no 10 or 20 type error occurred in the record

The time is given in the local time of the Sender (or Serving Network where this is not the Sender).  There must be a UTC Time Offset associated with the timestamp.

Optionality:

Transfer is at the discretion of the Sender PMN.

Conditionality: 

Mandatory within group Audit Control Information subject to optionality.

Validations

Error Code	Context	Severity Level	Validation Description
10   20   30     100	Audit   Audit   Audit     Audit	Warning   Warning   Warning     Warning	Syntax error.   Value out of range.   Mandatory associated item UTC Time Offset missing.   The timestamp does not match the timestamp of the latest Call Event Detail Timestamp.

 

LatestCallTimeStamp ::= [APPLICATION 133] DateTimeLong

Parent Types

AuditControlInfo
Text extracted from GSMA TD57 standard