IP Library Granted Patent US 12,189,813
Granted Patent B2
US 12,189,813 · App. 18/073,164 · Granted Jan 7, 2025

Multiple synonymous identifiers in data privacy integration protocols

Inventors: Benny Rolle (Reinhardshagen, DE); Matthias Vogel (Saarbrücken, DE)
Assignee: SAP SE
G06F21/6245
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,189,813
App. No.
18/073,164
Granted
Jan 7, 2025
Kind
B2
Abstract

The present disclosure involves systems, software, and computer implemented methods for using multiple synonymous identifiers in data privacy integration protocols. One example method includes identifying a request to initiate a protocol in a multiple-application landscape for an object with an identifier. A determination is made that at least one context-using application participant of the protocol relies on a context-providing application participant of the protocol for resolving the identifier to a local identifier local to a context of the context-providing application participant. A resolution request is sent to context-providing application participants that can provide resolution for an identifier for at least one context-using application. A local identifier corresponding to the identifier that is local to the context of the context-providing application participant is received from each context-providing application participant. A protocol work package that includes a resolved local identifier to is sent to each context-using application participant.

Claims (55)

1. A computer-implemented method comprising:

identifying a request to initiate a data privacy integration protocol in a multiple-application landscape for an object with a first identifier;

determining that at least one context-using application participant of the data privacy integration protocol relies on a context-providing application participant of the data privacy integration protocol for resolving the first identifier to a local identifier local to a context of the context-providing application participant;

sending a resolution request to each context-providing application participant that can provide resolution for at least one context-using application;

receiving, from each context-providing application participant in response to the resolution request, a local identifier corresponding to the first identifier that is local to the context of the context-providing application participant;

sending a first data privacy integration protocol work package that includes the local identifier to each context-using application participant;

receiving a first data privacy integration protocol response from each context-using application participant that includes a result of a respective context-using participant executing the first data privacy integration protocol work package using the local identifier;

sending a second data privacy integration protocol work package that includes the first identifier to each protocol application participant other than context-using application participants;

receiving a second data privacy integration protocol response from each non-context-using application participant that includes a result of a respective non-context-using participant executing the second data privacy integration protocol work package using the first identifier; and

determining a data privacy integration protocol result based on evaluating first data privacy integration protocol responses received from context-using application participants and second data privacy integration protocol responses received from non-context-using application participants.

2. The computer-implemented method of claim 1 , wherein the data privacy integration protocol is an integrated end of purpose protocol and the request is to determine whether the object can be blocked.

3. The computer-implemented method of claim 1 , wherein the data privacy integration protocol is an aligned purpose disassociation protocol and the request is to determine whether a purpose can be disassociated from the object.

4. The computer-implemented method of claim 1 , wherein the data privacy integration protocol is an integrated personal data retrieval protocol, the object corresponds to a data subject, and the request is to gather data concerning the data subject.

5. The computer-implemented method of claim 1 , wherein a first context-using application participant understands the local identifier of a first context-providing protocol participant.

6. The computer-implemented method of claim 5 , wherein the first context-providing protocol participant replicates data including an object with the local identifier to the first context-using protocol participant.

7. The computer-implemented method of claim 1 , wherein the first identifier is a common identifier understood by multiple applications of the multiple-application landscape.

8. The computer-implemented method of claim 7 , wherein the common identifier is assigned to the object by an object redistribution service.

9. The computer-implemented method of claim 8 , wherein the object redistribution service is a master data integration service.

10. The computer-implemented method of claim 1 , wherein the first identifier is received in a request from a requester that initiates the data privacy integration protocol.

11. The computer-implemented method of claim 1 , wherein an initial request from a requester includes a second identifier different from the first identifier, the method further comprising:

sending a second resolution request to a first context-providing application participant to resolve the second identifier to a common identifier understood by multiple applications of the multiple-application landscape;

receiving the common identifier as the first identifier in response to the second resolution request; and

modifying the initial request to include the first identifier rather than the second identifier.

12. The computer-implemented method of claim 1 , further comprising:

receiving a second request that includes a second identifier from a first context-using application;

sending a second resolution request to a first context-providing application to resolve the second identifier to a local identifier; and

providing the local identifier in a third data privacy integration work package to a second context-using application.

13. The computer-implemented method of claim 1 , further comprising receiving, from a first context-providing application participant in response to the resolution request, along with the local identifier, a second local identifier corresponding to the first identifier that is local to a second context understood by the context-providing application participant.

14. A system comprising:

one or more computers; and

a computer-readable medium coupled to the one or more computers having instructions stored thereon which, when executed by the one or more computers, cause the one or more computers to perform operations comprising:

identifying a request to initiate a data privacy integration protocol in a multiple-application landscape for an object with a first identifier;

determining that at least one context-using application participant of the data privacy integration protocol relies on a context-providing application participant of the data privacy integration protocol for resolving the first identifier to a local identifier local to a context of the context-providing application participant;

sending a resolution request to each context-providing application participant that can provide resolution for at least one context-using application;

receiving, from each context-providing application participant in response to the resolution request, a local identifier corresponding to the first identifier that is local to the context of the context-providing application participant;

sending a first data privacy integration protocol work package that includes the local identifier to each context-using application participant;

receiving a first data privacy integration protocol response from each context-using application participant that includes a result of a respective context-using participant executing the first data privacy integration protocol work package using the local identifier;

sending a second data privacy integration protocol work package that includes the first identifier to each protocol application participant other than context-using application participants;

receiving a second data privacy integration protocol response from each non-context-using application participant that includes a result of a respective non-context-using participant executing the second data privacy integration protocol work package using the first identifier; and

determining a data privacy integration protocol result based on evaluating first data privacy integration protocol responses received from context-using application participants and second data privacy integration protocol responses received from non-context-using application participants.

15. The system of claim 14 , wherein the data privacy integration protocol is an integrated end of purpose protocol and the request is to determine whether the object can be blocked.

16. The system of claim 14 , wherein the data privacy integration protocol is an aligned purpose disassociation protocol and the request is to determine whether a purpose can be disassociated from the object.

17. The system of claim 14 , wherein the data privacy integration protocol is an integrated personal data retrieval protocol, the object corresponds to a data subject, and the request is to gather data concerning the data subject.

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:

identifying a request to initiate a data privacy integration protocol in a multiple-application landscape for an object with a first identifier;

determining that at least one context-using application participant of the data privacy integration protocol relies on a context-providing application participant of the data privacy integration protocol for resolving the first identifier to a local identifier local to a context of the context-providing application participant;

sending a resolution request to each context-providing application participant that can provide resolution for at least one context-using application;

receiving, from each context-providing application participant in response to the resolution request, a local identifier corresponding to the first identifier that is local to the context of the context-providing application participant;

sending a first data privacy integration protocol work package that includes the local identifier to each context-using application participant;

receiving a first data privacy integration protocol response from each context-using application participant that includes a result of a respective context-using participant executing the first data privacy integration protocol work package using the local identifier;

sending a second data privacy integration protocol work package that includes the first identifier to each protocol application participant other than context-using application participants;

receiving a second data privacy integration protocol response from each non-context-using application participant that includes a result of a respective non-context-using participant executing the second data privacy integration protocol work package using the first identifier; and

determining a data privacy integration protocol result based on evaluating first data privacy integration protocol responses received from context-using application participants and second data privacy integration protocol responses received from non-context-using application participants.

19. The computer-readable medium of claim 18 , wherein the data privacy integration protocol is an integrated end of purpose protocol and the request is to determine whether the object can be blocked.

20. The computer-readable medium of claim 18 , wherein the data privacy integration protocol is an aligned purpose disassociation protocol and the request is to determine whether a purpose can be disassociated from the object.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 1, 2022
From: ROLLE, BENNY; VOGEL, MATTHIAS
To: SAP SE
Reel/Frame 061945/0525 →
Continuity (1)
Related Publication 20240184914A1 · Jun 6, 2024
References Cited (88)
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 7831567B2 · Luther et al. · 2010 [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 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 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 20070089117A1 · Samson · 2007 [cited by applicant]
US 20080060051A1 · Lim · 2008 [cited by applicant]
US 20080174425A1 · Torning · 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 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 20160292455A1 · Jebara · 2016 [cited by examiner]
US 20170006135A1 · Siebel et al. · 2017 [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 20190236294A1 · McDonald et al. · 2019 [cited by applicant]
US 20190236334A1 · Babushkin · 2019 [cited by applicant]
US 20200019728A1 · Rolle · 2020 [cited by applicant]
US 20200285766A1 · Jois 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 20220043917A1 · Rolle · 2022 [cited by applicant]
US 20220050834A1 · Rolle et al. · 2022 [cited by applicant]
US 20220050920A1 · Rolle · 2022 [cited by applicant]
US 20220058333A1 · Rolle · 2022 [cited by applicant]
US 20220100755A1 · Rolle · 2022 [cited by applicant]
US 20220207429A1 · Haribhakti et al. · 2022 [cited by applicant]
US 20220277023A1 · Rolle et al. · 2022 [cited by applicant]
US 20220300837A1 · Shmelkin et al. · 2022 [cited by applicant]
US 20220309052A1 · Rolle · 2022 [cited by applicant]
US 20230081785A1 · Zhang · 2023 [cited by applicant]
US 20230177182A1 · Rolle · 2023 [cited by examiner]
US 20230237192A1 · Kahan · 2023 [cited by examiner]
US 20230244637A1 · Wu · 2023 [cited by applicant]
CA 3096061 · 2023 [cited by applicant]
CN 114092253 · 2022 [cited by applicant]
CN 115809259 · 2023 [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,816, filed Dec. 6, 2021, Vogel 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]
U.S. Appl. No. 17/680,717, filed Feb. 25, 2022, Rolle et al. [cited by applicant]
U.S. Appl. No. 17/680,741, filed Feb. 25, 2022, Rolle et al. [cited by applicant]
U.S. Appl. No. 17/680,759, filed Feb. 25, 2022, Rolle et al. [cited by applicant]
U.S. Appl. No. 17/680,858, filed Feb. 25, 2022, Rolle. [cited by applicant]
U.S. Appl. No. 17/702,013, filed Mar. 23, 2022, Rolle. [cited by applicant]
U.S. Appl. No. 17/718,770, filed Apr. 12, 2022, Rolle. [cited by applicant]
U.S. Appl. No. 18/049,063, filed Oct. 24, 2022, Hesse et al. [cited by applicant]
Wikipedia.org [online], “Hyperscale computing” created on May 2013, retrieved on Dec. 1, 2022, retrieved from URL <https://en.wikipedia.org/wiki/Hyperscale_computing>, 2 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]
Wikipedia.org [online], “Personal Identifier” created on Feb. 2007, retrieved on Dec. 1, 2022, retrieved from URL <https://en.wikipedia.org/wiki/Personal_identifier>, 3 pages. [cited by applicant]
U.S. Appl. No. 18/074,745, filed Dec. 5, 2022, Vogel et al. [cited by applicant]
U.S. Appl. No. 18/077,476, filed Dec. 8, 2022, Rolle et al. [cited by applicant]
U.S. Appl. No. 18/077,493, filed Dec. 8, 2022, Rolle et al. [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]
Non-Final Office Action in U.S. Appl. No. 17/457,811, mailed on Dec. 20, 2023, 27 pages. [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]
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]
Cited By (2)
US 12,417,294 US 12,499,263