M2M Inter-Network Routing via DNS Resource Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing Machine-to-Machine (M2M) communication networks face challenges in enabling communication between devices and applications from different M2M service providers, as current standards do not define how an application or Service Capability Layer (SCL) from one network can retrieve or exchange information with entities in another network, especially when they are not connected via the same Gateway or Network entities.
Innovation Solution
A method and system are introduced to facilitate communication between M2M devices and applications from different networks by using a RESTful architecture style, where entities register with their respective network nodes, and requests are routed through these nodes to reach entities in other networks, utilizing a tree-like structure for resource addressing and routing, and introducing the concept of announced resources for inter-network discovery and routing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If devices are connected to different M2M service provider networks, then network coverage and device connectivity increase, but communication between devices from different networks becomes impossible
Solution Approach 1:
The patent introduces a Domain Name System (DNS) as an intermediary mechanism that enables resolution of device identifiers across different M2M service provider networks. The DNS stores mapping information between device identifiers and network-specific addressing information, allowing devices from different networks to communicate without direct knowledge of each other's network infrastructure. This mediator resolves the contradiction by providing a universal lookup service that works across network boundaries.
Solution Approach 2:
The patent implements a universal addressing scheme where device identifiers are designed to be network-agnostic. The same device identifier can be used across multiple M2M service provider networks, and the DNS system provides a universal resolution mechanism that translates these identifiers into network-specific addresses. This universality allows devices to maintain consistent identities while communicating across different network domains.
2Ease of operation
If a centralized registration system is implemented for inter-network communication, then routing between networks is enabled, but system complexity and management overhead increase
Solution Approach 1:
The patent implements preliminary registration of device identifiers with the DNS system during device provisioning or initial activation. This advance registration stores the mapping between device identifiers and their network-specific addressing information before actual inter-network communication is needed. By performing this registration action in advance, the system eliminates the need for complex real-time discovery and negotiation mechanisms, simplifying the overall routing process.
Solution Approach 2:
The patent creates a simplified virtual representation of device addressing information in the DNS system, which is a copy of the actual network-specific addressing data. This copied information in the DNS allows devices to resolve addresses without needing direct access to or knowledge of the complex underlying network infrastructure. The DNS copy provides a simplified interface that abstracts away the complexity of inter-network routing.
Data Source
AI summary
Machine-to-Machine (M2M) communication has been described for communication in a single network in among others publications from the European Telecommunications Standards Institute (ETSI). The publications describe a single network with defined entities, a resource structure and protocols. According to the invention, a solution is described for communication between entities residing in different M2M networks. Entities residing in a first M2M network requiring information of an entity in another second M2M network submit a request with a target ID pointing to the entity in the second M2M network. The request is forwarded to the network node of the first network. The network node of the first network checks whether the target ID matches with an announced resource in the network node of the first network. On a match the request is routed towards the network node of the second M2M network according to an address available in a REstful structure comprising the announced resource. The network node of the second network routes the request further towards the second entity. On reception of the request the second entity processes the request and returns a reply via the path created by the previous steps.