Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Claims 1 – 9 are pending in this application.
Priority
Receipt is acknowledged of certified copies of papers submitted under 35 U.S.C. 119(a)-(d), which papers have been placed of record in the file.
Information Disclosure Statement
The information disclosure statements (IDS) submitted on 12/11/2024 was filed in compliance with the provisions of 37 CFR 1.97 and 1.98. Accordingly, the information disclosure statement is being considered by the examiner.
Applicants have not provided an explanation of relevance of cited document(s) discussed below.
Nomura (U.S PG Publication No. 2010/0085599 A1) teaches a method for configuring a second computing device to communicate with a printer (i.e., configuring a client terminal 101/102 to communicate with a printer 104/105, ¶0041, ¶0050), comprising: creating a printer definition for the printer, wherein the printer definition comprises a network address, a reference to a printer driver, and a reference to a printer profile (i.e., creating a printer definition (file) for said printer, wherein said printer definition (file) includes IP address, details to a printer driver, and details to printer information, ¶0050 - ¶0051, ¶0066, Fig. 10, Fig. 21); and sending an installer to the second computing device, wherein the installer installs the printer driver and configures the computing device to communicate with the printer using the network address, the printer driver, and the printer profile (e.g., providing an installer to said client terminal, wherein the client terminal can installs the printer driver and configures said client terminal to communicate with said printer using IP address, printer drive and other printer information, ¶0050, ¶0053, ¶0066).
Neville (U.S PG Publication No. 2017/0046147 A1) teaches: The steps are performed via a website (e.g., since there is a web browser and a web server, the use of these features in a manufacturer or a cloud based software repository is considered as website, ¶0012, ¶0004); sending an email that includes a link with an install uniform resource identifier (URI) associated with the printer definition (e.g. send an electronic alert (email, text, etc.) to an user with a list of network printer devices that need to be updated with links (URLs) to the updated firmware files based on characteristics of the network printer devices, ¶0020, ¶0025, ¶0053), wherein the install URI specifies an access mechanism and a location for downloading a printer installer (e.g., wherein Fig. 5(b) shows at least an activated icon in order to allow the user to download a file by using a link, ¶0044 - ¶0047, ¶0053); receiving an indication that the emailed link with the install URI has been activated by the computing device (e.g., from said electronic alert, said activated icon can be ready to be motivated by a computer (e.g., smartphone, PDA, tablet computer, smart watch, etc., ¶0053 - ¶0055); the printer installer to install the printer driver and configure the computing device to communicate with the printer based on the created printer definition in response to receiving the indication that the emailed link with the install URI has been activated (e.g., after pressing the activated icon that corresponds to the link, an installation process is executed by installing a driver so that the network printer device and the client system accessible by a user, based on printer information, ¶0038 - ¶0039, ¶0044 - ¶46).
Xu (U.S PG Publication No. 2013/0047149 A1) teaches: dynamically generating, by a printer cloud engine module on a server, an installer in response to receiving the indication that the install URI has been activated (Xu: e.g., dynamically generating (or converting), from the prepared software packages 110/111 into repositories 121/122 on the server side in which are uploaded by a developer 103, an installer in response to a button (input/request), Fig. 11, ¶0022, ¶0079, ¶0115 - ¶0118, ¶0165), wherein the printer cloud engine module is a software-as-a-service (SaaS) module that is separate from a printer cloud administration module on the server (e.g., Since SaaS is a software delivery model in which a third-party provider hosts applications and makes them available to customers over the Internet; Xu teaches said prepared software packages 110/111 into repositories 121/122 are configured to provide services to users when a user wants to start/launch or run the drivers, ¶0019, ¶0041, ¶0055, ¶0110; and it’s also separated from an “administration” for the purpose of set/deploy/modifies service/privileges to certain user(s), ¶0084, ¶0103).
Bhogal et al. (U.S PG Publication No. 2014/0089531 A1) teaches a method for configuring, via a server, a second computing device to communicate with a printer (e.g., configuring, via a server computer, a client computer 105a to communicate with a peripheral device 940a, Fig. 1), comprising: receiving, at the website, a printer profile uploaded from a first computing device (e.g., upon collecting information about configuration from at least each of client computers (105b – 105c) and setting parameters that define a profile from the at least each of said client computer (105b – 105c), sends profile to said server computer, Fig. 2B, ¶0032 - ¶0033), the printer profile being configured on the first computing device based on a printer driver installed on the first computing device (e.g., said profile contains information about device driver installation(s) and configuration from the at least said client computer (105b – 105c), ¶0028, ¶0032), wherein the website is hosted by a server that is accessible by the first computing device via the Internet (e.g., wherein said server computer is a web server, in which can be configured to purchase a peripheral device over the Internet (¶0039) or download using URL (¶0038), that is accessible by the client computer (105b – 105c) via the network 102 or over the Internet, Fig. 1, ¶0039; In addition, to support the functionality: Bhogal further teaches generating, via said server, a recommendation for the peripheral device, where said recommendation comprises compatibility of device drivers installed from at least client computers (105b – 105c); and information collected from the profile, ¶0023, ¶0026, ¶0033, Fig. 2A & Fig. 2B; said recommendation generated is sent to the end-user (of any client computers); said recommendation may include a download location (e.g., uniform resource locators) of versions of device drivers, ¶0038, ¶0043); and when creating a definition for the printer, wherein the definition comprises a reference to the printer driver installed on the first computing device, and a reference to the printer profile (e.g., At time of collecting information about configuration of at least the client computers 105b/105c and setting parameters, generate a recommendation, as a definition, for the peripheral device (e.g., a computer printer), where said recommendation comprises at least a reference of successful driver(s) installed in other client computers 105b/105c, and a reference to the profile, said recommendation is further configured to be sent to the client computer so that the user can download and install a compatible or successful driver, ¶0024 - ¶0027, ¶0032, ¶0037 - ¶0038).
Kemp et al. (U.S PreGrant Publication No. 2003/0200291 A1) teaches a method for configuring, via a website, a second computing device to communicate with a printer (e.g., configuring, via a web, a workstation to communicate with a printer, ¶0022), comprising: receiving, at the website, a printer profile and a printer driver uploaded from a first computing device, the received printer profile comprising printer settings configured on the first computing device using the printer driver installed on the first computing device (e.g., while accessing a website, a printer configuration and a printer driver is obtained from a remote device (or server), ¶0005, ¶0009, ¶0032);
creating, via the website, a printer definition for the printer (e.g., a database of printer configuration information and print drivers can be maintained on the remote server such that they can be readily accessed anytime an instance of a locally managed printer is to be created; an identification information of the printer may be a network address of the printer, such as an IP address, a printer's name, a DNS name or a NetBios name; and In a html page, a code for a hyperlink includes a call for an active server page and parameters associated with the printer, such as the printer's name, IP address and device type", ¶0032 and ¶0034);
sending a printer installer to the second computing device (e.g., when a link is pressed (clicked), the installer is sent (downloaded) to the workstation as a response, ¶0005, ¶0008, ¶0033),
wherein the printer installer installs the printer driver and configures the second computing device to communicate with the printer using the network address, the printer driver, and the received printer profile (e.g., installs the printer driver and configures the workstation to communicate with the printer using the network address, the printer driver and the received configuration, ¶0010, ¶0022).
Noguchi et al. (U.S PreGrant Publication No. 2009/0201547 A1) teaches: downloading automatically, without an action by an end user, a printer installer to the second computing device, wherein the printer installer automatically installs the printer driver (Noguchi: e.g., a server 300 regularly access an in-house download server that store drivers (in order to compare versions); and when there is a printer driver that needs to be updated, the server, by itself, automatically download and install print driver, ¶0212).
Matsushita et al. (U.S PreGrant Publication No. 2009/0059272 A1) broadly teaches: a print driver is automatically installed from the server without using a print server (e.g., shows a system including at least a print server 18A/B, a printer auto installation tool 16, wherein a print driver can be automatically downloaded and installed from said printer auto installation tool 16 to a client terminal not the print server 18A/B itself, ¶0044, ¶0048, ¶0050 - ¶0054).
Attia (U.S PreGrant Publication No. 2015/0239270 A1, in the current References Cited) teaches a website configured for SaaS of printer files for driving printer(s) (¶0036).
Double Patenting
A rejection based on double patenting of the “same invention” type finds its support in the language of 35 U.S.C. 101 which states that “whoever invents or discovers any new and useful process... may obtain a patent therefor...” (Emphasis added). Thus, the term “same invention,” in this context, means an invention drawn to identical subject matter. See Miller v. Eagle Mfg. Co., 151 U.S. 186 (1894); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); and In re Ockert, 245 F.2d 467, 114 USPQ 330 (CCPA 1957).
A statutory type (35 U.S.C. 101) double patenting rejection can be overcome by canceling or amending the claims that are directed to the same invention so they are no longer coextensive in scope. The filing of a terminal disclaimer cannot overcome a double patenting rejection based upon 35 U.S.C. 101.
Claims 1 - 9 are rejected under 35 U.S.C. 101 as claiming the same invention as that of at least claims 1 – 4 and 6 - 10 of prior U.S. Patent No. 12,131,082 B2. This is a statutory double patenting rejection.
It is clear that all the elements of the parent claim 1 is to be found in instant claim (as the parent claim 1 fully encompasses the instant claim 1).
No difference between the instant application claim 1 and the patent claim 1 is found. However, the invention of instant claim 1 is in effect a “species” of the “generic” invention of the parent application claim 1.
It has been held that the generic invention is “anticipated” by the “species”. See In re Goodman, 29 USPQ2d 2010 (Fed. Cir. 1993). Since parent application claim 1 is anticipated by claim 1 of the instant application, it is not patentably distinct from claim 1 the instant claims.
Below is a side-by-side comparison (bolded where significant different, and underlined where limitation is mentioned somewhere):
Instant Application 18/928924
12,131,082 B2
Claim 1
A method for configuring printing, comprising:
creating, via a website configured for software-as-a-service (Saas) deployment of printer drivers,
a printer definition for a printer,
wherein the printer definition comprises a reference to a printer driver uploaded from a first computing device; and
sending a printer installer generated based on the printer definition to a second computing device,
wherein the printer installer installs the printer driver and configures the second computing device to communicate with the printer using the printer driver.
Claim 1
A method for configuring printing, comprising:
creating, via a website configured for software-as-a-service (Saas) deployment of printer drivers and printer profiles,
a printer definition for a printer,
wherein the printer definition comprises a reference to a printer driver uploaded from a first computing device, and a reference to a printer profile uploaded from the first computing device; and
sending a printer installer generated based on the printer definition to a second computing device,
wherein the printer installer installs the printer driver and configures the second computing device to communicate with the printer using the printer driver and the printer profile.
Claim 2
The method of claim 1, further comprising:
sending an install uniform resource identifier (URI) associated with the created printer definition; and receiving an indication that the install URI has been activated by the second computing device.
Claim 2
The method of claim 1, further comprising:
sending an install uniform resource identifier (URI) associated with the created printer definition; and receiving an indication that the install URI has been activated by the second computing device.
Claim 3
The method of claim 1, wherein creating the printer definition comprises: receiving, via the website, a network address of the printer; receiving, via the website, the printer driver for the printer; and receiving, via the website, a printer profile for the printer.
Claim 3
The method of claim 1, wherein creating the printer definition comprises: receiving, via the website, a network address of the printer; receiving, via the website, the printer driver for the printer; and receiving, via the website, the printer profile for the printer.
Claim 4
The method of claim 1, wherein the printer driver is stored in a repository, and wherein the reference to the printer driver uploaded from the first computing device uniquely identifies the printer driver in the repository.
Claim 4
The method of claim 1, wherein the printer driver is stored in a repository, and wherein the reference to the printer driver uploaded from the first computing device uniquely identifies the printer driver in the repository.
Claim 5
The method of claim 1, wherein configuring the second computing device to communicate with the printer comprises: creating a network printer port based on a network address; and configuring settings based on a printer profile.
Claim 6
The method of claim 1, wherein configuring the second computing device to communicate with the printer comprises: creating a network printer port based on a network address; and configuring settings based on the printer profile.
Claim 6
An electronic device for configuring printing, comprising: at least one processor configured to:
create, via a website configured for software-as-a-service (Saas) deployment of printer drivers,
a printer definition for a printer,
wherein the printer definition comprises a reference to a printer driver uploaded to the website; and
send a printer installer generated based on the printer definition to a second computing device, wherein the printer installer installs the printer driver and configures the second computing device to communicate with the printer using the printer driver.
Claim 7
An electronic device for configuring printing, comprising: at least one processor configured to:
create, via a website configured for software-as-a-service (Saas) deployment of printer drivers and printer profiles,
a printer definition for a printer,
wherein the printer definition comprises a reference to a printer driver uploaded to the website, and a reference to a printer profile uploaded to the website; and
send a printer installer generated based on the printer definition to a second computing device, wherein the printer installer installs the printer driver and configures the second computing device to communicate with the printer using the printer driver and the printer profile.
Claim 7
The electronic device of claim 6, wherein the at least one processor is further configured to: send an install uniform resource identifier (URI) associated with the created printer definition; and receive an indication that the install URI has been activated by the second computing device.
Claim 8
The electronic device of claim 7, wherein the at least one processor is further configured to: send an install uniform resource identifier (URI) associated with the created printer definition; and receive an indication that the install URI has been activated by the second computing device.
Claim 8
The electronic device of claim 6, wherein the at least one processor is further configured to: receive, via the website, the printer driver for the printer; and receive, via the website, a printer profile for the printer.
Claim 9
The electronic device of claim 7, wherein the at least one processor is further configured to: receive, via the website, the printer driver for the printer; and receive, via the website, the printer profile for the printer.
Claim 9
The electronic device of claim 6, wherein the printer driver is stored in a repository, and wherein the reference to the printer driver uniquely identifies the printer driver in the repository.
Claim 10
The electronic device of claim 7, wherein the printer driver is stored in a repository, and wherein the reference to the printer driver uniquely identifies the printer driver in the repository.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to JUAN M GUILLERMETY whose telephone number is (571)270-3481. The examiner can normally be reached 9:00AM - 5:00PM.
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, Benny Q TIEU can be reached at 571-272-7490. 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.
/JUAN M GUILLERMETY/Primary Examiner, Art Unit 2682
Prosecution Insights