Resource Name Conflict Resolution in M2M Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In M2M communication networks, the lack of coordinated resource naming across different manufacturers leads to resource name conflicts, causing management disorders and limiting application scenarios due to the inability to ensure unique resource names.
Innovation Solution
A method where a resource creation request is processed to determine if a resource name needs to be reallocated to avoid conflicts, ensuring unique names and preventing duplicated registrations by verifying resource creation authority and checking for existing resource names within the specified position.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If resource names are provided by different manufacturers without coordination, then device compatibility and ease of manufacture are improved, but resource name conflicts and management disorders occur
Solution Approach 1:
The patent introduces a Common Service Entity (CSE) as an intermediary between application entities from different manufacturers. The CSE receives resource creation requests, checks for name conflicts against existing resources, and manages resource names centrally. This mediator enables manufacturers to independently provide devices while ensuring global resource name uniqueness through centralized coordination.
Solution Approach 2:
The system implements feedback mechanisms where the CSE checks resource creation requests against existing resource names in the database. When a conflict is detected, the system provides feedback to prevent duplicate registration. This feedback loop ensures that resource name uniqueness is maintained while allowing multiple manufacturers to contribute devices to the network.
2Reliability
If resource names are coordinated across manufacturers, then resource name uniqueness is improved, but system complexity and difficulty of operation increase
Solution Approach 1:
The CSE automatically performs resource name conflict detection and prevention without requiring manual coordination between manufacturers. The system self-services by maintaining a database of existing resource names and automatically checking new registrations against this database, eliminating the need for complex inter-manufacturer coordination protocols.
Solution Approach 2:
The Common Service Entity serves multiple functions: it acts as a registration authority, maintains a database of resource names, checks for conflicts, and manages resource creation requests. This multi-functional approach consolidates coordination complexity into a single universal entity rather than requiring distributed coordination mechanisms across multiple manufacturers.
3Ease of operation
If duplicate resource names are allowed, then ease of operation is improved, but management disorders and application errors occur
Solution Approach 1:
The system performs preliminary conflict detection before resource creation is finalized. The CSE checks the resource name against existing resources in the database before allowing registration, preventing duplicate names from being created. This preliminary action ensures application correctness is maintained while keeping the operation process simple for manufacturers.
Data Source
Figure 1~2
Figure 3~4
AI summary
The present invention discloses a method and apparatus for creating a resource. In the above method, receiving a resource creation request from a transmitting end, herein information carried in the resource creation request carries resource creation information corresponding to a resource to be created; and determining whether a first resource name needs to be reallocated to the resource to be created and creating the resource to be created according to the resource creation information. According to the technical solutions provided by the present invention, the management of resource names by a CSE is enhanced, and the uniqueness of the resource names is ensured, consequently the application scenarios of an M2M service provider are expanded, and at the same time the duplicated registration of the same resources is avoided.