xmlvend (online vending specification) towards an industry standard (nrs009-6-10)
DESCRIPTION
XMLVend (Online Vending Specification) Towards an Industry Standard (NRS009-6-10). Presented by Kennedy Subramoney Specification – Project Leader Resources & Strategy (A Division of Eskom) CR&D Department. Discussion Points. XMLVend Background Online Vending - Context - PowerPoint PPT PresentationTRANSCRIPT
Presented byKennedy Subramoney
Specification – Project Leader Resources & Strategy (A Division of Eskom)
CR&D Department
XMLVend (Online Vending Specification)
Towards an Industry Standard(NRS009-6-10)
1. XMLVend Background2. Online Vending - Context3. XMLVend Specification Overview4. Road Map5. Some implementation insights6. XMLVend 2.07. Conclusions8. XMLVend in Action
Discussion Points
Background The requirements for an Online
Vending Specification were: Curb the use of Proprietary Systems. Specify minimum security, communication,
& interoperability standards. Must be platform independent, extensible
and adaptable. Support existing prepayment standards,
STS and CVS (NRS009 Series). Ensure industry support and ownership. Utilize existing industry technology
standards. Development tool set support Existing Developer Skills base.
Online Vending Centralized Multiuser Database Centralized Vending Business Logic Centralized Security Modules (STS Token Generation) “Thin” Client / Server Architecture
SM
MasterDatabase
BusinessLogic
Online ClientApplication
OnlineServer
Application
BusinessLogic
“Permanent”Connection
Specification Overview
Web Service Interoperability Organization (WS-I) – Ensures interoperability.
WSDL - XML file used to define the contract by which ML file used to define the contract by which the Web Service Providers and Consumers interact, the Web Service Providers and Consumers interact, i.e. Vending Servers and Vending Clients.i.e. Vending Servers and Vending Clients.
XML Schema - XML file used to define message XML file used to define message contents and message element data types and contents and message element data types and constraints.constraints.
XML Schema 1.0
WSDL 1.1
Message Pair Data Model
WS-I Basic Profile 1.0aWS-I Usage Scenarios 1.01
Web Services layer –(XML and SOAP)
Content Compression uses GZIP.
Application layer uses HTTP.
Security - SSL / TLS authentication and encryption.
TCP/IP – Network Communications layer.
Link / Physical Layer
Specification Overview
SOAP 1.1
HTTP 1.1
XML 1.0 (second edition)
Security Protocol - SSL / TLS
Network Communications Protocol - TCP / IP
Compression Algorithm - GZIP
Ethernet, GPRS, POTS Dial-up, X25, LeasedLines
Implementation Protocols
XMLVend Road Map
v1.0(5/03/2004)
•1st Release
v1.1(11/06/2004)
•Fixes minorIssues.•Server RFP
v1.22(28/01/2005)•Major Update•KCT•<choice> schema type•Tax Details
v2.0May/June
‘06•Major Update•New Use Cases.•O.O.
Implementation Insights
Eskom Server RFP and Pilot Results. Extensive Testing of Use Cases – updates identified. Implementation of SSL / TLS. Implementation of GZIP Compression.
Security (SSL / TLS)
Technology easily implemented, however the required supporting PKI is still to be tested.
Mandatory “Client ID” Authentication on every financial request.
VendingClient Vending
Server
XMLVend_Request (123)
XMLVend_Response
XMLVend_Request (456)
XMLVend_Response
Secure SSL Channel
Client ID-123
0
1000
2000
3000
4000
5000
6000
XMLVend Messages
Byte
s
Total Message Size -Compressed
Total Message Size - NoCompression
Compression - GZIP Average saving - 1156 bytes Average % Impact of GZIP - 38%.
Compression - GZIP
Average Overhead – 53% Vend Use Case overhead – 47%
XMLVend Vend Message Stack
52.21
35.33
12.46
0.00
20.00
40.00
60.00
80.00
100.00
120.00
Vend
Per
cen
tag
e
%SSL Overhead
% HTTP Header
% Soap Body
Illustrative Message Costs* Assuming GPRS cost of R2-00 per MB The cost of a Vend and EBSST
transactions are – 0.41 cents and 0.39 cents resp.
The average cost of all transactions – 0.38 cents.
Note: These costs only indicate the cost per transaction and not the Total Cost of Operating an Online Vending System.
XMLVend 2.0 The following new Use Cases have been
identified: Credit Update Statement STS Engineering Tokens Auto-Reprint Last Transaction Debt Recovery Bank (“Create Deposit Slip”) Customer Fault Reporting Account Payments Reprint Deposit Slip
XMLVend 2.0
Improved Object Oriented Design. Message size optimization. HTTP Header optimization. Specification Reference
Implementation. Specification Test Suite Release.
Conclusions XMLVend ensures that there is the
continued standardization of prepayment vending.
XMLVend1.0 has been produced with significant contributions from several vending equipment suppliers, which demonstrates the level of maturity within the industry.
XMLVend has matured into a robust and stable specification, with significant support to become an Industry Standard.
XMLVend in Action
Thank youThank you
and Acknowledgementand Acknowledgement of all contributors to XMLVend - of all contributors to XMLVend -
a specification for industry, by the industry. a specification for industry, by the industry.
http://www.nrs.eskom.co.za/xmlvendhttp://www.nrs.eskom.co.za/xmlvend