Transfer of valuable information between a secure module and another module

Abstract

The present invention relates to system, apparatus and method for communicating valuable data from a portable module to another module via an electronic device. More specifically, the disclosed system, apparatus and method are useful for enabling a user to fill a portable module with a cash equivalent and to spend the cash equivalent at a variety of locations. The disclosed system incorporates an encryption/decryption method.

Claims

What is claimed is:

1. A method for electronically transferring units of exchange between a first module and a second module, comprising the steps of:

a. initiating communication between said first module and an electronic device;

b. passing a first value datum from said first module to said electronic device;

c. passing said first value datum from said electronic device to said second module;

d. performing a mathematical calculation on said first value datum thereby creating a second value datum;

e. passing said second value datum from said second module to said electronic device;

f. passing said second value datum from said electronic device to said first module;

g. storing said second value datum in said first module; and

h. discontinuing communication between said first module and said electronic device.

2. The method of claim 1, wherein said first value datum represents a monetary equivalent.

3. The method of claim 1, wherein said first value datum is encrypted.

4. The method of claim 1, wherein said second value datum is encrypted.

5. The method of claim 3, wherein the step of performing a mathematical calculation comprises the steps of:

m. decrypting said first value datum with a public key thereby creating a decrypted value;

n. performing at least one of an addition function and a subtraction function on said decrypted value thereby creating a value result; and

o. encrypting said value result with a private key thereby creating said second value datum.

6. The method of claim 1, wherein the step (b) of passing is performed over at least a single conductive contact.

Description

CROSS REFERENCE TO OTHER APPLICATIONS

The following applications of common assignee contains related subject matter and is hereby incorporated by reference:

Ser. No. UNKNOWN, filed Jan. 31, 1996, entitled METHOD, APPARATUS, SYSTEM AND FIRMWARE FOR SECURE TRANSACTIONS; and

Ser. No. UNKNOWN, filed Jan. 31, 1996, entitled METHOD, APPARATUS AND SYSTEM FOR TRANSFERRING UNITS OF VALUE.

BACKGROUND OF THE INVENTION

1. Technical Field of the Invention

The present invention relates to a method and system for transferring valuable information securely between a secure module and another module. More particularly, the present invention relates to transferring units of value between a microprocessor based secure module and another module used for carrying a monetary equivalent.

2. Description of Related Art

In the past the preferred means for paying for an item was cash. As our society has become more advanced, credit cards have become an accepted way to pay for merchandise or services. The payment is not a payment to the merchant, but instead is a credit given by a bank to the user that the merchant accepts as payment. The merchant collects money from the bank based on the credit. As time goes on, cash is used less and less, and money transfers between parties are becoming purely electronic.

Present credit cards have magnetic strips to identify the owner of the card and the credit provider. Some credit cards have electronic circuitry installed that identifies the credit card owner and the credit or service provider (the bank).

The magnetic strips installed in present credit cards do not enable the card to be used as cash. That is the modern credit card does not allow the consumer to buy something with the credit card and the merchant to receive cash at the time of the transaction. Instead, when the consumer buys something on credit, the merchant must later request that the bank pay for the item that the consumer bought. The bank then bills the consumer for the item that was bought.

Thus, there is a need for an electronic system that allows a consumer to fill an electronic module with a cash equivalent in the same way a consumer fills his wallet with cash. When the consumer buys a product or service from a merchant, the consumer's module can be debited and the merchant's cash drawer can be credited without any further transactions with a bank or service provider.

SUMMARY OF THE INVENTION

The present invention is an apparatus, system and method for communicating a cash equivalent electronically to and from a portable module. The portable module can be used as a cash equivalent when buying products and services in the market place.

The present invention comprises a portable module that can communicate to a secure module via a microprocessor based device. The portable module can be carried by a consumer, filled with electronic money at an add-money station, and be debited by a merchant when a product or service is purchased by the consumer. As a result of a purchase, the merchant's cash drawer will indicate an increase in cash value.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the method and apparatus of the present invention may be had by reference to the following Detailed Description when taken in conjunction with the accompanying Drawings wherein:

FIG. 1 depicts an exemplary system for transferring valuable information between a module and a secure device;

FIG. 2 is a block diagram of an embodiment of a portable module;

FIG. 3 is a block diagram of an embodiment of a microprocessor based module;

FIG. 4 is an exemplary technique for transferring valuable data securely into a portable module;

FIG. 5 is an exemplary technique for transferring valuable data securely out of a portable module;

FIG. 6 is an exemplary organization of the software and firmware within a secure microprocessor based device; and

FIG. 7 is an exemplary configuration of software and firmware within a secure microprocessor based device.

DETAILED DESCRIPTION OF A PRESENTLY PREFERRED EXEMPLARY EMBODIMENT

FIG. 1 depicts a block diagram of an exemplary system 100 for transferring valuable information to and from a portable module. A portable module 102, which will be described in more detail later, communicates to a microprocessor based device 104. The portable module 102 may contain information that represents units of exchange or a currency equivalent. The microprocessor based device 104 can be any of an unlimited number of devices. For example, the microprocessor based device 104 could be a personal computer, an add-a-fare machine at a train or bus station (similar to those in today's District of Columbia metro stations), a turn style, a toll booth, a bank's terminal, a ride at a carnival, a washing machine at a Laundromat, a locking device, a mail metering device or any device that controls access, or meters a monetary equivalent, etc.

The means for communication 106 between the portable module 102 and the microprocessor based device 104 is preferably via a single wire or contact connection. The single wire connection 106 preferably incorporates a communication protocol that allows the portable module 102 and the microprocessor based device 104 to communicate in a bidirectional manner. Preferably the communication protocol is a one-wire protocol developed by Dallas Semiconductor. It is understood that the means for communicating 106 is not limited to a single wire connection. The communication means 106 could be multiple wires, a wireless communication system, infrared light, any electromagnetic means, a magnetic technique, or any other similar technique.

The microprocessor based device 104 is electrically connected to another microprocessor based device, which is preferably a secure device 108. The term secure device means that the device is designed to contain a secret code and the secret code is extremely difficult to learn. An example of a secure device 108 is explained later in this document.

The microprocessor based device 104 can be connected to a variety of other devices. Such devices include, but are not limited to a cash acceptor 110, an automatic teller machine (ATM) 112, a credit card reader 114, and a phone line 116.

The cash acceptor 110 is adapted to receive cash in the form of currency, such as dollar bills or coins. The cash acceptor 110, preferably, determines the value of the accepted currency. The cash acceptor 110 communicates to the microprocessor based device 104 and informs the device 104 of how much currency has been deposited in the cash acceptor 110.

The cash acceptor 110 can also be a device which provides currency. That is, the cash accepter 110 in response to a communication from the microprocessor based device 104, may provide a metered amount of currency to a person.

The credit card reader 114, and ATM 112 can also be attached to the microprocessor based device 104. The credit card reader 114 could be used to read a user's credit card and then, when authorized, either communicate to the microprocessor based device 104 that units of exchange need to be added to the portable module or that units of exchange need to be extracted from the portable module to pay for a good, service or credit card bill.

The ATM 112 may also be connected to the microprocessor based device. Via communications from the ATM 112, the microprocessor based device 104 can be informed that units of exchange need to be added or subtracted from the portable module 102.

Furthermore, it is also possible that the microprocessor based device 104 is connected to a phone line 116. The phone line may be used for a variety of things. Most importantly, the phone line may be used to allow the microprocessor based device 104 to communicate with a network of devices. Such telephonic communication may be for validating transactions or for aiding the accounting of transactions that are performed via the microprocessor based device's 104 aid. It is further understood that the phone line may be any of a vast variety of communication lines including wireless lines. Video, analog, or digital information may be communicated over the phone line 116.

FIG. 2 depicts a preferred exemplary portable module 102. The portable module 102 is preferably a rugged read/write data carrier that can act as a localized data base and be easily accessed with minimal hardware. The module can be incorporated in a vast variety of portable items which includes, but is not limited to a durable micro-can package that is highly resistant to environmental hazards such as dirt, moisture, and shock. The module can be incorporated into any object that can be articulated by a human or thing, such as a ring, bracelet, wallet, name tag, necklace, baggage, machine, robotic device, etc. Furthermore, the module 102 could be attached to a stationary item and the microprocessor based device 104 may be articulated to the portable module 102. For example, the module 102 may be attached to a piece of cargo and a module reader may be touched to or brought near the module 102. The module reader may be part of the microprocessor based device 104.

The portable module 102 comprises a memory 202 that is preferably, at least in part, nonvolatile memory for storing and retrieving vital information pertaining to the system to which the module 102 may become attached to. The memory 202 may contain a scratchpad memory which may act as a buffer when writing into memory. Data is first written to the scratchpad where it can be read back. After data has been verified, the data is transferred into the memory.

The module 102 also comprises a counter 206 for keeping track of the number of transactions the module has performed (the number of times certain data in the memory of the module has been changed). A timer 102 may be provided in the module to provide the ability to time stamp transactions performed by the module. A memory controller 204 controls the reading and writing of data into and out of the memory 202.

The module also may comprise an identification number 210. The identification number preferably uniquely identifies the portable module from any other portable module.

An input/output control circuit 212 controls the data flow into and out of the portable module 102. The input/output control ("I/O") 212 preferably has an input buffer and an output buffer and interface circuitry 214. As stated above, the interface circuitry 214 is preferably a one-wire interface. Again, it is understood that a variety of technologies can be used to interface the portable module 102 to another electronic device. A single wire or single connection is preferred because the mechanics of making a complete connection is simplified. It is envisioned that a proximity/wireless communication technique is also a technique for communicating between the module 102 and another device. Thus, the interface circuit 214 can be a single wire, multiple wire, wireless, electromagnetic, magnetic, light, or proximity, interface circuit.

FIG. 3 depicts a block diagram of an exemplary secure microprocessor based device ("secure device") 108. The secure device circuitry can be a single integrated circuit. It is understood that the secure device 108 could also be a monolithic or multiple circuits combined together. The secure device 108 preferably comprises a microprocessor 12, a real time clock 14, control circuitry 16, a math coprocessor 18, memory circuitry 20, input/output circuitry 26, and an energy circuit 34.

The secure device 108 could be made small enough to be incorporated into a variety of objects including, but not limited to a token, a card, a ring, a computer, a wallet, a key fob, a badge, jewelry, a stamp, or practically any object that can be grasped and/or articulated by a user of the object. In the present system 100, the secure device 108 is preferably adapted to be a trusted certifying authority. That is the secure device 108 is a trusted computer. The secure device 108 comprises a numeric coprocessor 18 optimized for math intensive encryption. The BIOS is immune to alteration and is specifically designed for secure transactions. This secure device 108 is preferably encased in a durable, dirt, moisture and shock resistant stainless steel enclosure, but could be encased in wide variety of structures so long as specific contents of the secure device 108 are extremely difficult to decipher. The secure device 108. The secure device 108 may have the ability to store or create a private/public key set, whereby the private key never leaves the secure device 108 and is not revealed under almost any circumstance. Furthermore, the secure module 108 is preferably designed to prevent discovery of the private key by an active self-destruction of the key upon wrongful entry.

The microprocessor 12 is preferably an 8-bit microprocessor, but could be 16, 32, 64 or any operable number of bits. The clock 14 provides timing for the module circuitry. There can also be separate clock circuitry 14 that provides a continuously running real time clock.

The math coprocessor circuitry 18 is designed and used to handle very large numbers. In particular, the coprocessor will handle the complex mathematics of RSA encryption and decryption or other types of math intensive encryption or decryption techniques.

The memory circuitry 20 may contain both read-only-memory and non-volatile random-access-memory. Furthermore, one of ordinary skill in the art would understand that volatile memory, EPROM, SRAM and a variety of other types of memory circuitry might be used to create an equivalent device.

Control circuitry 16 provides timing, latching and various necessary control functions for the entire circuit.

An input/output circuit 26 enables bidirectional communication with the secure module 108. The input/output circuitry 26 preferably comprises at least an output buffer and an input buffer. For communication via a one-wire bus, one-wire interface circuitry can be included with the input/output circuitry 26. It is understood that the input/output circuitry 26 of the secure device 108 can be designed to operate on a single wire, a plurality of wires or any means for communicating is information between the secure module 108 and the microprocessor based device 104.

An energy circuit 34 may be necessary to maintain stored information in the memory circuitry 20 and/or aid in powering the other circuitry in the module 108. The energy circuit 34 could consist of a battery, capacitor, R/C circuit, photo-voltaic cell, or any other equivalent energy producing circuit or means.

The firmware architecture of the secure module 108 and how it operates within the exemplary system for transferring valuable information, such as units of exchange or currency, between the secure module 108 and a portable module 102 will now be discussed. The secure module 108 provides encryption and decryption services for confidential data transfer through the microprocessor based device 104. The following examples are intended to illustrate a preferred feature set of the secure module 108 and to explain the services that the exemplary system 100 can offer. These applications and examples by no means limit the capabilities of the invention, but instead bring to light a sampling of its capabilities.

I. Overview of the Preferred Secure Module 108 and its Firmware Design

Referring to FIG. 3 again, the secure module 108 preferably contains a general-purpose, 8051-compatible micro controller 12 or a reasonably similar product, a continuously running real-time clock 14, a high-speed modular exponentiation accelerator for large integers (math coprocessor) 18, input and output buffers 28, 30 with a one-wire interface 32 for sending and receiving data, 32 Kbytes of ROM memory 22 with preprogrammed firmware, 8 Kbytes of NVRAM (non-volatile RAM) 24 for storage of critical data, and control circuitry 16 that enables the micro controller 12 to be powered up to interpret and act on the data placed in an input data object. The module 108 draws its operating power from a single wire, one-wire communication line. The micro controller 12, clock 14, memory 20, buffers 28, 30, one-wire front-end 32, modular exponentiation accelerator 18, and control circuitry 16 are preferably integrated on a single silicon chip and packaged in a stainless steel micro can using packaging techniques which make it virtually impossible to probe the data in the NVRAM 24 without destroying the data. Initially, most of the NVRAM 24 is available for use to support applications such as those described below. One of ordinary skill will understand that there are many comparable variations of the module design. For example, volatile memory might be used, or an interface other than a one-wire interface could be used.

The secure module 108 is preferably intended to be used first by a Service Provider who loads the secure module 108 with data to enable it to perform useful functions, and second by an End User who issues commands to the secure module 108 to perform operations on behalf of the Service Provider for the benefit of the End User. For this reason, the secure module 108 offers functions to support the Service Provider in setting up the module for an intended application. It also offers functions to allow the End User to invoke the services offered by the Service Provider.

Each Service Provider can reserve a block of NVRAM memory to support its services by creating a transaction group 40 (refer to FIGS. 6 and 7). A transaction group 40 is simply a set of software objects 42 that are defined by the Service Provider. These objects 42 include both data objects (encryption keys, transaction counts, money amounts, date/time stamps, etc.) and transaction scripts 44 which specify how to combine the data objects in useful ways. Each Service Provider creates his own transaction group 40, which is independent of every other transaction group 40. Hence, multiple Service Providers can offer different services in the same module 108. The number of independent Service Providers that can be supported depends on the number and complexity of the objects 42 defined in each transaction group 40. Examples of some of the objects 42 that can be defined within a transaction group 40 are the following:

    ______________________________________
    RSA Modulus         Clock Offset
    RSA Exponent        Random SALT
    Transaction Script  Configuration Data
    Transaction Counter Input Data
    Money Register      Output Data
    Destructor
    ______________________________________

    ______________________________________
    Privatize Object   Lock Object
    Lock Transaction Group
                       Lock Micro-In-A-Can .TM.
    ______________________________________

    ______________________________________
    Set Common PIN(01H)
    ______________________________________
    Transmit (to secure module)
    01H, old PIN, new PIN, PIN option byte
    Receive data
    CSB (command status byte) = 0 if successful,
    appropriate error code otherwise
    Output length = 0
    Output Data = 0
    ______________________________________

    ______________________________________
    PIN.sub.-- TO.sub.-- ERASE
                      00000001b (require PIN for
                      Master Erase)
    PIN.sub.-- TO.sub.-- CREATE
                      00000010b (require PIN for
                      group creation).
    ______________________________________

    ______________________________________
    ERR.sub.-- BAD.sub.-- COMMON.sub.-- PIN
                        (Common PIN match
                        failed)
    ERR.sub.-- BAD.sub.-- PIN.sub.-- LENGTH
                        (New PIN length
                        > 8 bytes)
    ERR.sub.-- BAD.sub.-- OPTION.sub.-- BYTE
                        (Unrecognizable option
                        byte)
    ______________________________________

    ______________________________________
    Command status byte
                      (0 if command successful,
                      error code otherwise, 1 byte)
    Output data length
                      (Command output length, 2
                      bytes)
    Output data       (Command output, length
                      specified above).
    ______________________________________


______________________________________
    Master Erase (02H)
    ______________________________________
    Transmit data
    02H, Common PIN
    Receive data
    CSB = 0 if command was successful,
    ERR.sub.-- BAD.sub.-- COMMON.sub.-- PIN otherwise
    Output length = 0
    Output data = 0
    ______________________________________

    ______________________________________
    Create Group (03H)
    ______________________________________
    Transmit data
    03H, Common PIN, Group name, Group PIN
    Receive data
    CSB = 0 if command successful, appropriate
    error code otherwise
    Output length = 1 if successful, 0 otherwise
    Output data = Group ID if successful, 0
    otherwise
    ______________________________________

    ______________________________________
    ERR.sub.-- BAD.sub.-- COMMON.sub.-- PIN
                       (Incorrect common PIN)
    ERR.sub.-- BAD.sub.-- NAME.sub.-- LENGTH
                       (If group name length > 16
                       bytes)
    ERR BAD.sub.-- PIN.sub.-- LENGTH
                       (If group PIN length
                       > 8 bytes)
    ERR.sub.-- MIAC.sub.-- LOCKED
                       (The secure module has
                       been locked)
    ERR.sub.-- INSUFFICIENT.sub.-- RAM
                       (Not enough memory for
                       new group)
    ______________________________________


______________________________________
    Set Group PIN (04H)
    ______________________________________
    Transmit data
    04H, Group ID, old GPIN, new GPIN
    Receive data
    CSB = 0 if command successful, appropriate
    error code otherwise
    Output length = 0
    Output data = 0
    ______________________________________

    ______________________________________
    ERR.sub.-- BAD.sub.-- GROUP.sub.-- PIN
                        (Group PIN match
                        failed)
    ERR.sub.-- BAD.sub.-- PIN.sub.-- LENGTH
                        (New group PIN length
                        > 8 bytes)
    ______________________________________


______________________________________
    Create Object (05H)
    ______________________________________
    Transmit data
    05H, Group ID, Group PIN, Object type, Object
    attributes, Object data
    Receive data
    CSB = 0 if command successful, appropriate
    error code otherwise
    Output length = 1 if successful, 0 otherwise
    Output data = object ID if successful, 0
    otherwise
    ______________________________________

    ______________________________________
    ERR.sub.-- BAD.sub.-- GROUP.sub.-- PIN
                        (Incorrect group PIN)
    ERR.sub.-- GROUP.sub.-- LOCKED
                        (The group has been
                        locked)
    ERR.sub.-- MIAC.sub.-- LOCKED
                        (The secure module has
                        been locked)
    ERR.sub.-- INVALID.sub.-- TYPE
                        (The object type
                        specified is invalid)
    ERR.sub.-- BAD.sub.-- SIZE
                        (The objects length
                        was invalid)
    ERR.sub.-- INSUFFICIENT.sub.-- RAM
                        (Not enough memory for
                        new object)
    Object types: RSA modulus    0
                  RSA exponent   1
                  Money register 2
                  Transaction counter
                                 3
                  Transaction script
                                 4
                  Clock offset   5
                  Random SALT    6
                  Configuration object
                                 7
                  Input data object
                                 8
                  Output data object
                                 9
    Object Attributes:
                  Locked         00000001b
                  Privatized     00000010b
    ______________________________________

    ______________________________________
    Lock Object (06H)
    ______________________________________
    Transmit data
    06H, Group ID, Group PIN, Object ID
    Receive data
    CSB = 0 if command successful, appropriate
    error code otherwise
    Output length = 0
    Output data = 0
    ______________________________________

    ______________________________________
    ERR.sub.-- BAD.sub.-- GROUP.sub.-- PIN
                        (Incorrect group PIN)
    ERR.sub.-- GROUP.sub.-- LOCKED
                        (The group has already
                        been locked)
    ERR.sub.-- MIAC.sub.-- LOCKED
                        (The secure module has
                        been locked)
    ERR.sub.-- BAD.sub.-- GROUP.sub.-- ID
                        (Specified group does
                        not exist)
    ERR.sub.-- BAD.sub.-- OBJECT.sub.-- ID
                        (Specified object does
                        not exist)
    ______________________________________


______________________________________
    Privatize Object (07H)
    ______________________________________
    Transmit data
    07H, Group ID, Group PIN, Object ID
    Receive data
    CSB = 0 if successful, appropriate error code
    otherwise
    ______________________________________

    ______________________________________
    ERR.sub.-- BAD.sub.-- GROUP.sub.-- PIN
                        (Incorrect group PIN)
    ERR.sub.-- GROUP.sub.-- LOCKED
                        (The group has already
                        been locked)
    ERR.sub.-- MIAC.sub.-- LOCKED
                        (The secure module has
                        been locked)
    ERR.sub.-- BAD.sub.-- GROUP.sub.-- ID
                        (Specified group does
                        not exist)
    ERR.sub.-- BAD.sub.-- OBJECT.sub.-- ID
                        (Specified object does
                        not exist)
    ______________________________________


______________________________________
    Make Object Destructable (08H)
    ______________________________________
    Transmit data
    08H, Group ID, Group PIN, Object ID
    Receive data
    CSB = 0 if successful, appropriate error code
    otherwise
    ______________________________________

    ______________________________________
    ERR.sub.-- BAD.sub.-- GROUP.sub.-- PIN
                        (Incorrect group PIN)
    ERR.sub.-- GROUP.sub.-- LOCKED
                        (The group has already
                        been locked)
    ERR.sub.-- MIAC.sub.-- LOCKED
                        (The secure module has
                        been locked)
    ERR.sub.-- BAD.sub.-- GROUP.sub.-- ID
                        (Specified group does
                        not exist)
    ERR.sub.-- BAD.sub.-- OBJECT.sub.-- ID
                        (Specified object does
                        not exist)
    ______________________________________


______________________________________
    Lock Secure module (09H)
    ______________________________________
    Transmit data
    09H, Common PIN
    Receive data
    CSB = 0 if successful, appropriate error code
    otherwise
    Output length = 2 if successful, 0 otherwise
    Output data = audit trail size if successful,
    0 otherwise
    ______________________________________

    ______________________________________
    ERR.sub.-- BAD.sub.-- COMMON.sub.-- PIN
                        (Supplied common PIN
                        was incorrect)
    ERR.sub.-- MIAC.sub.-- LOCKED
                        (Secure module was
                        already locked)
    ______________________________________


______________________________________
    Lock Group (0AH)
    ______________________________________
    Transmit data
    0AH, Group ID, Group PIN
    Receive data
    CSB = 0 if command successful, appropriate
    error code otherwise
    Output length = 0
    Output data = 0
    ______________________________________

    ______________________________________
    ERR.sub.-- BAD.sub.-- GROUP.sub.-- PIN
                        (Incorrect group PIN)
    ERR.sub.-- GROUP.sub.-- LOCKED
                        (The group has already
                        been locked)
    ERR.sub.-- MIAC.sub.-- LOCKED
                        (The secure module has
                        been locked)
    ERR.sub.-- BAD.sub.-- GROUP.sub.-- ID
                        (Specified group does
                        not exist)
    ______________________________________


______________________________________
    Invoke Transaction Script (0BH)
    ______________________________________
    Transmit data
    0BH, Group ID, Group PIN, Object ID
    Receive data
    CSB = 0 if command successful, appropriate
    error code otherwise
    Output length = 1 if successful, 0 otherwise
    Output data = estimated completion time
    ______________________________________

    ______________________________________
    ERR.sub.-- BAD.sub.-- GROUP.sub.-- PIN
                        (Incorrect group PIN)
    ERR.sub.-- BAD.sub.-- GROUP.sub.-- ID
                        (Specified group does
                        not exist)
    ERR.sub.-- BAD.sub.-- OBJECT.sub.-- ID
                        (Script object did not
                        exist in group)
    ______________________________________


______________________________________
    Read Object (0CH)
    ______________________________________
    Transmit data
    0CH, Group ID, Group PIN, Object ID
    Receive data
    CSB = 0 if command successful, appropriate
    error code otherwise
    Output length = object length if successful, 0
    otherwise
    Output data = object data if successful, 0
    otherwise
    ______________________________________

    ______________________________________
    ERR.sub.-- BAD.sub.-- GROUP.sub.-- PIN
                        (Incorrect group PIN)
    ERR.sub.-- BAD.sub.-- GROUP.sub.-- ID
                        (Specified group does
                        not exist)
    ERR.sub.-- BAD.sub.-- OBJECT.sub.-- ID
                        (Object did not exist
                        in group)
    ERR.sub.-- OBJECT.sub.-- PRIVATIZED
                        (Object has been
                        privatized)
    ______________________________________


______________________________________
    Write Object (0DH)
    ______________________________________
    Transmit data
    0DH, Group ID, Group PIN, Object ID, Object
    size, Object Data
    Receive data
    CSB = 0 if successful, appropriate error code
    otherwise
    Output length = 0
    Output data = 0
    ______________________________________

    ______________________________________
    ERR.sub.-- BAD.sub.-- GROUP.sub.-- PIN
                         (Incorrect group PIN)
    ERR.sub.-- BAD.sub.-- GROUP.sub.-- ID
                         (Specified group does
                         not exist)
    ERR.sub.-- BAD.sub.-- OBJECT ID
                         (Object did not exist
                         in group)
    ERR.sub.-- BAD.sub.-- OBJECT.sub.-- SIZE
                         (Illegal object size
                         specified)
    ERR.sub.-- OBJECT.sub.-- LOCKED
                         (Object has been
                         locked)
    ERR.sub.-- OBJECT.sub.-- PRIVATIZED
                         (Object has been
                         privatized)
    ______________________________________


______________________________________
    Read Group Name (0EH)
    ______________________________________
    Transmit data
    0EH, Group ID
    Receive data
    CSB = 0
    Output Length = length of group name
    Output data = group name
    ______________________________________

    ______________________________________
    Delete Group (0FH)
    ______________________________________
    Transmit data
    0FH, Group ID, Group PIN
    Receive data
    CSB = 0 if successful, appropriate error code
    otherwise
    Output length = 0
    Output data = 0
    ______________________________________

    ______________________________________
    ERR.sub.-- BAD.sub.-- CROUP.sub.-- PIN
                         (Incorrect group PIN)
    ERR.sub.-- BAD.sub.-- GROUP.sub.-- ID
                         (Specified group does
                         not exist)
    ERR.sub.-- MIAC.sub.-- LOCKED
                         (Secure module has
                         been locked)
    ______________________________________


______________________________________
    Get Command Status Info (10H)
    ______________________________________
    Transmit data
    10H
    Receive data
    CSB = 0
    Output length = 6
    Output data = secure module status structure
    (see below)
    ______________________________________

    ______________________________________
    Last command executed  (1 byte)
    Last command status    (1 byte)
    Time command received  (4 bytes)
    ______________________________________


______________________________________
    Get Secure module Configuration Info (11H)
    ______________________________________
    Transmit data
    11H
    Receive data
    CSB = 0
    Output length = 4
    Output data = secure module configuration
    structure
    ______________________________________

    ______________________________________
    Number of groups       (1 byte)
    Flag byte (see below)  (1 byte)
    Audit trail size/Free RAM
                           (2 bytes)
    ______________________________________

    ______________________________________
    00000001b (Secure module is locked)
    00000010b (Common PIN required for access)
    ______________________________________


______________________________________
    Read Audit Trail Info (12H)
    ______________________________________
    Transmit data
    12H, Common PIN
    Receive data
    CSB = 0 if command successful, appropriate
    error code otherwise
    Output length = audit trail structure size (5)
    if successful, 0 otherwise
    Output data = audit trail info structure if
    successful, 0 otherwise
    ______________________________________

    ______________________________________
    Number of used transaction records
                            (2 bytes)
    Number of free transaction records
                            (2 bytes)
    A boolean specifying whether or
                            (1 byte)
    not the audit trail rolled
    since previous read command
    ______________________________________

    ______________________________________
    ERR.sub.-- BAD.sub.-- COMMON.sub.-- PIN
                         (Common PIN was
                         incorrect)
    ERR.sub.-- MIAC.sub.-- NOT.sub.-- LOCKED
                         (Secure module is not
                         locked)
    ______________________________________


______________________________________
    Read Audit Trail (13H)
    ______________________________________
    Transmit data
    13H, Common PIN
    Receive data
    CSB = 0 if command successful, appropriate
    error code otherwise
    Output length = # of new records * 6 if
    successful, 0 otherwise
    Output data = new audit trail records
    ______________________________________

    ______________________________________
    ERR.sub.-- BAD.sub.-- COMMON.sub.-- PIN
                       (Common PIN was
                       incorrect).
    ERR.sub.-- MIAC.sub.-- NOT.sub.-- LOCKED
                       secure module is not locked
    ______________________________________


______________________________________
    Read Group Audit Trail (14H)
    ______________________________________
    Transmit data
    14H, Group ID, Group PIN
    Receive data
    CSB = 0 if command successful, appropriate
    error code otherwise
    Output length = # or records for group * 6 if
    successful, 0 otherwise
    Output data = audit trail records for group
    ______________________________________

    ______________________________________
    ERR.sub.-- BAD.sub.-- GROUP.sub.-- ID
                         (Group ID does not
                         exist)
    ERR.sub.-- PAD.sub.-- GROUP.sub.-- PIN
                         (Common PIN was
                         incorrect)
    ERR MIAC.sub.-- NOT.sub.-- LOCKED
                         (The secure module is
                         not locked)
    ______________________________________


______________________________________
    Read Real Time Clock (15H)
    ______________________________________
    Transmit data
    15H, Common PIN
    Receive data
    CSB = 0 if the common PIN matches and
    ERR.sub.-- BAD.sub.-- COMMON.sub.-- PIN otherwise
    Output length = 4
    Output data = 4 most significant bytes of the
    real time clock
    ______________________________________

    ______________________________________
    Read Real Time Clock Adjusted (16H)
    ______________________________________
    Transmit data
    16H, Group ID, Group PIN, ID of offset object
    Receive data
    CSB = 0 if successful, appropriate error code
    otherwise
    Output length = 4 if successful, 0 otherwise
    Output data = Real time clock + clock offset ID
    ______________________________________

    ______________________________________
    ERR.sub.-- BAD.sub.-- GROUP.sub.-- PIN
                        (Incorrect group PIN)
    ERR.sub.-- BAD.sub.-- GROUP.sub.-- ID
                        (Specified group does
                        not exist)
    ERR.sub.-- BAD OBJECT.sub.-- TYPE
                        (Object ID is not a
                        clock offset)
    ______________________________________


______________________________________
    Get Random Data (17H)
    ______________________________________
    Transmit data
    17H, Length (L)
    Receive data
    CSB = 0 if successful, appropriate error code
    otherwise
    Output length = L if successful, 0 otherwise
    Output data = L bytes of random data if
    successful
    ______________________________________

    ______________________________________
    ERR.sub.-- BAD.sub.-- SIZE
                      (Requested number of bytes
                      > 128)
    ______________________________________


______________________________________
    Get Firmware Version ID (18H)
    ______________________________________
    Transmit data
    18H
    Receive data
    CSB = 0
    Output length = Length of firmware version ID
    string
    Output data = Firmware version ID string
    ______________________________________

    ______________________________________
    Get Free RAM (19H)
    ______________________________________
    Transmit data
    19H
    Receive data
    CSB = 0
    Output length = 2
    Output data = 2 byte value containing the
    amount of free RAM
    ______________________________________

    ______________________________________
    Change Group Name (1AH)
    ______________________________________
    Transmit data
    1AH, Group ID, Group PIN, New Group name
    Receive data
    CSB = 0 if successful or an appropriate error
    code otherwise
    Output 1ength = 0
    Output data = 0
    ______________________________________

    ______________________________________
    ERR.sub.-- BAD.sub.-- GROUP.sub.-- PIN
                       (Incorrect group PIN)
    ERR.sub.-- BAD.sub.-- GRQUP.sub.-- ID
                       (Specified group does
                       not exist)
    ERR.sub.-- BAD NAME.sub.-- LENGTH
                       (New group name > 16 bytes)
    ______________________________________

• Inventors
  Curry, Stephen M.; Loomis, Donald W.; Bolan, Michael L.;
• Assignee
  Dallas Semiconductor Corporation (Dallas, TX)
• Published
  Sep-7-1999
• Current US Classes:
  705/39
  705/42
  705/65
  705/66
• Application #
  978798
• International Classes
  H04L 009/00
• Field of Search
  380/23 380/24 380/25 705/39 705/40 705/42
• Examiner
  Tarcza; Thomas H.
• Agent
  Jenkens & Gilchrist
• US Patent References:
  5003594
  5539825
  5546463
  5577121
  5621796
  5642419
  5671280