MBC Traffic Control for Misbehaving IoT Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current IoT devices can misbehave, leading to unauthorized access and resource wastage in networks, with existing technologies failing to detect and mitigate such issues effectively until a radio connection is established, resulting in significant resource utilization and potential network congestion.
Innovation Solution
A method where a Mobility Management Control Entity (MBC) communicates with an access node (eNodeB) to issue messages indicating traffic reduction, allowing the eNodeB to block, reject, or restrict traffic from misbehaving devices, using reserved identity spaces and Globally Unique Mobile Management Entity Identifiers (GUMMEI) to identify and isolate faulty devices during the radio connection setup process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If the network waits until radio connection is established to detect misbehaving devices, then the detection accuracy is improved, but the network resource wastage increases
Solution Approach 1:
The patent applies preliminary action by implementing device behavior monitoring and anomaly detection before radio connection establishment. The network detects misbehaving devices during the access request phase using criteria such as repeated access attempts, invalid device identities, or abnormal signaling patterns, and prevents connection establishment for these devices. This early detection and prevention mechanism stops resource wastage before it occurs, while maintaining detection accuracy through predefined detection rules and collaborative filtering among network nodes.
2Loss of energy
If the network blocks traffic from misbehving devices early, then the resource wastage is reduced, but the device complexity increases
Solution Approach 1:
The patent applies segmentation by dividing the traffic blocking function into multiple independent components: behavior monitoring modules at different network nodes, anomaly detection engines with separate detection rules, and enforcement mechanisms that operate independently. Each component handles specific aspects of misbehaving device identification and response, allowing the system to scale and manage complexity through modular architecture rather than monolithic implementation.
Solution Approach 2:
The patent introduces intermediary elements such as behavior monitoring entities and anomaly detection filters that mediate between device access requests and the core network. These intermediaries analyze device behavior, make blocking decisions, and enforce traffic restrictions without requiring complex modifications to the core network infrastructure. The intermediaries absorb and manage system complexity while providing simple interfaces to both devices and core network elements.
3Reliability
If the network monitors all IoT devices for misbehaviour, then the reliability is improved, but the processing overhead increases
Solution Approach 1:
The patent applies partial action by implementing selective monitoring that focuses on specific behavior patterns and device types most likely to exhibit misbehaving characteristics. Rather than uniformly monitoring all devices with equal intensity, the system applies enhanced monitoring only to devices showing preliminary anomaly indicators, while using lighter monitoring for normal devices. This selective approach maintains high reliability for detecting actual threats while reducing overall processing overhead through intelligent resource allocation.
Data Source
AI summary
A mobile management control entity, MBC, being adapted for communicating with an access node, AN, such as an eNodeB, the MB being adapted for issuing a message comprising an indication (7) of a type of traffic to be reduced to or from the AN, wherein the traffic reduction comprises one of rejecting, ignoring or selectively restricting traffic. An Access Node, AN the AN being adapted for receiving (7) from the MBC an indication (7) of a type of traffic to be reduced, receiving (210, 150) a message (150) of a UE associated with the indication of a type of traffic to be reduced, rejecting, ignoring or selectively restricting (212) traffic to or from the UE belonging to the indication of type of traffic to be reduced.