SEAL Notification Management Trigger Mechanism

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing pull notification systems in 5G mobile communication technologies face challenges such as increased resource consumption due to frequent polling or long polling methods, leading to heightened network traffic and resource wastage.

Innovation Solution

The introduction of a 'device trigger' or 'application trigger' mechanism within the service enabler architecture layer (SEAL) notification management service allows the notification management client (SNM-C) to initiate a pull notification message procedure only when outstanding notifications are available from the notification management server (SNM-S), thereby reducing unnecessary resource consumption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If frequent polling or long polling methods are used in pull notification systems, then notification delivery reliability is improved, but network traffic increases and resource consumption increases

Engineering Contradiction:

Improvenotification delivery reliabilityVSAvoidresource consumption

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The patent implements a feedback mechanism where the notification management server (SNM-S) sends a trigger signal to the notification management client (SNM-C) when notifications are available. This feedback-based approach eliminates the need for continuous polling, as the system automatically notifies the client when data is ready, thereby reducing resource consumption while maintaining reliable notification delivery.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system enables self-service operation where the server proactively triggers notification pulls when content is available, rather than passively waiting for client requests. This self-service mechanism reduces unnecessary polling operations and optimizes resource utilization while ensuring reliable notification delivery.

Inventive Principle:

Principle #25Self-service

2Reliability

If frequent polling or long polling methods are used in pull notification systems, then notification delivery reliability is improved, but network traffic increases

Engineering Contradiction:

Improvenotification delivery reliabilityVSAvoidnetwork traffic

Core Design Contradiction:

ReliabilityVSObject-generated harmful factors

Solution Approach 1:

The patent implements a feedback mechanism where the notification management server (SNM-S) sends a trigger signal to the notification management client (SNM-C) when notifications are available. This feedback-based approach eliminates the need for continuous polling, as the system automatically notifies the client when data is ready, thereby reducing network traffic while maintaining reliable notification delivery.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system replaces continuous or frequent periodic polling with event-driven periodic action, where notifications are pulled only when content is available. This transforms the polling mechanism from time-based to event-based, significantly reducing network traffic while preserving notification delivery reliability.

Inventive Principle:

Principle #19Periodic action

3Speed

If pull notification message procedure is initiated continuously, then notification responsiveness is improved, but device resource consumption increases

Engineering Contradiction:

Improvenotification responsivenessVSAvoiddevice resource consumption

Core Design Contradiction:

SpeedVSUse of energy by moving object

Solution Approach 1:

The patent implements a feedback mechanism where the notification management server (SNM-S) sends a trigger signal to the notification management client (SNM-C) when notifications are available. This feedback-based approach ensures the client only pulls notifications when necessary, maintaining responsive notification delivery while avoiding unnecessary resource consumption from continuous polling.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system dynamically adjusts notification pull behavior based on availability conditions. Instead of continuous or fixed-interval polling, the system transitions to a dynamic model where pull operations are triggered only when content is available, optimizing the balance between notification responsiveness and device resource consumption.

Inventive Principle:

Principle #15Dynamics

Data Source

PatentUS20250142306A1Method and apparatus for managing a pull notification message trigger in a seal notification management service

Publication Date: 2025.05.01 SAMSUNG ELECTRONICS CO LTD

AI summary

Embodiments of the disclosure describe a method for managing a PULL notification message trigger procedure to enable a service enabler architecture layer (SEAL) notification management client (SNM-C) 200 to share a pull notification message trigger indication to a SEAL notification management server (SNM-S) 300. The updates to the existing create notification channel procedures to manage a pull notification message triggers (PNMT) in SEAL notification management services are performed. Further, a new pull notification message trigger information field represents the SNM-C 200 indication to support such application triggers to initiate the pull notification message procedure. The method for the SNM-C 200 to encode the pull notification message trigger information field as part of the create notification channel request information element sent in a HTTP request body to the SNM-S 300.