Presence Server Event Sequence Notification Logic

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current presence notification systems in communications systems lack the ability to specify notification triggers based on historical and future values of presence information elements, ordered or unordered sequences of events, and time period parameters, which are insufficient for advanced user scenarios such as public safety applications.

Innovation Solution

A method and apparatus that allow clients to subscribe to presence notifications based on a sequence of events, including a time period parameter, enabling the presence server to monitor and send notifications when the specified sequence of events occurs, using advanced Boolean logic to define triggers and reference past and future presence information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If simple subscription and notification mechanism is used, then ease of operation is improved, but adaptability to complex user scenarios deteriorates

Engineering Contradiction:
Improvesimplicity of subscription mechanismVSAvoidcapability to specify complex notification triggers
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The notification trigger is segmented into multiple independent components: sequence of events, time period parameters, and Boolean logic conditions. Each component can be independently configured and combined to create complex notification scenarios while maintaining a structured and manageable interface for users.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system dynamically evaluates presence information changes against the configured sequence of events and time parameters in real-time. The notification mechanism adapts to different user scenarios by dynamically interpreting and executing complex trigger conditions without requiring users to manually configure every detail.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If presence server monitors sequence of events with time parameters, then adaptability to complex scenarios is improved, but device complexity increases

Engineering Contradiction:
Improvecapability for sequence-based notificationsVSAvoidcomplexity of presence server processing
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The presence server pre-processes and stores presence information in a structured format, maintaining historical records and current state data. When a notification trigger is configured, the server retrieves relevant historical and current presence data to evaluate whether the sequence of events has occurred within the specified time parameters, reducing real-time processing complexity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system introduces an intermediary evaluation layer that acts as a mediator between the presence server and the notification mechanism. This intermediary component handles the complex logic of sequence evaluation and time parameter checking, allowing the presence server to maintain a simpler core architecture while still supporting advanced notification scenarios.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP2519888B1Methods for presence notification based on a sequence of events
Publication Date: 2018.04.04 MOTOROLA SOLUTIONS INC
  • EP2519888B1 patent drawingFigure 1
  • EP2519888B1 patent drawingFigure 2~3
  • EP2519888B1 patent drawingFigure 4

AI summary

A client entity generates a subscription to a presentity that includes a sequence of events which define a trigger that controls when a presence server sends a notification to the client entity; and the subscription further indicates a time period parameter for the sequence of events. Upon receiving (302) the subscription, the presence server receives and monitors (304) presence information based on the indicated time period parameter to detect an occurrence of the sequence of events, and sends (306) the notification to the client entity when the presence information satisfies the trigger.