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 .
Specification
The disclosure is objected to because of the following informalities: The specification should be updated to reflect the current status of all co-pending applications.
Appropriate correction is required.
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-20 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-20 of U.S. Patent No. 12,363,099. Although the claims at issue are not identical, they are not patentably distinct from each other because the claims in the ‘099 patent anticipate the claims in the instant application.
Claim 1 of ‘099 patent
Claim 1 of instant application
A system comprising:
A system comprising:
An authentication token generator comprising:
An authentication token generator comprising:
A first memory configured to store:
A first memory configured to store:
A group associated with each user; and
A group associated with each user; and
User credentials for each user; and
User credentials for each user; and
A first processor communicatively coupled to the first memory, wherein the first processor is configured to:
A first processor communicatively coupled to the first memory, wherein the first processor is configured to:
Receive first user credentials of a first user from a first user device;
Receive first user credentials of a first user from a first user device;
Compare the first user credentials to stored user credentials for the first user;
In response to the first user credentials matching the stored user credentials for the first user, authenticate the first user;
Determine a first group of the first user based on the first user credentials;
Determine a first group of the first user based on the first user credentials;
Send the first group to a computing cluster;
Send the first group to a computing cluster;
In response to sending the first group, receive first access information for the first user from the computing cluster, wherein the first access information comprises a first set of uniform resource locators (URLs) associated with the first group, and wherein each URL of the first set of URLs corresponds to a respective user interface (UI) of the computing cluster that is accessible to the first group;
In response to sending the first group, receive first access information for the first user from the computing cluster, wherein the first access information comprises a first set of uniform resource locators (URLs) associated with the first group, and wherein each URL of the first set of URLs corresponds to a respective user interface (UI) of the computing cluster that is accessible to the first group;
Generate a first authentication token based on the first user credentials and the first access information;
Generate a first authentication token based on the first user credentials and the first access information;
Send a first copy of the first authentication token to the first user device; and
Send a first copy of the first authentication token to the first user device; and
Send a second copy of the first authentication token to the computing cluster; and
Send a second copy of the first authentication token to the computing cluster; and
The first user device communicatively coupled to the authentication token generator, wherein the first user device comprises:
The first user device communicatively coupled to the authentication token generator, wherein the first user device comprises:
A second memory configured to store a first browser application; and
A second memory configured to store a first browser application; and
A second processor communicatively coupled to the second memory, wherein the second processor is configured to:
A second processor communicatively coupled to the second memory, wherein the second processor is configured to:
Receive the first copy of the first authentication token from the authentication token generator;
Receive the first copy of the first authentication token from the authentication token generator;
Assign the first copy of the first authentication token to a first session variable of the first browser application;
Assign the first copy of the first authentication token to a first session variable of the first browser application;
Input a first URL into the first browser application to attempt accessing a first UI of the computing cluster; and
Input a first URL into the first browser application to attempt accessing a first UI of the computing cluster; and
Send the first URL and the first session variable to the computing cluster; and
Send the first URL and the first session variable to the computing cluster; and
The computing cluster communicatively coupled to the first user device and the authentication token generator, wherein the computing cluster comprises:
The computing cluster communicatively coupled to the first user device and the authentication token generator, wherein the computing cluster comprises:
A third memory configured to store respective access information for each user; and
A third memory configured to store respective access information for each user; and
A third processor communicatively coupled to the third memory, wherein the third processor is configured to:
A third processor communicatively coupled to the third memory, wherein the third processor is configured to:
Receive the second copy of the first authentication token from the authentication token generator;
Receive the second copy of the first authentication token from the authentication token generator;
Receive the first URL and the first session variable from the first user device;
Receive the first URL and the first session variable from the first user device;
Compare the first session variable to the second copy of the first authentication token; and
Compare the first session variable to the second copy of the first authentication token; and
In response to the first session variable matching the second copy of the first authentication token, compare the first URL to the first set of URLs, wherein the second processor is further configured to:
In response to the first session variable matching the second copy of the first authentication token, compare the first URL to the first set of URLs, wherein the second processor is further configured to:
In response to the first URL being one of the first set of URLs and the first session variable matching the second copy of the first authentication token, access the first UI of the computing cluster using the first browser application.
In response to the first URL being one of the first set of URLs and the first session variable matching the second copy of the first authentication token, access the first UI of the computing cluster using the first browser application.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Bhimanaik US 10,785,201
Yaqub et al. US 11,941,103
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Jeffrey R. Swearingen whose telephone number is (571)272-3921. The examiner can normally be reached M-F 8:00 am - 5:00 pm.
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, Oscar Louie can be reached at 571-270-1684. 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.
Jeffrey R. Swearingen
Primary Examiner
Art Unit 2445
/Jeffrey R Swearingen/Primary Examiner, Art Unit 2445
Prosecution Insights