Element

ChargingTimeStamp

Validations ASN.1 Parent Types

The timestamp showing the start of the Charge Information. This item will be present where it is not the same as an associated Call Event Start Timestamp or where there is no such associated timestamp.

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

Note that local time is the local time at the location of the chargeable subscriber. Where the location is not available, as in some call forwarding scenarios, this will be a notional ‘network local time’.

Derivation:

GSM item answerTime or seizureTime (3GPP TS 32.005). The actual derivation will be dependent upon the charging principles used by the Sender and as defined by their IOT.

Conditionality:

Mandatory within groups

Supplementary Service Used where this occurs within Supplementary Service Event

Within group Location Service Usage the timestamp will only be present where it is not the same as the associated LCS Request Timestamp.

Within group

Basic Service Used

the timestamp will only be present where it is not the same as an associated Call Event Start Timestamp.

Format: CCYYMMDDHHMMSS

Validations

Error Code

Context

Severity Level

Validation Description

10

20

30

100

101

200

Calls

Calls

Calls

MOC

MTC

LCS

SS

LCS

Severe

Severe

Severe

Severe

Severe

Severe

Syntax error.

Value out of range.

Mandatory associated item UTC Time Offset Code missing.

Charging Timestamp is later than end of call (Call Event Start Timestamp plus Total Call Event Duration).

Charging Timestamp is later than LCS Request Timestamp plus Response Time.

Charging Timestamp before the commercial roaming start date for the specific service and the TAP file is not a test file.