Instant Messaging Protocol for Multi-Server Contact Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing instant messaging (IM) protocols face challenges in configuring client devices to be compatible with multiple enterprise IM servers, leading to difficulties in seamless communication and contact list management across different server platforms.

Innovation Solution

A protocol that enables a client device to communicate with various enterprise IM servers by using an ID tag for contact list management, persisting a local copy of the contact list, and automatically sending updates upon login, while also providing a consistent user experience through images and text definitions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a client device is configured to work with a specific enterprise IM server, then communication reliability with that server is improved, but adaptability to communicate with multiple different IM servers deteriorates

Engineering Contradiction:
Improvecommunication reliabilityVSAvoidserver compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent implements a universal protocol layer that enables a single client device to communicate with multiple different enterprise IM servers (Lotus Sametime, GroupWise, Office Live Communications Server) through a common interface, making the client multi-functional across different server platforms while maintaining reliable communication with each

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

2Measurement precision

If contact list management is performed separately for each IM server, then server-specific communication precision is improved, but device complexity increases

Engineering Contradiction:
Improvecontact list accuracyVSAvoidconfiguration complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent merges contact list management operations into a unified protocol that handles contact list retrieval, updates, and synchronization across multiple IM servers through a single standardized interface, reducing device complexity while maintaining contact list accuracy through consistent handling methods

Inventive Principle:
Principle #5Merging (Combining)

3Manufacturing precision

If manual configuration is used for each IM server, then configuration precision is improved, but ease of operation deteriorates

Engineering Contradiction:
Improveconfiguration accuracyVSAvoidconfiguration ease
Core Design Contradiction:
Manufacturing precisionVSEase of operation

Solution Approach 1:

The patent implements automatic server detection and configuration capabilities where the client device autonomously identifies available IM servers, retrieves contact lists, and configures communication parameters without requiring manual user input, thereby maintaining configuration accuracy while dramatically improving ease of operation

Inventive Principle:
Principle #25Self-service

Data Source

PatentEP2362595B1Instant messaging device/server protocol
Publication Date: 2019.10.23 BLACKBERRY LTD
  • EP2362595B1 patent drawingFigure 1
  • EP2362595B1 patent drawingFigure 2
  • EP2362595B1 patent drawingFigure 3

AI summary

A generic IM device/server protocol permits a single implementation of a IM application on client devices for communicating with different enterprise IM servers types. The protocol defines a server maintained tag to identify the currency of a contact list it is managing for a client device. The client device receives and persists the tag and provides it at login. The server automatically sends a contact list update only if the tag indicates the client devices contact list instance is not current. Presence updates may also be sent automatically at login and the client device need not separately request contact list or presence updates at login. The client device may be pre-provisioned with respective graphics, text and server capabilities for multiple server types. A specific IM configuration may be selected in response to service information.