Online Vending Online Vending

SpecificationSpecification

Project: Project:

NRS009-6-10 / XMLVendNRS009-6-10 / XMLVend

NRS009 -WG12/05/2004

Kennedy P Subramoney

Eskom (NRS Project Management Agency

Resources and Strategy Group)

Developments since last meeting

• Project Working Group meeting was held on the 17 November 2003 in Cape Town, where several key decisions were taken.

• XMLVend 1.0 frozen end January 2004.• XMLVend 1.0 release for “Trial Use” end February.• Eskom, Manguang and Ethekweni are at advanced

stages of the procurement processes for Online Vending Systems based on XMLVend.

• NRS has agreed to fund continued development of the specification to a Version 2 (after Pilot)

• A article on XMLVend 1.0 was published in the March 2004 issue of Energize.

XMLVend 1.0 Implementation Models

XMLVend

Consumer Vending Client Operator

Vending Transaction Server

Vending Client

• Model 1

XMLVend 1.0 Implementation Models

• Model 2 (B2B)

XMLVend

XMLVend

Consumer Operator

Vending Transaction Server

Vendor B Vending Client

Vendor A Vending Client

Vendor C Vending Client

Consumer Operator

Consumer Operator

Vendor A Terminal/s

Vendor B Terminal/s

Vendor C Terminal/s

Proprietary Interface

Proprietary Interface

Proprietary InterfaceXMLVend

Use Cases

• 12 Consumer and Operator Use Cases – define the functionality of the system.– Confirm Customer / Meter Details (UC101)– Purchase Credit Token (UC102)– Receive EBSST Token (UC103)– Reprint Token (UC104)– Cancel Token (UC105)– Vend Trial Token (UC106)– Vend Replacement Token (UC107) – Log in (UC501)– Log out (UC502) – Start Batch (UC503)– End Batch (UC504) – Check Batch Totals (UC505)

Message Pairs And Data Model

• Message Pairs are used to implement each Use Case.

• The Data Model defines an XML vocabulary for Prepayment Vending.

Consumer /Operator

VendingClient

VendingServer

XMLVend_Request

XMLVend_Response

Result Data

Result message

XMLVend use case

Synchronous Request /Response Message pair(SOAP message boundto HTTP)

Data Model Example

 

 

<Login_Request>(ClientID)(TerminalID)(MsgID)(OpName) ?(Password) ?(Custom) ?</Login_Request> 

<Login_Response>(TerminalID)(MsgID)(CurrentVendorCredit)(OperatorMsg) ?(Custom) ?</Login_Response> 

Client (System) Reversals and Confirmations

Two options:• Client Request -> if server response received then

do nothing. If no response (after n retries), then send a system reversal message.

• Client Request -> always sends an advice message, if ok, then an advice confirmation message sent. If problem (after n retries), then send an advice system reversal message.

• This applies to Purchase Credit Token and Replacement Token only.

• System reversals have been introduced due to the unreliable nature of Online Vending communications.

• To reduce “pending transactions”.• To assist with the reconciliation process.

XMLVend 1.0 Specification Stack

XMLVend1.0

XML Schema 1.0

WSDL 1.1

SOAP 1.1

HTTP 1.1

XML 1.0 (second edition)

WS-I Basic Profile 1.0aWS-I Usage Scenarios 1.01

NRS009 Series

Use Case Message Pair Data Model

SSL / TLS

Security Options

• NRS Specification– SSL/TLS

•128bit server certificates•40 / 128 client certificates•NRS CA ???

– VPN•Network Layer Security

Compression

• An optional compression algorithm has been include in the specification.

Next Steps….

• We have achieved phase 1 of the project, release of Version 1.

• Phase 2 of the specification is to stabilise and promote the use of the specification.– Development of a compliance Test Suite.– Proactively move towards XMLVend 2.0

by monitoring and evaluating specification performance in pilots.

– Presentation of the specification to greater Prepayment community – SAPW.

– Engage other token providers, such as Telkom, Vodacom, MTN, Cell C

Mission:NRS009-6-10