Service Orchestration Function for Network Resource Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing approaches to service composition in telecommunications networks are limited in managing user experience and optimizing network resources, particularly in multi-modal scenarios with rich media services, as they lack flexibility and efficient resource management.

Innovation Solution

A method and network element that combines independent service elements into compositions using service chaining applications, with a Service Orchestration Function (SOF) acting as a gateway to manage network and user events, resources, and services, enabling customization and optimal resource allocation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple independent service elements are combined to form service compositions, then user experience and service functionality are improved, but device complexity and resource management difficulty increase

Engineering Contradiction:
Improveservice composition flexibilityVSAvoidresource management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a Service Orchestration Function (SOF) as an intermediary component that mediates between service chaining applications and network resources. The SOF simplifies resource management by providing standardized interfaces and automated orchestration capabilities, allowing service compositions to be managed without directly increasing operational complexity. This mediator handles resource allocation, event coordination, and service element management centrally.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the service management system into distinct functional components: service chaining applications (SCAs), Service Orchestration Function (SOF), and independent service elements. Each component has a specific responsibility, allowing the system to handle complex service compositions through modular, manageable units. This segmentation enables independent development, deployment, and management of service elements while maintaining overall system coordination.

Inventive Principle:
Principle #1Segmentation

2Extent of automation

If service chaining applications are used to manage service compositions, then service control and coordination are improved, but processing overhead and system complexity increase

Engineering Contradiction:
Improveservice composition automationVSAvoidsystem architecture complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The Service Orchestration Function (SOF) is designed as a universal component that handles multiple functions: resource management, event detection and routing, service element coordination, and SCA execution support. This multi-functional design reduces the need for separate specialized components, thereby automating service composition management without proportionally increasing system complexity. The SOF serves as a centralized intelligence that manages diverse service elements through unified mechanisms.

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

3Productivity

If network resources are dynamically allocated for service compositions, then service efficiency and user experience are improved, but resource management complexity and overhead increase

Engineering Contradiction:
Improveservice delivery efficiencyVSAvoidresource allocation complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements feedback mechanisms where the Service Orchestration Function continuously monitors service element performance, resource utilization, and event states. Based on this feedback, the SOF dynamically adjusts resource allocation, service element activation, and SCA execution parameters. This closed-loop control enables efficient resource utilization while maintaining manageable complexity through automated decision-making based on real-time system state information.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs preliminary actions by pre-configuring service compositions and resource allocation policies before actual service delivery. Service chaining applications are prepared and validated in advance, and resource requirements are predetermined based on service composition definitions. This preliminary setup reduces runtime complexity and enables faster, more efficient service delivery without requiring complex real-time decision-making for every resource allocation decision.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9043465B2Method of providing services in a network, network element and computer program product
Publication Date: 2015.05.26 HEWLETT PACKARD ENTERPRISE DEV LP
  • US9043465B2 patent drawing
  • US9043465B2 patent drawing
  • US9043465B2 patent drawing

AI summary

The invention focuses on providing services (3) originating from a plurality of services (3a, 3b) through one central network element (4), which may be integrated in a gateway. The network element performs a method comprising:—combining pluralities of independent service elements (3a, 3b) to form respective service compositions;—providing a plurality of service chaining applications, each of said service chaining applications being associated with one of said service compositions and defining a set of network and/or user events associated with actions for controlling the independent service elements (3a, 3b) of the corresponding service composition; wherein upon triggering of at least one service composition said method further comprises:—identifying and executing a corresponding service chaining application to manage instances of the independent service elements (3a, 3b) comprised in said service composition in accordance with current network and/or user events; and—managing said network resources and said network services in accordance with a totality of current instances of independent service elements (3a, 3b).