IMS Service Gateway Architecture for Reliable Data Delivery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current techniques for delivering email messages to mobile handheld devices do not adequately address the reliability and scalability requirements specified by the 3GPP standards for IP Multimedia Subsystem (IMS) networks, particularly in terms of service architecture.

Innovation Solution

A network architecture and method that involves detecting data items, processing them to include address information, and providing this information to a service gateway in an IMS network for delivery to mobile communications devices, utilizing a remote services server and service client, with optional push or pull models and filtering schemes to manage data redirection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If current email delivery techniques are used, then delivery functionality is provided, but reliability and scalability requirements of IMS networks are not met

Engineering Contradiction:
Improveservice delivery reliabilityVSAvoidcompatibility with IMS standards
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a Service Gateway as an intermediary component between external networks and the IMS core network. This gateway translates and adapts service delivery protocols, ensuring that existing email delivery mechanisms can operate reliably within the IMS framework while maintaining compatibility with 3GPP standards. The gateway acts as a mediator that reconciles different protocol requirements and service architectures.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the service delivery architecture into distinct functional components: external network elements, Service Gateway, IMS core network elements, and user equipment. This segmentation allows each component to be optimized independently for reliability while maintaining overall system compatibility with IMS standards. The Service Gateway itself is decomposed into specific functional blocks that handle different aspects of service delivery.

Inventive Principle:
Principle #1Segmentation

2Ease of manufacture

If service architecture is simplified for ease of implementation, then deployment is easier, but scalability and reliability are compromised

Engineering Contradiction:
Improveease of service deploymentVSAvoidservice delivery reliability
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The patent implements dynamic service delivery mechanisms where the Service Gateway can adapt its behavior based on network conditions, service types, and user profiles. The architecture supports dynamic provisioning and configuration of service parameters, allowing the system to maintain reliability while remaining flexible and easy to deploy. Service capabilities can be dynamically activated or deactivated without reconfiguring the entire architecture.

Inventive Principle:
Principle #15Dynamics

3Device complexity

If service gateway functionality is consolidated, then system complexity is reduced, but scalability is limited

Engineering Contradiction:
Improveservice gateway complexityVSAvoidservice delivery scalability
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The Service Gateway functionality is segmented into distinct functional blocks including protocol translation, service routing, and message handling components. This segmentation allows the gateway to maintain manageable complexity while enabling scalable deployment through selective activation of functional blocks. Multiple service gateways can be deployed with identical or differentiated functional subsets, enhancing overall system scalability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The Service Gateway is designed as a universal platform that can handle multiple service types and protocols through a common architectural framework. This multi-functionality allows a single gateway design to serve diverse service delivery requirements without proportionally increasing complexity, thereby enabling scalable service deployment across different network scenarios.

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

Data Source

PatentUS8706075B2Architecture for service delivery in a network environment including IMS
Publication Date: 2014.04.22 MALIKIE INNOVATIONS LTD
  • US8706075B2 patent drawing
  • US8706075B2 patent drawing
  • US8706075B2 patent drawing

AI summary

In one embodiment, a network architecture is described for facilitating delivery of data items over a communications network to a mobile communications device. A remote services server disposed in an enterprise network is operable for detecting a data item at a computer system and for processing the data item into processed information that includes address information relating to the mobile communications device. A service gateway disposed in an Internet Protocol (IP) Multimedia Subsystem (IMS) network is operably connected to the remote services server for receiving the processed information using a first protocol, wherein the service gateway includes functionality to transmit the processed information using a second protocol over the IMS network based on routing information obtained from an IMS-aware node.