Personal IoT Network Joining by Service Compatibility Matching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods and systems do not define procedures for joining or releasing Personal Internet of Things (IoT) network elements (PINE) into or from a personal IoT network (PIN) based on service requests, leading to inefficiencies in communication setup and management.
Innovation Solution
A method and system for service-based joining of PINE into a PIN, involving a PIN network apparatus that broadcasts PIN information, receives join requests, determines compatible PINEs, and facilitates communication between them, while also allowing PINEs to request release from the PIN.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If PINEs join PIN without service-based procedures, then network elements can be connected, but communication setup efficiency deteriorates due to lack of structured joining mechanisms
Solution Approach 1:
The patent segments the PINE joining process into distinct phases: service requirement declaration, service matching, joining procedure, and release procedure. This structured segmentation improves communication setup efficiency by providing clear procedural steps while managing complexity through organized process division.
Solution Approach 2:
The patent implements preliminary action by requiring PINEs to declare their service requirements before joining the PIN. The network controller pre-matches services and prepares joining procedures in advance, which streamlines the actual connection process and improves overall setup efficiency.
2Reliability
If service matching is performed during PINE joining, then service compatibility is ensured, but processing time increases due to service determination requirements
Solution Approach 1:
Service matching is performed as a preliminary action during the joining procedure. The network controller determines service compatibility before finalizing the connection, ensuring reliability while integrating the matching process into the overall joining timeline rather than as a separate post-connection step.
Solution Approach 2:
PINEs autonomously declare their own service requirements and capabilities in their joining requests. This self-service approach reduces the burden on the network controller, allowing faster service matching while maintaining compatibility through structured declaration formats.
3Ease of operation
If structured joining and release procedures are implemented, then network management is improved, but system complexity increases due to additional protocols
Solution Approach 1:
The patent creates universal joining and release procedures that can be applied to any PINE regardless of specific service type. These multi-functional protocols handle diverse service requirements through a unified framework, improving ease of operation while avoiding the need for service-specific complex protocols.
Solution Approach 2:
The network controller acts as an intermediary that manages the complexity of service matching and joining procedures. It mediates between PINEs' service requirements and PIN resources, simplifying the interface for individual PINEs while handling protocol complexity centrally.
4Adaptability or versatility
If PINEs can request release from PIN, then network flexibility is enhanced, but management overhead increases due to release procedure handling
Solution Approach 1:
PINEs can autonomously initiate release requests when their service requirements change or they leave the network. This self-service capability enhances network flexibility by allowing dynamic reconfiguration without manual intervention, while the standardized release procedure keeps management overhead manageable.
Data Source
AI summary
The disclosure relates to a 5G, 6G, or personal IoT network communication system for supporting a higher data transmission rate. The method of PEMC comprises: transmitting a first message comprising information related to a personal internet of things network (PIN); receiving, from a first personal internet of things network element (PINE), a first joining request message comprising information on a supported service of the first PINE; determining whether to add the first PINE in the PIN based on the information on the supported service; and transmitting, to the first PINE, a first joining accept message comprising at least one identifier (ID) of at least one PINE in the PIN based on a determination that the first PINE is added in the PIN.


