Interconnect Border Control Node for Enterprise Service Provisioning

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current service provisioning systems for Next Generation Corporate Networks (NGCNs) face challenges in supporting IMS-style registration procedures, leading to complex data management and limited redundancy and load sharing capabilities, especially when connecting to IMS platforms.

Innovation Solution

The method involves using an interconnect border control network node to connect the enterprise network to the service provisioning network, allowing for centralized control and execution of enterprise services without requiring IMS-style registration, thereby enabling advanced originating and terminating services through a standard IMS Application Server.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If IMS-style registration procedures are used to connect NGCN to IMS platform, then service provisioning is enabled, but data management complexity increases and device complexity increases

Engineering Contradiction:
Improveservice provisioning capabilityVSAvoiddata management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts the registration procedure from the service provisioning process. By using surrogate registration where the SBC registers the NGCN site identifier rather than individual user identifiers, the complex IMS-style registration is separated from the service provisioning function, enabling services without full registration support.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The SBC acts as an intermediary between the NGCN and IMS platform. It performs surrogate registration to enable service provisioning without requiring the NGCN to support full IMS-style registration procedures, thereby reducing data management complexity while maintaining service capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If surrogate registration is used to enable services without IMS-style registration, then adaptability improves, but customer data distribution increases complexity

Engineering Contradiction:
Improvecompatibility with non-IMS NGCNVSAvoidcustomer data distribution
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges customer data management into the HSS/UPSF, consolidating what would otherwise be distributed across multiple entities. The SBC stores minimal NGCN site identifier data, while the HSS/UPSF holds the complete customer data, simplifying the overall data distribution architecture.

Inventive Principle:
Principle #5Merging (Combining)

3Ease of operation

If individual user registration is required for services, then service execution is enabled, but redundancy and load sharing capabilities are limited

Engineering Contradiction:
Improveservice execution capabilityVSAvoidredundancy and load sharing
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent segments the registration approach by registering the NGCN site identifier at the SBC level rather than individual user identifiers. This segmentation enables the system to treat the entire NGCN as a single registrant, allowing redundancy and load sharing across multiple NGCN sites without requiring individual user registration.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8601141B2Providing enterprise services in a service provisioning network
Publication Date: 2013.12.03 KONINK KPN NV
  • US8601141B2 patent drawing
  • US8601141B2 patent drawing
  • US8601141B2 patent drawing

AI summary

A method and a system for providing enterprise services in a service provisioning network is described wherein service provisioning network is connected through at least one trunk to at least one enterprise network. The method comprises the steps of: providing a service request associated with an enterprise network; associating trunk information to said service request; routing said service request to an application server comprising one or more enterprise services associated with said enterprise network; and, said application server executing at least one enterprise service using said trunk information.