Source: http://www.google.com/patents/US20010056411?dq=5,815,794
Timestamp: 2017-04-30 16:22:50
Document Index: 166001115

Matched Legal Cases: ['arty 115', 'arty 115', 'arty 115', 'arty 115', 'arty 115', 'arty 115', 'arty 115', 'arty 115', 'arty 115', 'arty 115', 'arty 115', 'arty 115']

Patent US20010056411 - Mobile electronic transaction personal proxy - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsA method for obtaining a digital signature is disclosed. Upon receipt of request for a digital signature within a customer computer, a Mobile electronic transaction proxy within the customer PC notifies a web browser of the request for the digital signature and assists in obtaining a digital signature...http://www.google.com/patents/US20010056411?utm_source=gb-gplus-sharePatent US20010056411 - Mobile electronic transaction personal proxyAdvanced Patent SearchTry the new Google Patents, with machine-classified Google Scholar results, and Japanese and South Korean patents.Publication numberUS20010056411 A1Publication typeApplicationApplication numberUS 09/803,005Publication dateDec 27, 2001Filing dateMar 8, 2001Priority dateJun 5, 2000Also published asCN1446329A, EP1314077A2, US7043456, WO2001095070A2, WO2001095070A3Publication number09803005, 803005, US 2001/0056411 A1, US 2001/056411 A1, US 20010056411 A1, US 20010056411A1, US 2001056411 A1, US 2001056411A1, US-A1-20010056411, US-A1-2001056411, US2001/0056411A1, US2001/056411A1, US20010056411 A1, US20010056411A1, US2001056411 A1, US2001056411A1InventorsHelena Lindskog, Mikael NilssonOriginal AssigneeHelena Lindskog, Mikael NilssonExport CitationBiBTeX, EndNote, RefManPatent Citations (19), Referenced by (47), Classifications (25), Legal Events (3) External Links: USPTO, USPTO Assignment, EspacenetMobile electronic transaction personal proxy
DETAILED DESCRIPTION [0021] Referring now to the drawings, and more particularly to the FIG. 1, there is illustrated a document 10 and a hash 15 of the document 10. The document 10 would consist of a copy of text which may comprise a contract, letter, sales receipt, or any other item that may need to be signed by a user. The hash 15 contains a listing of information pertaining to the document. This information could include, for example, a document title, a document number/id, an author/name id, and a hash representation which may be numeric, alpha-numeric or symbolic. [0022] Referring now to FIG. 2, there is illustrated a general representation of the manner for using a personal trusted device such as a mobile terminal 20 to digitally sign a document 10. Alternatively, the personal trusted device could be a laptop computer, personal data assistant, pager or another mobile electronic device. The document 10 is forwarded to some type of viewing location 25 such as a PC, trusted server or other area which will be discussed momentarily. The document 10 is provided to the viewing location 25, where it may be displayed in its entirety by a user wishing to digitally sign the document 10. The hash 15 is created at the viewing location 25 or at a location associated with the viewing location 25 such that the hash 15 may be transmitted to the mobile terminal 20 over a wireless or wireline connection. The user may view the document 10 in its entirety at the viewing location 25 and digitally sign the hash 15 at the mobile terminal 20. [0023] A first embodiment is illustrated in FIG. 3 where there is illustrated a method for obtaining a digital signature using a trusted PC 30. In this embodiment, the information contained on the trusted PC 30 is assumed to be accurate, including the document 10, and the only thing needed to be protected is the communications channel 32 between the trusted PC 30 and the mobile terminal 20. The communications channel 32 may utilize a serial cable, infrared link or Bluetooth (Bluetooth is a trademark of Telefonaktiebolaget LM Ericsson) pairing for transmitting data. The only requirement for this embodiment is that the trusted PC 30 be authenticated and the integrity of the data be protected over the communications link 32. [0024] Referring now to FIG. 4, the trusted PC 30 receives the document 10 to be digitally signed at step 35. The mobile terminal 20 must authenticate the trusted PC 30 at step 40 to confirm that the mobile terminal 20 is linking with the proper trusted PC 30. After authentication, the communications channel 32 is established at step 45, and the hash 15 of document 10 is transmitted at step 50 to the mobile terminal 20. The user views the entire document 10 at the trusted PC 30 and provides the digital signature at step 55 using the mobile terminal 20. The digital signature may be automatically provided by entering a PIN number at the mobile terminal 20. [0025] A further embodiment, shown in FIG. 5, uses a crypto module 70 which may be implemented in a browser 65 contained within a PC 60. The crypto module 70 is integrated within the browser 65 and implements cryptography such as PKCS#11 and MS CAPI. In order to integrate the crypto module 70 within the browser 65, authenticity and integrity of the crypto module 70 must be verified by the PC operating system or the browser 65 before the module 70 is used. The crypto module 70 displays the document 10 to be signed along with the hash 15 to be transmitted to the mobile terminal 20 as is illustrated in FIG. 6. The mobile terminal 20 may also authenticate and integrity protect the communications channel 75 between the PC 60 and mobile terminal 20 as discussed previously with respect to FIGS. 3 and 4. [0026] Referring now to FIG. 7, there is illustrated a flow diagram of the method for obtaining a digital signature utilizing a crypto module 70. The document 10 to be signed is received at step 80 and displayed by the crypto module 70 using the browser 65 at step 85. The mobile terminal 20 authenticates the PC 60 and crypto module 70 at step 90 and establishes a communications channel 75 at step 95. The hash 15 of the document 10 is transmitted at step 100 to the mobile terminal 20 such that the hash 15 may be displayed at step 105 on a display of the mobile terminal 20. The user views the displayed hash 15 at the mobile terminal and the document 10 displayed at the crypto module 70 and provides at step 110 a digital signature of the document 10. [0027] Referring now to FIG. 8, there is illustrated a further embodiment for obtaining a digital signature of a document 10 wherein a trusted party 115 is used. In this embodiment, after receipt of a document 10, a PC 120 forwards the document through a web server 125 to the trusted party 115. Within the web server 125 a servlet 130 generates a hash 15 that is to be signed by the user at the mobile terminal 20. The hash 15 and document 10 are forwarded from the web server 125 to the trusted party 115, and the hash is forwarded to the mobile terminal 20 via a communications channel 135. The data is transmitted from the PC 120 to the web server 125 and from the web server 125 to the trusted party 115 using SSL/TLS protocol. [0028] Referring now to FIG. 9, there is provided a flow diagram more fully illustrating a method for obtaining a digital signature using a personal trusted device such as a mobile terminal 20 through a trusted party 115. The document 10 to be signed is received at the PC 120 at step 140, and a user requests a digital signature at the PC 120 at step 145. The trusted party 115 authenticates the PC 120 at step 150 before the connection established from the PC 120 to the web server 125 to the trusted party 115. Alternatively, the PC 120 may have been previously securely identified at the trusted party 115 and already have a registered mobile terminal 20 on file with the trusted party 115 for the transaction. [0029] After the PC 120 has been authenticated, the request for a digital signature is transmitted to the web server 125 at step 155 along with the document 10. The servlet 130 generates a hash 15 from the provided document 10. The hash 15 along with the document 10 and the request for the digital signature are forwarded at step 165 to the trusted party 115 from the web server 125. The trusted party 115 sends at step 170 the hash 15 to the mobile terminal 20 over a communications channel 135. After viewing the document at the trusted third party, the mobile terminal provides the digital signature at step 180, and the mobile terminal 20 notifies the trusted party 115 of the signature at step 185. The trusted party validates the provided digital signature and updates and notifies the transaction as being signed at both the PC 120 and mobile terminal 20 at step 190. [0030] Referring now to FIG. 10, there is illustrated yet another embodiment wherein a PC 200 transmits a document 10 to the mobile terminal 20 as streaming data. The general concept behind the use of streaming data is that all or a large portion of the data, not only the hash, shall be transmitted to the mobile terminal 20 for signature generation. The data to be signed is displayed at the PC 200 and is streamed to the mobile terminal 20. The problem still exists that the entire document cannot be displayed to a user on a small screen of the mobile terminal 20, and the internal buffers of the mobile terminal 20 are not normally large enough to store a large document. This requires the use of one of two solutions described in more detail in FIGS. 11 and 12. [0031] Referring now to FIG. 11, there is illustrated a method wherein a user utilizes a mouse at the PC 200 to select relevant text at step 205 that the user considers to be essential. The selected text and the hash 15 are transmitted to the mobile terminal at step 210. The user digitally signs the received information at step 215 after viewing the provided text and the hash 15. [0032] Referring now to FIG. 12, there is illustrated an alternative embodiment wherein a user may trigger a button or activation point at step 220 of the mobile terminal 20. Responsive to the trigger, the mobile terminal 20 displays the present content of its buffers at step 225. The user may then digitally sign a document at step 230 based upon what is viewed. [0033] Despite being unable to display or even store a large document 10, the mobile terminal 20 may be able to receive the text of the document 10 from the PC and compute the hash 15 from the received text. The hash 15 computed in the mobile terminal 20 can then be compared in the mobile terminal 20 with the hash 15 transmitted by the PC which the user is being invited to sign. Other checks such as byte count can also be computed in the mobile terminal 20 to verify that the document 10 to which the hash code 15 applies is the claimed document 10. It would be preferable to include the document byte count as part of the bytestring over which the hash code 15 is computed. The above steps provide additional security safeguards to the user that he is signing what he thinks he is signing. [0034] Referring now to FIG. 13, there is illustrated an alternative embodiment for providing a digital signature including a customer PC 250, a merchant server 255 and a customer mobile electronic transaction (MeT) device 260. The customer PC 250 includes a web browser 265 enabling the user to access the merchant server 255 via a network such as the Internet. The customer PC 250 further includes a mobile electronic terminal personal proxy (MPP) 270 for controlling electronic commerce transactions between the customer PC 250, the merchant server 255 and the customer Mobile electronic transaction device 260. The MPP 270 is accessed via the web browser 265. The MPP 270 comprises a software module that is executable by the customer PC 250. Communications between the browser 265 and MPP 270 and between the MPP 270 and the merchant server 255 use HTTP protocol (extended to handle the Mobile electronic transaction specific header information) over TCP/IP. The MPP 270 enables the customer PC 250 to act as a server for a Mobile electronic transaction device 260. Access to the Mobile electronic transaction device 260 will only require user provided authentication (password, PIN) when payment is requested. [0035] An application 275 within the customer PC provides any of a number of functionalities with respect to an electronic commerce transaction. With respect to the following description of the method of the present invention, the application 275 will provide a digital signature functionality wherein a data string provided from the merchant server 255 may have a digital signal appended thereto by the application 275. [0036] The web server 280 provides the ability for the mobile terminal to connect to services in the PC 250. The WAP gateway 285 provides for the ability of a wireless device such as the Mobile electronic transaction device 260 to access the Internet using the WAP protocol through the customer PC 250. The WAP gateway 285 acts as an interface between a WAP network and a TCP/IP network such as the Internet. The WAP gateway 285 converts between the WAP and TCP/IP protocols. [0037] The Bluetooth stack 290 enables the customer PC 250 to generate a short range wireless link with the Mobile electronic transaction device 260 within a limited, defined area using the Bluetooth protocol. While the present invention is described with the use of a short range wireless link using the Bluetooth protocol, it should be realized that any other short range wireless protocol enabling the customer PC 250 to access a closely located Mobile electronic transaction device 260 or other information devices would be useful within the context of the present invention. [0038] The mobile electronic transaction device 260 may consist of a mobile telephone, laptop computer, personal data assistant, or any other similarly configured mobile electronic device which contains information necessary to complete an electronic commerce transaction. The merchant server 255 includes applications 295 for performing necessary functionalities for completing an electronic commerce transaction with the customer PC 250 and a web server 300 enabling the merchant server to obtain access to a network such as the Internet. [0039] Referring now also to FIG. 14, there is illustrated a flow diagram illustrating the manner in which the MPP 270 controls a request for performance of a digital signature between a customer PC 250, merchant server 255 and Mobile electronic transaction device 260. At step 305, a request is transmitted from the web browser 265 to the MPP 270. The MPP 270 forwards the request to the web server 300 of the merchant server 255 at step 310. The request may comprise a request to purchase a particular item or to download already purchased products. [0040] In order to process the request, the merchant server 255 requires a digital signature from the customer. The merchant server 255 responds to the request by transmitting at step 315 a response that includes a specific data string and a request for digital signature to be attached to the data string. The merchant response to the request from the MPP 270 comprises a URI containing a specific HTTP 1.1 header: for example: [Mobile electronic transaction-sign: “http://merchantsite.com/responsesite/”, “String to sign”]. This comprises an instruction for the Mobile electronic transaction device 260 to sign the attached data string and transmit the digitally signed data string back to the indicated HTTP site. The MPP 270 will pass most requests or responses through without taking action. However, once a Mobile electronic transaction command is detected within a request or response the MPP 270 is actuated. The MPP 270 recognizes the Mobile electronic transaction command included in the HTTP header and transmits at step 320 a notification to the browser 265 indicating a digital signature has been requested. It should be realized that Mobile electronic transaction commands other than a request for a digital signal may also be utilized. The web browser 265 will display a page having a PRAGMA REFRESH (fetch from server when reloaded, i.e., do not cache) header command while the digital signature is obtained. [0041] The data string within the response from the merchant server 255 is forwarded at step 325 to the application 275 within the customer's PC 250. Responsive to the received data string, the application 275 transmits at step 330 a command to the Bluetooth stack 290. The command instructs the Bluetooth stack 290 to awaken the Mobile electronic transaction device 260, if possible. The awakening is accomplished by transmitting an AT command to the Mobile electronic transaction device 260 using Bluetooth at step 335. Responsive to this awakening, the Mobile electronic transaction device 260 will request at step 336 the same application of the Mobile electronic transaction device 260. The application within the Mobile electronic transaction device 260 executes at step 340 a WML script code that will provide a request containing the digital signature (response). At step 345 the response including the digital signature is transmitted to the web server 280 via the Bluetooth stack 290 and WAP Gateway 285. The response is then passed to the application 275. The application 275 appends the digital signature to the provided data string at step 350 and notifies the Bluetooth stack 290 of the completed signature at step 355. [0042] The application 275 forwards at step 360 the digitally signed data string back to the MPP 270. The MPP 270 notifies the browser at step 365 of the completed signing of the data string which then begins reloading a URI displaying an indication that the data string has been signed. The MPP transmits at step 370 an HTTP request to the URL contained in the original HTTP header (http://merchantsite.com/responsesite/) containing the signed data string. Upon receipt of the signed data string the web server 300 within the merchant server 255 transmits a response back to the MPP at 375 notifying the web browser 265 of the customer PC that the transaction is completed. [0043] The previous description is of a preferred embodiment for implementing the invention, and the scope of the invention should not necessarily be limited by this description. The scope of the present invention is instead defined by the following claims. Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS5604801 *Feb 3, 1995Feb 18, 1997International Business Machines CorporationPublic key data communications system under control of a portable security deviceUS5907681 *Oct 20, 1997May 25, 1999International Business Machines CorporationIntelligent method, apparatus and computer program product for automated refreshing of internet web pagesUS5910989 *Apr 22, 1996Jun 8, 1999GemplusMethod for the generation of electronic signatures, in particular for smart cardsUS6269445 *Nov 18, 1999Jul 31, 2001Hitachi, Ltd.Electronic shopping method, electronic shopping system and document authenticating method relating theretoUS6377810 *Jun 11, 1999Apr 23, 2002Motorola, Inc.Method of operation of mobile wireless communication system with location informationUS6405178 *Dec 20, 1999Jun 11, 2002Xerox CorporationElectronic commerce enabled purchasing systemUS6453416 *Dec 19, 1997Sep 17, 2002Koninklijke Philips Electronics N.V.Secure proxy signing device and method of useUS6463534 *Mar 26, 1999Oct 8, 2002Motorola, Inc.Secure wireless electronic-commerce system with wireless network domainUS6515988 *Jul 17, 1998Feb 4, 2003Xerox CorporationToken-based document transactionsUS6654754 *Dec 8, 1999Nov 25, 2003Inceptor, Inc.System and method of dynamically generating an electronic document based upon data analysisUS6694431 *Oct 12, 1999Feb 17, 2004International Business Machines CorporationPiggy-backed key exchange protocol for providing secure, low-overhead browser connections when a server will not use a message encoding scheme proposed by a clientUS6697944 *Oct 1, 1999Feb 24, 2004Microsoft CorporationDigital content distribution, transmission and protection system and method, and portable device for use therewithUS6707915 *Jul 27, 1999Mar 16, 2004Nokia Mobile Phones LimitedData transfer verification based on unique ID codesUS6779115 *Feb 18, 2000Aug 17, 2004Digital5, Inc.Portable device using a smart card to receive and decrypt digital dataUS20020026584 *Mar 8, 2001Feb 28, 2002Janez SkubicMethod for signing documents using a PC and a personal terminal deviceUS20020095583 *Aug 29, 2001Jul 18, 2002Vanstone Scott A.Digital signatures on a smartcardUS20020116608 *Mar 4, 2002Aug 22, 2002Wheeler Henry LynnSending electronic transaction message, digital signature derived therefrom, and sender identity information in AADS systemUS20030140114 *Dec 31, 2002Jul 24, 2003Katz Donald R.Digital information library and delivery systemUS20030172280 *Oct 22, 2002Sep 11, 2003Scheidt Edward M.Access control and authorization system* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS7357309 *Jun 22, 2004Apr 15, 2008Telefonaktiebolaget Lm Ericsson (Publ)EMV transactions in mobile terminalsUS7650639 *Mar 31, 2005Jan 19, 2010Microsoft CorporationSystem and method for protecting a limited resource computer from malwareUS7673227Sep 16, 2004Mar 2, 2010Microsoft CorporationUser interface for integrated spreadsheets and word processing tablesUS7673228Mar 30, 2005Mar 2, 2010Microsoft CorporationData-driven actions for network formsUS7689929Feb 11, 2005Mar 30, 2010Microsoft CorporationMethods and systems of providing information to computer usersUS7692636Sep 30, 2004Apr 6, 2010Microsoft CorporationSystems and methods for handwriting to a screenUS7721190Nov 16, 2004May 18, 2010Microsoft CorporationMethods and systems for server side form processingUS7725834Mar 4, 2005May 25, 2010Microsoft CorporationDesigner-created aspect for an electronic form templateUS7743063Jan 27, 2005Jun 22, 2010Microsoft CorporationMethods and systems for delivering software via a networkUS7774620May 27, 2004Aug 10, 2010Microsoft CorporationExecuting applications at appropriate trust levelsUS7779027Sep 13, 2004Aug 17, 2010Microsoft CorporationMethods, systems, architectures and data structures for delivering software via a networkUS7818677Aug 12, 2004Oct 19, 2010Microsoft CorporationSingle window navigation methods and systemsUS7865477Oct 15, 2007Jan 4, 2011Microsoft CorporationSystem and method for real-time validation of structured data filesUS7900134Nov 8, 2006Mar 1, 2011Microsoft CorporationAuthoring arbitrary XML documents using DHTML and XSLTUS7913159Mar 28, 2003Mar 22, 2011Microsoft CorporationSystem and method for real-time validation of structured data filesUS7925621Jan 29, 2008Apr 12, 2011Microsoft CorporationInstalling a solutionUS7937651Jan 14, 2005May 3, 2011Microsoft CorporationStructural editing operations for network formsUS7971139Oct 31, 2007Jun 28, 2011Microsoft CorporationCorrelation, association, or correspondence of electronic formsUS7979856Sep 1, 2005Jul 12, 2011Microsoft CorporationNetwork-based software extensionsUS8001459Dec 5, 2005Aug 16, 2011Microsoft CorporationEnabling electronic documents for limited-capability computing devicesUS8010515Apr 15, 2005Aug 30, 2011Microsoft CorporationQuery to an electronic formUS8074217Oct 29, 2007Dec 6, 2011Microsoft CorporationMethods and systems for delivering softwareUS8117552Dec 5, 2006Feb 14, 2012Microsoft CorporationIncrementally designing electronic forms and hierarchical schemasUS8200975 *Jun 29, 2005Jun 12, 2012Microsoft CorporationDigital signatures for network formsUS8429522Jun 15, 2011Apr 23, 2013Microsoft CorporationCorrelation, association, or correspondence of electronic formsUS8487879Oct 29, 2004Jul 16, 2013Microsoft CorporationSystems and methods for interacting with a computer through handwriting to a screenUS8819072Feb 2, 2004Aug 26, 2014Microsoft CorporationPromoting data from structured data filesUS8892993Feb 8, 2008Nov 18, 2014Microsoft CorporationTranslation fileUS8918729Apr 2, 2008Dec 23, 2014Microsoft CorporationDesigning electronic formsUS8955094Jan 17, 2006Feb 10, 2015International Business Machines CorporationUser session management for web applicationsUS9191213 *Dec 18, 2013Nov 17, 2015Xerox CorporationMethods and systems for messaging with physical presence and temporal verificationsUS9210234Jun 13, 2011Dec 8, 2015Microsoft Technology Licensing, LlcEnabling electronic documents for limited-capability computing devicesUS9229917Mar 18, 2011Jan 5, 2016Microsoft Technology Licensing, LlcElectronic form user interfacesUS9239821Oct 31, 2014Jan 19, 2016Microsoft Technology Licensing, LlcTranslation fileUS9268760Apr 22, 2013Feb 23, 2016Microsoft Technology Licensing, LlcCorrelation, association, or correspondence of electronic formsUS20050156026 *Jun 22, 2004Jul 21, 2005Angana GhoshEMV transactions in mobile terminalsUS20060236393 *Mar 31, 2005Oct 19, 2006Microsoft CorporationSystem and method for protecting a limited resource computer from malwareUS20070169185 *Jan 17, 2006Jul 19, 2007Readshaw Neil IUser session management for web applicationsUS20100000888 *Jul 7, 2008Jan 7, 2010J.L. Clark, Inc.Tobacco Container With InsertUS20110185180 *Sep 15, 2009Jul 28, 2011Peter GullbergMethod and device for creating digital signatureUS20140068409 *Sep 6, 2012Mar 6, 2014Signaturelink, Inc.Systems and Methods for Capturing Real Time Client Side Data and For Generating a Permanent RecordUS20140208198 *Oct 22, 2013Jul 24, 2014International Business Machines CorporationRepresentation of an element in a page via an identifierUS20150172059 *Dec 18, 2013Jun 18, 2015Xerox CorporationMethods and systems for messaging with physical presence and temporal verificationsUS20160071104 *Sep 4, 2014Mar 10, 2016George Gregory StamatisSecurebuy merchant information analytics decision engineDE102013221764A1 *Oct 25, 2013Apr 30, 2015Bundesdruckerei GmbhVerfahren zur Erzeugung einer elektronischen SignaturDE102013221764A9 *Oct 25, 2013Jun 25, 2015Bundesdruckerei GmbhVerfahren zur Erzeugung einer elektronischen SignaturWO2006120365A1 *May 10, 2005Nov 16, 2006Hani GirgisSecure transactions using a personal computer* Cited by examinerClassifications U.S. Classification705/76International ClassificationH04L9/32, H04L29/06, H04L29/08Cooperative ClassificationH04L67/289, H04L67/04, H04L67/2814, H04L9/3247, H04L2209/56, H04L63/0281, H04L2209/76, G06Q10/0875, G06Q20/3821, H04L63/12, H04L2209/80, H04L63/08, H04L9/321European ClassificationH04L63/12, H04L63/08, G06Q10/0875, G06Q20/3821, H04L29/08N3, H04L9/32S, H04L29/08N27X8, H04L29/08N27DLegal EventsDateCodeEventDescriptionJun 18, 2001ASAssignmentOwner name: TELEFONAKTIEBOLAGET L M ERICSSON (PUBL), SWEDENFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:NILSSON, MIKAEL;LINDSKOG, HELENA;REEL/FRAME:011906/0238Effective date: 20010606Nov 9, 2009FPAYFee paymentYear of fee payment: 4Nov 12, 2013FPAYFee paymentYear of fee payment: 8RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services