MTC-IWF Proxy for MNO and Service Provider Interworking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile Network Operators (MNOs) face challenges in providing data services to various Machine-Type Communication (MTC) devices due to limited interoperability with MTC service providers, as they use different internal signaling protocols, necessitating a solution that allows communication without modifying these protocols.

Innovation Solution

The deployment of an MTC interworking function (MTC-IWF) Proxy, hosted on an Internetwork Packet Exchange (IPX) server, establishes connections between MTC-IWF on the MNO side and Services Capabilities Server on the MTC service provider's side, using a trigger-service provider interface, and provides identity mapping services, ensuring communication without altering internal signaling protocols, with mutual authentication and security through TLS, DTLS, or IPSec-IKEv2.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If MNOs and MTC service providers use different internal signaling protocols, then each provider maintains protocol independence and security, but interoperability between them is limited and difficult to deploy

Engineering Contradiction:
ImproveinteroperabilityVSAvoidprotocol integration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an MTC-IWF Proxy as an intermediary component that sits between the MTC-IWF of the MNO and the SCS of the MTC service provider. This proxy translates and adapts signaling protocols between different providers, enabling interoperability without requiring modifications to the internal protocols of either the MNO or the MTC service provider. The proxy acts as a mediator that handles protocol conversion, authentication, and message routing.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the signaling path into distinct functional components: the MTC-IWF of the MNO, the MTC-IWF Proxy, and the SCS of the MTC service provider. This segmentation allows each component to maintain its own protocol stack and security domain while still enabling end-to-end communication. The proxy is a separate deployable entity that can be independently configured and managed.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If MNOs modify their internal signaling protocols to enable communication with MTC service providers, then interoperability improves, but protocol integrity and security are compromised

Engineering Contradiction:
Improvecommunication capabilityVSAvoidprotocol integrity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The MTC-IWF Proxy serves as an intermediary that enables communication capability between MNOs and MTC service providers without requiring the MNO to modify its internal signaling protocols. The proxy handles all protocol adaptation, authentication, and message formatting, allowing the MNO to maintain its protocol integrity and security while still achieving seamless communication with external service providers.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If multiple MNOs and MTC service providers connect directly to each other, then full connectivity is achieved, but system complexity and authentication overhead increase significantly

Engineering Contradiction:
Improveconnectivity coverageVSAvoidconnection management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The MTC-IWF Proxy provides universal functionality that serves multiple MNOs and multiple MTC service providers through a single deployment. It handles authentication, authorization, message routing, and protocol translation for all connected providers, eliminating the need for each MNO to establish separate direct connections with each service provider. This multi-functional approach achieves full connectivity while reducing system complexity.

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

4Ease of operation

If subscriber identifiers are mapped between MNO and MTC service provider domains, then seamless user experience is achieved, but security risks increase if identifiers are exposed

Engineering Contradiction:
Improveuser experience continuityVSAvoididentifier exposure risk
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The MTC-IWF Proxy acts as a secure intermediary that performs identity mapping between MNO subscriber identifiers and MTC service provider identifiers. It maintains a mapping database that correlates these identifiers without exposing either set of identifiers to external parties. The proxy translates identifiers internally while ensuring that MNO subscriber identifiers remain confined within the MNO domain, thus maintaining user experience continuity while mitigating security risks.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9948646B1Machine type communication interworking function proxy
Publication Date: 2018.04.17 SYNIVERSE TECHNOLOGIES LLC
  • US9948646B1 patent drawing
  • US9948646B1 patent drawing
  • US9948646B1 patent drawing

AI summary

A method of establishing connectivity between a mobile network operator (MNO) and a machine type communications (MTC) service provider. A machine type communications interworking function (MTC-IWF) Proxy is hosted on an IPX network service. MTC-IWF Proxy is connected to a MTC-IWF of the MNO and is also connected to a Service Capacities Center (SCS) of the MTC service provider. MTC-IWF Proxy connects to the MNO and the MTC service providers via trigger-service provider (Tsp) interface. Identity mapping services are provided between a first set of subscriber identifiers used by the MNO and a second set of subscriber identities used by the MTC service provider. The MTC-IWF Proxy hides the internal topology and relays signaling protocols used over a Tsp interface, thus enabling the MTC service providers and MNOs communicate without modifying their internal signaling protocols.