Remote IMS Service Invocation for Cloud Telecom Sessions

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for integrating application servers in telecommunication networks, such as PBX integration and Network to Network Interface (NNI), are complex and offer limited flexibility, especially when hosting in cloud environments, requiring substantial modifications or provisioning of new network nodes.

Innovation Solution

A method and system that utilize a modified IMS Service Control (ISC) interface with a secure signaling channel to communicate between an invocation server and a remote application server, allowing seamless integration and service provisioning without the need for complex setup or additional network nodes, using a simplified SIP interface and X-sip headers to manage telecommunications sessions efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If application servers are hosted in a remote network using NNI integration, then service flexibility is improved, but network complexity increases due to requiring HSS, CSCF, HLR nodes

Engineering Contradiction:
Improveservice flexibilityVSAvoidnetwork complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts the essential service control functionality from the complex IMS network nodes (HSS, CSCF, HLR) and consolidates it into a single invocation server. This allows application servers to be hosted in remote networks without requiring the full suite of IMS network nodes, thereby maintaining service flexibility while reducing network complexity.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The invocation server acts as an intermediary between the telecommunications network and remote application servers. It handles the complex signaling and service control logic, allowing simple application servers to be deployed in remote networks without requiring them to implement complex NNI interfaces or require full IMS network infrastructure.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of manufacture

If PBX integration methods are used to host application servers, then setup complexity is reduced, but service flexibility and adaptability are limited

Engineering Contradiction:
Improvesetup simplicityVSAvoidservice flexibility
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The invocation server implements a universal interface that can handle multiple service types and communication protocols. It supports both simple PBX-like integration and complex IMS service control through a single standardized interface, allowing application servers to be deployed with simple setup while maintaining access to a wide range of services and protocols.

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

Solution Approach 2:

The system dynamically adapts the level of integration complexity based on service requirements. For simple services, it operates in a PBX-like mode with minimal setup, while for complex services, it automatically engages full IMS service control capabilities through the invocation server, providing both simplicity and flexibility as needed.

Inventive Principle:
Principle #15Dynamics

3Reliability

If application servers are hosted within the core network, then network reliability is maintained, but cloud deployment flexibility and scalability are limited

Engineering Contradiction:
Improvenetwork reliabilityVSAvoidcloud deployment flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the service control functionality from the application server hosting. The invocation server remains within the trusted core network to maintain reliability and security, while application servers can be hosted in remote cloud networks. This segmentation allows the system to leverage cloud scalability and flexibility while maintaining core network reliability through the segregated control plane.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The invocation server acts as a secure intermediary that maintains reliable control within the core network while enabling flexible cloud deployment. It handles authentication, authorization, and service control logic, allowing application servers to run in untrusted remote networks while maintaining the reliability and security guarantees of the core network through the mediating invocation server.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP4231608B1Methods of managing services for a telecommunications session and servers, computer software and systems for performing the methods
Publication Date: 2026.01.28 VODAFONE GROUP SERVICES LTD
  • EP4231608B1 patent drawingFigure 1
  • EP4231608B1 patent drawingFigure 2
  • EP4231608B1 patent drawingFigure 3

AI summary

A method of managing services for a telecommunications session handled by a telecommunications network (130) comprises receiving, at an invocation server in a remote network (100), wherein the remote network (100) is remote from the telecommunications network (130), a first message initiating a telecommunications session, wherein the message is received from the telecommunications network (100) via a secure signalling channel (140). The method further comprises determining, based on the first message, one or more services required for the telecommunications session. The method further comprises sending, based on the one or more services required, a second message to an application server (120) in the remote network (100), wherein the application server (120) is configured to provide one or more services, wherein the second message causes the application server (120) to provide the one or more services for the telecommunications session.