Dual MAC Addressing for IoT Scalability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing MAC address space is limited, particularly in the context of growing IoT networks, leading to a need for alternative methods to manage MAC addressing that do not rely on centralized or scattered control, and current methods fail to efficiently assign unique MAC addresses at the manufacturing or provisioning stage.
Innovation Solution
The use of two MAC addresses: a globally unique group MAC address (gMAC) and a unique MAC address (uMAC) within a local group, where the uMAC is embedded as an IP header option, allowing devices to communicate within a group without conflicts and conserving the global MAC address space.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If a single global MAC address space is used for all devices, then network addressing is simple and standardized, but the address space depletes quickly as device numbers grow (especially in IoT)
Solution Approach 1:
The patent divides the MAC address space into two segments: a group MAC address (gMAC) that is shared among devices in the same group, and a unique MAC address (uMAC) that is specific to each device within the group. This segmentation allows multiple devices to share a common gMAC, effectively expanding the usable address space without requiring each device to have a globally unique MAC address.
Solution Approach 2:
The patent introduces a new dimension to MAC addressing by embedding the uMAC within the IP header options field rather than using it as the primary Data Link layer address. This creates a hierarchical addressing structure where the gMAC operates at the Data Link layer for basic communication, while the uMAC operates at the Network layer within IP options for device differentiation, effectively adding an addressing dimension.
2Reliability
If centralized control methods (BOOTP, DHCP, server-based assignment) are used for MAC address assignment, then address uniqueness is ensured, but system complexity and control overhead increase
Solution Approach 1:
The patent enables devices to perform self-configuration by automatically generating their own uMAC addresses and incorporating them into IP packets without requiring centralized MAC address assignment. Devices autonomously manage their addressing by embedding the uMAC in IP header options, eliminating the need for BOOTP, DHCP, or server-based MAC assignment systems while maintaining address uniqueness within their groups.
3Stability of the object's composition
If static MAC address assignment is used, then address consistency is maintained, but adaptability to dynamic network conditions and IoT scalability is reduced
Solution Approach 1:
The patent introduces dynamic elements to MAC addressing by allowing devices to dynamically generate and embed their unique MAC addresses (uMAC) within IP header options rather than using static, pre-assigned addresses. This dynamic approach enables devices to adapt to changing network conditions and scalability requirements while maintaining consistency through the structured gMAC/uMAC separation and standardized embedding methodology.
Data Source
AI summary
Method for MAC addressing in a device operating in OSI layers 2 and 3, the method comprising the steps of: receiving a connection request (400) from a first 2MAC client (102) wherein the request comprises: the client's (102) first MAC address gMAC (406) being globally unique, the client's (102) second MAC address uMAC (407) being unique within a local 2MAC clients (102, 105) group; and a target's IP address and port (408); establishing (401) a connection between the server (108) and the first 2MAC client (102). Additionally, there is presented a method for MAC addressing in a device operating in OSI layer 2 or OSI layers 2 and 3, the method comprising: constructing (253) a packet from a first 2MAC client (102) targeted at another 2MAC client (105) wherein the packet comprises: the client's (102) first MAC address gMAC (406) being globally unique and the client's (102) second MAC address uMAC (407) being unique within a local 2MAC clients (102, 105) group.