MTC Device Software Update via Control Plane Messaging
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for software updating MTC devices using IP connectivity fail to leverage the benefits of non-IP data communications, leading to inefficient battery usage and complex architecture in MTC devices.
Innovation Solution
Implementing software updates for MTC devices through non-IP data delivery (NIDD) and non-access stratum (NAS) messaging, utilizing control plane network nodes like MME, SCEF, and AS to transmit and manage software updates without requiring an IP protocol stack.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If IP connectivity is used for software updates, then software updates can be delivered, but battery consumption increases and device architecture becomes more complex
Solution Approach 1:
The patent extracts the IP protocol stack requirement from the MTC device by using non-IP data delivery (NIDD) messaging over the control plane. The software update is delivered through NAS messaging between the MME and MTC device, eliminating the need for IP connectivity and protocol stack in the MTC device, thereby reducing battery consumption and architectural complexity while maintaining reliable software update delivery.
2Reliability
If IP protocol stack is implemented in MTC device, then software updates can be received, but device architecture becomes more complex
Solution Approach 1:
The patent removes the IP protocol stack requirement from the MTC device architecture by implementing software updates through non-IP control plane messaging. The MME acts as an intermediary that handles the software update delivery using NAS messages, allowing the MTC device to receive software updates without implementing IP protocol stack, thus simplifying device architecture while ensuring reliable update reception.
3Reliability
If background file transfer mechanism is used, then software updates can be transmitted, but non-IP data communication benefits are not utilized
Solution Approach 1:
Instead of using the conventional user plane background file transfer mechanism that requires IP connectivity, the patent inverts the approach by using the control plane for software update delivery. The MME directly sends software updates to the MTC device using NAS messaging, a non-IP communication method, thereby enabling software update transmission while fully utilizing non-IP data communication capabilities and their associated benefits.
Data Source
AI summary
Methods, systems, and computer readable media for machine type communications/Internet of things (MTC/IoT) device updating are described. One method for machine type communications (MTC) device software updating includes receiving, by a control plane network node including at least one processor and via non-Internet protocol data delivery (NIDD) or non-access stratum (NAS) messaging, hardware and software version information regarding an MTC device. The method includes identifying, by the control plane network node, that a software update is available for the MTC device. The method further includes, in response determining that a software update is available for the MTC device, transmitting, by the control plane network node and via NIDD or NAS messaging, the software update to the MTC device. The method further includes receiving, at the control plane network node and via NIDD or NAS messaging, status information regarding delivery of the software update to the MTC device or installation of the software update by the MTC device.