DETAILED ACTION
This Office Action is in response to the Application Ser. No. 18/945,948 filed on November 13, 2024. Claims 1-20 are pending and are examined.
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 .
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 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.
Priority
Acknowledgment is made of applicant’s claim for domestic priority as a continuing application under 35 U.S.C. 120 based on Non-Provisional Application Ser. No. 18/297,791 filed on April 10, 2023, which claims the benefit of Non-Provisional Application Ser. No. 16/414,730 filed May 16, 2019, which claims the benefit of Provisional Application Ser. No. 62/672,536 filed May 16, 2018.
Drawings
Drawings were received on November 13, 2024. These drawings are accepted.
Information Disclosure Statement
Applicant’s submission of the Information Disclosure Statement dated November 13, 2024, is acknowledged by the Examiner and the cited references have been considered in the examination of the claims now pending (see attached PTO-1449).
Claim Objections
Applicant is advised that should Claims 5 and 16 be found allowable, Claims 6 and 17 will be objected to under 37 CFR 1.75 as being substantial duplicates thereof. When two claims in an application are duplicates or else are so close in content that they both cover the same thing, despite a slight difference in wording, it is proper after allowing one claim to object to the other as being a substantial duplicate of the allowed claim. See MPEP § 608.01(m).
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-9 and 11-20 are rejected on the ground of nonstatutory double patenting as being unpatentable over Claims 1-5 and 7-12 of issued U.S. Patent 11,663,350 B2.
Although the claims at issue are not identical, they are not patentably distinct from each other because it would be obvious to one of ordinary skill in the art at the time of the effective filing that the claims cover substantially the same subject matter, i.e., sharing content of an enterprise environment. The following charts provide examples of how independent Claims 1-4 and 12-15 of the instant application corresponds to Claims 1 and 8 of the issued patent. Similar relationships hold for the remaining dependent claims.
Instant Application
Issued Patent
18/945,948
US 11,663,350 B2
1. A method, comprising:
1. A method, comprising:
maintaining an enterprise environment comprising a plurality of clients, wherein each client is associated with a set of client data;
maintaining an enterprise environment comprising a plurality of clients, wherein each client is associated with a set of client data;
sending an asynchronous client request, from a client at a client device, to a partner device of a partner associated with the client, the client request comprising a subset of the client data and one or more screen sets to be shared, the subset of the client data and the one or more screen sets being selected by the client in a client user interface, wherein the enterprise environment is configured to allow the client to have granular control over which data is sent in the client request;
sending a client request, from a client at a client device, to a partner device of a partner associated with the client, the client request comprising a subset of the client data and one or more screen sets to be shared, the subset of the client data and the one or more screen sets being selected by the client in a client user interface, wherein the enterprise environment is configured to allow the client to have granular control over which data is sent in the client request, the data including project, activity and task metadata, portions of screens, and screens with elements redacted or blurred;
4. The method of claim 1, wherein the data includes project, activity and task metadata, portions of screens, and screens with elements redacted or blurred.
receiving a notification that the partner has responded to the client request with an acceptance;
sending one of an account creation request or account login request to the partner device;
creating an information exchange session for the partner, wherein the information exchange session occurs between a software-as-a-service (SAAS) environment for the partner device and a client portal for the client device; and
creating an information exchange session for the partner, wherein the information exchange session occurs between a software-as-a-service (SAAS) environment for the partner device and a client portal for the client device, and wherein updates to the information exchange session occur via datamodel synchronization between the SAAS environment and the client portal, wherein the SAAS environment itself does not store any client data; and
3. The method of claim 1, wherein updates to the information exchange session occur via datamodel synchronization between the SAAS environment and the client portal, wherein the SAAS environment itself does not store any client data.
providing, on a display of the partner device, a partner user interface comprising the subset of the client data and the one or more screen sets, wherein the one or more screen sets are shared by first being converted into a data serialization format, wherein access to the enterprise environment by the partner is restricted to only the subset of the client data and the one or more screen sets, and wherein one or more pieces of client data are editable by the partner via the partner user interface.
providing, on a display of the partner device, a partner user interface comprising the subset of the client data and the one or more screen sets, wherein access to the enterprise environment by the partner is not a direct screen exchange, but instead, restricted to only the subset of the client data and the one or more screen sets, wherein the one or more screen sets are shared by first being converted into JSON format and then being converted into a format for display on the partner device, and wherein one or more pieces of client data are editable by the partner via the partner user interface;
2. The method of claim 1, wherein the one or more screen sets are shared by first being converted into JSON format and then being converted into a format for display on the partner device.
wherein the client request, the notification and the updates to the information exchange session are transmitted via asynchronous communication.
Instant Application
Issued Patent
18/945,948
US 11,663,350 B2
12. A system, comprising:
8. A system comprising:
a processor; and
memory, the memory storing program instructions to execute a method, the method comprising:
memory configured to maintain an enterprise environment comprising a plurality of clients, wherein each client is associated with a set of client data;
maintaining an enterprise environment comprising a plurality of clients, wherein each client is associated with a set of client data;
an interface configured to send an asynchronous client request, from a client at a client device, to a partner device of a partner associated with the client, the client request comprising a subset of the client data and one or more screen sets to be shared, the subset of the client data and the one or more screen sets being selected by the client in a client user interface, wherein the enterprise environment is configured to allow the client to have granular control over which data is sent in the client request;
sending a client request, from a client at a client device, to a partner device of a partner associated with the client, the client request comprising a subset of the client data and one or more screen sets to be shared, the subset of the client data and the one or more screen sets being selected by the client in a client user interface, wherein the enterprise environment is configured to allow the client to have granular control over which data is send in the client request, the data including project, activity, and task metadata, portions of screens, and screens with elements redacted or blurred;
15. The system of claim 12, wherein the data includes project, activity and task metadata, portions of screens, and screens with elements redacted or blurred.
receiving a notification that the partner has responded to the client request with an acceptance;
sending one of an account creation request or account login request to the partner device;
a processor configured to create an information exchange session for the partner, wherein the information exchange session occurs between a software-as-a-service (SAAS) environment for the partner device and a client portal for the client device; and
creating an information exchange session for the partner, wherein the information exchange session occurs between a software-as-a-service (SAAS) environment for the partner device and a client portal for the client device, and wherein updates to the information exchange session occur via datamodel synchronization between the SAAS environment and the client portal, wherein the SAAS environment does not store any client data; and
14. The system of claim 12, wherein updates to the information exchange session occur via datamodel synchronization between the SAAS environment and the client portal, wherein the SAAS environment itself does not store any client data.
wherein a partner user interface comprising the subset of the client data and the one or more screen sets is provided on a display of the partner device, wherein the one or more screen sets are shared by first being converted into a data serialization format, wherein access to the enterprise environment by the partner is restricted to only the subset of the client data and the one or more screen sets, and wherein one or more pieces of client data are editable by the partner via the partner user interface.
providing, on a display of the partner device, a partner user interface comprising the subset of the client data and the one or more screen sets, wherein access to the enterprise environment by the partner is not a direct screen exchange, but instead, restricted to only the subset of the client data and the one or more screen sets, wherein the one or more screen sets are shared by first being converted into JSON format and then being converted into a format for display on the partner device, and wherein one or more pieces of client data are editable by the partner via the partner user interface;
13. The system of claim 12, wherein the one or more screen sets are shared by first being converted into JSON format and then being converted into a format for display on the partner device.
wherein the client request, the notification and the updates to the information exchange session are transmitted via asynchronous communication.
Claims 1-20 are rejected on the ground of nonstatutory double patenting as being unpatentable over Claims 1-12 of issued U.S. Patent 12,174,986 B2.
Although the claims at issue are not identical, they are not patentably distinct from each other because it would be obvious to one of ordinary skill in the art at the time of the effective filing that the claims cover substantially the same subject matter, i.e., sharing content of an enterprise environment. The following charts provide examples of how independent Claims 1-4 and 12-15 of the instant application corresponds to Claims 1 and 8 of the issued patent. Similar relationships hold for the remaining dependent claims.
Instant Application
Issued Patent
18/945,948
US 12,174,986 B2
1. A method, comprising:
1. A method, comprising:
maintaining an enterprise environment comprising a plurality of clients, wherein each client is associated with a set of client data;
maintaining an enterprise environment comprising a plurality of clients, wherein each client is associated with a set of client data;
sending an asynchronous client request, from a client at a client device, to a partner device of a partner associated with the client, the client request comprising a subset of the client data and one or more screen sets to be shared, the subset of the client data and the one or more screen sets being selected by the client in a client user interface, wherein the enterprise environment is configured to allow the client to have granular control over which data is sent in the client request;
sending an asynchronous client request, from a client at a client device, to a partner device of a partner associated with the client, the client request comprising a subset of the client data and one or more screen sets to be shared, the subset of the client data and the one or more screen sets being selected by the client in a client user interface, wherein the enterprise environment is configured to allow the client to have granular control over which data is sent in the client request, the data including project, activity and task metadata, portions of screens, and screens with elements redacted or blurred;
4. The method of claim 1, wherein the data includes project, activity and task metadata, portions of screens, and screens with elements redacted or blurred.
receiving a notification that the partner has responded to the client request with an acceptance;
sending one of an account creation request or account login request to the partner device;
creating an information exchange session for the partner, wherein the information exchange session occurs between a software-as-a-service (SAAS) environment for the partner device and a client portal for the client device; and
creating an information exchange session for the partner, wherein the information exchange session occurs between a software-as-a-service (SAAS) environment for the partner device and a client portal for the client device, and wherein updates to the information exchange session occur via datamodel synchronization between the SAAS environment and the client portal, wherein the SAAS environment itself does not store any client data; and
3. The method of claim 1, wherein updates to the information exchange session occur via datamodel synchronization between the SAAS environment and the client portal, wherein the SAAS environment itself does not store any client data.
providing, on a display of the partner device, a partner user interface comprising the subset of the client data and the one or more screen sets, wherein the one or more screen sets are shared by first being converted into a data serialization format, wherein access to the enterprise environment by the partner is restricted to only the subset of the client data and the one or more screen sets, and wherein one or more pieces of client data are editable by the partner via the partner user interface.
providing, on a display of the partner device, a partner user interface comprising the subset of the client data and the one or more screen sets, wherein access to the enterprise environment by the partner is not a direct screen exchange, but instead, restricted to only the subset of the client data and the one or more screen sets, wherein the one or more screen sets are shared by first being converted into JSON format and then being converted into a format for display on the partner device, and wherein one or more pieces of client data are editable by the partner via the partner user interface.
2. The method of claim 1, wherein the one or more screen sets are shared by first being converted into JSON format and then being converted into a format for display on the partner device.
Instant Application
Issued Patent
18/945,948
US 12,174,986 B2
12. A system, comprising:
8. A system comprising:
a processor; and
memory, the memory storing program instructions to execute a method, the method comprising:
memory configured to maintain an enterprise environment comprising a plurality of clients, wherein each client is associated with a set of client data;
maintaining an enterprise environment comprising a plurality of clients, wherein each client is associated with a set of client data;
an interface configured to send an asynchronous client request, from a client at a client device, to a partner device of a partner associated with the client, the client request comprising a subset of the client data and one or more screen sets to be shared, the subset of the client data and the one or more screen sets being selected by the client in a client user interface, wherein the enterprise environment is configured to allow the client to have granular control over which data is sent in the client request;
sending an asynchronous client request, from a client at a client device, to a partner device of a partner associated with the client, the client request comprising a subset of the client data and one or more screen sets to be shared, the subset of the client data and the one or more screen sets being selected by the client in a client user interface, wherein the enterprise environment is configured to allow the client to have granular control over which data is sent in the client request, the data including project, activity, and task metadata, portions of screens, and screens with elements redacted or blurred;
15. The system of claim 12, wherein the data includes project, activity and task metadata, portions of screens, and screens with elements redacted or blurred.
receiving a notification that the partner has responded to the client request with an acceptance;
sending one of an account creation request or account login request to the partner device;
a processor configured to create an information exchange session for the partner, wherein the information exchange session occurs between a software-as-a-service (SAAS) environment for the partner device and a client portal for the client device; and
creating an information exchange session for the partner, wherein the information exchange session occurs between a software-as-a-service (SAAS) environment for the partner device and a client portal for the client device, and wherein updates to the information exchange session occur via datamodel synchronization between the SAAS environment and the client portal, wherein the SAAS environment does not store any client data; and
14. The system of claim 12, wherein updates to the information exchange session occur via datamodel synchronization between the SAAS environment and the client portal, wherein the SAAS environment itself does not store any client data.
wherein a partner user interface comprising the subset of the client data and the one or more screen sets is provided on a display of the partner device, wherein the one or more screen sets are shared by first being converted into a data serialization format, wherein access to the enterprise environment by the partner is restricted to only the subset of the client data and the one or more screen sets, and wherein one or more pieces of client data are editable by the partner via the partner user interface.
providing, on a display of the partner device, a partner user interface comprising the subset of the client data and the one or more screen sets, wherein access to the enterprise environment by the partner is not a direct screen exchange, but instead, restricted to only the subset of the client data and the one or more screen sets, wherein the one or more screen sets are shared by first being converted into JSON format and then being converted into a format for display on the partner device, and wherein one or more pieces of client data are editable by the partner via the partner user interface.
13. The system of claim 12, wherein the one or more screen sets are shared by first being converted into JSON format and then being converted into a format for display on the partner device.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure:
Spataro et al., Pub. No. US 2006/0053196 a1, discloses a system and methods that provide a client-server infrastructure capable of supporting a variety of asynchronous and synchronous collaboration activities including viewing and/or editing one or more data files and sharing one or more applications, data files and/or displays.
A shortened statutory period for reply to this action is set to expire THREE MONTHS from the mailing date of this action. An extension of time may be obtained under 37 CFR 1.136(a). However, in no event, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to WILLIAM C MCBETH whose telephone number is (571)270-0495. The examiner can normally be reached on Monday - Friday, 8:00AM - 4:30PM ET.
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, Vivek Srivastava can be reached on 571-272-7304. 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.
/WILLIAM C MCBETH/Examiner, Art Unit 2449