M2M Device Connection Management via Network Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing mobile communication networks face challenges in managing connections for M2M devices, which have distinct requirements different from human user devices, such as low mobility and periodic data transmission, leading to potential network overload and inefficient resource allocation.
Innovation Solution
An M2M device identifies itself to the network, allowing a network node to control the setup and maintenance of connections based on this indication, routing requests to specialized nodes for handling M2M traffic, and implementing specific routines for types of M2M devices to optimize resource usage and reduce unnecessary traffic.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If M2M devices use the same connection management as human user devices, then network infrastructure remains simple, but network overload occurs and resource allocation becomes inefficient
Solution Approach 1:
The patent segments the network into dedicated M2M service areas and separates M2M device management from conventional human user management. This involves creating separate routing areas, service areas, and management entities (such as MME-m for M2M devices) that handle M2M traffic independently, preventing congestion in the core network while maintaining simplified management for each segment.
Solution Approach 2:
The patent introduces intermediary network elements such as M2M servers, service area routers, and dedicated gateways that act as mediators between M2M devices and the core network. These intermediaries buffer M2M traffic, translate M2M protocols to standard protocols, and manage connection setup/detachment without requiring direct core network involvement for every M2M operation.
2Productivity
If M2M devices transmit data at scheduled intervals, then data exchange requirements are met, but network traffic increases during peak times causing overload
Solution Approach 1:
The patent implements periodic action by enabling M2M devices to transmit data at scheduled intervals rather than continuously. The network manages connection states based on these periodic transmission patterns, maintaining connections during active periods and putting them to sleep during idle periods, thereby reducing overall network traffic while ensuring data is available when needed.
Solution Approach 2:
The patent applies preliminary action by pre-establishing connection parameters, routing paths, and resource allocations before M2M devices need to transmit data. The network pre-configures service areas, allocates dedicated resources, and sets up transmission schedules in advance, allowing M2M devices to communicate efficiently without causing sudden network overload during actual data transmission.
3Ease of operation
If M2M devices have low mobility and stationary operation, then connection setup is simplified, but connection maintenance becomes less efficient without mobility-based optimization
Solution Approach 1:
The patent applies local quality by tailoring connection management parameters specifically for stationary or low-mobility M2M devices. Instead of using generic connection management, the system implements location-based connection persistence, maintaining connections longer for stationary devices while using mobility-triggered connection setup for moving devices. This localized optimization improves maintenance efficiency without complicating the overall setup process.
Data Source
Figure 1~3
Figure 2
Figure 4~5
AI summary
The invention relates to the setting up and/or maintaining of a connection between an M2M device and a mobile communication network. In order to be able to adapt the connection management to the requirements of the M2M device, it is suggested that the M2M device transmits an indication that is an M2M device to the mobile communication network and that at least one network node of the mobile communication network controls the setting up and/or the maintaining of the connection based on the indication. In particular, the network node may route a request for setting up the connection to a further network node based on the indication.