Virtualized Service Discovery Engine for Network Deployment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network service deployment requires new software and hardware, making it difficult to create and update services, as the software is often tightly integrated with dedicated hardware, leading to complex changes and limited flexibility in service offerings.

Innovation Solution

A virtualized services discovery and recommendation engine that receives service requests, determines relevant services and components, generates custom product recommendations, tests their functionality, and deploys them to data centers, allowing for the creation and deployment of custom applications without the need for new hardware.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If new software is created and tied to new dedicated hardware to deploy a new network service, then service functionality is achieved, but device complexity and difficulty of deployment increase

Engineering Contradiction:
Improveservice functionalityVSAvoiddeployment complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments network services into virtualized service components that can be independently deployed and managed. Instead of requiring complete new hardware for each service, the system divides services into modular virtual components that can be allocated across existing hardware infrastructure, reducing deployment complexity while maintaining service functionality.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a universal hardware platform that can host multiple different network services through virtualization. A single data center infrastructure can provide diverse network services to multiple customers simultaneously, eliminating the need for dedicated hardware per service and reducing overall device complexity.

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

2Reliability

If software is tightly integrated with dedicated hardware, then service reliability is improved, but ease of manufacture and updating deteriorate

Engineering Contradiction:
Improveservice reliabilityVSAvoidservice update ease
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The patent extracts the service logic from hardware dependencies by implementing virtualization. Service components are separated from physical hardware and executed as virtual instances on standardized platforms. This extraction maintains service reliability through consistent execution environments while enabling easy updates by simply deploying new virtual service images without hardware changes.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent uses virtual copies of service instances that can be replicated and deployed across multiple hardware platforms. Service definitions are stored as reusable templates that can be copied and instantiated repeatedly, allowing rapid service deployment and updates without reconfiguring underlying hardware, thus improving ease of manufacture while maintaining reliability through consistent service behavior.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If custom service combinations are created, then adaptability to customer needs is improved, but device complexity and testing requirements increase

Engineering Contradiction:
Improvecustom service adaptabilityVSAvoidservice configuration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements dynamic service composition where service configurations can be flexibly assembled and modified based on customer requirements. The system allows runtime configuration of service parameters and components without requiring complete redesign, enabling custom service combinations while managing complexity through automated configuration management and validation mechanisms.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent introduces an intermediary service catalog and configuration management system that mediates between customer requirements and underlying service implementations. This intermediary layer provides standardized interfaces for service composition, automatically validates configurations, and manages the complexity of custom service combinations, allowing high adaptability while reducing configuration complexity for users.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Adaptability or versatility

If service changes require updating software and hardware, then service evolution is achieved, but loss of time and productivity decrease

Engineering Contradiction:
Improveservice evolution capabilityVSAvoidservice update time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements preliminary service packaging where service definitions, configurations, and dependencies are pre-packaged as standardized virtual service images. When service evolution is needed, pre-prepared service images can be rapidly deployed without lengthy update processes. This preliminary preparation enables service evolution while minimizing update time by eliminating on-site configuration and integration work.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11138645B2Virtualized services discovery and recommendation engine
Publication Date: 2021.10.05 AT&T INTELLECTUAL PROPERTY I L P
  • US11138645B2 patent drawing
  • US11138645B2 patent drawing
  • US11138645B2 patent drawing

AI summary

Concepts and technologies are disclosed herein for a virtualized services discovery and recommendation engine. A request for a service can be received from a requestor. The request can include feature data that can define two or more features. Two or more features can be determined based on the feature data and requestor data associated with the requestor can be obtained. Two or more services that satisfy the request can be identified and a recommendation that represents the two or more services can be generated. The recommendation can include a data representation of a custom product that can include the two or more services. The recommendation can be tested to determine if the custom product functions, and the recommendation can be provided to the requestor.