Joint IoT and Proximity Service Registration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current proximity communication systems treat IoT service registration and de-registration independently of proximity service registration, leading to inefficiencies and increased overhead, as they fail to exploit dependencies and interactions between IoT and proximity services.
Innovation Solution
Proposed methods for joint IoT and proximity service registration and de-registration, including device-initiated, IoT-server-assisted, and proximity-manager-assisted approaches, where proximity information can be piggybacked during IoT registration or vice versa, allowing for more efficient resource allocation and service management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If IoT service registration and proximity service registration are treated independently, then each service can be registered separately, but signaling overhead increases and system efficiency decreases
Solution Approach 1:
The patent combines IoT service registration and proximity service registration into a single unified registration process. The network entity receives one registration request that contains both IoT service information and proximity service information, processes them together, and returns a single registration response. This merging eliminates the need for separate registration procedures, reducing signaling overhead and message exchanges while maintaining the ability to register both services independently through a unified interface.
2Adaptability or versatility
If separate registration procedures are used for IoT services and proximity services, then service independence is maintained, but system complexity and processing time increase
Solution Approach 1:
The patent implements a universal registration interface that handles both IoT service registration and proximity service registration through a single procedure. The network entity is designed to process multiple types of service information within one registration framework, making the registration system multi-functional. This universal approach reduces procedural complexity while preserving service independence, as the same interface can register different service types without requiring separate specialized procedures for each service.
3Productivity
If joint registration is implemented, then signaling overhead is reduced, but the registration protocol becomes more complex
Solution Approach 1:
The patent segments the registration information into distinct components within the unified registration request. The request includes separately identifiable IoT service information and proximity service information, allowing the network entity to process each service type independently while maintaining a single registration flow. This segmentation reduces protocol complexity by providing clear structure and organization, making it easier to implement and process joint registration without requiring a completely new complex protocol framework.
Data Source
AI summary
Disclosed herein are a variety of devices, methods, and systems for combined proximity services and Internet of Things (IoT) services registration or de-registration. An exemplary method includes one or more of receiving a device initiated IoT service registration request, wherein proximity information relating to the device is contained within the received IoT service registration request; receiving a device initiated proximity service registration request, wherein IoT service information relating to the device is contained within the received IoT service registration request; sending, from an IoT server, a proximity service registration message; and sending, from a proximity manager, an IoT service registration request.