that the UTRN Counter contained within a UTRN is greater than the lowest value in the UTRN Counter cache held on the Device. This ensures that a limited number of UTRNs can be executed out of sequence); and that the UTRN Counter is not equal to any value currently held in the UTRN Counter cache, i.e. that the Pre-payment Command has not be accepted before. PTUT The PTUT Truncated Originator Counter is The PTUT Truncated Originator provides a There is no additional impact to the Device Truncated detailed separately in Section 14 but a means for a Device to derive the Originator as the same UTRN Counter cache is used Originator summary is included here for completeness. Counter (and therefore the UTRN Counter) as for the UTRN Counter. Counter for the Prepayment Top Up Command This is the UTRN Counter as carried in the when it is entered locally (as a numeric 20 locally entered 20 digit UTRN. It is the 10 least digit code). significant bits of the UTRN Counter, which is itself the 32 most significant bits of the In order to determine the UTRN Counter, Originator Counter for the Command. the Device uses the algorithm defined in Section 14.6. The PTUT truncated counter is not processed in WAN received top-up commands. Remote 64-bit values carried in Update Security Remote Party Floor Sequence Numbers Party Floor Credentials Command, in: are of two types: Sequence newRemotePartyFloorSeqNumber Remote Party Sequence Numbers. Numbers attribute; Values used to set Execution Counters on a change of a Remote digital Party’s otherRemotePartyFloorSeqNumber signing credential with which the sequence; counter is associated; and Remote Party Specialist Sequence r attribute; and Numbers. Value is used to populate UTRN Counter cache following its sequence; clearance on change of the Supplier The values are used to set Counters Key Agreement Prepayment credential. associated with the credential being updated to Both types have a and variant. ‘new’ ‘other’ new values. Processing is as detailed in is used when the authorising remote ‘new’ Section 13.3.5.10. party is changing its own credentials (e.g.
that the UTRN Counter contained within a UTRN is greater than the lowest value in the UTRN Counter cache held on the Device. This ensures that a limited number of UTRNs can be executed out of sequence); and that the UTRN Counter is not equal to any value currently held in the UTRN Counter cache, i.e. that the Pre-payment Command has not be accepted before. PTUT Truncated Originator Counter The PTUT Truncated Originator Counter is detailed separately in Section 14 but a summary is included here for completeness. This is the UTRN Counter as carried in the locally entered 20 digit UTRN. It is the 10 least significant bits of the UTRN Counter, which is itself the 32 most significant bits of the Originator Counter for the Command. The PTUT truncated counter is not processed in WAN received top-up commands. The PTUT Truncated Originator provides a means for a Device to derive the Originator Counter (and therefore the UTRN Counter) for the Prepayment Top Up Command when it is entered locally (as a numeric 20 digit code). In order to determine the UTRN Counter, the Device uses the algorithm defined in Section 14.6. There is no additional impact to the Device as the same UTRN Counter cache is used as for the UTRN Counter. Remote Party Floor Sequence Numbers 64-bit values carried in Update Security Credentials Command, in: newRemotePartyFloorSeqNumber attribute; otherRemotePartyFloorSeqNumber sequence; attribute; and sequence; The values are used to set Counters associated with the credential being updated to new values. Processing is as detailed in Section 13.3.5.10. Remote Party Floor Sequence Numbers are of two types: Remote Party Sequence Numbers. Values used to set Execution Counters on a change of a Remote Party’s digital signing credential with which the counter is associated; and Remote Party Specialist Sequence Numbers. Value is used to populate UTRN Counter cache following its clearance on change of the Supplier Key Agreement Prepayment credential. Both types have a ‘new’ and ‘other’ variant. ‘new’ is used when the authorising remote party is changing its own credentials (e.g. r
GBCS_v0.8.1.docx