Neutral Computing Instance for Secure Remote Network Data Sharing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In multi-instance remote network management platforms, sharing information between computational instances is inefficient due to the need for manual or out-of-band data transfer, leading to outdated data across multiple instances, especially when dealing with numerous entities, and poses security risks due to direct data intermingling.

Innovation Solution

A neutral computing instance acts as an intermediary, allowing secure, indirect data sharing through standardized interfaces like REST or SOAP, where providers publish updates and consumers subscribe, ensuring authentication and authorization, thus avoiding direct data exchange between instances.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If direct data sharing between computational instances is implemented, then data sharing efficiency is improved, but data security and privacy are compromised due to direct data intermingling

Engineering Contradiction:
Improvedata sharing efficiencyVSAvoiddata security risk
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces a neutral computational instance as an intermediary between provider and recipient instances. This neutral instance receives data from providers, validates authentication and authorization, and distributes data to recipients. This mediator approach enables efficient data sharing while maintaining security by preventing direct data intermingling between entities.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Object-affected harmful factors

If manual or out-of-band data transfer is used between instances, then data security is maintained, but data sharing efficiency deteriorates and data becomes outdated

Engineering Contradiction:
Improvedata securityVSAvoiddata sharing efficiency
Core Design Contradiction:
Object-affected harmful factorsVSProductivity

Solution Approach 1:

The patent implements continuous data sharing through automated mechanisms where provider instances publish updates and consumer instances subscribe to receive them. The neutral instance continuously validates and distributes data, eliminating manual transfer processes and ensuring data remains current across all instances without compromising security.

Inventive Principle:
Principle #20Continuity of useful action

Solution Approach 2:

The system enables self-service data sharing where instances automatically authenticate, authorize, and transfer data without manual intervention. Provider instances autonomously publish updates and consumer instances autonomously subscribe and receive data, improving efficiency while maintaining security through automated validation.

Inventive Principle:
Principle #25Self-service

3Object-affected harmful factors

If information is provided to multiple computational instances individually, then data security is maintained, but the complexity of data management increases and redundant data collection occurs

Engineering Contradiction:
Improvedata securityVSAvoiddata management complexity
Core Design Contradiction:
Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

The neutral computationalinstance serves multiple functions simultaneously: it acts as a data collector from providers, a validation server for authentication and authorization, a distribution hub to recipients, and a security gateway. This multi-functional design simplifies data management complexity while maintaining security across multiple instances.

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

Data Source

PatentUS11729170B2Efficient and secure communication between computational instances of a remote network management platform
Publication Date: 2023.08.15 SERVICENOW INC
  • US11729170B2 patent drawing
  • US11729170B2 patent drawing
  • US11729170B2 patent drawing

AI summary

A remote network management platform may include a provider computing instance, a recipient computing instance, and a neutral computing instance including persistent storage that defines a table and fields therein, and where the neutral computing instance is configured to: (i) receive, by way of a first software interface, data from the provider computing instance, where the data is an update to a field within the table; (ii) validate that the provider computing instance is permitted to update the field; (iii) write a representation of the data to the field; (iv) receive, by way of a second software interface, a request from the recipient computing instance for the data; (v) validate that the recipient computing instance is permitted to access the field; and (vi) transmit the data as stored in the field to the recipient computing instance.