Network Service Management via Intermediary Mediator

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current solutions lack effective deployment and management of end-to-end virtual extranet web service architectures, particularly in communication network provider spaces, due to scalability issues, high availability, and speed requirements, as well as difficulties in integrating diverse security and policy controls across multiple enterprises.

Innovation Solution

A network service management apparatus with a policy enforcement module, security module, SOAP proxy, UDDI proxy, and service handling module, implemented in client gateways and network controllers, to enforce access rules, secure communication, and manage network services across a services network, utilizing standards like SOAP, UDDI, and XML for interoperability and security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If ad-hoc approaches are used for web services interactions between enterprises, then compatibility and communication can be achieved, but device complexity and integration difficulty increase significantly

Engineering Contradiction:
ImprovecompatibilityVSAvoidintegration difficulty
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a services network as an intermediary infrastructure that mediates web services interactions between enterprises. This services network provides standardized interfaces, security policies, and communication protocols that enable compatibility without requiring direct point-to-point integration between enterprises, thereby reducing integration complexity while maintaining versatility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The services network implements universal interfaces and standardized protocols (such as SOAP, XML) that can handle multiple types of web services interactions across different enterprises. This multi-functional framework allows the same infrastructure to support various communication patterns and service types, achieving adaptability without proportionally increasing complexity.

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

2Reliability

If enterprise-class products are deployed to meet security and policy requirements, then security control is improved, but scalability and speed to meet core network requirements deteriorate

Engineering Contradiction:
Improvesecurity controlVSAvoidscalability
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the services network into distributed service providers and service consumers connected through standardized interfaces. This segmentation allows security policies to be enforced at individual service boundaries rather than requiring centralized enterprise-class security infrastructure for the entire network, enabling scalability while maintaining security control through modular policy enforcement.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The services network enables dynamic parameter changes in security policies and service configurations without requiring deployment of new enterprise-class security products. Policies can be modified, updated, and enforced in real-time through the standardized framework, allowing the system to scale while adapting security parameters to meet varying requirements.

Inventive Principle:
Principle #35Parameter changes

3Ease of operation

If point-to-point web services connections are established between enterprises, then direct communication is achieved, but the number of connections and system complexity increase exponentially

Engineering Contradiction:
Improvedirect communicationVSAvoidnumber of connections
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The services network acts as a mediator that replaces direct point-to-point connections between enterprises. Instead of establishing numerous direct connections, enterprises connect to the services network which handles routing, communication, and coordination, thereby maintaining ease of direct communication while dramatically reducing the number of physical connections required.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Speed

If firewalls are opened for business traffic flow between applications, then communication speed is improved, but security vulnerabilities and access control difficulties increase

Engineering Contradiction:
Improvecommunication speedVSAvoidsecurity vulnerabilities
Core Design Contradiction:
SpeedVSObject-affected harmful factors

Solution Approach 1:

The services network serves as a secure intermediary that enables fast communication without requiring firewalls to be opened between enterprises. The intermediary enforces security policies, authentication, and access control at the network level, allowing rapid data transmission while maintaining security boundaries and preventing direct exposure of internal systems.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP2547069B1Network services infrastructure systems and methods
Publication Date: 2015.11.04 ALCATEL LUCENT SA
  • EP2547069B1 patent drawingFigure 1
  • EP2547069B1 patent drawingFigure 2
  • EP2547069B1 patent drawingFigure 3

AI summary

Managing network services in a services network. A registry manager coupled to a client gateway interface receives requests regarding information in a services registry and provides requested information responsive thereto. Further the registry manager receives information associated with a network service to be made available in the services network and publishes the received information in the services registry. Also the registry manager receives subscriptions for modifications in the services registry and sends notifications of the modifications.