Self-driving Content Distribution Platform for Dynamic Network Automation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current datacenter and cloud network architectures face challenges in managing dynamic and instant connectivity among millions of software instances, requiring unique network pathways with varying tolerances for packet loss, delay, and overhead, due to the disconnection between application development and network services, leading to complexity and inflexibility.

Innovation Solution

The introduction of a self-driving content distribution (SDCD) platform that enables applications to define and manage network services directly, using special packets with embedded content delivery instructions, allowing applications to control data processing and forwarding without relying on intermediate servers, and allowing the network to serve as both a data forwarding and processing environment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional network services are used with static configuration, then network infrastructure is simple and centralized, but network flexibility and adaptability to application-specific needs deteriorate

Engineering Contradiction:
Improvenetwork flexibilityVSAvoidnetwork architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Applications autonomously define and manage their own network services by embedding content delivery instructions directly in data packets. The network switches execute these instructions without requiring centralized controller programming, enabling applications to self-configure network pathways based on their specific needs for packet loss tolerance, delay requirements, and overhead constraints.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Instead of the traditional model where network controllers program switch behavior to implement services, this invention inverts the approach by allowing applications to directly program switch behavior through embedded instructions in packets. The control flow reverses from network-to-application to application-to-network, eliminating the need for intermediate controllers.

Inventive Principle:
Principle #13The other way round (Inversion)

2Productivity

If millions of software instances require instant dynamic connectivity, then application responsiveness improves, but network connection management complexity increases

Engineering Contradiction:
Improveconnection establishment speedVSAvoidconnection management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The invention extracts the network service definition and connection management logic from centralized controllers and places it directly within application code. Each software instance embeds its own network delivery instructions in packets, eliminating the need for complex centralized provisioning and enabling instant activation and removal of connections without controller intervention.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Applications pre-define their network service requirements and delivery instructions during application development. These instructions are embedded in packets before transmission, allowing network switches to immediately execute the correct forwarding behavior without requiring real-time configuration or controller programming when connections are established.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If centralized network controllers program switch behavior, then network service provisioning is centralized and simple, but application-specific network customization deteriorates

Engineering Contradiction:
Improveapplication-specific network customizationVSAvoidnetwork service provisioning simplicity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

Applications autonomously define their own network service requirements by embedding content delivery instructions directly in data packets. Each application specifies its unique needs for packet loss tolerance, delay requirements, and overhead constraints, and the network switches execute these instructions without requiring centralized controller programming or complex provisioning procedures.

Inventive Principle:
Principle #25Self-service

4Productivity

If intermediate servers are used for data forwarding, then network control and security are centralized, but resource utilization efficiency and reliability deteriorate

Engineering Contradiction:
Improveresource utilization efficiencyVSAvoidsystem reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The invention removes intermediate servers and controllers from the data forwarding path. Network switches directly execute content delivery instructions embedded in packets, eliminating the need for server-based service logic and reducing points of failure. This distributes control across the network infrastructure itself rather than concentrating it in vulnerable intermediate nodes.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The invention replaces intermediate servers with network switches that directly execute embedded instructions. Network switches act as the intermediary that processes and forwards packets based on application-defined rules, eliminating the need for application servers to perform network forwarding functions and improving both resource utilization and system reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10681177B2Self-driving content distribution
Publication Date: 2020.06.09 TARASENKO IGOR
  • US10681177B2 patent drawing
  • US10681177B2 patent drawing
  • US10681177B2 patent drawing

AI summary

A platform provides a novel mechanism of implementation and operation for network functions such as switching, routing, firewalling, load balancing, isolation, etc. In the prior art, all the network functions are defined and instantiated within the software- or hardware-based network appliances. In the present invention, all the network appliances execute only the content delivery instructions received from business applications. Virtual service templates are used by application developers to describe different sets of application communication roles. The new platform includes a controller that stores those templates, authorizes interactions between platform components, collects information about the running state of platform components, and assists applications with the use of the platform. In accordance with the role assignments, each application may request role-specific configuration from the controller, use it to generate content delivery instructions, and send data alongside with the instructions, in the form of a special packet, into the network.