MTC Service Class Routing for Trigger Messages

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing message routing technologies in machine-type communications (MTC) face challenges in efficiently handling infrequent and small data transmissions, as well as group-based communications, due to the diverse requirements of MTC devices, which are not adequately addressed by current hierarchical network architectures and server systems.

Innovation Solution

A computer network node determines a machine-to-machine (MTC) service class for registered devices based on registration data and associates it with specific network routes, allowing for efficient routing of messages, such as trigger messages, through the use of service classes that account for device properties and applications, thereby optimizing message delivery.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If default routing methods are used for MTC devices, then network architecture simplicity is maintained, but message delivery efficiency and reliability deteriorate due to diverse MTC device requirements not being addressed

Engineering Contradiction:
Improvemessage delivery efficiencyVSAvoidnetwork architecture complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments MTC devices into different service classes (e.g., Class 0, Class 1, Class 2, Class 3) based on their communication characteristics and requirements. Each service class is associated with specific routing rules and network routes, allowing the network to handle different types of MTC traffic differently. This segmentation enables efficient message delivery for each device type while maintaining overall network manageability through structured classification.

Inventive Principle:
Principle #1Segmentation

2Reliability

If service classes with specific network routes are implemented for MTC devices, then message routing efficiency improves, but device complexity and network configuration complexity increase

Engineering Contradiction:
Improvemessage delivery reliabilityVSAvoidrouting configuration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements preliminary action by pre-configuring service classes and their associated network routes during device registration or network setup. The MTC server pre-determines the appropriate service class for each device based on its characteristics and pre-establishes the routing rules. When messages need to be delivered, the pre-configured routes are simply followed, eliminating the need for complex real-time routing decisions and reducing operational complexity despite the detailed configuration.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP2920928B1Trigger message routing according to a service class
Publication Date: 2020.06.17 CISCO TECHNOLOGY INC
  • EP2920928B1 patent drawingFigure 1A~1C
  • EP2920928B1 patent drawingFigure 2
  • EP2920928B1 patent drawingFigure 3

AI summary

In one embodiment, a machine type communication (MTC) device can receive registration associated with a new device upon the new device registration for a computer network. The MTC device can further determine a machine-to-machine (MTM) service class for the new device based on the registration data with the service class associated with at least one network route for messages destined for the new device. The MTC device can further receive a trigger message destined for the device and route the trigger message according to the network route associated with the determined MTM service class.