Service Session Analysis Using Snapshot Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems face challenges in automatically analyzing and optimizing end user service sessions due to the vast variety and volume of services, lack of holistic models for managing service expectations, experiences, and contexts, and performance issues with semantic techniques.

Innovation Solution

A method and apparatus that utilize a semantic knowledge base to analyze and optimize end user services by receiving performance measurements, dividing them into snapshots, and determining compliance with user expectations, with an analyser module to assess compliance and an optimiser module to apply necessary network optimizations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Difficulty of detecting and measuring

If semantic techniques are applied to analyze service sessions, then analysis capability is improved, but CPU and memory usage increase

Engineering Contradiction:
Improveservice quality analysis capabilityVSAvoidCPU and memory usage
Core Design Contradiction:
Difficulty of detecting and measuringVSUse of energy by moving object

Solution Approach 1:

The patent divides the service session analysis into discrete snapshots at defined intervals rather than continuous monitoring. Each snapshot captures service quality metrics at a specific point in time, allowing the system to process manageable portions of data sequentially. This segmentation reduces memory requirements by not holding all service session data simultaneously and reduces CPU usage by processing discrete time-bound segments rather than continuous streams.

Inventive Principle:
Principle #1Segmentation

2Loss of information

If comprehensive service monitoring is implemented, then service quality understanding is improved, but system complexity increases

Engineering Contradiction:
Improveservice quality information completenessVSAvoidmonitoring system complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent establishes service quality expectations and thresholds in advance before actual service delivery occurs. These pre-defined criteria include service level agreements, quality targets, and compliance thresholds that are configured beforehand. During service session monitoring, the system simply compares actual metrics against these pre-established benchmarks, eliminating the need for complex real-time analysis algorithms and reducing system complexity while maintaining comprehensive monitoring capability.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If continuous service session monitoring is performed, then service quality detection is improved, but processing time increases

Engineering Contradiction:
Improveservice quality detection reliabilityVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements periodic monitoring of service sessions by capturing snapshots at defined time intervals rather than continuous monitoring. This approach maintains reliability by systematically sampling service quality at regular intervals, ensuring that service issues are detected within known time windows. The periodic nature reduces processing time requirements compared to continuous monitoring, as the system only needs to analyze service metrics at discrete intervals rather than maintaining constant analysis capability.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS9917763B2Method and apparatus for analyzing a service in a service session
Publication Date: 2018.03.13 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US9917763B2 patent drawing
  • US9917763B2 patent drawing
  • US9917763B2 patent drawing

AI summary

A service provided to an end user in a service session is analyzed. A plurality of measurements of at least one performance parameter of a network providing a service to an end user in a service session is received (501). The received plurality of measurements of the at least one performance parameter are divided (503) into a plurality of snapshots. The service is analyzed (505) by determining the compliance of the received measurements to the expectations of the end user for that service session within a snapshot.