throbber
IN THE UNITED STATES PATENT AND TRADEMARK OFFICE
`
`Docket No.: W0537—700620
`
`Applicant:
`Serial No:
`Confirmation No:
`
`Kenneth P. Weiss
`11/768,729
`3536
`
`Filed:
`For:
`
`June 26, 2007
`UNIVERSAL SECURE REGISTRY
`
`Dada, Beemnet W.
`Examiner:
`2435
`Art Unit:
`
`
`CERTIFICATE OF TRANSMISSION UNDER 37 C.F.R. §1.8§a[
`
`The undersigned hereby certifies that this document is being electronically filed in accordance with
`§ l.6(a)(4), on the 20th day of November, 2009.
`
`/Robert V. Donahoe/
`
`Robert V. Donahoe, Reg. No. 46,667
`
`Commissioner for Patents
`
`Sir:
`
`AMENDMENT
`
`In response to the Office Action mailed July 20, 2009, please amend the above—identified
`
`application as follows. Changes to the Claims are shown by strike through (for deleted matter)
`
`and underlining (for added matter).
`
`Amendments to the Claims are reflected in the listing of claims which begins on page 2
`
`of this paper.
`
`Remarks begin on page 8 of this paper.
`
`9778691
`
`1 of 11
`
`10f11
`
`APPLE 1106
`
`APPLE 1 106
`
`

`

`Serial No.: 11/768,729
`
`- 2 -
`
`Art Unit: 2435
`
`Amendments to the Claims
`
`This listing of claims will replace all prior versions, and listings, of claims in
`
`the application.
`
`Listing of Claims:
`
`10
`
`15
`
`1.
`
`(Currently Amended) A secure registry system for providing information to a
`
`service provider to enable the service provider to provide services to entities with
`
`secure data stored in the secure registry system, comprising:
`
`a database including secure data for each entity and a multicharacter code for
`
`each entity having secure data in the secure registry system, the multicharacter code
`
`being mapped to the secure data; and
`
`a processor configured to receive, from the service provider, the
`
`multicharacter code for the entity on whose behalf services are to be provided,
`
`configured to map the multicharacter code to information required by—the—sewiee
`
`provider—inorder—to provide the services where the information is unknown to the
`
`service provider, to provide the information to—one—of—the—ser—viee—provider—to—perform
`
`Wto a third party to enable a transaction without providing the
`
`20
`
`information to the service provider.
`
`2.
`
`(Original) The system of claim 1, wherein the multicharacter code is a secret
`
`code of the entity.
`
`25
`
`30
`
`3.
`
`(Currently Amended) The system of claim 1, wherein the multicharacter code
`
`is provided to the systemvi—a—the—entit—y via a secure electronic transmission device.
`
`4.
`
`(Currently Amended) The system of claim 1, wherein the multicharacter code
`
`is encrypted and transmitted to the systemby—the—entit—y, and the system is configured
`
`to decrypt the multicharacter code with a public key of the entity.
`
`977869—1
`
`2 of 11
`
`20f11
`
`

`

`Serial No.: 11/768,729
`
`- 3 -
`
`Art Unit: 2435
`
`5.
`
`(Currently Amended) The system as claimed in claim 1, wherein said service
`
`provider’s service includes provides delivery—serviees, wherein the information is an
`
`address to which an item is to be delivered t_ofor the entity, wherein the system
`
`receives the multicharacter code and the system uses the multicharacter code to obtain
`
`the appropriate address for delivery of the item by the third party.
`
`10
`
`15
`
`20
`
`25
`
`6.
`
`7.
`
`8.
`
`(Canceled)
`
`(Canceled)
`
`(Currently Amended) The secure registry system as claimed in claim 1,
`
`wherein the information includes the secure datawherein—the—s—ystem—is—eonfi—gured—to
`
`
`
`9.
`
`(Currently Amended) The secure registry system as claimed in claim fl[[1]],
`
`wherein the identity information includesis credit card information regarding the
`
`entity, and wherein the processor is configured to provide the credit card information
`
`based upon the multicharacter code of the entity to enable the a—transaction.
`
`10.
`
`(Original) The system as claimed in claim 9, wherein the system is configured
`
`to receive an approval of the credit card transaction without providing the credit card
`
`number of the entity to the service provider.
`
`11.
`
`(Currently Amended) The system as claimed in claim Q1, wherein the identity
`
`information includesis bank card information regarding the entity, and wherein the
`
`processor is configured to provide the bank card information to enable th_ea
`
`transaction based upon the multicharacter code of the entity.
`
`977869—1
`
`3 of 11
`
`30f11
`
`

`

`Serial No.: 11/768,729
`
`- 4 -
`
`Art Unit: 2435
`
`12.
`
`(Original) The system as claimed in claim 11, wherein the system is
`
`configured to provide an approval of the bank card transaction without providing the
`
`bank card number of the entity to the service provider.
`
`13.
`
`(Currently Amended) The system as claimed in claim 31, wherein the
`
`information is personal identification information regarding the entity.
`
`14.
`
`(Original) The system as claimed in claim 13, wherein the personal
`
`identification information comprises a photograph of the entity.
`
`10
`
`15
`
`20
`
`25
`
`15.
`
`(Original) The system as claimed in claim 1, wherein the information is email
`
`address information regarding the entity.
`
`16.
`
`(Currently Amended) A method for providing a service to entities who have
`
`secure data stored in a secure registry in which each entity is identified by a
`
`multicharacter code, the service provided by a service provider, the method
`
`comprising:
`
`receiving the multicharacter code for an entity on whose behalf the services
`
`are to be provided;
`
`mapping the multicharacter code to information required by—the—sewiee
`
`provider—inorder—to provide the services;
`
`providing the information to a third party without providing the information to
`
`the service provider; and
`
`using the eorresponding information to enable the service provider to
`
`provideper—for—m the service without the service provider’s knowledge of the
`
`information.
`
`17.
`
`(Canceled)
`
`977869—1
`
`4 of 11
`
`4of11
`
`

`

`Serial No.: 11/768,729
`
`- 5 -
`
`Art Unit: 2435
`
`18.
`
`(Original) The method of claim 16, wherein the act of receiving the
`
`multicharacter code comprises receiving a secret multicharacter code which is secret
`
`to the entity.
`
`19.
`
`(Original) The method of claim 16, wherein the act of receiving the
`
`multicharacter code comprises receiving the secret code which has been transmitted
`
`by via a secure electronic transmission device.
`
`20.
`
`(Original) The method of claim 16, wherein the act of receiving the
`
`multicharacter code comprises receiving an encrypted multicharacter code and the
`
`method further comprises decrypting the encrypted multicharacter code.
`
`21.
`
`(Currently Amended) The method as claimed in claim 16, wherein the service
`
`provider’s service includes provides delivery—services, wherein the information is an
`
`address to which an item is to be delivered for the entity, and wherein the third party
`
`the—provider receives an—item—to—be—deli—vered—and the address for delivery of the Q
`
`item provided by the service provider.
`
`22.
`
`(Canceled)
`
`23.
`
`(Canceled)
`
`10
`
`15
`
`20
`
`24.
`
`(Original) The method as claimed in claim 16, wherein the act of using the
`
`information to perform the services comprises using credit card information about the
`
`25
`
`entity to enable a transaction.
`
`25.
`
`(Original) The method as claimed in claim 24, wherein the act of using the
`
`information comprises receiving a validation or denial of the credit card transaction
`
`without providing the credit card number of the entity to the service provider.
`
`30
`
`977869—1
`
`5 of 11
`
`50f11
`
`

`

`Serial No.: 11/768,729
`
`- 6 -
`
`Art Unit: 2435
`
`26.
`
`(Original) The method as claimed in claim 16, wherein the act of using the
`
`information to perform the services comprises using bank card information about the
`
`entity to enable a transaction.
`
`27.
`
`(Original) The method as claimed in claim 26, wherein the act of using the
`
`information comprises receiving a validation or denial of the bank card transaction
`
`without providing the bank card number of the entity to the service provider.
`
`28.
`
`(Currently Amended) The method as claimed in claim 16, wherein the act of
`
`mapping the multicharacter code to information required by the service provider
`
`comprises mapping the multicharacter code i—nto personal identification information
`
`about the entity.
`
`29.
`
`(Original) The method as claimed in claim 28, wherein the personal
`
`identification information comprises a photograph of the entity.
`
`30.
`
`(Original) The method as claimed in claim 16, wherein the information to
`
`comprises an email address information about the entity.
`
`31.
`
`(New) The system of claim 1, wherein the information includes identity
`
`information concerning the entity.
`
`32.
`
`(New) The method as claimed in claim 24, further comprising an act of
`
`transmitting to the service provider one of an approval or a denial of the credit card
`
`transaction without providing the credit card number of the entity to the service
`
`provider.
`
`33.
`
`(New) The system of claim 1, wherein the database is further configured to
`
`associate biometric information with each entity having secure data in the secure
`
`10
`
`15
`
`20
`
`25
`
`30
`
`registry, respectively.
`
`977869—1
`
`6 of 11
`
`6of11
`
`

`

`Serial No.: 11/768,729
`
`- 7 -
`
`Art Unit: 2435
`
`34.
`
`(New) The system of claim 33, wherein the processor is further configured to
`
`map the multicharacter code to biometric information associated with the entity on
`
`whose behalf the services are to be provided and to provide the biometric information
`
`to the service provider.
`
`35.
`
`(New) The system of claim 34, wherein the biometric information includes an
`
`image of the entity on whose behalf the services are to be provided.
`
`36.
`
`(New) The system of claim 34, wherein the multicharacter code comprises a
`
`10
`
`time-varying multicharacter code generated by a device associated with the entity on
`
`whose behalf services are to be provided.
`
`37.
`
`(New) The method as claimed in claim 16, further comprising an act of
`
`associating biometric information with each entity having secure data in the secure
`
`15
`
`registry, respectively.
`
`38.
`
`(New) The method of claim 37, further comprising acts of:
`
`mapping the multicharacter code to biometric information associated with the
`
`entity on whose behalf the services are to be provided; and
`
`providing the biometric information to the service provider.
`
`39.
`
`(New) The method of claim 38, wherein the biometric information includes
`
`an image of the entity on whose behalf the services are to be provided.
`
`40.
`
`(New) The method of claim 38, further comprising an act of generating a
`
`time-varying multicharacter code by a device associated with the entity on whose
`
`behalf the services are to be provided.
`
`20
`
`25
`
`977869—1
`
`7 of 11
`
`7of11
`
`

`

`Serial No.: 11/768,729
`
`— 8 —
`
`Art Unit: 2435
`
`REMARKS
`
`Claims 1—30 were previously pending in this application. By this amendment, Applicant
`
`is canceling claims 6, 7, 17, 22, and 23 without prejudice or disclaimer. Claims 1, 3—5, 8, 9, 11,
`
`13, 16, 21 and 28 are amended herein. New claims 31—40 are added herein. As a result claims 1—
`
`5, 8—16, 18—21 and 24—40 are pending for examination with claims 1 and 16 being independent
`
`claims. No new matter has been added. Support for the amendments to the independent claims
`
`can be found at least, for example, in Figs. 7—10 and the associated description at pages 17—20 of
`
`the application as originally filed. Support for the new claims can be found at least, for example,
`
`at page 12, lines 20—28 and page 17, lines 5—26.
`
`Re'ections Under 35 U.S.C.
`
`102
`
`The Office Action rejects claims 1—3, 5—19 and 21—30 under 35 U.S.C. §102(e) as being
`
`anticipated by US. Patent No. 6,941,271 B1 to Soong (hereinafter Soong). This rejection
`
`includes the rejection of independent claims 1 and 16.
`
`Applicants respectfully assert that Soong does not anticipate independent claims 1 and
`
`16, as amended herein. Claim 1 recites “a secure registry system for providing information to a
`
`service provider to enable the service provider to provide services to entities with secure data
`
`stored in the secure registry system, comprising
`
`a processor configured to receive, from the
`
`service provider, the multicharacter code for the entity on whose behalf services are to be
`
`provided, configured to map the multicharacter code to information required to provide the
`
`services where the information is unknown to the service provider, to provide the information to
`
`a third party to enable a transaction without providing the information to the service provider.”
`
`(Emphasis added.) Claim 16 recites a “method for providing a service to entities who have
`
`secure data stored in a secure registry in which each entity is identified by a multicharacter code,
`
`the service provided by a service provider, the method comprising: receiving the multicharacter
`
`code for an entity on whose behalf the services are to be provided; mapping the multicharacter
`
`code to information required to provide the services; providing the information to a third party
`
`without providing the information to the service provider;_and using the information to enable
`
`the service provider to provide the service without the service provider’s knowledge of the
`
`information.” (Emphasis added.)
`
`9778691
`
`8 of 11
`
`80f11
`
`

`

`Serial No.: 11/768,729
`
`— 9 —
`
`Art Unit: 2435
`
`Soong describes a method for accessing component fields of a patient record where
`
`access to a site computer by authorized persons is provided through the use of login IDs and
`
`passwords. (Col. 6, lines 14—59.) User are allowed access to patient records, for example, when
`
`they provide the correct password. In each case, the user seeking access to a patient’s records
`
`has knowledge of the information needed to login and gain access. Id. Accordingly, the mere
`
`description of login IDs and passwords does not describe either: a secure registry system for
`
`providing information to a service provider to enable the service provider to provide services to
`
`entities with secure data stored in the secure registry system,
`
`where the information is
`
`unknown to the service provider, to provide the information to a third party to enable a
`
`transaction without providing the information to the service provider,” as recited in claim 1; or a
`
`method for providing a service to entities who have secure data stored in a secure registry in
`
`which each entity is identified by a multicharacter code, the service provided by a service
`
`provider, the method comprising:
`
`mapping the multicharacter code to information required to
`
`provide the services; providing the information to a third party without providing the information
`
`to the service provider; and using the information to enable the service provider to provide the
`
`service without the service provider’s knowledge of the information, as recited in claim 16.
`
`Thus, Applicant respectfully asserts that independent claims 1 and 16 are patentable in
`
`view of Soong at least for the above reasons. Each of claims 2, 3, 5, 8—16, 18, 19, 21 and 24—30
`
`directly or indirectly depend from one of allowable claims 1 and 16 and are therefore patentable
`
`for at least the same reasons as the independent claim from which they depend, respectively.
`
`Claims 6, 7, 17, 22 and 23 are canceled herein. Accordingly, reconsideration and withdrawal of
`
`the rejection of claims 1—3, 5—19 and 21—30 under 35 U.S.C. §102(e) as being anticipated by
`
`Soong is respectfully requested.
`
`Re'ections Under 35 U.S.C.
`
`103
`
`The Office Action rejects claims 4 and 20 under 35 U.S.C. §103(a) as being unpatentable
`
`over Soong in view of U.S. Patent No. 5,398,285 to Borgelt (hereinafter Borgelt). Claim 4
`
`depends from independent claim 1 and claim 20 depends from independent claim 16. Applicant
`
`respectfully asserts that Borgelt does not cure the deficiencies of Soong because Borgelt alone or
`
`in proper combination with Soong also does not teach or suggest “a secure registry system for
`
`providing information to a service provider to enable the service provider to provide services to
`
`977869—1
`
`9 of 11
`
`9of11
`
`

`

`Serial No.: 11/768,729
`
`— 10 —
`
`Art Unit: 2435
`
`entities with secure data stored in the secure registry system, comprising
`
`a processor
`
`configured to receive, from the service provider, the multicharacter code for the entity on whose
`
`behalf services are to be provided, configured to map the multicharacter code to information
`
`required to provide the services where the information is unknown to the service provider, to
`
`provide the information to a third party to enable a transaction without providing the information
`
`to the service provider,” as recited in claim 1; or a “method for providing a service to entities
`
`who have secure data stored in a secure registry in which each entity is identified by a
`
`multicharacter code, the service provided by a service provider, the method comprising:
`
`receiving the multicharacter code for an entity on whose behalf the services are to be provided;
`
`mapping the multicharacter code to information required to provide the services; providing the
`
`information to a third party without providing the information to the service provider; and using
`
`the information to enable the service provider to provide the service without the service
`
`provider’s knowledge of the information,” as recited in claim 16.
`
`Accordingly, claims 4 and 20 are patentable for at least the same reasons as claims 1 and
`
`16, respectively. Applicant respectfully requests reconsideration and withdrawal of the rejection
`
`of claims 4 and 20 under 35 U.S.C. §103(a) as being unpatentable over Soong in view of
`
`Borgelt.
`
`W
`
`In addition to the above, Applicant respectfully asserts that new claims 31—40 further
`
`patentably distinguish over the cited references. For example, new claim 33 recites that “the
`
`database is further configured to associate biometric information with each entity having secure
`
`data in the secure registry, respectively.” New claim 37 recites “an act of associating biometric
`
`information with each entity having secure data in the secure registry, respectively.” Applicant
`
`respectfully notes that neither Soong nor Borgelt even refer to biometric information.
`
`Accordingly, new claims 33 and 37, and claims 34—36 and 38—40 which depend therefrom,
`
`respectively, are patentable for at least this additional reason.
`
`977869—1
`
`10 of 11
`
`lOofll
`
`

`

`Serial No.: 11/768,729
`
`— 11 —
`
`Art Unit: 2435
`
`CONCLUSION
`
`In View of the foregoing amendments and remarks, reconsideration is respectfully
`
`requested. This application should now be in condition for allowance; a notice to this effect is
`
`respectfully requested. If the Examiner believes, after this amendment, that the application is not
`
`in condition for allowance, the Examiner is requested to call the Applicant’ s attorney at the
`
`telephone number listed below.
`
`If this response is not considered timely filed and if a request for an extension of time is
`
`otherwise absent, Applicant hereby requests any necessary extension of time. If there is a fee
`
`occasioned by this response, including an extension fee that is not covered by an accompanying
`
`payment, please charge any deficiency to Deposit Account No. 50/2762, Ref. No. W0537—
`
`700620.
`
`Respectfully submitted,
`Kenneth P. Weiss, Applicant
`
`By: /Robert V. Donahoe/
`Robert V. Donahoe, Reg. No. 46,667
`LANDO & ANASTASI, LLP
`One Main Street
`
`Cambridge, Massachusetts 02142
`United States of America
`
`Telephone: 617—395-7000
`Facsimile: 617—395-7070
`
`977869—1
`
`11 of 11
`
`ll ofll
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket