[0001] The present invention relates generally to value printing systems and, more particularly,
to value printing systems wherein a printer is not dedicated to a metering module.
[0003] Since the issuance of
U.S. Patent No. 1,530,852 to Arthur H. Pitney, the postage meter has evolved from completely mechanical postage meters to meters
that incorporate extensive use of electronic components. Although postage meters have
performed satisfactorily in the past, and continue to perform satisfactorily, with
the advancement in computer controlled digital printing technology, the United States
Postal Service (USPS) and other Posts are considering requirements for new technology
metering devices.
[0004] The USPS is presently considering requirements for two metering device types: closed
systems and open systems. In a closed system, the system functionality is solely dedicated
to metering activity. Examples of closed system metering devices, also referred to
as postage evidencing devices (PEDs), include conventional digital and analog postage
meters wherein a dedicated printer is securely coupled to a metering or accounting
function. In a closed system, since the printer is securely coupled and dedicated
to the meter, printing cannot take place without accounting. Recently, Pitney Bowes
Inc. has introduced the Post Perfect™ meter which is a new closed system metering
device that includes a dedicated digital printer securely coupled to a secure accounting
module.
[0005] In an open system, the printer is not dedicated to the metering activity, freeing
system functionality for multiple and diverse uses in addition to the metering activity.
Examples of open system metering devices include personal computer (PC) based devices
with single/multi-tasking operating systems, multi-user applications and digital printers.
An open system metering device is a PED with a non-dedicated printer that is not securely
coupled to a secure accounting module.
[0006] When a PED prints postage indicia on a mailpiece, the accounting register within
the PED must always reflect that the printing has occurred. Postal authorities generally
require the accounting information to be stored within the postage meter in a secure
manner with security features that prevent unauthorized and unaccounted for postage
printing or changes in the amounts of postal funds stored in the meter. In a closed
system, the meter and printer are integral units, i.e., interlocked in such a manner
as to ensure that the printing of a postage indicia cannot occur without accounting.
[0007] Since an open system PED utilizes a printer that is not used exclusively for printing
proof of postage payment, additional security measures are required to prevent unauthorized
printing evidence of postage payment. Such security measures include cryptographic
evidencing of postage payment by PEDs in the open and closed metering systems. The
postage value for a mail piece may be encrypted together with other data to generate
a digital token. A digital token is encrypted information that authenticates the information
imprinted on a mail piece including postage values.
[0008] Examples of systems for generating and using digital tokens are described in
U.S. Patents Nos. 4,757,537,
4,831,555,
4,775,246,
4,873,645, and
4,725,718.
[0009] These systems employ an encryption algorithm to encrypt selected information to generate
at least one digital token for each mailpiece. The encryption of the information provides
security to prevent altering of the printed information in a manner such that any
misuse of the tokens is detectable by appropriate verification procedures.
[0010] Typical information which may be encrypted as part of a digital token includes origination
postal code, vendor identification, data identifying the PED, piece count, postage
amount, date, and, for an open system, destination postal code. These items of information,
collectively referred to as postal data, when encrypted with a secret key and printed
on a mail piece provide a very high level of security which enables the detection
of any attempted modification of a postal revenue block or a destination postal code.
A postal revenue block is an image printed on a mail piece that includes the digital
token used to provide evidence of postage payment. The Postal data may be printed
both in encrypted and unencrypted form in the postal revenue block. Postal data serves
as an input to a Digital Token Transformation which is a cryptographic transformation
computation that utilizes a secret key to produce digital tokens. Results of the Digital
Token Transformation, i.e., digital tokens, are available only after completion of
the Accounting Process As used herein "digital token" may be an encryption of all
postal data or a subset thereof.
[0011] Digital tokens are utilized in both open and closed metering systems. However, for
open metering systems, the non-dedicated printer may be used to print other information
in addition to the postal revenue block and may be used in activity other than postage
evidencing. In an open system PED, addressee information is included in the postal
data which is used in the generation of the digital tokens. Such use of the addressee
information creates a secure link between the mailpiece and the postal revenue block
and allows unambiguous authentication of the mail piece.
[0012] Preferably, two digital tokens are used to authenticate postal data and postage payment.
The first is produced by a Digital Token Transformation using a secret key held by
the Postal Service and the mailer's PED. The second is produced by a Digital Token
Transformation using a secret key held by the PED vendor and the mailer's PED. The
fact that two independent entities hold separate verification secrets greatly enhances
the security of the system because it provides the Postal Service and the vendor with
independent means to authenticate the postal revenue block, and thus, verify postage
payment. The use of the second Digital Token Transformation using the vendor's secret
key is an optional part of the security which authenticates postage payment by a particular
vendor's device. The use of two digital tokens (postal and vendor) is described in
US Patent No. 5,390,251 and
US Patent No. 5,655,023 (also published as
EP-A-686 94.6), which corresponds to pending
U.S. Patent Application Serial No. 08/242,564, filed May 13, 1994, both assigned to the assignee of the present invention.
[0013] According to a first aspect of the invention, there is provided a transaction evidencing
system, comprising: a personal computer (PCs), an unsecured printer and portable vault
means removably coupled to said PC, and user interface means, said PC including a
processor, memory and storage means, said storage means including at least one non-metering
application program that is selectively run on said PC, said unsecured printer connected
to said PC for printing in accordance with said non-metering application program,
said portable vault means including digital token generation means and transaction
accounting means, the system comprising: vault interface means in said PC for effecting
communications between said portable vault means and said non-metering application
program and for performing metering functions other than metering functions performed
in said portable vault means, said vault interface means comprising: an application
interface module for interfacing with said non-metering application program; a communications
module for communicating with said portable vault means; a storage area in the storage
means;' an indicia image creation and storage module for generating indicia bitmaps
and storing said indicia bitmaps in said storage area; and a transaction capture module
for storing in said storage area transaction records generated in said portable vault
means.
[0014] According to a second aspect of the invention, there is provided a method of implementing
a transaction evidencing system on a personal computer (PC) having a display and an
unsecured printer operatively coupled thereto, comprising the steps of: providing
a portable vault that is removably coupled to the personal computer via a vault interface
means, said portable vault operating as a secure accounting module of the transaction
evidencing system; requesting indicia for a particular document being processed in
an application program running in the PC; securely sending via the vault interface
means from an application interfacing module in the PC, in response to said request
for indicia, a request for at least one digital token to said vault with a predetermined
set of information relating to the particular document; issuing in said vault at least
one digital token and securely sending via the vault interface means the digital token
to an indicia generating module in the PC; storing the digital token and the predetermined
set of information in a transaction record; the vault interface means storing the
transaction record in a storage area of the personal computer; generating an indicia
bitmap in the PC using the transaction record; storing the indicia bitmap in said
storage area; and providing the indicia bitmap to the application program when the
application program is ready to print the indicia.
[0015] According to a third aspect of the invention, there is provided a transaction evidencing
system including a plurality of computer systems operatively configured to form a
network with one of the computer systems functioning as a server and the remaining
computer systems functioning as clients, each of the computer systems including processor,
memory, storage and user interface means, at least some of said storage means including
a plurality of non-metering application programs that are selectively run on said
client computer systems, at least one of said computer systems including an unsecured
printer operatively coupled thereto for printing in accordance with said non-metering
application programs, the system comprising: a portable vault card that is removable
coupled to said server computer system, said vault card including digital token generation
means and transaction accounting means, said server computer system including means
for removable coupling said vault card to said server computer system; vault interface
means for effecting communications between said portable vault means and said non-metering
application program and for performing metering functions other than metering functions
performed in said portable vault means, said vault interface means comprising: an
application interface module in said client computer system for interfacing with said
non-metering application program; a communications module in said server computer
system for communicating with said portable vault means; a storage area in said storage
means; an indicia image creation and storage module in said client computer system
for generating indicia bitmaps and storing said indicia bitmaps in said storage area;
and a transaction capture module for storing in said storage area transaction records
generated in said portable vault means.
[0016] According to a fourth aspect of the invention, there is provided a method of implementing
a transaction evidencing system on a computer network comprising a plurality of computer
systems operatively configured to form the computer network with one of the computer
systems functioning as a server and the remaining computer systems functioning as
clients, the method comprising the steps of: providing a portable vault that is operatively
coupled to the server via a vault interface means, said vault operating as a secure
accounting module of the transaction evidencing system; requesting indicia in one
of the clients for a particular document being processed in a non-metering application
program running in the requesting client; sending the request for indicia from the
requesting client to the server with a predetermined set of information relating to
the particular document; sending, in response to said request for indicia, a request
for at least one digital token from the server via the vault interface means to the
portable vault with the predetermined set of information; issuing in said portable
vault at least one digital token and sending the digital token as part of a transaction
record via the vault interface means to the server; storing the transaction record
in the server; sending from the server to the requesting client the digital token
and a predetermined set of information of the transaction record; the vault interface
means storing the transaction record in the client; generating an indicia bitmap using
the digital token and the predetermined set or information in the client; and providing
the indicia bitmap to the non-metering application program when the non-metering application
program is ready to print the indicia.
[0017] The above and other objects and advantages of the present invention will be apparent
upon consideration of the following detailed description, taken in conjunction with
accompanying drawings, in which like reference characters refer to like parts throughout,
and in which:
Fig. 1 is a block diagram of a PC-based metering system in accordance with the present
invention;
Fig. 2 is a schematic block diagram of the PC-based metering system of Fig. 1 including
a removable vault card and a DLL in the PC;
Fig. 3 is a schematic block diagram of the DLL in the PC-based metering system of
Fig. 1 including interaction with the vault to generate indicia bitmap;
Fig. 4 is a block diagram of the DLL sub-modules in the PC-based metering system of
Fig. 1;
Fig. 5 is a flow diagram of vault mode transitions in the PC-based metering system
of Fig. 1;
Fig. 6 is a flow diagram of power state transitions of the vault card in the PC-based
metering system of Fig. 1;
Fig. 7 is a flow chart of the Secure Communications sub-module in the PC-based metering
system of Fig. 1;
Fig. 8 is a flow chart of the Transaction Capture sub-module in the PC-based metering
system of Fig. 1;
Fig. 9 is an representation of indicia printed by the PC-based metering system of
Fig. 1;
Fig. 10 is a flow chart of the Secure Indicia Image Storage sub-module in the PC-based
metering system of Fig. 1;
Fig. 11 is a diagrammatic representation of a document printed by the PC-based metering
system of Fig. 1 with indicia printed thereon; and
Fig. 12 is a diagrammatic representation of a three windowed envelope in which the
document of Fig. 11 is inserted with the indicia showing through one of the windows.
Fig. 13 is a block diagram of a PC-Network metering system in accordance with the
present invention;
Fig. 14 is a schematic block diagram of the PC-Network metering system of Fig. 13
including a removable vault card in a server PC and a DLL in each of the PC's;
Fig. 15 is a schematic block diagram of the client and server PC's in the PC-Network
metering system of Fig. 13 including interaction with the vault to generate indicia
bitmap;
Fig. 16 is a flow chart of the client requesting an indicia in the PC-Network metering
system of Fig. 13; and
Fig. 17 is a flow diagram of the server responding to a request for an indicia in
the PC-Network metering system of Fig. 13.
[0018] In the system hereinafter described, some of the functionality typically performed
in the vault of a conventional postage meter has been removed from the vault of a
PC-based open metering system and is performed in the PC. It has been discovered that
this transfer of functionality from the vault to the PC does not effect the security
of the meter because the security of the PC-based open metering system is in the information
being processed not in the meter itself.
[0019] Thus, the present system provides a PC-based open metering system that comprises
a PC, special Windows-based software, a printer and a plug-in peripheral as a vault
to store postage funds. The PC meter uses a personal computer and its non-secure and
non-dedicated printer to print postage on envelopes and labels at the same time it
prints a recipient address.
[0020] Thus, a PC based open meter system is provided, which consists of a personal computer
(PC), a digital printer, a removable electronic vault, an optional modem for funds
recharge (debit or credit), a PC software module in the form of a Dynamic Link Library
(DLL) and a user interface module. The vault is a secure encryption device for digital
token generation, funds management and traditional accounting functions. The DLL module
performs all communications with the vault, and provides an open interface to Windows-based
applications. Secure communication between the DLL and the vault is desired but is
not necessary for system security. The DLL module obtains from the vaults transaction
records comprising digital tokens issued by the vault and associated postal data and
generates an electronic indicia image. The usage of postal fund and the transaction
record are stored in the vault. Another copy of the usage of postal funds and the
transaction record may be stored on the PC's hard drive as backup. The user interface
module obtains the electronic indicia image from the DLL module for printing the postal
revenue block on a document, such as an envelope. The user interface also communicates
with the vault via the DLL for remote refills and for performing administrative functions.
[0021] The present system provides open system metering that includes security to prevent
tampering and false evidence of postage payment as well as the ability to do batch
processing of envelopes, review of indicia and addressing on envelope before printing.
[0022] As described below in more detail, the transaction evidencing system includes a personal
computer (PC) comprising a conventional processor, memory and hard drive, with a plurality
of non-metering application programs that selectively run on the PC. An unsecured
printer is operatively coupled to the PC for printing in accordance with the non-metering
application programs. A portable vault card that is removably coupled to the PC is
programmed to generate tokens and perform transaction accounting. An application interface
module in the PC, which interfaces with the non-metering application programs, issues
a request for digital tokens in response to requests for indicia from a non-metering
application program. A secure communications module in the PC, which securely communicates
with the vault card when the vault card is coupled to the PC, sends the request for
digital token to the vault card and receives a digital token generated by the vault
card. An indicia bitmap generation module generates an indicia bitmap in the PC from
the digital token and stores it in memory . The indicia bitmap is accessed by the
non-metering application program when a print indicia operation is selected. A transaction
capture module in the PC stores on the hard drive a transaction record corresponding
to each issued digital token and associated postal data. The application interface
module, the secure communications module, the indicia bitmap generation module and
the transaction capture module are part of a dynamic link library module in the PC.
[0023] In describing the present system, reference is made to the drawings, wherein there
is seen in Figs. 1 and 2 an open system PC-based postage meter, also referred to herein
as a PC meter system, generally referred to as 10, comprising a conventional personal
computer configured to operate as a host to a removable metering device or electronic
vault, generally referred to as 20, in which postage funds are stored. PC meter system
10 uses the personal computer and its printer to print postage on envelopes at the
same time it prints a recipient's address or to print labels for pre-addressed return
envelopes or large mailpieces. It will be understood that although the preferred embodiment
of the present invention is described as a postage metering system, the present invention
is applicable to any value metering system that includes transaction evidencing.
[0024] As used herein, the term personal computer is used generically and refers to present
and future microprocessing systems with at least one processor operatively coupled
to user interface means, such as a display and keyboard, and storage media. The personal
computer may be a workstation that is accessible by more than one user.
[0025] The PC-based postage meter 10 includes a personal computer (PC) 12, a display 14,
a keyboard 16, and an unsecured digital printer 18, preferably a laser or ink-jet
printer. PC 12 includes a conventional processor 22, such as the 80486 and Pentium
processors manufactured by Intel, and conventional hard drive 24, floppy drive(s)
26, and memory 28. Electronic vault 20, which is housed in a removable card, such
as PCMCIA card, is a secure encryption device for postage funds management, digital
token generation and traditional accounting functions. PC meter system 10 may also
include an optional modem 29 which is located preferably in PC 12. Modem 29 may be
used for communicating with a Postal Service or a postal authenticating vendor for
recharging funds (debit or credit). A description of such communication by modem is
described in
U.S. Patent No. 4,831,555, incorporated herein by reference. In an alternate embodiment the modem may be located
in PCMCIA card.
[0026] PC meter system 10 further includes a Windows-based PC software module 34 (Figs.
3 and 4) that is accessible from conventional Windows-based word processing, database
and spreadsheet application programs 36. PC software module 34 includes a vault dynamic
link library (DLL) 40, a user interface module 42, (Fig. 2) and a plurality of sub-modules
that control the metering functions. The DLL is an application programming interface
(API) that is used by in Windows-based programs. It will be understood that the present
invention is suitable for use with an API corresponding to other than Windows-based
programs.
[0027] DLL module 40 securely communicates with vault 20 and provides an open interface
to Microsoft Windows-based application programs 36 through user interface module 42.
DLL module 40 also securely stores an indicia image and a copy of the usage of postal
funds of the vault. User interface module 42 provides application programs 36 access
to an electronic indicia image from DLL module 40 for printing the postal revenue
block on a document, such as an envelope or label. User interface module 42 also provides
application programs the capability to initiate remote refills and to perform administrative
functions.
[0028] Thus, PC-based meter system 10 operates as a conventional personal computer with
attached printer that becomes a postage meter upon user request. Printer 18 prints
all documents normally printed by a personal computer, including printing letters
and addressing envelopes, and in accordance with the present invention, prints postage
indicia.
[0029] A description of the key components of PC-based meter system 10 are described below
followed by a description of the preferred operation of PC-based meter system 10.
A description of the digital token generation process is disclosed in co-pending European
Patent Publication Nos.
0780804,
0780806 and
0782109, which are incorporated herein in their entirety by reference.
The Vault
[0030] In the preferred embodiment of the present invention, the vault is housed in a PCMCIA
I/O device, or card, which is accessed through a PCMCIA controller 32 in PC 12. A
PCMCIA card is a credit card size peripheral or adapter that conforms to the standard
specification of the Personal Computer Memory Card International Association.
[0031] Referring now to Figs. 2 and 3, the PCMCIA card includes a microprocessor 44, non-volatile
memory (NVM) 46, clock 48, an encryption module 50 and an accounting module 52. The
encryption module 50 may implement the NBS Data Encryption Standard (DES) or another
suitable encryption scheme. In the preferred embodiment, encryption module 50 is a
software module. It will be understood that encryption module 50 could also be a separate
device, such as a separate chip connected to microprocessor 44. Accounting module
52 may be EEPROM that incorporates ascending and descending registers as well as postal
data, such as origination ZIP Code, vendor identification, data identifying the PC-based
postage meter 10, sequential piece count of the postal revenue block generated by
the PC-based postage meter 10, postage amount and the date of submission to the Postal
Service. As is known, an ascending register in a metering unit records the amount
of postage that has been dispensed, i.e., issued by the vault, in all transactions
and the descending register records the value, i.e., amount of postage, remaining
in the metering unit, which value decreases as postage is issued.
[0032] The hardware design of the vault includes an interface 56 that communicates with
the host processor 22 through PCMCIA controller 32. Preferably, for added physical
security, the components of vault 20 that perform the encryption and store the encryption
keys (microprocessor 44, ROM 47 and NVM 46) are packaged in the same integrated circuit
device/chip that is manufactured to be tamper proof. Such packaging ensures that the
contents of NVM 46 may be read only by the encryption processor and are not accessible
outside of the integrated circuit device.
Alternatively, the entire card could be manufactured to be tamper proof.
[0033] In accordance with the present invention, the open system vault 20 is strictly a
slave device to PC 12. Host processor 22 generates a command and vault 20 replies
with a response. The vault 20 does not generate unsolicited messages. Thus, PC 12
requests vault status whenever any transaction is initiated.
[0034] Referring now to Fig. 5, vault 20 has four security access levels: normal mode 60,
service mode 62, privileged mode 64 and manufacturing mode 66. In normal mode 60,
commands available to users are processed. In service mode 62, normal mode commands
and service related commands are processed. In privilege mode 64, all commands except
direct access to NVM are processed. In manufacturing mode 66, all commands are processed.
An access level is assigned to every command that is processed by the vault. Passwords
are assigned to the various access levels. For example, to enter service mode 62 from
the normal mode 60, a service password is required. Another password is required to
enter privileged mode 64. Thus, two passwords, service and privileged, must be entered
to access privileged mode 64. Privileged mode 64 cannot be accessed from normal mode
60 or manufacturing mode 66.
[0035] When a 'blank' vault is manufactured, a manufacturing vendor puts vault 20 in manufacturing
mode 66 to program the NVM 46 of PCMCIA card. NVM 46 is programmed with encryption,
accounting, funds management and other vault software modules. Then the vendor locks
a serial number in NVM 46, prohibiting any unauthorized access to NVM 46, before delivering
PCMCIA card to a user. The vendor programs vault 20 to default to normal mode 60 whenever
power is applied. A manufacturing mode password is required, i.e. vault 20 must be
in manufacturing mode, to unlock the serial number in vault 20.
Commands From The PC To Control The Vault Power
[0036] PCMCIA card does not include a self contained power source. Power to PCMCIA card
is controlled by PC 12 in a conventional manner. When a user inserts vault 20 into
PCMCIA controller 32 of PC 12, PC 12 software is in full control of electric power
to vault 20. Microprocessor 44 in PCMCIA card is always in one of the four states:
power removed 70, execution 72, idle 74, or power-down 76. Microprocessor 44 enters
the execution state 72 each time it performs a task specified in a command from PC
12. Microprocessor 44 enters the idle state 74 after performing such task. Microprocessor
44 enters the power-down 76 if the system remains idle longer than the user specified
idle time. To exit power-down state 76, an external signal from PC 12 wakes up microprocessor
44. Microprocessor 44 is in the power removed state 70 whenever PCMCIA card is removed
from PCMCIA controller 32 or whenever PCMCIA controller 32 disables power to PCMCIA
card. Figure 6 shows the state transitions for power controls.
[0037] Status messages communicate the status of vault 20 to PC 12. The status messages
also serve as acknowledgment or failure to acknowledge a given command by PC 12.
Dynamic Link Library Control of the Vault
[0038] In accordance with the present invention, the functionality of DLL 40 is a key component
of PC-base meter 10. DLL 40 includes both executable code and data storage area 41
that is resident in hard drive 24 of PC 12. In a Windows environment, a vast majority
of applications programs 36, such as word processing and spreadsheet programs, communicate
with one another using one or more dynamic link libraries. The present invention encapsulates
all the processes involved in metering, and provides an open interface to vault 20
from all Windows-based applications capable of using a dynamic link library. In accordance
with the present invention, any application program 36 can communicate with vault
microprocessor 44 in PCMCIA card through DLL 40.
[0039] In accordance with the present invention, DLL 40 includes the following software
sub-modules: secure communications 80, transaction capture 82, secure indicia image
creation and storage 84, and application interface module 86.
Secure Communications
[0040] Since vault 20 is not physically secured to PC 12, it would be possible for a user
to replace one vault 20 attached to PC 12 with another vault 20 while a vault transaction
is in process. The Secure Communications sub-module 80 prevents this from happening
by maintaining secure communication between DLL 40 and vault 20. Referring now to
Fig. 7, the Secure Communications sub-module 80 identifies a specific vault 20 when
it opens a communication session through PCMCIA controller 32, and maintains communication
data integrity with the specific vault during the entire communication session. When
a communication session is initiated DLL 40 and vault 20 negotiate a session key at
step 100. All the messages thereafter are encoded/decoded using the session key which
is used for only the one particular communication session. Whenever the session key
changes during the communication session, the communication session terminates and
an error message is sent to the user at step 106. The use of session keys is described
in
Applied Cryptography by Bruce Schneier, published by John Wiley and Sons, Inc., 1994. Thus, the session key not only provides secure encrypted communication between DLL
40 and vault 20, but also prevents another vault (PCMCIA card) from replacing the
vault 20 that began a communication session, because the other vault does not have
the session key negotiated at the beginning of the communication session. Secure Communications
sub-module 80 also controls secure communications with the postal data center, for
example, during refills of the accounting registers in vault 20.
Transaction Captures
[0041] Conventional postage meters store transactions in the meter. In accordance with the
present invention, Transaction Capture sub-module 82 captures each transaction record
received from vault 20 and records the transaction record in DLL 40 and in DLL storage
area 41 on hard drive 24. If there is ample room on hard drive 24, such transaction
captures can be stored for a plurality of different vaults. Referring now to Fig.
8, from the moment that a communication session is established, Transaction Capture
sub-module 82 monitors message traffic at step 120, selectively captures each transaction
record for token generations and refills, and stores such transaction records in DLL
40 at step 124 and in an invisible and write-protected file 83 in DLL storage area
41 at step 126. The information stored for each transaction record includes, for example,
vault serial number, date, piece count, postage, postal funds available (descending
register), tokens, destination postal code and the block check character. A predetermined
number of the most recent records initiated by PC 12 are stored in file 83 which is
an indexed historical file. In the preferred embodiment, file 83 is indexed according
to piece count but may be searched according to addressee information. File 83 represents
the mirror image of vault 20 at the time of the transaction except for the encryption
keys and configuration parameters. Storing transaction records on hard drive 24 provides
backup capability which is described below.
Indicia Image Creation and Storage
[0042] In a closed metering system, such as conventional postage meters, the indicia is
secure because the indicia printer is dedicated to the meter activity and is physically
secured to the accounting portion of the meter, typically in a tamper-proof manner.
In an open metering system, such as the present invention, such physical security
is not present.
[0043] In accordance with the present invention, the entire fixed graphics image 90 of the
indicia 92, shown in Fig. 9 is stored as compressed data 94 in DLL storage area 41.
Postal data information, including piece count 93a, vendor ID 93b, postage amount
93c, serial number 93d, date 93e and origination ZIP 93f and tokens 93g are combined
with the fixed graphics image 90 by Indicia Image Creation Module 84.
[0044] Referring now to Fig. 10, when a request for indicia is made from an application
program in PC 12 at step 142, Indicia Image Creation Module 84 checks for a digital
token from vault 20 at step 144, and at step 146 generates a bit-mapped indicia image
96 by expanding the compressed fixed graphics image data 94 at step 148 and combining
at step 150 the indicia's fixed graphics image 90 with some or all of the postal data
information and tokens received from vault 20. At step 152, the indicia image is stored
in DLL 40 for printing. Sub-module 84 sends to the requesting application program
36 in PC 12 the created bit-mapped indicia image 96 that is ready for printing, and
then stores a transaction record comprising the digital tokens and associated postal
data in DLL storage area 41.
[0045] Thus, the bit-mapped indicia image 96 is stored in DLL 40 which can only be accessed
by executable code in DLL 40. Furthermore, only the executable code of DLL 40 can
access the fixed graphics image 90 of the indicia to generate bit-mapped indicia image
96. This prevents accidental modification of the indicia because it would be very
difficult for a normal user to access, intentionally or otherwise, the fixed graphics
image 90 of the indicia and the bit-mapped indicia image 96.
Application Interface
[0046] The Application Interface sub-module 86 provides the following services when requested
by an application program 36 in PC 12. Application program 36 accepts user data through
user interface module 42 and prints indicia on an envelope or on a label. In the preferred
embodiment of the present invention, such application program 36 would be an off-the-shelf
software module, such as a word processor or spreadsheet, that can access DLL 40.
In an alternate embodiment application program 36 could be a software module dedicated
solely to accept user data and print indicia on an envelope or on a label. Application
Interface sub-module 86 provides the destination ZIP data and associated postal data
needed to create the indicia. Application Interface sub-module 86 requests available
postage from vault 20 and reports the available postage to the requesting application
program 36.
[0047] When vault 20 is refilled with postage funds from the data center, Application Interface
sub-module 86 requests from vault 20 the access code required for refills and reports
the access code received to the Secure Communications sub-module 80 which initiates
communications with the data center. Application Interface sub-module 86 initiates
the refill and provides the amount and combination to vault 20. DLL 40 reports the
result to the requesting application program 36 which acknowledges the refill to the
user.
[0048] Application Interface sub-module 86 processes a request for indicia received from
application program 36 and forwards the request to Indicia Image Creation and Storage
sub-module 84. Application Interface sub-module 86 provides postal data, including
date, postage, and a destination postal code, such as an 11 digit ZIP code, to Indicia
Image Creation and Storage sub-module 84 which then generates a bit-mapped indicia
image 96. Application Interface sub-module 86 reports to application program 36 that
the bit-mapped indicia image 96 is ready for printing.
Backup On Hard Drive
[0049] Vault 20 must be a secure device because it contains the accounting information of
the amount of postage remaining in the vault and the postage printed. However, the
very nature of the security makes it hard to recover postal funds in the event a malfunction
occurs and the vault cannot be accessed by normal operation. The present invention
enhances the reliability of a PC meter system by using the hard disk of the user PC
to backup the accounting information of the vault. As previously described, the transaction
capture sub-module 82 stores transaction files as backup files on hard drive 24. This
provides a benefit that certain functions, such as account reconciliation, can be
performed even when vault 20 malfunctions. Such backup is unavailable in conventional
postage meters.
[0050] For further security, the backup transaction files can be encrypted before being
stored on hard drive 24 to prevent tampering. The number of transactions that are
maintained on hard drive 24 is limited only by the available storage space on hard
drive 24. Preferably, at least all transactions since the last refill would be maintained
as backup.
[0051] A detailed description of recovery from vault malfunction is disclosed in co-pending
European Patent Publication No.
0780808, which is incorporated herein in its entirety by reference.
Operation of the PC Meter
[0052] Generally, the first action by a user after powering up a conventional meter is setting
the time and date of the meter. Setting the date is necessary to generate derived
keys which are used to generate the digital tokens. (Some recent meters have a real
time clock internal to the meter in which case the time and date need only be set
once.) The present system spares the user from having to set the vault date.
[0053] As previously described, vault 20 does not have an independent power source and therefore
cannot have a continuous running real-time clock. The date must be set every time
the vault is powered-up. Power is applied to vault 20 only when it is plugged into
PC 12. Thus, the date would normally be entered by the user through PC 12 each time
vault 20 is plugged into PCMCIA controller 32. Since the PC to which the vault is
connected has a real-time clock, the date setting process may be automated and made
transparent to the user. In accordance with the present invention, the time and date
set in PC 12 is sent to vault 20 each time power is initially applied to vault 20.
The vault date is used by DLL 40 to generate the indicia. The vault date may be changed
at any time by the user to facilitate post-dating of mail.
[0054] Upon application of power to vault 20 by PCMCIA controller 32, the date of PC 12
is obtained through user interface 42. The date is then translated into the correct
format and sent to vault 20 which then sets its date, calculates its date dependent
token keys and returns its status and the token keys to PC 12. Additionally, a default
postage amount (e.g. First Class Postage) may be set in a similar manner. This method
enables PC meter system 10 immediately when vault 20 is plugged into PC 12 without
the user having to manually set parameters. The user may change the vault date (in
order to post date mail) or the default postage amount at any time.
[0055] In an alternate embodiment, PCMCIA card has its own internal clock that is automatically
set with the time and date in PC 12 each time PCMCIA card is inserted into PCMCIA
controller 32.
[0056] In the preferred operation, a user of an application program 36, such as a word processor,
highlights a recipient address from a letter or mailing list displayed on display
14. The user requests the printing of an envelope with indicia. A dialog box appears
on display 14 indicating the default postage amount which the user may accept or modify.
When the postage amount is accepted, the entire envelope is previewed with all addressing,
bar-coding and indicia shown on the envelope. At this point the user can print the
envelope as shown or correct any errors that are seen in the preview.
[0057] From the display 14 and keyboard 16, the user can change postage amount, date and
address information. The user can also select and customize a return address, slogan,
logo and greeting that may be printed with the indicia. The present invention also
provides from the application program 36 the ability for a user to check funds available
in vault 20 and to initiate 36 the automatic refilling of the PC meter through modem
29. PC meter system 10 also includes the capability of interfacing with optional software,
such as postal rate calculation and address hygiene, that improves the performance
of PC meter system 10.
[0058] PC meter system 10 provides capabilities that are not available with conventional
postage meters. For example, a user can scan in addressee information; generate indicia
for a batch of envelopes before printing any of the envelopes; observe an image of
the envelope to be printed, including addressee information and indicia, before printing
the envelope; and customize slogans, logos and greetings to be printed with the indicia
on the envelope.
[0059] Most personal bills received in the home today come with self-addressed, reply envelopes.
A user may desire to use PC meter system 10 to apply open system indicia to the self-addressed,
reply envelopes. Since the open system indicia includes addressee information, the
user can type such addressee information into PC 12 before requesting indicia. This
task can be simplified by using a conventional optical scanner connected to PC 12
for scanning in the unique addressee information printed on the reply envelope. PC
meter system 10 uses such unique addressee information to generate tokens for the
indicia. PC meter system 10 then prints the indicia to a label printer or label printed
on a conventional printer, or prints a completely new envelope with the scanned address.
The label with indicia printed on it, could then be applied to the self-addressed,
reply envelope. Using a scanner in this manner eliminates the need for a user to manually
enter information from the self addressed envelope which is a slower method that has
a higher potential for error. Such error in entering addressee information could result
in indicia that fails open system verification by the Post Office. It will be understood
that the scanner can also be used for scanning in addresses from a printed mailing
list. Finally, if the envelope was prepared previously or at another PC, the addressee
information can be scanned as described above.
[0060] As previously described, in PC meter system 10 the printer is not dedicated to the
metering function and the indicia are stored in PC 12 before printing. Thus, indicia
can be generated individually or for a batch of addressees and then printed at a later
time at the user's discretion. Such delayed printing and batch processing is described
in more detail in co-pending European Patent Publication No.
0782112, which is incorporated herein in its entirety by reference.
[0061] As with any document prepared in a Windowa-based PC system, a user may observe, through
the application program 36 in which an envelope was created, an image of a fully prepared
envelope or batch of envelopes to be printed, including addressee information and
indicia, before printing any of the envelopes. In addition, PC meter system 10 provides
a user with the ability to customize return addresses, slogans, logos and greetings
that are to be printed with the indicia on the envelope.
[0062] In an alternate embodiment of PC meter 10, the electronic vault is in an IC token,
such as manufactured by CDSM of Phoenix, Arizona, that is inserted into a token receptacle
of a PCMCIA card and programmed to operate as the vault in a similar manner as described
for PCMCIA card. In another alternate embodiment, the electronic vault is in a smart
diskette, such as manufactured by SmartDisc Security Corp. of Naples, Florida, that
is programmed to operate in a similar manner as described for PCMCIA card.
[0063] In another alternate embodiment of PC meter 10, the electronic vault is a tamper
proof, hardware peripheral, such as a dongle, that is attached to a serial, parallel
or SCSI port of the PC. In yet another alternate embodiment, not shown, the vault
is internal to PC-12, for example a separate chip within PC-12 that functions in a
manner similar to vault 20.
[0064] Finally, the present invention provides an alternate method of postage evidencing
which eliminates the need to print anything on an envelope. PC meter system 12 can
print an open system indicia on a letter itself as shown in Fig. 11. The format of
such a letter 170 includes a return address 172 in the upper left corner, an open
system indicia 174 in the upper right corner, a destination address 176 below the
return address, and the body of the letter 178 below the destination address. Using
a windowed envelope 180 with three windows, as shown in Fig. 12, the return address
is visible through an upper left corner window 182, the destination address is visible
through a lower left window 184, and the indicia is visible through an upper right
window 186. It will be understood that the present invention can be used to print
indicia anywhere on the letter or document being printed to accommodate alternately
configured windowed envelopes, such as a single, large windowed envelope. The present
invention is also suitable for printing indicia on a one piece mailer. The foregoing
method of mailing a letter with indicia printed directly on the letter and visible
through a window of the envelope eliminates a finishing step in production mail relating
to matching a separately printed envelope with its corresponding letter. It has been
a challenge to insert a letter to the corresponding envelope when the letters and
envelopes are printed separately. Thus the present invention simplifies and eliminates
errors in the mail preparation process.
[0065] In yet another alternate embodiment of a PC-based metering system, PC 12 is a host
computer in a network serving a plurality of users in which the vault is active within
the host computer and requests for indicia originate from and printing of indicia
occur at a local PC.
[0066] In Figs. 13-15, an open system network-based postage meter, also referred to herein
as a network-based metering system, generally referred to as 1, comprising a server
10 and a plurality of clients 11. Server 10 is configured to operate as a host to
a removable metering device or electronic vault, generally referred to as 20, in which
postage funds are stored.
[0067] In the following description and in the drawings, components common to server 10
and clients 11 are distinguished, when necessary, by referring to the client components
with a prime designation. When the component functionality is common to both server
and client PC's the description does not distinguish between server and client.
[0068] The server 10 and clients 11 include the following common components: a personal
computer (PC) 12, a display 14, a keyboard 16, and an unsecured digital printer 18,
preferably a laser or ink-jet printer. Each PC 12 includes a conventional processor
22, such as the 80486 and Pentium processors manufactured by Intel, and conventional
hard drive 24, floppy drive(s) 26, and memory 28. Server 10 includes an electronic
vault 20, which is housed in a removable card, such as PCMCIA card. Electronic vault
20 is a secure encryption device for postage funds management, digital token generation
and traditional accounting functions. Server 10 may also include an optional modem
29 which is located in PC 12, preferably, or in card. Modem 29 may be used for communicating
with a Postal Service or a postal authenticating vendor for recharging funds (debit
or credit). A description of such communication by modem is described in
U.S. Patent No. 4,831,555, incorporated herein by reference. In an alternate embodiment the modem may be located
in PCMCIA card.
[0069] Each of the PC's 12 includes a Windows-based PC software module 34 (Fig. 4) that
is accessible from conventional Windows-based word processing, database and spreadsheet
application programs 36. PC software module 34 includes a dynamic link library (DLL)
40, a user interface module 42, and a plurality of sub-modules that control the metering
functions. In server 10, DLL module 40 securely communicates with vault 20 and clients
11. In client 11, DLL module 40' securely communicates with server 10. DLL 40, in
server 10 and client 11, provides an open interface to Microsoft Windows-based application
programs 36 through user interface module 42. DLL module 40 also securely stores transaction
records reflecting the usage of postal funds of vault 20. User interface module 42
provides application programs 36 access to an electronic indicia image from DLL module
40 for printing the postal revenue block on a document, such as an envelope or label.
User interface module 42 also provides application programs the capability to initiate
remote refills and to perform administrative functions.
[0070] Thus, network-based metering system 1 operates as a conventional network, except
that a client or network printer prints postage upon user request. Printers 18 print
all documents normally printed by a personal computer, including printing letters
and addressing envelopes, and in accordance with the present invention, prints postage
indicia. Network-based meter system 1 uses server 10 to issue postage and one of the
printers to print the issued postage on envelopes at the same time it prints a recipient's
address or to print labels for pre-addressed return envelopes or large mailpieces.
It will be understood that although the preferred embodiment of the present invention
is described as a postage metering system, the present invention is applicable to
any value metering system that includes transaction evidencing. It will also be understood
that the present invention could also be used in a network in which a network printer,
such as the server printer, is used to print envelopes with indicia, when local printers
are not available to some or all of the client PC's.
[0071] The PCMCIA card includes a microprocessor 44, non-volatile memory (NVM) 46, clock
48, an encryption module 50 and an accounting module 52. The encryption module 50
may implement the NBS Data Encryption Standard (DES) or another suitable encryption
scheme. In the preferred embodiment, encryption module 50 is a software module. It
will be understood that encryption module 50 could also be a separate device, such
as a separate chip connected to microprocessor 44. Accounting module 52 may be EEPROM
that incorporates ascending and descending registers as well as postal data, such
as origination ZIP Code, vendor identification, data identifying server PC 12, sequential
piece count of the postal revenue block generated by the network-based metering system
1, postage amount and the date of submission to the Postal Service. As is known, an
ascending register in a metering unit records the amount of postage that has been
dispensed, i.e., issued by the vault, in all transactions and the descending register
records the value, i.e., amount of postage remaining in the vault, which value decreases
as postage is issued.
[0072] The hardware design of the vault includes an interface 56 that, communicates with
the server host processor 22 through PCMCIA controller 32. Preferably, for added physical
security, the components of vault 20 that perform the encryption and store the encryption
keys (microprocessor 44, ROM 47 and NVM 46) are packaged in the same integrated circuit
device/chip that is manufactured to be tamper proof. Such packaging ensures that the
contents of NVM 46 may be read only by the encryption processor and are not accessible
outside of the integrated circuit device. Alternatively, the entire card could be
manufactured to be tamper proof.
[0073] A description of the key components of network-based metering system 1 are described
below followed by a description of the preferred operation of network-based metering
system 1.
Dynamic Link Library Control of the Vault and Network Communications
[0074] In accordance with the present invention, the functionality of DLL's 40 and 40' in
server and client PC's, respectively, is a key component of network-based metering
1. DLL 40 includes both executable code and data storage area 41 that is resident
in hard drive 24 of PC 12. In a Windows environment, a vast majority of applications
programs 36, such as word processing and spreadsheet programs, communicate with one
another using one or more dynamic link libraries. The present invention encapsulates
all the processes involved in metering, and provides an open interface to vault 20
from all Windows-based applications capable of using a dynamic link library. In accordance
with the present invention, any client application program 36' can communicate with
vault microprocessor 44 in PCMCIA card through DLL 40' and server PC 12.
[0075] In accordance with the present invention, DLL 40 includes the following software
sub-modules: secure communications 80, transaction captures 82, secure indicia image
creation and storage 84, and application interface module 86.
Secure Communications
[0076] Since vault 20 is not physically secured to server PC 12, it may be possible for
that one vault 20 attached to server PC 12 is replaced with another vault 20 while
a vault transaction is in process. The Secure Communications sub-module 80 prevents
this from happening by maintaining secure communication between server DLL 40 and
vault 20. Secure Communications sub-module 80 in server 11 identifies a specific vault
20 when it opens a communication session through PCMCIA controller 32, and maintains
communication data integrity with the specific vault during the entire communication
session. Similarly, when a communication session is initiated between client 11 and
a server 10, Secure Communications sub-module 80 maintains communication data integrity
between the client 11 and server 10. Referring now to Fig. 7, when a communication
session is initiated, between server DLL 40 and vault 20, or between client 11 and
server 10, a session key is negotiated at step 100. All the messages thereafter are
encoded/decoded using the session key which is used for only the one particular communication
session. Whenever the session key changes during the communication session, the communication
session terminates and an error message is sent to the user at step 106. The use of
session keys is described in
Applied Cryptography by Bruce Schneider, published by John Wiley and Sons, Inc., 1994. Thus, the session key not only provides secure encrypted communication during a
token request and issue, but also prevents another vault (PCMCIA card) from replacing
the vault 20 that began a communication session, because the other vault does not
have the session key negotiated at the beginning of the communication session. The
secure communications between server 10 and client 11 ensures that only the client
requesting a token can receive the token. Secure Communications sub-module 80 in server
11 also controls secure communications with the postal data center, for example, during
refills of the accounting registers in vault 20.
Transaction Captures
[0077] Conventional postage meters store transactions in the meter. In accordance with the
present invention, Transaction Capture sub-module 82 in server 10 captures each transaction
record received from vault 20 and records the transaction record in DLL 40 and in
DLL storage area 41 on hard drive 24. When server 10 sends the transaction record
to client 11, Transaction Capture sub-module 82' in client 11 captures the transaction
record and records the transaction record in DLL 40' and in DLL storage area 41' on
hard drive 24'. Referring now to Fig. 6, from the moment that a communication session
is established, between server DLL 40 and vault 20, or between client 11 and server
10, respective Transaction Capture sub-modules 82 and 82' monitor message traffic
at step 120, selectively capture each transaction record for token generations and
refills, and store such transaction records in respective DLLs 40 and 40' at step
124 and in an invisible and write-protected files 83 and 83' in DLL storage areas
41 and 41' at step 126. The information stored for each transaction record includes,
for example, vault serial number, date, piece count, postage, postal funds available
(descending register), tokens, destination postal code and the block check character.
A predetermined number of the most recent records initiated can be stored in this
manner by indexing files 83 and 83' accordingly. In the preferred embodiment files
83 and 83' are indexed according to piece count but may searched according to addressee
information. Server file 83 represents the mirror image of vault 20 at the time of
the transaction except for the encryption keys and configuration parameters. Client
file 83' may represent a subset of the image of vault 20 at the time of the transaction
because each client 11 stores transaction records of transactions initiated by such
client. Storing transaction records on hard drive 24 provides backup capability which
is described below.
[0078] A description of a digital token generation process is disclosed for a PC-meter system
in the related European Patent Publication Nos.
0780804,
0780806 and
0782109, which are incorporated herein in their entirety by reference. The digital token
generation process for network-based metering system 1 is the same as described in
the related applications except that a client application program 36' sends a request
for digital token to vault 20 through client DLL 40' and server DLL 40 as shown in
Fig. 3. The generated token is sent to the client DLL 40' through the server DLL 40
for use in generating an indicia. In the present invention, when a request for token
is sent from a client to server 10, all postal information that is needed to calculate
the token as well as parameters identifying the client, such as user ID, password
and client PC identification, must accompany the request since multiple clients may
be requesting tokens simultaneously.
[0079] Referring now to Fig. 16, a request for indicia is made, at step 142, from application
program 36' in client 11 to server 10. At step 144, Secure Communications sub-module
80' in client 11 checks for a response from server 10. When a response is received,
Indicia Image Creation and Storage sub-module 84' checks, at step 146, the response
for postal data, including at least one digital token. If the postal data has not
been sent with the response, at step 148, an error condition is processed that results
in a message to the user. If the response from server 10 included the expected postal
data, at step 150, Indicia Image Creation and Storage sub-module 84' generates a bit-mapped
indicia image 96 by expanding the compressed fixed graphics image data 94, at step
152, and combining, at step 154, the indicia's fixed graphics image 90 with some or
all of the postal data information and tokens received from vault 20. At step 156,
the indicia image is stored in DLL 40' for printing. Sub-module 84' sends to the requesting
application program 36' in client PC 12' the created bit-mapped indicia image 96 that
is ready for printing, and then stores a transaction record comprising the digital
tokens and associated postal data in DLL storage area 41'.
[0080] Thus, the bit-mapped indicia image 96 is stored in DLL 40' which can only be accessed
by executable code in DLL 40'. Furthermore, only the executable code of DLL 40' can
access the fixed graphics image 90 of the indicia to generate bit-mapped indicia image
96. This prevents accidental modification of the indicia because it would be very
difficult for a normal user to access, intentionally or otherwise, the fixed graphics
image 90 of the indicia and the bit-mapped indicia image 96.
[0081] Referring now to Fig. 17, when the request for indicia is made, from application
program 36', Secure Communications sub-module 80 in server 10 checks for the request
from client 11, at step 160. When the request is received, Secure Communications sub-module
80 requests tokens from vault 20, at step 162. At step 164, Secure Communications
sub-module 80 checks for a transaction record, including digital token, from vault
20. If a transaction record is not received in response to the request from server
10, an error is processed, at step 166, resulting in an error message to client 11.
If a transaction record is received, then, at step 168, the transaction record is
stored in DLL 40 and DLL storage area 41. At step 170, Secure Communications sub-module
80 sends the postal data received as in the transaction record, including token and
piece count, to client 11.
[0082] The request for indicia most likely will originate from a client 11 but could originate
from server 10. When server 10 originates a request for indicia server 10 functions
as a PC-based meter.
Application Interface
[0083] This Application Interface sub-module operates as previously described for the basic
PC meter.
[0084] As previously described, the transaction capture sub-modules 82 and 82' store transaction
files as backup files on hard drives 24 and 24'. This provides a benefit that certain
functions, such as account reconciliation, can be performed even when vault 20 malfunctions.
Such backup is unavailable in conventional postage meters.
[0085] For further security, the backup transaction files can be encrypted before being
stored on hard drives 24 and 24' to prevent tampering. The number of transactions
that are maintained on hard drives 24 and 24' is limited only by the available storage
space on the hard drives. Preferably, at least all transactions since the last refill
would be maintained on server 10 as backup.
[0086] In the preferred operation, a user of an application program 36 (running in either
client 11 or server 10), such as a word processor, highlights a recipient address
from a letter or mailing list displayed on display 14. The user requests the printing
of an envelope with indicia. A dialog box appears on display 14 indicating the default
postage amount which the user may accept or modify. When the postage amount accepted,
the entire envelope is previewed with all addressing, bar-coding and indicia shown
on the envelope. At this point the user can print the envelope as shown or correct
any errors that are seen in the preview.
[0087] As previously described, in network-based metering system 1 the printers are not
dedicated to the metering function and the indicia are stored in PC 12 before printing.
Thus, tokens can be generated individually or for a batch of addressees stored in
the requesting client 11 which can later generate an indicia from each of the tokens
and then print the indicia at the user's discretion.
1. A transaction evidencing system (10), comprising:
a personal computer (PC) (12), an unsecured printer (18) and portable vault means
(20) removably coupled to said PC, and user interface means (14,16), said PC including
a processor (22), memory and storage means (24, 28), said storage means including
at least one non-metering application program (36) that is selectively run on said
PC, said unsecured printer (18) connected to said PC (12) for printing in accordance
with said non-metering application program, said portable vault means (20) including
digital token generation means (50) and transaction accounting means, the system comprising:
vault interface means (34) in said PC (12) for effecting communications between said
portable vault means (20) and said non-metering application program and for performing
metering functions other than metering functions performed in said portable vault
means (20), said vault interface means (34) comprising:
an application interface module (86) for interfacing with said non-metering application
program;
a communications module (80) for communicating with said portable vault means (20);
a storage area (41) in the storage means (24);
an indicia image creation and storage module (84) for generating indicia bitmaps and
storing said indicia bitmaps in said storage area (41); and
a transaction capture module (82) for storing in said storage area (41) transaction
records generated in said portable vault means(20).
2. The transaction evidencing system of Claim 1, wherein said portable vault means (20)
comprises a vault card that is removably coupled to said PC (12), said PC including
means for removably coupling said vault card to said PC.
3. The transaction evidencing system of Claim 2, wherein said vault card is a PCMCIA
card (20).
4. The transaction evidencing system of Claim 1, further comprising:
means (82) in said PC for capturing in said storage area a transaction record corresponding
to said digital token, said transaction record including said digital token and said
predetermined information.
5. The transaction evidencing system of Claim 4, wherein said vault interface means comprises
a dynamic link library modules (40) in said PC.
6. The transaction evidencing system of Claim 4, wherein a batch of digital tokens may
be generated before any indicia bitmaps corresponding to said batch of digital tokens
are generated.
7. The transaction evidencing system of Claim 4, further comprising means for encrypting
said transaction record before being captured in said storage area (41).
8. The transaction evidencing system of Claim 4, further comprising means for storing
a plurality of consecutive ones of said transaction records in said storage area (41)
as backup to information stored in said portable vault means (20).
9. The transaction evidencing system of Claim 1, wherein said storage means is a hard
drive (24) of said PC.
10. The transaction evidencing system of Claim 1, wherein said portable vault means (20)
is programmed with a plurality of security access levels including at least a default
mode for normal user access and at least one restricted mode that is accessed by password.
11. The transaction evidencing system of Claim 1, further comprising means coupled to
said PC (12) for scanning addressee information for selection by said non-metering
application programs when requesting indicia.
12. The transaction evidencing system of Claim 1, wherein said vault interface means (34)
is arranged to provide said indicia bitmap to said non-metering application program
for viewing an image of said indicia bitmap on a display coupled to said PC before
printing said indicia bitmap.
13. The transaction evidencing system of Claim 1, wherein said indicia image creation
and storage module (84) is arranged to generate a postage indicia bitmap.
14. The transaction evidencing system of Claim 1, wherein said indicia bitmap generating
means is operable to generate said indicia bitmap by combining indicia graphics stored
in said storage means (24,28) with said digital token and said predetermined information.
15. The transaction evidencing system of Claim 1, wherein said application interface module
(86) is operable to issue a request for at least one digital token in response to
a request for indicia from said non-metering application program, said request for
digital token including predetermined information required by said token generation
means (50), said communications module (80) being operable to send said request for
digital token and said predetermined information to said portable vault means (20)
and to receive from said portable vault means (20) a transaction record including
a digital token generated by said token generation means (50), said indicia image
creation and storage module (84) being operable to generate an indicia bitmap from
said digital token and to store said indicia bit map, said transaction capture module
(82) being operable to store said transaction record, and said application interface
module (86) being operable to provide said indicia bitmap to said non-metering application
program (36).
16. The transaction evidencing system of Claim 15, wherein said communications module
(80) is operable to maintain communication data integrity with said portable vault
means (20) through the use of a session key for each transaction evidencing communication
session relating to a request for and receipt of a digital token.
17. The transaction evidencing system of Claim 16 wherein said communications module (80)
is also operable to control secure communications with a postal data center during
refills of accounting registers in said transaction accounting means of said portable
vault means (20).
18. The transaction evidencing system of Claim 17 wherein said portable vault means (20)
comprises a plurality of portable vault devices, any one of which may be coupled to
said PC (12) for each transaction evidencing communication session, and wherein said
transaction capture module (82) is arranged to monitor communications between each
of said vault devices (20) and said communications module (80) and to store in said
storage means (28) all transaction records and refill accounting information received
by said communications module for each of said vault devices (20), whereby said storage
means (28) stores a backup of information stored in said vault devices (20).
19. A method of implementing a transaction evidencing system (10) on a personal computer
(PC) (12) having a display (14) and an unsecured printer (18) operatively coupled
thereto, comprising the steps of:
providing a portable vault (20) that is removably coupled to the personal computer
(12) via a vault interface means (34), said portable vault (20) operating as a secure
accounting module of the transaction evidencing system (10);
requesting indicia for a particular document being processed in an application program
(36) running in the PC (12);
securely sending via the vault interface means (34) from an application interfacing
module (86) in the PC, in response to said request for indicia, a request for at least
one digital token to said vault (20) with a predetermined set of information relating
to the particular document;
issuing in said vault (20) at least one digital token and securely sending via the
vault interface means (34) the digital token to an indicia generating module (84)
in the PC;
storing the digital token and the predetermined set of information in a transaction
record;
the vault interface means (34) storing the transaction record in a storage area (41)
of the personal computer (12);
generating an indicia bitmap in the PC (12) using the transaction record;
storing the indicia bitmap in said storage area (41); and
providing the indicia bitmap to the application program (36) when the application
program is ready to print the indicia.
20. The method of Claim 19, comprising the further step of:
viewing on a PC display (14) an image of at least a part of the particular document
with the indicia shown thereon before printing the particular document.
21. The method of Claim 19, comprising the further step of:
storing a plurality of transaction records on a hard drive of the PC, each of the
transaction records corresponding to transactions occurring in said portable vault
(20).
22. The method of Claim 19, comprising the further steps of:
providing a dynamic link library (DLL) (41) containing routines for controlling communications
with the portable vault (20), storing transactions, storing indicia bitmaps, and application
interfacing;
loading the DLL into a memory (28) of the PC (12) when an indicia request is made
from the application program (36); and
accessing the DLL from the application program (36).
23. The method of Claim 19, comprising the further steps of:
selecting in the application program (36) recipient address information for in the
application program;
selecting in the application program (36) an amount of postage to be printed;
including the recipient address information and the amount of postage as part of the
predetermined set of information; and
printing said recipient address and said indicia on an envelope.
24. The method of Claim 19, comprising the further steps of:
printing the indicia directly on the document; and
inserting the document into an envelope such that the indicia is visible through a
windowed portion of the envelope.
25. A transaction evidencing system including a plurality of computer systems (12,12')
operatively configured to form a network (1) with one (12) of the computer systems
functioning as a server and the remaining computer systems (12') functioning as clients,
each of the computer systems including processor, memory, storage and user interface
means, at least some of said storage means including a plurality of non-metering application
programs (36') that are selectively run on said client computer systems (12'), at
least one of said computer systems (12') including an unsecured printer (18') operatively
coupled thereto for printing in accordance with said non-metering application programs,
the system comprising:
a portable vault card (20) that is removable coupled to said server computer system
(12), said vault card (20) including digital token generation means (50) and transaction
accounting means (52), said server computer system (12) including means (32) for removable
coupling said vault card (20) to said server computer system (12);
vault interface means (34,40,80,82,84,86) for effecting communications between said
portable vault means (20) and said non-metering application program (36) and for performing
metering functions other than metering functions performed in said portable vault
means (20), said vault interface means comprising:
an application interface module (86) in said client computer system for interfacing
with said non-metering application program;
a communications module (80) in said server computer system (12) for communicating
with said portable vault means (20);
a storage area (41) in said storage means;
an indicia image creation and storage module (84) in said client computer system for
generating indicia bitmaps and storing said indicia bitmaps in said storage area (41);
and
a transaction capture module (82) for storing in said storage area (41) transaction
records generated in said portable vault means (20).
26. The transaction evidencing system of Claim 25, wherein said vault interface means
are part of dynamic link library modules in said computer systems (12, 12').
27. The transaction evidencing system of Claim 25, wherein said vault card is a PCMCIA
card (20).
28. The transaction evidencing system of Claim 25, wherein a batch of digital tokens may
be generated in the vault card (20) and stored in a requesting one of said client
computer systems (12') before any indicia bitmaps corresponding to said batch of digital
tokens are generated.
29. The transaction evidencing system of Claim 25, further comprising means for encrypting
said transaction record before being stored in said storage means (28) of said server
computer system (12).
30. The transaction evidencing system of Claim 25, further comprising means for storing
a plurality of consecutive ones of said transaction records in said storage means
(28) of said server computer system as backup to information stored in said vault
card (20).
31. The transaction evidencing system of Claim 25, wherein said vault interface means
is operable to provide said indicia bitmap to said one of said non-metering application
programs for viewing an image of said indicia bitmap on a display coupled to said
requesting client computer system (12') before printing said indicia bitmap.
32. The transaction evidencing system of Claim 25 wherein said indicia bitmap generating
means is operable to generate a postage indicia bitmap by combining indicia graphics
stored in said storage means of said requesting client computer system with said digital
token and said predetermined information.
33. The transaction evidencing system of Claim 25 wherein said application interface module
(86) is operable to issue a request for at least one digital token in response to
a request for indicia from said non-metering application program (36), said request
for digital token including predetermined information required by said token generation
means, said communications module (80) being operable to send said request for digital
token and said predetermined information to said portable vault means (20) and to
receive from said portable vault means (20) a transaction record including a digital
token generated by said token generation means (50), said indicia image creation and
storage module (84) being operable to generate an indicia bitmap from said digital
token and to store said indicia bit map, said transaction capture module (82) being
operable to store said transaction record, and said application interface module (86)
being operable to provide said indicia bitmap to said non-metering application program
(36).
34. The transaction evidencing system of Claim 25 or 33 wherein said transaction capture
module (82,82') is in each of said server (12) and client computer systems (12').
35. The transaction evidencing system of Claim 25 or 33 wherein said transaction capture
module (82) is in said server computer system (12).
36. A method of implementing a transaction evidencing system on a computer network(1)
comprising a plurality of computer systems (12, 12') operatively configured to form
the computer network with one of the computer systems (12) functioning as a server
and the remaining computer systems functioning as clients (12'), the method comprising
the steps of:
providing a portable vault (20) that is operatively coupled to the server (12), via
a vault interface means (34), said vault operating as a secure accounting module (20)
of the transaction evidencing system;
requesting indicia in one of the clients (12') for a particular document being processed
in a non-metering application program running in the requesting client;
sending the request for indicia from the requesting client (12') to the server (12)
with a predetermined set of information relating to the particular document;
sending, in response to said request for indicia, a request for at least one digital
token from the server (12) via the vault interface means (34) to the portable vault
(20) with the predetermined set of information;
issuing in said portable vault (20) at least one digital token and sending the digital
token as part of a transaction record via the vault interface means (34) to the server
(12);
storing the transaction record in the server (12);
sending from the server (12) to the requesting client (12`) the digital token and
a predetermined set of information of the transaction record;
the vault interface means (34) storing the transaction record in a storage area of
the client (12');
generating an indicia bitmap using the digital token and the predetermined set of
information in the client; and
providing the indicia bitmap to the non-metering application program when the non-metering
application program is ready to print the indicia.
37. The method of Claim 36, comprising the further step of:
viewing on a display (14') coupled to the requesting client computer (12') system
an image of at least a part of the particular document with the indicia shown thereon
before printing the particular document.
38. The method of Claim. 36, comprising the further step of:
storing a plurality of transaction records in a file on a hard drive of the server
(12), and indexing the transaction records according to piece count.
39. The method of Claim 36, comprising the further steps of:
selecting in the non-metering application program (36) recipient address information
for use in the application program;
selecting in the non-metering application program an amount of postage to be printed
on in the application program;
including the recipient address information and the amount of postage as part of the
predetermined set of information; and
printing said recipient address and said indicia on an envelope.
1. Transaktions-beweisendes System (10), mit:
einem Personal-Computer (PC) (12), einem ungesicherten Drucker (18) und einer tragbaren
Tresorvorrichtung (20), die entfernbar mit dem PC gekoppelt ist und einer Benutzerschnittstellenvorrichtung
(14, 16), wobei der PC einen Prozessor (22), einen Speicher und eine Speichervorrichtung
(28) umfasst, wobei die Speichervorrichtung zumindest ein nicht-messendes Anwendungsprogramm
(36) umfasst, das selektiv auf dem PC laufengelassen wird, der ungesicherte Drucker
(18), mit dem PC (12) zum Drucken gemäß dem nicht-messenden Anwendungsprogramm verbunden
ist, die tragbare Tresorvorrichtung (20) eine Digitalzeichenerzeugungsvorrichtung
(50) und eine Transaktions-abrechnende Vorrichtung umfasst, wobei das System umfasst:
eine Tresorschnittstellenvorrichtung (34) in dem PC (12) zum Bewirken von Kommunikationen
zwischen der tragbaren Tresorvorrichtung (20) und dem nicht-messenden Anwendungsprogramm
und zum Durchführen von anderen messenden Funktionen als den messenden Funktionen,
die in der tragbaren Tresorvorrichtung (20) durchgeführt werden, wobei die Tresorschnittstellenvorrichtung
(34) umfasst:
ein Anwendungsschnittstellenmodul (86) zum Bilden einer Schnittstelle mit dem nicht-messenden
Anwendungsprogramm;
ein Kommunikationsmodul (80) zum Kommunizieren mit der tragbaren Tresorvorrichtung
(20);
einen Speicherbereich (41) in der Speichervorrichtung (28);
ein Freimachungsvermerkbilderzeugungs- und Speichermodul (84) zum Erzeugen von FreimachungsvermerkBitmaps
und Speichern der Freimachungsvermerkbitmaps in dem Speicherbereich (41); und
ein Transaktionserfassungsmodul (82) zum Speichern in dem Speicherbereich (41) von
Transaktionssätzen, die in der tragbaren Tresorvorrichtung (20) erzeugt werden.
2. Transaktions-beweisendes System nach Anspruch 1, wobei die tragbare Tresorvorrichtung
(20) eine Tresorkarte umfasst, die entfernbar mit dem PC (12) gekoppelt ist, wobei
der PC eine Vorrichtung zum entfernbaren Koppeln der Tresorkarte mit dem PC umfasst.
3. Transaktions-beweisendes System nach Anspruch 2, wobei die Tresorkarte eine PCMCIA-Karte
(20) ist.
4. Transaktions-beweisendes System nach Anspruch 1, weiter mit:
einer Vorrichtung (82) in dem PC zum Erfassen in dem Speicherbereich eines Transaktionssatzes
entsprechend dem Digitalzeichen, wobei der Transaktionssatz das Digitalzeichen und
die vorbestimmte Information umfasst.
5. Transaktions-beweisendes System nach Anspruch 4, wobei die Tresorschnittstellenvorrichtung
ein Dynamikverbindungsbibliotheksmodul (40) in dem PC umfasst.
6. Transaktions-beweisendes System nach Anspruch 4, wobei eine Menge von Digitalzeichen
erzeugt werden kann, bevor irgendwelche Freimachungsvermerkbitmaps entsprechend der
Menge von Digitalzeichen erzeugt werden.
7. Transaktions-beweisendes System nach Anspruch 4, weiter mit einer Vorrichtung zum
Verschlüsseln des Transaktionssatzes, bevor dieser in dem Speicherbereich (41) erfasst
wird.
8. Transaktions-beweisendes System nach Anspruch 4, weiter mit einer Vorrichtung zum
Speichern einer Vielzahl von aufeinander folgenden der Transaktionssätze in dem Speicherbereich
(41) als Sicherung für Information, die in der tragbaren Tresorvorrichtung (20) gespeichert
ist.
9. Transaktions-beweisendes System nach Anspruch 1, wobei die Speichervorrichtung eine
Festplatte (24) des PCs ist.
10. Transaktions-beweisendes System nach Anspruch 1, wobei die tragbare Tresorvorrichtung
(20) mit einer Vielzahl von Sicherheitszugangsleveln einschließlich zumindest eines
Standardmodus für normalen Benutzerzugang und zumindest eines beschränkten Modus programmiert
ist, auf den über ein Passwort zugegriffen wird.
11. Transaktions-beweisendes System nach Anspruch 1, weiter mit einer Vorrichtung, die
mit dem PC (12) gekoppelt ist, zum Scannen von Adressateninformation zur Auswahl durch
die nicht-messenden Anwendungsprogramme, wenn Freimachungsvermerke angefordert werden.
12. Transaktions-beweisendes System nach Anspruch 1, wobei die Tresorschnittstellenvorrichtung
(34) angeordnet ist, die Freimachungsvermerkbitmap an das nicht-messende Anwendungsprogramm
zum Betrachten eines Bildes der Freimachungsvermerkbitmap auf einer Anzeige bereitzustellen,
die mit dem PC gekoppelt ist, vor einem Drucken der Freimachungsvermerkbitmap.
13. Transaktions-beweisendes System nach Anspruch 1, wobei das Freimachungsvermerkbilderzeugungs-
und Speichermodul (84) angeordnet ist, eine Portofreimachungsvermerkbitmap zu erzeugen.
14. Transaktions-beweisendes System nach Anspruch 1, wobei die Freimachungsvermerkbitmap-erzeugende
Vorrichtung betriebsbereit ist, die Freimachungsvermerkbitmap durch Kombinieren von
Freimachungsvermerkgrafiken, die in der Speichervorrichtung (24, 28) gespeichert sind,
mit dem Digitalzeichen und der vorbestimmten Information zu erzeugen.
15. Transaktions-beweisendes System nach Anspruch 1, wobei das Anwendungsschnittstellenmodul
(86) betriebsbereit ist, eine Anfrage nach zumindest einem Digitalzeichen in Reaktion
auf eine Anfrage nach Freimachungsvermerken von dem nicht-messenden Anwendungsprogramm
auszugeben, wobei die Anfrage nach Digitalzeichen eine vorbestimmte Information umfasst,
die von der Zeichenerzeugungsvorrichtung (50) benötigt wird, wobei das Kommunikationsmodul
(80) betriebsbereit ist, die Anfrage nach Digitalzeichen und die vorbestimmte Information
an die tragbare Tresorvorrichtung (20) zu senden und von der tragbaren Tresorvorrichtung
(20) einen Transaktionssatz zu empfangen, der ein Digitalzeichen umfasst, das von
der Zeichenerzeugungsvorrichtung (50) erzeugt ist, wobei das Freimachungsvermerkbilderzeugungs-
und Speichermodul (84) betriebsbereit ist, eine Freimachungsvermerkbitmap aus dem
Digitalzeichen zu erzeugen und die Freimachungsvermerkbitmap zu speichern, wobei das
Transaktionserfassungsmodul (82) betriebsbereit ist, den Transaktionssatz zu speichern
und das Anwendungsschnittstellenmodul (86) betriebsfähig ist, die Freimachungsvermerkbitmap
an das nicht-messende Anwendungsprogramm (36) bereitzustellen.
16. Transaktions-beweisendes System nach Anspruch 15, wobei das Kommunikationsmodul (80)
betriebsbereit ist, eine Kommunikationsdatenintegrität mit der tragbaren Tresorvorrichtung
(20) durch die Verwendung eines Sitzungsschlüssels für jede Transaktions-beweisende
Kommunikationssitzung bezüglich einer Anfrage nach und eines Empfangs eines Digitalzeichens
aufrechtzuerhalten.
17. Transaktions-beweisendes System nach Anspruch 16, wobei das Kommunikationsmodul (80)
ebenso betriebsbereit ist, sichere Kommunikationen mit einem Postdatenzentrum während
einem Neuauffüllen von Abrechnungsregistern in der Transanktions-abrechnenden Vorrichtung
der tragbaren Tresorvorrichtung (20) zu steuern.
18. Transaktions-beweisendes System nach Anspruch 17, wobei die tragbare Tresorvorrichtung
(20) eine Vielzahl von tragbaren Tresorgeräten umfasst, von denen jedes mit dem PC
(12) für jede Transaktions-beweisende Kommunikationssitzung gekoppelt sein kann und
wobei das Transaktionserfassungsmodul (82) angeordnet ist, Kommunikationen zwischen
jedem der Tresorgeräte (20) und dem Kommunikationsmodul (80) zu überwachen und in
der Speichervorrichtung (28) alle Transaktionssätze zu speichern und Abrechnungsinformation
neu aufzufüllen, die von dem Kommunikationsmodul für jedes der Tresorgeräte (20) empfangen
wird, wobei die Speichervorrichtung (28) eine Sicherung von Information speichert,
die in den Tresorgeräten (20) gespeichert ist.
19. Verfahren eines Implementierens eines Transaktions-beweisenden Systems (10) auf einem
Personal Computer (PC) (12) mit einer Anzeige (14) und einem ungesicherten Drucker
(18), der mit diesem wirksam gekoppelt ist, mit den Schritten:
Bereitstellen eines tragbaren Tresors (20), der entfernbar mit dem Personal-Computer
(12) über eine Tresorschnittstellenvorrichtung (34) gekoppelt ist,
wobei der tragbare Tresor (20) als ein sicheres Abrechnungsmodul des Transaktions-beweisenden
Systems (10) arbeitet;
Anfordern von Freimachungsvermerken für ein bestimmtes Dokument, das in einem Anwendungsprogramm
(36) verarbeitet wird, das in dem PC (12) läuft;
sicheres Senden über die Tresorschnittstellenvorrichtung (34) von einem Anwendungsschnittstellenmodul
(86) in dem PC in Reaktion auf die Anforderung nach Freimachungsvermerken, einer Anforderung
nach zumindest einem Digitalzeichen an den Tresor (20) mit einem vorbestimmten Informationssatz,
der sich auf das bestimmte Dokument bezieht;
Ausgeben in dem Tresor (20) zumindest eines Digitalzeichens und sicherem Senden über
die Tresorschnittstellenvorrichtung (34) des Digitalzeichens an ein Freimachungsvermerk-erzeugendes
Modul in dem PC;
Speichern des Digitalzeichens und des vorbestimmten Informationssatzes in einem Transaktionssatz;
wobei die Tresorschnittstellenvorrichtung (34) den Transaktionssatz in einem Speicherbereich
(41) des Personal-Computers (12) speichert;
Erzeugen einer Freimachungsvermerkbitmap in dem PC (12) unter Verwendung des Transaktionssatzes;
Speichern der Freimachungsvermerkbitmap in dem Speicherbereich (41); und
Bereitstellen der Freimachungsvermerkbitmap an das Anwendungsprogramm (36), wenn das
Anwendungsprogramm bereit ist, die Freimachungsvermerke zu drucken.
20. Verfahren nach Anspruch 19, mit dem weiteren Schritt:
Betrachten auf einer PC-Anzeige (14) eines Bildes von zumindest einem Teil des bestimmten
Dokumentes mit den darauf gezeigten Freimachungsvermerken vor einem Drucken des bestimmten
Dokumentes.
21. Verfahren nach Anspruch 19, mit dem weiteren Schritt:
Speichern einer Vielzahl von Transaktionssätzen auf einer Festplatte des PCs, wobei
jeder der Transaktionssätze Transaktionen entspricht, die in dem tragbaren Tresor
(20) auftreten.
22. Verfahren nach Anspruch 19, mit den weiteren Schritten:
Bereitstellen einer Dynamikverbindungsbibliothek (DLL) (41) mit Routinen zum Steuern
von Kommunikationen mit dem tragbaren Tresor (20), Speichern von Transaktionen, Speichern
von Freimachungsvermerkbitmaps und Bilden von Schnittstellen mit einer Anwendung;
Laden der DLL in einen Speicher (28) des PCs (12), wenn eine Freimachungsvermerkanforderung
von dem Anwendungsprogramm (36) durchgeführt wird; und
Zugreifen auf die DLL von dem Anwendungsprogramm (36) aus.
23. Verfahren nach Anspruch 19, mit den weiteren Schritten:
Auswählen in dem Anwendungsprogramm (36) einer Empfängeradresseninformation für in
dem Anwendungsprogramm;
Auswählen in dem Anwendungsprogramm (36) eines zu druckenden Portobetrages;
Einschließen der Empfängeradresseninformation und des Portobetrages als ein Teil des
vorbestimmten Informationssatzes; und
Drucken der Empfängeradresse und des Freimachungsvermerkes auf einem Umschlag.
24. Verfahren nach Anspruch 19, mit den weiteren Schritten:
Drucken des Freimachungsvermerkes direkt auf dem Dokument; und
Einsetzen des Dokumentes in einen Umschlag derart, dass der Freimachungsvermerk durch
einen Fensterteil des Umschlages sichtbar ist.
25. Transaktions-beweisendes System einschließlich einer Vielzahl von Computersystemen
(12, 12'), die wirksam konfiguriert sind, ein Netzwerk (1) mit einem (12) der Computersysteme,
das als ein Server funktioniert und den verbleibenden Computersystemen (12') zu bilden,
die als Clients funktionieren, wobei jedes der Computersysteme einen Prozessor, einen
Speicher, eine Speicher- und Benutzerschnittstellenvorrichtung umfasst, wobei zumindest
einige der Speichervorrichtungen eine Vielzahl von nicht-messenden Anwendungsprogrammen
(36') umfassen, die selektiv auf den Clientcomputersystemen (12') laufengelassen werden,
zumindest eines der Computersysteme (12') einen ungesicherten Drucker (18') umfasst,
der wirksam mit diesem zum Drucken gemäß den nicht-messenden Anwendungsprogrammen
gekoppelt ist,
wobei das System umfasst:
eine tragbare Tresorkarte (20), die entfernbar mit dem Servercomputersystem (12) gekoppelt
ist, wobei die Tresorkarte (20) eine Digitalzeichenerzeugungsvorrichtung (50) und
eine Transaktionsabrechnungsvorrichtung (52) umfasst, wobei das Servercomputersystem
(12) eine Vorrichtung (32) zum entfernbaren Koppeln der Tresorkarte (20) mit dem Servercomputersystem
(12) umfasst;
eine Tresorschnittstellenvorrichtung (34) zum Bewirken von Kommunikationen zwischen
der tragbaren Tresorvorrichtung (20) und dem nicht-messenden Anwendungsprogramm (36)
und zum Durchführen von anderen messenden Funktionen als den messenden Funktionen,
die in der tragbaren Tresorvorrichtung (20) durchgeführt werden, wobei die Tresorschnittstellenvorrichtung
umfasst:
ein Anwendungsschnittstellenmodul (86) in dem Clientcomputersystem zum Bilden einer
Schnittstelle mit dem nicht-messenden Anwendungsprogramm;
ein Kommunikationsmodul (80) in dem Servercomputersystem (12) zum Kommunizieren mit
der tragbaren Tresorvorrichtung (20);
einen Speicherbereich (41) in der Speichervorrichtung;
ein Freimachungsvermerkbilderzeugungs- und Speichermodul (84) in dem Clientcomputersystem
zum Erzeugen von Freimachungsvermerkbitmaps und Speichern der Freimachungsvermerkbitmaps
in dem Speicherbereich (41); und
ein Transaktionserfassungsmodul (82) zum Speichern in dem Speicherbereich (41) von
Transaktionssätzen, die in der tragbaren Tresorvorrichtung (20) erzeugt werden.
26. Transaktions-beweisendes System nach Anspruch 25, wobei die Tresorschnittstellenvorrichtung
Teil von Dynamikverbindungsbibliotheksmodulen in den Computersystemen (12, 12') ist.
27. Transaktions-beweisendes System nach Anspruch 25, wobei die Tresorkarte eine PCMCIA-Karte
(20) ist.
28. Transaktions-beweisendes System nach Anspruch 25, wobei eine Menge von Digitalzeichen
in der Tresorkarte (20) erzeugt und in einem anfordernden der Clientcomputersysteme
(12') gespeichert werden kann, bevor irgendwelche Freimachungsvermerkbitmaps entsprechend
der Menge von Digitalzeichen erzeugt werden.
29. Transaktions-beweisendes System nach Anspruch 25, weiter mit einer Vorrichtung zum
Verschlüsseln des Transaktionssatzes, bevor dieser in der Speichervorrichtung (28)
des Servercomputersystems (12) gespeichert wird.
30. Transaktions-beweisendes System nach Anspruch 25, weiter mit einer Vorrichtung zum
Speichern einer Vielzahl von aufeinander folgenden der Transaktionssätze in der Speichervorrichtung
(28) des Servercomputersystems als Sicherung für Information, die in der Tresorkarte
(20) gespeichert ist.
31. Transaktions-beweisendes System nach Anspruch 25, wobei die Transaktionsschnittstellenvorrichtung
betriebsbereit ist, die Freimachungsvermerkbitmap an eines der nicht-messenden Anwendungsprogramme
zum Betrachten eines Bildes der Freimachungsvermerkbitmap auf einer Anzeige bereitzustellen,
die mit dem anfordernden Clientcomputersystem (12') gekoppelt ist, vor einem Drucken
der Freimachungsvermerkbitmap.
32. Transaktions-beweisendes System nach Anspruch 25, wobei die Freimachungsvermerkbitmap-erzeugende
Vorrichtung betriebsbereit ist, eine Portofreimachungsvermerkbitmap durch Kombinieren
von Freimachungsvermerkgrafiken, die in der Speichervorrichtung des anfordernden Clientcomputersystems
gespeichert sind, mit dem Digitalzeichen und der vorbestimmten Information zu erzeugen.
33. Transaktions-beweisendes System nach Anspruch 25, wobei das Anwendungsschnittstellenmodul
(86) betriebsbereit ist, eine Anforderung nach zumindest einem Digitalzeichen in Reaktion
auf eine Anforderung nach Freimachungsvermerken von dem nicht-messenden Anwendungsprogramm
(36) auszugeben, wobei die Anfrage nach Digitalzeichen eine vorbestimmte Information
umfasst, die von der Zeichenerzeugungsvorrichtung benötigt wird, wobei das Kommunikationsmodul
(80) betriebsbereit ist, die Anforderung nach Digitalzeichen und die vorbestimmte
Information an die tragbare Tresorvorrichtung (20) zu senden und von der tragbaren
Tresorvorrichtung (20) einen Transaktionssatz einschließlich eines Digitalzeichens
zu empfangen, das von der Zeichenerzeugungsvorrichtung (50) erzeugt wird,
wobei das Freimachungsvermerkbilderzeugungs- und Speichermodul (84) betriebsbereit
ist, eine Freimachungsvermerkbitmap aus dem Digitalzeichen zu erzeugen und die Freimachungsvermerkbitmap
zu speichern,
wobei das Transaktionserfassungsmodul (82) betriebsbereit ist, den Transaktionssatz
zu speichern und das Anwendungsschnittstellenmodul (86) betriebsbereit ist, die Freimachungsvermerkbitmap
an das nicht-messende Anwendungsprogramm (36) bereitzustellen.
34. Transaktions-beweisendes System nach Anspruch 25 oder 33,
wobei das Transaktionserfassungsmodul (82, 82') in jedem von Server- (12) und Clientcomputersystemen
(12') ist.
35. Transaktions-beweisendes System nach Anspruch 25 oder 33,
wobei das Transaktionserfassungsmodul in dem Servercomputersystem (12) ist.
36. Verfahren eines Implementierens eines Transaktions-beweisenden Systems auf einem Computernetzwerk
(1) mit einer Vielzahl von Computersystemen (12, 12'), die wirksam konfiguriert sind,
das Computernetzwerk mit einem der Computersysteme (12), das als ein Server funktioniert
und den verbleibenden Computersystemen zu bilden, die als Clients (12') funktionieren,
wobei das Verfahren die Schritte umfasst:
Bereitstellen eines tragbaren Tresors (20), der wirksam mit dem Server (12) über eine
Tresorschnittstellenvorrichtung (34) gekoppelt ist,
wobei der Tresor als ein sicheres Abrechnungsmodul (20) des Transaktions-beweisenden
Systems arbeitet;
Anfordern von Freimachungsvermerken in einem der Clients (12') für ein bestimmtes
Dokument, das in einem nicht-messenden Anwendungsprogramm verarbeitet wird, das in
dem anfordernden Client läuft;
Senden der Anforderung nach Freimachungsvermerken von dem anfragenden Client (12')
zu dem Server (12) mit einem vorbestimmten Informationssatz bezüglich des bestimmten
Dokumentes;
Senden in Reaktion auf die Anforderung nach Freimachungsvermerken einer Anforderung
nach zumindest einem Digitalzeichen von dem Server (12) über die Tresorschnittstellenvorrichtung
(34) zu dem tragbaren Tresor (20) mit dem vorbestimmten Informationssatz;
Ausgeben in dem tragbaren Tresor (20) zumindest eines Digitalzeichens und Senden des
Digitalzeichens als Teil eines Transaktionssatzes über die Tresorschnittstellenvorrichtung
(34) zu dem Server (12);
Speichern des Transaktionssatzes in dem Server (12);
Senden von dem Server (12) zu dem anfordernden Client (12') des Digitalzeichens und
eines vorbestimmten Informationssatzes des Transaktionssatzes;
wobei die Tresorschnittstellenvorrichtung (34) den Transaktionssatz in einen Speicherbereich
des Client (12') speichert;
Erzeugen einer Freimachungsvermerkbitmap unter Verwendung des Digitalzeichens und
des vorbestimmten Informationssatzes in dem Client; und
Bereitstellen der Freimachungsvermerkbitmap an das nicht-messende Anwendungsprogramm,
wenn das nicht-messende Anwendungsprogramm bereit ist, den Freimachungsvermerk zu
drucken.
37. Verfahren nach Anspruch 36, mit dem weiteren Schritt:
Betrachten auf einer Anzeige (14'), die mit dem anfordernden Clientcomputersystem
(12') gekoppelt ist, eines Bildes zumindest eines Teils des bestimmten Dokumentes
mit den darauf gezeigten Freimachungsvermerken vor einem Drucken des bestimmten Dokumentes.
38. Verfahren nach Anspruch 36, mit dem weiteren Schritt:
Speichern einer Vielzahl von Transaktionssätzen in einer Datei auf einer Festplatte
des Servers (12) und
Indizieren der Transaktionssätze gemäß der Stückzahl.
39. Verfahren nach Anspruch 36, mit den weiteren Schritten:
Auswählen in dem nicht-messenden Anwendungsprogramm (36) einer Empfängeradressinformation
zur Verwendung in dem Anwendungsprogramm;
Auswählen in dem nicht-messenden Anwendungsprogramm eines Portobetrages, der in dem
Anwendungsprogramm aufgedruckt werden soll;
Einschließen der Empfängeradressinformation und des Portobetrages als Teil des vorbestimmten
Informationssatzes; und
Drucken der Empfängeradresse und des Freimachungsvermerkes auf einem Umschlag.
1. Système (10) de mise en évidence de transaction, comportant
un ordinateur individuel (PC) (12), une imprimante non sécurisée (18) et un moyen
de caisse portable (20) couplés de façon amovible audit PC, et un moyen d'interface
d'utilisateur (14, 16), ledit PC comprenant un processeur (22), une mémoire et un
moyen de stockage (24, 28), ledit moyen de stockage comprenant au moins un programme
(36) d'application de non mesure qui est mis en oeuvre sélectivement sur ledit PC,
ladite imprimante non sécurisée (18) connectée audit PC (12) pour imprimer conformément
audit programme d'application de non mesure, ledit moyen de caisse portable (20) comprenant
un moyen (50) de génération de jeton numérique et un moyen de comptabilité de transaction,
le système comportant :
un moyen (34) d'interface de caisse dans ledit PC (12) pour effectuer des communications
entre ledit moyen de caisse portable (20) et ledit programme d'application de non
mesure et pour effectuer des fonctions de mesure autres que des fonctions de mesure
exécutées dans ledit moyen de caisse portable (20), ledit moyen d'interface de caisse
(34) comportant :
un module d'interface d'application (86) pour établir une interface avec ledit programme
d'application de non mesure;
un module de communication (80) pour communiquer avec ledit moyen de caisse portable
(20) ;
une zone de stockage (41) dans le moyen de stockage (24) ;
un module (84) de création et de stockage d'images de signes destiné à générer des
représentations en mode point de signes et à stocker lesdites représentations en mode
point de signes dans ladite zone de stockage (41) ; et
un module (82) de capture de transaction destinée à stocker dans ladite zone de stockage
(41) des enregistrements de transaction générés dans ledit moyen de caisse portable
(20) .
2. Système de mise en évidence de transaction selon la revendication 1, dans lequel ledit
moyen de caisse portable (20) comprend une carte de caisse qui est couplée de façon
amovible audit PC (12), ledit PC comprenant un moyen pour coupler de façon amovible
ladite carte de caisse audit PC.
3. Système de mise en évidence de transaction selon la revendication 2, dans lequel ladite
carte de caisse est une carte PCMCIA (20).
4. Système de mise en évidence de transaction selon la revendication 1, comportant en
outre :
un moyen (82) dans ledit PC pour capturer dans ladite zone de stockage un enregistrement
de transaction correspondant audit jeton numérique, ledit enregistrement de transaction
comprenant ledit jeton numérique et ladite information prédéterminée.
5. Système de mise en évidence de transaction selon la revendication 4, dans lequel ledit
moyen d'interface de caisse comprend un module de bibliothèque de liaison dynamique
(40) dans ledit PC.
6. Système de mise en évidence de transaction selon la revendication 4, dans lequel un
lot de jetons numériques peut être généré avant que toutes représentations en mode
point, de signes correspondant audit lot de jetons numériques soit générée.
7. Système de mise en évidence de transaction selon la revendication 4, comportant en
outre un moyen pour crypter ledit enregistrement de transaction avant qu'il soit capturé
dans ladite zone de stockage (41).
8. Système de mise en évidence de transaction selon la revendication 4, comportant en
outre un moyen pour stocker une pluralité de certains, consécutifs, desdits enregistrements
de transaction dans ladite zone de stockage (41) en tant que sauvegarde d'informations
stockées dans ledit moyen de caisse portable (20).
9. Système de mise en évidence de transaction selon la revendication 1, dans lequel ledit
moyen de stockage est une unité à disque dur (24) dudit PC.
10. Système de mise en évidence de transaction selon la revendication 1, dans lequel ledit
moyen de caisse portable (20) est programmé avec de multiples niveaux d'accès de sécurité
comprenant au moins un mode par défaut pour un accès d'utilisateur normal et au moins
un mode restreint auquel on accède par un mot de passe.
11. Système de mise en évidence de transaction selon la revendication 1, comportant en
outre un moyen couplé audit PC (12) pour analyser par balayage une information de
destinataire pour une sélection par lesdits programmes d'application de non mesure
lorsque des signes sont demandés.
12. Système de mise en évidence de transaction selon la revendication 1, dans lequel ledit
moyen d'interface de caisse (34) est agencé pour fournir ladite représentation en
mode de point de signes audit programme d'application de non mesure pour une visualisation
d'une image d'une dite représentation en mode point de signes sur un afficheur couplé
audit PC avant l'impression de ladite représentation en mode point de signes.
13. Système de mise en évidence de transaction selon la revendication 1, dans lequel ledit
module (84) de création et de stockage d'image de signe est agencé pour générer une
représentation en mode point de signes d'affranchissement.
14. Système de mise en évidence de transaction selon la revendication 1, dans lequel ledit
moyen de génération d'une représentation en mode point de signes peut être mis en
oeuvre pour générer ladite représentation en mode point de signe en combinant des
graphiques de signes stockés dans ledit moyen de stockage (24, 28) avec ledit jeton
numérique et ladite information prédéterminée.
15. Système de mise en évidence de transaction selon la revendication 1, dans lequel ledit
module (86) d'interface d'application peut être mis en oeuvre pour délivrer une demande
pour au moins un jeton numérique en réponse à une demande portant sur des signes provenant
dudit programme d'application de non mesure, ladite demande pour un jeton numérique
comprenant une information prédéterminée demandée par ledit moyen (50) de génération
de jeton, ledit module (80) de communications pouvant être mis en oeuvre pour envoyer
ladite demande pour un jeton numérique et ladite information prédéterminée audit moyen
(20) de caisse portable et pour recevoir dudit moyen (20) de caisse portable un enregistrement
de transaction comprenant un jeton numérique généré par ledit moyen (50) de génération
de jeton, ledit module (84) de création et de stockage d'images de signes pouvant
être mis en oeuvre pour générer une représentation en mode point de signes à partir
dudit jeton numérique et pour stocker ladite représentation en mode point de signes,
ledit module (82) de capteur de transaction pouvant être mis en oeuvre pour stocker
ledit enregistrement de transaction, et ledit module (86) d'interface d'application
pouvant être mis en oeuvre pour fournir ladite représentation en mode point de signes
audit programme (36) d'application de non mesure.
16. Système de mise en évidence de transaction selon la revendication 15, dans lequel
ledit module (80) de communications peut être mis en oeuvre pour maintenir l'intégrité
de données de communication avec ledit moyen (20) de caisse portable par l'utilisation
d'une clé de session pour chaque transaction mettant en évidence une session de communication
concernant une demande pour, et une réception de, un jeton numérique.
17. Système de mise en évidence de transaction selon la revendication 16, dans lequel
ledit module (80) de communications peut également être mis en oeuvre pour commander
des communications sécurisées avec un centre de données postales pendant des rechargements
de registres de comptes dans ledit moyen de comptabilité de transaction dudit moyen
de caisse portable (20).
18. Système de mise en évidence de transaction selon la revendication 17, dans lequel
ledit moyen de caisse portable (20) comporte une pluralité de dispositifs à caisses
portables dont n'importe lequel peut être couplé audit PC (12) pour chaque session
de communications de mise en évidence d'une transaction, et dans lequel ledit module
(82) de capture de transaction est agencé pour contrôler des communications entre
chacun desdits dispositifs de caisse (20) et dudit module de communications (80) et
pour stocker dans ledit moyen de stockage (28) tous les enregistrements de transactions
et recharger une information de compte reçue par ledit module de communications pour
chacun desdits dispositifs de caisse (20), grâce à quoi ledit moyen de stockage (28)
stocke une sauvegarde d'informations stockées dans lesdits dispositifs de caisse (20).
19. Procédé de mise en oeuvre d'un système (10) de mise en évidence de transaction sur
un ordinateur individuel (PC) (12) ayant un afficheur (14) et une imprimante non sécurisée
(18) couplée fonctionnellement à celui-ci, comprenant les étapes qui consistent :
à utiliser une caisse portable (20) qui est couplée de façon amovible à l'ordinateur
individuel (12) par l'intermédiaire d'un moyen d'interface de caisse (34), ladite
caisse portable (20) fonctionnant en tant que module de comptabilité sécurisé pour
le système (10) de mise en évidence de transaction ;
la demande de signes pour un document particulier en cours de traitement dans un programme
d'application (36) fonctionnant dans le PC (12) ;
l'envoi sécurisé en passant par le moyen (34) d'interface de caisse, depuis un module
(86) de mise en interface d'application dans le PC, en réponse à ladite demande portant
sur des signes, d'une demande pour au moins un jeton numérique à ladite caisse (20)
avec un ensemble prédéterminé d'informations concernant le document particulier;
la délivrance dans ladite caisse (20) d'au moins un jeton numérique et l'envoi sécurisé,
en passant par le moyen (34) d'interface de caisse, du jeton numérique à un module
(84) de génération de signes dans le PC ;
le stockage du jeton numérique et de l'ensemble prédéterminé d'informations dans un
enregistrement de transaction ;
le moyen (34) d'interface de caisse stockant l'enregistrement de transaction dans
une zone de stockage (41) de l'ordinateur individuel (12) ;
la génération d'une représentation en mode point de signes dans le PC (12) en utilisant
l'enregistrement de la transaction ;
le stockage de la représentation en mode point de signe dans ladite zone de stockage
(41) ; et
la fourniture de la représentation en mode point de signe au programme d'application
(36) lorsque le programme d'application est prêt à imprimer les signes.
20. Procédé selon la revendication 19, comprenant l'autre étape de :
visualisation sur un afficheur (14) du PC d'une image d'au moins une partie du document
particulier avec les signes représentés sur celui-ci avant l'impression du document
particulier.
21. Procédé selon la revendication 19, comprenant l'autre étape de :
stockage de plusieurs enregistrements de transaction sur une unité à disque dur du
PC, chacun des enregistrements de transaction correspondant à des transactions ayant
lieu dans ladite caisse portable (20).
22. Procédé selon la revendication 19, comprenant les autres étapes de :
l'utilisation d'une bibliothèque de liaison dynamique (DLL) (41) contenant des sous-programmes
pour commander des communications avec la caisse portable (20), stocker des transactions,
stocker des représentations en mode point de signes et mettre en interface des applications
;
le chargement de la DLL dans une mémoire (28) du PC (12) lorsqu'une demande de signes
est réalisée depuis le programme (36) d'applications ; et
l'accès à la DLL depuis le programme d'application (36).
23. Procédé selon la revendication 19, comprenant les autres étapes de :
sélection dans le programme d'application (36) d'une information d'adresse de destinataire
pour le programme d'application ;
sélection dans le programme d'application (36) d'une valeur d'affranchissement devant
être imprimée ;
inclusion de l'information d'adresse de destinataire et de la valeur d'affranchissement
en tant que partie de l'ensemble prédéterminé d'information ; et
impression de ladite adresse de destinataire et desdits signes sur une enveloppe.
24. Procédé selon la revendication 19, comprenant les autres étapes de :
impression des signes directement sur le document ; et
insertion du document dans une enveloppe de façon que les signes soient visibles à
travers une partie à fenêtre de l'enveloppe.
25. Système de mise en évidence de transaction comprenant de multiples systèmes informatiques
(12, 12') configurés fonctionnellement pour former un réseau (1) avec l'un (12) des
systèmes informatiques fonctionnant en tant que serveurs et les autres systèmes informatiques
(12') fonctionnant en tant que clients, chacun des systèmes informatiques comprenant
un processeur, une mémoire, des moyens de stockage et d'interface d'utilisateur, au
moins certains desdits moyens de stockage comprenant de multiples programmes (36')
d'application de non mesure qui sont mis en oeuvre sélectivement sur lesdits systèmes
informatiques clients (12'), au moins l'un desdits systèmes informatiques (12') comprenant
une imprimante non sécurisée (18') couplée fonctionnellement à ce système pour imprimer
conformément audit programme d'application de non mesure, le système comportant :
une carte de caisse portable (20) qui est couplée de façon amovible audit système
informatique serveur (12), ladite carte de caisse (20) comprenant un moyen (50) de
génération de jetons numériques et un moyen (52) de comptabilité de transaction, ledit
système informatique serveur (12) comprenant un moyen (32) pour coupler de façon amovible
ladite carte de caisse (20) audit système informatique serveur (12) ;
un moyen (34) d'interface de caisse pour effectuer les communications entre lesdits
moyens de caisse portable (20) et ledit programme d'application de non mesure (36)
et pour effectuer des fonctions de mesure autres que des fonctions de mesure effectuées
dans ledit moyen de caisse portable (20), ledit moyen d'interface de caisse comportant
:
un module (86) d'interface d'application dans ledit système informatique client pour
établir une interface avec ledit programme d'application de non mesure ;
un module (80) de communications dans ledit système informatique serveur (12) pour
communiquer avec ledit moyen de caisse portable (20) ;
une zone de stockage (41) dans lesdits moyens de stockage ;
un module (84) de création et de stockage d'images de signes dans ledit système informatique
client pour générer des représentations en mode point de signes, et stocker lesdites
représentations en mode point de signes dans ladite zone de stockage (41) ; et
un module (82) de capture de transaction destiné à stocker dans ladite zone de stockage
(41) des enregistrements de transactions générés dans ledit moyen de caisse portable
(20).
26. Système de mise en évidence de transaction selon la revendication 25, dans lequel
ledit moyen d'interface de caisse fait partie de modules de bibliothèque de liaison
dynamique dans lesdits systèmes informatiques (12, 12').
27. Système de mise en évidence de transaction selon la revendication 25, dans lequel
ladite carte de caisse est une carte PCMCIA (20).
28. Système de mise en évidence de transaction selon la revendication 25, dans lequel
un lot de jetons numériques peut être généré dans la carte de caisse (20) et stocké
dans l'un desdits systèmes informatiques client (12') qui le demande avant que toutes
représentations en mode point de signe correspondant audit lot de jetons numériques
soient générées.
29. Système de mise en évidence de transaction selon la revendication 25, comportant en
outre des moyens destinés à crypter ledit enregistrement de transaction avant qu'il
soit stocké dans ledit moyen de stockage (28) dudit système informatique serveur (12).
30. Système de mise en évidence de transaction selon la revendication 25, comportant en
outre des moyens destinés à stocker une pluralité de certains, consécutifs, desdits
enregistrements de transaction dans lesdits moyens de stockage (28) dudit système
informatique serveur en tant que sauvegarde d'informations stockées dans ladite carte
de caisse (20).
31. Système de mise en évidence de transaction selon la revendication 25, dans lequel
ledit moyen d'interface de caisse peut être mis en oeuvre pour fournir ladite représentation
en mode point de signes audit un desdits programmes d'application de non mesure pour
la visualisation d'une image de ladite représentation en mode point de signes sur
un afficheur couplé audit système informatique client (12') demandant avant une impression
de ladite représentation en mode point de signes.
32. Système de mise en évidence de transaction selon la revendication 25, dans lequel
ledit moyen de génération d'une représentation en mode point de signes peut être mis
en oeuvre pour générer une représentation en mode point de signes d'affranchissement
en combinant des graphiques de signes stockés dans ledit moyen de stockage dudit système
informatique client demandeur audit jeton numérique et à ladite information prédéterminée.
33. Système de mise en évidence de transaction selon la revendication 25, dans lequel
ledit module (86) d'interface d'application peut être mis en oeuvre pour délivrer
une demande portant sur au moins un jeton numérique en réponse à une demande portant
sur des signes provenant dudit programme d'application de non mesure (36), ladite
demande portant sur un jeton numérique comprenant une information prédéterminée demandée
par ledit moyen de génération de jeton, ledit module (80) de communications pouvant
être mis en oeuvre pour envoyer ladite demande portant sur un jeton numérique et ladite
information prédéterminée audit moyen (20) de caisse portable et pour recevoir dudit
moyen (20) de caisse portable un enregistrement de transaction comprenant un jeton
numérique généré par ledit moyen (50) de génération de jeton, ledit module (84) de
création et de stockage d'image de signes pouvant être mis en oeuvre pour générer
une représentation en mode point de signes à partir dudit jeton numérique et pour
stocker ladite représentation en mode point de signes, ledit module (82) de capture
de transaction pouvant être mis en oeuvre pour stocker ledit enregistrement de transaction,
et ledit module (86) d'interface d'application pouvant être mis en oeuvre pour fournir
ladite représentation en mode point de signes audit programme d'application de non
mesure (36).
34. Système de mise en évidence de transaction selon la revendication 25 ou 33, dans lequel
ledit module (82, 82') de capture de transaction se trouve dans chacun desdits systèmes
informatiques serveur (12) et client (12').
35. Système de mise en évidence de transaction selon la revendication 25 ou 33, dans lequel
ledit module (82) de capture de transaction se trouve dans ledit système informatique
serveur (12).
36. Procédé de mise en oeuvre d'un système de mise en évidence de transaction sur un réseau
informatique (1) comportant de multiples systèmes informatiques (12, 12') configurés
fonctionnellement pour former le réseau informatique dans lequel l'un des systèmes
informatiques (12) fonctionne en tant que serveur et les autres systèmes informatiques
fonctionnent en tant que client (12'), le procédé comprenant les étapes qui consistent
:
à utiliser une caisse portable (20) qui est couplée fonctionnellement au serveur (12)
par l'intermédiaire d'un moyen d'interface de caisse (34), ladite caisse fonctionnant
en tant que module de comptabilité sécurisée (20) du système de mise en évidence de
transaction ;
à demander des signes dans l'un des clients (12') pour un document particulier en
cours de traitement dans un programme d'application de non mesure fonctionnant dans
le client demandeur ;
à envoyer la demande portant sur des signes depuis le client demandeur (12') au serveur
(12) avec un ensemble prédéterminé d'informations concernant le document particulier;
à envoyer, en réponse à ladite demande de signes, une demande portant sur au moins
un jeton numérique depuis le serveur (12) en passant par le moyen d'interface de caisse
(34) à la caisse portable (20) avec l'ensemble prédéterminé d'informations ;
à délivrer dans ladite caisse portable (20) au moins un jeton numérique et à envoyer
le jeton numérique en tant que partie d'un enregistrement de transaction en passant
par le moyen d'interface de caisse (34) au serveur (12) ;
à stocker l'enregistrement de transaction dans le serveur (12) ;
à envoyer du serveur (12) au client demandeur (12') le jeton numérique et un ensemble
prédéterminé d'informations de l'enregistrement de la transaction ;
le moyen (34) d'interface de caisse stockant l'enregistrement de transaction dans
une zone de stockage du client (12') ;
à générer une représentation en mode point de signes en utilisant le jeton numérique
et l'ensemble prédéterminé d'informations dans le client ; et
à fournir la représentation en mode point de signes au programme d'application de
non mesure lorsque le programme d'application de non mesure est prêt à imprimer les
signes.
37. Procédé selon la revendication 36, comprenant l'autre étape qui consiste :
à visualiser sur un afficheur (14') couplé au système informatique client demandeur
(12') une image d'au moins une partie du document particulier avec les signes représentés
sur celle-ci avant l'impression du document particulier.
38. Procédé selon la revendication 36, comprenant l'autre étape qui consiste :
à stocker de multiples enregistrements de transaction dans un fichier sur une unité
à disque dur du serveur (12), et à indexer les enregistrements de transaction conformément
à un comptage de pièces.
39. Procédé selon la revendication 36, comprenant les autres étapes qui consistent :
à sélectionner dans le programme d'application de non mesure (36) une information
d'adresse de destinataire pour une utilisation dans le programme d'application ;
à sélectionner dans le programme d'application de non mesure une valeur d'affranchissement
devant être imprimée dans le programme d'application ;
à inclure l'information d'adresse de destinataire et la valeur d'affranchissement
en tant que partie de l'ensemble prédéterminé d'informations ; et
à imprimer ladite adresse de destinataire et lesdits signes sur une enveloppe.