Optimization of MTC Device Trigger Delivery

Abstract

A network node (21), which is placed within a core network, stores a list of network elements (24) capable of forwarding a trigger message to a MTC device (10). The network node (21) receives the trigger message from a transmission source (30, 40) placed outside the core network, and then selects, based on the list, one of the network elements to forward the trigger message to the MTC device (10). The MTC device (10) validates the received trigger message, and then transmits, when the trigger message is not validated, to the network node (21) a reject message indicating that the trigger message is not accepted by the MTC device (10). Upon receiving the reject message, the network node (21) forwards the trigger message through a different one of the network elements, or forwards the reject message to transmission source (30, 40) to send the trigger message through user plane.

Description

TECHNICAL FIELD[0001]The present invention relates to new functions for UE (User Equipment) / MTC (Machine-Type-Communication) device and MTC-IWF (MTC-Interworking Function), in order to provide an efficient mechanism for MTC device trigger delivery.BACKGROUND ART[0002]MTC device triggering is a feature defined by the 3GPP's (Third Generation Partnership Project's) LTE-A (Long Term Evolution-Advanced) (see e.g. NPL 1). The MTC device triggering is sent from SCS (Services Capability Server) or SME (Short Message Entities) to network and terminated at MTC device. MTC device triggering message can be sent in NAS (Non-Access-Stratum) messages, SMS (Short Message Service), or user plane message.[0003]MTC device trigger may not reach MTC device due to security protection check failure at UE. For example, it is described in NPL 2 that some NAS messages (e.g. Identity Request, Authentication Request, Detach Accept, etc.) with no protection can be processed by UE. If a fake MTC device trigger ...

AI Technical Summary

Benefits of technology

The present invention allows for better handling of triggering events in a network. It allows for the identification of a suitable path for delivering a trigger to a destination device, reducing the likelihood of unnecessary network traffic and wasted battery consumption. It also allows for early selection of the most suitable path, optimizing network traffic flow. Overall, this results in more efficient and effective trigger delivery.

Problems solved by technology

MTC device trigger may not reach MTC device due to security protection check failure at UE.

If a fake MTC device trigger is embedded in such NAS messages, it can cause MTC device battery consumption, and potential mis-behaviour / mis-configuration of the MTC device.

This will cause 1) overloading the network, 2) MTC device battery consumption.

Similarly problem should be considered that when the user plane message carrying trigger is not properly protected.

There is also considered an issue for SMS based trigger.

Images