Abstract:
Individuals asked to present two forms of picture identification face a problem as individuals usually only have one form of picture ID, that form of identification generally being a state-issued driver&#39;s license. The disclosed invention is a system and method for a party, generally a Customer or Patron, to establish proof of identification to another party, generally a Merchant or Agent, via a mobile phone using the mobile communications networks. The invention thereby provides the Merchant or Agent with an additional capability to verify the identity of Customers, including verification of the date of birth of the Customer. In a preferred embodiment, the invention uses the Short Message Service (“SMS”) and Multimedia Messaging Service (“MMS”) features available on mobile phones, or other wireless communication devices, to establish the identity of a Customer after communicating a request for such identification to a government administered identification database system.

Description:
CROSS REFERENCE TO RELATED APPLICATIONS  
       [0001]     This nonprovisional patent application claims the benefit of the filing date of provisional application 60/682,943, filed May 20, 2005, which is herein incorporated by reference. 
     
    
     STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH AND DEVELOPMENT  
       [0002]     No Federally sponsored research or development was requested for, accepted, or used in the development related to the invention herein claimed.  
       BACKGROUND OF THE INVENTION  
       [0003]     Individuals asked to present two forms of picture identification sometimes face a problem since the individual may only have one form of picture ID, that form of identification generally being a driver&#39;s license. Many individuals may own a passport but fail to have the passport on their person if they are challenged for two forms of picture ID at a domestic location. Although some individuals have credit cards embossed with a photograph, it is possible that a significant portion of consumers may lack either a passport or an additional form of picture ID.  
         [0004]     Some state agencies, such as state Departments of Transportation (“DOTs”), use electronic methods of issuing forms of state identification, such as driver&#39;s licenses. State approved photo centers for issuing such forms of identification are equipped to take a digital photograph of the subject, insert the photo into a digital identification card or driver&#39;s license (which may be a scan of a temporary driver&#39;s card), and then print the finalized identification or license. The photo centers may be networked into a state agency or DOT computer system so that information can be shared among the various photo centers. As an example, some photo centers may be able to issue duplicate driver&#39;s licenses by retrieving a digital version of the license (including the picture of the subject/licensee) from the DOT network and printing the license. The photographs of the subjects/licensees are stored on the network in the form of a digital file.  
         [0005]     The general availability of two forms of picture identification may also help to reduce the effects of identification fraud. Identification fraud is a concern of state governments in that false identification may be used to purchase alcohol, tobacco or firearms. The procurement of false identification may take two forms: (1) fraudulently obtaining a birth certificate, which is then used to obtain a false driver&#39;s license or other form of identification from a state agency or DOT; or (2) obtaining a false form of identification, such as a driver&#39;s license, from a forger. A simple system allowing merchants or agents to verify the identity of customers or patrons presenting questionable forms of identification could be used to reduce the use of false identification to purchase goods such as alcohol, tobacco or firearms.  
       BRIEF SUMMARY OF THE INVENTION  
       [0006]     The claimed invention is a system and method for a party, generally a Customer or Patron, to establish proof of identification to another party, generally a Merchant or Agent, via a mobile phone using the mobile communications networks, thereby allowing the Merchant or Agent to verify the identity of Customers or Patrons who either have no identification or who present forms of identification of questionable authenticity. The proposed system and method allows Merchants or Agents to verify from the proper state agency (such as a DOT) that the Customer or Patron presenting the identification is indeed the person depicted on the identification, and that he/she was indeed born on the date listed on any presented identification.  
         [0007]     The system embodying the disclosed method may take the form of using various electronic devices to facilitate electronic communications between the Customer and the Merchant. In a preferred embodiment, the Short Message Service (“SMS”) and Multimedia Messaging Service (“MMS”) features available on mobile or cellular phones, or other forms of wireless communication, are used to establish the identity of a Customer after communicating a request for such identification to a government administered identification database system. 
     
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0008]      FIG. 1  depicts the invention being used in a manner in which the Customer or Patron initiates the identification query after being challenged by the Merchant or Agent.  FIG. 2  depicts the invention being used in a manner in which the Merchant or Agent initiates the identification query after challenging the Customer or Patron.  FIG. 3  depicts a variant of  FIG. 1  in which the claimed invention is operated directly by a government agency.  FIG. 4  depicts a variant of  FIG. 2  in which the claimed invention is operated directly by a government agency.  FIG. 5  depicts a variant of  FIG. 1  in which the claimed invention is operated solely by a trusted third party.  FIG. 6  depicts a variant of  FIG. 2  in which the claimed invention is operated solely by a trusted third party.  
     
    
     DETAILED DESCRIPTION OF THE INVENTION  
       [0009]     The system (“System”) implementing the disclosed method of the invention comprises a plurality of computers, including web servers and database servers, routers, electronic communications devices, and software programs designed to implement the methods and processes described below. The System will also include a database of registered users (the “System User Database”) who have registered on the System so that they may use the invention. The System may be scalable to meet the operating entity&#39;s needs as required. A person skilled in the arts of computer technology may make the System using typical “off-the-shelf” components including routers, servers and electronic components available from any of a number of computer hardware manufacturers. A person skilled in the arts of information technology, including database administration and Internet and other communications protocols, may develop software programs implementing the methods and processes claimed herein from any number of computer languages, such as Perl or PHP, running on any number of computer operating systems, such as Linux. Such software programs will embody the processes described herein and operate on the System.  
         [0010]     There are two options for the administration of the System: it may be administered by a Trusted Third Party (“TTP”) entity, or it may be administered by a government agency, such as a DOT. In the former embodiment, the TTP has reached an agreement or contract with the government entity which administers a state-approved or state-managed identification database system, such as a DOT. Privacy concerns and electronic security concerns may dictate which option may be chosen for states which choose to implement the system and method.  
         [0011]     The embodiments in which the System is operated by a TTP are presented in  FIGS. 1, 2 ,  5  and  6 . A preferred embodiment of the invention is that depicted in  FIG. 1 . The alternatives in which the System is operated by a government entity, such as the DOT itself, are displayed in  FIGS. 3 and 4 . In another embodiment of the invention, the TTP may itself accept photographs of users uploaded to the TTP&#39;s computer systems by users whose identity has been verified by the TTP in some manner.  FIGS. 5 and 6  present two variants of this embodiment.  
         [0012]      FIG. 1  presents the first embodiment of the invention in which the query for the Customer&#39;s identification is submitted by the Customer.  
         [0013]     For this description of the process and method described in  FIG. 1 , a TTP shall administer and operate the System. The TTP will interface its System with an identification database system (“ID Database System”) operated by the appropriate government agency, such as a Department of Transportation. The ID Database System stores the digital pictures of the state&#39;s licensed drivers, which were taken at the state&#39;s photo identification centers, and also stores other relevant information, such as the licensees&#39; dates of birth (“DOB”), the licensees&#39; names, addresses, etc. This data may be stored in the ID Database System under a primary key equal to the driver number or license number which appears on driver&#39;s licenses.  
         [0014]     Note that in another implementation of the claimed invention the government entity itself may administer the System, integrating it with the ID Database System. This embodiment of the Invention is described below and presented in two variants in  FIGS. 3 and 4 .  
         [0015]     It shall be a requirement that Customers who wish to use the claimed invention as a form of ID verification set up accounts in the System User Database via the Internet or some other form of electronic communication. The Customers will need to provide the System User Database with the phone numbers of their mobile phones; in the alternative, when accessing their accounts on the System, the Customers may create a user identification name (“User ID”) to be associated with their personally identifiable information, including the phone number of their mobile phones. The Customers will also need to provide other information to the System User Database, such as their driver license number or identification number on their state-issued ID card. By submitting this information, the System now has a set of data which it can use to cross-check against the driver&#39;s data on the ID Database System.  
         [0016]     The System may also be configured so that Merchants who desire to use the system must also create accounts in the System User Database prior to using it in order to reduce the likelihood of fraud or abuse of the System by nonregistered parties.  
         [0017]     In Step  1  of  FIG. 1 , a Customer approaches a Merchant and attempts to purchase goods such as alcohol or cigarettes, or attempts entry into an establishment restricted by age, such as an alcohol-serving business or a casino. The Customer has set up an account on the System and has on their person a mobile phone capable of communicating with the System, such as by sending SMS messages (although other forms of electronic communication, such as a phone call to an automated phone line or email, are possible). When the Customer attempts to purchase the good or obtain entry, the Merchant will challenge the Customer to produce identification. If the Customer either (1) does not have their driver license, or (2) presents their license, which the Merchant does not believe to be valid, the Merchant will then challenge the Customer to produce further identification verifying their age and identity.  
         [0018]     In Step  2  of  FIG. 1 , the Merchant has on their person a mobile phone capable of receiving MMS messages. The Merchant will then give their mobile phone number or his/her User ID to the Customer. The Merchant&#39;s User ID must be created by the Merchant during an account set-up procedure on the System; the invention, however, may still be configured to operate even if the Merchant has not created an account on the System.  
         [0019]     In Step  3  of  FIG. 1 , the Customer will then send a SMS message (the “SMS Request Message”) addressed to the System by way of a cellular carrier, requesting that the System remit the Customer&#39;s identification to the mobile phone owned by the Merchant (the SMS Request Message may also take other forms of electronic communication, such as a phone call to an automated phone line or email). The SMS Request Message will include the Merchant&#39;s mobile phone number or the Merchant&#39;s User ID and may take a form such as “Show ID to Merchant 123 ” or “Show ID to 215-555-1234.” The TTP may also choose to have such requests delivered to a specially identified SMS short code address, email address, or phone number for “branding” purposes.  
         [0020]     In Step  4  of  FIG. 1 , the SMS Request Message (or other form of electronic communication) is delivered to the System operated by the Cellular Carrier.  
         [0021]     In Step  5  of  FIG. 1 , the System checks the identity of the mobile phone sending the SMS Request Message against the System User Database to match the phone number of the sending mobile phone with the phone number associated with the account created by the Customer. The System extracts the Merchant&#39;s mobile phone number or User ID from the SMS Request message; if the Merchant&#39;s User ID has been submitted, the System will obtain the Merchant&#39;s mobile phone number by checking the User ID against the User IDs in the System User Database, thereupon obtaining the mobile phone number associated with the User ID (the Merchant&#39;s use of a User ID would require the Merchant to have registered an account on the System). The System then sends an SMS to the Merchant&#39;s mobile phone asking the Merchant to verify that it wants to identify the Customer (the “Merchant SMS Verification Message”). The Merchant SMS Verification Message is delivered from the System to a Carrier, thereupon to the Merchant. The System may optionally send an SMS to Customer, asking the Customer to confirm that he/she wishes to remit his/her identification to the Merchant (the “Customer SMS Verification Message”). The System may optionally be configured to accept requests from registered Merchants only; should the System fail to locate the Merchant&#39;s mobile number or User ID in the System User Database, the System will terminate the procedure, and remit failure notices to the Merchant and Customer akin to the failure notice of Step  5 A.  
         [0022]     The Merchant SMS Verification Message may take the form “Receive ID Verification?” with an optional alphanumeric personal identification number (“PIN”) included in the Merchant SMS Verification Message. If the Merchant has registered with the System, it has already created a PIN on the System. After receiving the SMS Request Message and extracting the Merchant&#39;s mobile phone number (or obtaining the mobile phone number after checking the submitted User ID against the User IDs in the System User Database), the System will retrieve the Merchant&#39;s PIN from the System User Database and append the PIN to the Merchant SMS Verification Message. This process allows the Merchant to verify that the Merchant SMS Verification Message is authentic and has indeed been sent by the System because only the Merchant and the System will know the PIN created by the Merchant during his/her account set-up. Likewise, the Customer SMS Verification Message may take the form of “Remit your ID to Merchant 123 ?” with the Customer&#39;s PIN (again, created by the Customer when he/she created an account on the System) appended to the Customer Verification Message so that the Customer can verify the authenticity of the Customer Verification Message.  
         [0023]     In Step  5 A of  FIG. 1 , if the System cannot match the phone number of the mobile phone sending the SMS Request Message against the phone numbers in the System User Database, the System sends an SMS to the Merchant&#39;s mobile phone notifying the Merchant that it cannot confirm the ID of the Customer (the “SMS Denial Message”). The SMS Denial Message is delivered from the System to a Carrier, thereupon to the Merchant. The process ends and the Merchant may refuse service to the Customer.  
         [0024]     In Step  6  of  FIG. 1 , the Merchant, after verifying the optional PIN in the Merchant SMS Verification Message is correct, will then reply to the Merchant SMS Verification Message with an SMS message to the System, affirming the desire to receive the ID verification MMS message (the “Merchant SMS Affirmation Message”). The Merchant SMS Verification Message is routed through a Carrier and delivered to the System. The Customer will also reply to the Customer SMS Verification Message with an SMS message affirming his/her desire to have his/her ID submitted to the Merchant (the “Customer SMS Affirmation Message”). The System must receive both the Merchant SMS Affirmation Message and the Customer SMS Affirmation Message before the process may continue. If the System fails to receive both SMS Affirmation Messages (or only the Merchant SMS Affirmation Message if the Customer SMS Confirmation Message step has been omitted), then the System halts the process.  
         [0025]     Note that, in some forms of the first embodiment, the SMS Verification Messages and SMS Affirmation Messages of Steps  5  and  6  may be eliminated if a lesser degree of security, but a higher degree of ease of use, is desired.  
         [0026]     In Step  7  of  FIG. 1 , if the System, as described in Step  5 , has verified the identity of the mobile phone sending the SMS Request Message against the System User Database and successfully matched the User ID or phone number with the account created by the Customer, then the System submits an ID request (“ID Request”) for Customer&#39;s identification to the ID Database System administered by the government agency. The ID Request may take the form of sending the Customer&#39;s driver license number, which was submitted to the System upon Customer&#39;s registration with the System.  
         [0027]     In Step  8  of  FIG. 1 , after receiving the ID Request, the ID Database System queries its data records for the Customer&#39;s identification data and retrieves a digital image of Customer, and optionally other data such as a date of birth (“DOB”) and the Customer&#39;s name. The ID Database System then submits the digital image, DOB and any other data to the System via an electronic message (“ID Data Reply”).  
         [0028]     In Step  8 A of  FIG. 1 , if the ID Database System, after receiving the ID Request, cannot match the data submitted in the ID Request (such as the Customer&#39;s driver license number) to its stored data, the ID Database System sends a message to the System indicating the failure to achieve a match (“ID Failure Message”).  
         [0029]     In Step  9  of  FIG. 1 , the System receives the ID Data Reply which was sent as described in Step  8 . The System then composes an MMS message including the digital image and the DOB of Customer and any other optional data included in the ID Data Reply. The System can also include in the MMS message a warning if the Customer is below the age of eighteen or twenty-one. The System then addresses the MMS message to the Merchant&#39;s mobile phone and delivers the MMS message to the Cellular Carrier.  
         [0030]     In Step  9 A of  FIG. 1 , if the System receives an ID Failure Message, the System sends an SMS notifying the Merchant that it cannot confirm the ID of the Customer (“SMS Denial Message”). The SMS Denial Message is delivered from the System to a Carrier, thereupon to the Merchant. The process ends and the Merchant may refuse service to the Customer.  
         [0031]     In Step  10  of  FIG. 1 , the Cellular Carrier delivers the MMS message from Step  9  to Merchant&#39;s mobile phone. Merchant can now view the digital image of the customer, and the optional DOB (and other optional data) on the mobile phone.  
         [0032]     In Step  11  of  FIG. 1 , after viewing the MMS message, Merchant can confirm the identity and the age of Customer. If the identity of the Customer has been confirmed, the Merchant may sell the goods to the Customer, deliver services to the Customer, allow the Customer into Merchant&#39;s restricted premises, etc.  
         [0033]      FIG. 2  presents the second embodiment of the invention in which the query for the Customer&#39;s identification is made by the Merchant.  
         [0034]     In the second embodiment presented in  FIG. 2 , a TTP shall administer and operate the System. The System, however, may be administered by a government agency and integrated with the ID Database System; this alternate embodiment of the claimed invention is presented in  FIG. 4 .  
         [0035]     Step  1  of the second embodiment is equivalent to Step  1  of the first embodiment, above.  
         [0036]     In Step  2  of the second embodiment, instead of the Merchant giving its mobile phone number or email address to the Customer, the Customer gives its mobile phone number or User ID (as created by the Customer during his/her account set-up procedure on the System) to the Merchant.  
         [0037]     In Step  3  of the second embodiment, the Merchant will then send a SMS message (“SMS Request Message”) addressed to the System by way of a cellular carrier, requesting that the System remit the Customer&#39;s identification to the mobile phone owned by the Merchant (the SMS Request Message may also take other forms of electronic communication, such as a phone call to an automated phone line or email). The SMS Request Message will contain the Customer&#39;s mobile phone number or User ID and may take a form such as “Request ID for AnyUser 123 ” or “Request ID for 215-555-1234.” The System may also choose to have such requests delivered to a specially identified SMS short code address, email address, or phone number for “branding” purposes.  
         [0038]     Step  4  of the second embodiment is equivalent to Step  4  of the first embodiment, above.  
         [0039]     In Step  5  of the second embodiment, the System may optionally check the Merchant&#39;s mobile phone number against the mobile phone numbers of registered users in the System User Database and refuse the identification request if the Merchant is not registered. The System then extracts the Customer&#39;s mobile phone number or User ID from the SMS Request message and checks for a match in the System User Database. If the Customer&#39;s User ID has been submitted, the System will obtain the Customer&#39;s mobile phone number by checking the Customer&#39;s User ID against the User IDs in the System User Database, thereupon obtaining the mobile phone number associated with the User ID.  
         [0040]     The System then sends an SMS to the Customer&#39;s mobile phone asking the Customer to verify that he/she wants to identify himself/herself to the Merchant (the “Customer SMS Verification Message”). The Customer SMS Verification Message is delivered from the System to a Carrier, thereupon to the Customer. The System may optionally send an SMS to the Merchant, asking the Merchant to confirm that he/she wishes to identify the Customer (the “Merchant SMS Verification Message”). The System may optionally be configured to accept requests from registered Merchants only; should the System fail to locate the Merchant&#39;s mobile number or User ID in the System User Database, the System will terminate the procedure, and remit failure notices to the Merchant and Customer akin to the failure notice of Step  5 A.  
         [0041]     The Customer SMS Verification Message may take the form “Deliver your ID to Merchant 123 ?” with an optional alphanumeric personal identification number (“PIN”) included in the Customer SMS Verification Message. As the Customer has registered with the System, he/she has already created a PIN on the System. After receiving the SMS Request Message and extracting the Customer&#39;s mobile phone number (or obtaining the mobile phone number after checking the submitted User ID against the User IDs in the System User Database), the System will retrieve the Customer&#39;s PIN from the System User Database and append the PIN to the Customer SMS Verification Message. This process allows the Customer to verify that the Customer SMS Verification Message is authentic and has indeed been sent by the System because only the Customer and the System will know the PIN created by the Customer during his/her account set-up. Likewise, the Merchant SMS Verification Message may take the form of “Receive ID from AnyUser 123 ?” with the Merchant&#39;s PIN (again, created by the Merchant during the account set-up on on the System) appended to the Merchant SMS Verification Message so that the Merchant can verify the authenticity of the Merchant SMS Verification Message.  
         [0042]     In Step  5 A of the second embodiment, if the System cannot locate either the Customer&#39;s ID or the Customer&#39;s mobile phone number in the System User Database, it remits a failure notification to the Merchant indicating that that it cannot confirm the identity of the Customer (the “SMS Denial Message”). The SMS Denial Message is delivered from the System to a Carrier, thereupon to the Merchant. The process ends and the Merchant may refuse service to the Customer  
         [0043]     In Step  6  of the second embodiment, the Customer, after verifying the optional PIN in the Customer SMS Verification Message is correct, will then reply to the Customer SMS Verification Message with an SMS message to the System, manifesting his/her assent to the System remitting his/her identification to the Merchant (the “Customer SMS Affirmation Message”). The Customer SMS Verification Message is routed through a Carrier and delivered to the System. The Merchant will also reply to the Merchant SMS Verification Message with an SMS message affirming its desire to receive the Customer&#39;s identification (the “Merchant SMS Affirmation Message”). The System must receive both the Merchant SMS Affirmation Message and the Customer SMS Affirmation Message before the process may continue. If the System fails to receive both SMS Affirmation Messages (or only the Customer SMS Affirmation Message if the Merchant SMS Confirmation Message step has been omitted), then the System halts the process.  
         [0044]     Note that, in some forms of the second embodiment, the SMS Verification Messages and SMS Affirmation Messages of Steps  5  and  6  may be eliminated if a lesser degree of security, but a higher degree of ease of use, is desired.  
         [0045]     In Step  7  of the second embodiment, if the System, has optionally verified the identity of the Merchant&#39;s mobile phone (which sent the SMS Request Message) against the System User Database and successfully matched the Customer&#39;s User ID or phone number with the account created by the Customer, then the System submits an ID request (“ID Request”) for Customer&#39;s identification to the ID Database System administered by the government agency. The ID Request may take the form of sending the Customer&#39;s driver license number, which was submitted to the System upon Customer&#39;s registration with the System.  
         [0046]     Step  8  of the second embodiment is equivalent to Step  8  of the first embodiment, above.  
         [0047]     Step  8 A of the second embodiment is equivalent to Step  8 A of the first embodiment, above.  
         [0048]     Step  9  of the second embodiment is equivalent to Step  9  of the first embodiment, above.  
         [0049]     Step  9 A of the second embodiment is equivalent to Step  9 A of the first embodiment, above.  
         [0050]     Step  10  of the second embodiment is equivalent to Step  10  of the first embodiment, above.  
         [0051]     Step  11  of the second embodiment is equivalent to Step  11  of the first embodiment, above.  
         [0052]      FIG. 3  presents the third embodiment of the invention in which the query for the Customer&#39;s identification is made by the Customer to a System administered by a government entity instead of a TTP as described in the first and second embodiments.  
         [0053]     Step  1  of the third embodiment is equivalent to Step  1  of the first embodiment, above.  
         [0054]     Step  2  of the third embodiment is equivalent to Step  2  of the first embodiment, above.  
         [0055]     Step  3  of the third embodiment is equivalent to Step  3  of the first embodiment, above, excepting that the Customer&#39;s SMS Request Message is delivered to a System operated and administered by a government entity.  
         [0056]     Step  4  of the third embodiment is equivalent to Step  4  of the first embodiment, above, excepting that the SMS Request Message (or other form of electronic communication) is delivered to a System operated and administered by a government entity.  
         [0057]     Step  5  of the third embodiment is equivalent to Step  5  of the first embodiment, above, excepting that the System is operated and administered by a government entity.  
         [0058]     Step  5 A of the third embodiment is equivalent to Step  5 A of the first embodiment, above.  
         [0059]     Step  6  of the third embodiment is equivalent to Step  6  of the first embodiment, above, excepting that the System is operated and administered by a government entity.  
         [0060]     Note that, in some forms of the third embodiment, the SMS Verification Messages and SMS Affirmation Messages of Steps  5  and  6  may be eliminated if a lesser degree of security, but a higher degree of ease of use, is desired.  
         [0061]     In Step  7  of the third embodiment, after receiving the SMS Request Message and the optional SMS Affirmation Messages, the System queries the data records of the government entity&#39;s ID Database System for the Customer&#39;s identification data and retrieves a digital image of Customer, and optionally other data such as a date of birth (“DOB”), as stored in the database. The System then composes an MMS message including the digital image and the DOB of Customer and any other optional data, including a warning if the Customer is below the age of eighteen or twenty-one. The System of the government entity then addresses the MMS message to Merchant&#39;s mobile phone and delivers the MMS message to a Cellular Carrier.  
         [0062]     In Step  7 A of the third embodiment, if the System&#39;s query to the government entity&#39;s ID Database System of Step  7  yielded no data record for the Customer then the System sends an ID Failure Message via SMS to the Cellular Carrier, and thereupon to the Merchant, indicating the failure to achieve a match.  
         [0063]     In Step  8  of the third embodiment, the Cellular Carrier delivers the MMS message created in Step  7  to the Merchant&#39;s mobile phone. The Merchant can now view the digital image of the customer, and the optional DOB (and other optional data) on the mobile phone.  
         [0064]     Step  9  of the third embodiment is equivalent to Step  11  of the first embodiment, above.  
         [0065]      FIG. 4  presents the fourth embodiment of the invention in which the query for the Customer&#39;s identification is made by the Merchant to a System administered by a government entity instead of a TTP as described in the first and second embodiments.  
         [0066]     Step  1  of the fourth embodiment is equivalent to Step  1  of the second embodiment, above.  
         [0067]     Step  2  of the fourth embodiment is equivalent to Step  2  of the second embodiment, above.  
         [0068]     Step  3  of the fourth embodiment is equivalent to Step  3  of the second embodiment, above.  
         [0069]     Step  4  of the fourth embodiment is equivalent to Step  4  of the second embodiment, above, excepting that the SMS Request Message (or other form of electronic communication) is delivered to a System operated and administered by a government entity.  
         [0070]     Step  5  of the fourth embodiment is equivalent to Step  5  of the second embodiment, above, excepting that the System is operated and administered by a government entity.  
         [0071]     Step  5 A of the fourth embodiment is equivalent to Step  5 A of the second embodiment, above.  
         [0072]     Step  6  of the fourth embodiment is equivalent to Step  6  of the second embodiment, above, excepting that the System is operated and administered by a government entity.  
         [0073]     Note that, in some forms of the third embodiment, the SMS Verification Messages and SMS Affirmation Messages of Steps  5  and  6  may be eliminated if a lesser degree of security, but a higher degree of ease of use, is desired.  
         [0074]     In Step  7  of the fourth embodiment, after receiving the SMS Request Message and the optional SMS Affirmation Messages, the System queries the data records of the government entity&#39;s ID Database System for the Customer&#39;s identification data and retrieves a digital image of Customer, and optionally other data such as a date of birth (“DOB”), as stored in the database. The System then composes an MMS message including the digital image and the DOB of Customer and any other optional data, including a warning if the Customer is below the age of eighteen or twenty-one. The System of the government entity then addresses the MMS message to Merchant&#39;s mobile phone and delivers the MMS message to a Cellular Carrier.  
         [0075]     In Step  7 A of the third embodiment, if the System&#39;s query to the government entity&#39;s ID Database System of Step  7  yielded no data record for the Customer then the System sends an ID Failure Message via SMS to the Cellular Carrier, and thereupon to the Merchant, indicating the failure to achieve a match.  
         [0076]     In Step  8  of the third embodiment, the Cellular Carrier delivers the MMS message created in Step  7  to the Merchant&#39;s mobile phone. The Merchant can now view the digital image of the customer, and the optional DOB (and other optional data) on the mobile phone.  
         [0077]     Step  9  of the fourth embodiment is equivalent to Step  11  of the second embodiment, above.  
         [0078]      FIG. 5  presents the fifth embodiment of the invention in which the query for the Customer&#39;s identification is made by the Customer to a System administered by a TTP. In this embodiment, the TTP also administers the ID Database System, which may be uploaded to the TTP by a “batch” process from a database administered by a government entity, such as a DOT. In the alternative, the digital photographs in the ID Database System may be uploaded by Customers and users whose identities have been verified in some manner by the TTP. Both options are illustrated in  FIG. 5 .  
         [0079]     Step  1  of the fifth embodiment is equivalent to Step  1  of the first embodiment, above.  
         [0080]     Step  2  of the fifth embodiment is equivalent to Step  2  of the first embodiment, above.  
         [0081]     Step  3  of the fifth embodiment is equivalent to Step  3  of the first embodiment, above.  
         [0082]     Step  4  of the fifth embodiment is equivalent to Step  4  of the first embodiment, above.  
         [0083]     Step  5  of the fifth embodiment is equivalent to Step  5  of the first embodiment, above.  
         [0084]     Step  5 A of the fifth embodiment is equivalent to Step  5 A of the first embodiment, above.  
         [0085]     Step  6  of the fifth embodiment is equivalent to Step  6  of the first embodiment, above.  
         [0086]     Note that, in some forms of the third embodiment, the SMS Verification Messages and SMS Affirmation Messages of Steps  5  and  6  may be eliminated if a lesser degree of security, but a higher degree of ease of use, is desired.  
         [0087]     In Step  7  of the fifth embodiment, after receiving the SMS Request Message and the optional SMS Affirmation Messages, the System queries the data records of the ID Database System (operated and administered by the TTP) for the Customer&#39;s identification data and retrieves a digital image of Customer, and optionally other data such as a date of birth (“DOB”), as stored in the database. The System then composes an MMS message including the digital image and the DOB of Customer and any other optional data, including a warning if the Customer is below the age of eighteen or twenty-one. The System of the government entity then addresses the MMS message to Merchant&#39;s mobile phone and delivers the MMS message to a Cellular Carrier.  
         [0088]     In Step  7 A of the fifth embodiment, if the System&#39;s query to the ID Database System of Step  7  yielded no data record for the Customer then the System sends an ID Failure Message via SMS to the Cellular Carrier, and thereupon to the Merchant, indicating the failure to achieve a match.  
         [0089]     In Step  8  of the fifth embodiment, the Cellular Carrier delivers the MMS message created in Step  7  to the Merchant&#39;s mobile phone. The Merchant can now view the digital image of the customer, and the optional DOB (and other optional data) on the mobile phone.  
         [0090]     Step  9  of the fifth embodiment is equivalent to Step  11  of the first embodiment, above.  
         [0091]      FIG. 6  presents the sixth embodiment of the invention in which the query for the Customer&#39;s identification is made by the Merchant to a System administered by a TTP. In this embodiment, the TTP also administers the ID Database System, which may be uploaded to the TTP by a “batch” process from a database administered by a government entity, such as a DOT. In the alternative, the digital photographs in the ID Database System may be uploaded by Customers and users whose identities have been verified in some manner by the TTP. Both options are illustrated in  FIG. 5 .  
         [0092]     Step  1  of the sixth embodiment is equivalent to Step  1  of the second embodiment, above.  
         [0093]     Step  2  of the sixth embodiment is equivalent to Step  2  of the second embodiment, above.  
         [0094]     Step  3  of the sixth embodiment is equivalent to Step  3  of the second embodiment, above.  
         [0095]     Step  4  of the sixth embodiment is equivalent to Step  4  of the second embodiment, above.  
         [0096]     Step  5  of the sixth embodiment is equivalent to Step  5  of the second embodiment, above, excepting that the System is operated and administered by a government entity.  
         [0097]     Step  5 A of the sixth embodiment is equivalent to Step  5 A of the second embodiment, above.  
         [0098]     Step  6  of the sixth embodiment is equivalent to Step  6  of the second embodiment, above.  
         [0099]     Note that, in some forms of the third embodiment, the SMS Verification Messages and SMS Affirmation Messages of Steps  5  and  6  may be eliminated if a lesser degree of security, but a higher degree of ease of use, is desired.  
         [0100]     In Step  7  of the sixth embodiment, after receiving the SMS Request Message and the optional SMS Affirmation Messages, the System queries the data records of the ID Database System (operated and administered by the TTP) for the Customer&#39;s identification data and retrieves a digital image of Customer, and optionally other data such as a date of birth (“DOB”), as stored in the database. The System then composes an MMS message including the digital image and the DOB of Customer and any other optional data, including a warning if the Customer is below the age of eighteen or twenty-one. The System of the government entity then addresses the MMS message to Merchant&#39;s mobile phone and delivers the MMS message to a Cellular Carrier.  
         [0101]     In Step  7 A of the sixth embodiment, if the System&#39;s query to the ID Database System of Step  7  yielded no data record for the Customer then the System sends an ID Failure Message via SMS to the Cellular Carrier, and thereupon to the Merchant, indicating the failure to achieve a match.  
         [0102]     In Step  8  of the sixth embodiment, the Cellular Carrier delivers the MMS message created in Step  7  to the Merchant&#39;s mobile phone. The Merchant can now view the digital image of the customer, and the optional DOB (and other optional data) on the mobile phone.  
         [0103]     Step  9  of the sixth embodiment is equivalent to Step  11  of the second embodiment, above