JP2003524841A - Apparatus, system, and method for performing wireless transaction financial transfers, electronically recordable authorized transfers, and other information transfers - Google Patents

Abstract

SUMMARY OF THE INVENTION The present invention relates to a personal digital assistant "PDA" (also referred to as a personal intelligent communicator (PIC) and a personal communicator), a palm computer, an intelligent handheld cellular radio telephone, Using other wireless telephones and personal handheld electronic devices configured with infrared short-range data communication (referred to herein as "PDAs" for simplicity), the purchase price is paid wirelessly and financial accounting systems and Devices, systems, and methods are provided for interfacing, electronically recording approved transactions, and communicating wirelessly. Further, if the transaction amount is small, for example, less than $ 5, other types of transactions such as credit card charges, debit card charges, electronic cash transfers, tickets, other financial transactions, and electronic coupons. Device, firmware, software program, and computer-implemented method for paying service and / or sales service fees to a customer.

Description

Detailed Description of the Invention

[0001]

FIELD OF THE INVENTION

The present invention relates generally to point-of-sales point-of-sale terminal sales financial transactions, and more specifically, the present invention relates to portable electronic devices with wireless communication capabilities. Related to conducting sales terminal sales transactions using.

[0002]

BACKGROUND OF THE INVENTION

There have been many traditional methods of paying purchases in the past, including cash, checks, credit cards and debit cards, and are still in use today. Traditional payment methods typically require the user to individually and manually fill in each check in his checkbook, write the payment amount on a credit card invoice to the check, and so on. It is necessary to update accounting records.

Recently, online internet payment systems have been developed to allow payment of bills to centralized payment systems through online access. Some of these systems provide some level of integration with financial accounting systems. However, online internet payment systems are limited in that users cannot employ such systems in retail stores.

[0004] Purchase payment methods need to be portable and include a financial accounting system in a user-friendly electronic interface. Goods that can be purchased include authorization transfers (eg, tickets). Purchasing various types of tickets is the purchase of authorizations for doing something, such as watching a movie or winning a ticket for a particular airline. Traditionally, tickets have been obtained in the form of printed paper. Recently, many commercial services are doing electronic ticketing. Traditional printing paper tickets can disappear. Electronic ticketing is based on the premise that individual commercial systems are perfect. Therefore, there is a need for a way to personally control electronic ticketing.

[0005] Conventionally, a credit card processing fee for processing transactions such as bank charges, credit card charges, debit card fees, electronic transfers, etc. is 5 in amount.
It was such an amount that it was unattractive for merchants and unattractive for consumers to process transactions for small amounts, such as less than US dollars. What is needed is a way to process small transactions and charge small fees that are even more tailored to the transaction amount.

[0006]

[Outline of the Invention]

US Provisional Patent Application No. 60 / 181,6 filed February 10, 2000
No. 00, US Provisional Patent Application No. 60/187, filed March 8, 2000
, 924, and US Provisional Patent Application No. 60 / 255,980, filed Dec. 15, 2000, are hereby incorporated by reference for all purposes.

The present invention relates to a personal digital assistant (PDA) (also called Personal Intelligent .communicators: PIC's and personal communicator), a palm computer, an intelligent mobile phone or other wireless telephone, and infrared rays. , Bluetooth, Radio Frequency (RF),
Other personal portable electronic devices configured for other short-range wireless data communications (for simplicity, such devices are referred to herein as "PDAs" and all short-range wireless interfaces are referred to as "infrared"). Call) to wirelessly pay for purchases, electronically interface with a financial accounting system, electronically record authorization transactions, and provide wireless communication. is there. A PDA is a consumer electronic device that is configured and programmed to perform specialized tasks such as acting as an electronic diary, portable personal database, personal communicator, and so on.

The present invention provides services for credit card billing, debit card billing, electronic cash transfers, tickets and other financial transactions and / or transactions where the transaction amount is small, eg less than $ 5. Or, a device, a firmware, a software program, and a computer-implemented method for paying a sales service fee are provided. Those skilled in the art will understand that the amount of $ 5 used here is an example and not a limitation of the invention. The present invention can be applied to foreign currency and to such a small currency amount of foreign currency.

These and other features of the invention are more fully described in the following description of embodiments of the invention. The description will be given with reference to the accompanying drawings.

[0010]

[Copy of copyright material]

A portion of the disclosure of this patent document contains material that is copyrighted by Immtec. Immtec, the copyright owner, has no objection to anyone's reproductions of the patent files or patent documents or patent disclosures in the original registry of the Patent and Trademark Office, but in all other respects However, all copyrights are reserved.

[0011]

[Trademark]

Immtec ^™ , Microwallet ^™ , mewallet ^™ , CSRA ^™ , Customer Specific Receipt Advertising ^™ and PayStick ^™ are trademarks of Immtec. Actual company names and product names described here are trademarks of their respective owners.

[0012]   (Detailed Description of the Invention)           A.Summary of the main processes of the invention   FIG. 1a illustrates the relationship between the major nodes of a typical hardware network.
1 is an overview of an embodiment of a PDA payment system that does. In the embodiment shown in FIG.
, PDA 700 is the central component of the network. The role of PDA is user
Everything that he wants to end, even while he's away from his house
With short-term repositories and communication devices for
And function. In an embodiment, the PDA is a wireless interface
Through this wireless interface 705, the PDA is connected to the user environment.
It will communicate with other devices distributed throughout the boundary.

The PDA communicates with an Automated Teller Machine (ATM) 740. In ATM transactions, PDA obtains electronic money or electronic money certificate from ATM. The PDA communicates with a Point of Purchase (POP) terminal (also sometimes referred to as a Point of Sale (POS) terminal, as referred to herein) 710. In a POP terminal transaction, the PDA pays for the purchase using some credit or bank account, or with electronic money. In one embodiment, the account validator is stored in memory storage with a PDA. The PDA facilitates this transaction by storing a number of account numbers, from which the user chooses a payment method. The PDA notifies the POP terminal of the account number, then P
The user's account information temporarily stored in the DA is updated.

The PDA also communicates with the POP ticket terminal. In a transaction at a POP ticket terminal, the PDA holds an electronic authorization certificate or eTicket for use with individual services or participate in individual entertainment events. In this specification, a ticket including an electronic ticket is sometimes referred to as a transaction authorization,
It is used synonymously as an authorization certificate or a transaction authorization certificate.

The PDA communicates with a personal computer (PC) 760 via a communication interface 795, which is one of several different types of interfaces. This communication interface 795 is used to synchronize the PDA's data storage with the user's account information stored on the PC. ATM communicates with the bank's server through communication link 745. The POP terminal communicates with the Automated Clearing House (ACH) server 720 via the communication link 715 (even if the communication link 715 is a direct link, as described further below). Or it could be a link through the Immtec server host 750). The POP eTicket terminal communicates with the POP ticket server 780 via communication link 785. The ticket server maintains a database of issued, cleared, or unpaid eTickets used to validate the eTickets.

The PC communicates with the eTicket Server via communication link 765. Communication link 765 is used to enable eTicket purchases to be saved to the PDA. PC
Also communicates with bank server 730 via communication link 735 (communication link 735 may be a direct link, or I, as described further below).
It may be a link via the mmtec server host 750). This communication allows the PC to be used in conjunction with a bank server to manage the user's bank / cash and credit accounts that may be used by the PDA when making payments.

The PC also communicates with the Immtec server host 750 via communication link 755.
Communicate with. References herein to "Immtec" apply equally to any host server system embodying the present invention. That is, references to Immtec should be understood to include references to other host systems. References to Immtec are exemplary and
It is not a limitation of the invention. In the exemplary embodiment of the invention, communication link 755 is an Internet connection using the Hyper Text Transfer Protocol (HTTP) suite.
It is a link. The PC manages the PDA device using the resources on the Immtec host.

PDA wireless systems require a setup process to be performed using a PC, an Immtec server, and a PDA device. An example relationship between the network nodes of this embodiment during PDA device setup is shown in FIG. 1b as a UML layout diagram. As shown in FIG. 1 b, PC 760 hosts software objects that communicate with Immtec server 750 via Internet 755 and with PDA device 700 via communication link 795.
This communication link is one of several different types. In this example, the link is a Universal Serial Bus (USB).

The Immtec server holds initialization data for the PDA device. This initialization data includes encrypted registration data unique to each PDA device, which registration data is maintained at the Immtec host site in this embodiment. The PC includes setup software, which queries the Immtec server for setup data, combines the setup data from the Immtec server with user input credit and bank account information, and combines the combined data. To the PDA device. Figure 1
FIG. 4d is a partial illustration of an example software object communication sequence in an example setup process using this embodiment. As shown in FIG. 1d, P
DA setup software object 810 is also hosted by PC 760. The PDA setup object requests setup data from the user and sends data 815 to the PDA hosted by the PDA 700.
Send to DA management software object 820. And save the setup data for future use.

As used in this specification, the expression “via a modem” to connect to the Internet ”
It should be understood that it includes all internet connection methods including wireless, DSL, and all other methods of connecting to and / or accessing the internet.

One of the uses of the present invention is to make payments at a point of purchase terminal. FIG. 1c is a UML layout diagram showing a state in which an embodiment of the present invention is used to pay a purchase price. As shown in FIG. 1c, the PDA 700 has a P
A wireless communication link 705 is established with the OP terminal 710. Payment information is sent from the PDA to the POP terminal using communication link 705. The POP terminal connects to the ACH server 720 by communication link 715. The POP terminal sends the payment information to the ACE server via communication link 715.

An example of a communication sequence between software objects in this embodiment is shown in FIG.
It is shown in. PDA hosted by PDA 700, as shown in FIG. 1d
The payment object 830 sends the payment information 83 to the POP terminal object 840.
Send 5. The POP terminal sends payment information to the ACH server 850 to request payment verification (845). The ACH returns an authorization 855 to the POP terminal. Then
The POP terminal sends a transaction confirmation 865 back to the PDA payment object 830. The PDA payment object 830 then sends the transaction data 875 to the PDA management object. The PDA management object then stores the transaction data in the transaction history database. The PDA management object then sends the transaction history 885 to the PDA setup object hosted by the PC. The transaction data is then stored in the transaction history database on the PC and sent to the accounting object 800 for further processing.

The present invention may also be used as a carrier for electronic authorization or eTickets. A UML layout diagram of an embodiment of the present invention used as an eTicket carrier is shown in FIG.
It is shown in. As shown in FIG. 1e, PC 760 hosts a browser client in communication with ticket broker server 900 via communication link 905. In the example shown in FIG. 1e, the communication link is a connection using the Internet. Therefore, the user can use the browser to order the ticket from the ticket broker. The user can then choose the Immtec server as the eT icket certificate provider. If the user selects the Immtec server, the ticket broker will be able to
05 to the Immtec ticket server 770. The ticket broker can then request the eTicket certificate from the Immtec server. The certificate is then sent to the PC, where it is used to set up the PDA device 700. In the embodiment shown in FIG. 1e, the Immmtec server provides a copy of the eTicket certificate via the communication link 775 to the POP ticket server 78.
Send to 0. The POP ticket server 780 is, for example, a POP ticket server installed at a site where a ticket is to be used or accessible by a POP ticket terminal at this site. In another embodiment,
The PC is transparently connected to the Immtec server via the ticket broker to receive the certificate.

Once the PC receives the eTicket certificate, the PC sets up the PDA device by sending the eTicket certificate to the PDA device via communication link 795. The user then brings the PDA to the location of the event or service and uses it to establish a wireless communication link 705 with the POP eTicket terminal 710. The eTicket certificate is verified by the POP eTicket terminal to the POP ticket server via communication link 785.

An example communication event for eTicket creation and transfer between software components of this embodiment is shown in FIG. 1f. The PC client 1010 sends a request 1013 to the ticket server 1000. The ticket server then Im
Request to generate eTicket certificate from mtec ticket server 1060 (1003)
To do. The Immtec ticket server then creates an eTicket and sends it to the ticket server (1063). The Immtec server then sends a copy 1066 of the eTicket certificate to the POP ticket server. The ticket server then sends the eTicket certificate 1006 to the PC client. The PC client then contacts the PDA purchase object 1020 hosted by the PDA 700.
Send the eTicket certificate 1016. The PDA Purchase Object then stores the eTicket certificate.

The PDA checkout object 1030 hosted by the PDA then requests the eTicket certificate 1023 to be sent from the eTicket database. Then
The PDA payment object sends the eTicket certificate 1033 to the POP terminal 1040 via a wireless communication link. The POP terminal requests the POP ticket server 1050 to verify the e-ticket 1053. If the eTicket certificate is valid, the POP ticket server sends a confirmation 1056 to the POP terminal. The POP ticket server then deletes the ticket from the valid certificate database (1059). The POP terminal then sends a ticket receipt confirmation 1036 to the PDA payment object. The PDA Settlement object requests that the eTicket certificate be deleted (1039).

[0027]           B.Example hardware overview             1.Portable computing with infrared input / output device                 Device (PDA)   The present invention is applicable to all portable or watch supports without departing from the spirit of the invention.
It can be applied to the PDA computing device of Izu. The data is
You may type via a keypad, pen, voice, modem depending on the
Alternatively, it may be input by synchronizing with a PC. PDA device is infrared communication
And / or other short-range data transmission capabilities, and a personal computer (hardware
Via the wired sync cradle or infrared interface), shopping area
Office / sales hardware, automated teller machines (via wireless interface),
And can communicate with an electronic kiosk (also via a wireless interface)
To configure. PDA devices include wired and wireless communication devices as well as the Internet.
May optionally be configured to communicate via.   As shown in FIG. 1g, the PDA according to the embodiment of the present invention has the following hardware.
With example components. That is, operating system 1; RAM (random
-Access memory) 2a-2b; ROM (read-only memory) 3; Clock 4
A screen driver 5a and a liquid crystal (liquid crystal display) screen
Or other display device 5b; infrared input / output interface 6;
CPU (Central Processing Unit) including processor and microcontroller
Or another computer device 7; battery 8; software control button 9;
Installed software 10; optional wireless modem 11b and modem driver
Driver 11a; optional wired modem 12 and modem driver 11a; PC
Period Interface 13; PC Sync Cradle 14; Pen Interface (
15 (requires touch pad 23) or voice interface (internal
16 or keypad interface 17;
Optional biometric device 18; optional speaker 19; optional camera 20a and
A visual interface 20b; and an optional keypad 21;

[0028]           2.Selectable internal PDA and infrared input / output device               Wireless mobile phone   A wireless mobile telephone, which allows to carry out the functions according to the invention, is any
The size and model may be used. Its operating protocol is CDMA, TDMA, GSM.
And other digital protocols other than these. This is an infrared
It is configured to have the capability of transmission and other short-range data transmission. Also, a personal computer (ha
Purchasing via wired sync cradle or infrared interface)
Location hardware, automated teller machines and / or electronic kiosks (infrared interface
Communication), wired and wireless communication devices, or the Internet.
It is also configured to do.   As shown in FIG. 2, the wireless mobile telephone according to the embodiment of the present invention has the following hardware.
And software component examples. That is, the built-in PDA computer 3
0, keypad interface 31, selective voice activation ability 32, selective
Headset and headset interface 33, speaker 19, My
Blackphone 22, wireless data / voice transmission hardware 12b, antenna 34, tiger
Receiver 35, liquid crystal screens 5a, 5b, infrared interface 6, PC
Interface 13, RAM2a-2b, ROM3, operating system
System 1, clock 4, CPUs 7a, 7b, batteries 8a, 8b, battery charger
Charger interface 36 and battery charger / PC sync
The idle interface 14.

[0029]           3.Credit card processing terminal with infrared input / output device   Credit Card / Debit Card Purchasing Place / Sales Point in Embodiment of the Present Invention
The processing terminal is similar to the one currently in use manufactured by many manufacturers
However, if it is installed on the top or side of the terminal or the serial interface
Infrared input / output interface and / or externally connected to the interface port
Or, it is different in that a short distance data transmission device is further added.   In one embodiment of the present invention, various types of store terminals and credit cards
/ External aftermarket infrared interface that can be connected to a debit card processing terminal
There is a face. As an external infrared interface device,
Black processor, PDA, wireless telephone and / or dedicated purpose system device
Infrared communication stack that interfaces with the POS terminal, PDA,
, Wireless telephones and / or dedicated purpose system devices, and communication with server systems
Software that does this, or a serial port compatible with various POS terminals.
There is an auto plug. In one embodiment of the present invention, an external infrared interface
Device uses an POP power source to connect the infrared device
Provides power to the Ranceiva dongle and microprocessor.   As shown in FIG. 3, the infrared interface 50 includes a keypad interface.
A person who communicates with CPU 51 by way 52 and swipe interface 53
Communication is performed with the CPU 51 of the POP terminal by the same method as the method. Infrared interface
The data collected by the chair 50 is stored on the keypad or swipe interface.
Information sent to or received from a bank or clearinghouse
Sent to a bank / clearinghouse or in exactly the same way as
It is received from here.

[0030]             4.Automatic deposit and withdrawal machine with infrared input / output device   The ATM (Automatic Deposit Refund Machine) in this embodiment is the currently used ATM.
Similar, but with the exception of the infrared input / output interface, as shown in FIG.
A chair 60 or another short distance data transmitter is added to the front of the ATM or the like. Red
The outside line interface is an ATM keypad interface 62 and a switch.
Similar to the method in which the wipe interface 63 communicates with the ATM CPU 61.
Method to communicate with the ATM CPU 61. Collection of infrared interface 60
The data displayed is the current information collected by the keypad or swipe interface.
How to send to, or receive from, your bank or clearinghouse
Send it to a bank or a clearinghouse in exactly the same way, or
Receive from there.

[0031]             5.Wireless modem   The wireless modem can be installed in the PDA or in the slot of the PDA provided for that purpose.
Insert or externally connect to PDA. What is the communication mode of a wireless modem?
It can be configured and programmed to work in a rotocol as well.

[0032]             6.Wired modem   Wired modem can be installed in the PDA or in the slot of the PDA provided for that purpose.
Insert or externally connect to PDA. Wired modem is what telephone number
It can be configured to work in line as well.

7. PC Personal computer (“PC”) is Windows (registered trademark) 95-98, ME, 2
000+, NT-2000 OS, Mac OS, Linux OS, and other operating systems. The PC may be a desktop model, a laptop model, or another type of PC that can communicate with external devices. In this embodiment, the PC has a built-in modem and is configured to communicate with the Internet. For those skilled in the art, the description of the internal modem in this embodiment is not a limitation of the present invention, and another embodiment using an external modem does not depart from the spirit of the invention. I understand. As shown in FIG. 5, the personal computer of this embodiment includes the following example hardware and software components: operating system 100, permanent memory storage device (hard drive) 101, RAM 102, ROM 103, clock 104. , Display monitors 105a-105b, selective infrared input / output interface 106, CPU 107, battery 108, installed software 110, parallel port 111, serial port 112, selective USB port 113, selective SCSI port. 114, communication port 115,
An input device (touch pad 116 or mouse 117a-117b or voice interface 118 (with microphone 119 and speaker 120) and / or keyboard interface and keyboard 122), and modem 123a-123b.

[0034]           8.External infrared interface port   In the case of a personal computer, the external infrared interface device is connected via the communication port.
Connected to Sokon. An example of a port is USB. In this embodiment,
Installation cords are typically at least 1.3 meters in length, or 4 fibers.
It is In this embodiment, the device is a flat surface such as a desktop or a table.
It can be placed on any surface. The external infrared interface is
Allow any personal computer to communicate with an infrared equipped PDA,
And even if you don't have a sync cradle, your PDA
Or you can communicate directly with the Internet, etc.
To do.   In the case of a purchase location device, an external infrared interface for the purchase location terminal of one embodiment.
A face port is similar to a credit card processing terminal, ISDN and
Log phone, or connected to a network interface to connect to the retailer's
Computer system, clearinghouse or bank computer system
, And with the customer's PDA. This equipment is owned by the retailer or issuing bank.
Minutes credit card processing terminal with new built-in wireless communication port
Can be used if you choose not to replace the model.

[0035]           9.Server computer   A server computer or server computer set is a server system.
The payment system aspect of the invention (here, "P
"DA payment system" and authorized transaction interface system (here)
Then, "Ticketdownload..com" and / or "Ticketdownload..com system" and
And / or "eTicket system")
. The system administrator of these systems is referred to herein as "Immtec".
In addition, as described below, the server system will include information such as prescriptions.
It also provides other trading functions, including maintenance and exchange of medical information.

[0036]       C.software           1.Infrared driver   The infrared software driver is the infrared hardware interface
Control function. The features of the infrared software driver program of the present invention are:
Without deviating from the spirit of the invention, any type of hardware system or
And equally applicable to operating systems. Infrared software drive
Iva is the CP of the personal computer between the PDA's infrared hardware interfaces.
Allows communication with U and / or with the host server system.

[0037]           2.ATM, credit card processing terminal, PDA               Interface software program   These interface software programs are: a) ATMs and banks
Between / clearinghouse (and / or host server system); b) ATM
Between CPA and PDA; c) Credit card processing terminal and clearing house / bank (and
/ Or host server system); d) credit card processing terminal and PDA
Between; e) PDA, infrared interface, credit card processing terminal, AT
Facilitates communication with M, or other infrared terminals.   Is the interface software program feature of the present invention the spirit of the invention?
Without deviating from any type of hardware or operating system
It is equally applicable to

[0038]           3.Interface software for PC   PC interface software program is; synchronization hardware
Between the PC and the portable PDA via the interface; via the synchronization hardware with the PC
Between PDAs of total size; P via sync hardware over the Internet
Between C and PDA; via infrared port, between PC and portable PDA; via infrared port
Via PC to wristwatch size PDA; infrared port via internet
Between the PC and the PDA via the network; or via the short distance data transmitter, the PC
And communication between PDA;   The PC interface software features of the present invention depart from the spirit of the invention.
Applies to all types of PCs and operating systems without
it can.

[0039]           4.Interfaces for major consumer accounting programs               software   As shown in FIG. 6, the present invention provides consumer accounting interface software 1
26a is provided. This is the data between PDA and various accounting programs.
Facilitates communication, synchronization and exchange of. These accounting programs are limited
I don't mean to, but Quicken 1998 for PC or Macintosh
+ Or have products like the Microsoft Money98 + program
. Typical software programs are, in particular, Windows-based PCs,
Macintosh computer, Windows CE / Pocket PC base
For PDA 127k and Palm OS 3+ based PDA 127j
Accounting interface.

[0040]         5.Interface software for the Internet   The PDA Pay eTicket system is already used by client and server computers.
Internet browser / interface software existing in
Programmed to use.

[0041]         6.PDA Pay & eTicket / mewallet ^TM for PC and PDA             System software   For example, in the personal computer (Fig. 6) and / or PDA device (Fig. 7),
Kets ("eTickets") 127b, 129h, banking information 127e, 129k
, Credit card information 127f, 129l, and medical information 127g, 129
Many types of data 127a to 127i, 129g to 129f) including m
Provide software to save. PDA Pay eTicket System / PC / Software
The software is installed on the user's personal computer. This software was
For example, a memory storage made up of a personal computer such as a computer hard drive.
User information in a database in the storage device (eg eTickets, user banking
Business information, credit card information and other relevant financial data and / or users
Medical information and other relevant information). This software
Allows all financials, after meeting the conditions of the appropriate security protocols
Personalized medical and eTicket data can be sent to the customer's PDA.

PDA Pay eTicket / mewallet ^TM system PDA software
Installed on. In one example scenario, the software is pre-installed by an authorized retailer, issuing bank, credit card company, or clearinghouse. It can also be installed by customers from their computer. This software provides an encrypted, secure and unique code 129f carried within each communication between the PDA and the other device.
Let it save. This software may also, for example, all bank account data 129k, security account data, credit card account data 1291, eTickets 129h, user ID, PIN1.
Many types of data 129g-129f, including 29a, other related financial data 129c, personal data 129g, etc., are to be stored securely by the PDA.

In this embodiment, in order to access and send data from a PDA device using PDA software, a user ID and / or PIN and / or fingerprint (as used herein “ The term "fingerprint" is intended to include a "push" of any finger, including the thumb, or another image), and / or biometric data 129n. The user has an ID and / or PI
You are given three chances to enter N and / or your fingerprint. ID or
If the PIN and / or PIN and / or fingerprint are correct, the user is allowed to access and send the data. If the ID and / or PIN and / or fingerprint are incorrect after three attempts, the software shuts down the PDA, locks it, and prohibits its use. Therefore, it is necessary to unlock the PDA. The PDA in this embodiment should be synchronized to the user's personal computer, an authorized PDA Pay & eTicket / mewallet ^™ system (sometimes simply referred to as a "system") service center or issuing bank or other issuing agency. Only unlocked by.

The PDA Pay & eTicket System / mewallet ^™ server software feature of the present invention is equally applicable to all types of server hardware and operating systems without departing from the spirit of the invention. The system server software is installed on the host system server. FIG. 8 shows an example of an example server software component. This system server software includes, among other things, firewalls 130a, 130b, encryption / decryption routines 131, website server software 132a, 132b, security checking routines 133a, directed purpose system device interface routines, PDA enums. Locking routine 133b, synchronization routine 133c to / from PDA, FSP, interface routines 133d, 133f to / from clearinghouse, wireless protocol 133g, micropayment receipt response routine 133j, bank account micropayment routine Thirteen
3k, via modem / Internet interface routine 133i, Tick etdownload..com interface routine 133e, authorized retailer accounts database 134a, Ticketdownload..com database 135a, unique user security code 134f, unique user security Code generator 136b, PDA system software 136d, PC system
Software 136c, authorized service center account database 134
b, user bitmap image 134c, biometric / fingerprint database 134d
, User name, ID, PIN database 134e, user's unique security code 134f, user's bank account data 137a, user's credit card account data 137h, user's intermediary account data 137c,
Other financial account data 137d, including user personal data 137e.

[0045]           7.Software for biometric device in PDA   The biometric interface software can be a fingerprint of the user, a PD
Optical information on A's screen or separate biometric hardware on PDA
-Provided to load the interface. User's own biometric data
The fingerprint / fingerprint is installed by the software when it is installed.
It is read and stored in the PDA. The software is then
When trying to access the DA or accessing any safety data in the PDA
When you tried to access the
Compare with the crest. If the fingerprint matches during three attempts, the software will
Authorize you to access the PDA Pay eTicket System software. Biometric
If the constant data / fingerprints do not match in 3 attempts, the biometric software will
Shut off and lock the PDA. Do not unlock locked PDA
I have to. The locked PDA is the user's personal computer, authorization system security
Unlocked only by synchronizing to the bank or issuing bank.   The biometric interface software features of the present invention deviate from the spirit of the invention.
Equally applicable to any type of operating system without getting out
It

[0046]           8.For storing and displaying images of PDA owners               Image storage software   One of the various existing image storage software systems is used
become. In this example, the owner's image is a bitmap image. The image is
User's PC to PDA, or authorization system outlet or bank
Is loaded into the PDA at. The picture of the PDA is "Photo
Accessed by opening "Lubam" and then displayed on the PDA screen
To be done. Image matching is an additional security pair that works in conjunction with anyone else.
It is a measure.   The PDA image storage software features of the present invention do not depart from the spirit of the invention.
And is equally applicable to all types of operating systems.

[0047]           9.PIN / user ID input / recognition software for PDA   In this embodiment, the PDA allows the user to use a pen pad, keypad,
You can use your personal identification number via the voice input device (built-in microphone).
Contains software that requires you to enter your ID name / code into your PDA.
Mu. Input software can be input from any of these input interfaces.
Recognize and approve. The user has to enter the correct PIN and user ID,
You will be given 3 trials. If the correct PIN and user ID are entered,
The software provides access to all PDA features, including the PDA Pay eTicket system.
Allow access. If your PIN or user ID is incorrect after three attempts
The software shuts down the PDA and bans access. Locked
The only way to unlock a PDA is a licensed bank or issuer or license
It is to synchronize the PDA with the user's personal computer at the system center. PIN
And user ID is also stored in the system software on the user's personal computer.
Saved.   As a user's option, PIN or user ID is not set in the non-guaranteed area of PDA.
It can be accessed at The system requires a PIN and / or user ID.
I need it.   The PIN / user ID input and recognition software feature of the present invention for PDA
Traits can be applied to any type of platform without departing from the spirit of the invention.
Equally applicable.

[0048]         10.PDA to identify correct PDA and user               Unique encryption security for all transmissions from               Software with code   The PDA encryption code software is the PDA and wireless interface of the user.
Unique encrypted security for attachment or embedding in any communication between chairs.
The security code is embedded. The user can change this code or
You cannot access or access the code. This unique code is
User's system on a personal computer and / or at the issuing bank or other issuing agency
-Embedded in software. Immtec Other Host System Day
The database is a database of all security that correlates with the distinguished name for the associated user.
Maintain tee code. This database is for all banks and clearing
Make a guhouse available. Each user, issuing bank or other issuing agency
To activate your own security code, the system software on your computer
Match software to Immtec. The PDA device communicates with the purchasing location terminal.
Secure Sockets Layer (secu Re socket layer (SSL) is used to communicate with each retailer's purchasing location device
. In this embodiment, the SSL layer is separate from the wireless communication method used.
It   Providing encrypted security code embedded software for PDAs
The distinctive feature is that it can be used on any platform without departing from the spirit of the invention.
Can be applied equally.

[0049]         D.Banking / Clearinghouse Infrastructure             1.For debit / credit card transactions                 Use the same infrastructure currently in place.   In this embodiment, as shown in FIG. 9, the present invention is a debit card / credit card.
Leverage existing infrastructure in place for credit card transactions. Purchasing place
The office terminal 141 is typically an analog or digital telephone line or satellite.
It communicates with the clearinghouse 142 via the. Next, clearing house
Credits the appropriate bank 144 or credit card company 143
Distribute the debit. The bank 144 or credit card company 143 then
Applies the appropriate credit or debit to consumer and retail accounts
To do. Micropayment will go to the server system host account 145
Deposited (this is described in more detail below). In one embodiment, PDA Pa There is no proprietary software for this aspect of the y eTicket system. PDA
Is done in the same way as a credit or debit card or check. Imm
tec or another host server system will give the user all clear
The security code that is the ID and PIN that match your
A daily update database 146 is provided. Clearing house
From the user's PDA at the time of purchase, as in the case of card and debit card processing
Electronically match the embedded security code sent.   In another embodiment (discussed in more detail below), the server system is
Controlling the processing of transactions between PDA, PDA and POS terminals to ensure proper clearing house
-Send the appropriate transactions to the system.

[0050]         E.The interface           1.PDA Pay eTicket System Process   As described below and as shown in Figures 10a-10c, an interface independent expression
Process is a PDA with a PDA Pay eTicket system or a PDA / wireless
Use the story. (This process is for brick mortar retailers or online
A retailer or a brick mortar financial service provider, or
Occurs while interfacing with online financial service providers.
This interface connection is via infrared. In another embodiment, the interface
Interface is via wireless or via hardwired sync. )   As shown in FIGS. 10a-10c, the user is a PDA (user I for each user selection).
Access 200 with or without D and PIN entry. The user
PDA Pay & eTicket via pen pad, keypad or voice 201 Select the System icon. System software is user ID and PI
Request N202. The user has a pen pad, keypad, or voice
Enter the user ID and / or PIN via 3. User ID or PI
If N is not correct (204), the system software determines that the user ID and
Request PIN re-entry. (User enters correct user ID and PIN
Three attempts are allowed to do so. ) 205. If the user makes three attempts,
If you fail to enter the correct user ID or PIN, the system software will
Shuts down PDA, locks it, and bans further access 206
.

If the user has entered the correct user ID and PIN 204, the system will display all active accounts 207. The user chooses a bank account or credit card account 208. The system software prompts the user to enter the amount 209 to send. The user inputs the transmission amount 210. The user then selects the "send" icon via the pen pad, keypad, or voice 211. The system software then sends the encrypted security code, user ID, PIN, and amount via the PDA's infrared interface to the purchase location infrared interface 212. The purchasing location interface sends the data to the appropriate clearinghouse system 213. If either the security code, ID, or PIN 214, 217 is incorrect, the transaction is rejected. The system tells the user the correct data 2
Allow 3 attempts to enter 15,218. If the user fails to enter the correct information, the PDA locks 216, 219. If the security code, ID, and PIN are all correct, but the user-selected account 220 does not have the desired funds, the transaction is rejected 221 and the user attempts another account 212 or disconnects. Have to or must do. If the security code, ID, and PIN are all correct and the user-selected account 210 has the desired funds, the transaction proceeds (222).

If the transaction proceeds (222), an electronic payment / transfer is made to the retailer's account 224 (223) and the debit is applied to the user's account 225. The financial service provider receives all transaction data 227. Micropayments may be sent from a financial service provider account 226-2 to a system host (Immtec) account 226, or micropayments may be sent from a user's bank or credit card account 226-1 to the system. It is transmitted to the host (Immtec) account 226.

The financial service provider then sends the transaction and update balance records to the purchasing location interface 228. The transaction record is then sent from the purchasing location infrared interface to the PDA infrared interface 229. P
The OP device also sends the update balance to the PDA via the infrared interface 230. In this example, the system software receives the transaction record, updates the appropriate account data 231 and completes the transaction 232.

[0054]           2.computer   In this embodiment, the personal computer is a hardwired sync interface, red
Interface with the PDA via one or both of the outside line interfaces
Configured and programmed to

[0055]           3.Credit card processing   In this embodiment, the credit card processing terminal has an infrared interface.
Configured and programmed to interface with a PDA.

[0056]           4.ATM   In the present embodiment, the automatic teller machine uses a PD via an infrared interface.
Configured and programmed to interface with A.

[0057]           5.Other infrared purchasing place equipment   In this embodiment, the other infrared purchasing location device has an infrared interface.
Configured and programmed to interface with a PDA.

[0058]           6.Accounting system interface for personal computer   In this embodiment, for example, Quicken or Microsoft Money
The una accounting program interface is a hardwired synchronous interface.
Interface with PDA via chair or infrared interface
. The data collected and entered into the PDA is synchronized with accounting software and
Apply to renew your account. The accounting software then went online.
Sync with your bank computer and update all your accounts. PDA is here
Again, sync with the accounting software on your PC, and everything on your PDA
Information is updated.

[0059]           7.Bank / credit card company / clearing house               ATM to / from   In this embodiment, the existing debit / credit card transaction interface is used.
The user's PDA uses an infrared communication device on the front of the ATM.
Data can then be exchanged with a system-enabled ATM. Then AT
M, using the examples of the ATM infrared interface aspect of the present invention,
Banking or clearinghouse systems, hardwire, analog
Alternatively, communication is performed via a digital telephone line or satellite. Bank or clearing
The house then credits and debits the appropriate bank or credit card company.
Debit shipping. The bank or credit card company can then
Apply Jit or Debit to the user's account. In all directions
All transactions are micropayed to Immtec or other host systems
To generate

[0060]           8.To / from a user / PC via the Internet               Bank / credit card company / clearing house   Online internet banking as client interface
Existing software that does this, for example, Quicken or Microsoft Mo Users exchange data with online banking using ney software
can do. The PDA synchronizes with the accounting software on the personal computer,
The software then interfaces with the online bank. This inn
With a face-to-face connection, the PDA communicates directly with the online bank via a personal computer.
There is nothing to do.

[0061]             9.Wireless PDA to / from Internet / Online retailers   Wireless PDAs use the same protocol as Internet-enabled wireless phones
. In this example, the Internet / online retailer
It has a website that runs the Internet Protocol. Everything in every direction
All transactions are micropayments to Immtec or other host systems
To generate. Trading works the same way as offline trading except for the interface
To do.

[0062]           10.To / from PDA and / or wireless telephone with wireless modem                  Bank / credit card company / clearing house (online                 In Financial Service Provider)   PDA with wireless modem with installed system software
Or a radiotelephone is shown in Figures 11a-11d according to an embodiment of the invention described below.
As with any direct online or internet sales data from multiple banks
, Credit card company and / or clearinghouse
Program to believe. As shown in FIGS.
In the exemplary embodiment, the user accesses the PDA 300. User PD A Pay eTicket system-Select Option 301. User select online sync
Select limb 301. The user then chooses the available optional
Choose one of them and sync with your financial service provider, or two or more financial
Synchronize with your service provider or use all financial services with which you have a financial relationship.
Service providers.

The PDA software requires the user to enter the user ID and / or PIN 302. The user has a pen pad, a keypad or a voice input device 3.
Enter the user ID and / or PIN via 03. User ID and / or PI
If the N304 is incorrect, the system software will use the ID and / or P
Request input of IN again. The user must have the correct user ID and PIN information 30
You are given 3 trials to enter 5. If the user does not enter the correct user ID and / or PIN after three attempts, the system software shuts down the PDA, locks it, and prohibits further access 306.

If the user enters the correct ID and / or PIN 304, the system displays all active accounts 307. The PDA then gives the user
Prompt to select one or more accounts to synchronize (308). A “Connect” icon appears on the display device and the PDA system prompts the user to press the connect icon 309. If the user presses the connect icon or key 310, the integrated wireless modem dials and attempts to connect to the appropriate online financial service provider 311. The PDA system software then provides the encrypted security code and user ID and PIN to the user registered financial service provider's system.
Send 312. The financial service provider's system receives the transmitted encrypted data and attempts to verify the accuracy of the transmitted information using the system's security protocol 313.

If any of the encrypted security code, ID and PIN 314, 317 are incorrect, the synchronization is interrupted (316, 319). The user is allowed three attempts to enter and send the correct ID and PIN 315,318. All encrypted security codes, IDs and PINs are correct (314,
317), the financial service provider (“FSP”) system checks the status of the user-selected account 320. Prompt the user to choose another account if the user-selected account is not running, or
Alternatively, the transaction 321 is ended.

If the user-selected account is active (320), the transaction proceeds. The PDA software 322 is a suitable online financial service provider system 32.
3, all relevant financial data is encrypted and sent to the online financial service provider 324, all relevant financial data is encrypted,
Sent from financial service provider 324 to PDA.

The system software updates all user-selected accounts 325 with the appropriate financial information. Micropayments have been recorded and Immtec (or other host system) account 32 from the online financial service provider.
7, 328. Micropayments are recorded and sent from the user's bank or credit card account to the Immtec (or other host system) account 326, 328. The financial service provider prompts the user to make an additional transaction via PDA 329 and causes the transaction selection to be displayed on the screen of PDA 330,331. The user selects a new transaction 333 or chooses to end the connection 332. If the user chooses a new transaction 333, this transaction takes place (334).
a, 334b, 334c). If the user chooses to terminate the connection, the connection between the PDA / telephone and the financial service provider is terminated (337).

[0068]             11.PC to / from the internet   Between the client PC configured in the system and the host system server
Interface connection through the Internet is a modem or other connection means (
Direct connection to server or any available high speed connection, including DSL
) May be used for dial-up. Enable 128-bit encryption
Browsers are preferred for security purposes. The present invention uses any special cipher
It is not limited to the activation level. The 128-bit encryption capability is as an example,
It does not limit the invention.

[0069]             12.Bank / credit card company / clearing house /                   From retailers   In an embodiment of the present invention, the present invention is applicable to retailers, banks, credit cards,
Debit Cards that already exist in
Use existing infrastructure to process card and / or credit card transactions
It By utilizing the existing infrastructure, the user of the embodiment of the present invention
The PDA is an infrared communication device and red according to the retailer interface aspect of the present invention.
Exchange data with the purchasing place device configured with an external line interface.   Where to buy equipment is then hardwired, analog or digital telephone lines,
Retailer's computer equipment, accounting system, via satellite or other wireless communication link.
System and communicates with an associated third-party financial system (eg, bank,
Communicate with a credit card, debit card or clearinghouse system)
I do. (Where bank or clearinghouse or bank system or
When we say a clearinghouse system, it means various types of third-party financial systems.
It should be understood that it includes a stem. )   The banking system or clearinghouse system then credits
And debit, as the case may be, with the appropriate bank, credit card company or other
Deliver to a financial institution. Bank, credit card company or other financial system
Will then provide the appropriate credit or debit to the user's and retailer's account.
Applies to counting.   In an embodiment of the invention, all transactions involving the system are accepted by the system.
Micropayments from financial service providers on the taker's side to Immtec
Is generated. All transactions involving the system will be processed in the user's bank account or credit
Cause the generation of micropayments from a credit card account to Immtec
Let

[0070]         13.Ticket download..com / to / from authorized online retailers                downloadtickt..com   In an embodiment of the invention, the system is a website (here, "Ticketdo wnload..com ”). In the embodiment of the present invention, Ticketdownload. .com downloads electronic tickets to a personal computer or PDA with wireless modem
Provide the ability to System software is the user's personal computer and PDA
To store electronic tickets (“eTicket”) in a storage device composed of
There is. The system software determines where the ticket is used (for example, air terminal
Le, train terminal, boat terminal, theater, cinema, museum etc.)
User request to infrared interface via PDA's infrared interface
The eTicket is sent according to the est.   Ticketdownload..com software engine supports all authorized ticket
Interface with brokers, airlines, theaters, travel agencies and more. eT icket can be accessed through the Ticketdownload..com internet site or directly
Typically purchased from any authorized ticket store or retailer. In the embodiment of the present invention
In fact, Ticketdownload..com is not a ticket broker broker website.
Instead, retailers and ticket brokers will be using PDA Pay & eTicket
/ Mewallet^TMUse the system to provide customers with a downloadable eTicket
It is a portal that gives you the opportunity to Described below and shown in Figures 12a-12d.
As such, the Ticketdownload..com software when used by authorized retailers
The core runs transparently to the user / ticket purchaser.

In the example shown in FIGS. 12 a-12 d, a user / customer (or simply called “customer”) searches the online retailer database for a desired ticket 400. The retailer displays the tickets available according to the customer's request 401. In the scenario shown in Figures 12a-12d, the retailer is authorized to provide a link that allows the retailer's customers to connect to the PDA Pay & eTicket / mewallet ^™ system to download the eTicket.

The authorized retailer site may or may not buy the ticket to the customer (402
) Prompt you to choose. If the customer chooses not to purchase the ticket 403, the customer may continue to search for another ticket at the retailer site 404 or terminate the connection with the retailer site 405.

If the customer chooses to purchase the ticket 406, the retailer site prompts the customer to enter payment information 407. Once the customer enters the required payment information,
And if the retailer site validates that information, the customer is
You are prompted to download an electronic ticket by clicking on the ticketdownload choice button or other type of choice button or link.
Once the customer clicks on the ticketdownload (system) choice button on the retailer site 408, the authorized retailer website is transparent to PDA Pay and eTicket / mewallet ^™ system server software at Ticketdownload..com. Access and submit the license code 409 to the Ticketdownload..com site with a request to download the appropriate eTicket. In this embodiment, the license code transmission is encrypted.

Ticketdownload..com site offers ticket transaction requests and licenses
Upon receiving the code 410, it is decrypted and the license code is verified against a database of license codes. If the system fails to validate the license code on the first try 411,
Ticketdownload..com requires repeated transmissions of license codes from the online retailer website 413. If the system is the second trial 41
If the validity of the license code cannot be confirmed in No. 2, access to the Ticketdo wnload..com server is denied (414).

If the system cannot verify the validity of the license code 415 sent to it, Ticketdownload..com will check the validity of the license code with the retailer's website and the retailer's website. Directly and transparently initiate communication with the customer via 416.

Ticketdownload..com provides the customer with payment information (either through the retailer's system or directly from the system software in their PDA or wireless telephone / PDA 417) through the retailer's system. If not, within that range),
Request to supply user ID, PIN and other security codes. In one embodiment, the payment information is provided by the customer to the retailer site only, and the retailer is responsible for paying the micropayment to the system host (ie, Immtec). In another embodiment, the customer provides payment information to the system, which carries the payment information to the retailer system.

The customer enters the customer's user ID and PIN, selects the payment method (check, credit card or debit card) and payment amount, and then via the internet interface or wireless modem interface 418 the retailer / Ticketdownload. Send this information to .com.

Ticketdownload..com receives payment and security data 419. T icketdownload..com is a security data system (ie Immt
ec) Compare with security data in database 420. If the system cannot verify the security data 421, Ticketdownload..com will ask the customer to re-enter the user ID and PIN code 422. The system gives the customer / user three opportunities to enter the correct security information. If the system is still unable to validate the customer-entered security information after the third attempt 423, Ticketdownload..com will
Decline authorization of transaction 424 and notify retailer system and customer.

If the system notifies the retailer system that it could not verify the validity of the security information, the retailer site may indicate that the customer may choose another means of purchasing the ticket 425. Let us know.

If the system is able to validate the customer-entered security information 426, Ticketdownload..com will request the credit / debit card clearinghouse 427 for an authorization code for the transaction. To do. Clearinghouses may not be able to obtain sufficient credits (432), have expired credit or debit cards (431), or may not have sufficient funds available to their account (433). Refuses approval.

If the system receives a negative transaction from the clearinghouses 431-433, Ticketdownload..com / retailer site will request another payment method from the customer 430. On the other hand, if the system receives the transaction approval from the clearinghouse,
The system allows the transaction to continue (434). Ticketdownload..com sends the transaction approval to the customer's PDA device via the retailer's web interface 440. Ticketdownload..com then sends the transaction approval to the retailer site 441.

In an embodiment of the invention, transaction payments are transferred to the retailer's account 442 through the clearinghouse. Payments are debited from the customer's account 443 through the clearinghouse. Micropayments are made from a retailer account 444 through a clearinghouse to an Immtec (or other host institution) account. In addition, micropayments are made through the Clearinghouse from the customer's account 445 to the Immtec (or other host institution) account.

In this example, Ticketdownload..com sends a unique security code for the eTicket to the online retailer 446. Ticketdownload..com
Sends all transaction data to the online retailer 447. The online retailer generates an invoice / receipt from the transaction data 448 and sends the invoice / receipt to the customer 4
Email to 49. Ticketdownload..com (or retailer), for example, electronically sends a confirmation copy of the eTicket to the retailer requesting the ticket for admission or purchase 450, and then, for example, electronically encrypted eTicket
To the customer's PC or wireless phone / PDA 451.

If the eTicket is sent to the customer's wireless phone / PDA, the wireless phone / PDA
The system software therein receives the eTicket and stores the eTicket in the eTicket database in the memory 452, 453 of the wireless phone / PDA. If the eTicket is sent to a system installed on the customer's personal computer, the customer / user will receive a PDA via a hardwire or infrared interface.
ETicket can be downloaded to the system, and the system software in the wireless phone / PDA receives the eTicket and stores the memory 45 in the wireless phone / PDA.
Save the eTicket in the eTicket database in 4-456.

14. PDA eTicket Exchange If a PDA user (eTicket customer) wants to exchange an eTicket downloaded to enter an event or purchase a product, the eTicket to the infrared interface via the PDA's infrared interface at the exchange retail location device. To send. In this example, the eTickets are transferred from the PDA to the exchange retailer with the same security measures used in the PDA payment system. Exchange of eTickets is described below for this example and is illustrated in Figures 13a-13c.

In an embodiment as shown in FIGS. 13a-13c, a user accesses a PDA or wireless phone / PDA 500. The user selects the PDA Pay and eTicket / mewallet ^™ system icon 501. The PDA system (or the system in this section) prompts the user to enter the user ID & PIN 502. The user inputs the user ID & PIN 503, and the system displays the PD
Attempt to confirm the validity of the input for the user ID and PIN stored in the memory of the device A. If the system cannot verify the validity of the user ID & PIN 504, the system will prompt the user for the correct user ID & PIN 505-.
Allow more than one attempt to enter 506. If the system still fails to validate the user ID & PIN after the third attempt, the system locks the PDA using software instructions 507a-507b. Various methods of unlocking the PDA are disclosed below.

If the system is able to validate the User ID & PIN 508, the system will display all active accounts 509 available to the user. In this illustrated scenario, the user selects eTicket option 510. Once the user has selected the eTicket option, the system prompts the user to confirm the particular eTicket that the user wishes to exchange (511). 13a-1
In the example shown in 3c, the system prompts the user to select the eTicket to be exchanged by listing all the eTickets available for exchange.

The user selects (512) eTickets that they wish to exchange. Once the user has selected an eTicket to exchange, the system prompts the user to send an eTicket 513. In the example shown in FIGS. 13a-13c, the system prompts the user to send the selected eTicket by prompting the send button or icon to send the eTicket 513.

The user sends the eTicket by pressing the send button or selecting the send icon 514. If the system recognizes the user's push of the submit button, or the choice of the submit icon, as a command, the selected eTicket.
And the associated user ID, PIN and encrypted security information are sent via the infrared interface configured on the user's PDA. The system sends the eTicket and associated user ID, PIN, and encrypted security information to the exchange retailer infrared interface device 515 via the infrared interface configured on the user's PDA.

The computer of the exchange retailer receives the transmitted eTicket data, and then transmits the transmitted eTicket data first by Ticketdownload..com,
Compare with data stored in its own database 516 by the exchange retailer's computer system. If the exchange retailer's computer system cannot verify the validity of the security information 517,522, the exchange retailer's computer rejects the attempt to exchange eTicket 520-521,525-526 (exchange The retailer's computer system uses eTickets and valid security information 518-51.
Give the user three attempts to send 9,523-524).

The trader's system compares the eTicket data for the user previously given by Ticketdownload..com / online retailer website with the eTicket data sent by the user. If the eTicket data 528 does not match 529, the eTicket is rejected (531-532). The exchange retailer's system provides the user with one additional eTicket exchange attempt 530. If the eTicket data does not match after the second attempt (531), the ticket is rejected and the exchange retailer either contacts Ticketdownload..com or sets this eTicket as a malformed ticket 532. Refuse.

If the eTicket data sent by the user's PDA was previously sent by Ticketdownload..com / online retailer site and matches the eTicket stored in the memory of the replacement retailer's system. In turn, the exchange retailer's system sends an eTicket acceptance to the user's PDA. Then, depending on the type of eTick et that has been sent, the PDA's system either marks the eTicket in PDA memory as “used”, or Withdraw some.

There are various types of eTickets. One type of eTicket is a single-use eTicket, such as a ticket to attend a particular entertainment event. Another type of eTick et is the fully variable eTicket. Such eTickets record the full amount. For example, there is a metro ticket that is initially allocated an amount of $ 10. The amount of money for each use of eTicket depends on the distance traveled by the user. If the user moves from A point to B point, the system will
Only reduce the amount of money left on your eTicket. If the user moves from point A to point C, the system reduces the amount remaining in the eTicket by the amount "Y". Yet another type of eTicket records the total amount that a given amount is reduced with each use. For example, the toll booth eTicket is initialized to $ 100. Each time the user passes the toll booth, the eTicket amount is reduced by a fixed amount, for example $ 2. Another type of ticket is recorded as a quantity, for example 10 tickets. This type of eTicket is identified by the eTicket retailer and is recorded by the system on the PDA when the user purchases the eTicket. In this embodiment, the system is programmed to interpret the eTicket type and mark it appropriately as "used" or reduce the remaining quantity upon replacement.

When the exchange retailer approves the eTicket, the exchange retailer's system sends an instruction to the clearinghouse to transfer the micropayment from the exchange retailer's account to the Ticketdownload..com account 534. When the exchange retailer approves the eTicket, the exchange retailer's system sends an instruction to the clearinghouse to transfer the micropayment from the user's account to the Ticketdownload..com account 544. When the exchange retailer approves the eTicket, the exchange retailer's system updates the exchange retailer database in its memory (539). After the exchange retailer approves the eTicket and sends the eTicket acceptance to the user's PDA,
Once the system within the PDA marks the eTicket in PDA memory as "used" or withdraws a portion of the full amount 533 of that eTicket, the system within the PDA synchronizes with the user's PDA. Generate information to synchronize the eTicket status in the memory of the user's PC during the next synchronization session between the user's PDA and the user's PC 543.

As mentioned above, in some embodiments of the invention, the eTicket may be used multiple times (535-538). If not 541, the system is eTicket
Mark used 542 on

[0096]           15.Unlocking routine for PDA using PC   As disclosed above, the system within the PDA will pay the PDA for further PDA payments.
There are many scenarios that lock you out of using eTickets. This is a security eye
It is done for the purpose. Proper security for a given user after multiple attempts
If the information could not be sent, the person trying to use the device is correct.
You may not be the proper owner. By locking the PDA device
, Prevent legitimate users from using the PDA device by unauthorized people
Be protected. However, if the user simply
Or if you have forgotten your PIN, the user can choose one of the methods described here.
One can be used to "unlock" the device. Here, if you are
, The examples provide all of the described methods to unlock locked devices
However, the present invention is limited to the examples that provide all of the unlocking methods described.
You can understand that it is not done. Without departing from the spirit of the invention,
One or some of the unlocking methods is optional among other unlocking methods.
Can be provided without providing the above method.

In an embodiment of the present invention, as described below, and in FIGS.
As shown at b, a PDA unlocking routine via the user's PC is provided. In this embodiment, the user turns on his or her own home or office PC configured with sync hardware 600. The user connects the locked PDA to the PC sync hardware 601. The user then P
Start the system software on the C602. The user selects “Synchronize with PDA” from the system menu on the PC 603.

The system on the PC initiates the synchronization routine and puts the user ID, P
Send IN and encrypted security code. The PDA is activated (605) and the system on the PDA receives the user ID, PIN and encrypted security code sent from the PC 606. The system on the PDA compares the sent user ID and PIN with the user ID and PIN stored in the memory of the PDA 607. User ID and PIN sent are PDA608
If it does not match the user ID and PIN stored in the memory of the user, the user is instructed to restart the synchronization process 609. If the user ID and PIN do not match after the second attempt on sync 610, then the user
You will be advised to contact customer support 611 at a tec or authorized service center.

On the other hand, the system on the PDA sends the transmitted user ID and PIN to the PD.
If the system in the PDA determines that it matches the ID and PIN stored in the memory of the A612, the system in the PDA sends the encrypted security code of the encrypted security code stored in the memory of the PDA 613. Check for a match with. If there is no match for the encrypted security code 614, the user is prompted to restart the sync process 615. If there is no match after the second attempt 616, the user is advised to contact Immtec or an authorized service center customer support 617. Cryptographic security code 618 sent and stored
If there is a match, the PDA system unlocks the PDA
The database information stored in A is synchronized with the database information stored in PC 619.

In another embodiment, the PDA sends the user ID, PIN, and encrypted security information stored on it to the PC. The PC system checks for a match between the user ID, PIN and encrypted security information sent by the PDA and the user ID, PIN and encrypted security information stored in the PC's memory. If there is a match, the PC system sends an unlocking key to the PDA. The PDA unlocks the PDA using the unlocking key it receives. In either embodiment, the PDA is unlocked. However, the user may, via independent means, obtain the appropriate user ID, PIN and / or security
Need to determine the code.

[0101]             16.PDA Unlocking Routine at an Authorized Service Center   As described below, and as shown in FIGS. 15a-15c, in an embodiment of the present invention,
, Provides PDA unlocking routines through authorized service centers. Figure
As shown in 15a to 15c, the representative of the authorized service center is
Turn on the PC with the 650 installed and configure the locked PDA with the PC651
652 connected to the sync hardware, online or directly online 652
Connect PC to Immtec server and Immtec database via
It Authorized service representatives can send the encrypted security code to the Immtec server.
You are prompted to send to the system on 653. System on Immtec server
Tries to validate the security code of the service center. SE
If the security code 654 is incorrect (655), the authorized service center
The data is instructed to send a retry 656. Immte after the second trial 657
c The system on the server cannot confirm the validity of the security code.
If not, access to the Immtec database is denied and authorized
The service center will contact Immtec or other customer support 658.
Instructed to do so.

Security code 65 sent by the system on the Immtec server
When the validity of No. 9 is confirmed, the authorized service center PC is allowed to access the Immtec database (660). The authorized service center requests access to the locked out user 662's data. The system on the Immtec server requires a user ID, PIN, username and / or fingerprint for the locked out user 663.

The user inputs the user ID and PIN to the input device configured by the computer 664 of the authorized service center. And / or the user places one finger on a biometric device configured with a computer 665 at an authorized service center. User ID
, PIN and / or biometric data / fingerprints are encrypted and sent to the system on the Immtec server 667 via the authorized service center computer, but are not stored in the memory of the authorized service center PC 666.

The system of the Immtec server receives the transmitted user ID, PIN, and / or biometric data / fingerprint data, then decrypts and stores them in the database 668 in the system memory of the Immtec server. Try to match the data about the associated user with the data that was sent.

If the transmitted user ID, PIN and / or biometric data / fingerprint 669 does not match the data in the Immtec database 670, then Immtec
The system on the server requests reentry and transmission of the data 671-672. If the data sent does not match after the third enforcement, the user's access to the data is denied and the Authorized Service Center is instructed to contact Immtec or another entity / customer service 674. .

If the data sent matches the data on the Immtec database 675, then the system on the Immtec server will use the unlocking routine,
The user ID, PIN, and unique security code are decrypted and sent to the user's PDA 676 through the authorized service center computer. The system software in the user's PDA receives and executes the unlocking routine, unlocks the PDA, and synchronizes the PDA's database with the Immtec database 677. Immtec ends communication 678. The PDA is disconnected from the sync hardware and is ready for use (679).

[0107]             17.Initial user setup at purchase   User purchases a PDA / wireless phone at any retail store that sells such devices
can do. Otherwise, the user will need to access the bank or other financial services
You can purchase a PDA / wireless phone through a lover (“FSP”). Yu
The user also calls a website (in the example, called "mewallet..com")
Through such devices that are pre-loaded and configured with system software
You can also purchase it. The system on the PDA / wireless telephone device has the following methods.
It can be set up and initialized through the gap. That is, official sales / service
Directly to Immtec at a center, bank or other financial services provider
Buy a pre-configured device on the connection or with the system preloaded
By doing so, it is set up and initialized.

[0108]               a.Certified service center   Users will have to install the system at an authorized sales / service center.
The following functions are performed when purchasing the installed device.   Authorized service center representative turns on PC with sync hardware
To do. Authorized service center representatives will synchronize new PDA / wireless phones with hardware
Connect to the Immtec server via a direct connection line.
. The authorized service center PC sends the encrypted security code to Immtec
Send to system on server.   The system on the Immtec server validates the encrypted security code.
Try to confirm. If the system on the Immtec server is encrypted security
・ If the validity of the code cannot be confirmed, on the Immtec server
The system instructs the authorized service center to try the transmission again. Immt
ec server system (or simply "server system")
You can check the validity of the security code sent even after the
If not, server system user setup routines and data
Deny access to the base and contact an authorized service center with Immtec customer support
Instruct them to contact you.

If the server system is able to verify the validity of the security code, the authorized service center PC will grant access to the server system user setup routine. Once the Authorized Service Center PC has been granted access to the Server System User Setup Routine, the Authorized Service Center Representative will provide the new user with online personal data, financial data through the Authorized Service Center PC System. Allow you to enter
It is then sent to the server system. The authorized service center computer does not capture user input data.

The server system may be configured such that the user has, for example, a user name, address, telephone number, birthday, social security number or other identifying name other than the United States, optional biometric data, and selective eyeball data. , Selective users. Request to enter bmp image, desired PIN, desired user ID, bank account number, credit, debit card number. The authorized service center representative validates the physical submission of the user's credit and / or debit card and enters the validation into the server system through the authorized service center computer.

The server system captures all of the user-entered data and validates it and adds valid information to the system database, as described further below. The server system attempts to validate the accuracy of the bank account data through the clearinghouse system.

If the server system cannot verify the validity of the bank account data, the server system sends a request for modified account data to the user through the authorized service center computer. If the server system is unable to verify the validity of the bank data after the second enforcement, the use of the data will be denied and the user will be instructed to contact Immtec customer service.

If the server system is able to validate the bank account data, the server system will populate the new user's data in the server system database with the validated bank account information. to add. The server system also attempts to validate the accuracy of the credit card and / or debit card information by sending user input to the clearinghouse system.

If the server system cannot confirm the validity of the credit card and / or debit card information, the server system may inform the user of the credit card and / or debit card through the computer of the authorized service center. Submit a request to correct the information. If the server system is unable to verify the validity of the information after the second attempt, the server system refuses further use of the information and prompts the user through the authorized service center's computer to use Immtec or other Send instructions to contact our customer service. If the server system confirms the validity of the information, the server system
Add validated credit and debit card information to the new user's data in the server system database.

The server system also attempts to validate the user-entered personal identification information through the clearinghouse system. If the server system is unable to verify the validity of the user-entered personally identifiable information, the server system notifies the user through the authorized service center computer to contact Immtec or other customer service.

If the server system is able to verify the validity of the user-entered personally identifiable information, then the server system will use its own cryptographic security for the user.
Generate code and add this unique cryptographic security code to the system server database. The server system then generates auto-run system software for the appropriate operating system for the particular device, which operating system identity may have been entered by an authorized service center or user. Send it directly to your PDA / wireless phone with encrypted unique security code as well as all your financial and personal data. In one embodiment of the present invention, financial and personal data is transmitted to the PDA / wireless telephone through the computer of the authorized service center and stored in the PDA / wireless telephone in encrypted form. The PDA / wireless phone receives the autorun software and the transmission of the encrypted data. The PDA / wireless phone runs the software and installs the system and data. The server system is disconnected from the authorized service center computer. P
The DA / wireless phone is configured in the system and is ready for use.

[0117]             b.Bank or other financial service provider   Preconfigured with installed system software in some cases
PDA / wireless telephones are available through banks or other financial service providers.
To be able to use. In addition, system software can
When the user obtains a PDA / wireless phone, the appropriate storage medium (
For example, install it on a CD-ROM, diskette or other storage medium.
It has become so.   The new user is required to select a user ID and PIN. the above
PDA's unique encrypted security code
Assigned in and installed in. The initialization process then
User's PC. The user does not have a personal computer, or
, Immtec or mewallet..com as an interface device
If you choose not to use the computer, the system-equipped PDA / wireless phone will
It can be initialized by row or FSP. If the initialization process is carried out at the bank,
Steps except interface and software installation used
Are the same. Below are examples of the initialization process in these scenarios.
explain about.

The user connects the synchronization hardware to the user's personal computer and turns on the personal computer. The user installs the system software on the personal computer. The user turns on the PDA / wireless phone and clicks on the system icon. The user connects the PDA / wireless phone to the user's personal computer via the synchronization hardware. The synchronization hardware in one embodiment comprises an infrared interface. The user activates the system software on the personal computer. The system software in the PDA requires the user to enter a new user ID and PIN. The user enters the user ID and PIN on the PDA. The PDA system directs the user and the PDA to synchronize the PDA with the system software on the user's personal computer. The PDA responds to the sync command by sending all the information in the PDA to the system software in the user's personal computer.

The system software in the user's personal computer allows the user to
Ask them to enter their financial account information. The user may be, for example, a name, address, telephone number, date of birth, social security number or other identification number outside the United States, selective biometric data, selective eye data, selective user.bmp image, Enter the desired PIN, desired user ID, personal, including bank account number and credit card number, financial account information. The system within the PC records the user's personal and financial account information and stores the information on the hard drive or other storage device of the personal computer 1062. The system software in the personal computer instructs the user to connect the PC to the Immtec server system, for example, by clicking on the "connect" icon displayed on the display monitor configured on the PC. The PC system software establishes a connection with the Immtec server system, for example through the Internet or a direct source connection.

Once the connection is established between the user's personal computer and the Immtec server system, the rest of the initialization is performed as described below. The Immtec server system receives the transmission of the user's data including the new ID, PIN and unique encrypted security code. Required data include, for example, name, address, telephone number, date of birth, social security number or other identification number outside the United States, selective biometric data, selective eye data, selective user. There are bmp images, desired PIN, desired user ID, bank account number, and credit card number. The server system takes this data, attempts to validate it in a manner similar to the validation process described above, and adds the information to the server system database.

Once the server system has validated the data and added it to its database, the server system sends a welcome message to the new user and any updates to the software. And send instructions on how to use it to your computer as a printable file. Once this welcome process is complete, the system server disconnects the user's personal computer and the PDA / wireless phone is configured in the system and ready for use.

[0122]             c.Order from the direct order website (pre-configured, pre-configured                 Installation, pre-initialization)   The user has set up a secure website for that purpose, for example
A website named "mewallet..com" has all the necessary personal and financial accounts
Pre-install the system and pre-populate the information by giving
You can order a PDA / wireless phone that has been initialized to. mewallet..com web
The site is also a system software to be installed on the user's personal computer.
It also facilitates the shipping of software and instructions to the user. All you need is a user
Installed the system software for the personal computer on the personal computer,
Then via a wired or infrared sync connection to the PC, and Immt
Imte PDAs / Wireless Phones Using Secure Connections to ec Server Systems
Synchronizing with the c-server system. User has a personal computer and Imm
Scenarios that want to use this computer as an interface to tec
An example of the installation process in is described below.

The user can either attach a pre-configured and pre-initialized PDA / wireless phone to the user's personal computer via the supplied synchronization hardware, or install a PDA / wireless phone infrared interface to the infrared on the user's personal computer. Turn to the interface. The user installs the system software on the user's personal computer and launches the PC system software. The user synchronizes the PDA / wireless phone with the system software in his PC. PDA / wireless phone,
Send personal and financial data to a PC. The system software in the personal computer is
It receives all of the data sent from the PDA / wireless phone and adds it to the PC system's database.

The user selects “Im
Click the "Connect to mtec" icon. The system software in the user's personal computer connects to the Immtec server system via a direct connection line, for example via an internet connection or via a modem.

The system software in the user's personal computer sends the unique encrypted security code and user data to the Immtec server system. I
The mmtecc server system uses the Immtec server
Compare with data on file in system database (this data is the person who was received, validated and saved when the user placed the user's order for the pre-initialized PDA / wireless phone) ).

If the data sent does not match the data in the server system database, the server system instructs the user to retransmit the data. If the data sent does not match the data in the server system database after the second attempt, the server system prompts the user to Im
Instruct them to call mtec or other customer support.

If the data sent matches the data in the server system database, the server system updates the database with information about the startup and any other new user data, and the user's personal computer. Send the initialization code to the system software in. This enables all features in the system software within the PDA / wireless phone.

The server system then sends a welcome message to the new user, any updates to the software, and instructions to the user. The server system then disconnects from the user's personal computer. The user's PC then directs the user to synchronize the PDA / wireless phone with the system software in the user's personal computer. Once the user has synchronized the PDA / wireless phone with the system software in the personal computer, the PDA / wireless phone with the system is ready for use.

[0129]             18.Replacement of lost or stolen PDA / wireless phone   I lost my PDA / wireless phone with system software installed.
Rui, if stolen, must report it to Immtec. Im
mtec then locked the user's use of the system and lost PDA /
Contact all wireless phone credit card and financial service providers
To do. In an embodiment of the invention where the PDA comprises a biometric reader, the PDA
The data stored in the memory device configured in is stored in an encrypted form,
Fingerprint-like biometric readings that match the encrypted biometric data stored on this device.
Only Tori unlocks and decrypts the data. In such an embodiment
Anyone who steals or discovers this device can use it.
Absent. In another embodiment of the invention, the user ID and PIN are in encrypted form.
The user ID and P that are stored in
You must enter IN. The encryption of the data stored in the device is performed by the user I
It makes it difficult to reverse engineer the matching of D and PIN.   To replace a lost or stolen PDA / wireless phone, the user must
Purchased a PDA / wireless phone with system software installed
You can do it in the same place. PDA / wireless phone at authorized service center
The exchange is typical.

[0130]     a)Exchange of authorized sales / service centers, banks or financial institutions   A system that has been lost or stolen at an authorized service center, bank or financial institution.
To replace a mobile-enabled PDA / wireless telephone device, the user must
Go and apply for exchange equipment. The term authorized service center is used below to refer to banks and
It should be understood that is equally applicable to exchanges at financial institutions.

The user gives the authorized service center / bank / FSP representative a personal image identification. The representative of the authorized service center uses the computer of the center as an Immtec server.
Connect to the system, for example via the Internet or via a direct line. The authorized service center sends the encrypted security code to the server system. The server system attempts to validate the authorized service center security code. If the server system cannot verify the validity of the security code, the server system directs the authorized service center to retry the transmission. If the server system is unable to verify the security code after the second attempt, access to the server system and its database by the authorized service center to which it is connected is denied. The server system directs the authorized service center to contact Immtec customer support.

If the server system is able to verify the validity of the security code, it causes the authorized service center to enter the user ID and PIN for the user via its computer. Give instructions. In this embodiment, the server system also prompts the user to enter the user's fingerprint (or any fingerprint or some combination of fingerprints) via the biometric reader configured on the authorized service center computer. Give instructions. User input data is sent to the server system and is not captured by the authorized service center computer.

The server system attempts to validate the user-entered identification data with the identification data for the corresponding user stored in the database of the server system.
When a user registers a PDA / wireless device that is currently lost or stolen, information about the corresponding user is saved. If the server system cannot verify the validity of the user identification data, the server system prompts the user to re-enter the information. If the server system cannot verify the validity of the user identification after the second attempt, the user is instructed to contact customer service. If the server system confirms the validity of the user identification information, then in an embodiment of the invention, the server system may then provide an image of the user whose information is registered with the server system, eg ,. Send the bmp image to the authorized service center's computer display monitor to instruct the authorized service center representative to confirm that he or she replaces the PDA / wireless device of the individual whose image is on the screen.

The authorized service center representative compares the previously registered display image of the user with the personal image present on the screen. If the images do not match, the authorized service center representative indicates to the server system and the server system directs the user or authorized service center representative to take appropriate action. If the images match, the authorized service center representative indicates to the server system. At this point, the server system sends an authorization to the authorized service center representative and gives the user a PDA / wireless telephone capable of switching systems.

Once the approval is complete, the authorized service center representative will notify the new PDA
/ Connect the wireless phone to the authorized service center computer system via sync hardware or infrared interface and send confirmation to the server system that a new PDA / wireless phone has been connected. The server system generates a new unique encrypted security code for the user and adds this new code to the user's data in the server system's database. The server system sends to the PDA / wireless phone the system software configured for the appropriate operating system along with any encrypted or proprietary security code attached or embedded, as well as all financial and personal data.
The server system updates its database with the exchange user data, unlocks the use of the new device and sends this information to the clearinghouse, banks and financial service providers. Server system disconnects from authorized service center computer, PDA
/ The wireless telephone is configured in the system, enabled and ready for use.

[0136]           b)Exchange through direct order website   The procedure for replacing a lost device through the direct order website is covered by an authorized service.
Initialization process through Scenta and first through direct ordering website
Similar to the aging process.   To replace a lost device through the direct order website, the user must
From your computer with the system software installed, for example,
After that, connect directly to the ordering website (here called "mewallet..com")
It The mewallet..com page says "Lost or stolen PDA / wireless
Here are the options, including the "exchange talks" option.

In order to replace a lost device, the user has to say “A lost or stolen PDA.
/ Replace wireless phone "icon. Direct order website server
The system then gives the user a name, address, social security number, user ID, PI.
Instruct them to fill out a secure page with information including N and the type of equipment lost or stolen.

The direct order website (mewallet..com) checks whether the user input data provided in the input form matches the data maintained in the server system database. If the data do not match, the direct order website (me wallet..com) prompts the user to correct the data and resubmit. If the server system fails to get an exact match of the user input data after the second attempt, mewallet..com requires the user to call the customer to the service.

If the server system is able to obtain an exact match of the user input data with the data stored for the corresponding user on the system server database, the server system will place the order. Acknowledge and, in response, authorize shipments (eg, overnight delivery) for PDA / wireless phones with system software installed. The server system notifies the user that the replacement PDA / wireless phone is in transit and will arrive on the next business day, and the replacement transaction is complete.

When the user receives the exchange PDA / wireless phone, a set of printed instructions arrives with the device at the user's location and / or the instructions are emailed to the user. The user is instructed to or connects the PDA / wireless phone with the system software installed on the personal computer to the system software installed via the hardwire synchronizer or infrared interface device. The user activates the system software on the personal computer. The user
Synchronize the PDA / wireless phone with the system software on the PC. The system software on the user's personal computer allows the switching device to
Recognize it as a wireless phone and instruct the user to enter their user ID and PIN. As mentioned above, the PC system attempts to validate the user ID and PIN. If validation fails after the second attempt, the user is instructed to contact customer service and the system software is inaccessible.

If the validation is successful, the system software in the user's personal computer sends all the data in its database to the system software in the new PDA / wireless device. The user then clicks "Im" on the display monitor screen of the user's personal computer.
The system will prompt you to select the "Connect to mtec" icon. By clicking on this icon, the system software in the user's personal computer establishes a connection to the server system, for example via a direct line via the modem.

The system software in the user's personal computer then sends the server system its own encrypted security code and user data. The server system then compares the transmitted data with the data stored for the corresponding user on the server system database. If the data sent does not match the database information, the server system will instruct the user to retransmit the data. If the retransmitted data still does not match, the server system then directs the user to call customer support. If the data sent matches, the server system updates its database with the exchange user data, unlocks its use for the new device, and clears this information for clearing houses, banks and financial services. -Send to the provider.

The server system then sends the initialization code to the system software in the user's personal computer. This initialization code is used by the system in the PDA / wireless telephone.
Enable the software. The server system then sends a thank-you message to the user, software update data to the user's PC, and disconnects from the user's PC. The PC system then directs the user to synchronize the PDA / wireless phone system with the system software in the user's personal computer. The user is P
Synchronize the DA / wireless telephone system with the system software in the user's personal computer. Then, the system-enabled PDA / wireless telephone is ready for use.

[0144]             c)Direct telephone exchange from Immtec   The user can make a direct phone call from the system host (eg Immtec).
The PDA / wireless device can then be replaced. Similar to the exchange process, or
Some exceptions are described below.   Once the Immtec host server system has been
The validity of the information provided and ready to ship a new device.
For example, the Immtec server system is the installed system software.
Prepare a replacement device by installing
Completely configure the device with all personal and financial data of. However, Immt
ec uses the system soft air for PDA / wireless device and Immtec
Set to be locked in the database.   Once the user receives the switching device, the user
Instruct to connect the device to the user's personal computer with the software pre-installed
To be done. The device is equipped with a hardwire synchronous interface or an infrared interface.
"Connected" via chair.   Once the user boots the computer and enters a valid user ID and PIN
System software on the user's personal computer,
To send all data from the source to the PDA / wireless device system software
.

The user then selects the “Connect to Immtec” icon on the display monitor screen of the display device configured with the user's personal computer. "Im
By selecting the "Connect to mtec" icon, the system software in the user's personal computer establishes a connection with the server system, for example via a direct line via a modem. Once the connection with the server system is established, the system software on the personal computer sends its own encrypted security code and user data to the server system. As mentioned earlier, the server system attempts to validate the information. Once the information has been validated, the server system updates its database with exchange user data, unlocks usage and sends this information to the clearinghouse, bank and financial service providers. The server system sends the authorization code to the system software on the user's personal computer. The system software on the user's personal computer receives the authorization code and unlocks and enables the system software in the PDA / wireless phone. From this point on, the user synchronizes the new device with the system software on his personal computer, as described above. If the user does not have access to the personal computer when the user receives the exchange, the user calls Immtec Customer Service. Immtec Customer Service requires a name, address, social security number, user ID, PIN and code to be printed on the PDA / wireless phone. Immtec Customer Service Representative is
Instruct the user to turn on the switching device.

Once the user has turned on the switching device, the Immtec Customer Service Representative will instruct the user to select the “System” icon on the display screen of the switching device. Once the user selects the "System" icon, the system software on the switch opens the PDA Pay & eTicket / mewallet ^™ system. The Immtec Customer Service Representative then instructs the user to select the "Security" icon. Once the user has selected the "security" icon, the system software on the device prompts the user to enter an authorization code. The Immtec Customer Service Representative gives the user an authorization code to enter into the PDA / wireless device. Once the user has entered the authorization code on the PDA / wireless device, the system unlocks the device and the device is ready for use. The Immtec Customer Service Representative then
Send unlocking approval to the database.

[0147]           F. Designated purpose system device   1. Overview   In the context of the present invention, the term "designated purpose" is used here to describe the purpose of the device.
Electronic transactions of the type indicated, for example electronic money, electronic tickets or other electronic
It means storing, sending, and processing lookups. Designated purpose device
Any in 19a-19c design, including watch size devices or other handheld devices
Shape or size. The "specified purpose" device is a
You can store, send and process many types of transactions. Do not use mobile phone communication
Rui holds a calendar or is implemented by a PDA and / or cell phone
In order not to perform a function that performs something like another type of special function,
It is called a "specified purpose" device.   In this embodiment, the Directed Purpose System device is one or more ties.
Store data (typical data structures and relationships are described below). For example
, A memory storage device configured by a designated purpose system device, for example, 1 of electronic currency
Save up to $ 1,000 or equivalent in electronic currency of any country
Can be configured as

Embodiments of system embodying features of the present invention provide for international currency exchange and / or conversion. One way currency conversion works is for the server system to keep a record of each user's account in the first currency. The server system is
A payment request is received from a merchant POS terminal for payment in a second currency. The server system converts the requested amount in the second currency into the corresponding amount in the first currency. The server system authorizes payment of an amount equal to the requested amount in the second currency and reduces the total available currency for the user / user by an amount equal to the requested amount in the first currency. Send instructions directed to the device. Upon receipt of the instruction, the PDA or PayStick will send the permission to the seller to pay an amount equal to the requested amount in the second currency, and the entire amount of the user equal to the requested amount in the first currency. Reduce available currencies. The vendor's system sends the authorization to the server system. The server system receives the authorization and then
Withdraw from the user's account balance by an amount equal to the requested amount in the currency of.

One example of a Directed Purpose System device is referred to herein as a PayStick ^™ . The Directed Purpose System device is configured to hold electronic tickets, for example, multipurpose tickets used in commuter trains, buses, trolleys and subways. The Directed Purpose System device can also be configured to be utilized as an electronic key or an identification confirmation device. Directed Purpose System devices may also be configured to store credit card data or bank account data. The Directed Purpose System device may also be configured to store medical data, insurance data or other personal data of one individual user. The data in the device can be easily viewed and updated by synchronizing the device to a computer system equipped with a hardwire interface or short range data transmission means or an infrared interface.

An example of a Directed Purpose System device is comprised of the following hardware components, as shown in Figures 19b to 19c and 20b to 20f. That is, the infrared interface 1100, the hardwire synchronization input port 1101, the internal memory (
RAM and ROM / eeprom) devices 1102 and 1103, on / off operation button 1104, biometric device 1105, send / receive button 1106, battery 1107, short range data transmission hardware (option) 1108, small LCD display screen 1109, Digital signal processor or microprocessor 1110, 4-button array 1111 and optional solar cells 1112. Memory storage is used to store one or more types of data. These data include, but are not limited to, eTickets, electronic currencies, personal health information, personal insurance information and / or other discrete amounts of data and / or instructions (eg, "unlocking").

An external view of another embodiment of the Directed Purpose System device is shown in Figures 19a-19b. As shown in FIGS. 19a-19b, the device is a small (eg, 2 line) multi-character LCD display 1109, 4 buttons (input keys) 1111.
, An optional biometric chip 1105 and an infrared transceiver 1100. On the back of the same embodiment of the device, as shown in FIG.
And two additional buttons (input keys) 1104, 1106 and scroll button 1114 are provided. These six buttons 1104, 1106, 11
11 can be used to act as an input key, which allows the user to enter their user ID, PIN and also as a selection mechanism to select the prompt that appears on the liquid crystal display. is there.

In one embodiment, the serial interface 1101 is a USB,
Connect the dedicated end to the standard A terminal that connects to the designated purpose system unit and computer. One of the pins on serial interface 1101 provides power to recharge battery 1107. The solar cell 1112 is
This is an alternative method of recharging the battery 1107.

2. Software An embodiment of software for a Directed Purpose System device (alternatively referred to herein as PayStick ^™ ) provides the following functions: That is, the ability to receive, store, retrieve, and send a unique encrypted security code input, the ability to perform a synchronization routine to update system software, the user ID, P
The ability to receive, store, retrieve, and send IN inputs, one or more types of data (including but not limited to eTickets, e-currencies, debit cards, credit cards, e-coupons, (Including branded seller's unique code, unique encrypted security code for the device, personal medical information, personal insurance information, identification information and / or other discrete amounts of data and / or instructions), Functions to save, read, send, update, calculate stored electronic money with corresponding adjustment values, communicate micropayments, update, receive, save, read, send biometric data Function, interface with liquid crystal and other display devices, digital clock display of date and time on LCD, low battery status With the ability to display status, interface with biometric readouts, interface with microprocessors, interface with hardwire ports, interface with short range transceiver devices such as infrared transceivers or Bluetooth transceivers. is there. Once turned on, the Directed Purpose System device will be installed on the host system with the mewallet ^TM system software installed without the user having to scroll through and select a payment method, ticket type or other transaction type. From the connected point-of-sale terminal, it is possible to respond to a properly coded secure demand for currency or eTicket.

3. PC Software The system software described above for a personal computer can interface with a Directed Purpose System device in a limited manner. It can synchronize all the data that the Directed Purpose System device can store. System software for personal computers can also be synchronized with online financial service providers to download electronic money. It can also be synchronized with an online ticket provider to download electronic tickets. It may also store a copy of all transactions sent to or from the Directed Purpose Equipment. It can set the date and time in the built-in Directed Purpose System device clock. It can also store all personal, security and financial data and synchronize some personal and security data with Directed Purpose System devices.

4. Server system software Server system for interfacing with designated purpose system devices.
Software is Unix (registered trademark) and Microsoft Windows 20
00 (registered trademark) / NT4 + operating system. However, those skilled in the art will understand that the operating system embodying the present invention is not a limitation of the invention. The present invention may be programmed to operate on other operating systems without departing from the spirit of the invention. The server system software is for use on a centralized host system server (e.g., accessible through the Internet).
However, the server system software may also run on computers running individual banks, financial institutions, etc. Server system software can be firewall, encryption /
Cryptanalysis Routine, Website, Security Checking Routine, Directed Purpose System Device Interface Routine, PDA Unlocking Routine, Currency Conversion Routine, Directed Purpose System Synchronization Routine, Financial Service Provider and Clearing Interface to / from house
Routines, Wireless Communication Protocols, Micropayment Receiving / Verifying Routines, Micropayment Routines for Bank Accounts, Interface Routines via Modem, Ticketdownload..com Interface Routines, Authorized Merchant Account Database, Ticketdownload..com Database, Own User security code, unique user security code generator, designated purpose system device system software, PC system software, authorized service center account database, user bitmap image, biometric /
Fingerprint database, user name / ID / PIN database, user / unique security code, user bank account data, user credit card account data, user brokerage account data, other financial account data,
User / personal data, user / customer-specific receipt advertisement data processing (reception, confirmation,
(Save, compare, send).

5. Directed Purpose System Device Interface Embodiments of the Directed Purpose System include, among other things, a hardwire interface for communication and / or synchronization with a communication device of the following type: a personal computer.
An infrared interface for communication and / or synchronization with any device having an infrared interface and / or an interface for other short range data transmission to / from any device having short range data transmission capability ( For example, one or a combination of "Bluetooth") is used to communicate with other devices. Examples of Directed Purpose System devices are hardwire, personal computers with short range data transmission capability or infrared interface, purchase location devices with infrared interface, purchase location devices with short range data transmission capability, authorized financial service providers. Or interface with a number of other devices including one or more of ticket distributors, system enabled PDAs / wireless phones.

A) Personal Computer Interface FIG. 16 is a high-level functional flowchart showing a personal computer system interface processing example with the designated purpose system device in the embodiment of the present invention. FIG.
When interfacing with a personal computer requiring a hard-wired synchronization interface, the user connects the Directed Purpose System device directly to the personal computer, and then turns on the personal computer 1200, as shown in FIG. When interfacing with a personal computer equipped with either an infrared transceiver or a short range data transceiver, the user turns on the personal computer and then points the infrared transceiver or the short range data transceiver to the corresponding device on or near the personal computer. .

The user executes the PDA Pay & eTicket / mewallet ^™ system software 1203 on the personal computer. This system software will prompt the user for the user ID, PIN1205, in the appropriate space on the interface screen on the PC.
Request to enter. Then, the user is prompted to click the “Enter” icon 1208. The system software is the user ID entered by the user.
, PIN with the user ID, PIN in the system database 1211. If the entered user ID, PIN does not match the stored user ID, PIN 1213, the user is prompted to re-enter the data 1215. If the system is unable to validate the information after a preset number of attempts (eg, 2), the system denies access to the PC system software. The PC system software directs the user to contact customer service 1218.

If the system is able to verify the validity of the user ID, PIN 1221, the PC system then selects the available transaction and action options 12.
24 shows a list. Such options include, for example, cash downloads, ticket purchases / downloads, personal health care, insurance, emergency data, and synchronization with designated purpose system devices. The system prompts the user to choose one of the options. If the user selects the option 1226 "Synchronize with the Directed Purpose System Device" at 1229, the system directs the user to direct the Directed Purpose System device to the short-range wireless interface configured on the PC1231. The system prompts the user to click the "sync" icon on the PC display screen 1234. The user points the designated purpose system device at the short-range wireless interface configured on the PC 1237. The PC system and Directed Purpose System device software synchronize via short-range wireless communication 1240. One skilled in the art will appreciate that the options described below can be equally applied to system-enabled PDA / wireless telephone devices without departing from the spirit of the invention.

1) Cache Download FIGS. 17a to 17d are high-level functional flowcharts showing an example download eCash process for the example designated purpose system device in an embodiment of the present invention. Figure 1
7a to 17d, the user selects the cache download option 1300.
If selected, the PC system prompts the user to confirm the financial service provider from a pull-down menu or user input (1303). Once the user has selected a particular financial service provider (1306)
, The PC system establishes an online connection to the system or website of the online financial service provider via the Immtec server, for example, via the Internet (1309). Once connected, PC
The system reads (1311) from its database and sends the user identification, security information (eg, associated account number, user ID, PIN) to the financial service provider's system (1314). The financial service provider's system seeks to validate the information. If the financial service provider's system cannot verify the validity of the information (1320), the user is prompted to re-enter the data (1323). Once the user has re-entered the data (1326), the PC system re-transmits the data (1311).
If the financial service provider's system fails to validate the information after a preset number of attempts (eg, 2) (1320), the financial service provider's system denies access to the PC system. To do. After receiving a negative 1329, the PC system directs the user to contact customer service (1332).

Once the financial service provider's system has notified the PC system that the identification / security information has been validated (1335), the PC system requests a list of available financial transaction options for the user. (1338). The financial service provider's system retrieves information (1339) about available options for the corresponding user and generates a display of available options 1344 (1341). One such option is "cache download"
Is.

If the user selects cash download 1347, the financial service provider, or PC system generating the selection of the amount in another embodiment, provides an input field and asks “How much cash, today, Do you want to download? "Ask the user 1350. The user has a list 135 of preset amount options.
Select the amount 1356 from 3 or enter the amount. In an embodiment, the amount is limited to 1000 US dollars or a non-US currency equivalent. The PC system informs the financial service provider of the selected amount via the Immtec server (1359). The financial service provider may use the user's account 13
Check available funds in 62. If the amount of available funds is less than the requested funds 1368, the financial service provider system notifies the PC system 1365 of this,
The user is prompted to request a lower price or to contact the customer service 1374, 1371 of the financial service provider. Requested funds (including micropayment amount) are available (1377)
In some cases, the PC system, the financial service provider, sends the selected amount through the host system, eg, Immtec server 1380. At the host system, the host server system calculates the micropayment percentage, deducts this amount from the requested amount 1383, and transfers the deducted amount to the host system micropayment account 1385. The host server then sends a PC to the user's intended purpose system device
Send the balance through the system. The PC system displays all the details of the transaction 1390 and then closes the connection with the host server and financial service provider 1399. In another embodiment, electronic money from a financial service provider is sent to a host computer available to the user via the Directed Purpose System device 1397.
It may be transferred to the user's account 1396 on the server. Or, in another embodiment, the financial service provider system calculates a financial service provider micropayment amount and transfers this amount to its own account. Alternatively, in another embodiment, the financial service provider system calculates (1400) user micropayments and
From the user's account to the host system (eg, Immt)
ec1403) instruct to send the calculated user micropayment amount to the account. The financial service provider electronically sends the requested amount of electronic currency to the synchronized Purpose Purpose System device 1409 through the user's PC system. The financial service provider deducts the user's account by the amount of electronic currency sent and the amount of the user's micropayment. The PC system generates a receipt for transaction 1415. The PC system stores the transaction receipt in the memory of the user's PC and sends a copy of the receipt to the financial service provider system. At this point, the transaction is complete (1418) and the connection between the user's PC and the financial service provider system can be terminated (1421). The Directed Purpose System device contains the appropriate amount of electronic currency and is ready for use (1412).

In another embodiment of the Directed Purpose System device, the financial services provider sets up a separate account for the user, specifically the Directed Purpose System device. In this example, the financial services provider sends "currency" to the Directed Purpose System device account 1424 for a particular user. In this example, the financial service provider may specify the purpose-specific system device 142.
7, 1436 sends the accounting of the transferred amount, but the device uses electronic currency 143
Do not "hold" 9. In such an embodiment, the electronic currency exchange is activated by communication between the purpose-built system device and the over-the-counter device. However, the actual transfer of funds is between the corresponding user's Directed Purpose System Equipment account at one particular financial service provider and the account for the reseller at that or any other financial service provider. To be achieved.

2) Ticket purchase / download After the user's PC system is started, the PC system offers various options (one is "
Buy ticket, download ”). If the user selects the "Buy, Download Tickets" option, the PC system formats the display of choice choices including the choices for the Internet ticket website where the user previously purchased the ticket and the "Others" choice. And generate. The process flow for downloading an electronic ticket to a Directed Purpose System device is similar to that described above for a PDA / wireless device and shown in Figures 12a-12d. If the user selects one of the particular internet internet websites from the list of choices, the PC system connects to that website via a modem or other internet connection. If the user selects the "other" option, the user is prompted to enter a search term or website address. Once the user has verified a particular website, the PC system establishes a connection with the verified internet ticket website. In an embodiment of the invention, the internet ticket websites available for selection through the PC system are limited to online ticket vendors authorized to interact with the system. Postponement of a "license" to a particular online seller, among other things, allows the online ticket seller to register with the server system host (eg, Immtec) and provide all necessary information, authorization, and The server system will settle and transfer the amount to the merchant's account and then deduct the micropayment amount from such transfer, or thereafter, the seller's account to the server system host's account. It is necessary to transfer the micropayment amount to.

Once in the verified Internet Ticket Website, the user searches the online merchant website / database for the desired ticket. The merchant's website displays the tickets and prices available according to the user's request. The user can stop buying tickets, continue searching, end the connection with the website of a particular seller,
You can choose to go back to the C system. Once the user has indicated the option to purchase one or more tickets, the seller's system requests payment information. To pay for the ticket and download the ticket, the user clicks the "PDA Pay & eTicket / mewallet ^TM System" option button on the Authorized Distributor site. Authorized Distributor Website, Internet or other connection (Ticketdownload..com)
Transparently access the server system via and send the license code. The server system (eg Ticketdownload..com) receives the transaction request and the license code. The server system attempts to validate the license code sent to it. If the server system is unable to verify the validity of the license code sent to it after a preset number of attempts (eg, 2), then the distributor may choose the server system Ticketdownload.com. Refuse to use the feature.

If the server system can confirm the validity of the license code, the server system Ticketdownload..com mechanism will license the distributor to
Send code validation and transparently open communication directly with the user through the seller's website. The server system Ticketdownload..com mechanism (or, in another embodiment, the merchant's website) stores the payment information, user ID, PIN and security code from the user and his PC and / or his system device. Request. The user enters the user ID, PIN, payment method (check, credit card or debit card) and the amount to be paid. The user
Select a send option that causes the PC system to send the input data and other information to the seller / Ticketdownload.com mechanism via the Internet interface.

The Ticketdownload..com mechanism attempts to validate the information about the corresponding user on the server system database after receiving the payment and security data sent. If the server system is unable to verify the validity of the information after the planned number of attempts (eg, 3), the server system rejects the transaction and directs the user to the merchant's website. Return to management. The seller then informs the user of the choice of another ticket purchasing means.

If the server system can verify the validity of the information sent, the server system Ticketdownload..com mechanism will provide the financial services clearinghouse with information about the transaction. , Request approval (eg, in the form of an authorization code) for a transaction from the Financial Services Clearinghouse. Financial services and clearinghouses, in particular, do not have enough credit available,
Certain transactions may be rejected for reasons including that the credit or debit card has expired or the designated account does not have sufficient funds available.

If the financial services clearinghouse refuses to approve a particular transaction, the server system Ticketdownload..com mechanism (or, in another embodiment, the merchant website) may give the user another payment method. Request selection and identification. If the financial services clearinghouse approves the transaction, the server system
The Ticketdownload..com mechanism / merchant sends approval of the proposed transaction to the user via the online merchant's web interface and then to the online merchant, eg, by sending an authorization code. The server system calculates the merchant micropayment. In this embodiment, the server system also calculates user micropayments. The server system Ticketdownload..com then forwards to the financial services clearinghouse the payment of the amount of the transaction from the user-specified account to the seller's account and debits the amount from the user-specified account. From the seller's account to the server system host's account (eg I
mmtec's account) to transfer the calculated amount of seller micropayment, and instruct to deduct the amount of seller micropayment from the seller's account, and in this embodiment, from the user's account to the server system. Transfer the calculated user micropayment amount to the host's account (eg, Immtec's account) and instruct to deduct the user's micropayment amount from the user's account.

The server system Ticketdownload..com mechanism generates a unique security code for a particular eTicket and sends it to the online merchant. The server system Ticketdownload..com mechanism sends all transaction data regarding ticket purchases to the website of the online seller. The online merchant's website generates an invoice from the transaction data and emails the invoice to the user. The server system Ticketdownload..com mechanism sends the eTicket data to the merchant's computer that needs the ticket for admission or purchase. The server system Ticketdownload..com mechanism (or, in another embodiment, the merchant's website) sends the encrypted eTicket to the user's PC system.

The PC system stores the encrypted eTicket in the memory storage device configured on the user's PC. Once this is done, the user can eTicket to the Directed Purpose system device or any other system device via the user PC, hardwire between system devices, infrared interface or short range data transmission interface.
Can be downloaded. Once the user has downloaded the eTicket from that PC to the system unit, the PC system marks eTick et in the PC's memory as downloaded.

3) Personal Medical Care, Insurance, and Transmission of Emergency Data FIG. 18a shows personal medical care in the designated purpose system device according to the embodiment of the present invention.
3 is a high level functional flow chart showing insurance and emergency data interface processing. As shown in FIG. 18a, after the user activates the PC system, the PC system displays various options 1500, one of which is "personal medical, insurance, emergency data." If the user selects the "Personal Health, Insurance Data" option (1503), the PC system prompts the user to enter all relevant personal health, emergency, insurance data 1506,1509.

The PC system receives this information and then stores it in the memory configured by the PC 1512. If the user has entered all the data, the system
Generate an option menu prompting the user 1515 to click the "Synchronize with your mobile device" or "Synchronize with mobile device and database" option 1518 on the display screen of the display device configured on the user PC. To display. You also have the option of uploading and synchronizing all your personal medical, insurance and emergency data to a secure host (eg Immtec server). This PC system encrypts the data, the server system stores information related to user accounts in an emergency, and a telephone line or other communication method to a host server that is accessible only to authorized individuals 1533-1554. Send encrypted data via.

Once the user has selected to synchronize the PC with the portable device only 1521, the PC system will provide the user's personal medical and insurance data to the system device 152.
4-1530 (including the Directed Purpose System device and properly configured to receive the transmitted data).

The Directed Purpose System device may also receive a medical prescription, as shown in FIG. 18b.
You can also save and send. FIG. 18b is a high level functional flowchart showing an example of a prescription download interface processing in the example of the specified purpose system device according to the embodiment of the present invention. To perform the prescription function, the user provides the Directed Purpose System device to an authorized physician. An authorized physician uses the PC system mechanism for this purpose to prescribe the user's prescription 1563 on the physician's computer.
Enter. Once all prescription information including brand name, generic name, physical fitness, dosage etc. is entered into the doctor's PC system 1566-1567, the doctor will
The user's device 1571 is instructed to download the information.

The physician establishes communication between the user's device and the physician's PC system, for example, via a hardwire connection or infrared or short range data transmission transceiver 1574. The doctor chooses a special doctor option, "Download the prescription to the patient's mobile device and sync it with your database." Selection of this option causes the physician's PC system to authenticate the user and the user's device and, if authenticated, cause device 1577 to download the selected prescription.
This selection also causes the physician's PC system to be installed on the host server (eg, I
mmtec 1583) and associates all prescriptions, security data, and links with a particular physician's account 1590-1594 for later retrieval by the pharmacist when a patient seeks a prescription drug. Upload all prescriptions and security data to the server system database (1585-1588). The Directed Purpose System device stores the downloaded prescription for later use. The host server is the doctor's PC system 15
A notification of synchronization completion is sent to 96. Then the connection with the host server is terminated (
1599).

B) Purchase Place Device Interface The Purpose Purpose system device interfaces with any of the purchase place devices equipped with an infrared interface or short range data transmission capability that can interface with system enabled PDAs / wireless phones. The Directed Purpose System device is configured to receive and transmit electronic tickets, electronic currency, credit cards, identification, security and / or personal medical, insurance, and emergency data, among others. The configuration of the functions performed by a particular Directed Purpose System device can be updated by synchronizing the user's personal computer or an authorized sales / service center.

19b-19c are graphical representations showing various views of an exemplary external configuration of an embodiment of a directed purpose system device (FIG. 19c is a “front” surface and FIG. 19b is
It is a reverse image rear view). For security purposes, the memory of the Directed Purpose System device contains a unique encrypted security code, user name, address and telephone number, and in one embodiment, the user's biometric data (eg, not intended to be limiting). Not included, but included in the fingerprint data). In one embodiment of the Directed Purpose System device as shown in FIGS. 19b-19c, a biometric reader 1105 is provided on the outer surface of which a user has a finger (eg, right or left thumb or right or left thumb). Place the index finger). Two buttons are provided on the opposite surface of the designated purpose system, one is a send button 1104 and one is a receive button 1106. Furthermore, a small liquid crystal screen 1109 is also provided. An input / output interface for the hard wire synchronous cable 1101 is provided at one end of the designated purpose system device, and an infrared interface 1100 is provided at the opposite end.

Examples of uses of the Directed Purpose System device include, inter alia, wallets for electronic currencies,
Electronic single-use and / or multi-use ticket holding and carrying, identification,
There are repositories and information sources for licenses, personal care, insurance, emergency data (including medical prescriptions).

In an embodiment of the present invention using a PDA / wireless phone, the PDA / wireless phone comprises a number of input devices including a plurality of keys, and in the case of a PDA also a handwriting input device, a voice input device. PDAs and wireless phones also include display interfaces that are larger than those that can be provided using compact Directed Purpose System devices. On the other hand, the embodiment of the Directed Purpose System device as shown in FIGS. 19b-19c has limited input and display functions due to its size limitation.

Due to the size limitation of the example Directed Purpose System device, the embodiment of the Directed Purpose System device shown in FIGS. 19b-19c requires only limited user input at the time of the "place of purchase interaction". And interacts with the "place of purchase" device. An example of a Directed Purpose System is that the initial communication between the Directed Purpose System device and the vendor purchase location is via a connection established by the vendor's purchase location device with a server system, for example, an internet connection. Activates the interaction between the specified purpose system device and the server system. At this point, the server system receives a request from the vendor's place of purchase device, for example, an amount of money, a particular eTicket, medical information or a prescription, and then prompts to respond to this request. , To the designated purpose system device via the vendor's purchase location interface according to the system protocol.

In this embodiment, the user directs the infrared or other short range data communication interface of the Directed Purpose System device to a similar device interface on the storefront device that the user wishes to communicate with and directs the Directed Purpose System device. Press the "send" button 1104 on the outside of the device to turn on the device. The designated purpose system device is
Display a request for PIN and / or biometric identification. Once the correct identification data has been entered, the device sends the identification and security information to the over-the-counter device. The user then presses the "receive" button 1106 to receive the server system's instructions.

The designated-purpose system device receives the server system instruction and then executes it, and notifies the user of the amount and type of the transaction on the liquid crystal 1109 display configured by the designated-purpose system device. The Directed Purpose System device also notifies the user when the device is ready to fulfill the instructions. At this point, the user is
Press the "Send" button to submit the information needed to complete the requested transaction (eg, electronic currency, eTickets, medical information, prescription information, etc.). In this embodiment, the information is sent to the server system via the seller's purchase location interface according to the server system protocol, and the server system performs the requested transaction with the seller.

FIG. 20a is a high level graphical representation that conceptually illustrates another embodiment of a Directed Purpose System device configuration that includes a biometric reader and additional context sensitive user input buttons. In the embodiment shown in FIG. 20a, the user enters information using the additional context sensitive user input buttons 1111 and selects the options appearing on the device's LCD to fulfill the requested transaction. I do.

FIG. 20b is a schematic diagram illustrating example components of the PayStick ^™ embodiment and example connections between the example components. FIG. 20c is a schematic diagram showing an example of physical connections between example components. Note that, here, the reference numerals of the components in FIGS.
It should be noted that it is only relevant for the parts disclosed in ~ 20f and not necessarily for the reference numbers in the other figures of this disclosure.

FIG. 20d is a partial list showing a list of example specifications for the example components shown in FIG. 20b. 20e and 20f are example material tables for the example components shown in FIG. 20a. FIG. 20e shows the English version and FIG. 20f shows the German version.

The six-input button embodiment of the Directed Purpose System Device interface, together with the vendor's place of purchase device and server system, can be used in scenarios for each Directed Purpose System device function described below without departing from the spirit of the invention. Can fit.

1) Electronic Wallet for Electronic Currency FIGS. 21a to 21b are high-level functions showing an example of transaction interface processing between an electronic currency usable designated purpose system device and an over-the-counter terminal or an electronic kiosk according to an embodiment of the present invention. It is a flowchart. Assuming the user has downloaded electronic currency to the Directed Purpose System device, the user can use the device as an electronic wallet for electronic currency. To do this, the user has an “on” button 160.
Press 0. The designated-purpose system device requests the input of security data 1603. In an embodiment of the Directed Purpose System device with a biometric reader, the user places a finger on the biometric / on / off button interface on the Directed Purpose System device. As a result, the designated-purpose system device displays the biometric data 1606.
Read. In another embodiment of the Directed Purpose System device, the device comprises a number of additional buttons, for example four buttons 1111 shown in FIG. 19a, by means of which the user can enter a user ID and / or a PIN 1606. You can

The specified purpose system may be different from the biometric data or the ID, PIN 1609, 1621, 1615 (in some cases, the one stored in the specified purpose system) even after the preset number of times (eg, twice) has taken place. If the validity of (No) cannot be confirmed, the designated-purpose system device does not function and locks (1624). In this example, prior to locking, the user is prompted to place another finger on the biometric interface.

The designated purpose system uses biometric data or ID, PIN (in some cases 1627
If so, the Directed Purpose System device is turned on (1630), the transceiver communication port is opened, and through this device's infrared or other short range data communication interface, Send the "I am here" code to the interface as well as to the point-of-sale device to which the Directed Purpose System device was directed. In this way, the Directed Purpose System device opens communication with the over-the-counter device, and through this over-the-counter device, with the server system 1630.

The user points the infrared interface of the designated purpose system device to the infrared interface on the purchase place device of the seller, and then presses the receive button 1633. In the case of a Directed Purpose System device initialized to perform multiple functions (electronic wallet, eTicket, medical information), the device will prompt the user on the LCD with a “send” button (eg 1106 as shown in FIG. 19b). ) Prompt to press. Alternatively, a special code is sent (1636) through the vendor point-of-sale terminal, which confirms with the Directed Purpose System device the method of payment requested. The working interface makes the vendor's purchase location device establish a connection with the server system (if not previously established).

The transaction details appear on the Directed Purpose System device LCD 1639. If the data is correct, the user presses the “Send” button 1642 and the payment type, amount, user ID, unique security code and security data are sent to the designated purpose system device through the vendor store terminal and server. The system (or clearinghouse) communication protocol 1645 is used to send to the host server system (or clearinghouse). The server system attempts to validate the identification and security information 1648 sent to it. If the user account is suspended (1651), or does not have enough funds for the transaction, or is on hold, the host system requests the data to be retransmitted through the seller's terminal 1654. To do. After the second attempt, if the user account is in fact suspended, has insufficient funds, or is on hold, a message is sent to seller terminal 1657 that the transaction is denied.

Once the server system has determined that the account is up and that there are sufficient funds available (1660), the server system will process the seller's proposed request. (Eg, the server system tests the full amount of electronic currency available on the Directed Purpose System device and charges (plus the micropayment amount calculated by the server system 1663 and sent to the host or server system host). Make sure you have enough currencies available to satisfy). It then generates a set of instructions and sends them to the Directed Purpose System device to perform a particular function as required by the vendor's over-the-counter device. In another embodiment, the host system calculates a micropayment commission on sale, adds it to the transaction amount, and sends this data via short range wireless transmission through the seller terminal (16
69, 1678) All discounts on the user-specified
Send with data and / or credit data.

In the present scenario of implementing the functionality of an electronic wallet, if the user's account has sufficient funds and this account is up (1660), the instructions sent by the server system will be Through the infrared interface configured with the purchase place device, the designated purpose system device reads out the total amount of available electronic currency from the memory storage, and displays the available total amount on the liquid crystal screen display of the designated purpose system device, Then, it instructs to prompt the user to press the reception button 1633. The server system sends the amount requested by the vendor to the purpose-built system device via the infrared interface configured with the vendor's place of purchase device and, if the user approves the total amount payable to the vendor 1642, the user. Prompt you to press the "send" button.

When the user approves the total amount to be paid, the user presses the “send” button on the designated purpose system device 1642. If not enough electronic currency is available on the Directed Purpose System device, the transaction is rejected (1657). When the designated purpose system device sends a sufficient amount of electronic currency, the purchase location device of the seller notifies the server system of the user ID, PIN, unique security code, biometric data, currency. Appropriate financial services
Send to the clearinghouse system.

When the host system can confirm the validity of the information sent, the host server system deducts the total amount of the transaction from the user's account and collects the micropayment from the amount. Then, this micropayment is deposited in the account 1666 of the server system host (for example, Immtec), and the balance balance is deposited in the accounts 1672 and 1675 of the seller. host·
The system sends a transaction approval to the server system, which in turn notifies the seller's purchase location device, which in turn notifies the Directed Purpose System device and the user that the transaction has been completed. .. The amount of electronic currency paid is displayed on the LCD screen of the Directed Purpose System device and is deducted from the total amount stored in the memory of the Directed Purpose System device 1669. Then, the remaining balance of the electronic currency is displayed on the liquid crystal screen 1678.

Repayments are handled in the same manner as merchants handle any other repayment or credit transaction, including cash. In some embodiments, a Directed Purpose System device configured as an electronic currency device may not connect to any financial service provider account. In such cases, the credit cannot be applied to a particular account corresponding to the user.

2) Electronic Multi-Use Ticket Device In this embodiment, when the multi-use ticket is downloaded from the website or transmitted from the place of purchase device to the designated purpose system device, a unique electronic ticket is used. The ticket code is embedded in the ticket recognized by the vendor's purchase location device. A server system for sellers to sell and exchange tickets
In order to take advantage of the infrastructure, the merchant must "register" with the server system host (eg Immtec). Exchanging multi-use tickets is similar in various ways to using a purpose-built device as an electronic wallet. Embodiments of the present invention provide information and provide prompts for receiving instructions and information in exactly the same manner as described above for electronic wallet functionality. The difference with the multi-use ticket feature is that instead of displaying the amount of currency, the number of tickets available and the types of tickets available are displayed on a liquid crystal screen configured on the Directed Purpose System device.

User turns on Directed Purpose System device utilizing standard security protocol, seller requests ticket, server system validates identity and security information and number of tickets available And, after the user approves the exchange of tickets, the user turns on the Directed Purpose System device using standard security protocols and then turns the infrared interface of the Directed Purpose System device on to the vendor's purchase location. Point to the infrared interface of the device and press the "Send" button.

By pressing the "Send" button, the user can
Instruct to send a ticket, plus, user ID, unique security code and unique electronic ticket code. The merchant's place of purchase device receives the ticket and security data and then, in this example, sends that information to the server system. The server system validates the information and authorizes and records ticket exchanges on the user and merchant accounts. The server system generates and sends instructions to the directed purpose system device to reduce the number of tickets available one at a time and notifies the directed purpose system device and the user of the completion of the transaction. In contrast to the electronic money feature, the multi-use ticket and single-use ticket features in this embodiment perform a micropayment calculation and transfer it when the ticket is downloaded.

In one embodiment, micropayments are redeemed for exchanged tickets rather than for downloaded tickets. In such an embodiment, each day, the vendor's system sends a vendor database of Directed Purpose System device exchange tickets, including the user ID and the ticket to be exchanged. At this point, the server system will calculate the accumulated micropayments for all tickets to be redeemed and transfer the full amount of micropayments to the server system host account, the appropriate clearinghouse system. To notify.

3) Repository for personal medical, insurance and emergency data Similar to the functions described above for electronic money and electronic tickets, the Directed Purpose System device stores personal medical, emergency and insurance data. It can be configured to store, process requests for them, and send them. The major difference in this feature compared to other previously mentioned electronic money and electronic high-use ticket features is that the server system receives the type of information it needs from the "merchant" and "place of purchase" systems. Sending the type of information required to the Directed Purpose System device and instructing the device to send the information to the purchase location device. Medical, insurance or emergency data can be sent to authorized service center providers by pressing the send button on the device and sending an identification code from the authorized service center provider PC system, over-the-counter device or other short range wireless transceiver to the device. Can be accessed by. This identification code is available from Immtec and is provided to authorized service center providers (eg, hospitals or doctors). This method of accessing the purpose-built system device allows access only to the user's medical data, not to other areas of system memory.

C) Third Party Financial Service Provider or Ticket Vendor Interface Directed Purpose System Equipment may be authorized by a financial service provider even if the user does not have an account such as from a bank or Western Union. Can be used to download electronic currency. 22a-22b show
3 is a high-level functional flowchart showing an electronic currency / ticket download process between an example of a specified purpose system device and an authorized service center provider in an embodiment of the present invention. The Directed Purpose System device may replenish multi-use tickets from an authorized Tibetan retailer (eg, a transportation office or electronic kiosk).

As shown in FIGS. 22a-22b, in an embodiment of a third party financial service provider interface, funds are available for the user along with the user's ID, name, address and other security data 1700. Deposited in a special account. When a user appears at an authorized financial services provider office 1703,
The user is required to show proof of identity 1706 and, optionally, to provide the requested amount of cash, check or other payment method in addition to the micropayment amount, as well as transaction fees for the option. If the user presents the proper proof of identity and paid the requested amount, the user will turn on biometrics /
You are prompted to press the off button interface and enter the PIN code for Directed Purpose System device 1709. The designated-purpose system device reads biometric data or PIN 1711. When the designated purpose system device determines that the read biometric data does not match the biometric data stored in the designated purpose system device, the device does not function and refuses the transaction (1714).
.

Once the Directed Purpose System device confirms the validity of the biometric PIN data, the user may specify the amount of funds and use the infrared interface of the Directed Purpose System device to the computer service infrared of the financial service provider. Is asked to turn to the interface. The representative of the financial service provider is
Enter the amount of funds requested. The financial service provider's computer sends a request for a user ID, unique security code and biometric data 1717 to the Directed Purpose System device. This request appears, for example, as a blinking "R" on the LCD of the user's Directed Purpose System device. The user presses the "Send" button 1720 on the Directed Purpose System device to cause the Directed Purpose System device to send the user ID, unique encrypted security code and biometric data to the financial service provider computer 1723.

The financial service provider's computer receives the transmitted data and sends this data and the amount of funds requested to the financial service clearinghouse or host system. The clearinghouse or host system requests the server system to compare the submitted user's data with the information about the corresponding user stored in the server system's database 1726.

If the server system confirms the validity of the information, it notifies the clearinghouse. The clearinghouse validates the amount of available funds for financial service providers. If the financial service provider has sufficient funds, the clearinghouse notifies the financial service provider and the server system of the approval. Then, it sends the financial service provider instruction to be provided to the designated purpose system device to add the designated amount of funds authorized by the clearinghouse 1729. The server system calculates the financial service provider micropayment amount and the user micropayment amount and sends a notification of the micropayment amount to the clearinghouse. The clearinghouse transfers the requested funds from the financial service provider's account to a special account for the user and transfers to the server system host's account 1732 an additional amount of the financial service provider's micropayment amount. Recovering an amount equal to the user micropayment amount from the amount of funds requested and transferring the user micropayment to the account of the server system host. In one embodiment of the present invention, the clearinghouse also transfers a service fee 1735 from the user's funds to the financial service provider's account. The clearinghouse notifies the server system, which in turn notifies the financial services
Notify the provider system. The server system generates instructions to add the amount of funds required minus the user micropayment and any service charges to the electronic money stored in the memory of the purpose-built system device, the computer of the financial service provider and Send to designated purpose system device via infrared interface 1738.

The Directed Purpose System device receives the instruction to add the requested funds, and then
Increase the amount of electronic funds available. The designated purpose system device displays the amount of available funds on the liquid crystal screen of the designated purpose system device to complete the transaction (
1741) The user is notified of the fact.

The Directed Purpose System device holds multiple-use tickets, such as those used for commuter transport, and single-use tickets, such as for certain events.
The process of purchasing a ticket from an authorized Tibetan retailer (eg, Department of Transportation) is similar in many respects to the process described above for downloading funds from a financial services provider. The user pays for the ticket requested at the authorized Tibetan retailer 1750. Authorized Tibetan dealers inform the server system of the type and number of tickets to be purchased. The server system is
Generates electronic tickets 1777 of the type and number requested, generates instructions to be added to the ticket, passes the tickets and instructions through an authorized Tibetan dealer's computer infrared interface, and the user's specified purpose via the device's infrared interface. Send to system unit 1786. In an embodiment of the invention, the server system attaches the user's ID, biometric data and a unique encrypted security code to the electronic ticket data. The server system stores the ticket and security data in its database 1780 for later exchange of ticket exchange information with the Directed Purpose System device through the ticket exchange authority computer 1783.

The Directed Purpose System device receives an electronic ticket with all accompanying data and instructions sent via the device's infrared interface and authorized ticket selling computer 1786. Once the Directed Purpose System device executes the instructions and adds a ticket to its memory, the device displays the number of available tickets on the liquid crystal screen of the Directed Purpose System device and marks the transaction complete ( 1789).

D) PDA / Wireless Phone Interface Electronic currency is transferred between PDA / wireless phones, Directed Purpose System devices. Figure 2
3a-23b are high level functional flowcharts illustrating an example of electronic currency exchange processing between an example directed purpose system device and an example system enabled PDA / wireless telephone in an embodiment of the present invention. In one embodiment of the present invention, to transfer electronic money from a Directed Purpose System to a PDA / wireless telephone, the user directs the infrared interfaces of both devices towards each other (1822, 1859). The PDA / wireless phone user selects the system icon on the display screen 1800. User PDA system
D, PIN 1803 is required. The user inputs the user ID and PIN. P
The DA system confirms the validity of the user ID and PIN. Once confirmed, the PDA / wireless phone user selects the "e-cash transfer" icon 1812. The PDA system prompts the user to enter the amount to receive or send, and the PDA system user to select either "receive" or "send" 1815.

If the PDA / wireless telephone user selects “Receive” 1818, the Directed Purpose System device user presses a receive button 1818, and the Directed Purpose System device receives the electronic currency request and the amount of money, and the Directed Purpose System device Display the amount requested on the 1856 LCD screen. A Directed Purpose System device user places his finger on the biometric on / off button interface 1838. The Directed Purpose System device reads the biometric data and attempts to validate the information stored in the device's memory. Once the biometric data has been validated (1841), the Directed Purpose System device user is prompted to press the "Send" button, which causes the Directed Purpose System device to send the requested electronic currency amount. Send to PDA / wireless phone 1859. The Directed Purpose System device reduces the amount of electronic currency available and displays the transferred amount and then the balance on the liquid crystal screen of the Directed Purpose System device 1868. The PDA / wireless phone receives the transmitted amount 1825 and then adds this amount to the available amount of electronic currency and displays both the transferred amount and the total available amount 1826. These two devices are then notified of the transaction completion 1
Replace 829 and 1871.

In an embodiment of the invention in which the server system maintains an account deduction balance for each device / user, an account may be a PDA, a user's PC, a server system and / or a designated purpose system device, a user's It is updated during the next synchronization session 1832 between the PC and server system. As shown in FIG. 23b, electronic currency may be transferred from a PDA / wireless telephone to a Directed Purpose System device as well, except that the PDA / telephone user selects the “Send” option rather than the “Receive” option. , The transfer direction of funds is reversed (1873
~ 1940).

6. Initialization and Setup for New Directed Purpose System Equipment The Directed Purpose System Equipment may be purchased at any Authorized Sales / Service Center or may be purchased directly from a website (eg PayStick..com / Immtec).
) May be purchased directly from. The Directed Purpose System device is shipped fully configured and ready for use, except for initial recording of biometric data and registration with Immtec. The user ID is printed on the registration card and cannot be changed. The Directed Purpose System device may further have a sales / service provider logo on its surface and a sales / service provider unique code logo embedded in the device's firmware.

A new user of a Directed Purpose System device with a biometric reader is instructed to initialize the biometric data in the device. To do so, the user removes the plastic cover from the biometric on / off interface button. The user places a finger (eg, right thumb or left thumb or right index finger or left index finger) on the biometric on / off interface button and presses the button. This process can be repeated up to three times to provide accurate scanning of biometric data. The Directed Purpose System device records biometric data, encrypts it, and stores the data in its memory storage.

The new user is also instructed to register a new Directed Purpose System device after recording biometric data. To do so, the user is instructed to connect the user's personal computer, i.e., the computer of an authorized sales / service center, to the server system, for example via the Internet or a direct line. The user is instructed to select the "Initialize New Directed Purpose System Device" option from the server system menu.

The server system then takes the user I from name, address, phone, registration card.
Shows the user a safe form to fill out, including input fields for D and the mother's maiden name. The user is prompted to click the "Submit" button once he has completed the requested data. The new user data is sent to the server system, which receives the information and updates its database with this information. The user is then prompted by the server system to synchronize this new Directed Purpose System device with the server system via either a hardwire interface or an infrared interface or other short range data transmission interface. The user synchronizes the new device through the hardware or via an infrared interface or other short range data transmission interface to indicate whether the user is using a PC or "public" computer, and has a designated purpose system. Press the "Send" button on the device.

If the computer is a “public” computer, such as an authorized service center or another public computer or kiosk, the Directed Purpose System device may be a server via a hardwire interface or an infrared interface. Send the user ID, unique encrypted security code and biometric data to the system. Bypass public computers to prevent them from ingesting data. A method of accomplishing this in an embodiment is such that when the server system sends an "instruction" to the Directed Purpose System device, and the Directed Purpose System device executes it, the device encrypts and embeds the information in the instruction, Causes the information embedded in the instruction to be returned to the server system. The server system then decrypts the transmission, extracts the information, and stores the information in the server system's database. In another embodiment, the Directed Purpose System device simply encrypts the information as directed by the server system and sends the encrypted information to the server system. In either case, the public computer does not capture the information because it has no instructions to decrypt. Public computers or kiosks act only as routes. The server system sends some validated information to the financial services clearinghouse for future reference and processing. At this point, the Directed Purpose System device has received the data and is ready for use.

If, instead of using a public computer, the computer is the user's personal computer, the Directed Purpose System device sends the user ID to the server system via a hardwire or infrared interface with the user's PC.
Send your own encrypted security code and biometric data. server·
The system receives the user specified purpose system device data and then
Add user specified purpose system device data to the user's personal data in the system database. The server system then sends the user's data to the user's personal computer with instructions to save the data. The user's personal computer stores the data in the database after receiving the data and instructions. The server system sends some of the data to the financial services clearinghouse. At this point, the Directed Purpose System device has received the data and is ready for use.

7. Data Entity Relationships and Attributes FIG. 24 is a data relationship diagram illustrating an example data structure for data maintained by a server and / or PDA / wireless / directed purpose device. As shown in FIG. 24, an example of a data structure embodying the data of the present invention is ACCOUNT entity 3.
810 (short name: ACC, plural names: ACCOUNTS). The ACCOUNT entity 3810 is a repository for holding information about a particular account maintained by a particular customer. It also holds ticket information for certain events, season game tickets, train tickets, etc.
In addition, sometimes electronic money is held. It is common for multiple ACCOUNTS to be maintained for a single customer device. ACCOUNT entity 3810 is ACCOUNT-ID3
810-1 and optional QUANTITY 3810-2. ACCO UNT-ID 3810 is a primary unique identifier. ACCOUNT 3810 is held by one and only one CUSTOMER 3820, one or more TRANSACTIONS 38
30 and / or reassigned by one or more TRANSACTIONS 3830. ACCOUNT 3810 must be aggregated by a unique ACCOUNT-TYPE 3840. ACCOUNT3810 is the only EVENT3850
And / or only one EVENT-PACKAGE 3860.

As shown in FIG. 24, an example data structure embodying the data of the present invention provides an ACCOUNT-TYPE entity 3840. The ACCOUNT-TYPE entity 3840
Used to classify ACCOUNTS 3810 into group types. The ACCOUNT-TYPE entity 3840 is characterized by ACCOUNT-TYPE-ID 3840-1, NAME 3840-1, and optional DESCRIPTION 3840-3. ACCOUNT-TYPE3840
Can categorize one or more ACCOUNTS 3810. ACCOUNT-TYPE-ID 3840-1 includes, for example, cash, ticket, business, personal, and the like.

As shown in FIG. 24, an exemplary data structure embodying the data of the present invention comprises a CUSTOMER entity 3820. The CUSTOMER entity 3820 is a repository for holding customer information. The CUSTOMER 3820 is typically identified for each individual who has multiple ACCOUNTS and possibly multiple devices. The CUSTOMER entity 3820 aggregates, among other things, customer demographics, medical information, purchasing patterns, and the like. CUSTOMER entity 3820 is CUSTOMER-ID 3820-1
, FIRST-NAME 3820-2, LAST-NAME 3820-3 and many choice attributes (A CTIVE-IND 3820-4, ADDRESS 13820-5, ADDRESS 23820-6, BIRTHDAY 3820-7, CITY 3820-8, COUNTRY 3820-9, EMAIL 3820-10, GENDER 3820-11, MARITAL-STATUS 3820-12, POSTAL-CODE 3820-13
, STATE 3820-14, TITLE 3820-15 and USERNAME 3820-16). CUSTOMER 3820 may be used by only one .COMPANY 3880, hold one or more ACCOUNTS 3810, hold one or more DEVICES 3890, and / or be grouped by one or more DESCRIPTORS 3900.

As shown in FIG. 24, the example data structure embodying the data of the present invention comprises an ALLO WED-EVENT entity 3870. ALLOWED-EVENT entity 3870
Is used to group events according to EVENT-PACKAGE3860. For example, a seasonal ticket package only includes good tickets for certain games. The ALLOWED-EVENT entity 3870 is characterized by ALLOWED-EVE NT-ID 3870-1. ALLOWED-EVENT3870 is the only
It can hold an EVENT3850 and must be included in the only EVENT-PACKAGE3860.

As shown in FIG. 24, an example data structure embodying the data of the present invention comprises a .COM PANY entity 3880. The .COMPANY entity 3880 is used by the CUSTOM ERS 3820 to keep track of the associated .COMPANY 3880. .COMPANY entity 3880 is characterized by .COMPANY-ID 3880-1 and NAME 3880-2. The .COMPANY entity 3880 may use one or more CU STOMERS 3820.

As shown in FIG. 24, the exemplary data structure embodying the data of the present invention comprises a DESC RIPTOR entity 3900. The DESCRIPTOR entity 3900 comprises a repository for descriptive information bulletins about the CU STOMER 3820. DESCRIPTOR entity 3900 is DESCRIPTOR-ID 3900-1, alternative NAME 3900
-2, characterized by the option DESCRIPTION 3900-3. Multiple DESCR IPTOR-TYPES 3900-1 are used to store different types of information about a particular CUSTOMER 3820. A particular DESCRIPTOR must be grouped by a unique DESCRIPTOR-TYPE 3920 and grouped into a unique CUSTOMER 3820.

As shown in FIG. 24, the exemplary data structure embodying the data of the present invention comprises a DESC RIPTOR-TYPE entity 3920. DESCRIPTOR-TYPE entity 39
20 comprises a selectable type of CUSTOMER 3820, DESCRIPTOR 3900.
DESCRIPTOR-TYPE entity 3920 is characterized by DESCRIPTOR-TYPE-ID 3920-1, N AME 3920-2, and optional DESCRIPTION 3920-3. DESCRIPTOR-TYPE 3920 contains one or more DESCRIPTORS 390
Must be classified as 0.

As shown in FIG. 24, the example data structure embodying the data of the present invention comprises a DEVI CE entity 3890. The DEVICE entity 3890 is owned and
And / or holds information about all devices associated with a particular CUSTOMER 3820. DEVICE entity 3890 is characterized by DEVICE-ID 3890-1 and NAME 3890-2. DEVICE3890 is the only DEVICE-TYPE3
Grouped by 910 and must be owned by a unique CUSTOMER 3820. DEVICE-ID 3890-1 comprises the identification of a device such as CUSTOMER 3820's business cell phone, personal cell phone, Palm Pilot, etc.

As shown in FIG. 24, the example data structure embodying the data of the present invention comprises a DEVI CE-TYPE entity 3910. DEVICE-TYPE entity 3890
Used to classify different types of devices that can hold a mewallet account. The DEVICE-TYPE entity 3910 is the DEVICE-TYPE-ID 3910-1.
And NAME 3910-2. DEVICE-TYPE 3910 is 1
One or more devices 3890 can be categorized. DEVICE-TYPE-ID is
Includes identification of device types such as palm computers, Directed Purpose System devices, battery phones, etc.

As shown in FIG. 24, an example data structure embodying the data of the present invention comprises an EVEN T entity 3850. EVENT entity 3850 is ACCOUNT38
Contains a data element for a particular single event held by 10. EVENT 3850 is referenced by ALLOWED-EVENT 3870 and may list all events 3850 in EVENT-PACKAGE 3860. EVENT entity 3850 is EVENT-ID 3850-1, option NAME 3850-2,
It is characterized by the option DESCRIPTION 3850-3, the option SCHEDULED-DATE 3850-4 and the option COST 3850-5. EVENT 3850 may be included in one or more ALLOWED-EVENTS 3870 and may be retained by one or more AC COUNTS 3810.

As shown in FIG. 24, an example data structure embodying the data of the present invention comprises an EVEN T-PACKAGE entity 3860. EVENT-PACKAGE Entity 3860
Is EVENT-TYPE-ID 3860-1, Choice DESCRIPTION 3860-2, Choice
Characterized by NAME3860-3. EVENT-PACKAGE 3860 may consist of one or more ALLOWED-EVENTS 3870 and may be retained by one or more ACCOUNTS 3810.

As shown in FIG. 24, the exemplary data structure embodying the data of the present invention comprises a MICR OWALLET-LEVEL entity 3970. The MICROWALLET-LEVEL entity 3970 holds information that classifies the type or level of VENDOR 3950.
The MICROWALLET-LEVEL entity 3970 is characterized by a VENDOR-LEVEL-ID 3970-1, an option LEVEL 3970-2, and an option DESCRIPTION 3970-3. The MICROWALLET-LEVEL 3970 must be grouped by a unique VENDOR 3950. VENDOR-LEVEL-ID 3870-1 identifies a group of VENDORS 3950 such as small, medium and large.

As shown in FIG. 24, the exemplary data structure embodying the data of the present invention comprises a PROD UCT entity 3930. The PRODUCT entity 3930 holds information about the products for sale on a particular VENDOR 3950. The PRODUCT entity 3930 is characterized by PRODUCT-ID 3930-1, NAME 3930-2, option DE SCRIPTION 3930-3, and option SKU 3930-4. PRODUCT 3930 may be applied to one or more TRANSACTIONS 3830 and may be provided by the unique VENDOR 3950.

As shown in FIG. 24, the exemplary data structure embodying the data of the present invention comprises a TRANSACTION entity 3830. The TRANSACTION entity 3830
With the ability to track all transactions on the ACCOUNT 3810. The TRANSACTION entity 3830 has TRANSACTION-ID 3830-1 and ACCOUNT-ID 3830-2.
, VENDOR-ID 3830-3. A TRANSACTION 3830 can be included in a unique PRODUCT 3930, can transfer a unique ACCOUNT 3810, must belong to a unique ACCOUNT 3810, and unique TRANSACTION-TYPE
Must be classified as 3940 and must be for the only VENDOR 3950. TRANSACTION 3830 identifies, for example, the purchase of a ticket for an event, the use of a ticket for a particular event, the transfer of account items such as tickets from one ACCO UNT 3810 to another ACCOUNT-ID. ..

As shown in FIG. 24, the exemplary data structure embodying the data of the present invention comprises a TRANSACTION-TYPE entity 3940. TRANSACTION-TYPE entity 3
940 is used to classify TRANSACTIONS 3830. TRANSACTION-TYPE entity 3940 includes TRANSACTION-TYPE-ID 3940-1, NAME 3940-2,
Characterized by the option DESCRIPTION 3940-3. TRANSACTION-TYPE
The 3940 can categorize one or more TRANSACTIONS 3830.

As shown in FIG. 24, the exemplary data structure embodying the data of the present invention comprises a VEND OR entity 3950. The VENDOR entity 3950 provides information about sellers who are members of the mewallet community who accept mewallet transactions. The VENDOR entity 3950 includes VENDOR-ID 3950-1, option ADDRESS13950-2, option ADDRESS23950-3, option CITY3950.
-4, option COUNTRY3950-5, option EMAIL3950-6, option FAX 3950-7, option NAME3950-8, option PHONE3950-9, option POSTAL-CODE 3950-10, option STATE3950-11 To be VENDOR 3950 may be associated with one or more TRANSACTIONS 3830 and may be classified as one or more MICROWALLET-LEVELS 3970,
One or more VENDOR-EMPLOYEES 3960 may be used and one or more PRODUCTS 3930 may be sold.

As shown in FIG. 24, an example data structure embodying the data of the present invention comprises a VEND OR-EMPLOYEE entity 3960. VENDOR-EMPLOYEE entity 39
60 is used to hold information about the people employed by a particular VENDOR 3950 to track human actions associated with mewallet transactions for the VENDOR 3950. VENDOR-EMPLOYEE entity 3960 is EMPLOYEE-ID396
0-1, option FIRST-NAME 3960-2, option JOB-TITLE 3960-3,
Characterized by option LAST-NAME 3960-4, option TITLE 3960-5, option USERNA ME3960-6. VENDOR-EMPLOYEE3960 must be used by only VENDOR3950. The VENDOR-EMPLOYEE entity 3960 date is moved from VENDOR 3950's own employee database.

8. PC and PayStick..com User Interface FIG. 25 is a graphical representation of an example user interface welcome screen provided to a user's PC according to an embodiment of the present invention. As shown in FIG. 25, the PC system uses the user ID 2000 and PIN 2001 of the user.
Generate and format an input field that collects. The PC system prompts the user to press the online enter button 2002 to enter the user ID 2000 and PIN 2001 (2003). The PC system is
Further, the user is prompted to see which of the wired interface 2006 or infrared interface 2007 he is using.

FIG. 26 is a graphic representation of an example main menu user interface screen provided to a user's PC according to an embodiment of the invention. Figure 2
As shown in FIG. 6, the user can select an option from the mewallet menu 2014, 2018 or the PayStic (designated purpose system device) menu 2016, 2020. The PC system prompts the user to make one choice (204).
0). For example, the PC system provides mewallet (2014) user selection options 2018 as follows. That is, Download eCash 2018-1, Synchr onize with my .computer 2018-2, Synchronize with my mewallet..com portal 2018-3, Purchase eTickets 2018-4, Download eTickets 20
18-5, Upload eTicket to my "Will Call" 2018-6, Update my profile 2018-7, Update my financial data 2018-8, Update my medical data ata 2018-9 or Initialize a new PayStick 2018-10. PC
The system provides PayStick 2016 user selection options 2020 as follows. In other words, Download eCash2020-1, Synchronize with my PayStick2
020-2, Synchronize with my PayStick..com portal 2020-3, Purcha se eTickets 2020-4, Download eTickets 2020-5, Upload eTicket to my "Will Call" 2020-6, Update my profile 2020-7, Update my f inancial data 2020- 8, Update my medical data 2020-9, Initializea new PayStick 2020-10 or Set Internal Clock 2020-11.

FIG. 27 is a graphical representation of an example user interface welcome screen provided to a website for a directed purpose system device user to interface with a server system in accordance with an embodiment of the present invention. This website is sometimes referred to herein as "PayStick..com". As shown in FIG. 27, the PayStick..com portal for the server system is the user's user ID 2066.
And create and format an input field to collect PIN 2068.
The PC system prompts the user to press the online enter button 2072 and enter the user ID 2066 and PIN 2068 (207).
4).

FIG. 28 is a graphical representation of an example main menu user interface screen provided to a Directed Purpose System device website interface according to an embodiment of the present invention. PayStick..com for server systems
The portal provides PayStick user selection options 2077 as follows. That is, Download eCash 2077-1, Purchase eTickets 2077-2, Download eTickets 2077-3, Upload eTicket to my "Will Call" 2077-4, Updated my profile 2077-5, Update my financial data 2077-6, Update my medical data 2077-7, Initialize a new PayStick 2077-8 or View my ACCOUNT 2077-9.

G. Micropayment System 1. Overview FIG. 29 is a high level simplified graphic display showing an example relationship between some of the components of an embodiment of the present invention. As shown in FIG. 29, the present invention provides a wireless handheld device 30.
No. 02 memory storage device 3001 stores the memory. Wireless handheld devices include, for example, wireless personal digital assistants (“PDAs”), wireless telephones (eg, cell phones) and wireless electronic authorities and cash transfer devices, examples of which are described below. , Referred to herein as PayStick ^™ . In an embodiment of the present invention, a wireless handheld device includes a memory storage device for storing data, an executable memory, a computing device (eg, a microprocessor) and a short range wireless communication such as an infrared transceiver or a Bluetooth wireless transceiver. Includes hardware 1100 and associated communication software and / or firmware. In some embodiments, the wireless handheld device comprises a display screen capable of displaying informational text, numbers and / or graphics. In one embodiment, the present invention provides an executable program for calculating a percentage amount equal to a pre-established percentage of a transaction amount as part of a wireless handheld device, as well as a service percentage micropayment for the calculated percentage amount. It has an executable program to reduce the amount of money dedicated.

In one embodiment of the invention, a unique, encrypted identification code for transmission to the micropayment processing service / sales provider is provided and stored in the memory device. In another embodiment of the invention, a certain amount of electronic currency is stored in memory storage for use in paying for very few services and / or sales bills during electronic payments. In yet another embodiment of the invention, both the unique, encrypted identification code and some special electronic currency amount are stored in the memory storage of the portable device. As used herein, the term "memory storage device" means any device capable of storing data, such as RAM, ROM, main memory, magnetic disks, optical disks, and the like. In an embodiment of the invention, a unique electronic identification number for paying a small electronic payment service / sales charge and / or some special electronic currency amount is stored in RAM memory.

The present invention also provides a software or firmware application for calculating and “paying” a small service charge (“Microwallet ^™ handheld
Micropayment application ”). As shown in FIG. 29, the Mi crowallet ^™ mobile micropayment application includes a wireless mobile device 30.
02 executable memory storage device 3. The Microwallet ^™ mobile micropayment application communicates and interacts with a server-based electronic payment system that handles small service charges or fees (“micropayments”).

FIG. 30 is a high level simplified graphic representation of an example mobile device component of an embodiment of the present invention. As shown in FIG. 30, the Microwallet ^™ handheld micropayment software 3100 in this embodiment stores some data 3101. Such data may be, for example, 1) electronic currency, 2) available currency amount, 3) received currency amount, 4) transmitted currency amount, 5) unique identifier associated with a particular mobile device. There is.

Example Microwallet ^™ Handheld Micropayment Software 3
100 creates an electronic currency transaction and sends it. Additionally, and as described in more detail below, the exemplary Microwallet ^™ handheld micropayment software 3100 provides instructions 3306 (FIG. 31) from a mewallet ^™ program application 3113 (FIG. 31) in a mobile handheld device or server. Receiving electronic currency according to (See).

Returning to FIG. 29, the present invention further contemplates that one or more server computers, eg, 3004a, 3004b, ... 3004n (these server computers are sometimes referred to herein as “Immtec”). ^TM "or" Immtec
A micropayment processing software application on a "s ^™ " server, eg, 3008a, 3008b, ... 3008n (sometimes referred to herein as a "Microwallet ^™ micropayment server application" or "Microwallet ^™ server application"). Called). In an embodiment of the present invention, each wireless handheld device has a Microwallet ^™ micropayment server with its own account number stored in a memory storage, for example, a database accessible by the Microwallet ^™ micropayment server application. -Pre-registered in the application. In an embodiment where a particular amount of electronic funds is stored in a memory storage device located on the user's wireless handheld device, that amount of electronic funds is accurate in a memory storage device accessible by the Microwallet ^™ micropayment server application. Replicated (ie stored). That is, the server-side electronic funds are related to the wireless mobile device /
Associated with a particular unique account number associated with the user (eg, by data relationship).

An example of a micropayment receipt processing service provider is “Imm
tec ^™ ". References to Immtec ^™ are exemplary only,
It does not limit the invention. Any micropayment receipt processing service provider may provide the functionality disclosed herein without departing from the spirit of the invention. Further, as shown in FIG. 29, in accordance with the present invention, the Microwallet ^™ handheld micropayment application residing in executable memory storage 3003 within wireless handheld device 3002 is an intermediary device, eg, service location / sales terminal, For example, communicate and interact with Microwallet ^™ micropayment server applications 3008a-3008n through 3407 (see also, eg, POS terminals as shown in FIGS. 32-35). Alternatively, the Microwallet ^™ handheld micropayment application communicates and interacts with the Microwallet ^™ micropayment server application through an intermediary device that provides an online computer application (eg, 3408 as shown in Figures 32-35). . The intermediary device is the short-range wireless communication hardware 110.
0 (for example, an infrared transceiver or a Bluetooth radio transceiver). Here, those skilled in the art will understand that the description of the components shown in FIG. 29 is merely an example and does not limit the present invention. For example, the wireless handheld device 3002 shown in FIG. 29 features a PayStick ^™ device. The present invention is equally applicable to other wireless handheld devices as well as PayStick ^™ devices, as described further below. For example, as mentioned above, wireless personal digital assistants (“
PDA) and other wireless devices (eg, cell phones).

With continued reference to FIG. 29, each wireless handheld device 3002 includes short range wireless communication hardware 1100 (eg, an infrared transceiver or a Bluetooth radio transceiver). In addition, each service location / sales (“POS”)
The terminal (e.g., 3407) may also have short-range wireless communication hardware 3007.
a (for example, an infrared transceiver or a Bluetooth radio transceiver). Each wireless handheld device 3002 includes short range wireless communication hardware (eg, 300) of a particular service location / sales terminal (eg, 3407).
7a) or short range wireless communication hardware (eg, 3007b) of the device providing the online computer application 3408 and data communication via short range wireless communication hardware 1100. A specific service location / sales (“POS”) terminal (eg, 3407) or online computer
Application 3408 then communicates with Microwallet ^™ micropayment server applications 3200a-3200n on one or more server computers (eg, 3004a, 3004b, ... 3004n). Here, those skilled in the art may directly connect the POS terminal and the server computer (for example, 3004a, 3004b, ... 3004n), or may use a local area network (“LAN”) or a wide area. It should be appreciated that it may be via a communications network, including an area network (“WAN”) or a global communications network (eg, Internet 3010). In some embodiments, communication with a server computer, eg, 3004a, 3004b, ... 3004n, may include one or more web servers and other control server computers (eg, 3009).
... 3009-YY ... 3009-nn).

FIG. 31 is a high level simplified graphic representation of an example server-side component of an embodiment of the present invention. The Microwallet ^™ server application 3200 is programmed to run on multiple server platforms. As shown in FIG. 31,
The Microwallet ^™ server application 3200 stores electronic micropayment funding data 3201 for each mewalet ^™ customer in a memory storage device accessible by the Microwallet ^™ server application 3200. Microwallet ^™ server application 3200 also stores electronic micropayment credit funding data 3202 for each participating seller in memory storage accessible by Microwallet ^™ server application 3200. In addition, Microwallet ^TM server application 3200, to save these micro-payment funds 3203 before the micro-payment funds 3203 Immtec ^TM to the bank account 3290 of Immtec ^{T M} is electronically transferred.

In an embodiment of the present invention, the Microwallet ^™ handheld micropayment application and the Microwallet ^™ micropayment server application may be used in an exemplary electronic payment system (sometimes referred to herein as a “mewallet ^™ system” or “server system”). Called) and is programmed to interface. In other embodiments, the Microwallet ^™ handheld micropayment application and the Microwallet ^™ micropayment server application are programmed to interface with any other electronic payment system. The mewallet ^™ device, system and method have been disclosed above. As disclosed above,
The mewallet ^™ device, system and method is sometimes referred to as the "PDA Pay eTicket System" or "system." The mewallet ^™ device, system and method make electronic payments to be made on a mobile terminal or device (herein the terms "mobile device" and "mobile device" are used interchangeably). The "portable terminal" or "portable device" comprises short range wireless communication hardware (eg, an infrared transceiver or a Bluetooth radio transceiver). The mewallet ^™ device, system and method include, but are not limited to, the following components: a computerized percentage calculator, a user database, a vendor database, security routines and trading routines. The mewallet ^™ device, system and method is a software application (eg, a mobile device, eg, a mobile phone or a personal digital assistant (“PDA”)).
"Mewallet ^TM software application"). The mewallet ^™ software application for mobile devices facilitates wireless station transfer and payment transactions and stores associated transaction data.

1. From the mewallet ^TM application in the user's mobile device during a transaction
Microwallet ^™ Micropayment Transmission to mmtec ^™ FIG. 32 is a high-level simplified graphic representation showing the micropayment transmission interface between example portable device components of an embodiment of the present invention. 32 shows
FIG. 6 illustrates sending a Microwallet ^™ micropayment from a mewallet ^™ in a user's handheld device during a transaction to a memory location for an Immtec ^™ account. During a Mewallet ^™ transaction of less than $ 1,000, micropayments are sent to the memory location for the Immtec ^™ account in the user's mobile device. The micropayment amount is calculated according to some pre-established percentage 3102 of financial transactions. An electronic currency 3101 account is stored by the mewallet ^™ software program in the memory of the user's electronic handheld device. This account 3101 is used only to store the electronic currency that is used to pay the commission by Immtec ^TM for each mewallet ^TM transaction. Here, this term account is referred to as Microwallet ^™ account 3101) for convenience of reference. Once the amount of transaction 3305 has been established by mewallet ^™ software 3113, the Microwallet ^™ software uses the programming instructions to calculate the established percentage 3102 of transactions 3303 and the Microwallet ^™ account in the user's handheld device. Withdrawal of electronic funds from 3101 (3
307), and then transfer this amount to all other payment data and security.
Send with data to Immtec ^™ servers 3110-3113, 3315.

2. Immm from user's mewallet ^TM Microwallet ^TM account during the transaction
Sending Microwallet ^™ Micropayments to tec ^™ Accounts FIG. 33 shows a high-level diagram showing a micropayment transfer interface between example mobile device components, example store / service components, and example server-side components of an embodiment of the present invention. It is a level simplified graphic display. As noted above, unlike storing electronic funds for payment of micropayment service fees, in one embodiment, the Microwallet ^™ application 3100 in the user's handheld device 3104 is used.
Stores only its own encrypted identification code. Unique encrypted identification code is Imm
tec ^™ mewallet server application 3404 (Immtec ^™ server (
For example, it is transmitted (3406) to 3004a) as shown in FIG. When the transaction approval is sent (3414) to the service location / sales terminal 3407, Imm
mewallet ^™ server application 3404 on the tec ^™ server (eg,
3004a) as shown in FIG. 29 calculates (3405) calculates the pre-established percentage of transactions. Calculated percentage is Microwallet server
Communicated to the application 3200, the Microwallet server application 3200 deducts the calculated percentage amount of electronic currency from the user's Microwallet ^™ account 3201 on the Immtec ^™ server database. Deducted the amount of electronic currency, Immtec ^TM micro by adding the amount of money that has been deducted the amount of the payment account 3203, Immtec ^TM micropayment account on the Immtec ^TM server database 320
3 is transferred (3412). Balance the total amount of Microwallet ^{T M} in the account 3201 of the user on the Immtec ^TM server is sent to the mewallet ^TM server applications, this mewal let ^TM server application, the user through the POS terminal 3407 or online computer applications 3408 The total balance is transmitted to the portable device 3002 (3414). In one embodiment, the total balance remaining is displayed on the display screen of the user's portable device.

3. Establishing a Seller Microwallet ^™ Micropayment Account FIG. 34 shows a seller between example handheld device components, example store / service or online application components, other server components, and example server-side components of embodiments of the present invention. 3 is a high level simplified graphic display showing a credit and transfer interface. Each seller who approves payment through the mewallet ^™ device and approves mewallet ^™ as a payment presentation system is a seller Microwallet ^™ micropayment credit account 3202 as shown in FIG.
Have the option to establish. The seller Microwallet ^TM micropayment credit account 3202, to add a Microwallet ^TM credit to Microwallet customers ^TM account 3201 (server side) and / or 3101 (wireless mobile client device). For example, the mewallet ^TM server application 3404
Using the online user interface with, the seller establishes a seller me wallet account 3519 (other), 3521 (me wallet). For example, online users with Microwallet ^TM server application 3200
Using the interface, the seller defines the percentage of each transaction amount that the customer should send to the customer's Mi crowallet ^™ account for each purchase. Seller may also be based on the particular item purchased, or the specific time frame in which the item was purchased (eg, a special promotional period).
Based on, we also establish a percentage of Microwallet ^TM credit payments for transfer to customers.

[0254] Filling Seller Microwallet ^™ Credit Account Continuing to refer to FIG. 34, each participating seller must have a Microwallet ^™ Micropayment Credit Account 3 within the Microwallet ^™ server application.
Establish 202. Upon establishing the Seller Microwallet ^™ Micropayment Credit Account 3202, the seller “fills” this account with an agreement for the amount of funds (“filled”). The payment for Immtec ^TM for the seller Microwallet ^TM micropayment credit account 3202, Bank Draft, in the form of a check or electronic wire transfer.
Funds Microwallet ^TM micropayment credit account 3202, Immtec ^TM is held immediately in some special account on the electronic access can be of the bank server. The Microwallet ^™ system keeps track of each seller's credit account. Whenever the Microwallet ^™ Micropayment Credit Account 3202 is exhausted up to or below the agreed amount, the Microwallet ^™ System will generate an invoice and the seller will be in charge of the Microwallet ^™ Micropayment Credit Account. Claim the amount to return 3202 to the full agreement. The seller Microwallet ^™ micropayment credit account 3202 on the Immtec ^™ server is a mirror (ie, equal in amount) of the account on the bank's server. The seller Microwallet ^™ micropayment credit account 3202 on the Immtec ^™ server holds a credit equal to the amount of funds available in the seller Mi crowallet ^™ credit account on the bank server. At the moment the transaction occurs, the seller Microwallet ^™ credit is sent from the seller's account on the Immtec ^™ server. The seller's bank and Immtec ^™ Microwallet ^™ credit account are cleared once a day.

5. Seller's Microwallet ^TM credits to customer's mewallet ^TM in mobile device
Sending Microwallet ^™ Micropayment Credits From Your Account With continued reference to FIG. 34, mewallet ^™ software 3104, 3100
During mewallet ^TM transaction, by mewallet ^TM system, probably for Microwallet ^TM credit 3516,3519,3521,3208,3202 to mewallet ^TM system (to and / or another system 3209) request 3506,3
524 transmissions occur. If you have Microwallet ^TM credits (3202) available from or through participating sellers, the appropriate amount of Microwall et ^TM credits will be available at the service location / sales system, kiosk or wireless internet system 3506,3524,3407,3408. , 3515, 311
4, 3510 through another interface system 3209,
3516, 3518, 3519 sent to the customer's handheld device with the transaction, eg, a credit or discount coupon (320).
8, 3506, 3524).

[0256]   6. Seller's Microwallet^TMCredit account to Immtec^TMSir
Customer mewallet on ba^TMMicrowallet^TMMicrowallet to account^TMMicrope
Element credits   FIG. 35 illustrates example mobile device components, store / service or online application.
Solution component examples, other server components and server-side configurations of embodiments of the present invention.
Shows the seller / credit server / account transfer interface between example elements
It is a high level simplified graphic display. As shown in FIG. 35, each mewallet^TM Trading, mewallet^TMSoftware 3104, 3100, 3611
Microwallet^TMCredits Microwallet^TMSystems 3521, 351
Requests are transmitted to 9, 3613, 3625 and 3202. From participating sellers
Microwallet available through Rui^TMCredit or discount
If you have 3202, Microwallet^TMSuitable for credit or discount
Pitiful amount of money is Immtec^TMCustomer's Microwallet on server^TMAccount 320
1 (3114). Microwallet^TMCredit / Discount Discount
Data from another system, such as the seller's system 3516, 3519, 32.
There is a service location / sales terminal, kiosk during the transaction from 09 to the customer's mobile device.
Or wireless internet system 3407, 3408, 3615, 3617
Through Microwallet^TM3626, b3660 and 3624. Microwallet^TM System is Microwallet^TMMicrowallet to account^TMAdd credit
Inform customer on mobile device display screen, credit / discount
Identifies the seller that the product comes from and the customer's Microwallet^TMAccount 3610, 361
Microwallet in 1^TMIndicates the credit / discount level. mewalle t's unique encrypted security code is compatible with any Microwallet^TMcredit/
Attached to a discount transaction. If Microwallet^TMSent with credit
Unique encrypted security code for mewallet in handheld device^TMOwn encryption
If the security code does not match, Microwallet^TMCredit is mew allet^TMNot added to your account, Immtec^TMCustomer mewallet on server^TM
Transferred to your account.

7. If the transmission Immtec ^TM of Microwallet ^TM micropayment credit from the seller's account to Immtec ^TM is the commission going to get a micro payment from the seller about a certain transaction, these micro-payment, such as the agreement of the contract agreement During the procedure, daily, weekly, monthly and other periods are transferred from the seller's bank account to the trading Immtec ^™ count.

8. If you Mewallet ^TM user a user to purchase a Microwallet ^TM micropayment credit to meet the mewallet ^TM Microwallet ^TM has run out of electronic currency of Microwallet ^TM in mewallet ^TM to a specified agreement level, is Microwallet ^TM is "replenished up to the specified level "There is a need. To facilitate Microwallet ^™ replenishment, the user must first obtain permission for I mmtec ^™ to withdraw the necessary funds from the user's credit card, EC or debit card or bank account. Immtec ^TM draws only up to the specified agreed level amount of funds necessary to meet the Micr owallet ^TM. These funds are then held in the user's Microwallet ^™ server funds account and all are accurately transmitted to the user's portable mewa llet ^™ enabled device during the next transaction (the transaction as shown in Figures 33-34). It

9. Sending Micropayments from mewallet ^™ PayStick ^™ FIG. 36 illustrates an example mobile Directed Purpose System (PayStick ^™ ) device component, an in-store / service or online application component example, another server component, and an embodiment of the present invention. 3 is a high level simplified graphic display showing a seller credit server account transfer interface between example server side components. Fig. 36
As shown, one embodiment of mewallet ^™ PayStick ^™ 3709 does not include Microwallet ^™ software components. In embodiments PayStick ^TM comprises Microwallet ^TM software component, a method for transmitting Microwallet ^TM micropayments to Mewallet ^TM and Microwallet ^TM server application (respectively 3404,3200) can be any other mobile utilizing Mewallet ^TM software Same as the device (see, eg, Figures 33-34). On the other hand, some embodiments of PayStick ^™ do not include Microwallet ^™ software components. In an embodiment of PayStick ^™ 3709 that does not include Microwallet ^™ software components, Immtec ^™ 3 is the commission for each PayStick ^™ transaction.
Micropayments paid from 405 will be deducted from the total amount of electronic currency contained in PayStick ^™ 3715 and will be accurately stored on the Immtec ^™ server 3727. After the transaction and payment of micropayments, the total amount of electronic currency remaining on the PayStick ^™ 3715 is sent from the Immtec ^™ server through the POS terminal or online computer application 3407-3408, 3727 (3706, 3724), and It is displayed on the liquid screen of PayStick ^™ (3711, 3715). If the user is using PayStick ^™ to win only the electronic ticket 3715, the micropayment will be added to the cost of the ticket at the time of purchase. In one embodiment, the percentage of the ticket price that is shown to be a commission by Immtec ^TM is due to Immtec ^TM from the ticket-seller is collected along with all of the other commission, from every day during the settlement procedure or weekly, the seller of the bank account Payment to Immtec ^™ .

10. Collect established percentages of service / sales commissions for over 1000 US dollars, and similar large transactions. For mewallet ^TM transactions over $ 1,000 or comparable amounts in other currencies. Commissions paid by Immmec ^™ for your credit card, EC card or debit card are credited to your bank account or debited from your bank account. For this level of transaction, the user currently has a valid account with the credit card company or bank as a file with Immtec ^™ . Immtec ^™ only accesses this account as needed to withdraw funds from the user's account to pay for commissions on the user's transactions.

[0261]

[Examples]

Although the present invention has been described in terms of certain specific embodiments, it will be apparent to those skilled in the art that numerous modifications and changes can be made. Therefore, it should be appreciated that the invention may be practiced in other ways FR than those specifically described. Therefore,
The embodiments of the invention described herein are in all respects only illustrative and not restrictive, the scope of the invention being determined by the appended claims rather than the foregoing description. Must be considered

[Brief description of drawings]

FIG. 1a is a Unified Modeling Language (UML) layout diagram showing an example relationship between major network nodes used in an embodiment of the present invention.

FIG. 1b is a UML layout diagram showing an example of node relationships during setup of a PDA device according to an embodiment of the present invention.

FIG. 1c is a UML layout diagram showing an example of node relationships when a PDA device is used to pay a purchase price in an embodiment of the present invention.

FIG. 1d is a UML sequence diagram showing a communication sequence example when a PDA device is used to pay a purchase price in the embodiment of the present invention.

FIG. 1e is a UML layout diagram showing an example of main node relationships when a PDA device is used to purchase a ticket in an embodiment of the present invention.

FIG. 1f is a diagram illustrating a case where a ticket is purchased and redeemed in the embodiment of the present invention.
It is a UML sequence diagram explaining the communication sequence example between main software objects when using a DA apparatus.

FIG. 1g is a semi-schematic diagram showing an embodiment of a PDA configured with infrared transceiver components and interfaces.

FIG. 2 is a semi-schematic diagram showing an embodiment of a wireless telephone / PDA configured with infrared transceiver components and interfaces.

FIG. 3 is a semi-schematic diagram showing an embodiment of a credit card processing terminal configured with infrared transmitting and receiving components and an interface.

FIG. 4 is a semi-schematic diagram showing an embodiment of an automated teller machine constructed with infrared transceiver components and interfaces.

FIG. 5 is a high level schematic representation that conceptually illustrates an embodiment of a personal computer configured with a PDA interface and infrared transceiver components and interfaces.

FIG. 6 is a high level graphical representation that conceptually illustrates an embodiment of a PDA Pay eTicket system software component for a personal computer.

FIG. 7 is a high level schematic representation that conceptually illustrates an embodiment of a PDA Pay eTicket System software component for a PDA.

FIG. 8 is a high level schematic representation conceptually illustrating an embodiment of a PDA Pay eTicket system software component for a server computer.

FIG. 9 is a diagrammatic representation showing an example of an interface between a user, retailer, clearinghouse, financial institution and system administrator.

10a-10c are high level functional flow charts illustrating an example of a basic interface independent process for using a PDA or PDA / wireless telephone with a PDA Pay eTicket system.

11a-11d with PDA and / or wireless telephone with wireless modem,
3 is a high level functional flowchart illustrating an example of an online financial service provider interface.

12a-12d are high level functional flow charts illustrating an example of an authorized online distributor interface for Ticketdownload..com.

13a-13c are high level functional flowcharts illustrating an embodiment of the PDA eTicket checkout aspect of the present invention.

14a-14b are high level functional flow charts illustrating an embodiment of a PDA unlock routine using a personal computer.

15a-15c are high level functional flowcharts illustrating an embodiment of a PDA unlock routine through an authorized service center.

FIG. 16 is a high level functional flowchart showing personal computer system interface processing in an example of a specified purpose system device in an embodiment of the present invention.

17a to 17d are high-level functional flowcharts showing Download eCash processing for an example designated purpose system device in an embodiment of the present invention.

FIG. 18a is a high level functional flowchart illustrating personal medical, insurance, and emergency data interface processing for an example directed purpose system device in accordance with an embodiment of the present invention.

FIG. 18b is a high level functional flowchart illustrating a prescription download interface process in an example designated purpose system device in accordance with an embodiment of the present invention.

19a-19c are schematic representations showing various views of an example external configuration of an embodiment of a directed purpose system device.

FIG. 20a is a high level schematic representation that conceptually illustrates another example of a Directed Purpose System device configuration that includes a biometric reader and additional context sensitive user input buttons.

FIG. 20b is a schematic diagram illustrating example components and connections between example components of an embodiment of PayStick ^™ .

FIG. 20c is a schematic diagram showing an example of physical connections between the example components shown in FIG. 20b.

20d is a parts list showing example specifications for the example components shown in FIG. 20b.

20e and 20f are example material tables for the example components shown in FIG. 20a, FIG. 20e showing English specifications, and FIG. 20f showing German specifications.

21a to 21b are high-level functional flowcharts showing an example of transaction interface processing between an electronic currency enabled designated purpose system device and a sales floor terminal or an electronic kiosk according to an embodiment of the present invention.

22a to 22b are high-level functional flowcharts showing an example of an electronic currency / ticket download process between the specified purpose system device example and the authorized service provider in the embodiment of the present invention.

23a to 23b are high-level functional flowcharts showing an example of an electronic currency exchange process between a specified purpose system device example and a system usable PDA / wireless telephone example in the embodiment of the present invention.

FIG. 24 is a data relationship diagram of an example data structure for data maintained by a server and / or PDA / wireless / directed purpose device.

FIG. 25 is a schematic representation of a user interface welcome screen provided to a user PC according to an embodiment of the invention.

FIG. 26 is a diagram showing a main program provided to a user PC according to an embodiment of the present invention.
9 is a schematic representation of a menu user interface screen.

FIG. 27 is a diagram illustrating a user provided to a website where a directed purpose system device user interfaces with a server system according to an embodiment of the present invention.
A schematic representation of an interface welcome screen.

FIG. 28 is a schematic representation of a Main Menu User Interface screen provided to a Directed Purpose System device website interface according to an embodiment of the present invention.

FIG. 29 is a high level simplified schematic representation of an example relationship between some components of an embodiment of the present invention.

FIG. 30 is a high level simplified schematic representation of example mobile device components of an embodiment of the present invention.

FIG. 31 is a high-level simplified schematic representation of example server-side components of an embodiment of the present invention.

FIG. 32 is a high level simplified schematic representation showing a micropayment transmission interface between example portable device components of an embodiment of the present invention.

FIG. 33 is a high-level simplified schematic representation showing a micropayment transfer interface between an example mobile device component, an example sales floor terminal sales / service component, and an example server-side component of an embodiment of the present invention.

FIG. 34 is a high level representation of a seller credit transfer interface between example handheld device components, point-of-sale terminal / server or online application component examples, other server components and example server-side components of embodiments of the present invention. It is a simplified schematic display.

FIG. 35 is a vendor between example handheld device components, server terminal sales / service or online application component examples, other server components, server-side component examples of embodiments of the present invention, where server account transfer is typical. Credit server
3 is a high-level simplified schematic display showing an account transfer interface.

FIG. 36 is an example of a mobile PayStick device component, a point-of-sale terminal sales / service or online application component example, another server component, a vendor credit server account transfer between server-side component examples of embodiments of the present invention. Is a high-level simplified schematic display showing.

─────────────────────────────────────────────────── ─── Continued front page    (31) Priority claim number 60 / 255,980 (32) Priority date December 15, 2000 (December 15, 2000) (33) Priority claiming countries United States (US) (81) Designated countries EP (AT, BE, CH, CY, DE, DK, ES, FI, FR, GB, GR, IE, I T, LU, MC, NL, PT, SE, TR), OA (BF , BJ, CF, CG, CI, CM, GA, GN, GW, ML, MR, NE, SN, TD, TG), AP (GH, G M, KE, LS, MW, MZ, SD, SL, SZ, TZ , UG, ZW), EA (AM, AZ, BY, KG, KZ, MD, RU, TJ, TM), AE, AL, AM, AT, AU, AZ, BA, BB, BG, BR, BY, CA, C H, CN, CR, CU, CZ, DE, DK, DM, EE , ES, FI, GB, GD, GE, GH, GM, HR, HU, ID, IL, IN, IS, JP, KE, KG, K P, KR, KZ, LC, LK, LR, LS, LT, LU , LV, MA, MD, MG, MK, MN, MW, MX, NO, NZ, PL, PT, RO, RU, SD, SE, S G, SI, SK, SL, TJ, TM, TR, TT, TZ , UA, UG, US, UZ, VN, YU, ZA, ZW

Claims (27)

[Claims] 1. A computer system programmed to wirelessly pay for a purchase price, which electronically communicates wirelessly with a financial institution system to download electronic money for sale for a seller. A computer system characterized in that it is electronically wirelessly communicated with a merchant financial system, and is programmed to electronically wirelessly transfer the downloaded electronic money to a seller's account to pay the purchase price. 2. A computer for wirelessly electronically transferring authorization transactions.
A computer system, wherein the system is programmed to wirelessly electronically download the electronic transaction authorization and programmed to wirelessly electronically redeem the electronic transaction authorization. 3. A computer-implemented method for wireless purchase location payment, the method comprising: providing a first purchase location payment device for storing payment authorization data; and storing the payment authorization data in the first device. And providing a second purchase location payment device for receiving said payment authorization data, and said first purchase location payment device to said second purchase location payment device via a wireless communication connection. Sending payment authorization data, and sending a payment confirmation from the second purchase location device to the first purchase location payment device via the wireless communication connection. . 4. A computer program product embodying computer program instructions for execution by a computer, the payment authorization data being transmitted via a wireless communication connection, the payment authorization data being transmitted via the wireless communication connection. A computer program product characterized in that it includes instructions for receiving confirmation. 5. A purchase location payment computer system comprising a computer processing device, a wireless communication interface connected to the computer processing device, and program instructions, the purchase location device including a memory device connected to the computer processing device. Including a set of program instructions operable to execute the program instructions, the program instructions transmitting payment authorization data via the wireless communication interface; A place-of-payment computer system including a set of program instructions for receiving confirmation of payment via a communication interface. 6. A purchase location payment computer system comprising a computer processing device, a wireless communication interface connected to the computer processing device and a portable device including a memory device connected to the computer processing device and including program instructions. Including a set of program instructions operable to execute the program instructions, the program instructions receiving payment authorization instructions via the wireless communication interface; and the payment authorization received. A place of purchase, comprising a set of program instructions for executing instructions and a set of program instructions for transmitting payment authorization via the wireless communication interface in response to the executed payment authorization instruction. Payment computer system. 7. A computer program product embodying computer-executable computer program instructions for wirelessly electronically paying a purchase price, the method comprising: receiving a payment authorization instruction via a wireless communication interface;
A computer program product comprising instructions for executing received payment authorization instructions and sending payment authorization via a wireless communication interface in response to said executed payment authorization instructions. 8. A computer program product embodying computer-executable computer program instructions for electronically wirelessly paying a purchase price, the computer program product comprising: a payment authorization instruction executable via a wireless communication interface. A computer program product comprising instructions for transmitting and receiving, via a wireless communication interface, an electronic payment authorization corresponding to the transmitted payment authorization instruction. 9. A computer system for redeeming an electronic authorization certificate comprising a computer processing device, a wireless communication interface connected to the computer processing device, and program instructions, the memory device connected to the computer processing device. Including a portable device, the computer processing device being operable to execute the program instructions, the program instructions comprising:
Responsive to the set of program instructions for receiving the approval certificate transfer instruction via the wireless communication interface, the set of program instructions for executing the received approval certificate transfer instruction, and the executed approval certificate transfer instruction. A computer system comprising a set of program instructions for transmitting an authorization certificate via the wireless communication interface. 10. A computer program product embodying computer-executable computer program instructions for wirelessly electronically redeeming an authorization certificate, the authorization certificate transfer via said wireless communication interface. A computer including instructions for receiving an instruction, executing the received authorization certificate transfer instruction, and transmitting an authorization certificate transfer over the wireless communication interface in response to execution of the authorization certificate. -Program product. 11. A computer program product embodying computer-executable computer program instructions for wirelessly electronically redeeming an authorization certificate, the authorization certificate executable via a wireless communication interface. A computer program product comprising instructions for transmitting a written transfer instruction and receiving, via a wireless communication interface, an electronic approval certificate transfer corresponding to the transmitted approval certificate transfer instruction. 12. A computer-implemented method for electronically wirelessly paying a purchase price, comprising receiving a request for payment of a certain amount from an intermediary terminal of a seller, the request comprising a customer and a customer. With data identifying the device, generating a set of executable payment authorization instructions to pay the requested amount directed to the customer, and an intermediary terminal oriented to pass to the customer's device. Sending to said set of executable payment authorization instructions. 13. A computer system for wirelessly electronically transferring medical information, comprising a computer processing device, a wireless communication interface connected to the computer processing device, and program instructions. A portable device including a memory device coupled to the computer processing device, the computer processing device operable to execute the program, the program instructions receiving medical information transfer instructions via the wireless communication interface. A set of program instructions for executing a received medical information transfer instruction, and transmitting medical information via the wireless communication interface in response to the execution of the medical information transfer instruction. And a set of program instructions for Computer system. 14. A computer program product embodying computer-executable computer program instructions for wirelessly electronically redeeming an authorization certificate, the medical information transfer instructions via said wireless communication interface. A computer for receiving medical information, executing the received medical information transfer instruction, and transmitting medical information via the wireless communication interface in response to the execution of the medical information transfer instruction. Program product. 15. A computer program product embodying computer-executable computer program instructions for wirelessly electronically transferring medical information, the medical information transfer being executable via a wireless communication interface. A computer program product comprising instructions for transmitting instructions and receiving medical information corresponding to the transmitted medical information via a wireless communication interface. 16. A purchase location payment computer system comprising a computer processing device, a wireless communication interface connected to the computer processing device, and program instructions, the purchase location including a memory connected to the computer processing device. A device including a device, the computer processing device operable to execute the program instructions, the program instructions receiving payment authorization data via the wireless communication interface; A place-of-payment computer system including a set of program instructions for sending a payment confirmation via a communication interface. 17. A purchase location payment computer system comprising: storage means for storing payment approval data; receiving means for receiving the payment approval data; and wirelessly transmitting the payment approval data from the storage means to the receiving means. A purchase location payment computer system comprising means for transmitting via communication means and means for transmitting payment confirmation from the receiving means to the storage means via the wireless communication means. 18. A computer-implemented method for transferring an authorization certificate, comprising:
Providing a first computer processing device configured with a first memory storage device for storing an electronic approval certificate, and storing the electronic approval certificate on the first memory storage device of the first computer processing device And providing a second computer processing device for receiving the electronic transmission of the electronic authorization certificate, and from the first computer processing device to the second computer processing device via a wireless communication connection. Sending the electronic authorization certificate. 19. A computer program product embodying computer program instructions for execution on a computer, including instructions for transmitting an electronic authorization certificate over a wireless communication connection. Computer program product. 20. A computer implemented authorization certificate transfer system comprising a computer processing device, a wireless communication interface connected to the computer processing device, and program instructions, the device including a memory connected to the computer processing device. And the computer processing unit is operable to execute the program instructions, the program instructions including a set of program instructions for transmitting an authorization certificate via the wireless communication interface. A computer-implemented approval certificate transfer system. 21. A computer-implemented approval certificate transfer system, wherein the computer system stores storage means for approval certificate, receiving means for the approval certificate, and wireless communication means from the storage means. Means for transmitting the authorization certificate to the receiving means via the. 22. A computer-implemented method for paying a small service charge for a small transaction, the steps of establishing a user micropayment account for each of a plurality of users, and each user micropayment account. Is funded with electronic funds, said electronic funds being equal to the amount deposited in a bank account for a particular micropayment processing provider with each particular user as a recipient. Computer execution method. 23. A wireless handheld device for paying a small service charge for a small transaction, the executable program calculating a percentage amount equal to a pre-established percentage of the transaction amount, and the calculated percentage amount. Wireless handheld device including an executable program for reducing the amount of service charges only for micropayments. 24. A wireless handheld device for paying a small service charge for a small transaction, a memory storage device for storing data, an executable memory, a microprocessor, and short-range wireless communication. Hardware, program instructions to support short-range wireless communications, executable programs that calculate a percentage equal to a pre-established percentage of the transaction amount, and a reduction of the service fee micropayment-only amount by the calculated percentage amount. A portable wireless device, comprising: 25. A computer-implemented method for processing a small service charge payment for a small transaction, the step of calculating a percentage amount equal to a pre-established percentage of the transaction amount, and the calculated percentage amount. And a step of reducing the amount of service charges only for micropayments. 26. A computer-implemented method for collecting a small service charge payment for a small transaction, the step of receiving the transaction amount via a wireless interface with a merchant, and a pre-established percentage of the transaction amount. Calculating a percentage amount equal to, generating a transaction to the financial clearinghouse system, reducing the amount in the seller's account by the calculated percentage amount, and adding the amount to the account for micropayment collection. Depositing a calculated percentage amount. 27. A computer-implemented method for collecting small service charge payments for small transactions, comprising the steps of receiving a plurality of transaction amounts via a wireless interface with a seller and summing the plurality of transaction amounts. And calculating a percentage amount equal to a pre-established percentage of the sum of the transaction amounts, and generating a transaction for the financial clearinghouse system, the calculated percentage amount being the amount in the seller's account. And depositing the calculated percentage amount in an account for collecting micropayments.