Observer Role in Calendar Notification Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing meeting scheduling systems on portable electronic devices do not efficiently notify interested parties of meeting schedules without requiring them to accept invitations, leading to duplication of effort and information when sending updates or changes.

Innovation Solution

A method is introduced where an observer can be added to a calendar event, allowing them to receive a notification of the meeting details without the option to accept or decline, with the event time displayed as free time, and updates or changes can be sent to the observer via email.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If an interested party is added as an invitee to a meeting, then they receive meeting information, but they cannot view the meeting details later if they decline the invitation

Engineering Contradiction:
Improvemeeting information retentionVSAvoidinvitation acceptance requirement
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The system segments the traditional invitee role into two distinct roles: invitees who can accept/decline meetings and observers who can only view meeting information. This segmentation allows interested parties to receive and retain meeting information without the requirement to accept or decline invitations, resolving the contradiction between information retention and operational simplicity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Instead of requiring invitees to accept invitations to view meeting details, the system inverts the approach by creating an observer role that automatically receives and can view meeting information without acceptance. This inversion eliminates the barrier of requiring invitation acceptance while ensuring information delivery.

Inventive Principle:
Principle #13The other way round (Inversion)

2Loss of information

If a separate e-mail is sent to notify an interested party of meeting details, then they receive the information, but it requires duplicating information already input during scheduling

Engineering Contradiction:
Improvemeeting notification deliveryVSAvoidnotification process complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system merges the meeting information storage and notification delivery functions into a single integrated process. When a meeting is scheduled, the information is automatically stored and made accessible to observers without requiring separate email composition and sending. This consolidation eliminates information duplication and reduces process complexity while ensuring reliable notification delivery.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The meeting information storage system serves multiple functions: it stores meeting details for invitees, provides view-only access to observers, and enables automatic notification delivery. This multi-functionality eliminates the need for separate notification processes and reduces overall system complexity while maintaining comprehensive information delivery.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Loss of information

If meeting updates are sent to interested parties via separate e-mails, then they receive changes, but it requires repeated manual effort for each update

Engineering Contradiction:
Improvemeeting update deliveryVSAvoidupdate notification efficiency
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The system implements automatic feedback mechanisms where observers are notified of meeting changes through the existing calendar event update process. When meeting details are modified, the system automatically detects the change and notifies affected observers without requiring manual intervention. This feedback loop ensures timely update delivery while eliminating repeated manual effort.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs preliminary setup by establishing observer relationships during meeting creation. This preliminary action configures automatic notification pathways in advance, so that subsequent updates are delivered automatically without requiring repeated manual notification actions. The preliminary configuration enables efficient ongoing update delivery.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9552571B2Electronic device and method of meeting notification
Publication Date: 2017.01.24 MALIKIE INNOVATIONS LTD
  • US9552571B2 patent drawing
  • US9552571B2 patent drawing
  • US9552571B2 patent drawing

AI summary

A method of providing a meeting notification includes adding an indication of an observer to a calendar event in a calendar graphical user interface at an organizer electronic device, saving the calendar event associated with the observer at the organizer electronic device, and sending an observer electronic message from the organizer electronic device to an observer electronic device. The observer electronic message includes the calendar event for storage at the observer electronic device with a period of time, associated with the calendar event, indicated as free time.