DETAILED ACTION
Claims 1-20 are examined and pending.
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 .
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 claims at issue 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); and 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 a nonstatutory double patenting ground provided the reference application or patent either is shown to be commonly owned with this 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 §§ 706.02(l)(1) - 706.02(l)(3) 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 USPTO Internet website contains terminal disclaimer forms which may be used. Please visit www.uspto.gov/forms/. The 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 http://www.uspto.gov/patents/process/file/efs/guidance/eTD-info-I.jsp.
Claims 1, 2, 5-13 and 15-20 rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-12 of U.S. Patent No. 12,348,578. Although the claims at issue are not identical, they are not patentably distinct from each other because all the claimed limitations recited in the present application are transparently found in the Patent 12,348,578 with obvious wording variations. A comparison of the claims are shown below:
Pending Application 19,229,819
Patent 12,348,578
1. A system comprising: a processor configured to execute a web browser and a local server program; a computer readable memory coupled to the processor, the computer readable memory comprising a web page comprising executable instructions, the web page configured to: generate, by the web browser of an operating system and via executable instructions of the web page, connection configuration data usable by a local server program instance registered with the operating system, wherein the connection configuration data comprises: a port on which the local server program instance is to listen for a connection request while the port is randomly selected by a web page; a randomly generated launch id; a port number corresponding to the port; and a protocol specific to the web browser; complete the connection, wherein the connection is usable for bi- directional communication between the web browser and the server program instance; receive a connection configuration launch id and a connection configuration port number for a port from the operating system based on a request by the web page; create a server socket instance bound to a loopback address; listen on the server socket instance for the connection request on the port; extract a connection request launch id from the connection request; and based on a determination that the connection configuration launch id and connection request launch id match, accept the connection request, wherein the port number is a random port number generated by the web page and the connection configuration launch id and connection request launch id comprise a string randomly generated by the web page.
2. The system of Claim 1, wherein the processor is further configured to launch the local server program instance by using the connection configuration data.
9. The system of Claim 1, wherein the local server program is executable to: receive a connection configuration launch id and a connection configuration port number for a port from the operating system based on a request by the web page; create a server socket instance bound to a loopback address; listen on the server socket instance for the connection request on the port; extract a connection request launch id from the connection request; based on a determination that the connection configuration launch id and connection request launch id match, accept the connection request, wherein the port number is a random port number generated by the web page and the connection configuration launch id and connection request launch id comprise a string randomly generated by the web page.
1. A system comprising: a processor configured to execute a web browser and a local server program; a computer readable memory coupled to the processor, the computer readable memory comprising a web page comprising executable instructions, the web page configured to: generate, by the web browser of an operating system and via executable instructions of the web page, connection configuration data usable by a local server program instance registered with the operating system, wherein the connection configuration data comprises: a port on which the local server program instance is to listen for a connection request while the port is randomly selected by a web page; a randomly generated launch id; a port number corresponding to the port; and a protocol specific to the web browser; launch, by the operating system, the local server program instance by using the connection configuration data, wherein the launching of the local server program instance further comprises associating the local server program instance with the protocol specific to the web browser; send the connection data as a connection request originating from the web page using the protocol, wherein the connection request is sent to the local server program instance to establish a connection between the web browser and the server program instance; based on an acceptance of the connection request by the server program instance, complete the connection, wherein the connection is usable for bi-directional communication between the web browser and the server program instance; receive a connection configuration launch id and a connection configuration port number for a port from the operating system based on a request by the web page; create a server socket instance bound to a loopback address; listen on the server socket instance for the connection request on the port; extract a connection request launch id from the connection request; and based on a determination that the connection configuration launch id and connection request launch id match, accept the connection request, wherein the port number is a random port number generated by the web page and the connection configuration launch id and connection request launch id comprise a string randomly generated by the web page.
5. The system of Claim 1, wherein the web page is configured to compose a uniform resource locator (URL) including the port number on a local host and the launch id and create a client socket instance using the URL.
2. The system of claim 1, wherein the web page is configured to compose a uniform resource locator (URL) including the port number on a local host and the launch id and create a client socket instance using the URL.
6. The system of Claim 5, wherein the client socket instance is a client WebSocket instance.
3. The system of claim 2, wherein the client socket instance is a client WebSocket instance.
7. The system of Claim 6, wherein the connection request is an HTTP GET request that includes the randomly generated launch id.
4. The system of claim 3, wherein the connection request is an HTTP GET request that includes the randomly generated launch id.
8. The system of Claim 1, wherein the web page is configured to launch the local server program instance and provide the connection data to the local server program instance by sending a launch request to the operating system to launch the local server program instance, the launch request including an indicator of the protocol that the local server program is registered to handle, the port number to be passed to the local server program instance and the launch id to be passed to the local server program instance.
5. The system of claim 1, wherein the web page is configured to launch the local server program instance and provide the connection data to the local server program instance by sending a launch request to the operating system to launch the local server program instance, the launch request including an indicator of the protocol that the local server program is registered to handle, the port number to be passed to the local server program instance and the launch id to be passed to the local server program instance.
10. The system of Claim 9, wherein the local server program is executable to extract the connection configuration launch id and connection configuration port number from command line attributes from the operating system.
6. The system of claim 1, wherein the local server program is executable to extract the connection configuration launch id and connection configuration port number from command line attributes from the operating system.
11. A method comprising: executing, by a processor, a web browser; rendering, by the web browser of an operating system, a web page, the web page comprising executable instructions; generating, by the web browser via executable instructions of the web page, connection configuration data usable by a local server program instance registered with the operating system, wherein the connection configuration data comprises: a port on which the local server program instance is to listen for a connection request while the port is randomly selected by a web page; a randomly generated launch id; a port number corresponding to the port; and a protocol specific to the web browser; completing the connection, wherein the connection is usable for bi-directional communication between the web browser and the server program instance; receiving a connection configuration launch id and a connection configuration port number for a port from the operating system based on a request by the web page; creating a server socket instance and binding the server socket instance to a loopback address; listening on the server socket instance for the connection request on the port; extracting a connection request launch id from the connection request; and based on a determination that the connection configuration launch id and connection request launch id match, accepting the connection request, wherein the port number is a random port number generated by the web page and the connection configuration launch id and connection request launch id comprise a string randomly generated by the web page.
12. The method of Claim 11, further comprising launching the local server program instance by using the connection configuration data.
13. The method of Claim 11, further comprising sending the connection data as a connection request originating from the web page using the protocol.
19. The method of Claim 11, further comprising the local server program instance: receiving a connection configuration launch id and a connection configuration port number for a port from the operating system based on a request by the web page; creating a server socket instance and binding the server socket instance to a loopback address; listening on the server socket instance for the connection request on the port; extracting a connection request launch id from the connection request; based on a determination that the connection configuration launch id and connection request launch id match, accepting the connection request, wherein the port number is a random port number generated by the web page and the connection configuration launch id and connection request launch id comprise a string randomly generated by the web page.
7. A method comprising: executing, by a processor, a web browser; rendering, by the web browser of an operating system, a web page, the web page comprising executable instructions; generating, by the web browser via executable instructions of the web page, connection configuration data usable by a local server program instance registered with the operating system, wherein the connection configuration data comprises: a port on which the local server program instance is to listen for a connection request while the port is randomly selected by a web page; a randomly generated launch id; a port number corresponding to the port; and a protocol specific to the web browser; launching, by the operating system, the local server program instance by using the connection configuration data, wherein the launching of the local server program instance further comprises associating the local server program instance with the protocol specific to the web browser; sending the connection data as a connection request originating from the web page using the protocol, wherein the connection request is sent to the local server program instance to establish a connection between the web browser and the server program instance; based on an acceptance of the connection request by the server program instance, completing the connection, wherein the connection is usable for bi-directional communication between the web browser and the server program instance; receiving a connection configuration launch id and a connection configuration port number for a port from the operating system based on a request by the web page; creating a server socket instance and binding the server socket instance to a loopback address; listening on the server socket instance for the connection request on the port; extracting a connection request launch id from the connection request; and based on a determination that the connection configuration launch id and connection request launch id match, accepting the connection request, wherein the port number is a random port number generated by the web page and the connection configuration launch id and connection request launch id comprise a string randomly generated by the web page.
15. The method of Claim 11, further comprising composing, by the web page, a uniform resource locator (URL) including the port number on a local host and the launch id and creating, by the web page, a client socket instance using the URL.
8. The method of claim 7, further comprising composing, by the web page, a uniform resource locator (URL) including the port number on a local host and the launch id and creating, by the web page, a client socket instance using the URL.
16. The method of Claim 15, wherein the client socket instance is a client WebSocket instance.
9. The method of claim 8, wherein the client socket instance is a client WebSocket instance.
17. The method of Claim 16, wherein the connection request is an HTTP GET request that includes the randomly generated launch id.
10. The method of claim 9, wherein the connection request is an HTTP GET request that includes the randomly generated launch id.
18. The method of Claim 11, wherein launching the local server program instance and providing the connection data to the local server program instance comprises sending, by the web page, a launch request to the operating system to launch the local server program instance, the launch request including an indicator of the protocol that a local server program is registered to handle, the port number to be passed to the local server program instance and the launch id to be passed to the local server program instance.
11. The method of claim 7, wherein launching the local server program instance and providing the connection data to the local server program instance comprises sending, by the web page, a launch request to the operating system to launch the local server program instance, the launch request including an indicator of the protocol that a local server program is registered to handle, the port number to be passed to the local server program instance and the launch id to be passed to the local server program instance.
20. The method of Claim 19, wherein the local server program is executable to extract the connection configuration launch id and connection configuration port number from command line attributes from the operating system.
12. The method of claim 7, wherein the local server program is executable to extract the connection configuration launch id and connection configuration port number from command line attributes from the operating system.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Feng et al. (U.S. 2018/0063221 A1) discloses a webpage sharing method, an apparatus and a system are disclosed, the method includes: acquiring, by a device with memory and at least one processor, a webpage sharing instruction, acquiring an terminal identification (ID) corresponding to a terminal according to the webpage sharing instruction, acquiring a webpage identifier that identifies at least a portion of the webpage, and transmitting the webpage identifier to an event monitoring process that is associated with a web browser in the terminal corresponding to the ID.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to JOE CHACKO whose telephone number is (571)270-3318. The examiner can normally be reached Monday-Friday 7am-5pm.
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, Ario Etienne can be reached at 5712724001. 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.
/JOE CHACKO/Primary Examiner, Art Unit 2457
