PrismToken

Core Functionality

The core functionality of the PrismToken – which developers would otherwise need to implement in their Vending System – includes the following:

• Communicates with the SM using the drivers and low-level API (STS600-8).
  • SM supports DKGA=04 and EA=11 per [STS202-3].
• Implements [STS600-4-2] key management processes using the SM, so there is no need to handle STS key management operations in the Vending System:
  • Provides a User Interface to key management features.
  • Generates VKLOADREQ that may be e-mailed to the KMC.
  • Parses an STS6 Enhanced Key Load File received from the KMC, loads the Vending Keys contained therein and maintains a store of Vending Key metadata and corresponding SM key register.
  • Provides Key Expiry warnings required by [STS 202-6].
• Thrift API to issue Credit (class=0), MeterTest (class=1), Management (class=2), and Key Change tokens.
  • Communication is over TCP/IPv4 with Transport Layer Security (TLS).
  • Implements TokenID conversion for the Vending Key’s Base Date (BDT) per [IEC 62055-41] and [STS402-1].
  • Maintains a store of TokenIDs issued per meter to prevent TokenID duplication (POS Application Process equivalent of Token Cancellation).
  • Provides Transfer Amount encoding for unit and currency tokens per [IEC 62055-41], [STS202-1], and [STS202-5]. Currency encoding is validated against the STSA VSM.
  • Supports 2-digit and 4-digit Manufacturer Code in meter PAN per [IEC 62055-41] and [STS202-2].
  • Supports Rollover Key Change tokens for BaseDate change (and associated TID rollover).
  • Supports 2-token (EA=07), 3-token (EA=07), and 4-token (EA=11) key change sets per [IEC 62055-41] and [STS202-3].
• The API is specified using the Thrift Interface Definition Language (IDL) which automatically generates the client’s software.
• Supports Prism instruction certificates (to convey SM manufacturer instructions to the SM) (see [PR- D2-0970] and [PR-
  D2-0828]).
• Provides a User Interface to miscellaneous SM configuration options and diagnostics.
• Handles the token generation portion of an STS transaction in a manner compatible with [SANS 1524- 6-10].
• STSA certified Point Of Sale (Entity Type A), tested against [STS531-1-0-02] and [STS531-1-0-04].
• {Future;Unplanned} Support for [STS101-2] virtual token carrier for DLSM/COSEM integration.

Also, the PrismToken maintains all this functionality in the face of an ongoing evolution of the IEC specification, STSA standards, Security Module, and Key Management Centre.

What The Prismtoken Doesn’t Do:

• Provide for meter registration, MSNO1 vending, or a meter configuration database.
• Implement [SANS 1524-6-10] (XMLVend) business rules (such a Grace Purchases, or resolving discrepancies between a
  meter’s magstripe card and the meter configuration database).
• Conversion of currency amounts to STS transfer units, using a Tariff mechanism.
• A database (or log) of vending transactions or tokens issued.
• Any form of “service point” or “point of connection” management.
• Any form of customer management, accounting, or debt collection.

The Vending System must provide this functionality.

Relationship to SM API

• The Security Module (SM) is the component of an STS system that secures the Vending Keys (VKs) and allows them to be used to construct STS tokens. While the SM only constructs well-formed tokens (per IEC 62055- 41), it has limited ability to enforce STS operational rules or ensure that the token is fit for purpose.
• Using an SM is necessary for building an STS vending system that complies with the IEC standard and STSA rules,
  but is not sufficient.
• The PrismToken provides high-level capabilities that result in a fully compliant subsystem for issuing STS tokens; these capabilities include:
  • Management of vending keys and association with Supply Group Codes (SGCs).
  • TokenId management to prevent the issue of duplicate tokens to a meter, and to restrict the issue of Special Reserved tokens.
  • Conversion of token fields (such as Transfer Amount and TokenId) to and from STS representation, with correct rounding.
  • To issue an STS token for a meter, third-party software integrating with the PrismToken need only know the meter’s configuration; PrismToken handles all other details of the STS environment.

XMLVend

• XMLVend is an XML-based protocol for Point-Of-Sale (POS) devices to communicate with an STS vending server. XMLVend is standardised in [SANS 1524-6-10].
• XMLVend assumes that the server integrates with POS and technical support systems, and supports functions such as payment and customer care; all of which are out of scope for the PrismToken. The token issue is a subset of the back-office functionality provided by a vending server, and as such the token issuing subsystem (PrismToken) cannot accept XMLVend requests.
• It would be typical for the PrismToken to be a component of a vending system that supports XMLVend. The PrismToken is designed to handle the issue of STS tokens within certain XMLVend transactions, in the manner prescribed by [SANS 1524-6-10] and other Eskom documents.
• Meter Serial Number Only (MSNO) vending looks up the meter’s configuration in a database given on the PAN or DRN (serial number).