Virtual Network Fabrication with Segmented Containers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing virtual networks lack secure authentication, efficient request allocation, and real-time tracking, leading to potential fraud and safety concerns for users, with unregulated data sharing and requiring human intervention for service request completion.

Innovation Solution

A system and method for fabricating virtual networks by registering computing devices based on embedded information in network-registration requests, generating primary and secondary data structures to categorize and sub-categorize devices, and allocating request-notifications to suitable devices using predefined attributes for secure and efficient service provision.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If virtual networks are created over generic internet-based platforms, then network formation is simplified, but user authentication security and data sharing regulation deteriorate

Engineering Contradiction:
Improvenetwork formationVSAvoiduser authentication security
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The system segments the virtual network into multiple isolated containers, each with its own authentication rules and data sharing policies. This allows generic platforms to maintain ease of network formation while implementing secure, regulated authentication and data sharing at the container level.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

An intermediary authentication system is introduced between users and the generic internet-based platform. This intermediary layer implements verified authentication and regulates data sharing without requiring changes to the underlying generic platform, thus maintaining ease of network formation while improving security.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If service request allocation requires human intervention, then flexibility in handling complex requests is improved, but processing speed and efficiency deteriorate

Engineering Contradiction:
Improverequest handling flexibilityVSAvoidrequest processing speed
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The system implements dynamic request allocation that automatically routes simple, structured requests through algorithmic matching for fast processing, while dynamically identifying and escalating complex, unstructured requests to human reviewers. This dynamic approach optimizes both processing speed and flexibility based on request characteristics.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system applies automated allocation to the partial set of requests that can be handled algorithmically (structured, well-defined requests), while reserving human intervention for the remaining complex cases. This partial automation achieves significant productivity improvements without completely eliminating human flexibility where needed.

Inventive Principle:
Principle #16Partial or excessive action

3Ease of operation

If data sharing between computing devices is unregulated, then ease of information exchange is improved, but user safety and fraud vulnerability deteriorate

Engineering Contradiction:
Improveinformation exchangeVSAvoiduser safety
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The system implements local quality control by applying different data sharing regulations to different parts of the network based on user preferences, device types, and request characteristics. This allows easy information exchange within trusted local contexts while maintaining safety through regulated sharing at boundary interfaces.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system dynamically changes data sharing parameters (access rights, visibility, duration) based on contextual factors such as user authentication level, device trustworthiness, and request type. This enables easy information exchange under favorable conditions while preventing fraud through parameter-based restrictions when risks are detected.

Inventive Principle:
Principle #35Parameter changes

4Speed

If request allocation is performed without evaluation of computing devices, then allocation speed is improved, but service quality and reliability deteriorate

Engineering Contradiction:
Improveallocation speedVSAvoidservice quality
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The system performs preliminary evaluation and categorization of computing devices during the registration phase, storing authentication credentials, service capabilities, and trust metrics in advance. This preliminary action enables fast real-time allocation decisions without compromising service quality, as the heavy evaluation work is completed beforehand.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11831452B2System and method for fabricating virtual networks and allocating requests therein
Publication Date: 2023.11.28 COGNIZANT TECH SOLUTIONS INDIA PVT LTD
  • US11831452B2 patent drawing
  • US11831452B2 patent drawing
  • US11831452B2 patent drawing

AI summary

The present invention provides for fabricating virtual networks and allocating request-notifications therein for providing support-services securely and efficiently. In operation, a virtual network is fabricated based on network-registration requests received from plurality of computing devices. Further, a primary data structure representative of registered computing devices categorized into devices offering services and requiring services is generated based on information embedded in network-registration requests. Furthermore, a secondary data structure is generated by sub-categorising categorised computing devices based on information embedded in network-registration requests. Yet further, request-notifications for completing incoming support-requests from registered computing devices requiring services are generated. Subsequently, request-notifications are allocated based on evaluation of one or more computing devices offering services out of plurality of computing devices based on data mapping using primary data structure, secondary data structure, and predefined attributes. Finally, support-information sharing and tracking of request-notifications are enabled based on acceptance of request-notification by evaluated computing devices.