SEAL Location Reporting for Shared Vertical Service Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless communication systems lack a unified service enabler layer to efficiently support vertical applications across different industries, leading to redundant development of auxiliary services and inefficiencies in deploying vertical services.
Innovation Solution
A Service Enabler Architecture Layer (SEAL) is introduced to provide a common set of capabilities shared by multiple vertical applications, including location management, group management, configuration management, and identity management, with a generic functional model supporting both on-network and off-network deployments.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a unified service enabler layer is introduced, then development efficiency and service deployment efficiency are improved, but system complexity increases
Solution Approach 1:
The SEAL introduces a unified service enabler layer that provides common auxiliary services (location management, group management, configuration management, identity management) that can be shared across multiple vertical applications and industries. This universal layer eliminates the need for each vertical application to implement its own auxiliary services, thereby improving development efficiency while the modular architecture manages system complexity through standardized interfaces and protocols.
2Device complexity
If vertical applications are developed without a unified service enabler layer, then system complexity is reduced, but redundancy in auxiliary services increases
Solution Approach 1:
The SEAL merges common auxiliary services into a unified service enabler layer that is shared across multiple vertical applications. Instead of each vertical application having separate implementations of location management, group management, configuration management, and identity management, these services are combined into a single standardized layer that serves multiple purposes and reduces overall service redundancy in the system.
3Adaptability or versatility
If industry-specific auxiliary services are developed for each vertical application, then service customization is improved, but development time and resource consumption increase
Solution Approach 1:
The SEAL architecture segments the service framework into a common service enabler layer and vertical application-specific layers. The common layer provides standardized auxiliary services (location, group, configuration, identity management) that can be reused across industries, while vertical applications can still customize their specific services by building upon this standardized foundation. This segmentation reduces development time by eliminating redundant work while maintaining adaptability through the modular structure that allows industry-specific extensions.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method of a service enabler architecture layer (SEAL) can include receiving a location reporting configuration at a first user equipment (UE) from a location management server of the SEAL. The location reporting configuration can indicate at least one location reporting event for triggering a first location information report from a first location management client at the first UE to the location management server. The first location information report can be transmitted to the location management server from the first location management client at the first UE in response to the at least one location reporting event occurring. The first location information report can include an identity of the first UE, an identity of the at least one location reporting event that triggers the first location information report, first location information of the first UE, and a first timestamp corresponding to the first location information of the first UE.