Messaging System Application Data Payload Extraction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current messaging systems lack the ability to effectively share and integrate application data across different services, limiting the context-aware configuration and interoperability of application services within messaging conversations.

Innovation Solution

The proposed solution involves a messaging system that extracts application data payloads from message packages, recommends relevant application services based on embedded identifiers, and transmits this data to those services, enabling context-aware interactions and enhanced interoperability between messaging clients and application services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If messaging systems only support text-based conversations, then system simplicity is maintained, but application data sharing and service interoperability are limited

Engineering Contradiction:
Improveapplication data sharing capabilityVSAvoidmessaging system architecture
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The message package is segmented into distinct components: message header, application data payload, and application service recommendation package. This segmentation allows the messaging system to handle different types of data separately, enabling application data sharing while maintaining core messaging functionality and reducing overall system complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The messaging system is enhanced with multi-functionality by integrating application data payload extraction, application service recommendation, and application interoperation capabilities into the existing messaging infrastructure, allowing the same system to handle both traditional text messaging and application data sharing.

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

2Adaptability or versatility

If messaging systems integrate multiple application services, then service interoperability improves, but system complexity increases

Engineering Contradiction:
Improveservice interoperabilityVSAvoidsystem integration architecture
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The messaging client acts as an intermediary between the messaging service and application services. It receives message packages, extracts application data payloads, obtains application service recommendations, and transmits data to recommended application services, thereby enabling service interoperability without requiring direct integration between all services.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The application service recommendation package is prepared in advance by the messaging service, containing pre-identified application services that can handle the application data payload. This preliminary action simplifies the integration process by providing a ready-made mapping between data types and suitable application services.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If application data is transmitted without service recommendations, then transmission speed is maintained, but context-aware configuration is lost

Engineering Contradiction:
Improvecontext-aware configurationVSAvoiddata transmission process
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The messaging service provides feedback to the messaging client by sending an application service recommendation package that identifies suitable application services for the received application data payload. This feedback mechanism enables context-aware configuration by matching data types with appropriate services, improving reliability without significantly complicating the transmission process.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9891970B2Techniques to share application data through a messaging system
Publication Date: 2018.02.13 META PLATFORMS INC
  • US9891970B2 patent drawing
  • US9891970B2 patent drawing
  • US9891970B2 patent drawing

AI summary

Techniques to share application data through a messaging system are described. In one embodiment, an apparatus may comprise a messaging component operative to receive a message package from a messaging service at a messaging client on a client device, the message package addressed from a source messaging account and addressed to a recipient messaging account, the recipient messaging account associated with the messaging client on the client device; extract an application data payload from the message package; receive an application service recommendation package from the messaging service, the application service recommendation package comprising an application service identifier; and an application interoperation component operative to transmit at least a portion of the application data payload to a recommended application service by the messaging client, the recommended application service identified by the application service identifier. Other embodiments are described and claimed.