Browse Prior Art Database

Non-Volatile Memory (NVM) Provision For Network

IP.com Disclosure Number: IPCOM000123513D
Original Publication Date: 1998-Dec-01
Included in the Prior Art Database: 2005-Apr-04
Document File: 2 page(s) / 58K

Publishing Venue

IBM

Related People

Flenley, J: AUTHOR

Abstract

In current Automated Teller Machine (ATM) and kiosk applications, it is very common for the user to require persistent storage of certain values such as cassette counts, teller totals, deposit totals etc. Different hardware solutions have been developed to provide Persistent Storage (Non-Volatile Memory (NVM) to meet this requirement, generally requiring a user to program to multiple devices if their network consisted of hardware for multiple vendors. Window Open Services Architecture (WOSA) extension for financial services (WOSA/XFS), was designed to overcome this type of problem, defining common interfaces to methods supporting common functions on common financial devices. Unfortunately, the WOSA/XFS specification did not include an interface for NVM.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Non-Volatile Memory (NVM) Provision For Network

   In current Automated Teller Machine (ATM) and kiosk
applications, it is very common for the user to require persistent
storage of certain values such as cassette counts, teller totals,
deposit totals etc.  Different hardware solutions have been
developed to provide Persistent Storage (Non-Volatile Memory (NVM)
to meet this requirement, generally requiring a user to program to
multiple devices if their network consisted of hardware for multiple
vendors.  Window Open Services Architecture (WOSA) extension for
financial services (WOSA/XFS), was designed to overcome this type of
problem, defining common interfaces to methods supporting common
functions on common financial devices.  Unfortunately, the WOSA/XFS
specification did not include an interface for NVM.

   The solution described here provides a secure component,
for use in the Web environment, that delivers access to persistent
Storage to web applications.

   The component utilises the Windows NT* Registry and its
ability to store and maintain Persistent Keys, to provide this
persistent storage.  The location of the keys are not obvious, being
hidden in the system created component ID keys for the component.
The key contents can be stored either in clear text/values, or
encrypted for security.

   The methods exposed by the component are as follows:
  long   GetValue(long Index);    // returns long value stored in
                                     position Index
  long   SetValue(long Index,     // sets long value at position
         long Value);                Index to Value
  BSTR   GetString(long Index);   // returns string value stored
                                      at position Index
  long   SetString(long Index,    // sets string value at
         BSTR String);               position Index to String
  long   GetMa...