|
ActualDeliveryTimeStamp |
The timestamp representing the actual time at which
the start of the Content Transaction was commenced. This is given in the time of the serving
Content Provider. There must be a UTC
Time Offset Code associated with the item.
Example:
The
Charged Party may request to download all messages at 2200hrs in order to
take advantage of off-peak rates while placing the order at an earlier time
but the actual content download may have commenced at 0030hrs.
Conditionality:
Must be
present within group
Content Transaction Basic Info
when no
other timestamp present within group or when item referenced as the Charging
Point.
|
Error Code |
Context |
Severity Level |
Validation Description |
|
10 11 20 21 30 31 100 101 200 |
Content Content Content Content Content Content Content Content Content |
Severe Warning Severe Warning Severe Warning Severe Warning Severe |
Syntax error and timestamp
referenced as Charging Point. Syntax error and timestamp not
referenced as Charging Point. Value out of range and timestamp
referenced as Charging Point. Value out of range and timestamp not
referenced as Charging Point. Mandatory associated UTC Time Offset
Code missing and timestamp referenced as Charging Point. Mandatory associated UTC Time Offset
Code missing and timestamp not referenced as Charging Point. Actual Delivery Timestamp after
associated Charge Detail timestamp and timestamp referenced as Charging
Point. Actual Delivery Timestamp after
associated Charge Detail timestamp and timestamp not referenced as Charging
Point. Actual Delivery Timestamp before the
commercial roaming start date for the specific service and the TAP file is
not a test file and the timestamp is referenced as the Charging Point. |