Distributed Asset Identity Management for Privacy Compliance

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The hub and spoke model for deploying software and services is inefficient, particularly for customers who require control over their data and privacy, as it centralizes resource management, making it difficult for partners and customers to coordinate and comply with privacy laws like HIPAA and Sarbanes-Oxley.

Innovation Solution

A system and method for managing distributed offerings that allows deployment of software and services from vendor, partner, or customer systems, enabling flexible business process abstraction, asset registration, and privacy control, where offerings are deployed based on business logic rather than hardware or network architecture, allowing customers to maintain control over their data within their proprietary networks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If the hub and spoke model is used for deploying software and services, then resource management is centralized and delivery is streamlined, but it becomes difficult for partners and customers to coordinate and comply with privacy laws

Engineering Contradiction:
Improvedelivery efficiencyVSAvoidprivacy control flexibility
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent segments the centralized hub-and-spoke architecture into distributed offering modules that can be deployed across multiple systems (vendor systems, partner systems, customer systems). Each system operates semi-independently with its own offering registry and deployment capabilities, allowing localized privacy control while maintaining overall system coordination. This segmentation enables partners and customers to manage their own data according to privacy laws like HIPAA and Sarbanes-Oxley while still participating in the distributed offering delivery network.

Inventive Principle:
Principle #1Segmentation

2Device complexity

If data is collected and stored centrally at the provider's hub, then analysis and processing are simplified, but customer privacy and data security control are compromised

Engineering Contradiction:
Improvedata management simplicityVSAvoidprivacy risk
Core Design Contradiction:
Device complexityVSObject-affected harmful factors

Solution Approach 1:

The patent implements local quality by allowing each participating system (vendor, partner, customer) to maintain local offering registries and data storage capabilities tailored to their specific privacy and security requirements. Customer systems can implement localized data handling policies that comply with applicable privacy laws while still enabling offering deployment and data collection where appropriate. This localizes data management complexity to where it is most effectively handled while reducing centralized privacy risks.

Inventive Principle:
Principle #3Local quality

3Productivity

If offerings are deployed from the provider's central hub to customer assets, then resource utilization is optimized, but partner coordination and customer autonomy are reduced

Engineering Contradiction:
Improveresource utilizationVSAvoidpartner coordination difficulty
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent creates a universal distributed offering management framework that can operate across multiple types of systems (vendor systems, partner systems, customer systems) with different levels of autonomy. The framework provides common interfaces and protocols that enable resource optimization while accommodating diverse operational requirements. Partner systems can function as independent offering providers with their own registries and deployment capabilities, eliminating coordination bottlenecks while maintaining resource efficiency through standardized interactions.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS8655757B1System and method for assigning a unique asset identity
Publication Date: 2014.02.18 ORACLE AMERICAN INC
  • US8655757B1 patent drawing
  • US8655757B1 patent drawing
  • US8655757B1 patent drawing

AI summary

Methods, systems, and articles of manufacture consistent with the present invention provide for managing a customer asset, which is a hardware or software component of a customer device, in a data processing system having an offering platform program. The customer asset's is discovered by an asset manager, and an asset identity is assigned. The asset identity is stored persistently.