Mobile Context Service Sharing Middleware

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current mobile applications face limitations in communication and data sharing due to unidirectional and non-scalable ad-hoc communication configurations, requiring each application to set up multiple APIs and interfaces, which leads to significant overhead and inefficiency, especially when a large number of applications need to share data.

Innovation Solution

A mobile platform with a uniform communication framework and sharing middleware system that enables seamless data sharing among mobile applications by using a single API, allowing applications to communicate and share data through a 'materialized shared space' facilitated by a sharing negotiation tool, capacity planning, and services like mobile context, recommendation, and business analytics.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If each mobile application sets up its own API and interfaces for data sharing, then data sharing capability is achieved, but device complexity and overhead increase significantly

Engineering Contradiction:
Improvedata sharing capabilityVSAvoidnumber of APIs and interfaces
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a shared data store as an intermediary component that enables multiple mobile applications to access and share data without requiring each application to set up separate APIs and interfaces. The shared data store acts as a central repository that applications can interact with through standardized mechanisms, eliminating the need for N(N-1) pairwise interfaces and reducing system complexity while maintaining data sharing capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If each application sets up interfaces for every other application it needs to communicate with, then communication between applications is enabled, but loss of time for setup and maintenance increases

Engineering Contradiction:
Improvecommunication capabilityVSAvoidtime for setup and maintenance
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements a universal shared data store that serves multiple applications simultaneously with a single interface. Instead of requiring each application to establish separate communication channels with every other application, the shared data store provides a multi-functional platform where any application can access data from any other application through the same standardized interface, dramatically reducing setup and maintenance time.

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

3Adaptability or versatility

If applications use ad-hoc communication configuration, then flexibility in data sharing is achieved, but ease of operation deteriorates due to manual configuration requirements

Engineering Contradiction:
Improvedata sharing flexibilityVSAvoidconfiguration simplicity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent enables applications to automatically access and share data through the shared data store without requiring manual configuration of interfaces and APIs. The system provides self-service capabilities where applications can independently interact with the shared data store using standardized protocols, eliminating the need for complex ad-hoc configuration while maintaining data sharing flexibility.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8763010B2System and method for gathering context parameters to determine a mobile user context
Publication Date: 2014.06.24 NEC CORP
  • US8763010B2 patent drawing
  • US8763010B2 patent drawing
  • US8763010B2 patent drawing

AI summary

A system and method for data sharing are provided. Context parameters associated with a user are gathered from a plurality of applications. A mobile context of the user is determined based on the gathered context parameters. Content is presented to the user in accordance with the mobile context of the user.