Status of the Claims
The following is a non-final, first office action on the merits in response to the application filed on 02/16/2023. Claims 1-24 are pending and are examined below. The Information Disclosure Statements (IDSs) filed on 5/15/2023 has been considered by the Examiner.
The application claims priority under 35 U.S.C. § 120 as a continuation of U.S. Patent Application No. 16/795,378 filed on February 19, 2020, which claims priority under 35 U.S.C. § 120 as a divisional of U.S. Patent Application No. 13/106,641 filed on May 12, 2011 (now U.S. Patent No. 10,614,417).
Notice of Pre-AIA or AIA Status
The present application is being examined under the pre-AIA first to invent provisions.
Double Patenting
The nonstatutory double patenting rejection is based on a judicially created doctrine
grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A nonstatutory double patenting rejection is appropriate where the conflicting claims are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg, 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman, 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi, 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); In re Thorington, 418 F.2d 528, 163 USPQ 644 (CCPA 1969).
A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on nonstatutory double patenting provided the reference application or patent either is shown to be commonly owned with the examined application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. See MPEP § 717.02 for applications subject to examination under the first inventor to file provisions of the AIA as explained in MPEP § 2159. See MPEP § 2146 et seq. for applications not subject to examination under the first inventor to file provisions of the AIA . A terminal disclaimer must be signed in compliance with 37 CFR 1.321(b).
The filing of a terminal disclaimer by itself is not a complete reply to a nonstatutory double patenting (NSDP) rejection. A complete reply requires that the terminal disclaimer be accompanied by a reply requesting reconsideration of the prior Office action. Even where the NSDP rejection is provisional the reply must be complete. See MPEP § 804, subsection I.B.1. For a reply to a non-final Office action, see 37 CFR 1.111(a). For a reply to final Office action, see 37 CFR 1.113(c). A request for reconsideration while not provided for in 37 CFR 1.113(c) may be filed after final for consideration. See MPEP §§ 706.07(e) and 714.13.
The USPTO Internet website contains terminal disclaimer forms which may be used. Please visit www.uspto.gov/patent/patents-forms. The actual filing date of the application in which the form is filed determines what form (e.g., PTO/SB/25, PTO/SB/26, PTO/AIA /25, or PTO/AIA /26) should be used. A web-based eTerminal Disclaimer may be filled out completely online using web-screens. An eTerminal Disclaimer that meets all requirements is auto-processed and approved immediately upon submission. For more information about eTerminal Disclaimers, refer to www.uspto.gov/patents/apply/applying-online/eterminal-disclaimer.
Claims 1-24 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-25 of U.S. Patent No. 11610182 Although the claims at issue are not identical, they are not patentably distinct from each other.
Instant Claims
Reference Claims
Claim 1: A method comprising:
receiving a first request at a verification server, the first request associated with a visitor accessing a web page comprising a form into which the visitor is able to enter information using a web browser of the visitor;
in response to the first request, providing a reference key comprising a unique identifier from the verification server;
collecting, at the verification server, information about the web page or form and about the visitor or the web browser of the visitor;
generating a certificate containing the collected information and associated with the reference key at the verification server, the certificate identified using a uniform resource locator (URL); and transmitting the certificate from the verification server.
Claim 1: A method of providing a lead that can be verified, the method comprising:
notifying a verification server when a visitor accesses a web page to enter information into a form;
receiving a reference key comprising a unique identifier from the verification server;
detecting that the visitor has submitted the form with entered information; and
in response to the visitor submitting the form, sending form data to the verification server or at least one interested party, the form data comprising the reference key, at least some of the entered information, and a screenshot of at least one of the web page or the form, the screenshot including at least a portion of the entered information.
Claim 3: wherein storing the reference key in the form comprises storing a verification universal resource locator (URL) that includes the reference key.
Instant Claims
Reference Claims
Claim 9: An apparatus comprising: at least one memory configured to store instructions; and at least one processing device configured to execute the instructions stored in the at least one memory, the instructions when executed configured to cause the at least one processing device to:
receive a first request associated with a visitor accessing a web page comprising a form into which the visitor is able to enter information using a web browser of the visitor;
in response to the first request, provide a reference key comprising a unique identifier;
collect information about the web page or form and about the visitor or the web browser of the visitor;
generate a certificate containing the collected information and associated with the reference key, the certificate identified using a uniform resource locator (URL); and initiate transmission of the certificate.
Claim 17: An apparatus comprising: at least one memory configured to store instructions; and at least one processing device configured to execute the instructions stored in the at least one memory, the instructions when executed configured to cause the at least one processing device to:
notifying a verification server when a visitor accesses a web page to enter information into a form;
receiving a reference key comprising a unique identifier from the verification server;
detecting that the visitor has submitted the form with entered information; and
in response to the visitor submitting the form, sending form data to the verification server or at least one interested party, the form data comprising the reference key, at least some of the entered information, and a screenshot of at least one of the web page or the form, the screenshot including at least a portion of the entered information.
Claim 19: store a verification universal resource locator (URL) that includes the reference key.
Instant Claims
Reference Claims
Claim 9: A non-transitory computer readable medium embodying instructions that when executed cause at least one processing device to:
receive a first request associated with a visitor accessing a web page comprising a form into which the visitor is able to enter information using a web browser of the visitor;
in response to the first request, provide a reference key comprising a unique identifier;
collect information about the web page or form and about the visitor or the web browser of the visitor;
generate a certificate containing the collected information and associated with the reference key, the certificate identified using a uniform resource locator (URL); and initiate transmission of the certificate.
Claim 25: A non-transitory computer readable medium embodying instructions that when executed cause at least one processing device to:
notifying a verification server when a visitor accesses a web page to enter information into a form;
receiving a reference key comprising a unique identifier from the verification server;
detecting that the visitor has submitted the form with entered information; and
in response to the visitor submitting the form, sending form data to the verification server or at least one interested party, the form data comprising the reference key, at least some of the entered information, and a screenshot of at least one of the web page or the form, the screenshot including at least a portion of the entered information.
Claim 11: store a verification universal resource locator (URL) that includes the reference key.
Claim Rejections - 35 USC § 101
35 U.S.C. § 101 reads as follows:
Whoever invents or discovers any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof, may obtain a patent therefor, subject to the conditions and requirements of this title.
Claims 1-24 are rejected under 35 U.S.C. § 101 because the claimed invention is directed to non-statutory subject matter.
Step 1
Claims 1-8 is directed to a method, claims 9-16 are directed to an apparatus and claims 17-24 are directed to a non-transitory computer readable medium. Thus, each of the claims falls within one of the four statutory categories as required by Step 1.
Step 2A, Prong One
For step 2A, the claim(s) recite(s) an abstract idea that is a method of organizing human activities. Using claim 9 as a representative example that is applicable to claims 1 and 17, the abstract idea is defined by the elements of the claim in bold:
An apparatus comprising: at least one memory configured to store instructions; and at least one processing device configured to execute the instructions stored in the at least one memory, the instructions when executed configured to cause the at least one processing device to:
receive a first request associated with a visitor accessing a web page comprising a form into which the visitor is able to enter information using a web browser of the visitor;
in response to the first request, provide a reference key comprising a unique identifier;
collect information about the web page or form and about the visitor or the web browser of the visitor;
generate a certificate containing the collected information and associated with the reference key, the certificate identified using a uniform resource locator (URL); and
initiate transmission of the certificate.
The claim recites a process for lead verification including the steps of receiving a request, providing a reference key in response to the request, collecting lead information, generating a certificate including the lead information and the reference key and transmitting the certificate. The claims recite commercial interactions and marketing or sales activities and thus falls under the certain methods of organizing human activity category of abstract ideas identified in the MPEP.
Step 2A, Prong Two
Next, the examiner considers whether the claims recites any additional elements that integrate the abstract idea into a practical application. The claims recite: at least one memory configured to store instructions; and at least one processing device configured to execute the instructions stored in the at least one memory, accessing a web page, using a web browser, a verification server and the use of uniform resource locators. The specification describes these additional elements in conventional terms. [0060] (describes “the computer system 500 includes a processor 502 (which may be referred to as a central processor unit or CPU) that is in communication with memory devices including secondary storage 508, read only memory (ROM) 510,random access memory (RAM) 512,input/output (I/O) device 506, and network connectivity devices 504. The processor 502 may be implemented as one or more CPU chips.”); [064] (describes “The processor 502 executes instructions, codes, computer programs, scripts, as such, for performing the processes discussed in the present disclosure. The instructions, codes, computer programs, or scripts may be accesses from hard disk, floppy disk, optical disk (these various disk based systems may all be considered secondary storage 508),ROM 510,RAM 512, or the network connectivity devices 504.”). The additional elements, do not, either individually or in combination, integrate the abstract idea into a practical application. Specifically, the additional elements are recited at such a high level of generality that they represents no more than mere instructions to apply the judicial exception using generic technology doing no more than what such generic technology routines does. Even when viewed in combination, these additional elements do not integrate the recited judicial exception into a practical application. Therefore, the claim as a whole is not considered to integrate the recited judicial exception into a practical application of the exception.
Step 2B
If the claims are not integrated into a judicial exception, the Examiner must consider whether there is “significantly more” recited in the claim in step 2B. As noted above, the additional elements were found to represent no more than mere instructions to apply the judicial exception on a computer using generic computer components. The analysis under Step 2A, Prong Two is carried through to Step 2B. Even when considered in combination, these additional elements represent mere instructions to apply an exception thus does not provide an inventive concept. The claim is not eligible.
The dependent claims are merely reciting further embellishment of the abstract idea and do not amount to anything that is significantly more than the abstract idea itself. In other words, none of the dependent claims recite an improvement to a technology or technical field or provide any meaningful limitations that, in an ordered combination provide “significantly more;” rather, the dependent claims are merely further reciting features that are just as abstract as those identified in independent claims 1, 9 and 17.
Therefore, Claims 1-24 are directed to non-statutory subject matter and are rejected as ineligible subject matter under 35 U.S.C. § 101.
Claim Rejections - 35 USC § 102
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
The following is a quotation of the appropriate paragraphs of pre-AIA 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(b) the invention was patented or described in a printed publication in this or a foreign country or in public use or on sale in this country, more than one year prior to the date of application for patent in the United States.
Claim(s) 1, 3, 5-9, 11, 13-17, 19, 21-24 is/are rejected under pre-AIA 35 U.S.C. 102(b) as being anticipated by Ganguly (US 2009/0164477).
Claim 1, 9 and 17: Ganguly describes a method comprising:
receiving a first request at a verification server, the first request associated with a visitor accessing a web page comprising a form into which the visitor is able to enter information using a web browser of the visitor; [0007] (describes “a remote computer user or consumer may submit information from their web-browser (or the like), computer or device using data collection forms expressed in a markup language such as HTML, XML or the like (Web-forms). In tie process of displaying the forms a server (Verification-agent) may receive and log the time, IP-address of the user's computer, the URL of the form, tie URL parameters and information in the HTTP request “);[0012] (describes “Still referring to FIG. 1, the provider may select a link (1) on a website (or the like) that causes an electronic lead form 104 to load into the browser or viewer on the computer 102 or device. For example, the provider may "click on" or select a "click to request a customized quotation from a dealer near you link/button" found on a data generator's website. Thereafter, form data for the electronic lead form 104 page, including a unique identifier for the form, may be transmitted from the data generator's server 100 to the provider's computer 102 and then displayed by internet browser or viewer. The unique identifier transmitted with the form data may be a computer code (e.g., html), a digital image, or other electronic tag that is provided in advance to the data generator server 100 by the seal server 106 (discussed below) and then associated with a specific type of electronic lead form 104.”)
in response to the first request, providing a reference key comprising a unique identifier from the verification server [0012] (describes “unique identifier transmitted with the form data may be a computer code (e.g., html), a digital image, or other electronic tag that is provided in advance to the data generator server 100 by the seal server 106”);
collecting, at the verification server, information about the web page or form and about the visitor or the web browser of the visitor[0007] (describes “a remote computer user or consumer may submit information from their web-browser (or the like), computer or device using data collection forms expressed in a markup language such as HTML, XML or the like (Web-forms). In tie process of displaying the forms a server (Verification-agent) may receive and log the time, IP-address of the user's computer, the URL of the form, tie URL parameters and information in the HTTP request “); [0015] (describes “Still referring to FIG. 1, once prepared, the electronic lead form 104 may be submitted/electronically returned (3) to the lead generator's server 100 from the provider's browser/computer 102 as a prepared electronic form. Then, as an optional step, upon submission of the electronic lead form 104 to the lead generator's server 100, the provider's internet browser 102 or device may be automatically redirected (4) to a post-submission webpage 110 that is likewise displayed on the provider's device using a computer code associated with tie form data/electronic lead form.”).;
generating a certificate containing the collected information and associated with the reference key at the verification server, the certificate identified using a uniform resource locator (URL) [0012] (describes “form data for the electronic lead form 104 page, including a unique identifier for the form, may be transmitted from the data generator's server 100 to the provider's computer 102 and then displayed by internet browser or viewer. The unique identifier transmitted with the form data may be a computer code (e.g., html), a digital image, or other electronic tag that is provided in advance to the data generator server 100 by the seal server 106 (discussed below) and then associated with a specific type of electronic lead form 104.”); [0013] (describes the generated form including the URL); [0007] (describes “a remote computer user or consumer may submit information from their web-browser (or the like), computer or device using data collection forms expressed in a markup language such as HTML, XML or the like (Web-forms). In tie process of displaying the forms a server (Verification-agent) may receive and log the time, IP-address of the user's computer, the URL of the form, tie URL parameters and information in the HTTP request “) and
transmitting the certificate from the verification server [0016] (describes transmitting the lead form 104 and the post submission page 110).
3, 11,19. Ganguly describes the method of Claim 1, apparatus of claim 9 and CRM of claim 17. Ganguly further describes wherein the certificate comprises one or more of: a URL associated with the web page or form; a Hypertext Transfer Protocol (HTTP) header for the web page; a timestamp associated with the web browser of the visitor accessing the web page; a network address associated with the web browser of the visitor; or text associated with the form that the visitor populates[0012] (describes “Thereafter, form data for the electronic lead form 104 page, including a unique identifier for the form, may be transmitted from the data generator's server 100 to the provider's computer 102 and then displayed by internet browser or viewer. The unique identifier transmitted with the form data may be a computer code (e.g., html), a digital image.”); [0013] (describes “Tie first query or tracked data may include: 1) a time and date log corresponding to the transmission time of the query (or alternatively the generation of the form on the browser); 2) the IP-address of the provider's computer 102 or device; 3) the URL of the form being prepared (i.e., the a referrer url); 4) the URL parameters and information in the HTTP request; and 5) the unique identifier associated with the form data.”).
5,13, 21. Ganguly describes the method of Claim 1, apparatus of claim 9 and CRM of claim 17. Ganguly further describes wherein providing the reference key comprises: providing a script to the web browser of the visitor; receiving a second request for a verification URL according to the script; and providing the verification URL in response to the second request. [0013] (describes “[0013] Still referring to FIG. 1, a computer code (e.g., html) associated with the form data/electronic lead form 104 may contain a script (or similar electronic prompt) to cause a query to be transmitted (2) from the provider's browser/computer 102 to a remotely located seal server 106, processing unit or like device. Specifically, as the form data/electronic lead form 104 is automatically loaded onto the provider's device/computer 102 by the browser (or concurrently therewith), the form data/electronic lead form 104 (specifically, the code therefore) may prompt the provider's device or browser to transmit a first query or tracked data set to a remote seal server 106. Tie first query or tracked data may include: 1) a time and date log corresponding to the transmission time of the query (or alternatively the generation of the form on the browser); 2) the IP-address of the provider's computer 102 or device; 3) the URL of the form being prepared (i.e., the a referrer url); 4) the URL parameters and information in the HTTP request; and 5) the unique identifier associated with the form data. The seal server may include a seal assignment database 107 that includes a collection of unique electronic data seals or identifiers in the form of a graphic image, and a seal request data log 108 (i.e., a computer readable memory).”); [0020] (describes “exchange 112 (or tie seal server 106) will command or transmit (as necessary) a verification request or query (7).”); [0021] (describes “In response the verification request, the exchange 112 (or the seal server 106) may compare collected data from the data generator's server 100 (e.g., tie sales lead information), against the first query (generated by the electronic lead form) and, if present, the second query (generated by the post-submission page) to determine if a links exist between the data. This comparison may, for example, review the data to determine if the collected data and the first query data include the same I.P. address, or the same unique identifier, or the same time or date stamps. Additionally, or alternatively, the collected data, first and second query data could be reviewed to confirm that the collected data, and first and second query data share the same I.P. address, and if tie first and second query data share associated unique identifiers.[0022] If a link can be established (8) between the collected data in the collected data of the submission log 114, the collected data may be certified though the generation and transmission by the lead exchange 112 or seal server 106 of a notice that includes a source verification attestation (e.g., a Yes). Alternatively where a link cannot be established, made (9) the data may not be certified and may include an alert (i.e., a No) that the source cannot be verified.”); [0016] (describes “ It will also be appreciated that the second query or tracked data set may contain the same type of data that is associated with the first query.”).
6, 14, 22. Ganguly describes the method of Claim 1, apparatus of claim 9 and CRM of claim 17. Ganguly further describes wherein receiving the first request comprises receiving the first request from a lead verification service script executed by the web browser of the visitor. [0013] (describes “[0013] Still referring to FIG. 1, a computer code (e.g., html) associated with the form data/electronic lead form 104 may contain a script (or similar electronic prompt) to cause a query to be transmitted (2) from the provider's browser/computer 102 to a remotely located seal server 106, processing unit or like device. Specifically, as the form data/electronic lead form 104 is automatically loaded onto the provider's device/computer 102 by the browser (or concurrently therewith), the form data/electronic lead form 104 (specifically, the code therefore) may prompt the provider's device or browser to transmit a first query or tracked data set to a remote seal server 106. Tie first query or tracked data may include: 1) a time and date log corresponding to the transmission time of the query (or alternatively the generation of the form on the browser); 2) the IP-address of the provider's computer 102 or device; 3) the URL of the form being prepared (i.e., the a referrer url); 4) the URL parameters and information in the HTTP request; and 5) the unique identifier associated with the form data. The seal server may include a seal assignment database 107 that includes a collection of unique electronic data seals or identifiers in the form of a graphic image, and a seal request data log 108 (i.e., a computer readable memory).”); [0020] (describes “exchange 112 (or tie seal server 106) will command or transmit (as necessary) a verification request or query (7).”).
7, 15, 23. Ganguly describes the method of Claim 1, apparatus of claim 9 and CRM of claim 17. Ganguly further describes further comprising: providing verification data from the verification server; and receiving additional data that is generated based on the verification data [0021] (describes “In response the verification request, the exchange 112 (or the seal server 106) may compare collected data from the data generator's server 100 (e.g., tie sales lead information), against the first query (generated by the electronic lead form) and, if present, the second query (generated by the post-submission page) to determine if a links exist between the data. This comparison may, for example, review the data to determine if the collected data and the first query data include the same I.P. address, or the same unique identifier, or the same time or date stamps. Additionally, or alternatively, the collected data, first and second query data could be reviewed to confirm that the collected data, and first and second query data share the same I.P. address, and if tie first and second query data share associated unique identifiers.”); [0022] (describes “If a link can be established (8) between the collected data in the collected data of the submission log 114, the collected data may be certified though the generation and transmission by the lead exchange 112 or seal server 106 of a notice that includes a source verification attestation (e.g., a Yes). Alternatively where a link cannot be established, made (9) the data may not be certified and may include an alert (i.e., a No) that the source cannot be verified.”).
8, 16, 24. Ganguly describes the method of Claim 1, apparatus of claim 9 and CRM of claim 17. Ganguly further describes further comprising: receiving a second request containing the URL; wherein transmitting the certificate comprises transmitting the certificate in response to the second request.[0017] (describes “[0017] The seal server 106 may log the second query, similar to the first query, and transmit a seal for the post-submission page back to the provider's browser/computer 102. However, in logging the second query, the second query will be associated or link with the first query based, for example, on a comparison of the unique identifiers transmitted with the first and second queries, the I.P. address of the provider's computer as indicated in the queries, or like data. Notably, the unique identifiers used in the forms, pages and queries may be represented by two different sets of computer code that are each associated with a particular form (104) or page (110), and that are also specifically paired to one another. This pairing of the unique identifiers will, of course, be advantageous for purposes of later verification of form data.”).
Claim Rejections - 35 USC § 103
The following is a quotation of pre-AIA 35 U.S.C. 103(a) which forms the basis for all obviousness rejections set forth in this Office action:
(a) A patent may not be obtained though the invention is not identically disclosed or described as set forth in section 102, if the differences between the subject matter sought to be patented and the prior art are such that the subject matter as a whole would have been obvious at the time the invention was made to a person having ordinary skill in the art to which said subject matter pertains. Patentability shall not be negated by the manner in which the invention was made.
The factual inquiries for establishing a background for determining obviousness under pre-AIA 35 U.S.C. 103(a) are summarized as follows:
1. Determining the scope and contents of the prior art.
2. Ascertaining the differences between the prior art and the claims at issue.
3. Resolving the level of ordinary skill in the pertinent art.
4. Considering objective evidence present in the application indicating obviousness or nonobviousness.
This application currently names joint inventors. In considering patentability of the claims under pre-AIA 35 U.S.C. 103(a), the examiner presumes that the subject matter of the various claims was commonly owned at the time any inventions covered therein were made absent any evidence to the contrary. Applicant is advised of the obligation under 37 CFR 1.56 to point out the inventor and invention dates of each claim that was not commonly owned at the time a later invention was made in order for the examiner to consider the applicability of pre-AIA 35 U.S.C. 103(c) and potential pre-AIA 35 U.S.C. 102(e), (f) or (g) prior art under pre-AIA 35 U.S.C. 103(a).
Claim 2, 10 and 18 is rejected under pre-AIA 35 U.S.C. 103(a) as being unpatentable over Ganguly as applied to claim 1, 9 and 17 above, and further in view of Gilbert at al., (US 2006/0020611).
2, 10 and 18. Ganguly describes the method of Claim 1. Ganguly further describes a certificate that may include personal information entered by the provider. [0019] (describes “The collected or prepared data concerning the provider may include personal, business information and financial information for the provider.”). Ganguly does not expressly describe wherein the certificate lacks personally identifiable information about the visitor.
Gilbert, which relates to a system and method that performs a de-intidentification process to maintain records without exposing personally identifying information teaches that it was known in the art, at the time of the invention, to remove personally identifiable information from collected data to maintain privacy. [0015] (describes “a method for transforming personal identifying information to facilitate protection of privacy interests while allowing use of non-personally identifying information is provided. Data for an individual including personally identifying information is de-identified or depersonalized at a client computer to create anomimity with respect to such record.”).
It would have been obvious, to one having ordinary skill in the art at the time of the invention, to modify Ganguly to remove some of the personal data collected for the expected benefits described in Gilbert. Gilbert notes that the “actual and potential impact on the lives of individuals based on this collected information can be harmful, ranging from annoyance of unsolicited email to profound hardships of employment denial. Therefore, there exists a need to be able to collect and process data records without exposing individuals to losses of privacy.” [0006-07].
Claim 4, 12 and 20 is rejected under pre-AIA 35 U.S.C. 103(a) as being unpatentable over Ganguly as applied to claim 1, 9 and 17 above, and further in view of van Duyne et al., (US 6,859,784).
4, 12 and 20. Ganguly describes the method of Claim 1. Ganguly further describes wherein the certificate comprises a number of digital elements including a digital image. [0014] (describes an “image” on the lead form). Ganguly does not expressly describe screenshot of at least one of the web page or the form, the screenshot including at least a portion of the information entered by the visitor.
Van Duyne, which relates to a system and method for gathering research data for a website, including marketing data, teaches the concept of collecting screen shots of data entries on websites for marketing purposes. [Col. 2, lines 18-26] (describes “Participant responses can be recorded when gathering participant research data. The participant responses can be selected from the group of audio, gestural and keystroke responses. A screenshot of a user interface presented to the participant can be captured for one or more of the participant responses.”).
It would have been obvious, to one having ordinary skill in the art at the time of the invention, to modify Ganguly to incorporate the concept of screen grabbing data input as described in van Duyne and add the screen grab to the collection of data verifying authenticity of the sales lead as described in Ganguly. Ganguly recognizes the need for verifying the origin of remotely prepared data “so that a purchaser of the data associated with the prepared form may have increased confidence in the legitimacy of that data.” [Ganguly, 0002]. It would have been obvious to incorporate the teachings of van Duyne in order to verify the origin of remotely prepared data thereby “increasing the confidence in the legitimacy of that data.”
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to JULIE MEYERS SHANKER whose telephone number is (571)270-5460. The examiner can normally be reached Monday and Tuesday 10:00am- 6:00pm EST.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Nate C Uber can be reached at (571) 270-3923. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
JULIE MEYERS. SHANKER
Examiner
Art Unit 3689
/JULIE M SHANKER/Primary Examiner, Art Unit 3626