IP Library Granted Patent US 12,499,263
Granted Patent B2
US 12,499,263 · App. 18/751,559 · Granted Dec 16, 2025

Enhancing an integrated end-of-purpose protocol with purpose information

Inventors: Matthias Vogel (Saarbrücken, DE); Benny Rolle (Göttingen, DE); Ufuoma Ighoroje (Schönefeld, DE)
Assignee: SAP SE
G06F21/6218G06F21/31G06F21/554
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,499,263
App. No.
18/751,559
Granted
Dec 16, 2025
Kind
B2
Abstract

The present disclosure involves systems, software, and computer implemented methods for integrated data privacy services. An example method includes determining to initiate an integrated end of purpose protocol for an object of an object type. Target applications are determined that are allowed to process objects of the object type for at least one purpose, based on identified purpose information. An end-of-purpose query is provided to the target applications and an end-of-purpose status is received from each target application that indicates whether the application is able to block the object. The received statuses are evaluated to determine whether an aligned end of purpose has been reached for the object. In response to determining that the aligned end of purpose has been reached for the object, a block command is provided to each of the multiple applications that instructs a respective application to locally block the object.

Claims (44)

1 . A computer-implemented method comprising:

providing, to each of multiple target applications in a multiple-application landscape, an end-of-purpose query that requests each respective target application to determine whether the respective target application is able to block an object;

receiving, as received end-of-purpose statuses, in response to the end-of-purpose query, an end-of-purpose status from each respective target application of the multiple target applications that indicates whether the respective target application is able to block the object;

evaluating the received end-of-purpose statuses to determine whether an aligned end of purpose has been reached for the object in the multiple-application landscape;

in response to determining that the aligned end of purpose has been reached for the object in the multiple-application landscape, providing, to each of the multiple target applications, a block command that instructs a respective application to locally block the object in the respective application; and

updating purpose information in the multiple-application landscape based on the received end-of-purpose statuses.

2 . The computer-implemented method of claim 1 , further comprising determining the target applications, wherein determining the target applications comprises identifying, as the target applications, applications that are allowed to process objects of an object type of the object for at least one purpose.

3 . The computer-implemented method of claim 1 , wherein updating the purpose information comprises:

evaluating the received end-of-purpose statuses and purpose information that indicates for which purposes respective applications are allowed to process objects in the multiple-application landscape; and

updating the purpose information, based on the received end-of-purpose statuses, to create updated purpose information for at least some of the target applications.

4 . The computer-implemented method of claim 3 , wherein updating the purpose information comprises removing a first purpose assignment for a first purpose from a first application in response to determining that no application is processing the object for the first purpose.

5 . The computer-implemented method of claim 4 , wherein an aligned end-of-purpose has not been reached for the object and the method further comprises determining that the first application has no purposes assigned to the object.

6 . The computer-implemented method of claim 5 , further comprising, based on determining that the first application has no purposes assigned to the object, sending a block command for the object to the first application instructing the first application to block the object.

7 . The computer-implemented method of claim 1 , wherein the target applications do not include a first application based on the first application not having any purposes assigned to the object and wherein the end-of-purpose query is not sent to the first application.

8 . The computer-implemented method of claim 1 , wherein evaluating the received end-of-purpose statuses comprises determining whether each end-of-purpose status indicates end of purpose for the object.

9 . The computer-implemented method of claim 1 , further comprising receiving a block status from each respective target application that indicates a success or failure of processing the block command in the respective target application.

10 . The computer-implemented method of claim 1 , wherein a first end-of-purpose status includes an end-of-purpose time for the object for a first target application.

11 . The computer-implemented method of claim 10 , further comprising determining that the first target application has reached end of purpose for the object based on determining that the end-of-purpose time is a historical time.

12 . The computer-implemented method of claim 10 , further comprising determining that the first target application has not reached end of purpose for the object based on determining that the end-of-purpose time is a future time.

13 . The computer-implemented method of claim 2 , wherein applications that do not process objects of the object type are not included in the target applications.

14 . A system comprising:

an integrated end of purpose handler;

multiple applications included in a multiple-application landscape;

wherein the integrated end of purpose handler is configured to:

provide, to each of multiple target applications in a multiple-application landscape, an end-of-purpose query that requests each respective target application to determine whether the respective target application is able to block an object;

receive, as received end-of-purpose statuses, in response to the end-of-purpose query, an end-of-purpose status from each respective target application of the multiple target applications that indicates whether the respective target application is able to block the object;

evaluate the received end-of-purpose statuses to determine whether an aligned end of purpose has been reached for the object in the multiple-application landscape;

in response to determining that the aligned end of purpose has been reached for the object in the multiple-application landscape, provide, to each of the multiple target applications, a block command that instructs a respective application to locally block the object in the respective application; and

updating purpose information in the multiple-application landscape based on the received end-of-purpose statuses.

15 . The system of claim 14 , wherein the integrated end of purpose handler is further configured to:

evaluate the received end-of-purpose statuses and the purpose information; and

update the purpose information, based on the received end-of-purpose statuses, to create updated purpose information for at least some of the target applications.

16 . The system of claim 15 , wherein updating the purpose information comprises removing a first purpose assignment for a first purpose from a first application in response to determining that no application is processing the object for the first purpose.

17 . The system of claim 16 , wherein an aligned end-of-purpose has not been reached for the object and the integrated end of purpose handler is further configured to determine that the first application has no purposes assigned to the object.

18 . A non-transitory, computer-readable medium coupled to one or more processors and having instructions stored thereon which, when executed by the one or more processors, cause the one or more processors to perform operations, the operations comprising:

providing, to each of multiple target applications in a multiple-application landscape, an end-of-purpose query that requests each respective target application to determine whether the respective target application is able to block an object;

receiving, as received end-of-purpose statuses, in response to the end-of-purpose query, an end-of-purpose status from each respective target application of the multiple target applications that indicates whether the respective target application is able to block the object;

evaluating the received end-of-purpose statuses to determine whether an aligned end of purpose has been reached for the object in the multiple-application landscape;

in response to determining that the aligned end of purpose has been reached for the object in the multiple-application landscape, providing, to each of the multiple target applications, a block command that instructs a respective application to locally block the object in the respective application; and

updating purpose information in the multiple-application landscape based on the received end-of-purpose statuses.

19 . The computer-readable medium of claim 18 , wherein the operations further comprise:

evaluating the received end-of-purpose statuses and the purpose information; and

updating the purpose information, based on the received end-of-purpose statuses, to create updated purpose information for at least some of the target applications.

20 . The computer-readable medium of claim 19 , wherein updating the purpose information comprises removing a first purpose assignment for a first purpose from a first application in response to determining that no application is processing the object for the first purpose.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 24, 2024
From: VOGEL, MATTHIAS; ROLLE, BENNY; IGHOROJE, UFUOMA
To: SAP SE
Reel/Frame 067812/0440 →
Continuity (2)
Continuation 17457816 · Dec 6, 2021
Related Publication 20240346167A1 · Oct 17, 2024
References Cited (138)
US 17186A · Atwater · 1857 [cited by applicant]
US 17457A · Tidgewell · 1857 [cited by applicant]
US 7308704B2 · Vogel et al. · 2007 [cited by applicant]
US 7350237B2 · Vogel et al. · 2008 [cited by applicant]
US 7685605B1 · Ahmed et al. · 2010 [cited by applicant]
US 8484351B1 · Dean et al. · 2013 [cited by applicant]
US 8566193B2 · Singh et al. · 2013 [cited by applicant]
US 9405429B1 · Gopalakrishnan · 2016 [cited by applicant]
US 9703813B2 · Hegde et al. · 2017 [cited by applicant]
US 9904796B2 · Pluder et al. · 2018 [cited by applicant]
US 10387810B1 · Kalush et al. · 2019 [cited by applicant]
US 10409790B2 · Lehnert et al. · 2019 [cited by applicant]
US 10430413B2 · Christoph et al. · 2019 [cited by applicant]
US 10552642B2 · Rolle et al. · 2020 [cited by applicant]
US 10642805B1 · Masse · 2020 [cited by applicant]
US 10754932B2 · Wiederspohn et al. · 2020 [cited by applicant]
US 10776254B1 · Dhayanithi · 2020 [cited by applicant]
US 10812608B1 · Thummala Abbigari et al. · 2020 [cited by applicant]
US 10839099B2 · Vogel et al. · 2020 [cited by applicant]
US 10909222B1 · Fregly et al. · 2021 [cited by applicant]
US 11042654B2 · Nos et al. · 2021 [cited by applicant]
US 11113417B2 · Rolle · 2021 [cited by applicant]
US 11200331B1 · Bouaichi et al. · 2021 [cited by applicant]
US 11615059B2 · Kottomtharayil et al. · 2023 [cited by applicant]
US 11630673B2 · Grant · 2023 [cited by applicant]
US 11675651B2 · Li et al. · 2023 [cited by applicant]
US 11720367B2 · Wallach · 2023 [cited by applicant]
US 11765045B1 · Nguyen et al. · 2023 [cited by applicant]
US 11899655B2 · Malik et al. · 2024 [cited by applicant]
US 11921905B2 · Savagaonkar et al. · 2024 [cited by applicant]
US 11941151B2 · Mendoza et al. · 2024 [cited by applicant]
US 11947662B2 · Gingell et al. · 2024 [cited by applicant]
US 11962576B2 · Sapek et al. · 2024 [cited by applicant]
US 11994966B2 · Anthonappa et al. · 2024 [cited by applicant]
US 12045242B2 · Srivastava et al. · 2024 [cited by applicant]
US 12056255B1 · Mystetskyi et al. · 2024 [cited by applicant]
US 12141302B2 · Rolle et al. · 2024 [cited by applicant]
US 12147567B2 · Rolle et al. · 2024 [cited by applicant]
US 12164470B2 · Rolle et al. · 2024 [cited by applicant]
US 12184656B2 · Rolle et al. · 2024 [cited by applicant]
US 12189813B2 · Rolle et al. · 2025 [cited by applicant]
US 12210897B2 · Rolle et al. · 2025 [cited by applicant]
US 20040187047A1 · Rathunde et al. · 2004 [cited by applicant]
US 20070089117A1 · Samson · 2007 [cited by applicant]
US 20080060051A1 · Lim · 2008 [cited by examiner]
US 20080091807A1 · Strub et al. · 2008 [cited by applicant]
US 20080174425A1 · Torning · 2008 [cited by applicant]
US 20080244016A1 · Parthasarathy et al. · 2008 [cited by applicant]
US 20080301175A1 · Applebaum et al. · 2008 [cited by applicant]
US 20080312982A1 · Braun et al. · 2008 [cited by applicant]
US 20090210394A1 · Saravanan et al. · 2009 [cited by applicant]
US 20090228340A1 · Bohannon · 2009 [cited by applicant]
US 20120036507A1 · Jonnala et al. · 2012 [cited by applicant]
US 20120221444A1 · Bowes et al. · 2012 [cited by applicant]
US 20130066977A1 · Katti et al. · 2013 [cited by applicant]
US 20130132696A1 · Tomida et al. · 2013 [cited by applicant]
US 20130347064A1 · Aissi · 2013 [cited by applicant]
US 20140032600A1 · Sarferaz et al. · 2014 [cited by applicant]
US 20140059458A1 · Levien et al. · 2014 [cited by applicant]
US 20140109238A1 · Ravindran · 2014 [cited by applicant]
US 20140188572A1 · Hegde et al. · 2014 [cited by applicant]
US 20140267770A1 · Gervautz et al. · 2014 [cited by applicant]
US 20150242531A1 · Rodniansky · 2015 [cited by applicant]
US 20160148143A1 · Anderson et al. · 2016 [cited by applicant]
US 20160292455A1 · Jebara · 2016 [cited by applicant]
US 20170091479A1 · Pluder et al. · 2017 [cited by applicant]
US 20180101164A1 · Noetzelmann et al. · 2018 [cited by applicant]
US 20180322279A1 · Beskorovajnov et al. · 2018 [cited by applicant]
US 20190018985A1 · Rolle et al. · 2019 [cited by applicant]
US 20190132276A1 · Scheiber et al. · 2019 [cited by applicant]
US 20190156445A1 · Markham et al. · 2019 [cited by applicant]
US 20190236294A1 · McDonald et al. · 2019 [cited by applicant]
US 20190236334A1 · Babushkin · 2019 [cited by applicant]
US 20200019728A1 · Rolle · 2020 [cited by applicant]
US 20200133554A1 · Kishi et al. · 2020 [cited by applicant]
US 20200167699A1 · Cohen · 2020 [cited by applicant]
US 20200293356A1 · Bonaud et al. · 2020 [cited by applicant]
US 20200380810A1 · Unagami et al. · 2020 [cited by applicant]
US 20210089678A1 · Gkoulalas-Divanis et al. · 2021 [cited by applicant]
US 20210192052A1 · Loch et al. · 2021 [cited by applicant]
US 20210209251A1 · Parthasarathy · 2021 [cited by applicant]
US 20220083513A1 · Wong et al. · 2022 [cited by applicant]
US 20220207429A1 · Haribhakti et al. · 2022 [cited by applicant]
US 20220300837A1 · Shmelkin et al. · 2022 [cited by applicant]
US 20220321566A1 · Coyle et al. · 2022 [cited by applicant]
US 20230081785A1 · Zhang · 2023 [cited by applicant]
US 20230111687A1 · Mclean et al. · 2023 [cited by applicant]
US 20230176894A1 · Rolle et al. · 2023 [cited by applicant]
US 20230177180A1 · Rolle · 2023 [cited by applicant]
US 20230177182A1 · Rolle et al. · 2023 [cited by applicant]
US 20230177183A1 · Rolle et al. · 2023 [cited by applicant]
US 20230177186A1 · Ighoroje et al. · 2023 [cited by applicant]
US 20230177188A1 · Vogel et al. · 2023 [cited by applicant]
US 20230177189A1 · Ighoroje et al. · 2023 [cited by applicant]
US 20230177194A1 · Rolle et al. · 2023 [cited by applicant]
US 20230177206A1 · Rolle et al. · 2023 [cited by applicant]
US 20230177213A1 · Rolle et al. · 2023 [cited by applicant]
US 20230179602A1 · Rolle et al. · 2023 [cited by applicant]
US 20230237192A1 · Kahan et al. · 2023 [cited by applicant]
US 20230244637A1 · Wu · 2023 [cited by applicant]
US 20230379276A1 · Roy et al. · 2023 [cited by applicant]
US 20240005037A1 · Chintalapati et al. · 2024 [cited by applicant]
US 20240370582A1 · Rolle et al. · 2024 [cited by applicant]
US 20250117245A1 · Rolle et al. · 2025 [cited by applicant]
CA 2922139 · 2021 [cited by applicant]
CA 3096061 · 2023 [cited by applicant]
CN 108664805 · 2018 [cited by applicant]
CN 112818372 · 2021 [cited by applicant]
CN 113095348 · 2021 [cited by applicant]
CN 113282864 · 2021 [cited by applicant]
CN 114092253 · 2022 [cited by applicant]
CN 115809259 · 2023 [cited by applicant]
CN 116522389 · 2023 [cited by applicant]
EP 1662355 · 2006 [cited by applicant]
EP 3575983 · 2019 [cited by applicant]
GB 2316509 · 1998 [cited by applicant]
KR 1020060004909 · 2006 [cited by applicant]
RU 2459379 · 2012 [cited by applicant]
WO WO2012061433 · 2012 [cited by applicant]
WO WO2018170504 · 2018 [cited by applicant]
WO WO2018131031 · 2019 [cited by applicant]
WO WO2022211899 · 2022 [cited by applicant]
U.S. Appl. No. 17/186,934, filed Feb. 26, 2021, Rolle et al. [cited by applicant]
U.S. Appl. No. 17/457,797, filed Dec. 6, 2021, Ighoroje et al. [cited by applicant]
U.S. Appl. No. 17/457,802, filed Dec. 6, 2021, Rolle et al. [cited by applicant]
U.S. Appl. No. 17/457,811, filed Dec. 6, 2021, Rolle et al. [cited by applicant]
U.S. Appl. No. 17/457,824, filed Dec. 6, 2021, Vogel et al. [cited by applicant]
U.S. Appl. No. 17/457,827, filed Dec. 6, 2021, Ighoroje et al. [cited by applicant]
Inquaero.com [online], “Fulfill GDPR Art. 17 (“Right to Erasure”): SAP ILM Simplified Blocking and Deletion”, Jun. 12, 2018, retrieved on Jan. 27, 2024, retrieved from URL <https://www.inquaero.com/blog/ilm-simplified-b… [cited by applicant]
Non-Final Office Action in U.S. Appl. No. 17/702,013, mailed on Jan. 4, 2024, 9 pages. [cited by applicant]
SAP “SAP Asset Manager Security Guide” Dec. 10, 2020, 28 pages. [cited by applicant]
SAP “SAP Event Stream Processor: Security Guide” Sep. 23, 2019, 58 pages. [cited by applicant]
Wikipedia.org [online], “Information privacy” created on May 2003, retrieved on Dec. 6, 2021, retrieved from URL <https://en.wikipedia.org/wiki/Information_privacy>, 7 pages. [cited by applicant]
Wikipedia.org [online], “Master Data” created on Oct. 2006, retrieved on Dec. 6, 2021, retrieved from URL <https://en.wikipedia.org/wiki/Master_data>, 2 pages. [cited by applicant]
Wikipedia.org [online], “Personal Data” created on May 2005, retrieved on Dec. 6, 2021, retrieved from URL <https://en.wikipedia.org/wiki/Personal_data>, 7 pages. [cited by applicant]
Barreto et al., “An Efficient and Fault-Tolerant Update Commitment Protocol for Weakly Connected Replicas” INESC-ID/IST, Sep. 2005, 1059-1068. [cited by applicant]
Final Office Action in U.S. Appl. No. 18/077,493, mailed on Mar. 4, 2025, 31 pages. [cited by applicant]
Non-Final Office Action in U.S. Appl. No. 18/077,493, mailed on Nov. 5, 2024, 30 pages. [cited by applicant]