Transparent SFID Switching for Dynamic Service Function Chains

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing communication networks face challenges in efficiently managing dynamic end-to-end Service Function Chains (SFCs) and re-orchestration of Service Function Identifiers (SFIDs) due to lack of transparent switching mechanisms.

Innovation Solution

Implementing a programmable middleware that uses a programmable application programming interface (API) to send configuration information to Service Function Endpoints (SFEs), register them with identifiers, and dynamically update SFIDs when mappings change, enabling transparent switching of SFIDs for dynamic end-to-end slicing and re-orchestration of SFCs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional SFID management methods are used, then system simplicity is maintained, but network flexibility and dynamic re-orchestration capability deteriorate

Engineering Contradiction:
Improvenetwork flexibilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a Service Function Identifier Translation (SFIT) entity as an intermediary component that sits between service function endpoints and the network core. This SFIT entity translates between old SFIDs and new SFIDs, enabling dynamic re-orchestration without requiring changes to existing service function endpoints. The intermediary handles the complexity of SFID mapping and translation, thereby improving network flexibility while containing system complexity within the translation entity rather than propagating it throughout the entire network.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a virtual copy of the SFID mapping relationship through the SFIT entity's translation tables. Instead of directly modifying SFIDs at all endpoints, the system maintains a copied representation of SFID mappings in the SFIT entity, which then translates requests. This copying approach allows dynamic updates to SFID mappings without requiring direct modification of numerous endpoint devices, thereby enhancing adaptability while managing complexity through centralized virtual mapping.

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If SFID mappings are updated dynamically, then service re-orchestration capability is improved, but mapping consistency and reliability may deteriorate

Engineering Contradiction:
Improveservice re-orchestration capabilityVSAvoidmapping consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements feedback mechanisms where the SFIT entity monitors SFID mapping relationships and automatically detects inconsistencies or conflicts. When dynamic updates are made to SFID mappings, the feedback system verifies that the changes maintain proper mapping consistency and do not create conflicts. This feedback loop ensures that service re-orchestration can proceed dynamically while reliability is maintained through automated consistency checking and conflict detection.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent employs beforehand cushioning by implementing validation and verification procedures before SFID mapping updates are fully applied. The SFIT entity performs preliminary checks on proposed mapping changes to ensure they will not compromise consistency or create conflicts. This prior cushioning approach allows dynamic re-orchestration while protecting mapping consistency by preventing problematic changes from being applied in the first place.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

3Reliability

If transparent switching of SFIDs is implemented, then service continuity is improved, but implementation complexity and deployment difficulty worsen

Engineering Contradiction:
Improveservice continuityVSAvoiddeployment difficulty
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The patent extracts the SFID translation and switching functionality from the core network elements and service function endpoints, consolidating it into a dedicated SFIT entity. This extraction allows transparent switching to be implemented in a localized manner rather than requiring system-wide modifications. Service continuity is improved through the SFIT entity's ability to handle translations seamlessly, while deployment difficulty is reduced by concentrating the implementation complexity in a single extractable component rather than distributing it across multiple network elements.

Inventive Principle:
Principle #2Taking out (Extraction)

4Extent of automation

If programmable middleware is introduced for SFID management, then automation and dynamic control are improved, but system complexity and operational overhead worsen

Engineering Contradiction:
Improvedynamic controlVSAvoidoperational overhead
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The patent implements self-service capabilities where the SFIT entity automatically manages SFID translation without requiring manual configuration or intervention. The programmable middleware within the SFIT entity autonomously handles mapping updates, translations, and consistency checks based on predefined policies and received instructions. This self-service approach improves automation and dynamic control while reducing operational overhead by eliminating the need for manual SFID management operations.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12578947B2Methods and apparatus for transparent switching of service function identifiers
Publication Date: 2026.03.17 INTERDIGITAL PATENT HOLDINGS INC
  • US12578947B2 patent drawing
  • US12578947B2 patent drawing
  • US12578947B2 patent drawing

AI summary

Method, apparatus, and systems for transparent switching of service function identifiers in wireless communications are provided. In an example, a method for wireless communications comprises sending configuration information to one or more Service Function Endpoints (SFEs) using a programmable application programming interface (API), implementing the API as a programmable middleware, and registering each of the one or more SFEs with a respective identifier according to a service description at the programable middleware.