IP Library Granted Patent US 12,737,490
Granted Patent B2
US 12,737,490 · App. 18/945,948 · Granted Sep 15, 2026

Enhanced mechanisms for information exchange in an enterprise environment

Inventors: Pierre Demonsant (Paris, FR); Fabrice Ollivier (Paris, FR); Thibault Roche (Paris, FR)
Assignee: Planisware SAS
G06F21/6218H04L12/1822H04L63/08H04L63/102H04L67/131H04L67/34
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,737,490
App. No.
18/945,948
Granted
Sep 15, 2026
Kind
B2
Abstract

Systems and methods for the exchange of information between an enterprise client and a partner within an enterprise environment are provided. In this exchange of information, the client selects, via a user interface, a subset of client data, as well as one or more screen sets, to share with a partner. Once the partner has accepted, the system then sends an account creation request or account login request to the partner. Once the partner is authenticated in the system with an account, the system creates an information exchange session for the partner, and provides, on a display of the partner's device, a user interface that shows the subset of the client data and the screen sets. Access to the rest of the customer's enterprise environment is restricted.

Claims (36)

1 . A method, comprising:

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;

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

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.

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.

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.

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.

5 . The method of claim 1 , further comprising:

receiving a partner update associated with the partner comprising one or more proposed edits to the subset of the client data; and

sending the partner update to the client device.

6 . The method of claim 5 , further comprising:

receiving a validation of at least a portion of the partner update; and

incorporating the validation of the at least a portion of the partner update into the subset of the client data.

7 . The method of claim 1 , wherein each of the one or more screen sets comprises one or more pieces of client data presented in a partner user interface screen, the partner user interface screen mirroring at least a portion of one or more user interface screens associated with the client user interface.

8 . The method of claim 1 , wherein the enterprise environment is implemented as a Software as a Service (SaaS) environment.

9 . The method of claim 1 , wherein asynchronous communication includes email, text message, or social media message.

10 . The method of claim 1 , wherein the client maintains its own database system and does not share access to the database system with the partner.

11 . The method of claim 1 , wherein at least a portion of the partner user interface is different than the client user interface.

12 . A system, comprising:

memory configured to maintain 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;

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

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.

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.

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.

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.

16 . The system of claim 12 , further comprising:

receiving a partner update associated with the partner comprising one or more proposed edits to the subset of the client data; and

sending the partner update to the client device.

17 . The system of claim 16 , further comprising:

receiving a validation of at least a portion of the partner update; and

incorporating the validation of the at least a portion of the partner update into the subset of the client data.

18 . The system of claim 12 , wherein each of the one or more screen sets comprises one or more pieces of client data presented in a partner user interface screen, the partner user interface screen mirroring at least a portion of one or more user interface screens associated with the client user interface.

19 . The system of claim 12 , wherein the enterprise environment is implemented as a Software as a Service (SaaS) environment.

20 . The system of claim 12 , wherein asynchronous communication includes email, text message, or social media message.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 13, 2024
From: DEMONSANT, PIERRE; OLLIVIER, FABRICE; ROCHE, THIBAULT
To: PLANISWARE SAS
Reel/Frame 069252/0893 →
Continuity (4)
Continuation 18297791 · Apr 10, 2023
Continuation 16414730 · May 16, 2019
Provisional Application 62672536 · May 16, 2018
Related Publication 20250068761A1 · Feb 27, 2025
References Cited (74)
US 10165022B1 · Hubbard et al. · 2018 [cited by applicant]
US 10410016B1 · Damick · 2019 [cited by applicant]
US 11663350B2 · Demonsant et al. · 2023 [cited by applicant]
US 12174986B2 · Demonsant · 2024 [cited by applicant]
US 20030097410A1 · Atkins et al. · 2003 [cited by applicant]
US 20060031779A1 · Theurer et al. · 2006 [cited by applicant]
US 20060053196A1 · Spataro · 2006 [cited by examiner]
US 20060235716A1 · Mahesh et al. · 2006 [cited by applicant]
US 20090150169A1 · Kirkwood et al. · 2009 [cited by applicant]
US 20100070842A1 · Aymeloglu et al. · 2010 [cited by applicant]
US 20100262925A1 · Liu et al. · 2010 [cited by applicant]
US 20120011451A1 · Bansal et al. · 2012 [cited by applicant]
US 20120036452A1 · Coleman et al. · 2012 [cited by applicant]
US 20130007895A1 · Brolley et al. · 2013 [cited by applicant]
US 20130036370A1 · Ananthakrishnan · 2013 [cited by applicant]
US 20130097687A1 · Storm · 2013 [cited by applicant]
US 20130141471A1 · Batson et al. · 2013 [cited by applicant]
US 20130318589A1 · Ford et al. · 2013 [cited by applicant]
US 20130318593A1 · Smith et al. · 2013 [cited by applicant]
US 20140122416A1 · Leto et al. · 2014 [cited by applicant]
US 20140123237A1 · Gaudet · 2014 [cited by examiner]
US 20140165176A1 · Ow · 2014 [cited by applicant]
US 20140215356A1 · Brander et al. · 2014 [cited by applicant]
US 20150032686A1 · Kuchoor · 2015 [cited by applicant]
US 20150082271A1 · Damonte et al. · 2015 [cited by applicant]
US 20150269522A1 · Tarrant · 2015 [cited by applicant]
US 20150286828A1 · Bulumulla et al. · 2015 [cited by applicant]
US 20150373081A1 · Laga et al. · 2015 [cited by applicant]
US 20160065672A1 · Savage et al. · 2016 [cited by applicant]
US 20160147952A1 · Garcia et al. · 2016 [cited by applicant]
US 20170024100A1 · Pieper et al. · 2017 [cited by applicant]
US 20170041296A1 · Ford et al. · 2017 [cited by applicant]
US 20170048285A1 · Pearl · 2017 [cited by examiner]
US 20170200021A1 · Patel et al. · 2017 [cited by applicant]
US 20170249394A1 · Loeb et al. · 2017 [cited by applicant]
US 20180053012A1 · Myers et al. · 2018 [cited by applicant]
US 20180121667A1 · Karpel et al. · 2018 [cited by applicant]
US 20180218120A1 · Canzoneri · 2018 [cited by applicant]
US 20180336373A1 · Deenadayal · 2018 [cited by applicant]
US 20190012053A1 · Hawa et al. · 2019 [cited by applicant]
US 20190020715A1 · Haviv et al. · 2019 [cited by applicant]
US 20190163927A1 · Kochura et al. · 2019 [cited by applicant]
US 20190196774A1 · Sarfi et al. · 2019 [cited by applicant]
US 20190356499A1 · Demonsant et al. · 2019 [cited by applicant]
US 20200026485A1 · Deenadayal · 2020 [cited by applicant]
US 20230244808A1 · Demonsant et al. · 2023 [cited by applicant]
U.S. Appl. No. 16/414,730, Examiner Interview Summary Record (Ptol-413), Sep. 8, 2020,3 pgs. [cited by applicant]
U.S. Appl. No. 16/414,730, Final Rejection, Oct. 27, 2020, 19 pgs. [cited by applicant]
U.S. Appl. No. 16/414,730, Non-Final Rejection, Jun. 5, 2020, 19 pgs. [cited by applicant]
U.S. Appl. No. 16/414,730, Office Action Appendix, Sep. 8, 2020, 10 pgs. [cited by applicant]
U.S. Appl. No. 16/414,730, USPTO e-Office Action: CTAV—Advisory Action (Ptol-303), Nov. 8, 2022, 2 pages. [cited by applicant]
U.S. Appl. No. 16/414,730, USPTO e-Office Action: CTFR—Final Rejection, Aug. 26, 2022, 18 pages. [cited by applicant]
U.S. Appl. No. 16/414,730, USPTO e-Office Action: EXIN—Examiner Interview Summary Record (Ptol-413), Jan. 10, 2023, 1 page. [cited by applicant]
U.S. Appl. No. 16/414,730, USPTO e-Office Action: EXIN—Examiner Interview Summary Record (Ptol-413), Nov. 8, 2022, 2 pages. [cited by applicant]
U.S. Appl. No. 16/414,730, USPTO e-Office Action: NOA—Notice Of Allowance And Fees Due (Ptol-85), Jan. 10, 2023, 14 pages. [cited by applicant]
U.S. Appl. No. 18/297,791, USPTO e-Office Action: CTAV—Advisory Action (Ptol-303), Aug. 7, 2024, 7 pages. [cited by applicant]
U.S. Appl. No. 18/297,791, USPTO e-Office Action: CTFR—Final Rejection, May 15, 2024, 24 pages. [cited by applicant]
U.S. Appl. No. 18/297,791, USPTO e-Office Action: CTNF—Non-Final Rejection, Oct. 18, 2023, 20 pages. [cited by applicant]
U.S. Appl. No. 18/297,791, USPTO e-Office Action: NOA—Notice Of Allowance And Fees Due (Ptol-85), Aug. 28, 2024, 10 pages. [cited by applicant]
U.S. Appl. No. 16/414,730, Advisory Action mailed Feb. 10, 222 pgs. [cited by applicant]
U.S. Appl. No. 16/414,730, Examiner Interview Summary mailed Feb. 10, 2022, 2 pgs. [cited by applicant]
U.S. Appl. No. 16/414,730, Examiner Interview Summary mailed Feb. 3, 2021, 3 pgs. [cited by applicant]
U.S. Appl. No. 16/414,730, Examiner Interview Summary mailed May 7, 2021, 3 pgs. [cited by applicant]
U.S. Appl. No. 16/414,730, Examiner Interview Summary mailed Sep. 7, 2021, 3 pgs. [cited by applicant]
U.S. Appl. No. 16/414,730, Final Office Action mailed Dec. 1, 2021, 14 pgs. [cited by applicant]
U.S. Appl. No. 16/414,730, Non Final Office Action mailed Apr. 11, 2022, 19 pgs. [cited by applicant]
U.S. Appl. No. 16/414,730, Non-Final Office Action mailed May 25, 2021, 16 pgs. [cited by applicant]
Bailey-Woods, L., Hall, T.M., Halpert, A.M., Rhia, Ma, C., Kotyk, S., Neal, S. and Rhit (2012), “Ensuring Data Integrity In Health Information Exchange,” [online] Available at: http://library.ahima.org/PdfView?oid=10561… [cited by applicant]
Banerji, Preeta, et al. “Deploying an Enterprise-Ready Content Sync-and-Share Solution.” (2013). (Year: 2013). [cited by applicant]
Chen, W. J., et al. “IBM Enterprise Content Management and Box. IBM International Technical Support Organization.” (2016). (Year: 2016). [cited by applicant]
Mao, L. (n.d.), “Information Resources Management Framework for Virtual Enterprise,” [online] Available at: https://arxiv.org/pdf/1512.02726 [Accessed Feb. 8, 2020], 6 pages. [cited by applicant]
Putman, Janis, and Stephen Strong. “A federated virtual enterprise (ve) of partners creating a federated ve of systems.” Proceedings. The Twenty-Second Annual International Computer Software and Applications Conference … [cited by applicant]
Thilakanathan, Danan, et al. “Safe Protect: Controlled data sharing with user-defined policies in cloud-based collaborative environment.” IEEE Transactions on Emerging Topics in Computing 4.2 (2015): 301-315. (Year: 201… [cited by applicant]
Wise, Catherine, et al. “Cloud docs: secure scalable document sharing on public clouds.” 2015 IEEE 8th International Conference on Cloud Computing. IEEE, 2015. pp. 1-2, 10, 16-18, 119 (Year: 2015). [cited by applicant]