SEAL Slice Usage Analytics for Historical Network Diagnostics
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional telecommunications networks lack the ability to provide historical data on network slice usage statistics, especially in response to service degradation complaints, due to the absence of data storage for past time intervals in the service enabler architecture layer for verticals.
Innovation Solution
Implement an interface using the SEAL-X reference point between the application data analytics enablement server and the application data analytics enablement service consumer, enabling the transmission of slice usage statistics data requests and responses, including mandatory and optional information elements, to facilitate retrieval and reporting of network slice diagnostics.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If conventional service enabler architecture layer for verticals is used, then the system maintains simplicity and follows standard protocols, but the system cannot store or provide historical slice usage statistics data for diagnostic purposes
Solution Approach 1:
The patent implements preliminary action by establishing a data storage mechanism that proactively stores slice usage statistics data in advance. The Application Data Analytics Enablement Server continuously collects and stores historical data related to network slice usage, performance metrics, and service quality indicators, making this information available before any diagnostic queries arise. This eliminates the need for reactive data collection and ensures historical information is always accessible for troubleshooting service degradation issues.
2Reliability
If historical data storage is implemented in the service enabler architecture layer, then diagnostic capability is improved, but the architecture complexity increases beyond conventional standards
Solution Approach 1:
The patent introduces an intermediary approach by leveraging existing standardized interfaces and protocols within the service enabler architecture layer. Rather than creating a completely new storage system, the solution uses established data collection mechanisms and interfaces that already exist in the network architecture, adding storage and retrieval capabilities through extensions to existing components rather than introducing entirely new complex subsystems.
Solution Approach 2:
The patent applies universality by designing the data storage and retrieval mechanism to serve multiple functions simultaneously. The same storage infrastructure supports not only historical slice usage statistics for diagnostics but also real-time monitoring, performance optimization, billing verification, and service quality assurance. This multi-functional approach reduces overall system complexity compared to having separate specialized systems for each function.
3Ease of operation
If slice usage statistics data is stored for past time intervals, then service consumer can perform checks on service degradation, but data storage resources are consumed
Solution Approach 1:
The patent implements local quality by selectively storing and retaining slice usage statistics data based on specific criteria such as service type, network slice priority, degradation severity thresholds, and regulatory requirements. Rather than uniformly storing all data indefinitely, the system applies different retention policies and storage qualities to different data categories, optimizing resource usage while ensuring critical diagnostic information is preserved with appropriate detail and duration.
Data Source
Figure 1~3
Figure 4~5
AI summary
The invention relates to a method for using a service enabler architecture layer for verticals, SEAL, in a vertical application layer implementation, VAL implementation, for providing communication services to a user equipment, using a vertical application layer server via a telecommunications network, especially for supporting and providing slice usage statistics data regarding at least one network slice, wherein the user equipment is a vertical application layer user equipment comprising a vertical application layer client, VAL client, and a service enabler architecture layer for verticals, SEAL, functionality client, wherein the service enabler architecture layer for verticals comprises an application data analytics enablement server and a network slice capability enablement server being responsible for or related to the at least one network slice, wherein, in order for supporting and for providing, by the application data analytics enablement server, slice usage statistics data towards an application data analytics enablement service consumer entity, the method comprises the following steps: -- in a first step, the application data analytics enablement service consumer entity transmits a slice usage statistics data request to the application data analytics enablement server in order to be provided with slice usage pattern statistics data, -- in a second step, the application data analytics enablement server transmits a slice usage statistics data response to the application data analytics enablement service consumer entity, the slice usage statistics data response comprising slice usage statistics data.