Patent Application
20050203854
The present invention relates generally to a method for initiating a transaction with a mobile communication device through an interaction with a printed media.
Mobile communication devices having digital camera capabilities are well known. One popular example of such a device is a cell phone equipped with a digital camera. Among other things, a cell phone user may spontaneously take a picture with the camera, and transmit the picture to another phone at a remote location.
In general, mobile phones are also recognized as opportunities for greater flexibility and spontaneity in business transactions. With a cell phone providing constant communications capabilities, a user can make a call from anywhere to initiate a business transaction at any time he or she has an impulse to do so.
The present invention advantageously combines the communications aspect of the cell phone with the camera-phone's digital imaging capabilities in a novel manner. This advantageous combination enables a user to spontaneously initiate a transaction with a business entity immediately upon viewing some printed material produced by the business entity. Numerous types of transactions can be enabled using the present invention.
The business entity first produces a printed medium indicating a transaction such as the sale of a product, or an offer for additional information. The printed medium includes a barcode that is embedded with direct contact data for communicating with the business entity. The barcode further includes specific transaction data relating to the transaction contemplated in the printed medium. The printed medium is then distributed for viewing by potential customers or users.
With the digital camera feature of a camera-phone, the user captures a digital image of the barcode. The camera-phone is programmed to decode the digital image to retrieve the direct contact data and the transaction data embedded in the barcode. The camera-phone then automatically initiates a communication with the business entity via the mobile communications device using the decoded direct contact data. Once communications are established, the camera phone transmits the transaction data derived from the barcode to further facilitate the transaction.
In one embodiment, the transaction data includes an identifier of a unique offer associated with the printed medium. Based on the identification of the offer, the business entity initiates the appropriate transaction routine for the communication. The unique offer transaction data may also include an identification of the particular medium from which the transaction data was retrieved. With this information, the business entity can track the source of its incoming communications for marketing analysis purposes.
In a preferred embodiment, the camera-phone further stores user information. Such user information can be transmitted by the camera phone to further facilitate the transaction. For example, a user's name, address, or account information can be stored in the phone's memory.
In the embodiment described above, the direct contact data is typically a phone number of the business entity, and the step of automatically contacting the business entity entails automatically dialing the decoded phone number derived from the barcode. Once contact is established, a human operator at the business entity may become part of the transaction, and the transaction may be carried out by voice communication. In one embodiment, the transaction is made more efficient by transmitting the stored user information from the camera phone to the business entity. As an alternative to a telephone transaction, a different embodiment may be used for World Wide Web transactions. In that embodiment, the direct contact information is a web address, and the communication device automatically contacts the web address after decoding the image of the barcode.
Once a transaction is started, the invention provides that an ongoing exchange of queries and responses may be used, depending on the nature of the transaction. Typically, the business entity will present a list of options, and the cell phone user can respond by transmitting an option selection.
In a preferred embodiment, prior to engaging in the transaction, the identity of the business entity is authenticated with a digital signature associated with the transaction. In a first arrangement, the digital signature may be included in the barcode and the step of decoding the digital image taken by the camera-phone includes decoding the digital signature. Authentication of the digital signature occurs prior to initiating the communication. Alternatively, the digital signature may not be in the barcode, but rather it may be transmitted to the mobile communications device from the business entity after initiation of the communication.
Preferably, the digital signature is generated using a private key and the step of authenticating the digital signature includes using a corresponding public key stored in the mobile communications device to verify the digital signature. If a valid digital signature is not authenticated then a warning may be provided, and the transaction may optionally be blocked. To facilitate tracking of potentially fraudulent activity, the authentication failure and corresponding data can be reported to a central authority.
The invention described provides a method for executing business or personal transactions by using existing and available technology in a novel manner. The preferred method allows an individual to use a cell phone equipped with an integrated camera and associated software to initiate a business transaction. As depicted in
In the preferred embodiment, the decoded bar code 13 includes a phone number to be dialed, and additional information pertaining to the transaction. Once the picture of the bar code 13 has been taken and the information decoded, the cell phone 15 automatically dials the embedded telephone number (step 17) contacting business organization 21. Once communication is established, the cell phone 15 transmits the additional information to the receiving organization 21. In addition to this information, supplemental information about the owner 16 of the cell phone 15, including but not limited to name, address, or cell phone number, may also be transmitted. Such supplemental information is gathered from data stored in the cell phone 15. This supplemental information allows the receiver to identify the caller and aids in completing the transaction.
At step 18, the business organization 21 can transmit information or queries back to the cell phone 15, and the user 16 may provide additional information, such as picking an option, or giving payment or confirmation instructions. In the depicted embodiment, in step 19, the business organization 21 fulfills the transaction by having goods shipped to the customer 16 by a delivery service 20.
In the preferred embodiment, the invention utilizes a software module included in the software suite supplied with cell phone 15. Other exemplary software applications in the suite may include conventional voice-mail, text messaging, web access, etc. The software supporting the present invention has the capability of decoding a bar code. The software may include, but is not limited to, the capability to decode one or two dimensional bar codes such as Maxicode, Aztec, etc.
As mentioned above, a telephone number is preferably encoded in the barcode along with other information. Such other information may include, but is not limited to a product number, special offer code, or some other identifier. Other information may be provided depending on the needs of the creator of the barcode. Such information is preferably used to assist in fulfilling the contemplated transaction.
The software module for use with the present invention may utilize the following steps. A first step is decoding the bar code for its embedded information. If the picture is not of sufficient quality, the user may be prompted. If the information from the bar code is decoded correctly, the phone is automatically dialed to the number embedded in the bar code. Next, once the connection is made, the remaining information contained in the bar code is transmitted. The receiving organization then processes the request. Such request may include a buying transaction, fulfillment transaction, an information query transaction, etc. The receiving organization may then send a message or series of messages back to the phone for the holder of the cell phone to interact directly for such things as, but not limited to, paying options (credit card information, etc.), color of item, or other product and service choices. Alternatively, a live call center operator may come on the line to carry out the transaction with the caller, using the information already gathered.
In the preferred embodiment the bar code 13 will include both a unique code to identify the organization 21 and the telephone number to call. Additional information in the bar code 13 may include a unique identifier of the item or offer, product or service parameters unique to the offer, a code identifying the source of the bar code 13 (for example if the offer is made in more than one publication).
A number of other embodiments and applications utilizing features of the basic invention are described in flow diagrams in
In
Preferably, the publishing entity processes the information and sends back a message to confirm the transaction is valid and has started. Through a series of messages between the cell phone and the fulfillment entity, messages, options, and menus of options may be displayed on the cell phone for the customer to answer. The types of information asked for could include but is not limited to type of document. The customer interacts with these questions/menus, and the answers are communicated back to the fulfillment entity.
The method of payment may be addressed by several methods. The first method will handle payment through queries displayed on the cell phone. This may involve the customer entering in a valid charge card number and related information. This information is then verified by the fulfillment entity in direct communications with the charge-card company or bank. The second method requires that the customer has previously set up a payment scheme with the telecommunications operator. In this scheme, the fulfillment entity defers to the telecommunications operator to manage the payment. The telecommunications operator may handle the payment within its organization or initiate a transaction on a pre-determined charge or bank number. Upon completion of all questions required to complete the transaction, the purchased publication is downloaded to the cell phone, and the cell phone is disconnected. The fulfillment agency then enters the transaction into its database for billing. These payment options are applicable to any of the transactions described in this application.
The game entity then processes the information and sends back a message or series of messages according to the game play (steps 510-515). Once the game turn is over, a confirmation message is sent to the cell phone, which is then disconnected (step 516).
The lottery organization then processes the information and sends back a message or series of messages according to the game play (steps 709-713). Once the game turn is over, a confirmation message is sent to the cell phone. This information can include but is not limited to where winnings can be claimed. The cell phone is then disconnected (step 714). This method allows interactive games to be played based on time or the number of active participants.
The movie fulfillment entity then processes the information and sends back a question if the customer wants a limited clip of the specified movie or to buy the movie (steps 815-817). If the customer wants a limited time clip, it is sent back to the customer and the phone disconnects (steps 818-820). If the customer wants the entire movie, it is sent and the transaction is entered into the receivables system of the movie fulfillment entity (steps 821-823). Movie offers can be printed on soda cups or cans, French fry containers, tickets, etc.
Similar to
The fulfillment entity then processes the information and sends back a message to confirm the transaction is valid and has started (steps 1110, 1111). The cell phone asks for the account number (and possibly password) of the customer, and this information is sent to the fulfillment entity (steps 1112-1115). The fulfillment entity then completes the transaction by entering the data into its order system, a confirmation message is sent to the cell phone, and the cell phone is disconnected (steps 1116-1118).
The fulfillment entity then processes the information and sends back a message to confirm the transaction is valid and has started (step 1216). Through a series of messages between the cell phone and the fulfillment entity, messages, options, and menus of options are displayed on the cell phone for the customer to answer (steps 1217-1221, 1225-1227). The types of information asked for could include but is not limited to color, size, shipment options etc. The customer interacts with these questions or menus, and the answers are communicated back to the fulfillment entity.
The method of payment may be addressed by several methods. The first method (steps 1221-1224) will simply look like another question displayed on the cell phone. This may involve the customer entering in a valid charge card number and related information. This information is then verified by the fulfillment entity in direct communications with the charge-card company or bank.
The second method (steps 1228-1230) requires that the customer has previously set up a payment scheme with the telecommunications operator. In this scheme, the fulfillment entity defers to the telecommunications operator to manage the payment. The telecommunications operator may handle the payment within its organization or initiate a transaction on a pre-determined charge or bank number.
Upon completion of all questions required to complete the transaction, the cell phone notifies the customer that the transaction has been completed, and breaks the connection with the fulfillment entity. The fulfillment agency then enters the transaction into its database for normal fulfillment of the order including shipment (steps 1230-1235).
The receiving entity then processes the information and sends back a message to confirm the transaction has started (step 1408, 1409). Through an optional series of messages between the cell phone and the receiving entity, messages, options, and menus of options are displayed on the cell phone for the user to answer (steps 1413-1417). The information asked for is dependent upon the type of entity using the technology. The individual interacts with these questions/menus, and the answers are communicated back to the receiving entity. When the questions are complete, the cell phone hangs up and the transaction is complete (step 1412).
The receiving entity then processes the information and sends back a message to confirm the transaction has started (step 1511). If the call center is automated, an optional series of messages is exchanged between the cell phone and a call center of the receiving entity. Messages, options, and menus of options are displayed on the cell phone for the user to answer (step 1512). A live customer service representative may typically be involved in taking the payment information, and completes the payment transaction with the customer in conventional fashion.
In a further embodiment depicted in
In an enhanced embodiment, the consumer maybe provided incentives to participate in the survey. Since the participant may be identified by his or her cell phone account, the phone provider may participate in providing incentive rewards. For example, as a reward for participating, the consumer's cell phone account may be credited with free minutes, redeemable points, or discounts.
Data Format
The following listing describes a preferred embodiment of the contents and format of the data encoded within the printed 2D symbol for use with the present invention. Alternative formats might include UPC symbols, USPS IBI or delivery confirmation codes, depending on the actions that are to be performed in accordance with one of the applications described above.
The following describes a preferred embodiment of the packet protocol to be used to communicated between the cell phone 15 and the business organization 21:
Start of Message Token
This value is always 0xAA and marks the beginning of a new message
Sequence Number
This value is a sequence number, starting at 0x00 and incrementing by 1 for each subsequent message, rolling over to 0x00 after the value 0xFF. This is used to insure message level integrity, especially important when the desired payload is larger than the maximum payload allowed by a single message.
Payload Type
This value defines the type of payload carried by this message. In addition, the payload type defines the total length of the payload, and thus the total length of the message.
Payload
Dependant upon payload type
CRC16
Cyclical Redundancy Check value (16 bit)
End of Message Token
This value is always 0x55 and marks the end of the message
Initial Message
The first message sent from the cell phone 15 to the organization 21 (Payload
Protocol for Menus-On-The-Fly
In order to query the cell-phone 15 for items such as product options (color, size etc), shipping, billing options, and other required information, this protocol within the message structure allows the fulfilling entity (business organization 21) to build a text or graphic menu to be displayed on the cell phone display. Upon sending the required information to the cell phone 15, the cell phone software is then responsible for displaying the menu (which could be a simple one text line (and/or graphic) display, capturing the resultant user 16 response, and sending the response back to the fulfilling vendor 21.
Within the payload data are embedded commands for formatting and displaying the menu item(s), as well as the data (text and/or graphical) to support the query. These embedded commands control defined functionality implemented on the cell phone 15. Because the capability of each cell phone depends upon the manufacturer and features selected by the user, it is known in the art that this finite set of functions with fixed API's may implement the commands differently for each type of phone while still performing the basic task defined by the protocol.
Payment Method
In many of the embodiments depicted in
Security Features
In the preferred embodiments, security features are incorporated into the invention. A first optional security feature allows use of the camera phone for initiating transactions to be restricted without entry of a proper PIN or password. When a transaction is initiated by scanning a barcode with a camera phone, the user is required to enter a PIN on the camera-phone before being allowed to proceed.
In an alternative embodiment, different types of transactions may have different security levels. PIN or password requirements are preferably stored in the camera phone. The security levels may be triggered by information about the nature of transaction, as identified by information embedded in the bar code. For example, toll calls might require PIN entry, while toll-free will not. In another example, calls where money is being transacted may require a PIN, while informational calls may not.
PINs and passwords can prevent unauthorized transactions if the phone is stolen. Also if the phone is given to a child the use of PINs and passwords can allow a parent to control the types of transactions that are allowed. The PIN and password functionality is programmed directly into the camera cell phone, and the need for a proper PIN will be triggered based on information decoded from the barcode, or from information transmitted to the cell phone from the business entity.
Another preferred security feature uses digital signatures to verify that the entity who produces the printed material is the entity that it claims to be. Consumers may be hesitant in using their camera phones to initiate automatic transactions out of concern that the bar-codes may be counterfeit or misrepresenting the identity of the author. An exemplary authentication procedure is depicted in the flow diagram of
In this exemplary embodiment, a trusted third party (TTP) will verify the identity of the entity publishing the bar code. At step 1700 the entity (for example an advertiser) submits data to be included in the bar-code to the TTP. The TTP can verify the identity of the entity and/or the content. (Step 1701). For example, the TTP can verify that a phone number is correct and valid for the entity. At step 1702, the TTP then uses a private key to provide a digital signature to be included in the bar code. The bar code with the digital signature is then printed on the document which is to be presented to potential customers.
Camera phones for use with the present invention include a public encryption key provided by the TTP. This public key corresponds to the private key used to generate the digital signature. Thus, by systematically using the TTP to maintain control over the public and private encryption keys, the entity creating the bar code can be identified and held accountable. At step 1704, the digital signature is verified by the camera phone using the public key. The camera phone then ascertains the bar code content is authentic based on whether verification of the digital signature (1705) was successful.
The user may be informed by a message whether the bar code was authenticated (1706-1707). In a preferred embodiment, the cell phone may be programmed with a preference to disallow any transactions from proceeding, unless an authenticated signature is found (1707). Since information in the bar codes may become outdated, date information may be included in the bar code, and a warning may be produced if the information is older than a predetermined expiration period. Transactions may also be blocked for expired bar codes.
An alternative to the digital signature scheme described above could be for a certificate to be downloaded during the transaction. The certificate includes a vendor key and a TTP signature authenticating that the vendor key is from an authentic source. These and other techniques for authenticating the source of a message are well known in the encryption arts.
In a further embodiment, if a non-authentic or otherwise suspicious bar code is detected, the camera phone can automatically, or upon user command, store and upload information about a suspicious bar code to a central repository for further action and analysis (1708). Preferably, the TTP could access the information about bad bar codes in order to make future determinations about bar code verification.
In a particular application of the digital signature security as described above, a consumer can verify the source of quality or rating information printed on a product package or an advertisement (for example, as shown in
A trusted third party (TTP) verifies the identity of the entity publishing the bar code. The TTP may also verify bar code content, such as the product and its rating information. The TTP then uses a private key to provide a digital signature to be included in the bar code. Camera phones are manufactured to include the corresponding public key. The digital signature is read by the camera phone using the public key. The ability of the camera phone to read the digital signature verifies the authenticity of the code.
An alternative authentication technique would require the cell-phone to dial a phone number included in the bar code. This phone number could be a direct contact number for the rating agency. Once communication is established, a certificate can be downloaded to the cell phone. The certificate includes a vendor key and a TTP signature authenticating that the rating agency key is from an authentic source. The rating agency key could then be used to authenticate rating information generated by the rating agency.
Exemplary Software
The following exemplary software code demonstrates the operation of the present invention. This provided exemplary code is in Visual Basic programming language, but any suitable programming language may be used, and it is to be understood that the software may be organized in many different ways without departing from the invention.
The following exemplary files are presented below: Form1.form, Form2.form, Project1.vbp, and Project1.vbw. These files are used to generate an executable file called CellPhoneConnector.exe that will operate on a camera phone device to interpret scanned data, provide a user interface, and to open a line of communication, and to initiate a transaction. It will be understood that certain other routine files are not presented below but would be easily understood and implemented by those skilled in the art.
For this exemplary embodiment, the software is capable of interpreting the bar-code information to determine whether communication will be by telephone or web. The software then dials the phone number, or contacts the appropriate web address, as the case may be, to initiate the transaction.
The Form1 and Form2 files describe the screen interfaces, the communication means, and the logic for interpreting the bar-codes and initiating transactions. The Project1 files bring together the Form1, Form2, and other necessary files containing information to allow the appropriate executable (CellPhoneConnector.exe) to be compiled.
These exemplary software files are as follows:
This application claims priority of provisional U.S. Patent Application 60/563,211, filed Apr. 16, 2004, and having the same title. That provisional application is hereby incorporated by reference in its entirety. This application is also a continuation-in-part of U.S. patent application Ser. No. 11/064409, filed Feb. 23, 2005, having the same title, which in turn claims priority from U.S. Provisional Application 60/546,765, filed Feb. 23, 2004.
| Number | Date | Country | |
|---|---|---|---|
| 60563211 | Apr 2004 | US | |
| 60546765 | Feb 2004 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11064409 | Feb 2005 | US |
| Child | 11107004 | Apr 2005 | US |
