MUD Wireless Emission Power Profile Extension
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The increasing number of unmanaged Internet-of-Things (IoT) devices connecting to networks poses a significant security risk due to inadequate security measures, as existing technologies are not mature enough to secure devices like security cameras, smart home technology, or medical devices.
Innovation Solution
Utilizing Manufacturer Usage Descriptions (MUD) to advertise device specifications, including intended communication patterns, allowing networks to enforce context-specific access policies and monitor deviations from expected power and emissions profiles.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If MUD is used to enforce context-specific access policies and monitor device behavior, then network security is improved, but device complexity and monitoring overhead increase
Solution Approach 1:
The patent applies preliminary action by embedding the power profile information in the MUD file before device deployment. The expected power consumption values are pre-calculated and stored in the MUD file during manufacturing, allowing the network to perform anomaly detection without real-time complex calculations. This resolves the contradiction by preparing security parameters in advance, reducing runtime monitoring complexity while maintaining security.
Solution Approach 2:
The patent introduces an intermediary approach by using pre-defined power profiles as a mediator between device manufacturer intentions and network security enforcement. The power profile acts as a reference standard that simplifies the monitoring process, allowing networks to compare actual consumption against expected values without requiring complex real-time analysis, thus improving security while managing system complexity.
2Measurement precision
If real-time monitoring of power consumption and emissions profiles is implemented, then deviation detection capability is improved, but energy consumption and processing overhead increase
Solution Approach 1:
The patent applies partial action by implementing selective monitoring based on the MUD-defined power profiles. Instead of continuously monitoring all device parameters at high precision, the system monitors only the specific power consumption parameters defined in the MUD file. This allows deviation detection while reducing overall monitoring energy consumption and processing overhead.
Solution Approach 2:
The patent uses parameter changes by establishing threshold-based monitoring where the system switches between different monitoring intensities. When power consumption deviates from the expected profile beyond a threshold, the system increases monitoring precision; otherwise, it maintains lower monitoring intensity. This resolves the contradiction by dynamically adjusting monitoring resources based on actual risk levels.
3Reliability
If comprehensive device specifications are embedded in MUD files, then access policy enforcement is improved, but information overhead and processing requirements increase
Solution Approach 1:
The patent extracts only the essential power consumption parameters from comprehensive device specifications and embeds them in the MUD file. Instead of including all possible device parameters, the system selectively extracts power profile information that is critical for security enforcement. This reduces MUD file size and information overhead while maintaining effective access policy enforcement.
Solution Approach 2:
The patent applies local quality by tailoring the MUD file content to specific device types and their power consumption characteristics. Different device types receive customized power profile parameters in their MUD files, including only the parameters relevant to their operational patterns. This optimizes the balance between enforcement capability and information overhead by making each MUD file contain only necessary local information.
Data Source
AI summary
Methods and systems are described herein for detecting deviations from an expected power profile of a device. The method comprises: retrieving a manufacturer usage description (MUD) associated with the device. The MUD includes a power profile associated with the device. An expected power consumption parameter can be determined from the power profile. The method may further comprise monitoring an actual power consumption parameter of the device and comparing the expected power consumption parameter to the actual power consumption parameter. The method may further comprise determining a deviation between the power consumption parameter and the expected power consumption indicated in the power profile, and outputting a notification when the deviation is equal to or greater than a threshold value.