Network Service Function API for Dynamic Path Selection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current communication networks lack an efficient mechanism for customers to dynamically select and manage network service functions, such as firewalls and NAT services, across different geographical locations, limiting flexibility and control over data routing.

Innovation Solution

An API is provided to expose network service functions, allowing customers to select and build service function paths through which data traffic is routed, enabling dynamic management of service function chains and routing decisions based on geographical location, loading, and service type.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If network service functions are placed near customers based on geographical location, then service delivery efficiency is improved, but customer flexibility and control over service function selection deteriorates

Engineering Contradiction:
Improveservice delivery efficiencyVSAvoidcustomer flexibility
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

An API intermediary is introduced between customers and network service functions. The API allows customers to discover, select, and configure service functions dynamically without directly managing their physical placement. This intermediary layer maintains geographical optimization for service delivery while granting customers flexible control through programmatic interfaces.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The network service function architecture is segmented into independent, selectable units that can be individually configured through the API. Customers can choose specific service functions from available options rather than receiving a monolithic service package, enabling flexible composition of services while maintaining efficient geographical deployment.

Inventive Principle:
Principle #1Segmentation

2Stability of the object's composition

If network service functions are statically deployed, then network stability is improved, but dynamic service management and customer control deteriorates

Engineering Contradiction:
Improvenetwork stabilityVSAvoiddynamic service management
Core Design Contradiction:
Stability of the object's compositionVSEase of operation

Solution Approach 1:

The system implements dynamic service function selection and configuration through the API while maintaining stable network infrastructure. Service function chains can be dynamically assembled, modified, and routed based on customer requirements without disrupting the underlying network stability. The API enables runtime configuration changes without requiring network reconfiguration.

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If comprehensive network service function information is exposed, then customer control and selection capability is improved, but system complexity and security exposure increases

Engineering Contradiction:
Improvecustomer controlVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The API serves as a controlled intermediary that exposes necessary service function information to customers while filtering and managing the complexity of underlying network infrastructure. The API abstracts complex network details into manageable service descriptors, enabling customer control without directly exposing system complexity or security vulnerabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20240089348A1Network service functions api
Publication Date: 2024.03.14 AT&T INTELLECTUAL PROPERTY I L P
  • US20240089348A1 patent drawing
  • US20240089348A1 patent drawing
  • US20240089348A1 patent drawing

AI summary

Aspects of the subject disclosure may include, for example, specification of network service functions (e.g., a firewall or network address translation appliance) to be included in a service function path. Routers in a communication network may publish information regarding reachable network service functions and an API may be exposed that provides the information regarding the reachable network service functions. Other embodiments are disclosed.