Cross-Tenant Kernel Services With Responder Groups to Cut Resource Use
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data privacy integration protocols across multiple landscapes face inefficiencies and resource wastage due to treating dependent landscapes as veto services, leading to higher resource consumption and protocol failure risks, especially when landscapes are managed by different legal entities or data centers.
Innovation Solution
A cross-landscape integration approach that coordinates responder groups across different landscapes without requiring detailed knowledge of the dependent landscape, using a main DPI service instance to manage protocol execution by merging responder groups and sending feedback requests to a subset of applications, optimizing resource usage and reducing failure risks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If dependent landscapes are treated as veto services with full protocol execution, then data privacy integration completeness is improved, but resource consumption increases significantly
Solution Approach 1:
The patent segments the landscape into a main landscape and dependent landscapes. The dependent landscapes are divided into responder groups that only execute specific protocol commands assigned to them, rather than executing all protocol commands. This segmentation allows the system to maintain data privacy integration completeness while reducing resource consumption by limiting protocol execution to only those applications that need to respond to specific commands.
Solution Approach 2:
The patent implements partial action by having responder groups in dependent landscapes execute only a subset of protocol commands rather than the complete protocol. The main landscape's DPI service instance sends specific protocol commands to selected responder groups, and these responder groups perform only the necessary actions to provide feedback, avoiding the excessive resource consumption of full protocol execution in all landscapes.
2Measurement precision
If full protocol execution is performed in all landscapes, then data privacy integration accuracy is improved, but protocol failure risk increases
Solution Approach 1:
The patent segments protocol execution across landscapes by designating a main landscape and dependent landscapes with specific responder groups. This segmentation reduces protocol failure risk by isolating failures to specific responder groups rather than propagating them across all landscapes. The main DPI service instance coordinates these segmented executions, ensuring data privacy integration accuracy is maintained through centralized control.
Solution Approach 2:
The patent implements feedback mechanisms where responder groups in dependent landscapes execute protocol commands and send feedback responses to the main DPI service instance. This feedback loop allows the main landscape to verify data privacy integration accuracy while reducing protocol failure risk, as the centralized coordination can detect and handle issues before they propagate across all landscapes.
3Manufacturing precision
If detailed knowledge of dependent landscape configuration is required, then protocol execution precision is improved, but system complexity increases
Solution Approach 1:
The patent implements universality by designing the DPI service instance and responder group interface to handle multiple landscapes through a standardized protocol command structure. The main DPI service instance can send protocol commands to responder groups in different dependent landscapes without needing detailed knowledge of each landscape's internal configuration. This universal interface maintains protocol execution precision while reducing system complexity by abstracting away landscape-specific details.
Data Source
AI summary
The present disclosure involves systems, software, and computer implemented methods for integrating data privacy integration protocols across system landscapes. One example method includes receiving, at a first tenant of a kernel service, a message from a first application in a first landscape. Data from the message is provided to a core component of the kernel service that communicates with multiple tenants of the kernel service. The core component stores data from the message in a core storage area accessible by multiple tenants of the kernel service. The first tenant performs, in the first landscape, a first processing of the message using data in the core storage area for which the first tenant is authorized. The core component initiates a second processing of the message by a second tenant of the kernel service in a second landscape using data in the core storage area for which the second tenant is authorized.


