Visited MTC Interworking Function Roaming Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current communication systems face challenges in supporting inter-operator charging and security in roaming scenarios for machine-type communication (MTC) due to the exposure of internal network topology and potential fake trigger messages, especially when MTC interworking functions are located in the home network.

Innovation Solution

Implementing a Visited MTC Interworking Function (V-MTC-IWF) in the visited network, which acts as a gatekeeper, supports charging functionality, and scrutinizes messages before forwarding them to serving nodes, thereby hiding internal network topology and enhancing security by filtering out fake messages.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If MTC-IWF is located in the home network, then device triggering functionality is enabled, but internal network topology is exposed and security threats increase

Engineering Contradiction:
Improvedevice triggering functionalityVSAvoidsecurity threats
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces a visited MTC-IWF as an intermediary component located in the visited network between the home MTC-IWF and the serving nodes. This intermediary receives trigger messages from the home MTC-IWF, validates them, and forwards them to the appropriate serving nodes, thereby preventing direct exposure of internal network topology while maintaining device triggering functionality

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the MTC-IWF functionality into two separate components: a home MTC-IWF that handles trigger message generation and a visited MTC-IWF that handles message validation and forwarding. This segmentation allows the system to maintain triggering functionality while isolating the security-critical validation functions in the visited network

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If MTC-IWF is located in the home network, then device triggering is supported, but inter-operator charging requires additional functionality in serving nodes

Engineering Contradiction:
Improvedevice triggeringVSAvoidcharging functionality
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges the charging functionality into the visited MTC-IWF component located in the visited network. The visited MTC-IWF generates charging data records and handles inter-operator charging procedures, eliminating the need for separate charging functionality in serving nodes and reducing overall system complexity

Inventive Principle:
Principle #5Merging (Combining)

3Productivity

If trigger messages are sent directly from MTC-IWF to serving nodes, then device triggering efficiency is improved, but fake trigger messages can bombard the network

Engineering Contradiction:
Improvetriggering efficiencyVSAvoidmessage authenticity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements preliminary validation of trigger messages at the visited MTC-IWF before they are forwarded to serving nodes. The visited MTC-IWF checks the authenticity and validity of incoming trigger messages, filtering out fake messages in advance. This preliminary action maintains triggering efficiency for legitimate messages while blocking malicious ones

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP2865199B1Machine type communication interworking function
Publication Date: 2021.08.25 NOKIA SOLUTIONS & NETWORKS OY
  • EP2865199B1 patent drawingFigure 1
  • EP2865199B1 patent drawingFigure 2
  • EP2865199B1 patent drawingFigure 3

AI summary

Communication systems, such as an evolved packet system, may benefit from various interworking functions. In particular, certain communication systems in which machine type communication devices are deployed may benefit from a machine type communication interworking function in a visited network. A method may comprise receiving, from a network element, a request in a visited machine type communication interworking function. The method may also comprise processing the request in the visited machine type communication interworking function. The method may further comprise sending a response to the network element in response to the request.