Method and system for facilitation of wireless e-commerce transactions

ES 2 249 461 T3

DESCRIPTION

Method and system to facilitate wireless electronic commerce transactions.

What is disclosed here generally refers to mobile e-commerce, and more particularly to methods and systems to facilitate wireless e-commerce transactions.

Wireless e-commerce is expected to grow extraordinarily. The sheer magnitude of the opportunity is impressive. The number of mobile devices with Internet access is expected to exceed the number of personal computers by 2003. It is anticipated that by 2004 the majority of e-commerce purchases will be made through wireless communication devices.

With the convergence of location information and wireless Internet access, users of wireless communication devices will be able to receive product offers related to their location and interests. This will open up a whole new method of targeting your target customers. A key area of ​​interest in wireless e-commerce is the communication of targeted advertisements to wireless devices. However, to take full advantage of wireless e-commerce, users will need to be in a position to act on such advertising in real time. This will require transactions to be made via a live wireless communication device upon receipt of an advertisement for a product or service.

However, there are several hurdles that must be overcome to make these wireless e-commerce transactions common. One of these widely accepted obstacles to wireless transactions is security. For wireless transactions to be accepted, the systems must be applied in such a way as to avoid unauthorized purchases on a user's wireless account. Such security measures are even more important in the case of a wireless communication device, due to the possibility of the wireless communication device being lost or stolen. Since wireless communication devices are significantly less secure than non-portable communication devices, steps must be taken to provide a high degree of security. However, current e-commerce security solutions are limited in their ability to provide effective and efficient solutions to facilitate secure wireless e-commerce transactions.

Another hurdle that must be overcome in making wireless e-commerce transactions common is interconnecting e-commerce transactions to “real world” products and services. For example, if an authorized user of a wireless communication device purchases a theater ticket for a movie at a particular theater using their wireless communication device, systems must be in place to notify the theater that the ticket has been purchased by an authorized user. In addition, systems must be implemented that allow the authorized user of the wireless communication device to enter the theater and the movie once they are in the theater.

Today's solutions for interconnecting e-commerce transactions to real-world products are cumbersome and time-consuming. As a result, they far outweigh the convenience of facilitating a wireless e-commerce transaction. For example, a current solution to interconnect an e-commerce transaction with a corresponding real-world product requires that a printed confirmation, such as receipt, pass, or ticket, be printed on a printer. This solution requires that the hard copy confirmation be generated at a physical location. Printed confirmations often include non-standardized barcodes that are processed at the merchant's location. Typically, the paper confirmation requires to be generated in a location other than the location where the wireless e-commerce transaction is executed.

Consequently, what is needed is a method to enable wireless e-commerce transactions to be facilitated and fulfilled safely and conveniently.

WO 00/62260 is an international patent application which is part of the prior art for novelty purposes only under Article 54 (3) EPC. This application describes a receipt system in which the "receipt" is stored in a memory module of a mobile communications terminal, the receipt being communicated to a reader device of a service device through a contactless interface.

According to a first aspect of the present invention, a method of facilitating a wireless transaction includes:

receiving, by a transaction management system, a transaction request from a transaction requester; verify an identity of the requestor of the transaction; communicating a first transaction code (PCBT) to a wireless communication device;

displaying the first transaction code (PCBT) on a screen of the wireless communication device;

optically scan the first transaction code (PCBT) from the screen; Y

ES 2 249 461 T3 receive, by a transaction fulfillment system, the scanned representation of the first transaction code (PCBT) to allow full or partial fulfillment of the transaction request.

According to a second aspect of the present invention, a system for facilitating a wireless transaction includes: a transaction management system capable of:

receive a transaction request from a transaction requester; verify an identity of the requestor of the transaction;

communicating a first transaction code (PCBT) to a wireless communication device; and, a transaction fulfillment system coupled to the transaction management system (302) capable of optically scanning the transaction code from a display of the wireless communication device.

Brief description of the drawings

Fig. 1 is a flow chart illustrating one embodiment of a method for facilitating a wireless transaction.

FIG. 2 is a flow chart illustrating one embodiment of a method for facilitating authentication of a spoken authentication code of a transaction requester.

Fig. 3A is a flow chart illustrating one embodiment of a method for facilitating compliance with a wireless transaction, where verification of the transaction code is completed by a transaction management system.

FIG. 3B is a flow chart illustrating one embodiment of a method for facilitating wireless transaction fulfillment, where verification of the transaction code is completed by a transaction fulfillment system.

Fig. 4 is a synoptic diagram illustrating one embodiment of a system for facilitating a wireless transaction using a telephone-type wireless communication device.

Fig. 5 is a diagrammatic view illustrating an embodiment of a telephone-type wireless communication device.

Fig. 6 is a synoptic diagram illustrating one embodiment of operations for carrying out a wireless transaction using the system illustrated in Fig. 4.

Fig. 7 is a synoptic diagram illustrating one embodiment of a system for facilitating the fulfillment of a wireless transaction using a non-telephone type wireless communication device.

Fig. 8 is a diagrammatic view illustrating an incorporation of a non-telephone type.

Fig. 9 is a synoptic diagram illustrating one embodiment of operations for carrying out a wireless transaction using the system illustrated in Fig. 7.

Fig. 10 is a synoptic diagram illustrating another embodiment of operations for carrying out a wireless transaction using the system illustrated in Fig. 7.

Detailed description

One embodiment of a method for facilitating a wireless transaction is illustrated in FIG. 1. In a box 100, the method includes an operation of facilitating an authenticated transaction request from the requester. In box 200, the method includes a wireless communication device facilitation operation that enables transaction fulfillment.

By wireless transaction is meant a transaction requested and fulfilled through the use of a wireless communication device. By wireless communication device that enables the fulfillment of a transaction it is meant that the wireless communication device is used to facilitate the fulfillment of the actual products or services requested. Internet-enabled cordless phones, Internet-enabled wireless personal digital assistants (wPDAs), and wireless notebook computers illustrate examples of suitable wireless communication devices capable of connecting to, and communicating over, a computer network system, such as the Internet. More generally, the wireless communication devices studied here are wireless communication devices capable of accessing a public or private computer network, or both.

ES 2 249 461 T3

As described in more detail below, apparatus for facilitating the methods and operations mentioned herein may include functional systems, such as a transaction management system and a transaction fulfillment system. The transaction requester uses a wireless communication device to communicate information to and from the transaction management system and the transaction fulfillment system.

Two or more of the functional systems of the apparatus, such as the transaction management system and the transaction fulfillment system, may be located remote from each other. However, in some applications, it may be advantageous for the functional systems to be located in the same physical location. In these applications, it may also be advantageous for a simple integrated hardware system to include the transaction management system and the transaction fulfillment system.

The portability of wireless communication devices requires that sufficient security measures are applied to ensure that the requestor for the transaction is an authorized user of the wireless communication device. Such security measures are intended to ensure that an unauthorized user of the wireless communication device cannot facilitate a transaction using the wireless communication device. Accordingly, it is advantageous that the method of facilitating the wireless transaction includes an operation to verify that the requestor for the transaction is an authorized user of the wireless communication device.

One embodiment of a method for executing the facilitation operation of the authenticated transaction request from the requester, box 100 of FIG. 1, is illustrated in FIG. 2. In box 102, the method includes receiving, on the system. transaction management, a transaction request from a wired or wireless communication device from a transaction requester. In box 104, the identity of the transaction requestor is authenticated. In box 106, a first transaction barcode (PCBT) is communicated to the wireless communication device. Depending on the architecture configuration of the system used to carry out method 100, the PCBT can be communicated from the transaction management system or the transaction fulfillment system.

The PCBT illustrates a first example of an optically scannable transaction code to facilitate transaction request fulfillment. In subsequent operations mentioned herein, the PCBT is displayed on a screen of the wireless communication device to be optically scanned by a component of the transaction fulfillment system to allow full or partial fulfillment of the transaction request.

Voice authentication illustrates an example of a suitable technique for executing transaction requester identity verification operation at box 104. One method for executing transaction requester voice authentication operation includes receiving , in box 104a, an authentication code of the spoken transaction requester. It is contemplated that the spoken authentication code may be received from a corded telephone or from the wireless communication device. In box 104b, a comparison operation of the authentication code of the spoken transaction requester is executed. In box 104c, an operation is performed to determine the match between the authentication code of the spoken transaction requester and an authentic voiceprint for an authorized user of the wireless communication device.

An example of voice authentication includes a wireless phone user calling a secure server and saying their phone number. The spoken phone number illustrates an example of the authentication code of the spoken transaction requester. The spoken telephone number is then compared to an authentic voice print of an authorized user of the wireless communication device. If the authentication code of the spoken transaction requester matches the authentic voiceprint, the transaction requester is allowed to continue to fulfill the transaction.

One embodiment of a method for executing the operation of facilitating compliance with the permitted transaction of the wireless communication device, the box 200 of FIG. 1, is illustrated in FIG. 3A. The method for embedding illustrated in Fig. 3A is more suitable for being facilitated by a system in which the verification of the transaction codes is executed in the transaction management system. In box 201, the PCBT is received by the wireless communication device. In box 202, the PCBT is scanned from the wireless communication device. In box 204 the PCBT is checked. Verification of the PCBT includes decoding the scanned PCBT in box 204a, communication of the decoded PCBT to the transaction management system in a box 204b, and cross-correlation of the decoded PCBT to a first transaction compliance action in box 204c . In a box 206 the first transaction fulfillment action is executed.

In a box 208 a second transaction barcode (SCBT) is received by the wireless communication device. In a box 210 the SCBT is scanned from the wireless communication device. In a box 212 the SCBT is verified. Verification of the SCBT includes decoding the scanned SCBT in box 212a, communication of the decoded SCBT to the transaction management system in box 212b, and cross-correlation of the decoded SCBT to a first transaction fulfillment action in box 212c . In a box 214 the second transaction fulfillment action is executed.

ES 2 249 461 T3

The first and second compliance actions can be physical or informational actions. Activating a turnstile at the entrance to a movie theater illustrates an example of a physical action. Communicating where to go to a hotel illustrates an example of an informative action.

Another embodiment of a method for executing the operation of facilitating the fulfillment of a transaction enabled by a wireless communication device, box 200 in FIG. 1, is illustrated in FIG. 3B. The method illustrated in Fig. 3B is more suitable for being facilitated by a system in which the verification of the transaction codes is executed in the transaction fulfillment system. In box 201, the PCBT is received by the wireless communication device. In box 202, the PCBT is scanned from the wireless communication device. In box 204 the PCBT is checked. Verify the PCBT includes decoding the scanned PCBT in a box 204a, cross-correlation of the decoded PCBT for a first transaction compliance action in a box 204b, and communication of a first compliance verification (PVC) to the transaction management system in a 204c box. Compliance checks can be used by the transaction management system to coordinate operations, such as removing the requested transaction from a list of available transactions. In a box 206 the first transaction fulfillment action is executed.

In a box 208 a second transaction barcode (SCBT) is received by the wireless communication device. In a box 210 the SCBT is scanned from the wireless communication device. In a box 212 the SCBT is verified. SCBT verification includes decoding the scanned SCBT in a box 212a, cross-correlation of the decoded SCBT for a first transaction compliance action in a box 212b, and second compliance verification communication (SVC) for the transaction management system in a 212c box. In a box 214 the second transaction fulfillment action is executed.

An embodiment of a transaction apparatus 300 for carrying out the methods of Figs. 1-3B using a telephone-type wireless communication device is illustrated in Fig. 4. The transaction apparatus 300 includes a transaction management system 302 coupled to a transaction fulfillment system 304 and a customer system 305 . It is also contemplated that in some applications it may be advantageous for the customer computing system to be bypassed from, or detached from, the transaction apparatus 300. The transaction management system 302 is coupled to the transaction fulfillment system 304 via a computer network system 306. A wireless communication device 308 is coupled to the transaction management system 302 and the transaction fulfillment system 304 through a telecommunications network system 310. A transaction requester 312 uses the wireless communication device 308 for the communication with the transaction management system 302 and the transaction compliance system 304.

A Transport Control Protocol / Internet Protocol (TCP / IP) computer network system illustrates an example of a computer network system 306. A suitable TCP / IP computer network system is a global computer network such as the Internet.

The telecommunications network system 310 includes a wireless telecommunications network and a wired telecommunications network. The telecommunications network system 310 enables the communication of voice and data information to and from the transaction management system 302 and the transaction fulfillment system 304. The Sprint, AT&T, and Southwestern telecommunications networks Bell illustrate examples of the 310 telecommunications network system.

The transaction management system 302 includes a central processing unit (CPU) 302a, an information storage device 302b, a network interface system 302c, speech services module 302d, and barcode software 302e. A network server or workstation comprises CPU 302a. A Dell PowerEdge ™ serial server illustrates an example of a suitable commercially available network server. A Dell Precision ™ Series Workstation illustrates an example of a suitable commercially available workstation.

Information storage device 302b, such as a floppy drive, is coupled to CPU 302a for storing information in non-volatile memory. A Dell PowerVault ™ series storage device illustrates an example of a suitable 302b information device. Compliance information, barcode information, and authentic voice prints illustrate examples of information retrieved from information storage device 302b.

Network interface system 302c is coupled to CPU 302a to facilitate communication of information between transaction management system 302, computer network system 306, and wireless communication device 308. A suitable network interface system includes a router, such as a Cisco Systems 7200 series unit coupled to a data service unit / channel service unit (DSU / CSU), such as a serial unit. ADC Kentrox D-Serv^TM.

The spoken services module 302d enables communication of voice signals between the wireless communication device 308 and the transaction management system 302. The spoken services module 302d includes components such as hardware and software to enable voice authentication.

ES 2 249 461 T3

Voice authentication is a desirable technique to verify the identity of the transaction requester. Wireless communication devices are not well suited for inputting alpha information. The spoken authentication codes can be effectively and conveniently communicated from a wireless communication device such as a cordless phone. Consequently, the use of voice authentication reduces the difficulty of presenting identity verification information.

Voice authentication technologies are commercially available from a number of sources. An example of suitable voice authentication is Nuance Verifier 2.0, offered by Nuance Communications. Nuance Verifier is tightly integrated with Nuance 7.0 speech recognition software to ensure an exceptional level of user comfort and safety. Users are recognized and authenticated simultaneously, thus shortening the total duration of the call and eliminating the need for users to remember personal identification numbers and passwords.

The tight integration of speech authentication and speech recognition technologies enables Nuance Verifier 2.0 to take advantage of the unique distributed architecture associated with the Nuance platform. This architecture supports simultaneous load balancing of speech recognition, natural language understanding, speech authentication, and text-to-speech resources. It ensures optimal use of each server CPU on the network, thus minimizing the amount of hardware required, and the associated cost, for a given speech system.

The SpeakEZ ™ speaker voiceprint verification software offered by T-Netix Incorporated illustrates another example of voice authentication software. Smart Tone Technologies Incorporated offers proprietary software to enable positive voice identification on corded and mobile phones, and in Internet applications. Both software offerings illustrate additional examples of voice authentication software that can be incorporated into the speech services module 302d.

The SpeakEZ speaker's voiceprint verification functionality has been incorporated into a number of commercially available software development toolkits and interactive voice response (IVR) systems. These types of RVI systems and development toolkits are suitable for providing the 302 transaction management system with voice authentication functionality. Examples of commercially available RVI systems and software development toolkits that incorporate SpeakEZ speaker voiceprint verification include the following. BioNetrix has SpeakEZ speaker voiceprint verification built into its BioNetrix Authentication Suite. Envoy Incorporated has integrated SpeakEZ speaker speech fingerprint verification into a number of its computer telephony development toolkits. IBM has SpeakEZ speaker voiceprint verification built into its RVI DirectTalk / 6000 and DirectTalk / 2 systems. Periphonics Corporation has SpeakEZ speaker voiceprint verification built into its VPS family of RVI systems.

The 302e barcode software enables the encoding and decoding of barcodes. The barcode software 302e is accessible by the CPU 302a from a computer-readable medium, such as a compact disk, floppy drive, or network connection. Commercially available barcode software from Omniplanar Incorporated, Peemet Incorporated, and RVB Systems Group illustrates examples of 302e barcode software.

Transaction fulfillment system 304 includes central processing unit (CPU) 304a, information storage device 304b, network interface system 304c, barcode reader 304d, and barcode software 304e . A network server or workstation comprises CPU 304a. A Dell PowerEdge ™ serial server illustrates an example of a suitable commercially available network server. A Dell Precision ™ Series Workstation illustrates an example of a suitable commercially available workstation.

Information storage device 304b, such as a floppy drive, is coupled to CPU 304a for storing information in non-volatile memory. A Dell PowerVault ™ serial storage device is an example of a suitable storage device. Compliance response information, product information, and barcode information illustrate examples of information that can be retrieved from the information storage device 304b.

Network interface system 304c is coupled to CPU 304a to facilitate communication of information between transaction fulfillment system 304, computer network system 306, and wireless communication device 308. A router such as, for example, a Cisco Systems 7200 series unit coupled to a data service unit / channel service unit (DSU / CSU), such as a Kentrox D-Serv ADC series unit^TM illustrates an example of the network interface system 304c. Based on the volume of transaction requests fulfilled through the transaction fulfillment system 304, a network interface card ("NIC") and a modem illustrate two other examples of a suitable network interface system 304c.

Bar code reader 304d allows transaction codes, such as bar codes, to be optically scanned and decoded. Bar code reader 304d is coupled to CPU 304a to communicate a scanned representation of a bar code to CPU 304a. Metrologic Incorporated offers several commercially available barcodes. Metrologic offers a fixed scanner with model # S7001 and a tabletop scanner with model # MS860.

ES 2 249 461 T3

The 302e barcode software enables the encoding and decoding of barcodes. The barcode software 302e is accessible by the CPU 302a from a computer-readable medium, such as a compact disk, floppy drive, or network connection. Bar code software that is commercially available from Omniplanar Incorporated, Peernet Incorporated and RVB Systems Group illustrates examples of 302e bar code software.

The customer computer system 305 is the system of the entity that offers the product or service requested in the transaction request. The customer computer system 305 communicates with the transaction management system 302 and the transaction fulfillment system 304 to facilitate the transaction. The client system 305 includes a network interface, a CPU 305a, an information storage device 305b, and a network interface device 305c. CPU 305a is coupled to information storage device 305b to store information, such as product and service information, in non-volatile memory. Network interface device 305c is coupled between CPU 305a and computer network system 306 to allow communication between them.

The wireless communication device 308 includes a device controller 308a, sound devices 308b, a keyboard 308c, a display 308d, and a transceiver 308e. Device controller 308a is capable of controlling and integrating the operation of sound devices 38b, keyboard 308c, display 308d, and transceiver 308e. Sound devices 308b, such as a microphone and speaker allow the transaction requestor 312 to present and listen to spoken information. Keypad 308c allows the requestor of transaction 312 to present typed information. Display 308d allows transaction requestor 312 to view visual information received by, and communicated from, wireless communication device 308.

The transceiver 308e is capable of allowing the communication of voice and data information between the wireless communication device 308 and the telecommunications network system 310. In this way, the information is communicated to and from the management system of the network. transaction 302 and the transaction fulfillment system 304. In incorporating the system architecture illustrated in Fig. 4, voice and data information is communicated to and from the transaction management system 302, and only data information is communicated to and from the transaction fulfillment system.

As illustrated in FIG. 5, the wireless communication device 308 includes a scrolling device 308e. A user interface 308f is displayed on the screen 308d of the wireless communication device 308. Using the scrolling device 308e, a desired transaction code name 308g is selected from a list of transaction code names 308h displayed on the screen 308d. . An optically scannable transaction code 308i is displayed on the screen 308d in response to selecting the desired transaction code name 308g.

A Wireless Application Protocol (WAP) enabled by a cordless phone illustrates an example of the 308 wireless communication device. In addition to wireless phones and devices that enable WAP, wireless communication devices that operate under other wireless protocols such as imode, sms, and hdml they can be used with the methods and systems discussed herein. Cordless phones capable of accessing computer networks, such as the Internet, are commercially available from various cordless phone manufacturers.

The transaction apparatus 300 of FIG. 4 allows the wireless transaction to be carried out by telephone-type wireless communication devices, such as wireless telephones with Internet access. However, by replacing the telecommunications network system with a wireless local area network system or adding a wireless local area network system to the transaction apparatus 300, the transaction apparatus 300 can be used to facilitate a wireless transaction using a telephone communication device that allows non-telephone Internet access, such as a wireless PDA. By carrying out the transaction requests with the non-telephone wireless communication device as mentioned, the authentication of the transaction requester can be more effectively achieved by known data password techniques rather than voice authentication.

The transaction apparatus 300, FIG. 4, is capable of allowing communication directly between a transaction fulfillment system 304 and a wireless communication device 308. To this end, the transaction fulfillment system 304 and the communication device Wireless 308 each include a digital low power short range radio communication 314 integrated therein. Each digital radio communication 314 includes a radio transceiver to allow voice and data information to be communicated between the transaction fulfillment system 304 and the wireless communication device 308 without being communicated through the computer network system 306 or the communication system. telecommunications network 310. The speed of information transfer between the transaction fulfillment system 304 and the wireless communication device 308 is significantly increased by the elimination of the need to communicate such information through the computer network system 306 and the network system. telecommunications 310.

A Bluetooth ™ radio illustrates an example of 314 digital radio communication. Bluetooth radios are based on a radio specification governed by the Bluetooth Special Interest group. The specification defines the standards for a tiny microchip that includes a radio transceiver. Consequently, Bluetooth radios are embedded in digital devices such as mobile phones, PDAs, laptops, etc.

The Bluetooth radio makes the communication of information almost instantaneous. It facilitates fast and secure transmissions of both voice and data, even when the devices are not within the line of sight. Ope7 transceivers

ES 2 249 461 T3 ran in a globally available frequency band, ensuring compatibility around the world. The Ericsson R520 cordless phone illustrates an example of a cordless phone that enables Bluetooth. The R520 phone is a triple mode phone with GPRS, Bluetooth radio, and WAP capabilities.

A key aspect of the system and method embodiments mentioned herein is the capability and functionality associated with the transaction codes optically scanned from the display of the wireless communication device. Optical transaction code scanning facilitates a secure and convenient technique that enables real-world product and service fulfillment from a wireless transaction. The transaction requester must simply pass the screen of the wireless communication device over the barcode reader of the transaction fulfillment system to activate wireless transaction fulfillment.

Many wireless communication devices such as cordless phones and PDAs have relatively small screens. As a result, the optically scannable code communicated to wireless communication devices must be relatively compact. One-dimensional barcodes and truncated two-dimensional barcodes illustrate examples of barcodes suitable for communicating to devices that have displays that are capable of displaying bitmap images. It is anticipated that commercially available wireless communication devices will eventually be able to display larger barcodes, such as two-dimensional barcodes. One of the advantages of the two-dimensional barcode is the ability to include several thousand bytes of information in the barcode.

Bar codes configured according to the Code 128 Specification illustrate an example of a bar code configuration suitable for small displays of cordless phones. Furthermore, most barcode readers used today are capable of reading Code 128 barcodes. Code 128 barcodes are very high density alphanumeric symbology. The symbol can be as long as necessary to store the encoded data. It is designed to encode all 128 ASCII characters, and will use the least amount of space for data of 6 characters or more of any 1-D symbology. Each data character encoded in a Code 128 symbol is made up of 11 black or white modules. The "stop" character, however, is made up of up to 13 modules. Three bars and three spaces are formed from these 11 modules. Bars and spaces can vary between 1 and 4 modules wide.

Currently, several commercially available wireless communication devices are not capable of displaying bitmap images. One solution for communicating an optically scannable code to these types of wireless communication devices is to communicate a type of "hash code" to these devices. An example hash code includes a string of right slashes (/), representing a binary 1, and left slashes (\), representing a binary 0. Appropriate software would be required to decode these types of code.

As illustrated in Fig. 4, the transaction management system (SGT) 302, the transaction fulfillment system (SCT) 304, the customer computing system (SIC) 305, and the wireless communication device (DCI ) 308 are coupled in such a way as to communicate information to each other. In this embodiment, transaction barcode verification and transaction barcode communication are facilitated by SGT 302. In addition, communication to determine the desired transaction is facilitated by the SGT 302.

Referring to Fig. 6, a receiving operation A, in the SGT 302, a transaction request is executed from the DCI 308. Upon receipt of the transaction request, a communication operation B of a request is executed for a Spoken Transaction Requestor Authentication Code (CAST) from SGT 302 to DCI 308. The request for Spoken CAST is intended to initiate a receive C operation, at SGT 302, a Spoken CAST from DCI 308. A requestor authentication message (MAS) communication operation D from SGT 302 to DCI 308 initiates a transaction first barcode communication operation (PCBT) E to DCI 308. The request authentication message confirms that the transaction request is approved and the PCBT has been communicated. SCT 304 and SGT 302 can interact with SIC 305 to facilitate and enable transaction request fulfillment.

A PCBT scan operation F is executed after operation E. In response to the PCBT scan, a receive operation G, at SGT 302, a decoded representation of the PCBT from SCT 304 is executed. Upon receipt of the decoded representation of the PCBT and in response to the PCBT being verified, a second transaction barcode (SCBT) communication operation H from SGT 302 to DCI 308 is executed. A first compliance action is normally also taken in response to the PCBT being verified. A scan operation I of the SCBT is executed after operation H. In response to the scan of the SCBT, a receive operation J, at the SGT 302, a decoded representation of the SCBT from the SCT 304 is executed. Upon receipt of the decoded representation from the SCBT and in response to the SCBT being verified, a transaction completion message (MCT) communication operation K from SGT 302 to DCI 308 is executed. A second enforcement action is normally also taken in response to the PCBT being verified. Communication from the MCT may be part of the second enforcement action.

After scanning and decoding the PCBT and the SCBT, SCT 304 or SGT 304, or both, perform internal operations. One of these internal operations is to communicate with the client's computer system to allow the facilitation of the requested transaction. SGT 302, SCT 304 or both can use compliance verification for ini8

ES 2 249 461 T3 cite the following internal operations, such as removing a given transaction offer from the available transaction requests.

The first and second transaction barcodes allow the transaction requester to trigger fulfillment of real-world products or services requested in the transaction request. Renting and taking possession of a rented car using a mobile phone represents a viable commercial implementation of the methods set forth herein, the system illustrated in Fig. 4 and the operations described with reference to Fig. 7.

Example 1

Rent a car

A transaction requester who will fly to another city uses his wireless phone with Internet access to rent a car to use during his trip. To do this, he contacts the SGT through his wireless phone. It then interacts with a Transaction Requestor User Interface (IUST) on your wireless phone to communicate car rental information to and from car rental information from the SGT. Car rental information includes typical car rental information such as rental dates, car type, and more. The SGT interacts with the OCS to complete the transaction request. For example, the SGT can interact with the OCS to determine if the selected type of vehicle will be available on the desired days. Once the transaction request is completed, your identity is authenticated using voice authentication techniques, such as those described herein.

Once your identity is authenticated, a PCBT is communicated to your wireless phone. When you arrive at the airport of the city to which you have traveled, you access the IUST to retrieve the PCBT. He then passes the cordless phone over one of the many SCT barcode scanners that are located throughout the airport. By doing so, the PCBT is optically scanned from the screen of your cordless phone. Scanning the PCBT he has confirmed with the SCT that he has arrived at the airport and hopes that the car is ready. Following the PCBT scan, an SCBT is communicated to your cordless phone.

Then he goes to the car rental parking lot. Once in the car rental parking, access the IUST to retrieve the SCBT. Upon retrieval of the SCBT, you optically scan the SCBT from the screen of your cordless phone using a barcode reader that is located in the car rental parking lot. By scanning the SCBT, you have confirmed with the SCT that you have arrived at the car rental parking lot and are ready to take possession of the rental car. After the SCBT scan, an MCT can communicate to your cordless phone. In this example, the SCBT includes information, such as where to go to your hotel, information about the city, etc.

This example illustrates the convenience and time savings associated with using the methods and systems discussed here when renting a car when traveling. The benefits are especially significant for business travelers, as their schedules often change on short notice. However, the advantages associated with these methods and systems allow travelers of all kinds to maintain a tight travel schedule.

An embodiment of a transaction apparatus for carrying out the methods of Figs. 1-3 using a non-telephone wireless communication device is illustrated in FIG. 7. Transaction apparatus 400 includes a transaction fulfillment system 402 coupled to a transaction fulfillment system 404 and a customer computer system 405 . It is also contemplated that in some applications it may be advantageous for the customer computing system to be bypassed from, or detached from, the transaction apparatus 400. The transaction management system 402 is coupled to the transaction fulfillment system 404 via a computer network system 406.

A wireless communication device 408, such as a wireless digital personal assistant, communicates with the transaction management system 402 and the transaction fulfillment system 404 through a wireless data network system 410 and the computer network system. 406. A transaction requester 412 uses the wireless communication device 408 for communication with the transaction management system 402 and the transaction fulfillment system 404.

Wireless data network system 410 is a network system for providing wireless connectivity of non-telephone wireless communication devices. The wireless data network system 410 can include a wireless local area network, a device-specific wireless network, or both. Examples of non-telephone wireless communication devices include lightweight notebooks including wireless modems and wireless PDAs.

The Cisco® Aironet ™ Wireless Local Area Network illustrates an example 410 wireless local area network system. The Aironet Wireless LAN system includes an Aironet 340 family of access points. The access point acts as a bridge by integrating wireless functionality into a wired infrastructure. The Aironet wireless LAN system also includes an Aironet 340 series family of client adapters. An example of a client adapter is an Aironet wireless data modem that connects to a PCMCIA connector on a computer.

ES 2 249 461 T3 portable. The wireless data modem allows the laptop to communicate with a network computer system such as the Internet through an Aironet 340 series access point.

The PalmNet ™ illustrates an example of a device-specific wireless network. The PalmNet provides wireless connection of PDAs offered by Palm Computing Corporation. Through PalmNet, Palm Computing PDA users can communicate information over a global computer network system such as the Internet.

The transaction management system 402 includes a central processing unit (CPU) 402a, an information storage device 402b, a network interface system 402c, and barcode software 402d. A network server or workstation, such as those identified above with reference to Fig. 4, comprises the CPU 402a. Information storage device 402B, as identified above with reference to Fig. 4, is coupled to CPU 402a to store information in non-volatile memory. Compliance information, barcode information, and transaction requester passwords illustrate examples of information that can be retrieved from an information storage device 402b.

Network interface system 402c, as identified above with reference to Fig. 4, is coupled to CPU 402a to facilitate communication of information between transaction management system 402, computer network system 406, and wireless communication device 408. Bar code software 402d, as identified above with reference to Fig. 4, enables the encoding and decoding of bar codes. The barcode software 402d is accessible by the CPU 402a from a computer-readable medium, such as a compact disk, floppy drive, or network connection.

The transaction fulfillment system 404 includes a central processing unit (CPU) 404a, an information storage device 404b, a network interface system 404c, a barcode reader 404d, and barcode software 404e. . The transaction fulfillment system 404 includes a central processing unit (CPU) 404a. A network server or workstation, such as those identified above with reference to Fig. 4, comprises the CPU 404a. Information storage device 404B, as identified above with reference to FIG. 4, is coupled to CPU 404a to store information in non-volatile memory. Compliance response information, transaction codes, product information, and barcode information illustrate examples of information that can be retrieved from the information storage device 404b.

Network interface system 404c, as identified above with reference to Fig. 4, is coupled to CPU 404a to facilitate communication of information between transaction fulfillment system 404, computer network system 406, and wireless communication device 408. Bar code reader 404d, as identified above with reference to FIG. 4, allows bar codes to be optically scanned and decoded. Bar code reader 404d is coupled to CPU 404a to communicate a scanned representation of a bar code to CPU 404a.

Barcode software 404e, as identified above with reference to Fig. 4, enables encoding and decoding of barcodes. Barcode software 404e is accessible by CPU 402a from a computer-readable medium, such as a compact disk, floppy drive, or network connection.

The customer system 405 is the system of the entity that offers the product or service requested in the transaction request. The customer computer system 405 communicates with the transaction management system 402 and the transaction fulfillment system 404 to facilitate the transaction. The client system 405 includes a network interface, a CPU 405a, an information storage device 405b, and a network interface device 405c. CPU 405a is coupled to information storage device 405b to store information, such as product and service information, in non-volatile memory. The network interface device is coupled between the CPU 405a and the computer network system 406 to allow communication between them.

The wireless communication device 408 includes a device controller 408a, a sound output component 408b, a touch screen 408c, and a data transceiver 408d. The device driver is capable of controlling and integrating the operation of the sound output component 408b, touch screen 408c, and data transceiver 408d. The sound output component 408b, such as a loudspeaker, allows the transaction requester to listen to spoken information. Touch screen 408c allows transaction requester 412 to enter information by touching screen 408c, writing on screen 408c, or both.

The data transceiver 408d is capable of allowing communication of data information between the wireless communication device 308, the transaction management system 402, and the transaction fulfillment system 404. The transceiver may also be capable of communicating information. between the wireless communication device 308 and the wireless local area network system 410. In this way, information is communicated between the wireless communication device 408, the transaction management system 402, and the transaction fulfillment system 404.

As illustrated in FIG. 8, the screen 408c of the wireless communication device 308 includes a touch screen. A user interface 408e is displayed on the screen 408c of the wireless communication device 408. Using a suitable physical indication device, a desired transaction code name is selected.

ES 2 249 461 T3

408f from a list of transaction code names 408g displayed on screen 408c. An optically scannable transaction code 408h is displayed on screen 408c in response to selecting the desired transaction code name 408f. A wireless digital personal assistant illustrates an example wireless communication device 408.

As illustrated in FIG. 7, the transaction management system (SGT) 402, the transaction compliance system (SCT) 404, the customer computing system (SIC) 405, and the wireless communication device (DCI). ) 408 are coupled so that information is communicated between them. In this embodiment, transaction barcode verification and transaction barcode communication are facilitated by SCT 404. Communication to determine the desired transaction is facilitated by SGT 402. Referring to Fig. 9, a receive operation A, in SGT 402, a transaction request is executed from DCI 408. Upon receipt of the request for transaction, a communication operation B of a request for a password from SGT 402 to DCI 408 is executed. The password request is intended to initiate a C operation of reception, in SGT 402, of a password from DCI 408. A requestor authentication message (MAS) communication operation D from SGT 402 to DCI 408 initiates a first transaction barcode communication operation (PCBT) E to DCI 408. MAS confirms that the transaction request has been approved and that the PCBT has been communicated. SCT 404 and SGT 402 can interact with SIC 405 to facilitate and enable transaction request fulfillment. The PCBT is used by the transaction requestor to trigger compliance with the real-world products or services requested in the transaction request. SCT 404 and SGT 402 can interact with SIC 405 to facilitate and enable transaction request fulfillment.

A PCBT scan operation F is executed after operation E. In response to the execution of operation F, a decoded representation of the PCBT is generated in the SCT 404. After scanning and decoding the PCBT and in response to the SCBT that is being verified, a reception operation G, in the SGT 402, of a first compliance check (PVC) from the SCT 404 is executed. A first compliance action is normally also taken in response to the PCBT being verified. SGT 302, SCT 304, or both can use such verification to initiate subsequent internal operations, such as removing an offer from a given transaction if selectable by the requestor for the transaction.

After the PCBT scan. an operation H of communicating a second transaction barcode (SCBT) from SCT 404 to DCI 408 is executed. A SCBT scan operation I is executed after operation H. In response to the SCBT scan, a decoded representation of the SCBT is generated in the SCT 404. Following SCBT scanning and in response to SCBT verification, a receive operation J, at SGT 402, a second compliance check (SVC) from SCT 404 is executed. A second compliance action is normally also taken in response to the SCBT verification.

The first and second compliance checks illustrate an example of compliance checks. Said verifications of SCT 404 notify SGT 402 that the transaction has been initiated or completed. After the SCBT is scanned, a transaction completion message (MCT) communication operation K from SCT 402 to DCI 408 is executed.

Example 2

Movie theater

A transaction seeker uses her wireless PDA to purchase a ticket to a desired movie while on her way to the theater. To do this, he contacts the SGT using his wireless PDA. She then interacts with a Transaction Requestor User Interface (IUST) on her PDA to communicate movie information to, and receive movie information from, the SGT. The movie information includes typical information, such as the title of the movie and the projection time. The SGT interacts with the OCS to complete the transaction request. For example, the SGT can interact with the OCS to determine if there are seats left for the desired movie at the desired time. After the completion of the transaction request, her identity is authenticated in response to the password that she has entered.

After authenticating your identity, a PCBT is communicated to your PDA. Upon arriving at the cinema, she accesses the IUST to recover the PCBT.

Then he passes the PDA over a barcode reader located at the entrance to the cinema. In this way, the PCBT is optically scanned from your PDA screen. The PCBT scan activates a first turnstile that allows you to enter the cinema lobby. In some cases, you can also activate a ticket dispenser at the turnstile to dispense a physical ticket for the specified film. After scanning the PCBT, an SCBT is communicated to your PDA. Then she continues to the theater stalls. In order to enter the theater stalls, retrieve the SCBT. After recovering the SCBT, she passes the PDA over a barcode reader that is located at the entrance to the theater stalls. The SCBT scan activates a second turnstile that allows you to enter the theater stalls. After the SCBT is scanned, a transaction completion message is sent to your PDA. The transaction fulfillment message includes information such as where to get to the specific stalls where the film is being shown, interactive or exclusive information about the film, etc.

ES 2 249 461 T3

This example illustrates the convenience and time savings associated with using the methods and systems discussed here when going to the cinema to see a movie. In this example, the benefits associated with these methods and systems are even more powerful during peak theater hours.

Fig. 10 illustrates another embodiment of a flow chart of operation for the system illustrated in Fig. 7. In this embodiment verification of transaction barcodes, communication of transaction barcodes, and communication for determining the desired transaction are facilitated by the SCT 404. A reception operation A ", in the SGT 402, of a transaction request from the DCI 408 is executed. Upon receipt of the transaction request, an operation B "of communication of a request for a password from SGT 402 to DCI 408 is executed. The password request is intended to initiate an operation C "of reception, in SGT 402, of a password from DCI 408. An operation D" of communication of a requestor authentication message (MAS) from SGT 402 to DCI 408 initiates a transaction request communication operation E "from SGT 402 to SCT 404. MAS confirms that the password has been approved. In this incorporation, the transaction request is communicated to SCT 404 to allow the fulfillment of the transaction request by SCT 404. SCT 404 and SGT 402 can interact with SIC 405 to facilitate and allow the fulfillment of the request transaction.

A PCBT communication operation F "from SCT 404 to DCI 408 is executed after SCT 404 has received the transaction request. The PCBT is used by the transaction requestor to trigger compliance with the real-world products or services requested in the transaction request. A PCBT scan operation G "is executed after operation F". In response to the execution of operation G ", a decoded representation of the PCBT is generated in SCT 404 and a first compliance check operation is completed by SCT 404.

After the verification of the PCBT, a second transaction barcode (SCBT) communication operation H "from the SCT 404 to the DCI 408 is executed. A SCBT scan operation I "is executed after operation H". In response to the SCBT scan, a decoded representation of the SCBT is generated at SCT 404 and a second compliance check operation is completed by SCT 404. In response to the SCBT verification, a transaction completion message (MCT) communication operation J "from SCT 402 to DCI 408 is executed.

A multiphase transaction method that includes the communication of two transaction codes is discussed herein. It is contemplated and expected that the methods set forth herein may be implemented such that a one-phase transaction method or a three-phase or more multiphase transaction method is provided. For example, in some applications, it will be advantageous to use a one-stage transaction method in which only one transaction code, such as the first transaction code discussed herein, is communicated to the wireless communication device. It will be well understood that the number of transaction codes communicated to the wireless communication device depends on the specific application, rather than being definitive on the systems and methods discussed herein.

Commercial implementation of the methods and systems described herein can be accomplished in conjunction with one of many open or proprietary global specifications that allow users of wireless communication devices to easily access and interact with information and services through the communication systems. computer network described herein. An example of such an open global specification is the Wireless Application Protocol (WAP). WAP is designed to work with most wireless device architectures such as CDPD, CDMA, GSM, PDC, PHS, TDMA, FLEX, ReFLEX, iDEN, TETRA, DECT, DataTAC, Mobitex. Examples of wireless phones that allow WAP include the phone offered by Nokia as model number 7110, the phone offered by Siemens with model number S25, and the phone offered by Ericsson with model number R380. Examples of wireless PDAs that enable WAP are the PDAs offered by 3Com under the PalmPilot VII trade name and the PDA offered by Ericsson under the model number MC218.

WAP is a communication protocol and an application environment. WAP technology can be included in the operating system of most wireless communication devices, including PalmOS, EPOC, Windows CE, FLEXOS, OS / 9, JavaOS, etc. Provides interoperability of services even between different device families. Additional details on the WAP can be obtained from the Wireless Application Protocol Forum Ltd. (www. wapforum.org) and Dynamical Systems Research Ltd. (www.wap.net).

Symbian (www.symbian.com) offers a technology and hardware system under the trade name EPOC that provides a complete solution for manufacturers of wired communications devices. EPOC Release 5 includes Symbian's complete technology platform to deliver EPOC and other Symbian technologies at the core of the wireless industry. This includes technologies to support embedded Internet email, wireless text messaging, contact database and scheduling, standard Internet website browser, synchronization between PC-based and EPOC-based personal information and document formats, and a high-performance implementation of a wireless application language offered by Sun Microsystems under the Java trademark. EPOC provides robustness, compactness, and performance that are produced through careful system design in programming languages ​​including C ++.

ES 2 249 461 T3

WAP gateways are applications capable of allowing Internet content to be delivered to wireless communication devices. WAP accesses include accesses offered by Opensource, Ericsson, Apion, Mobileways, Nokia, Unwired Planet, and Edgemail.

Dynamical Systems Research offers the WAP Development Toolkit (WDT). WDT supports the development of WAP applications. WAP applications use Wireless Dialer Language (WML) and Wireless Dialer Language Script (WML Script). WML is used to create WAP pages in a similar way to how HTML is used to create web pages for the Internet. WML Script is a scripting language for creating and designing current page content.

Phone.com offers UP.SDK, a free software development kit accessible at www.phone. com / products / upsdk.html, which enables web developers to quickly and easily create HDML and WML information services and applications. UP.SDK includes a software development tool known as UP.Simulator that accurately simulates the behavior of a UP. Device with finder. The simulator can activate applications locally or connect to a UP.Link so that developers can test the full set of services that enable UP.Link. Phone.com also provides a publicly available UP.Link for free use by all developers to create complete applications without the need for an expensive carrier infrastructure or handset. The UP.SDK tools can work on both Windows 95 and Windows NT (Windows 95 and Windows NT are registered trademarks of Microsoft Corporation).

In the above detailed description, reference has been made to the accompanying drawings which form a part hereof, and in which specific embodiments to which the invention may be applied are shown by illustration. These embodiments, and certain variants thereof, have been described in sufficient detail to enable those of skill in the art to put the invention into practice. It is to be understood that other suitable incorporations can be used and that logical, mechanical, chemical and electrical changes can be made without departing from the scope of the invention. For example, the functional blocks shown in the figures could further be combined or divided in any way without departing from the scope of the invention. To avoid unnecessary detail, the description omits certain information known to those of skill in the art. The preceding detailed description is not intended, therefore, to be limited to the specific forms set forth herein, quite the contrary. It is intended to cover alternatives, modifications, and equivalents that may reasonably be included within the scope of the appended claims.