Network Element Scheduling M2M Data Delivery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional methods for communicating with machine-to-machine (M2M) devices in wireless networks are inefficient due to lack of knowledge about network and device status, leading to resource consumption and repeated transmissions, and existing overload mechanisms are ineffective in managing demand.
Innovation Solution
A network element is introduced to schedule data delivery between an application server and M2M devices based on network and policy information, including congestion, device status, and authorization, using separate sessions and protocols to optimize communication and security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional overload mechanisms such as blocking are used to protect the wireless network, then network security is improved, but communication efficiency deteriorates due to repeated transmission attempts
Solution Approach 1:
The network element performs preliminary actions by proactively notifying the application server about device status changes (registration, wake-up, location changes) before communication is needed. This allows the application server to plan transmissions in advance, avoiding repeated failed attempts and improving communication efficiency while maintaining security through controlled access.
Solution Approach 2:
The system implements feedback mechanisms where the network element continuously monitors device status and network conditions, then provides this information to the application server. This feedback loop enables dynamic adjustment of transmission strategies based on current network state, reducing wasted transmissions while maintaining reliable security controls.
2Device complexity
If applications communicate without knowledge of network and device status, then system complexity is reduced, but resource consumption increases
Solution Approach 1:
The network element acts as an intermediary between applications and M2M devices, absorbing the complexity of network and device status monitoring. Applications can communicate through this intermediary without directly handling complex status information, while the intermediary optimizes resource usage by coordinating transmissions based on real-time network and device state.
Solution Approach 2:
The network element autonomously monitors network conditions and device status without requiring application intervention. It automatically adjusts transmission scheduling and resource allocation based on observed conditions, enabling the system to optimize resource consumption without increasing application complexity.
3Adaptability or versatility
If push and pull content capabilities are provided by individual application servers in over-the-top fashion, then application flexibility is improved, but network efficiency deteriorates due to lack of device status knowledge
Solution Approach 1:
The network element serves as an intermediary that maintains application flexibility by allowing application servers to initiate push and pull operations, while simultaneously improving network efficiency by filtering and scheduling these operations based on real-time device status and network conditions. The intermediary translates application requests into optimized network operations.
4Reliability
If individual sessions are established with each device for large-scale messaging, then communication reliability is improved, but system complexity and resource usage increase
Solution Approach 1:
The network element merges multiple individual device management functions into a single centralized entity. It maintains individual communication reliability for each M2M device while consolidating session management, status monitoring, and transmission scheduling at the network element level, thereby reducing overall system complexity and resource consumption compared to distributed session management.
Data Source
Figure 1
Figure 2~3
Figure 4
AI summary
Systems and methods for communication data between an application server and at least one machine-to-machine (M2M) device via an internet network and a network are provided. An example system includes a network element configured to schedule delivery of the data between the application server and at least one M2M device based on network information. The network element is located on a boundary between the network and the internet network to which the application server communicates with the at least one M2M device.