|
chargingTimeStamp |
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 (GSM 12.05). 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
Value Added Service Used where this occurs within Value Added Service.
Within group
Location Service Usage the timestamp will only be present where it is not the
same as the associated LCS Request Timestamp.
Within groups
Basic Service Used
GPRS Service Used
the timestamp will
only be present where it is not the same as an associated Call Event Start
Timestamp.
Where groups
Supplementary Service Used
Value Added Service Used
occur within either
Mobile Originated Call or Mobile Terminated Call then the timestamp will only
be present where it is not the same as an associated Call Event Start
Timestamp.
Format:
CCYYMMDDHHMMSS
|
Error Code |
Context |
Severity Level |
Validation Description |
|
10 20 30 100 101 |
Calls Calls Calls MOC MTC GPRS LCS |
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. |