Dynamic Calendar Availability Interface for Multi-Server Compatibility

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current mobile device systems for entering event details, particularly availability status, lack intuitive interfaces, which hampers user experience and efficiency in scheduling events.

Innovation Solution

An electronic device configured to determine the type of remote server it communicates with and sets availability status options for calendar events based on this type, generating a user interface screen with an availability status field that allows users to select from options dependent on the server type, enabling seamless data exchange with a remote server.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a fixed availability status interface is provided for all server types, then device complexity is reduced, but adaptability to different server types deteriorates

Engineering Contradiction:
Improveadaptability to different server typesVSAvoidinterface complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The availability status field dynamically changes its options based on the detected server type. The interface transitions from a static fixed set of options to a dynamic adaptive set of options that automatically adjusts according to the communication protocol requirements of different servers (e.g., Exchange, Lotus Domino, GroupWise), resolving the contradiction between adaptability and complexity.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the parameter of available status options based on server type detection. Different server types trigger different sets of availability status options (e.g., 'Free', 'Busy', 'Tentative' for Exchange servers vs. different options for Lotus Domino or GroupWise), allowing the interface to adapt to server-specific requirements without increasing overall complexity.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If multiple fixed availability status options are provided for all server types, then adaptability is improved, but ease of operation deteriorates

Engineering Contradiction:
Improvecompatibility with different serversVSAvoiduser input simplicity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The system performs self-service by automatically detecting the server type and configuring the appropriate availability status options without requiring user intervention. The device autonomously identifies whether it is communicating with an Exchange, Lotus Domino, or GroupWise server and sets the corresponding options, eliminating the need for users to manually configure settings and simplifying operation.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary action by pre-configuring the availability status options based on the detected server type before the user needs to enter event details. The correct options are automatically prepared and displayed in advance, so users don't need to understand server-specific requirements or perform manual configuration, improving ease of operation while maintaining adaptability.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If a generic availability status field is used for all server types, then device complexity is reduced, but data exchange reliability deteriorates

Engineering Contradiction:
Improvedata exchange compatibilityVSAvoidinterface configuration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements feedback by detecting the server type from communication protocols and using this information to configure the availability status field accordingly. The feedback loop ensures that the interface automatically adapts to server-specific requirements, maintaining data exchange reliability without requiring manual configuration of complex server parameters.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The server type detection mechanism acts as an intermediary between the user interface and the data exchange layer. It translates generic user input into server-specific formatted data by first identifying the target server type and then configuring the appropriate options, ensuring reliable data exchange while keeping the user interface simple and generic.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUSRE50149E1Free busy calendar interface
Publication Date: 2024.09.24 MALIKIE INNOVATIONS LTD
  • USRE50149E1 patent drawing
  • USRE50149E1 patent drawing
  • USRE50149E1 patent drawing

AI summary

A method and electronic device which provide a calendar having availability status options based on a type of remote server are described. In accordance with one embodiment, there is provided a method comprising: determining, by an electronic device, a type of a remote server in communication with the electronic device; and setting, by the electronic device, availability status options for an availability status field for calendar events based on the type of the remote server.