M2M Device Identifier Segmentation for Network Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current communication systems face challenges in efficiently identifying and managing machine-to-machine (M2M) devices connected to user equipment, leading to difficulties in data communication and device triggering within networks.
Innovation Solution
The method involves assigning a device connection identifier that includes a portion of the user equipment identifier, allowing for the transmission of this identifier to network operators, enabling data communication and device triggering based on this identifier, thereby facilitating the management and control of M2M devices within the network.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If traditional communication systems are used for M2M devices, then device identification and management become complex and inefficient, but implementing a new identifier assignment mechanism increases system complexity
Solution Approach 1:
The identifier system is segmented into two parts: the user equipment identifier (from the wireless network) and the device identifier (generated by the local host). This segmentation allows the network operator to efficiently identify and manage devices without handling complete unique identifiers for each M2M device, thus improving productivity while managing complexity through division of responsibilities.
Solution Approach 2:
The local host acts as an intermediary between the wireless network and M2M devices. It generates device identifiers and assigns them to connected devices, serving as a mediator that simplifies the overall system architecture. This intermediary approach improves device identification efficiency while distributing complexity to the local host rather than centralizing it in the network operator system.
2Adaptability or versatility
If multiple M2M devices connect through a single user equipment, then network resource sharing improves, but device-specific data communication becomes difficult
Solution Approach 1:
The identifier is segmented into the user equipment identifier (for network resource sharing) and the device identifier (for device-specific communication). This segmentation enables both multiple devices to share the user equipment's network connection while maintaining unique identification for each device, thus achieving both network resource sharing and device-specific data communication simultaneously.
Solution Approach 2:
The device identifier is nested within the complete identifier structure alongside the user equipment identifier. The complete identifier effectively nests both levels of identification (user equipment level and device level), allowing the system to maintain hierarchical relationships where multiple devices can share user equipment resources while preserving individual device identity for targeted communication.
3Measurement precision
If complete device identifiers are transmitted through the network, then device identification precision improves, but network traffic and processing load increase
Solution Approach 1:
The device identifier component is extracted from the complete identifier and assigned by the local host rather than being transmitted through the network. This extraction reduces the amount of data that needs to be transmitted and processed in the network while maintaining the precision of device identification, as the network only needs to handle the user equipment identifier portion.
Solution Approach 2:
The local host performs the device identifier assignment and management function itself, rather than relying on the network operator system to generate and manage complete device identifiers. This self-service approach reduces network traffic and processing load on the operator's infrastructure while maintaining accurate device identification through the locally generated identifiers.
Data Source
AI summary
Systems and methods for control and triggering of machine to machine (M2M) devices (e.g., smart meters). More specifically how to allow an M2M service provider (e.g., utility company) to use an operator's network to communicate with the M2M device connected with a UE/GW associated with the operator's network. The M2M service provider may receive identification of the UE/GW, but not for the M2M device. By transmitting an identifier for the M2M device along with an identifier for the UE/GW, the network operator may define establish and maintain a communication path specific to M2M devices. Similar techniques may be incorporated to allow the M2M service provider to locate and trigger the M2M device.