DETAILED ACTION
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 .
1. This is in response to communication filed on 3/05/25 in which claims 1-21 are pending.
Claim Rejections - 35 USC § 102
2. The following is a quotation of the appropriate paragraphs of 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 –
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
3. Claims 1, 2-4, 6-11, 13-18, 20-21 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by U.S. Publication No. 2017/0116349 to Steiner et al.
a. As per claim 1, Steiner et al teaches a computer-implemented method comprising:
receiving a hosting request to host a website on a virtual site hosting subnetwork, wherein the hosting request includes a web Document Object Model (DOM) and one or more assets associated with the web DOM, and wherein the website is implemented using the web DOM (See paragraph [0029-0030 and 0075], The subsystem 316 can evaluate this information and construct a set of metadata representing interactions that can be performed on the mirage image and this data can be transmitted along with the mirage image to facilitate fast navigation off the page or facilitate user interaction that can easily be replayed in the context of the full DOM once available); provisioning a hosted website instance for the website, wherein the hosted website instance provides the web DOM and the one or more assets through the virtual site hosting subnetwork (See paragraph [0099-0103]); receiving a website access request for accessing the website, wherein the website access request is received through a website rendering instance implemented through a virtual site rendering subnetwork (See paragraph [0039], a client device typically requests an HTML document at a given URL and receives the HTML document from a content server, such as server 102 in FIG. 1. The HTML contains references to embedded objects at other URLs, e.g., an <img> with a src attribute pointing to a URL. The client requests the embedded objects, and then renders the page (although rendering may begin before all objects are retrieved); encoding the web DOM and the one or more assets to generate data usable to generate a graphical facsimile of the website, wherein data is generated through the website rendering instance, and wherein the website rendering instance obtains the web DOM and the one or more assets from the hosted website instance (See paragraph [0056, 0060-0061], the subsystem 316 analyzes the web page snapshots in the category graphically. This analysis is to identify pixels that are “dynamic” versus pixels that are identical across snapshots (“static”). (This step could be accomplished with a tool such as ImageMagick, part of a Linux distribution, or similar technology); and transmitting data to fulfill the website access request, wherein the data is transmitted through the website rendering instance, and wherein when the data is received, the data is decoded to generate and present the graphical facsimile of the website (See paragraph [0090 and 0095]).
b. As per claim 8, Buzbee et al teaches a system, comprising: one or more processors (See paragraph [0126]); and memory storing thereon instructions that, as a result of being executed by the one or more processors, cause the system to: receive a hosting request to host a website on a virtual site hosting subnetwork, wherein the hosting request includes a web Document Object Model (DOM) and one or more assets associated with the web DOM, and wherein the website is implemented using the web DOM (See paragraph [0029-0030], The subsystem 316 can evaluate this information and construct a set of metadata representing interactions that can be performed on the mirage image and this data can be transmitted along with the mirage image to facilitate fast navigation off the page or facilitate user interaction that can easily be replayed in the context of the full DOM once available); provision a hosted website instance for the website, wherein the hosted website instance provides the web DOM and the one or more assets through the virtual site hosting subnetwork (See paragraph [0099-0103]); receive a website access request for accessing the website, wherein the website access request is received through a website rendering instance implemented through a virtual site rendering subnetwork (See paragraph [0039], a client device typically requests an HTML document at a given URL and receives the HTML document from a content server, such as server 102 in FIG. 1. The HTML contains references to embedded objects at other URLs, e.g., an <img> with a src attribute pointing to a URL. The client requests the embedded objects, and then renders the page (although rendering may begin before all objects are retrieved); encode the web DOM and the one or more assets to generate data usable to generate a graphical facsimile of the website, wherein the data is generated through the website rendering instance , and wherein the website rendering instance obtains the web DOM and the one or more assets from the hosted website instance (See paragraph [0056, 0060-0061], (See paragraph [0056, 0060-0061], the subsystem 316 analyzes the web page snapshots in the category graphically. This analysis is to identify pixels that are “dynamic” versus pixels that are identical across snapshots (“static”). (This step could be accomplished with a tool such as ImageMagick, part of a Linux distribution, or similar technology); and transmit data to fulfill the website access request, wherein the data is transmitted through the website rendering instance, and wherein when the data is received, the data is decoded to generate and present the graphical facsimile of the website (See paragraph [0090-0095]).
c. As per claim 15, Steiner et al teaches a non-transitory, computer-readable storage medium storing thereon executable instructions that, as a result of being executed by one or more processors of a computer system, cause the computer system to: receive a hosting request to host a website on a virtual site hosting subnetwork, wherein the hosting request includes a web Document Object Model (DOM) and one or more assets associated with the web DOM, and wherein the website is implemented using the web DOM (See paragraph [0029-0030], The subsystem 316 can evaluate this information and construct a set of metadata representing interactions that can be performed on the mirage image and this data can be transmitted along with the mirage image to facilitate fast navigation off the page or facilitate user interaction that can easily be replayed in the context of the full DOM once available); provision a hosted website instance for the website, wherein the hosted website instance provides the web DOM and the one or more assets through the virtual site hosting subnetwork (See paragraph [0099-0103]); receive a website access request for accessing the website, wherein the website access request is received through a website rendering instance implemented through a virtual site rendering subnetwork (See paragraph [0039], a client device typically requests an HTML document at a given URL and receives the HTML document from a content server, such as server 102 in FIG. 1. The HTML contains references to embedded objects at other URLs, e.g., an <img> with a src attribute pointing to a URL. The client requests the embedded objects, and then renders the page (although rendering may begin before all objects are retrieved); encode the web DOM and the one or more assets to generate data usable to generate a graphical facsimile of the website, wherein the data is generated through the website rendering instance, and wherein the website rendering instance obtains the web DOM and the one or more assets from the hosted website instance (See paragraph [0056, 0060-0061], the subsystem 316 analyzes the web page snapshots in the category graphically. This analysis is to identify pixels that are “dynamic” versus pixels that are identical across snapshots (“static”). (This step could be accomplished with a tool such as ImageMagick, part of a Linux distribution, or similar technology); and transmit data to fulfill the website access request, wherein the data is transmitted through the website rendering instance, and wherein when the data is received, the data is decoded to generate and present the graphical facsimile of the website (See paragraph [0090-0095]). .
d. As per claims 2, 9 and 16, Steiner et al teaches the claimed invention as described above. Furthermore, Steiner et al teaches wherein the hosting request is transmitted through a command line interface (CLI) call to an application programming interface (API) associated with the virtual site hosting subnetwork (See paragraph [0104]).
e. As per claims 3, 10 and 17, Steiner et al teaches the claimed invention as described above. Furthermore, Steiner et al teaches wherein the web DOM and the one or more assets are not accessible through the website rendering instance (See paragraph [0089, 0094 and 0099]).
f. As per claims 4, 11 and 18, Steiner et al teaches the claimed invention as described above. Furthermore, Steiner et al teaches wherein the data is generated using a Web Real-Time Communication (WebRTC) protocol, wherein the data includes a set of pixels generated using the WebRTC protocol, and wherein the set of pixels is used to generate the graphical facsimile of the website (See paragraph 0107]).
g. As per claims 6, 13 and 20, Steiner et al teaches the claimed invention as described above. Furthermore, Steiner et al teaches transmitting a set of executable instructions that, as a result of being executed, cause an option to inspect the graphical facsimile of the website to become disabled (See paragraph [0119 and 0123]).
h. As per claims 7, 14 and 21, Steiner et al teaches the claimed invention as described above. Furthermore, Steiner et al teaches wherein the web DOM and the one or more assets are encoded according to a custom data structure, and wherein the custom data structure is indicated through the hosting request (See paragraph [0096])..
Claim Rejections - 35 USC § 103
4. 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 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention 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 35 U.S.C. 103 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 the examiner presumes that the subject matter of the various claims was commonly owned as of the effective filing date of the claimed invention(s) absent any evidence to the contrary. Applicant is advised of the obligation under 37 CFR 1.56 to point out the inventor and effective filing dates of each claim that was not commonly owned as of the effective filing date of the later invention in order for the examiner to consider the applicability of 35 U.S.C. 102(b)(2)(C) for any potential 35 U.S.C. 102(a)(2) prior art against the later invention.
6. Claims 5, 12 and 19 are rejected under 35 U.S.C. 103 as being unpatentable over in view of U.S. Publication No. 2017/0116349 to Steiner et al in view of U.S. Publication 2016/0234330 to Popowitz et al.
a. As per claims 5, 12 and 19, Steiner et al teaches the claimed invention as described above. However, Steiner et al fails to teach further comprising: identifying a Uniform Resource Identifier (URI) associated with the website, wherein the URI is identified based on the hosting request; and updating one or more DNS servers to map the URI to the website rendering instance.
Popowitz et al teaches : identifying a Uniform Resource Identifier (URI) associated with the website, wherein the URI is identified based on the hosting request; and updating one or more DNS servers to map the URI to the website rendering instance (See paragraph [0055-0056]).
It would have been obvious to one with ordinary skill in the art to incorporate the teaching of Popowitz et al in the claimed invention of Steiner et al in order to in order to insert reverse-proxy into the request path made to the website.
Conclusion
7. The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
U.S. Publication No. 2012/0323794 to Livshits teaches enable personalization in a privacy-conscious manner.
U.S. Publication No. 2014/0047413 to Sheive et al teaches Developping, modifying and using Applications.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to DJENANE BAYARD whose telephone number is (571)272-3878. The examiner can normally be reached 9-5.
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, John Follansbee can be reached at (571)272-3964. 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.
/DJENANE M BAYARD/Primary Examiner, Art Unit 2444
Prosecution Insights