SEAL Group Synchronization for IoT Vertical Applications
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The Service Enabler Architecture Layer (SEAL) group management service lacks procedures for fetching a list of groups that a vertical application layer (VAL) user is a member of, and for sending group creation notifications to VAL users who do not support SEAL clients.
Innovation Solution
A system and method are introduced to enable VAL clients to fetch the list of groups they are members of using a SEAL client, and to send notifications about group creations to VAL users without SEAL clients, ensuring synchronization between the UE, VAL server, and SEAL server.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If SEAL group management service provides multiple features for managing groups, then group management capability is improved, but the system complexity increases and lacks procedures for fetching group lists and sending notifications to non-SEAL users
Solution Approach 1:
The system is divided into two distinct components: a SEAL client running on the UE for fetching group lists and receiving notifications, and a VAL server for sending notifications to non-SEAL users. This segmentation allows each component to handle specific functions, improving overall system capability while maintaining manageable complexity through clear separation of concerns.
Solution Approach 2:
The SEAL client acts as an intermediary between the SEAL server and the VAL server. It receives group management information from the SEAL server, processes it locally, and then communicates with the VAL server to ensure non-SEAL users receive notifications. This intermediary role enables seamless integration between SEAL and non-SEAL users without increasing core SEAL server complexity.
2Measurement precision
If SEAL clients are required for all group management operations, then synchronization accuracy is improved, but usability deteriorates for users without SEAL clients
Solution Approach 1:
The notification system is designed to serve dual purposes: it provides precise synchronization for SEAL clients while simultaneously enabling notification delivery to non-SEAL users through the VAL server. The SEAL client handles precise synchronization when present, while the VAL server provides universal notification capability for all users regardless of SEAL client presence, making the system both accurate and universally accessible.
3Stability of the object's composition
If group information is synchronized only when SEAL client is present, then data consistency is improved, but information loss occurs for users without SEAL clients
Solution Approach 1:
The system implements a feedback mechanism where the SEAL client continuously monitors group management events from the SEAL server and triggers notifications to the VAL server when changes occur. This feedback loop ensures that group information is propagated to non-SEAL users through the VAL server, preventing information loss while maintaining data consistency through the established synchronization protocol.
Solution Approach 2:
The SEAL client performs preliminary processing of group management information received from the SEAL server before forwarding it to the VAL server. By pre-processing and preparing the notification data in advance, the system ensures that when non-SEAL users need information, it is already formatted and ready for delivery, preventing information loss without compromising data consistency.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A communication method and system for converging a 5th-Generation (5G) communication system for supporting higher data rates beyond a 4th-Generation (4G) system with a technology for Internet of Things (IoT) are provided. The embodiments herein disclose a method performed by a service enabler architecture layer (SEAL) server in a wireless communication system, the method comprising receiving, from a SEAL client, a group creation request; performing group creation based on the group creation request, creating group information during the group creation, transmitting, to a vertical application layer (VAL) server, group creation notification, and in response to receiving the group creation request, transmitting, to the SEAL client, a group creation response. The group creation notification comprises an identity list.